1.0.4 and 1.0.7 have both been working fine on this IBM Thinkpad 600x.
I upgraded the memory and now 1.0.4 boots from the HDD fine but 1.0.7 from the CD triggers a Kernel Panic.
It seems to happen when mounting /usr_cram.fs file on /usr ...
"Unable to handle kernel paging request at virtual address 2d747465"
followed by a bunch of stuff then ...
"Code: 8b 02 85 c0 74 06 8b 02 a8 02 74 06 81 c1 00 08 00 00 8b 52
<0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - no syncing"
Help, please? doc
Upgraded memory on IBM Thinkpad 600x, now get kernel panic.
Upgraded memory on IBM Thinkpad 600x, now get kernel panic.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
I had the same problem with several Linux distributions on my TP600E and TP770. Seems like some kernels do not reconginze the correct amount of usable RAM on these Thinkpads. The last few megabytes (~2MB) are not usable by the os, cause the Thinkpad uses them in some way.(power management or BIOS stuff?)
My TP770 had 128MB RAM and i got kernel panics.
I fixed this by passig "mem=124M" to the kernel at boot prompt.
Maybe this works for you.
My TP770 had 128MB RAM and i got kernel panics.
I fixed this by passig "mem=124M" to the kernel at boot prompt.
Maybe this works for you.
You are presuming I am smarter than I am!miq wrote:I had the same problem with several Linux distributions on my TP600E and TP770. Seems like some kernels do not reconginze the correct amount of usable RAM on these Thinkpads. The last few megabytes (~2MB) are not usable by the os, cause the Thinkpad uses them in some way.(power management or BIOS stuff?)
My TP770 had 128MB RAM and i got kernel panics.
I fixed this by passig "mem=124M" to the kernel at boot prompt.
Maybe this works for you.
Would I pass such a command within Grub or how, please?
I am running 1.0.7 on the 600x.
Thanks! doc
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
I'm new to puppylinux so I had to figure this out first:
when booting from CD, you get a boot: prompt.
If you have 128MB try this:
boot: vmlinuz root=/dev/ram0 initrd=image.gz PFILE=pup001-none-26144 mem=120M
In case you have 96MB try mem=88M, with 64MB try mem=56M .
I've tried this with puppy 1.07 live cd, and it worked fine.
If you can boot up (without kernel panic), you can try to increase the mem -value in 1MB steps.
when booting from CD, you get a boot: prompt.
If you have 128MB try this:
boot: vmlinuz root=/dev/ram0 initrd=image.gz PFILE=pup001-none-26144 mem=120M
In case you have 96MB try mem=88M, with 64MB try mem=56M .
I've tried this with puppy 1.07 live cd, and it worked fine.
If you can boot up (without kernel panic), you can try to increase the mem -value in 1MB steps.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
There's an easier way to add boot options to the liveCD than miq has suggested; at the boot prompt enter the number (1-5) of your boot-choice, then type a space, then each additional boot option separated by a space. Example -
boot: 1 mem=124M
If using grub, open /boot/grub/menu.lst in a text editor and add your boot option(s) to the "kernel" line.
boot: 1 mem=124M
If using grub, open /boot/grub/menu.lst in a text editor and add your boot option(s) to the "kernel" line.