You are not logged in.
I've had this problem for a while, but it hasn't really bothered me enough to fix it. Now it's just sort of built up and I want to try to find a solution.
I have a Toshiba Satellite A200-28P. When plugged in to the mains with no battery in, it works perfectly well. I can also put the battery in after Arch has booted, and it works perfectly. However, if the battery is in the laptop when Arch boots, X locks up completely when it starts, and the only solution is a hard reset (SysRq does nothing). But if I boot into fallback mode (ie: no X), it works perfectly, assuming I don't try to start X.
Last edited by Barrucadu (2009-01-23 21:04:53)
Offline
I would think that in fall back mode there is some module that is loaded that is not in your regular mode.
Check what you have in your fall back and one-by-one add the modules until it boots OK in your regular kernel and you should have your unit working fine in both normal and fall back.
Hope this helps.
R
Offline
No, it's not that. the problem occurs in the fallback mode if I start X - I just don't start X in the fallback mode by default. Sorry if i didn't make that clear enough.
Offline
Regardless, the principle applies.
In fall back mode a bunch of drivers is loaded, even if you do not use them, because the idea is that all possible scenarios to boot the system are covered.
Some driver is loaded in fall back mode that makes X freeze. Look at what's loaded there, then use "modprobe" to load the different drivers one at a time until it freezes and you found what causes the problem.
R.
Last edited by ralvez (2009-01-23 00:37:54)
Offline
The problem has miraculously fixed itself after the upgrade to kernel 2.6.28.1-1. Hooray!
Offline