fglrx - gutsy - ati: Black Screen with ATI RV535 [Radeon X1650 Series] [1002:71c7]

Bug #146515 reported by marianito
10
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Fix Released
High
Unassigned
linux-restricted-modules-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Im currently using Ubuntu Gutsy Beta (fresh installation), after enable Restricted Drivers y get a Black Screen.

My Chipset: GeForce 6100-m9 (with graphic card onboard)
Graphic Card: Ati Radeon X1650 (PCI-E)

Vesa offcourse works.

Revision history for this message
marianito (rgambra) wrote : Xorg.conf
Revision history for this message
marianito (rgambra) wrote : /var/log/Xorg.0.log
Revision history for this message
marianito (rgambra) wrote : lspci
Revision history for this message
Brian Murray (brian-murray) wrote : Re: fglrx - gutsy - ati: Black Screen

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please also add the full output of 'sudo lspci -vvnn'? This will capture the PCI ID of your video card which would be quite helpful. Thanks in advance.

Changed in xorg:
importance: Undecided → Medium
Revision history for this message
marianito (rgambra) wrote : Full Lspci
Changed in xorg:
status: Incomplete → Triaged
Changed in linux-restricted-modules-2.6.22:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

Just curious about the status of this issue.
I too experience exactly the same problem with my ATI Radeon x1650 on my fresh Gutsy install (as of 6. nov 07): I enable the restricted driver, reboot...and black screen.

The only graphics setting that lets me see the Desktop is 'vesa'. See my attached lspci

Revision history for this message
Paganini (nebanks) wrote :

I also have this bug.

/proc/version:

Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Dec 18 08:02:57 UTC 2007

lspci:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV530LE [Radeon X1600/X1650 PRO] [1002:71c6] (prog-if 00 [VGA])
        Subsystem: PC Partner Limited Unknown device [174b:0850]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at fdef0000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at bc00 [size=256]
        [virtual] Expansion ROM at fde00000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] AGP version 3.0
                Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
                Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000

01:00.1 Display controller [0380]: ATI Technologies Inc RV530LE [Radeon X1650 PRO] (Secondary) [1002:71e6]
        Subsystem: PC Partner Limited Unknown device [174b:0851]
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Region 0: Memory at fdee0000 (64-bit, non-prefetchable) [disabled] [size=64K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Revision history for this message
Bryce Harrington (bryce) wrote :

marianito, can you test against Hardy to see if the issue still exists with the new -fglrx 8.1 driver?

Changed in linux-restricted-modules-2.6.22:
status: Triaged → Incomplete
Revision history for this message
Paganini (nebanks) wrote :

Confirm that this problem still exists with Hardy. I just did a clean install on the same system mentioned previously. The system hangs up with a black scree after booting when using the proprietary fglrx drivers. I have to hit the reset button to reboot. The only way to get the system into a usable state is to boot into recovery mode, and edit XORG.CONF to use the "ati" or "vesa" driver.

Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

Same goes here - exactly the same behaviour on Hardy as on Gutsy.

Revision history for this message
Paganini (nebanks) wrote :

Try changing your AGP aperture size in your BIOS. When I set the AGP aperture size to be the same as the amount of video ram on my card I could boot. I found this solution mentioned on some underground linux forum - not ubuntu related - but I tried it and it seems to work.

Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

Thanks Paganini. That was good constructive advice, only the card is 512 Mb and max setting in my BIOS is 256mb.
Anyway, it did enhance the overall performance a bit but unfortunately it didn't solve my main problem - it only puzzled me further!

After updating from 7.10 to 8.04, in my GRUB boot menu, I have two entries for Ubuntu 8.04: kernel 2.6.22-14-generic and 2.6.22-16-generic.

And of those two, I'm only able to boot normally, sort of, into 2.6.22-14-generic and I can even enable the restricted ATI driver and reboot into this same kernel, now without any black screen - but it seems like the card isn't doing much good.

When I go for 'Appearance' to turn 'Extra' on under Visual Effects, the screen turns all white! Fortunately, I'm able to guess what to do to go back to the None setting.

What's going on.,..????

Revision history for this message
Paganini (nebanks) wrote :

Hi Davur,

I think the white-screen issue is a different bug. There are a lot of useless forum posts about it, but no solution that I have found. I'm a little confused by your post though. Are you saying that you get the white screen when you enable desktop effects using "fglrx?" If so that is very strange. I got the white screen using "ati." I had to *switch* to "fglrx" to get rid of it.

Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

That's correct - enabling the restricted driver (aka 'fglrx') now works with kernel 2.6.22-14 without the screen going black.
On enabling Desktop Effects, the screen goes white instantly.

Same old problem with black screen persists when using kernel 2.6.22-16.

Revision history for this message
easyrider (easyrider) wrote :

I have had same issue on hardy(AGP Radeon X1600). Fixed using Paganini advise.
Thanks.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

Hi again,

well - I have hoped and prayed that Intrepid would bring a solution to this bug but alas: the driver activation just fails a bit more graceful - but still it fails.
During reboot after upgrade, an error msg appeared, stating 'Unsure what to do' regarding multible occurrences of flgrx [something]. But X started up nonetheless and everything appeared to work as before the upgrade, i.e. ATI driver doesn't work.
Then the 'Hardware Drivers' icon appeared and I go there to activate - and hit the designated Activate button, which launches a 'Download and Install' dialog box...which hangs and causes an application crash.

I reboot and this time no error on boot - and I do the Activate Hardware Drivers thing... which apparently works: it downloads the driver and I'm all excitement. I turn on the visual effects under appearence and behold: It does not turn white on me, leaving me blindfolded - but it turns back to 'No visual effects'.

Only thing changed afaik: Graceful fail!

I attach my Xorg.0.log.

Bryce Harrington (bryce)
Changed in fglrx-installer:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Mario Limonciello (superm1) wrote :

Unfortunately, that log is not using the fglrx driver, but instead the radeonhd driver. It looks like you have some inconsistencies among your install. Please follow the following steps to ensure you get everything properly loaded:

1) Open up synaptic and search for "fglrx". Ensure that xorg-driver-fglrx, fglrx-amdcccle, and fglrx-kernel-source are all "Completely Removed"
2) Backup your xorg.conf.
sudo cp /etc/X11/xorg.conf /etc/X11.xorg.conf.old
3) Run the following command to get a standard xorg.conf:
sudo dpkg-reconfigure xserver-xorg
4) Remove the contents of /etc/ati
sudo rm -rf /etc/ati
5) Reactivate the driver using the Hardware Drivers tool
6) Reboot
7) Repost your /var/log/Xog.0.log if the issue persists.

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → Won't Fix
Changed in fglrx-installer:
status: Confirmed → Incomplete
Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

Thanks,

good constructive advice and thorough walkthrough, which I followed perfectly - but still 'desktop effects could not be enabled'.

I followed pts [1-6], hurried to enable desktop effects after reboot, upon which the Download and Install dialog re-appears, runs and the notorious popup says 'desktop effects could not be enabled'.

Bug is alive and kicking, as far as I'm concerned.

I attach new Xorg.0.log, as per your #7

Revision history for this message
Dávur Eyðunsson (ds-profocms) wrote :

Ah...finally - doing [1-6] once more did the trick :) I don't know - I have probably missed one Completely Remove the first time around :S

Anyways...THANKS a bundle - first time I've seen this card do me any good.

Bug is FIXED, as far as I'm concerned :)

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for letting us know you've gotten the issue resolved.

Changed in fglrx-installer:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.