Install problemsForum: HD Install Topic: Install problems started by: morpheus Posted by morpheus on Jan. 22 2007,13:32
Hello, I'm new to DSL, and only been using Linux for a few months. I have an older PC I dug out from under the stairs and I'm trying to resesitate it before sending it to the computer graveyard. The hardware consist of a 150mhz Pentium, 32mb of ram, and currently a 500mb hd, although I've also tried using a 2gig hd and obtained the same results. Because the hardware is older, I'm using the syslinux install. The problem, I'm receiving an error stating Init: Panic: segmentation violation at 0x804e19a! sleeping for 30 seconds. I've tried using different options when booting, dsl 2 base mem=32 failsafe etc, all to an avail. Although the hardware is older, according to the DSL web site, I meet the minimum requirements. Thank you in advance for your help! Posted by ^thehatsrule^ on Jan. 22 2007,14:20
Is your cd media burnt correctly? (I'm assuming you meant the syslinux cd image)Did you also try the super lowram method described in the wiki? Also, the mem=32 should be mem=32M Are there any errors before the panic? Posted by skaos on Jan. 22 2007,15:26
0x804e19a (hexadecimal) = 134537626 (decimal)It looks like DSL tries to access some memory around 134 MB - which you don't have. Try thehatsrule's suggestion. If it still doesn't work, try < http://www.toms.net/rb/ > and see if that boots. If it doesn't, some of your hardware may be too special. Posted by morpheus on Jan. 22 2007,15:56
The CD media is burt correctly, I checked it with md5sum. I'm using the syslinux cd image when I receive the INIT Panic errors.I've tried the "lowram" option during boot, and this did not work either. Sorry about the typo with mem=32; I did use mem=32M when I tried the option at boot time - didn't work. Using the current.iso and and a boot disk(floppy), I am able to get to a prompt root@tty1[dsl]# after hitting ctrl c to stop the following loop.
I do receive a lot of other errors before getting to the loop in above code, but the errors scroll by so fast I cannot see them all. Here are a couple of the errors I was able to see:
Being a newbie, I'm not sure what all this means, but I hope the information provided allows us to get DSL to run on this PC. Just a thought, is it possible to install from the command line, now that I'm here? Posted by ^thehatsrule^ on Jan. 22 2007,16:20
If you can get to the cmd prompt, you can try running 'dmesg' for the log.Sorry, I meant the 'super' failsafe method described in the wiki. Posted by morpheus on Jan. 22 2007,17:47
UPDATE-------- I've used the super low memory options described in the Wiki and I'm now able to boot to a command line with the prompt being root@tty1[/]# (This is using a boot disk with the current.iso) I think this is good, but I'm not sure what I need to do at this point to install to the HD. Any directions on how to install to the HD from the command prompt are much appreciated. If it would help to see the error log that's created at boot up, I'd be happy to paste it to a web site if I knew how to write the log to a floppy. Posted by roberts on Jan. 22 2007,17:52
from command prompt# dslinstall But with all of your cloop read errors, I suspect that either the cd is not good or the cdrom reader is not good. Posted by ^thehatsrule^ on Jan. 22 2007,19:31
mount your floppy first,mount /mnt/xxx dmesg > /mnt/xxx/dmesg.log where xxx is your floppy drive Posted by Carl1957 on Jan. 24 2007,23:20
I've seen the same messages trying to install - turned out it was a small imperfection in the media and/or a dirty cd drive lens.Cleaned the lens and did a fresh burn on a new cd and it went away.... Dsl Does work well on lowram systems but swap is mandatory! My laptop has no floppy and no cd, pulled the HD and used an adapter to mount it as hd1 on my desktop and made a frugal install. Put the HD back in the laptop and my Compaq 4131T w/ 32m ram works fine. BTW USR 2410 wireless card was recognized and works w/no fiddling..... Almost forgot: I'm using DSL3.2 if that makes a dif.... Posted by morpheus on Jan. 25 2007,02:32
Thank you for your response. I think the cd itself is good because I was able to run DSL on another (newer) computer with no problem. As you stated, the lens on the CD ROM may need to be cleaned. I'm curious to know if you are using the .iso or the syslinux version of 3.2. According to what I've read, the syslinux version is suppose to work better with older hardware, but I'm finding I can at least get to a command prompt with the .iso and a boot disk. Posted by morpheus on Jan. 25 2007,16:57
I've posted the error message on another forum < http://www.frihost.com/forums/vt-64372.html#540793 >Please check it out; any help on interpreting what the error message is saying, and how to fix it, is much appreciated. I tried cleaning the CD ROM last night with a compact disc laser lens cleaner. The media (CD) I believe is good because it boots fine in my newer computer. One final thing I should add, I tried using a newer CD ROM I have, but could not get the computer to boot from the CD ROM. I tried booting directly from the CD ROM, and also tried booting from a floppy first, then reading the CD ROM, both ways failed. I think the newer CD ROM I used may be faulty. Posted by roberts on Jan. 26 2007,00:22
I still maintain a read errors indicates faulty media or hardware.Could be your cdrom reader is out of alignment or mis-aligned as to the cdrom burner. Posted by morpheus on Jan. 26 2007,12:57
Would there be any reason why I have more progress with the .iso vs the syslinux? From my understanding, the syslinux is suppose to work better with older hardware, but this does not seem to be the case. I think at this point I'm going to re-burn the CD at 4x and see what happens.
Posted by ^thehatsrule^ on Jan. 26 2007,13:59
I think you meant isolinux vs syslinux (.iso is just a filename extension for the standard disc image format)They are just different bootloaders, so I am leaning towards bad media (since it looks like you were already past the bootloader) |