Date: Mon, 05 Mar 2001 15:18:09 +0000 From: Dave Barnett <dbarn@ot.com> To: questions@FreeBSD.org Subject: FreeBSD4.2 & FreeBSD3.4 Message-ID: <3AA3AE31.B38A715@ot.com>
next in thread | raw e-mail | index | archive | help
--------------BA90DBECD2F390F12CB8C8DD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sirs: I'm having the same trouble with my FreeBSD 4.2 as I have with 3.4. I install ccording to the NewUser/Standard installation and on trying to boot it just sits there after the intro. message from Boot-Magic - "Preparing to boot FreeBSD". My particulars are as foloows Processor - Intel 686 - 350mhz Memory - 96MB HD (1) - 8.1 GB Partitions - (Roughly) (1) 2 GB - DOS 6.2/Windows 3.1 (all primaries) (2) 3.5 GB - Slackware Linux 7.1 (3) .2 GB - Linux Swap (4) 2.2 GB - FreeBSD/386 (as typed by the lable prog.) .x GB (I dont know quite how to use this - it's beyond 1024cylinders, or whatever) ZIP drive (internal) I'm using 'BootMagic' as the boot manager in the (I think) master boot record. I tried making FreeBSD the bootable partition in the "Label" program, instead of my work-horse "Slack", but that didn't help. I even wiped out Slack & BootMagic(accidentally, but I'm used to that) and tried it as the only system besides DOS/WIN on the disk, with the same results. In one case - which I've been unable to reproduce, it did output "Read error." The hard disk is clicking at ~ 1" intervals. I think I'm not doing something right, but I've not been able to find my error. And I just ordered your Book. Maybe that gives some system detail. The linux 'mount' command "mount /dev/hda4 /mnt" apparently mounts the disk (I have the USF enabled, read-only, in the linux kernel), but the 'ls' command says that some filename is too long to read. I ordered FreeBSD 4.2 (just received and tried to install it) because I figured maybe my trouble with 3.4 was known and probably fixed, but - alas, no. I checked the FAQ on your website, also to no avail, so I'm writing you. If you need any more specifics, please let me know. In the meantime, I have my Slack 7.1 back up and running and can operate. I'm just a user, not a server or chatter, and I'm retired with lot's of time to try suggestions, so I would appreciate anything you can offer. Thank you. Sincerely Dave Barnett <dbarn@ot.com> --------------BA90DBECD2F390F12CB8C8DD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Sirs: <p> I'm having the same trouble with my FreeBSD 4.2 as I have with 3.4. I install ccording to the NewUser/Standard installation and on trying to boot <b><i>it just sits there</i></b> after the intro. message from Boot-Magic - "Preparing to boot FreeBSD". My particulars are as foloows <p> Processor - Intel 686 - 350mhz <br> Memory - 96MB <br> HD (1) - 8.1 GB <br> Partitions - (Roughly) (1) 2 GB - DOS 6.2/Windows 3.1 <br> (all primaries) (2) 3.5 GB - Slackware Linux 7.1 <br> (3) .2 GB - Linux Swap <br> (4) 2.2 GB - FreeBSD/386 (as typed by the lable prog.) <br> .x GB (I dont know quite how to use this - it's beyond 1024cylinders, or whatever) <br> ZIP drive (internal) <p> I'm using 'BootMagic' as the boot manager in the (I think) master boot record. <p> I tried making FreeBSD the bootable partition in the "Label" program, instead of my work-horse "Slack", but that didn't help. I even wiped out Slack & BootMagic(accidentally, but I'm used to that) and tried it as the only system besides DOS/WIN on the disk, with the same results. In one case - which I've been unable to reproduce, it <b><u>did</u></b> output "Read error." The hard disk is clicking at ~ 1" intervals. <p> I think I'm not doing something right, but I've not been able to find my error. And I just ordered your Book. Maybe that gives some system detail. <p> The linux 'mount' command "mount /dev/hda4 /mnt" apparently mounts the disk (I have the USF enabled, read-only, in the linux kernel), but the 'ls' command says that some filename is too long to read. <p> I ordered FreeBSD 4.2 (just received and tried to install it) because I figured maybe my trouble with 3.4 was known and probably fixed, but - alas, no. <p> I checked the FAQ on your website, also to no avail, so I'm writing you. <p> If you need any more specifics, please let me know. In the meantime, I have my Slack 7.1 back up and running and can operate. I'm just a user, not a server or chatter, and I'm retired with lot's of time to try suggestions, so I would appreciate anything you can offer. <p> Thank you. <p> Sincerely <p> Dave Barnett <dbarn@ot.com> <br> </html> --------------BA90DBECD2F390F12CB8C8DD-- 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?3AA3AE31.B38A715>