1002:9802 graphics driver does not load on boot Radeon HD 6310

[Gerhard Burger]

My machine is a samsung-305u1 (with a AMD Fusion E-350) and I use the open source drivers. Quite regularly the graphics driver does not load on boot and I am stuck with a purple screen. Grub shows fine but when I select Ubuntu I get the purple screen. On a successful boot the purple screen disappears and I see the runscripts (I removed 'quiet splash' from the boot options'), but sometimes the screen merely flickers and stays purple.
However the system is still responsive, I can use Alt+SysReq+REISUB to reboot and I can even ssh to my machine.
According to http://ubuntuforums.org/showthread.php?t=2012657 the problem can also occur on nvidia machines, and by typing the following commands in the grub commandline the system boots fine:
test
continue
videoinfo
normal

The problem seems to occur quite randomly, but by doing the next steps I can reproduce the problem 4 out of 5 times:
1. Boot normally
2. Connect external monitor with larger resolution
3. Close the lid of the laptop ( i guess this turns of the laptop screen)
4. Shutdown
5. Remove the external monitor
6. open the lid and power on

Because I can ssh into the machine i can provide error logs, but I don't know which ones to provide, so someone please point me in the right direction...

WORKAROUND: Setting gfxmode to 'text' lets me boot normally

WORKAROUND: Using the following kernel boot parameter works but this boots my machine to unity 2d:
nomodeset

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gerhard 1664 F.... pulseaudio
 /dev/snd/controlC0: gerhard 1664 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 43'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0xfeb40000 irq 16'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,144dc600,00100100'
   Controls : 19
   Simple ctrls : 11
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=a61a19a0-e46b-4166-ba49-6a56ed9a4673
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=efa624b8-abed-4c31-a30e-08852678e504 ro
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic N/A
 linux-backports-modules-3.2.0-32-generic N/A
 linux-firmware 1.79.1
Tags: precise running-unity
Uname: Linux 3.2.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
dmi.bios.date: 07/29/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 01PS.M002.20110729.LEO
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 305U1A/305U1A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 01PS
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr01PS.M002.20110729.LEO:bd07/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr01PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr01PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 305U1A
dmi.product.version: 01PS
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1069353/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1069353

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[Gerhard Burger (burger.ga)]

apport information

[penalvch (penalvch)]

Gerhard Burger, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelBoot ?

As well, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.7-rc1-quantal

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Gerhard Burger (burger.ga)]

Setting gfxmode to 'text' lets me boot normally, which is an acceptable workaround for me.

However, if I install the mainline 3.7rc2 I get errors about missing firmware for r8169 and radeon. I guess the radeon firmware should be installed, because I get a kernel panic immediately after grub:
early exception 08 rip 246:10 error 810440a6 cr2 0

[penalvch (penalvch)]

Gerhard Burger, thank you providing the requested information. Did this issue not occur in a release prior to Precise?

[Lex Ross (lross)]

This bug struck me when I upgraded to 12.10 using nouveau driver (my graphics card is Nvidia GeForce 7000M / nForce 610M] (rev a2). The system info menu lists the "Driver: unknown" in the "Graphics" section.

[penalvch (penalvch)]

Lex Ross, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may cause your problem to not be addressed as quickly as possible.

Thank you for your understanding.

[Gerhard Burger (burger.ga)]

Cristopher, I just bought the laptop so precise was the only operating system I tried. In the weekend I will check if any of the older kernels on my system give the same problem and can see if 12.10 gives me the same problem.

Or maybe you can point me to some instructions on how to add the missing radeon firmware so I could use kernel 3.7. I'm not afraid to get my hands dirty ;)

[penalvch (penalvch)]

Gerhard Burger, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069353/comments/29 :
>"Cristopher, I just bought the laptop so precise was the only operating system I tried."

Could you please test for this problem in a Lucid live environment via http://releases.ubuntu.com/lucid/ and report back the results?

>"In the weekend I will check if any of the older kernels on my system give the same problem and can see if 12.10 gives me the same problem."

Please do check prior kernels and report back on the results.

>"Or maybe you can point me to some instructions on how to add the missing radeon firmware so I could use kernel 3.7. I'm not afraid to get my hands dirty ;)"

