[Bug 36998] Re: Kernel Won't Boot on an IBM Thinkpad R30
schnirfl
jochen.gruse at web.de
Fri Apr 27 08:55:44 UTC 2007
Updating the BIOS to 1.40 went flawless, if a little bit convoluted. As
the R30 has no floppy drive and is not running Windows, no IBM-supported
update path exists. ThinkWiki has a valuable page:
"http://thinkwiki.org/wiki/BIOS_Upgrade#Updating_via_CD.2FDVD_Drive".
In a nutshell, you have to download the program to create a boot floppy
and run it on a windows machine with a floppy drive. Then boot linux on
that machine (KNOPPIX comes to mind...) and create an image of that
floppy. At last you can create and burn a CD image that boots the floppy
image. I can mail the CD image to you if you're interested.
As I said, latest version is 1.40 (Aug. 2006). If you want to check
your BIOS' version, do a "sudo dmidecode | less". You'll find a
"Version:" tag in the BIOS Information stanza, which is probably the
first.
Success re resume after suspend to disk has been mixed. At first sight,
nothing seemed to have changed - screen goes out, laptop freezes. But
accidentally leaving the laptop in this state for a while showed some
disk activity! After a reboot my debugging output lists the first two
resume scripts as having been called... So, my next actions will be
* Try SysRq. I previously thought that my machine didn't react to Alt-SysRq combos, but checking while running normally revealed that I have to use the *right* Alt-key (which is in fact labeled as "AltGr" on my german keyboard).
* Check and maybe change the DSDT (again). The new BIOS revision might have changed something.
* Weed out all unneeded resume.d scripts. Maybe there's one which leads to this bug...?
I'll let you know if I discover anything interesting.
OT: Slow installation is probably not a result of not enough RAM but of
a slow hard disk. Running on 512MB here did'nt make the installation
(update actually) go any faster.
Cheers,
schnirfl
--
Kernel Won't Boot on an IBM Thinkpad R30
https://bugs.launchpad.net/bugs/36998
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.
More information about the kernel-bugs
mailing list