Re: mformat, boot disks
>>>>> "R1nso" == R1nso <R1nso13@aol.com> writes:
R1nso> the disk created with mkboot does work to boot the system.
R1nso> however, i have made boot disks using basically the method you
R1nso> described (dd and rdev) and they don't work. the only
R1nso> difference between the two methods is that i used dd with a
R1nso> blocksize of 8192 (bs=8192) and then checked to make sure it
The blocksize should not matter.
R1nso> was set to the first partition on the hard disk (rdev /dev/fd0
R1nso> << /dev/hda1), and it was correct, so i didn't need to set it
R1nso> again, right? perhaps i should have mentioned that after
R1nso> printing several dots following 'loading' it began to rapidly
R1nso> print "200" then on a new line "AX:<some numbers> " new line
R1nso> "BX:<some numbers>" and so on until 'DX' another thing I
That looks like a kernel panic: something has made the kernel crash.
Very strange. The same kernel works when booted by LILO. I looked at
mkboot and it doesn't add any flags besides the root device.
R1nso> recently discovered is that there is a file called "vmlinuz" in
R1nso> the root '/' directory. i have also tried dd - ing it to fd0,
R1nso> checking it w/ rdev but only to produce the same results. Which
R1nso> file should i use, and how can i make it work?
/vmlinuz is actually a link to /boot/vmlinuz-x.x.x, so either one
should work. (Do `ls -l /' to see for yourself.)
As far as I can see, you did everything correct. There are two other
options I can think of:
- your floppy drive is defective/strange. LILO manages to work around
the problem, but the loader built into the kernel doesn't.
- the floppy this you used for the raw kernel image is defective. Try
a different one.
--
G. ``Iggy'' Geens - ICQ: #64109250
Home: <ggeens@iname.com> - Work: <guy.geens@cgey.be>
WWW: http://users.pandora.be/guy.geens/
`I want quality, not quantity. But I want lots of it!'
Reply to: