Gotcha, it is amd64, so I will look at that and report back.
Next plan9.ini's "rootdir". It is no longer documented in
plan9.ini(8), but the little code that uses it in bootrc is odd as
well as at odds with the legacy documentation. My hope was to give it
"9front" as a value and have Fossil serve that as the root for a
diskless 9front workstation, as in
bind -b $rootdir /
Instead, I find "mount -c /srv/boot $rootdir" which is definitely not
it. I'm not sure under what circumstances one target a different
location for the ROOT directory, I would be interested to hear. Of
course, this conflict needs to be resolved.
This is starting to get interesting.
Lucio.
PS: Thanks a bunch for the support, both you and Hiro.
On 5/5/19, cinap_len...@felloff.net <cinap_len...@felloff.net> wrote:
>> It's the 3Com that baffles me. I suspect the two-stage boot (I know
>> dangerously little about 9front's boot process) somehow fails to pick
>> up a supported device (3c905b - etherelink3).
>
> is this the amd64 kernel or 386 one? the amd64 one does not include
> the etherelnk3 driver. the reason is that the amd64 kernel shares its
> drivers with the pc kernel, but not all drivers might be ready for
> 64 bit pointers. so we only include what we can test and verify.
>
> you can try to add the etherelnk3 line to the pc64 config and
> rebuild.
>
> if you have this issue with the 386 kernel, then knowing the pci
> device id would be a start.
>
> the boot process is nothing special. we have a bootloader that loads
> the kernel. the loader uses BIOS/EFI calls to get the kernel from the
> boot media so that it does not need drivers. once the kernel
> is taking over, it needs a driver.
>
> --
> cinap
>
>
--
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa
Ph.: +27 58 653 1433
Cell: +27 83 251 5824
FAX: +27 58 653 1435
