Date: Sun, 4 Mar 2001 22:21:32 -0800 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Robert Liotta" <rsliotta@hotmail.com>, <questions@FreeBSD.ORG> Subject: RE: Interesting boot floppy problem Message-ID: <005801c0a53c$85b92ca0$1401a8c0@tedm.placo.com> In-Reply-To: <OE30rIyklxDqRQtdB3x00001b9c@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Your going to have to build a custom boot floppy with a kernel that does not have that particular device driver in it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Robert Liotta Sent: Sunday, March 04, 2001 12:06 PM To: questions@FreeBSD.ORG Subject: Interesting boot floppy problem Folks, I have been running FreeBSD 3.2 on a system forever. It is an SMP system. At that time, the onboard AMD PCI SCSI adapter was not supported. I am trying to upgrade to release 4.2. I tried source and that is failing. I have even seen some people upgrade to release 3.5 and the go forward. 3.5 kernel hangs during reboot. So I am getting desperate. I am trying to boot from floppies and do a binary upgrade. I figured I can just reupgrade from source after that and I will be OK. Now here's the problem. This $#%#$%# AMD PCI SCSI now seems to be supported. As soon as it hit this, I lock up tight. How do I tell the kernel to ignore a PCI device that is probed? I know how to do the others. Any help would be appreciated. Thanks. Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005801c0a53c$85b92ca0$1401a8c0>