HFS+ & Networking

[Samuel Rydh]

On Mon, Mar 24, 2003 at 09:26:11PM -0600, Eric Volker wrote:
> Well, I did a little RTFMing and got MOL compiled.  I've got it running, 
> and can actually boot OS X.2.4 and MacOS 9.2.2! However, I'm running 
> into several quirks and/or bugs. When I boot OS X off an HFS+ volume, it 
> boots just fine. However, when I include an HFS+ volume in molrc.macos 
> and try to boot from MacOS 9 I get the following:
> 
> >> =============================================================
> >> Mac-on-Linux OpenFirmware 0.9.12
> >> ea_to_phys: no translation for 0000002a, using 1-1
> >> ea_to_phys: no translation for fffffffc, using 1-1
> >> ea_to_phys: no translation for 6000000c, using 1-1
> Unmapped 'RAM-read-access', 6000000c
> >> ea_to_phys: no translation for 12d9008c, using 1-1
> Unmapped 'RAM-read-access', 12d90094
> 
> The MOL window will not advance past the logo, nor is there any more 
> output until I CTRL-C in the terminal window. MacOS 9 will boot just 
> fine off of an HFS partition. Anyone have any idea what the "no 
> translation" and "unmapped 'RAM-read-access'" lines mean?

Yes... this is a bug which has been present for quite some
time. Unfortunately, I can't reproduce it locally so I haven't
been able to fix it (only certain HFS+ volumes seems to trigger
it). If someone with this bug could make an image of the HFS+
volume, compress it send it to me somehow, it would be very useful
(but I understand that this usually is not a viable option in
most cases).

In any case, there is a workaround.

i)	Use -boot to specify the boot volume (if it was one of the
	other volumes that triggered the problem). Note that
	for this to really be useful, one has to specify the
	fully qualified partition, e.g. 'blkdev: /dev/hda7 -rw -boot'.

ii)	If the problem is still there, copy the "System Folder/Mac OS ROM"
	file to the linux side (avoid MacBinary encoding!) and
	specify it using 'newworld_rom: /path/to/the/rom_file' in
	/etc/mol/molrc.macos.

> I'm also having trouble getting networking to work under OS 9. The tun 
> driver under OS X works OK if I assign an IP address of 192.168.2.x 
> (DHCP won't work) and a gateway of 192.168.2.1. However the same 
> procedure (substituting 192.168.1.x in the appropriate places) doesn't 
> work for OS 9, even when I run MOL as root. The ethertap driver works 
> for neither OS 9 nor OS X.

Are you certain you have selected the tun driver? By default,
two "ethernet cards" show up in MacOS (the sheep_net driver and the
tun driver).

As for DHCP, check that you have the /usr/sbin/dhcpd daemon installed.
You might also have to uncomment the line

#ddns-update-style      ad-hoc;

in /etc/mol/dhcpd-mol.conf (some versions of the dhcpd client requires
it, others choke on it...).

/Samuel