Slackware bootdisk boots but Linux bootdisk won't!

Slackware bootdisk boots but Linux bootdisk won't!

Post by ASCII of Ameri » Thu, 27 Oct 1994 05:12:07



Please Help!  Here's my story:

I have a P-90 with a Mitsumi CD-ROM.
My hard disk has 1046 cylinders, 16 heads, and 63 sectors.

I made a boot disk from the "mitsumi.gz" file in the slackware2.0.0
"bootdsk1" directory.  I gave it the following information:

boot: ramdisk hd=1046,16,63

It boots fine.  I was able to partition and format my disk, and the
install process for each of the disk sets appeared to go smoothly.

I installed the Linux kernel 1.1.18 with SCSI+IDE+UNIFIX+MITSUMI CD.

I created a boot disk, copying vmlinuz to the boot disk.  I was not asked
to provide any "ramdisk hd..." information when I did this.

I created a Lilo (on floppy) that only boots Linux, from partition /hd3.
I indicated the "ramdisk hd=1046,16,63" command.

I tried to boot from the Lilo floppy, only to get the following output:

L04040404040404040404040404040404040
040404040404040404040404040404040404
040404040404040404040404040404040404
040404040404040404040404040404040404
040404040404040404040404040404040404
.....
and so on forever.

When I try to boot from the Linux boot floppy that I created during
the setup process, I got a lot of errors that I could not follow
as they scrolled across my screen.  The last screenfull of errors
said the following:

--------------------------------------------------------------------------------
MSDOS bread failed
isofs_read_super: bread failed, dev 0x303 iso_blknum 16
Weird - unlocked, clean and not uptodate buffer on list 0 303 1
Weird - unlocked, clean and not uptodate buffer on list 0 303 0
Weird - unlocked, clean and not uptodate buffer on list 0 303 32
Weird - unlocked, clean and not uptodate buffer on list 0 303 1
Weird - unlocked, clean and not uptodate buffer on list 0 303 0
Weird - unlocked, clean and not uptodate buffer on list 0 303 32
harddisk I/O error
dev 0303, sector 0
HPFS: map sector: read error
Unable to handle kernel NULL pointer dereference at kernel address 00000000
...
--------------------------------------------------------------------------------

And then a bunch of eight digit variable values that appear to be debugging
information.

WHY DOES MY MITSUMI BOOT DISK WORK, BUT NOT THE INSALLED KERNEL?

Is it because the installed kernel does not know the cylinder/head/sector
information for my hard-disk?  How can I tell it this information?

Thanks for your help!
Ooooh, this is soooooo frustrating!

Dave

 
 
 

Slackware bootdisk boots but Linux bootdisk won't!

Post by Tom Griffi » Sat, 29 Oct 1994 12:18:08




Quote:>Please Help!  Here's my story:

>I have a P-90 with a Mitsumi CD-ROM.
>My hard disk has 1046 cylinders, 16 heads, and 63 sectors.

                  ^^^^
I have found that LILO won't install the boot information
correctly on a partition with any cylinders greater than
1023.  I will continue booting from a boot floppy until
LILO gets fixed or until I re-partition my disk and reload.
(I know it's not an elegant solution, but it works.)

Quote:>I created a boot disk, copying vmlinuz to the boot disk.  I was not asked
>to provide any "ramdisk hd..." information when I did this.

What command did you use to make it?  I use:

    $ dd if=/vmlinuz of=/dev/fd0 bs=18k
    $ rdev -R /dev/fd0 1

Quote:>Is it because the installed kernel does not know the cylinder/head/sector
>information for my hard-disk?  How can I tell it this information?

>Thanks for your help!
>Ooooh, this is soooooo frustrating!

Not sure I helped much, but I hope it helps,

--
        _______________________________________________________________________
       /                         /                                            /
      /   Thomas L. Griffing    /   To invent, you need a good imagination   /


 
 
 

1. Bootdisk won't boot:Slackware 3.1.0

I am trying to load Slackware 3.1.0
I made a copy of the 1.2 boot and root disks using rawrite.exe as per
instuctions. When I load the bootdisk, I get "No Basic in ROM" error.
I then tried the 1.2 bootdisk from Slackware 3.0 and it boots okay,then I
load the rootdisk from 3.1.0 and it loads fine.But when I try to run
setup,I get a segmentation fault.I can see where it may not like the two
versions mixed among the bootdisk and the rootdisk,but why didn't the
original 3.1.0 bootdisk load?
Any help would be much appreciated.
Thanks in advance...

2. new disk wont boot

3. My Bootdisk won't boot; can't load /libc.so.4 ???

4. Linux Automounter

5. Redhat bootdisk won't boot?!

6. LINUX boot disk SCSI ?

7. Help: bootdisk won't boot machine

8. OS support for SMP- basic question

9. HELP! Can't load Slackware bootdisks

10. Can't make Slackware bootdisks

11. HELP! Can't load Slackware bootdisks

12. Can't make Slackware bootdisk with newer kernels

13. Slackware '96 stock bootdisks lock at "LI"...