no more graphical screen after fglrx intallation through system settings interface

Bug #1030151 reported by Thomas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm running Quantal alpha 3 and few nights ago the new interface to install the proprietary drivers landed. I decided to test it and selected fglrx a the driver I wan to use for my graphic card (HD5770). The other choice was fglrx-update but I picked the first of the two since no more explanations were provided.

Upon reboot, the computer throw me back to tty1 and a console login prompt. On tty7 the last message displayed is :
* Stopping save kernel messages [OK]

cat /var/log/Xorg.0.g | grep EE give :
[ timestamp] (WW) No matchingDevice section for instance (BusID PCI:0@2:0:1) found

Nothing special pop in dmesg nor in kern.log about fglrx though I have a lot of error about fd0 which is the floppy disk I don't have I guess.

I'm pretty stuck right now since I don't know how to remove fglrx and revert to the xorg ati driver by command line, cleanly. I also ignore if the new interface for proprietary drivers has a command line interface...

Cheers,
Thomas
---
.tmp.unity.support.test.0:

ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
DistUpgraded: Fresh install
DistroCodename: quantal
DistroRelease: Ubuntu 12.10
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Juniper [Radeon HD 5700 Series] [1002:68b8] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:0344]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
MachineType: Gigabyte Technology Co., Ltd. EX58-DS4
Package: fglrx-installer (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-6-generic root=UUID=d5cc10bb-b9e9-43e9-8864-eb2d33b8e760 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Tags: quantal ubuntu regression reproducible compiz-0.9
Uname: Linux 3.5.0-6-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/11/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11
dmi.board.name: EX58-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnEX58-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX58-DS4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EX58-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.37-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~really6.14.4-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1

tags: added: quantal
description: updated
Revision history for this message
Edward Donovan (edward.donovan) wrote :

Thomas, I don't know what problem fglrx is having, but I'll try to help get your system usable again.

To get rid of fglrx, run:

  sudo apt-get purge fglrx

(You could use 'remove' as well as 'purge'. 'purge' removes the leftover configuration files, too, which probably isn't a big difference in this case.) That should remove it cleanly.

And then reboot. When fglrx is not present, the Xorg ATI driver should run automatically, again.

To pursue this problem, it would help to file the bug with Ubuntu's bug reporting program, apport. It will collect information about the hardware and software of your system, that will be needed to examine what's going on. You can do that for this existing bug report, by running the command:

  apport-collect 1030151

When you make new bug reports, it's 'apport-bug' from the command line. (Also available as 'ubuntu-bug' if that's easier to remember.) Thanks, and I hope this helps!

Revision history for this message
Thomas (thcourbon) wrote :

Heelo Edward,

Thank you for helping me out. I had memory of a time where removing fglrx was a lot more complicated than that.

Thank to you my computer is shining again.

On another topic, I can't run apport-collect, python crashes on a TypeError about unicode missing a buffer interface...

I'll try to look into it tomorrow morning.

Revision history for this message
Edward Donovan (edward.donovan) wrote :

Hey, Thomas, that's great!

It's hard to keep working on a bug when the tools crash, so thanks for trying. Searching around a little about apport and Unicode, I see bug reports like this:

  Apport console frontend (ubuntu-bug, apport-cli) doesn't work with non-English locales
  Bug 492290

I wonder if that could be it, if your Ubuntu machine is set for a French, or other, locale?

If that might be it, people there have been able to use apport from the terminal, if they run it under a generic locale. That could look like:

  LC_ALL=C apport-collect 1030151

or

  LANG=C apport-collect 1030151

Those are probably pretty equivalent for our purposes; I don't know enough about locales.

Revision history for this message
Thomas (thcourbon) wrote :

Hi Edward,

Despite setting the LC_ALL or LANG variable to C apport-collect does not work. You were right about the fact my locale is french but I'm not sure that issue is related to 492290 (though I think it's definetly related to non-english locale). I can do my share of python programming so I'll try to unroll the issue.

Thank for your help.

Revision history for this message
Thomas (thcourbon) wrote : BootDmesg.txt

apport information

tags: added: apport-collected compiz-0.9 regression reproducible ubuntu
description: updated
Revision history for this message
Thomas (thcourbon) wrote : BootLog.gz

apport information

Revision history for this message
Thomas (thcourbon) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : DpkgLog.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : GconfCompiz.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : LightdmLog.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : Lspci.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : Lsusb.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : ProcModules.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : UdevDb.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : UdevLog.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : UnitySupportTest.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : XorgLog.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : XorgLogOld.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : Xrandr.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote : xdpyinfo.txt

apport information

Revision history for this message
Thomas (thcourbon) wrote :

I manage to get apport working (filed a bug under #1030483 about that, I also describe the workaround I used).

I can try to reinstall fglrx to reproduce the problem and run apport again if necessary.

Revision history for this message
Edward Donovan (edward.donovan) wrote :

I think you're right, if anyone looks into the fglrx problem, they'd probably like another apport-collect run, after reproducing that crash.

Nice job on bug 1030483. :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.