Date: Thu, 1 May 2008 20:25:25 -0700 From: Jeremy Chadwick <koitsu@freebsd.org> To: Shaun Sabo <shaun.bsd@gmail.com> Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller Message-ID: <20080502032525.GA83155@eos.sc1.parodius.com> In-Reply-To: <be79767b0805012003i72578470x9b568c7cf47fe4b@mail.gmail.com> References: <be79767b0805011034l7b82327dp12637daa12598567@mail.gmail.com> <20080501182325.GA62281@eos.sc1.parodius.com> <be79767b0805011204r1a7aad67tf4f78d5363684f81@mail.gmail.com> <20080501204157.GA67015@eos.sc1.parodius.com> <be79767b0805011918k304e26d0ybd79f2d20e102bf7@mail.gmail.com> <be79767b0805011946p4a49ff7bs51db30652e0736aa@mail.gmail.com> <20080502025657.GA82058@eos.sc1.parodius.com> <be79767b0805012003i72578470x9b568c7cf47fe4b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > but then why does it not complain in freebsd 6.2, linux, or windows but it > does in 7.0? FreeBSD 6.2 is very different than 7.0. :-) And you later state that Linux had the same problem as FreeBSD. And chances are, Dell has tested their system thoroughly on Windows, not Linux or FreeBSD, so device support under Windows is going to be quite solid. > and why i mean by the freebsd sysinstaller is the screen you > get when you boot a freebsd disk or when you type sysinstall at a command > line in a bsd system. I don't see what this has to do with your machine stalling 2/3rds of the way through its boot-up process. The only thing I can think of is that some kind of ATA request is causing the nF4 to lock up, and the BIOS isn't properly resetting it upon a soft reboot. > i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was > still on the 2.4 linux kernel and didnt support my mobo yet so it tried to > detect it and you had to completely power off the system to get it to boot > again, which seems like what is happening here. Okay, so this is useful knowledge. It means that Linux has also exhibited the same behaviour as FreeBSD, at least in the past, which means there may be some incompatibility with the devices on the motherboard. It would be useful to know what the Linux folks did to work around the problem. Since I know the nForce 4 works on FreeBSD, the only thing I can think of which might be causing chaos is ACPI, and there are many board manufacturers who release incorrect ACPI tables within in their BIOS. If you try booting either 7.0-RELEASE or 7.0-STABLE with ACPI disabled (it's one of the bootup menu items), does it help? > im going to try re-flashing > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. You're burning the livefs ISO image to a CD and booting it, correct? What is the exact error you get from FreeBSD when trying to boot the livefs CD? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080502032525.GA83155>