Results 1 to 6 of 6
Hello,
I am currently using OpenSuse kernel 2.6.18.8 and Dual booting Arch Linux kernel 2.6.22.6 and Fedora 2.6.22.1 - the plan is to move to Arch linux when I get ...
- 09-13-2007 #1Just Joined!
- Join Date
- Nov 2006
- Posts
- 14
Strange boot hang AFTER using kernel 2.6.22...
Hello,
I am currently using OpenSuse kernel 2.6.18.8 and Dual booting Arch Linux kernel 2.6.22.6 and Fedora 2.6.22.1 - the plan is to move to Arch linux when I get it setup, fedora is just for fun.
Opensuse boots fine, Arch boots fine and Fedora boots fine - but after using Arch linux or Fedora, OpenSuse hangs during boot. If I leave it for about 5min it will boot, but the Keyboard and Mouse do not work.
I am forced to hard reset my machine usually the first two boots after using Arch or Fedora (both with the 2.6.22 kernel).
I'm guessing it's a usb problem as both my mouse and keyboard are usb. Any idea how to troubleshoot this? Logs just say "USB disconnect...."
Intel DP35DP board, firmware is up to date (9/1/07). USB mouse and keyboard.
Thanks for any ideas,
nate
- 09-13-2007 #2
Have you enabled Legacy USB Support in BIOS?
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 09-13-2007 #3Just Joined!
- Join Date
- Nov 2006
- Posts
- 14
- 09-13-2007 #4
hmmm... Problem is somewhere else.
Hit Esc key while booting up SuSe. It will turn off splash image. Check where is SuSe taking time.OpenSuse hangs during boot. If I leave it for about 5min it will boot, but the Keyboard and Mouse do not work.It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 09-13-2007 #5Just Joined!
- Join Date
- Nov 2006
- Posts
- 14
I don't like the splash screen so I boot with splash=verbose in my menu.lst, it hangs after:
"usb 1-2: USB disconnect"
Any idea why this only happens after booting a different kernel? It's not just reboots either, happens on cold starts too - but only after using 2.6.22.
Thanks again,
Nate
- 09-13-2007 #6
It could just be a problem with the way the kernel handles your USB device. Other than that, I have no idea. Then again, I suppose I just stated the obvious. :P


Reply With Quote