Regarding your mainline test https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069353/comments/25 , what would need to be known is what files specifically did you try to install?

[Gerhard Burger (burger.ga)]

I don't think lucid live has this problem, because I think at shutdown some state of the graphics is stored (see the reproduction steps, after I reset with REISUB, I can boot normally).

But I tested on some previous kernels, and I think the issue is introduced in 3.2.0-31, the kernels before that one (tested on 27,29,30) didn't give any problems. Also the problem is still present in 12.10 ...

To use kernel 3.7 (raring) I installed the following files:
linux-headers-3.7.0-030700rc2_3.7.0-030700rc2.201210220428_all.deb
linux-headers-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210220428_amd64.deb
linux-image-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210220428_amd64.deb
linux-image-extra-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210220428_amd64.deb

To use kernel 3.7 (quantal) I installed the following files:
linux-headers-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210201535_amd64.deb
linux-image-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210201535_amd64.deb
linux-image-extra-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210201535_amd64.deb

both give me the same warning about missing firmware for r8169 and radeon

[penalvch (penalvch)]

Gerhard Burger, thank you for testing Lucid, prior Ubuntu kernels, and the mainline. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069353/comments/31 :
>"I don't think lucid live has this problem, because I think at shutdown some state of the graphics is stored (see the reproduction steps, after I reset with REISUB, I can boot normally)."

Just to clarify, without any WORKAROUNDs, you could not reproduce the problem in the Lucid live environment?

>"But I tested on some previous kernels, and I think the issue is introduced in 3.2.0-31, the kernels before that one (tested on 27,29,30) didn't give any problems. Also the problem is still present in 12.10 ..."

Ok.

>"To use kernel 3.7 (raring) I installed the following files:
linux-headers-3.7.0-030700rc2_3.7.0-030700rc2.201210220428_all.deb
linux-headers-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210220428_amd64.deb
linux-image-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210220428_amd64.deb
linux-image-extra-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210220428_amd64.deb

To use kernel 3.7 (quantal) I installed the following files:
linux-headers-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210201535_amd64.deb
linux-image-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210201535_amd64.deb
linux-image-extra-3.7.0-030700rc2-generic_3.7.0-030700rc2.201210201535_amd64.deb

both give me the same warning about missing firmware for r8169 and radeon"

Hmmmm. Could you please post the install logs for 3.7 (raring) so we may see the errors specifically?

[madbiologist (me-again)]

Gerhard, its interesting that you reported in comment #31 that this does not happen on Ubuntu kernels before 3.2.0-31. According to http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html that kernel was based on the upstream 3.2.28 kernel and according to http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.2.28 not much was changed for radeon in that kernel. To rule out changes made by Ubuntu, could you test the upstream 3.2.27 and 3.2.28 kernels as per https://wiki.ubuntu.com/KernelMainlineBuilds ?

[Gerhard Burger (burger.ga)]

@cristopher see the attached install log

[Gerhard Burger (burger.ga)]

@Cristopher, I tested the lucid live and could not reproduce the problem. But in lucid my resolution was not supported because the E-350 is too new I guess.

@madbiologist, my suspicion is that is a timing issue, which might explain the random occurance. Also if you follow the link in the problem description some people do experience this issue on kernels before 3.2.0-31. I think the workaround using the grub commandline also sort of hints to this...
I'll give the upstream kernels a try.

[Gerhard Burger (burger.ga)]

@madbiologist do you mean this one: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.28-precise/ ?

[madbiologist (me-again)]

@Gerhard - yes, that's one of them.

[Gerhard Burger (burger.ga)]

I tested both 3.2.27 and 3.2.28, and they don't have this problem. Also in the meantime I've updated my system to 3.2.0-33-generic and I don't have the problem anymore! To rule out that other updates caused this, I tried 3.2.0-31 again, it still had the problem.
I guess it is fixed then...

[penalvch (penalvch)]

Gerhard Burger, thank you for noting this issue is resolved in Precise 3.2.0-33-generic. Did you need this resolved for Quantal or may we close this report as Status Invalid?

[Gerhard Burger (burger.ga)]

You can close it as Status Invalid,this is my working machine, so I will probably not upgrade to quantal. Thanks for your help.

[penalvch (penalvch)]

Gerhard Burger, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069353/comments/40 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.