Ubuntu
network-manager package

X freezes after fglrx install via app-installer

Bug #83167 reported by cstrippie
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Completed native install of herd 3 on Dell 1705 w/ Radeon x1400 video. After updating all available items, I used app-install to load ATI fglrx drivers (8.32.5), disabled "composite" in xorg.conf (as always), and restarted. On restart I get login screen, but after logging in, X freezes with only a small white square in the upper left corner of the screen. So far unable to resolve.

Same procedures were used on Herd 2 on this machine without issue.

Revision history for this message
cstrippie (ctfreedom) wrote :

Further info: managed to get the system booted with fglrx. For some reason disconnecting wired ethernet will allow the machine to boot. The ethernet cable can then be reattached and will connect to the internet. Interplay between fglrx & network-manager?

Additional machine config - since network is somehow involved I should note that the machine uses a broadcom 440 10/100 ethernet chip and is configured for DHCP.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Added network-manager ubuntu task. Please report bugs directly against the distro or a package.

Changed in ubuntu-iso-tests:
status: Unconfirmed → Rejected
Revision history for this message
cstrippie (ctfreedom) wrote :

Update #2: installed all available updates today, including the revised 8.32.5 fglrx driver - no change in issue. Even more interesting is that gedit will not launch unless the system is booted without the network attached as listed above. Attempting to launch gedit after connecting network results in nothing (sudo), or a white, empty box (gksudo). In response to this, I installed leafpad, which works without issue no matter what state the machine is in.

Removed/purged all driver files and manually built 8.33.6 driver only to have the build fail. Launched ATI graphical installer, but this also failed.

Brought machine back up with Mesa drivers: still won't boot with net cable attached. Retested gedit failure: still present. Interesting: just launching gedit works fine, it's only when invoked via sudo or gksudo that the problem appears. Still no error messages.

Unknown what common linkages exist between network-manager, fglrx, & gedit.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi, I'm closing this bug as it seems to conflate several issues. It would be great if you could test again with Gutsy and report the different issues separately. Please see: https://wiki.ubuntu.com/DebuggingXorg

Changed in network-manager:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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