Ubuntu
linux package

  1. Bug #1029790
  2. Comment #22

Comment 22 for bug 1029790

Revision history for this message
penalvch (penalvch) wrote : Re: Can't boot without nomodeset option-kernel 3.5.X.X/3.6.X.X ATI M52 [Mobility Radeon X1300]

Paul, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029790/comments/21 :
>"Thanks for pointing out this policy. I did however want to share my workaround with people who might find this bug. And surely you'll agree that having one's bug report marked as a duplicate feels like it is being thrown away, it's not a good feeling for the reporter;"

I do not agree. How one feels about a Ubuntu developer/triager marking their bug a duplicate is not a reason to not file a new report. The purpose of filing a new report is not to make you feel bad if it's marked a duplicate of another, but so a Ubuntu developer/triager may analyze the debugging attachments and make the determination if it is in fact a duplicate or not. By not filing a new report, you are preventing Ubuntu developers/triagers from analyzing your hardware.

>"and in this case it is clear that we're dealing with a duplicate."

It is not clear in this case we are dealing with a duplicate. Please see above and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029790/comments/20 .

>"By the way, I performed the bisection, using quantal kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/
3.4.17 (2012-10-31) works, as reported earlier, while 3.5.0-rc1 (2012-06-03) crashes (screen and keyboard frozen, no log files left). Further bisection would require delving into the git history. Newer kernels are also affected, right up to the latest 3.7.0-rc4 (2012-11-04). So the signs point to a problem upstream.
Red Hat users have hit the same issue, and have got further than we in debugging. Timothy Davis narrowed the problem down to changes made in radeon_kms.c between 3.4 and 3.5. Again, we need to send this upstream.
 https://bugzilla.redhat.com/show_bug.cgi?id=845745"

While it is appreciated you took the time to investigate this on your hardware, it would be demonstrably more helpful if you filed a new report, as already requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029790/comments/20 .

Thank you for your understanding.