I had a similar issue when installing RC2. What does " Loading module if_awi.ko failed. Baystack 660 and others" refers to? I haven't had much luck with this and every install attempt fails with this message. Plus, I haven't see any such problem with 4.6 or 4.7.
Anybody has any idea? <> JF -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Gavin Atkinson Sent: Thursday, December 26, 2002 4:00 PM To: [EMAIL PROTECTED] Subject: 5.0-RC2 install story Hi all, I've just tested an install of 5.0-RC2 using the boot floppies FTP install method (from ftp3.uk.freebsd.org). The machine is a 1.8GHz P4 with an Intel 850MV2 motherboard. Overall the installation was successful, however: First time I booted the install disks, the machine hung on a sysinstall requester, "Loading module if_awi.ko failed. Baystack 660 and others". Not even caps lock or scroll lock worked. I rebooted, checked the bios was setup correctly, never changed anything, and tried again. it worked. The drive was originally formatted NTFS, i deleted the whole partition and created a freebsd partition on the first half of the drive. I used the Auto option for the slices, and then manually split /usr into /usr and /usr/home. I performed a custom install, installing everything except kerberos and pre-4 compat. The install went well, however at the end of the install, every option I selected on the menu gave "Couldn't stat dir /tmp. Bad file descriptor". Rebooted to find the same problem. I had to unmount it, newfs it, remount it and chmod it before it worked. I tried installing Gnome2, but the install couldn't find libgtkhtml-2.0.3 on the ftp mirror I was using. I grabbed it off the primary successfully. Similarly with the option to read online docs, lincs-0.98,1 could not be found on ftp3.uk.freebsd.org but was on ftp.freebsd.org. FreeBSD happily detected all my hardware, and seemed happy with everything. Xfree86 auto-config detected everything and worked fine. Worryingly, the game same-gnome died with a floating-point exception, which I haven't seen since all the FP problems last time. I won't be able to investigate this further until the new year. Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
