> but it also happens when the m0n0wall drive is the only one on the bus
Do you mean one disk on the primary channel and one on the secondary? I
still had the problem with that configuration not just when both disks
shared the same IDE channel. I gave up in the end.
From: Chris Craft [mailto:ccraft at netgenius dot org]
Sent: 21 November 2003 16:38
To: Frans King
Subject: Re: [m0n0wall] Trouble installing to harddisk
That would make sense if it only happened with both drives plugged in,
but it also happens when the m0n0wall drive is the only one on the bus.
Frans King wrote:
> I had a similar problem. Basically it sounds like you have two MBRs -
> one for linux and one for m0n0wall. Some BIOS's don't seem to like it.
> -----Original Message-----
> From: Chris Craft [mailto:ccraft at netgenius dot org]
> Sent: 21 November 2003 00:06
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] Trouble installing to harddisk
> Hello folks.
> First of all, THANKS to all the developers for their efforts on this
> software gem!
> I have tried the procedure to install generic-pc-pb19r536.img to a
> drive on a machine that boots from the CDROM version just fine. (The
> reason why I'm doing this is because the @#!!$ floppy drive is now
> toast, and I like the reliability of hard drives better.) It didn't
> work. After writing the uncompressed image to the drive (gunzip -c g*
> dd of=/dev/hdc), and swapped that drive in as /dev/hda... caused the
> bios to hang. Plugged the linux drive back in as hda, plugged my
> m0n0wall drive in as hdc, and it still hung the bios. Unplugged the
> m0n0wall drive, and the linux drive booted fine. Pulled a nasty trick
> (kids, don't do this at home!) by plugging the ide cable in to the
> m0n0wall drive after BIOS-POST, and zeroed the boot sector of it after
> linux had come up. This allowed the machine to boot normally, but, of
> course, no m0n0wall. :( I'm extremely impressed by m0n0wall's ease of
> use and flexibility, but stymied by this unexpected behaviour. Any
> hints, anyone?