Problems Installing FreeBSD-PPC

[David S. Besade]

on 3/18/04 5:51 AM, Peter Grehan at grehan at freebsd.org wrote:

> Hi David
> 
>> Okay tried that new kernel in my setup and all. Thought you might like to
>> know that I finally got DHCPD, TFTP and NFS all running off my Mac, properly
>> it seems, the DHCPD is finally sending all the BOOTP info.
> 
> Did you have to do much different than the posted instructions for
> FreeBSD ?
> 
Here is what I have to do exactly:

I boot to open firmware as per the directions and then do the following:

Boot enet:,loader

**connects to my G4 gets the loader and boots, the loader then says it can't
find a bootable kernel, even if I put a kernel file in there or rename the
kernel.dc**

Load kernel/kernel.dc (or whatever kernel I am trying to boot)

**the command executes and the kernel loads fine**

boot -s

**the kernel boots just fine everything loads except the Ethernet
(obviously). I tried the -v option but it all flew by so damn quickly, I
mean FAST so I couldn't even make out the text.**

Mountroot> nfs
Mounting root from nfs
nfs_diskless: no interface
Root mount failed: -1

Various jargon about what root systems I can mount and how

Mountroot>
(so that¹s exactly what I do with respect to trying to get this all to work)
>> (the load comes up, says it can't find/load the kernel)
>> I type (at the loader prompt)
>> 
>> Load kernel/kernel.dc
> 
> I should have mentioned that kernel.dc has to be renamed to 'kernel',
> or the manual load command used as you did.
> 
Doesn't matter if its named kernel or kernel.dc, the loader won't
automatically boot the kernel.. Odd enough.
>> mountroot> nfs
>> Mounting root from nfs
>> nfs_diskless: no interface
> ...
>> Welp what next?
> 
> Looks like the PCI ID for the 21143 eth chip isn't being matched
> by the driver, so that has to be determined. Try a 'boot -v', and
> hopefully you will see the PCI IDs of all devices go past and be
> able to see the eth ID before it scrolls by.
Heh, if I could read 100 million words per second I might be able to make
some of that out :grin:, but sorry couldn't see it, but I was able via debug
mode (if I hit enter at the mountroot prompt when its blank, it enters
debug) to get a listing of the PCIReg's. Maybe that will help you. Here they
all are:

Grackle_hb0 at pci0:11:0: class=0x060000 card=0x00000000 chip=0x0020106b
rev=0x00 hdr=0x00 

none0 at pci0:16:0: class=0x038000 card=0x524c1002 chip=0x524c1002 rev=0x00
hdr=0x00

Grackle_hb1 at pci0:11:0: class=0x060000 card=0x00000000 chip=0x001f106b
rev=0x00 hdr=0x00

fwohci0 at pci0:18:0: class=0x0c0010 card=0x00000000 chip=0x8019104c rev=0x00
hdr=0x00

none1 at pci0:19:0: class=0x020000 card=0x00000000 chip=0x00191011 rev=0x41
hdr=0x00

macio0 at pci0:23:0: class=0xff0000 card=0x00000000 chip=0x0022106b rev=0x02
hdr=0x00

ohci0 at pci0:24:0: class=0x0c0310 card=0x00000000 chip=0x0019106b rev=0x00
hdr=0x00

ohci1 at pci0:25:0: class=0x0c0310 card=0x00000000 chip=0x0019106b rev=0x00
hdr=0x00

Grackle_hb2 at pci0:11:0: class=0x060000 card=0x00000000 chip=0x001e106b
rev=0x00 hdr=0x00

While I am no developer, I am guessing that is what you needed. Everything
that was listed is there. Hopefully it is of some help to you.
> I might have some more detailed instructions tomorrow when I can
> get to a test system and give you some expected text.
> 
It might help a few people. I am just wanting to get this installed and get
it down so when its time to upgrade its pretty much a snap :).
> later,
> 
> Peter.
> 
~Regards
Dave
-MacHowto.com WebMaster