Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

I did md5sum on fs.img for BL3.32 on the computer where BL3.32 and BL3.00 
do a kernel panic (loop version) but BL2 works in RAMdisk and in its own 
linux ext2 partition.  It is the same number as on the other computer from 
which I transferred the zip file, and where it DOES work.  So fs.img 
appears to be okay but BL3 won't boot.  It booted on another computer with 
the same motherboard (a PII Gateway) with a slower cpu (300 vs 233).  I 
will see if it works on another 300MHz computer (Opus PI Socket 7 instead 
of Intel PII Slot1 motherboard).

Do other people have BL3.32 or any BL3 working on a PII?  Slot1 cpu?

Only other odd thing about this computer (which was given to us with no 
known problems), which has Win98 DOS on it, is the Virge video card, which 
two of my DOS viewers (QPV and Display) won't display with.  I did have 
BL3.32 booting on the other Gateway (same DOS) with an STB Lightspeed 
video card (which Xvesa does not like).  So this is probably irrelevant.


And on this computer syschk said there was some sort of memory issue that 
required me to add D=64 to the emm386 line in config.sys, so I may try 
booting without a config.sys next.  But I think the other Gateway had the 
same problem and it DOES boot BL3, in fact I tried BL3.32 first on there 
before these two computers, because it is otherwise just a Win98 computer 
with no linux partitions available.

Bypassing system files (skipping the emm386 stuff) did not help.  Where it 
goes wrong is apparently:

Partition check:
        hda:  hda1 hda2 hda3 hda4
        hdb:  hdb1 hdb2 hdb3
attempt to access beyond end of device.

In BL2 (which I am using at present) it proceeds to VFS:  Mounted root 
(ext2 filesystem) readonly.

Might BL3 work on this computer if I changed rw to ro and added whatever 
else BL2 uses to later make it read-write?  I don't see anything obvious.
> From there it frees unused kernel memory and lods modules.

Maybe there was some good reason we do not know about for the SW7.1 
approach with ro?

On the other computer where it works I also have hdb1 hdb2 hdb3.

What might be letting BL2 boot but stopping BL3?
Some PII hardware bug that was caught by the time of SW7.1?
I might try BL1 as an experiment.  Or BL3 floppy/lilo.
More in an hour after I download that version.


On Tue, 26 Oct 2004, sindi keesan wrote:

> I am unable to get startx to work in BL3.30 so I downloaded 3.32 and tried to 
> do a fresh install on a  Gateway computer PII Intel 233MHz that never had BL3 
> on it (no baslin) in e:\baslin.  I unzipped bl3-32.zip.
>
> hda is 3MB no cache, hdb is 2M 128kB cache, hdc is Atapic CDROM
> One floppy drive found.  I also have an fd1 that I don't see here
> but maybe the CMOS is messed up and it is not listed there.
>
> This motherboard was said to be working fine when given to us.  So far the 
> first drive has been okay (for DOS, and BL2 RAMdisk on D: boots with the
> same boot file except for the loop part).
>
> I typed boot.  This boot.bat looks exactly like one that works with BL3.30 on 
> the other computer here.  I even tried just typing out the line instead of 
> using the boot.bat file.
>
> boot.bat is:
>
> loadlin zimage root=/dev/loop0  initrd=initfs.gz rw
>
> Three times in a row it will not boot. I have two hard drives, DOS on hda. I 
> was going to put BL3 on hdb1 in 200MB partition.  I have BL2 RAMdisk working 
> on D:.  I have BL2 working fine on a linux partition on hdb2. I have BL3.02 
> in D: and renamed that directory back to baslin and it also will not boot, 
> same problem.  What is it about BL3 that is causing the boot problem? Does it 
> not like the hard drive for some reason?  I have another identical 
> motherboard and will see what BL3.02 does there tomorrow.
>
> This is a 300MHz cpu.  BL3 worked with 233MHz on two other computers.
> Should I try the pentium zimage?
>
> Partition check
> hda:  (four partitions)
> hdb:  (three partitions)
> attempt to access beyond end of device
> 07:00:  rw=0, want=2, limit=0
> EXT2-fs:  unable to read superblock
> attempt to access beyond end of device
> 07:00:  rw=0, want=1, limit=0
> dev 07:00 blksize=1024 blocknr=0 sector=0 size=1024 count=1
> FAT bread failed
> Kernle panic:  VGS:  Unable to mount root fs on 07:00
>
> Where did I goof?  Is 07:00 the loop partition?
>
> I was doing this because I CANNOT get startx to work in BL3.30.
> I deleted all but the line
>
> exec icewm
>
> It gets to a screen with X and won't do anything else.  Have to power off and 
> on again, won't reboot, won't switch terminals.  Was the startx/xinit not 
> working in BL3.30?
>
> Startx crashes - X and grey screen.
>
> Xvesa & rxvt works fine.  Default VGA.
>
> I don't know how to get the xmodmap part to work without .xinitrc.
>
> I could try simply
> xinit -- /usr/X11R6/bin/Xvesa &rxvt to see if it works, but startx crashes.
>
> I had hoped to get 3.32 on here instead but want to put it on the other 
> computer first before overwriting 3.30 on this one.
>
> Is there some way to install fs.img to hda1 without first booting BL3?
> I have BL2 on here to work from (to make a loop if needed).
>
> For the 2-floppy version do I really need to make floppy disks or can I 
> install somehow from the download floppy-disk version on hard drive?
>
> Hal says I left out a '-' for cdrecord CLI which is why it made a blank disk.
>
>
> keesan AT sdf.lonestar.org
> SDF Public Access UNIX System - http://sdf.lonestar.org
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org