Date: Thu, 06 Jan 2000 16:56:40 -0600 From: "Wes Bauske" <wsb@paralleldata.com> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: mjacob@feral.com, "Jordan K. Hubbard" <jkh@time.cdrom.com>, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/15611: EIDE Large Disk Support, Newfs problem, File systemcorruption,IBM-DPTA-353750 Message-ID: <38751DA8.4A66051B@paralleldata.com> References: <1693.947188310@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" wrote: > > Hurm, I don't have those results at all the Alpha snapshots I've > tried. Perhaps we could hear a bit more about the specific versions > used and the hardware in question? > > - Jordan > > > > > > OK, I tried the latest two versions of boot floppies > > > from current.FreeBSD.org and both fail to get to the > > > point where I can do an install. Any preferences on > > > which date snapshot for 4.0 I should try?? > > > > > > One got to the point where it put up the sysinstall > > > menu but I couldn't use the keyboard to navigate the > > > menus. The other wouldn't boot saying it couldn't > > > load /kernel. > > > > Boy, that sucks. Jordan? > > > > OK. I got the floppies from: ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000103-CURRENT/ ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000105-CURRENT/ The first one booted and got to the blue menu but when I tried to use the keyboard, the whole menu moved up and down, kind of like curses was broken/no longer active. The last one wouldn't boot saying /kernel not loaded. I used the "ls" command in the boot program and it showed kernel.gz was there. The system is a PIII 600 with SuperMicro PIIISCD board. It uses the Intel 820 chipset architecture so it's quite new. Has a standard 1.44MB floppy, 50x cdrom and two 40GB Maxtor EIDE drives. I did install 3.4 on the box but doing any large file systems on the Maxtors trashes my separate root partition. Also, I tried RH6.0 Linux and it's OK except for using large FS on the Maxtors. If I just do a "touch junk" when the FS is 32GB or more, it trashes Linux's root FS too. Not sure if that's helpful but it tells me this board is doing something different than the Athlon I started with 40GB EIDE drives on. The Athlon at least behaved with Linux and large file systems. What else do you want to know?? I'm expecting a Via Apollo Pro133 based motherboard sometime next week that I'll be trying too. Wes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38751DA8.4A66051B>