Date: Thu, 18 Mar 2004 08:19:34 -0700 From: "David S. Besade" <webmaster@machowto.com> To: Peter Grehan <grehan@freebsd.org> Cc: freebsd-ppc@freebsd.org Subject: Re: Problems Installing FreeBSD-PPC Message-ID: <BC7F0C16.1D4%webmaster@machowto.com> In-Reply-To: <40599B49.8020706@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 3/18/04 5:51 AM, Peter Grehan at grehan@freebsd.org wrote: > Hi David >=20 >> Okay tried that new kernel in my setup and all. Thought you might like t= o >> know that I finally got DHCPD, TFTP and NFS all running off my Mac, prop= erly >> it seems, the DHCPD is finally sending all the BOOTP info. >=20 > Did you have to do much different than the posted instructions for > FreeBSD ? >=20 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=B9s 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) >>=20 >> Load kernel/kernel.dc >=20 > I should have mentioned that kernel.dc has to be renamed to 'kernel', > or the manual load command used as you did. >=20 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? >=20 > 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 debu= g 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 the= y all are: Grackle_hb0@pci0:11:0: class=3D0x060000 card=3D0x00000000 chip=3D0x0020106b rev=3D0x00 hdr=3D0x00=20 none0@pci0:16:0: class=3D0x038000 card=3D0x524c1002 chip=3D0x524c1002 rev=3D0x00 hdr=3D0x00 Grackle_hb1@pci0:11:0: class=3D0x060000 card=3D0x00000000 chip=3D0x001f106b rev=3D0x00 hdr=3D0x00 fwohci0@pci0:18:0: class=3D0x0c0010 card=3D0x00000000 chip=3D0x8019104c rev=3D0x00 hdr=3D0x00 none1@pci0:19:0: class=3D0x020000 card=3D0x00000000 chip=3D0x00191011 rev=3D0x41 hdr=3D0x00 macio0@pci0:23:0: class=3D0xff0000 card=3D0x00000000 chip=3D0x0022106b rev=3D0x02 hdr=3D0x00 ohci0@pci0:24:0: class=3D0x0c0310 card=3D0x00000000 chip=3D0x0019106b rev=3D0x00 hdr=3D0x00 ohci1@pci0:25:0: class=3D0x0c0310 card=3D0x00000000 chip=3D0x0019106b rev=3D0x00 hdr=3D0x00 Grackle_hb2@pci0:11:0: class=3D0x060000 card=3D0x00000000 chip=3D0x001e106b rev=3D0x00 hdr=3D0x00 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. >=20 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, >=20 > Peter. >=20 ~Regards Dave -MacHowto.com WebMaster
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BC7F0C16.1D4%webmaster>