package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[KIPY]

Each time I want to use ATI driver suggested I deeply crash the session.
The computer is a PACKARD BELL portable Proc SU4100 fited with ATI HD 4330 graphic card

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue Oct 26 16:23:12 2010
DkmsStatus:

ErrorMessage: subprocess installed post-installation script returned error exit status 1
GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
MachineType: Packard Bell EN Butterfly s
ProcCmdLine: locale=fr_FR bootkbd=fr-latin1 console-setup/layoutcode=fr console-setup/variantcode=oss noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.gz splash -- BOOT_IMAGE=/casper/vmlinuz
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
dmi.bios.date: 09/14/2009
dmi.bios.vendor: Packard Bell
dmi.bios.version: V1.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: EN Butterfly s
dmi.board.vendor: Packard Bell
dmi.board.version: PSMBOU-1234567
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: None
dmi.modalias: dmi:bvnPackardBell:bvrV1.14:bd09/14/2009:svnPackardBell:pnENButterflys:pvrV1.14:rvnPackardBell:rnENButterflys:rvrPSMBOU-1234567:cvnPackardBell:ct10:cvrNone:
dmi.product.name: EN Butterfly s
dmi.product.version: V1.14
dmi.sys.vendor: Packard Bell
glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic

[Felix Kuehling (felix-kuehling)]

Your Xorg.0.log shows you're using the Intel driver. So I guess your laptop has Switchable graphics and the Intel graphics device is the one that's enabled by default. The only way for you to use the RadeonHD 4330 under Linux at this time is to disable the Intel graphics in the BIOS setup. If your BIOS setup doesn't have such an option, or if your laptop doesn't have a hardware MUX to connect the Radeon to the display outputs, you're stuck with the Intel integrated graphics under Linux.

[KIPY (carremichel)]

Thank you very much for your time, I will try your suggestions in as soon as
possible

2010/10/26 Felix Kuehling <email address hidden>

> Your Xorg.0.log shows you're using the Intel driver. So I guess your
> laptop has Switchable graphics and the Intel graphics device is the one
> that's enabled by default. The only way for you to use the RadeonHD 4330
> under Linux at this time is to disable the Intel graphics in the BIOS
> setup. If your BIOS setup doesn't have such an option, or if your laptop
> doesn't have a hardware MUX to connect the Radeon to the display
> outputs, you're stuck with the Intel integrated graphics under Linux.
>
> --
> package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
> https://bugs.launchpad.net/bugs/666807
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “fglrx-installer” package in Ubuntu: New
>
> Bug description:
> Each time I want to use ATI driver suggested I deeply crash the session.
> The computer is a PACKARD BELL portable Proc SU4100 fited with ATI HD 4330
> graphic card
>
> ProblemType: Package
> DistroRelease: Ubuntu 10.04
> Package: fglrx 2:8.723.1-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-22-generic i686
> Architecture: i386
> Date: Tue Oct 26 16:23:12 2010
> DkmsStatus:
>
> ErrorMessage: subprocess installed post-installation script returned error
> exit status 1
> GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit
> code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
> GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit
> code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
> LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
> MachineType: Packard Bell EN Butterfly s
> ProcCmdLine: locale=fr_FR bootkbd=fr-latin1 console-setup/layoutcode=fr
> console-setup/variantcode=oss noprompt cdrom-detect/try-usb=true persistent
> file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.gz
> splash -- BOOT_IMAGE=/casper/vmlinuz
> SourcePackage: fglrx-installer
> Title: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade:
> subprocess installed post-installation script returned error exit status 1
> dmi.bios.date: 09/14/2009
> dmi.bios.vendor: Packard Bell
> dmi.bios.version: V1.14
> dmi.board.asset.tag: Base Board Asset Tag
> dmi.board.name: EN Butterfly s
> dmi.board.vendor: Packard Bell
> dmi.board.version: PSMBOU-1234567
> dmi.chassis.type: 10
> dmi.chassis.vendor: Packard Bell
> dmi.chassis.version: None
> dmi.modalias:
> dmi:bvnPackardBell:bvrV1.14:bd09/14/2009:svnPackardBell:pnENButterflys:pvrV1.14:rvnPackardBell:rnENButterflys:rvrPSMBOU-1234567:cvnPackardBell:ct10:cvrNone:
> dmi.product.name: EN Butterfly s
> dmi.product.version: V1.14
> dmi.sys.vendor: Packard Bell
> glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type
> system:
> distro: Ubuntu
> codename: lucid
> architecture: i686
> kernel: 2.6.32-22-generic
>
> To unsubscribe from this bug, go to:
>
>...

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 557023, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.