Date: Mon, 12 Jul 2004 15:11:58 -0400 From: "Eric Toll" <etoll@vipstructures.com> To: "Lute Mullenix" <lute@vfemail.net>, <freebsd-newbies@freebsd.org> Subject: RE: Agp0 probe forced my to use floppy kernel in 5.2.1 Release Message-ID: <9BC86C67C3AF7646B9C5382020457A9456DE67@VIP10-WIN2K>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-newbies@freebsd.org=20 > [mailto:owner-freebsd-newbies@freebsd.org] On Behalf Of Lute Mullenix > Sent: Monday, July 12, 2004 3:09 PM > To: freebsd-newbies@freebsd.org > Subject: Re: Agp0 probe forced my to use floppy kernel in=20 > 5.2.1 Release >=20 > On Mon, 12 Jul 2004 11:00:41 -0400 > "Eric Toll" <etoll@vipstructures.com> insisted: >=20 > > Hello list! > >=20 > > I had a *hell* of a time trying to get FreeBSD 5.2.1 installed on a=20 > > Netserver E60. PII 450 SCSI > >=20 > > During the agp0 probe the system would lock up tight. > >=20 > > Here's what I did. Made some floppies, (since they don't have AGP=20 > > support on them) Booted System, went thru the whole install=20 > and then=20 > > right before Exiting Install, I ran an Emergency Shell on TTY4. > >=20 > > Then I FTP'd the gunziped kernel file into /boot/kernel.=20 > Then rebooted=20 > > system. (From another 5.2.1 box) > >=20 > > System came up fine (no lockup) but now I have no ethernet, yet the=20 > > std boot and mfsroot floppies do have an Intel nic driver=20 > on them that=20 > > works, after all I used the floppy boot discs to FTP the=20 > floppy kernel=20 > > onto my scsi HD. > >=20 > > Geesh, what an ordeal. (If you didn't know how to go about it as I > > didn't) > >=20 > > What am I doing wrong? Is this the wrong way? I tried to let the HD=20 > > boot up to the loader prompt after the 5.2.1 install and then set=20 > > currdev=3D/dev/fd0 and then do a load kernel (this did not work), = and=20 > > then to a setcurrdev=3D<back to my HD> so I can boot from it=20 > but no luck. > >=20 > > Anyway my machine is up but it's pretty useless without Network... > >=20 > > Tips, pointers, misc. info would be much appreciated. > >=20 > > TIA > >=20 > > Eric > >=20 > >=20 >=20 > Was that kernel you transfered a custome job for that=20 > machine? If so it may not have the proper driver built into=20 > it for the new machine. >=20 >=20 > -- > Lute >=20 > It's OK to be different > FreeBSD 5.2.1 RELEASE >=20 > _______________________________________________ > freebsd-newbies@freebsd.org mailing list=20 > http://lists.freebsd.org/mailman/listinfo/freebsd-newbies > To unsubscribe, send any mail to=20 > "freebsd-newbies-unsubscribe@freebsd.org" >=20 No It was not. It was the exact kernel from the floppy boot = (floppy.flp) 5.2.1 Release. When I use 5.2.1 boot, and 5.2.1 msfroot to load the machine the Ether = adapter is there, and works. When I take the 5.2.1 floppy boot kernel copyt it the HD under = /boot/kernel the machine boots but no NIC. How can I add it back in??? Thanks Much, Eric =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9BC86C67C3AF7646B9C5382020457A9456DE67>