1.8b Development

I updated my net6501-30 to the latest 1.41 BIOS and can finally boot m0n0wall from a USB stick.
1.33 booted fine and gave me the configuration to start with, the generic-pc-serial-1.8.0b477 boots fine, but runs into a message saying it can't find the config file on the device, and therefore will not continue booting.

The following is the error with part before and part after.

SMP: AP CPU #1 Launched!
Root mount waiting for: usbus7 usbus6 usbus3
uhub6: 1 port with 1 removable, self powered
uhub3: 3 ports with 3 removable, self powered
uhub7: 3 ports with 3 removable, self powered
Root mount waiting for: usbus7
ugen7.2: <Generic> at usbus7
umass0: <Generic USB2.0-CRW, class 0/0, rev 2.00/19.81, addr 2> on usbus7
Trying to mount root from ufs:/dev/md0
kern.coredump: 1 -> 0
net.enc.in.ipsec_filter_mask: 0x00000001 -> 0x00000002


*******************************************************************************
* FATAL ERROR                                                                 *
* The device that contains the configuration file (config.xml) could not be   *
* found. m0n0wall cannot continue booting.                                    *
*******************************************************************************

(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to rea
dy change, medium may have changed)
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: <Generic- SD/MMC 1.00> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 3837MB (7858176 512 byte sectors: 255H 63S/T 489C)
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
W
Syncing disks, vnodes remaining...0 aiting (max 60 seconds) for system process `
syncer' to stop...0 done
All buffers synced.
Uptime: 13s

The operating system has halted.
Please press any key to reboot.

Seems kind of odd to me. Shouldn't it show me the config to actually build the config.xml?

Going to try the upgrade through 1.33 now, which I did before on the old board with a CF card.
So I know that should work.

Nevermind, the 1.33 can't do anything with the NICs at all. Missing drivers I presume.

Looks like that board uses Intel 82574IT ethernet ports. And on FreeBSD 7.x they are supported and use the em driver. Apparently not supported on FreeBSD 6.4 that m0n0wall 1.33 is built on though.

It may be possible to compile the available source code for the driver on FreeBSD 6.4 and then modify a copy of the m0n0wall 1.33 image with the new driver. I am willing to give this a try for you but I have to download a copy of 6.4 and install it first. I'll let you know how this turns out.

m0n0wall generic-pc-serial-1.8.0b477 is built on FreeBSD 8.x so they ethernet would almost certainly work if you weren't having problems getting it fully loaded.

If it's any consolation, none of the m0n0wall 1.8 betas work on my hardware yet.

I'd like that. I don't have any BSD boxes here, except Mac OS.

The console shows all four em NIC's are loaded and functional.
But something seems to go wrong for usbus7, since it's waiting for it to be able to mount root on it. Which then would explain why it cannot find the config.xml.

Well, I don't go to the trouble of setting up a box from scratch when I need to do something like this, I just load the target OS into a VM running on what I do have on hand.

I am getting the 6.4 iso now, but it's a slow go. wget says 12 more hours, but that will come down when my other download finishes. Getting it from Finland isn't helping any.

I'll let you know what happens, but I can't actually test anything I come up with, I don't have any of those Intel 82574ITs here.

Testing I can do of course. Easily done.

Solved with the update to 1.8.0b478. Thanks Manuel!

Thanks indeed, and to Fred for the help as well.