[Bug 671282] New: Radeon driver broken in 11.4 RC1.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c0 Summary: Radeon driver broken in 11.4 RC1. Classification: openSUSE Product: openSUSE 11.4 Version: RC 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: stiening@comcast.net QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: Customer Blocker: Yes Broken Radeon driver makes install difficult. Screen is black most of the time with only occasional glimpses of install GUI. It might be safer to use frame buffer graphics for the install screens to faclilitate testing. My specific hardware is a motherboard integrated HD 4250 GPU. I have seen this behavior from time to time in the past with other versions of openSUSE but never with drivers directly downloaded from AMD. Frame buffer graphics works fine at 1600x1200. Windows 7 and openSUSE 11.3 do not have the problem described above. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |sndirsch@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c1 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |stiening@comcast.net --- Comment #1 from Stefan Dirsch <sndirsch@novell.com> 2011-02-11 18:04:18 UTC --- We still use fbdev for installation. Sure that you aren't using a LiveCD or an installation running on top of a LiveCD? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Radeon driver broken in |radeon [HD 4250] Black |11.4 RC1. |screen most of the time -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c2 --- Comment #2 from Rae Stiening <stiening@comcast.net> 2011-02-11 21:15:35 UTC --- You are correct, this may not be a Radeon driver problem per se. I installed 11.4 RC1 from a DVD burned from openSUSE-DVD-Build1056-x86_64.iso which I downloaded. I unchecked the "Use Automatic Configuration" box and checked the KDE desktop option. The installation proceeded normally through the reboot. The last screen that I saw before the display went dark was the Hostname step of the Configuration menu. After a few minutes I reset the computer and it booted to the usual Linux boot option screen. I selected Failsafe and was able to complete the missing steps of the configuration menu. If I reboot and select Failsafe I get a framebuffer graphics system that behaves normally. If I select the default the screen is dark. By using the package manager to remove and reinstall the X11 Radeon driver I was able to make a system that worked with Radeon graphics. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c3 --- Comment #3 from Stefan Dirsch <sndirsch@novell.com> 2011-02-11 22:00:55 UTC --- Likely broken radeon KMS driver. Another option would be to try radeonhd driver by adding "nomodeset" boot option. Or switch to UMS radeon driver by additionally uninstallating xorg-x11-driver-video-radeonhd package. Chosing failsafe boot option means "fbdev" driver. The same driver as used during installation.
By using the package manager to remove and reinstall the X11 Radeon driver I was able to make a system that worked with Radeon graphics.
This doesn't make sense. What did you uninstall and reinstall exactly? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c4 --- Comment #4 from Rae Stiening <stiening@comcast.net> 2011-02-11 23:42:39 UTC --- It would probably be best to focus on why the installation fails. I have repeated the installation twice each on two different similar but not identical systems and the outcome was the same each time. Despite the failure, as I indicated it was possible to recover something that would boot with framebuffer graphics. In that state I was able to use yast to remove and reinstall xorg-X11-driver-video-radeonhd. After rebooting the accelerated graphics worked and the screen resolution was set to 1920x1200 which isn't possible with framebuffer graphics. So perhaps the radeon driver isn't the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c5 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|stiening@comcast.net | --- Comment #5 from Stefan Dirsch <sndirsch@novell.com> 2011-02-12 06:50:16 UTC --- Well, without the boot option "nomodeset" the radeonhd driver isn't used at all. Uninstalling and reinstalling radeonhd driver package doesn't change anything either. I do not understand the change in behaviour. I would understand the behaviour only if you would have been running the installation from a LiveCD, where we still have a race (radeon kernel module not loaded in time for X). This would be another dup of bnc #609607. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c6 --- Comment #6 from Rae Stiening <stiening@comcast.net> 2011-02-12 14:16:33 UTC --- At the install welcome screen I selected the option "Check Installation Media". No errors were found. To see if the KDE or X11 were responsible for the reported behavior I made the following test: At the desktop selection screen I chose "Minimal Server Selection", i.e. text mode. That installation came to a halt at the installation submenu "Perform Installation" stage with the message: "An error occurred during initrd creation." /sbin/mkinitrd illegal option -- s Clicking on the OK resulted in the screen going blank. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c7 --- Comment #7 from Stefan Dirsch <sndirsch@novell.com> 2011-02-12 14:21:43 UTC --- (In reply to comment #6)
To see if the KDE or X11 were responsible for the reported behavior I made the following test:
At the desktop selection screen I chose "Minimal Server Selection", i.e. text mode. That installation came to a halt at the installation submenu "Perform Installation" stage with the message:
"An error occurred during initrd creation." /sbin/mkinitrd illegal option -- s
Clicking on the OK resulted in the screen going blank.
Indeed that's unrelated to any X drivers ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c8 --- Comment #8 from Stefan Dirsch <sndirsch@novell.com> 2011-02-12 14:32:37 UTC --- mkinitrd issue with minimal installation: https://bugzilla.novell.com/show_bug.cgi?id=663764 https://bugzilla.novell.com/show_bug.cgi?id=670225 This seems completely unrelated to the initial issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c9 --- Comment #9 from Rae Stiening <stiening@comcast.net> 2011-02-12 16:48:43 UTC --- I agree that the mkinitrd issue is not relevant to the problem I reported. To get a more precise record of where the installation crashed I made an iPhone movie of the screen and stepped through it frame by frame. The installation went normally through the reboot. The first time the screen goes black is when it is "Preparing the initial system configuration." in the "Check Installation" phase the "Configuration" step. The screen comes alive again and reports that it is "Loading the Package Manager". The screen briefly goes black again and then the install moves on to "Hostname". The last step visible on the screen before it goes black forever is "Hostname and Domain Name". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c10 --- Comment #10 from Stefan Dirsch <sndirsch@novell.com> 2011-02-12 20:05:47 UTC --- Ok. Then my current guess is that this freeze happens during hardware detection and is likely unrelated to X. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c11 --- Comment #11 from Rae Stiening <stiening@comcast.net> 2011-02-12 21:23:26 UTC --- I asked my monitor what resolution it was using while the last screen before the crash was displayed. It said 1920 x 1200. I thought that the maximum frame buffer resolution was 1600 x 1200. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c12 --- Comment #12 from Stefan Dirsch <sndirsch@novell.com> 2011-02-12 21:26:55 UTC --- (In reply to comment #11)
I asked my monitor what resolution it was using while the last screen before the crash was displayed. It said 1920 x 1200. I thought that the maximum frame buffer resolution was 1600 x 1200.
Depends on the graphics card's BIOS. ==> hwinfo --framebuffer -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c13 --- Comment #13 from Rae Stiening <stiening@comcast.net> 2011-02-12 22:13:06 UTC --- This is what hwinfo reported when running 11.3. The graphics are on the motherboard with 128k of sideport memory and as-required system memory. The particular motherboard is ASUS M4A88TD-V EVO/USB3. <6>[ 1.420197] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90011800000, using 7500k, total 16384k <6>[ 1.420199] vesafb: mode is 1600x1200x16, linelength=3200, pages=3 <6>[ 1.420200] vesafb: scrolling: redraw <6>[ 1.420201] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 <6>[ 1.420326] bootsplash 3.1.6-2004/03/31: looking for picture... <6>[ 1.420328] bootsplash: silentjpeg size 164791 bytes <6>[ 1.461275] bootsplash: scaling image from 1920x1200 to 1600x1200 <6>[ 1.622609] bootsplash: scaling image from 1920x1200 to 1600x1200 <4>[ 1.648008] Console: switching to colour frame buffer device 196x71 <6>[ 1.669743] bootsplash: scaling image from 1920x1200 to 1600x1200 <6>[ 1.831986] bootsplash: scaling image from 1920x1200 to 1600x1200 <6>[ 1.857491] fb0: VESA VGA frame buffer device -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c14 --- Comment #14 from Stefan Dirsch <sndirsch@novell.com> 2011-02-12 22:19:16 UTC --- So you used 1600x1200 framebuffer mode on openSUSE 11.3. What does that tell us? Nothing ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c15 --- Comment #15 from Rae Stiening <stiening@comcast.net> 2011-02-25 23:19:15 UTC --- The problem I reported is not present in 11.4 RC2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671282 https://bugzilla.novell.com/show_bug.cgi?id=671282#c16 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #16 from Stefan Dirsch <sndirsch@novell.com> 2011-02-25 23:39:50 UTC --- Ok. Then it must have been fixed. Likely in KMS. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com