Guys, I had a fairly rude surprise when I pulled the testing updates tonight. The install of kernel26-2.6.32-1-x86_64 left my toshiba 205d laptop unbootable. The boot process would start as usual but then get to a point just after it had started X and lock. There was no way to ctrl+f1 to break out of X and the only solution was to reboot. I booted to the install cd, and chrooted everything in /mnt/arch and downgraded the kernel to kernel26-2.6.31.6-1 (along with madwifi) and now everything is back to normal. I have looked throught the logs, but I don't know where the useful information would be captured. I think the failed boot sequences (I tried twice) are shown in these snippets: kernel.log: Dec 6 20:55:46 alchemy kernel: Unpin not necessary for ffff88011dd6fe00 ! Dec 6 20:55:46 alchemy kernel: i2c-adapter i2c-1: unable to read EDID block. Dec 6 20:55:46 alchemy kernel: radeon 0000:01:05.0: LVDS-1: no EDID data Dec 6 20:55:46 alchemy kernel: i2c-adapter i2c-1: unable to read EDID block. Dec 6 20:55:46 alchemy kernel: radeon 0000:01:05.0: LVDS-1: no EDID data Dec 6 20:55:54 alchemy kernel: Unpin not necessary for ffff8800ba072800 ! Dec 6 20:55:56 alchemy kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Dec 6 20:55:56 alchemy kernel: wlan0: deauthenticating by local choice (reason=3) Dec 6 20:55:56 alchemy kernel: wlan0: deauthenticating by local choice (reason=3) I don't even know if the failed boot attempts made it to the point that logging was turned on. Anyway, you guys let me know what you want to see or what you want me to test and I'll get it for you FAST. I can't have my Arch install down. I can live without suse, but not Arch ;-) -- 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
