Date: Sat, 06 Nov 2004 18:45:25 -0800
From: Mark Srebnik <[EMAIL PROTECTED]>
Subject: Re: [LIB] Linux on 110CT Install from HD - Update
(resending as this didn't seem to get to list...)
Thanks for your help Philip!
Also, want to thank Gokhan who sent me emails offlist and attached files for
me to try out...
See my comments below yours...but make sure you read the news at the bottom
of this post... ;-)
Mark
on 11/1/04 7:34 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
> Date: Sat, 30 Oct 2004 15:29:58 +0200 (MEST)
> From: [EMAIL PROTECTED]
> Subject: Re: [LIB] Linux on 110CT Install from HD - Update
>
>> Date: Fri, 29 Oct 2004 21:22:37 -0700
>> From: Mark Srebnik <[EMAIL PROTECTED]>
>> Subject: Linux on 110CT Install from HD - Update
> ...<snip>
>> message ( Kernel Panic: VFS: unable to mount rootfs on 01:00 ) I managed
>> to get past that finally and install process started. However, after a
>> while display went black and didn't seem like anything was happening...so
>> after some time past I shutdown and restarted....
>>
>> Sometimes, got to point where it asks you to select where to start
>> install from, selected CD-ROM. CD drive would start up and make whirring
>> noises, but after a minute it would shut down and nothing would happen...
>
> I have similar experiences. Sometimes it worked, sometimes not.... and I have
> no clue at all why.
> But I have several times suggested to press <Alt>-F1, <Alt>-F2, <Alt>-F3 or
> <Alt>-F4 to see how far the install kernel got. You never reported on this....
The problem I've had with using the <Alt>-F1, <Alt>-F2, <Alt>-F3 or <Alt>-F4
idea is that when I wanted to check on what's going on with install is when
I think something's not working right.
Unfortunately, that is usually the situation...then this technique doesn't
work as the Libretto has frozen up due to kernel panic or something....
In other words, this works well it seems when the install is working OK, but
not when the install is not going OK, which is when you want the report....
Hope this makes sense.... ;-)
However, if there's a way to make this work better, please let me know...
> ...<snip>
>> loadlin bzimage root=/dev/ram initrd=pcmcia.dsk rw
>
> This is wrong. pcmcia.dsk is a floppy disk image, not a RAM disk image.
I had a feeling this was not good... ;-)
>> Second approach, per Slackware install instructions:
>> Loadlin bzimage rw root=/dev/ram initrd=initrd.img load_ramdisk=1
>
> That looks better.
That's what I thought...
>> Linux starts loading and then with either approach, I get the following
>> error message:
>>
>> FAT: bogus logical sector size 5345
>
> It sounds like the FAT (=Windows) partition you are installing from has some
> problems. Have you ever run scandisk? The scan-/chkdsk version from Win2K is
> much more rigorous BTW. Are there no bad sectors on your HD?
Well, didn't report on this, but I swapped out hard drive recently just
before recent post...put new 60GB drive in. Reinstalled WinXP Pro
fresh...then tried Linux...
But I can run scandisk...and see if there's any problems...
> It may also be that the MBR has irreconcilable entries. The info on each
> partition is always double, once in CHS and once in absolute sectors.
> Ofcourse Windows uses one of these, the rest of the world the other, and that
> is where problems may start.
> These problems may well be the cause of failure of all your Linux install
> attempts.
> But read on......
Yipes.....
>> UMSDOS: msdos_read_super failed, mount aborted
>> sh-2021: reiserfs_read_super: can not find reiserfs on ramdisk(1,0)
>> Kernel Panic: VFS: unable to mount rootfs on 01:00
>>
>>
>> UPDATE: Gokhan was kind enough to check his files and send me his
>> Slackware3.1 install files. This worked up to point where it asks you
>> partition hard drive. Had problems with version of fdisk. Something not
>> right about it....
>
> Try to dump fdisk and use cfdisk. Various Linux docs about fdisk point out
> that it has many flaws. I don't remember the details, but it mentioned
> somewhere that "luckily, fdisk will usually (but not always) come up with the
> right info" or words like that (in man fdisk IIRC).
I can try this...
> But as you made so many "proper" attempts already, I am suspicious that
> something in your Libretto is flakey. Windows is not too critical especially
> about disk geometry, so that's wher I would look first.
So you think it's hard drive related??? Even though I just put in brand new
drive last week???
> BTW my apologies if I am wrong, aren't you the one who a while ago complained
> that when booting from floppy the HD couldn't be seen, and it turned out you
> had a disk manager on your HD? (...I am away from home currently so can't
> check the archives)
Yes, that was me....good memory Philip...
> If that were true, it would explain a bit..... Recent
> Linux kernels & install kernels should be able to recognize disk managers, but
> certainly not all of them, and may be upset or even break up if these disk
> managers mislead them.
> That is just one of the many reasons I try to avoid disk managers like EZ or
> Ontrack or MaxBlast at all costs.....
However, with new hard drive, I decided NOT to use a disk manager....just
formatted drive with first partition just under 8GB...
>> Soooo,... if anyone can provide any input or suggestions that would be
>> greatly appreciated!!
>
> All I can offer at the moment is right above.
As always every bit of help and insight is greatly appreciated!
>> I have spent hours and hours trying to get Linux installed and going
>> crazy...
>
> Probably of little comfort, but I do know the feeling......
>
> Good luck,
>
> Philip
Again, everyone's help is greatly comforting in the midst of so much
aggravation and failed attempts...the kind help from everyone in this group
is part of what keeps me going in my persistence to overcome this 'series of
disasters'.... ;-)
Well, the GOOD NEWS for a change is:
A) Got Linux working today!!
First tried ZipSlack...linux part worked but couldn't get 'X' working...
Then found out about AmigoLinux and BINGO!!
Worked great first time...running now on my ol' Libby!!!
Basic install allows you to run it off of Windows 'C' drive....then you
can move it if you want to a separate Linux partition....will try that
in a while...
B) In the interim, I tried and successfully installed PearPC/OSX 10.1.4 on
my ol' Libby!!!
Pretty cool to see OSX on it, but it runs like molasses... ;-)
Really need a fast CPU like a P4 to get good performance, but a great
conversation piece nonetheless.
So things are looking up a bit right now....;-)
Now if I just had a $ for every hour I've spent getting to this point, I'd
be all set... ;-)
Thanks,
Mark
Not-So-Frustrated Silicone Valley Libretterati