On 08/03/2010 11:49 PM, Andreas Radke wrote:
Bug reopened. You didn't gave an answer for some days. Please make sure to divide it into either KMS/module loading is broken or your Compiz is fucked up. As written in the bugreport I had to manually put all needed graphics related modules into the rc.conf file. Now it boots almost every time for me. You can boot with "debug" command in the kernel append line to get more feedback when modules get loaded.
I apologize for not getting back sooner, but at times my real life calls and I have to push linux to the side for a week or two. I'll have a bit of time this week and next to help as much as I can. What I really need is a list of what I can get off my box to help track this down. Heck, I don't even mind configuring the router to get the smart folks in and giving an account if that would help.
Since this bug occurs before logging is available, that makes it doubly-hard for me to know where to even begin with this one. I've already run tests with both configurations of KMS early/late and posted the results to the bug report, but what more I need to do is where I'm drawing a blank. I'll start with "debug" appended to the kernel line and post the results back at the bug report. We'll go from there.
The big issue/mystery is why in the heck the box hardlocks on boot starting with the 2nd boot after initramfs is compiled. At least I know that is the issue that needs to be addressed first to find out where the bug is. I'm a great set of hands at the keyboard -- it's knowing what to type that's the problem :p
Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
