FreeBSD 7.0 SATA Controller

Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop
machine and im
having a lot of trouble with this. First I could not use USB
keyboards with
the installer program (which is fine, i dont mind switching
to PS2). then
once i got into the sysinstaller it does not detect my Hard
Disks. i also
tried installing an old 6.2 cd that i had sitting around and
remaking world
and kernel but when i installed the kernel and restarted to
go into single
user mode the system could not mount the root filesystem.
the motherboard im
using is a nvidia nforce4 with Serial ATA hard disks. Does
anyone know how
to get FreeBSD 7.0 to recognize my hard drives?
_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

On Thu, May 01, 2008 at 01:34:53PM -0400, Shaun Sabo wrote:
> Im trying to install FreeBSD 7.0 on a Dell XPS 600
desktop machine and im
> having a lot of trouble with this. First I could not
use USB keyboards with
> the installer program (which is fine, i dont mind
switching to PS2). then
> once i got into the sysinstaller it does not detect my
Hard Disks. i also
> tried installing an old 6.2 cd that i had sitting
around and remaking world
> and kernel but when i installed the kernel and
restarted to go into single
> user mode the system could not mount the root
filesystem. the motherboard im
> using is a nvidia nforce4 with Serial ATA hard disks.
Does anyone know how
> to get FreeBSD 7.0 to recognize my hard drives?

Re: USB keyboard: USB support on FreeBSD is spotty.  That
said, I've
never run into problems getting FreeBSD to detect and use a
USB keyboard
(other USB devices are a different story).  You'd need to
provide some
dmesg(8) output to verify, but I know that's going to be
difficult until
you can get FreeBSD installed.

Re: SATA disks: I can assure you that FreeBSD works fine
with SATA disks
connected to an nForce 4 chipset, because I've used them
myself with no
issue.  Chances are there's a BIOS setting that's causing
mayhem, or
you may be using a RAID array of some sort (since the XPS700
is one of
those "gamer lozlozlz" systems).

The manual for this system is here:

http://support.dell.com/support/edocs/systems/xps700/

Screenshots of the BIOS are here:

http://www.bit-tech.net/hardware/2006/09/04/Del
l_XPS_700_review/5

Are you using RAID at all on this system?  If so, chances
are that's why
it doesn't see your array.

Finally, if available, I'd try a BIOS update.  Googling for
results
shows that system has quite a large number of issues with
its BIOSes,
and Dell has been fairly good about providing updates to fix
problems.

-- 
| 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 |

_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

I checked to make sure that the hard disks are not in raid
configuration and
there are not. i also checked and my bios are at the latest
version
available (A11). also this is an XPS 600 not 700 and i have
the correct
users manual in paper and digital formats. how would you
like the dmesg to
be presented? i dont think i have any way to writing it to a
thumb drive or
such devices from the installer. should i just take digital
pictures?

On Thu, May 1, 2008 at 2:23 PM, Jeremy Chadwick
<koitsufreebsd.org> wrote:

> On Thu, May 01, 2008 at 01:34:53PM -0400, Shaun Sabo
wrote:
> > Im trying to install FreeBSD 7.0 on a Dell XPS 600
desktop machine and
> im
> > having a lot of trouble with this. First I could
not use USB keyboards
> with
> > the installer program (which is fine, i dont mind
switching to PS2).
> then
> > once i got into the sysinstaller it does not
detect my Hard Disks. i
> also
> > tried installing an old 6.2 cd that i had sitting
around and remaking
> world
> > and kernel but when i installed the kernel and
restarted to go into
> single
> > user mode the system could not mount the root
filesystem. the
> motherboard im
> > using is a nvidia nforce4 with Serial ATA hard
disks. Does anyone know
> how
> > to get FreeBSD 7.0 to recognize my hard drives?
>
> Re: USB keyboard: USB support on FreeBSD is spotty. 
That said, I've
> never run into problems getting FreeBSD to detect and
use a USB keyboard
> (other USB devices are a different story).  You'd need
to provide some
> dmesg(8) output to verify, but I know that's going to
be difficult until
> you can get FreeBSD installed.
>
> Re: SATA disks: I can assure you that FreeBSD works
fine with SATA disks
> connected to an nForce 4 chipset, because I've used
them myself with no
> issue.  Chances are there's a BIOS setting that's
causing mayhem, or
> you may be using a RAID array of some sort (since the
XPS700 is one of
> those "gamer lozlozlz" systems).
>
> The manual for this system is here:
>
> http://support.dell.com/support/edocs/systems/xps700/
>
> Screenshots of the BIOS are here:
>
> http://www.bit-tech.net/hardware/2006/09/04/Del
l_XPS_700_review/5
>
> Are you using RAID at all on this system?  If so,
chances are that's why
> it doesn't see your array.
>
> Finally, if available, I'd try a BIOS update.  Googling
for results
> shows that system has quite a large number of issues
with its BIOSes,
> and Dell has been fairly good about providing updates
to fix problems.
>
> --
> | 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 |
>
>
_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote:
> I checked to make sure that the hard disks are not in
raid configuration and
> there are not. i also checked and my bios are at the
latest version
> available (A11). also this is an XPS 600 not 700 and i
have the correct
> users manual in paper and digital formats. how would
you like the dmesg to
> be presented? i dont think i have any way to writing it
to a thumb drive or
> such devices from the installer. should i just take
digital pictures?

Digital pictures would be fine, unless you want to try the
serial
console route (chances are you don't have this sort of
environment set
up, so it's probably more effective to take photos).

One thing: does Linux detect your disks on this system?

I'd recommend downloading one of the recent RELENG_7
snapshot CDs,
specifically the "livefs" one, and boot it.  dmesg
doesn't come with the
standard installation disc (disc1), hence why I'm
recommending livefs.
The snapshots are available here:

ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804

You probably want one of these two:

ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABL
E-200804-amd64-livefs.iso
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABL
E-200804-i386-livefs.iso

dmesg should show some ATA stuff at the end, assuming you're
familiar
with FreeBSD's kernel output.  Something like this, assuming
the
physical disks are detected:

ad4: 190782MB <WDC WD2000JD-00HBB0 08.02D08> at
ata2-master SATA150
ad6: 476940MB <WDC WD5000AAKS-00YGA0 12.01C02> at
ata3-master SATA300
ad8: 476940MB <WDC WD5000AAKS-00TMA0 12.01C01> at
ata4-master SATA300
ad10: 476940MB <WDC WD5000AAKS-00TMA0 12.01C01> at
ata5-master SATA300

You'll need to work backwards to figure out what is
connected to what,
e.g.:

$ dmesg | grep ata2
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ad4: 190782MB <WDC WD2000JD-00HBB0 08.02D08> at
ata2-master SATA150

$ dmesg | grep atapci1
atapci1: <Intel AHCI controller> port
0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30
b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on
pci0
atapci1: [ITHREAD]
atapci1: AHCI Version 01.10 controller with 4 ports
detected
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
ata4: <ATA channel 2> on atapci1
ata5: <ATA channel 3> on atapci1

Otherwise, if none of this works, you'll need to somehow
provide the
full output of "pciconf -lv", which will be many
screen fulls of data.
You'll probably have to pipe it through "more",
take a shot, hit
spacebar, take another shot, etc...

Please post URLs to the photos, rather than attaching them. 
The mailing
list software does not take kindly to large attachments.

-- 
| 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 |

_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

since it is not 7-stable im interested in shouldnt i use the
7.0-RELEASE
livefs?

On Thu, May 1, 2008 at 4:41 PM, Jeremy Chadwick
<koitsufreebsd.org> wrote:

> On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo
wrote:
> > I checked to make sure that the hard disks are not
in raid configuration
> and
> > there are not. i also checked and my bios are at
the latest version
> > available (A11). also this is an XPS 600 not 700
and i have the correct
> > users manual in paper and digital formats. how
would you like the dmesg
> to
> > be presented? i dont think i have any way to
writing it to a thumb drive
> or
> > such devices from the installer. should i just
take digital pictures?
>
> Digital pictures would be fine, unless you want to try
the serial
> console route (chances are you don't have this sort of
environment set
> up, so it's probably more effective to take photos).
>
> One thing: does Linux detect your disks on this
system?
>
> I'd recommend downloading one of the recent RELENG_7
snapshot CDs,
> specifically the "livefs" one, and boot it. 
dmesg doesn't come with the
> standard installation disc (disc1), hence why I'm
recommending livefs.
> The snapshots are available here:
>
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804
>
> You probably want one of these two:
>
>
>
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABL
E-200804-amd64-livefs.iso
>
>
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABL
E-200804-i386-livefs.iso
>
> dmesg should show some ATA stuff at the end, assuming
you're familiar
> with FreeBSD's kernel output.  Something like this,
assuming the
> physical disks are detected:
>
> ad4: 190782MB <WDC WD2000JD-00HBB0 08.02D08> at
ata2-master SATA150
> ad6: 476940MB <WDC WD5000AAKS-00YGA0 12.01C02> at
ata3-master SATA300
> ad8: 476940MB <WDC WD5000AAKS-00TMA0 12.01C01> at
ata4-master SATA300
> ad10: 476940MB <WDC WD5000AAKS-00TMA0 12.01C01>
at ata5-master SATA300
>
> You'll need to work backwards to figure out what is
connected to what,
> e.g.:
>
> $ dmesg | grep ata2
> ata2: <ATA channel 0> on atapci1
> ata2: [ITHREAD]
> ad4: 190782MB <WDC WD2000JD-00HBB0 08.02D08> at
ata2-master SATA150
>
> $ dmesg | grep atapci1
> atapci1: <Intel AHCI controller> port
>
0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30
b0-0x30bf mem
> 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0
> atapci1: [ITHREAD]
> atapci1: AHCI Version 01.10 controller with 4 ports
detected
> ata2: <ATA channel 0> on atapci1
> ata3: <ATA channel 1> on atapci1
> ata4: <ATA channel 2> on atapci1
> ata5: <ATA channel 3> on atapci1
>
> Otherwise, if none of this works, you'll need to
somehow provide the
> full output of "pciconf -lv", which will be
many screen fulls of data.
> You'll probably have to pipe it through
"more", take a shot, hit
> spacebar, take another shot, etc...
>
> Please post URLs to the photos, rather than attaching
them.  The mailing
> list software does not take kindly to large
attachments.
>
> --
> | 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 |
>
>
_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

i tried both the 7-stable and 7.0-RELEASE livefs disks and
when i went into
fixit then to CD/DVD livefs it would ask me for the livefs
cd (which i had
in the drive and which i booted from) it looks like i cant
even mount the
image of the livefs disk from the cd-rom drive. also iv
noticed that when i
reboot after booting into the sysinstaller the bios gets
about 2/3 of the
way booted and stops and i have to hold the power and reboot
to get back
into opensuse/vista.

On Thu, May 1, 2008 at 10:18 PM, Shaun Sabo
<shaun.bsdgmail.com> wrote:

> since it is not 7-stable im interested in shouldnt i
use the 7.0-RELEASE
> livefs?
>
>
> On Thu, May 1, 2008 at 4:41 PM, Jeremy Chadwick
<koitsufreebsd.org>
> wrote:
>
> > On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun
Sabo wrote:
> > > I checked to make sure that the hard disks
are not in raid
> > configuration and
> > > there are not. i also checked and my bios are
at the latest version
> > > available (A11). also this is an XPS 600 not
700 and i have the
> > correct
> > > users manual in paper and digital formats.
how would you like the
> > dmesg to
> > > be presented? i dont think i have any way to
writing it to a thumb
> > drive or
> > > such devices from the installer. should i
just take digital pictures?
> >
> > Digital pictures would be fine, unless you want to
try the serial
> > console route (chances are you don't have this
sort of environment set
> > up, so it's probably more effective to take
photos).
> >
> > One thing: does Linux detect your disks on this
system?
> >
> > I'd recommend downloading one of the recent
RELENG_7 snapshot CDs,
> > specifically the "livefs" one, and boot
it.  dmesg doesn't come with the
> > standard installation disc (disc1), hence why I'm
recommending livefs.
> > The snapshots are available here:
> >
> >
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804
> >
> > You probably want one of these two:
> >
> >
> >
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABL
E-200804-amd64-livefs.iso
> >
> >
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABL
E-200804-i386-livefs.iso
> >
> > dmesg should show some ATA stuff at the end,
assuming you're familiar
> > with FreeBSD's kernel output.  Something like
this, assuming the
> > physical disks are detected:
> >
> > ad4: 190782MB <WDC WD2000JD-00HBB0 08.02D08>
at ata2-master SATA150
> > ad6: 476940MB <WDC WD5000AAKS-00YGA0
12.01C02> at ata3-master SATA300
> > ad8: 476940MB <WDC WD5000AAKS-00TMA0
12.01C01> at ata4-master SATA300
> > ad10: 476940MB <WDC WD5000AAKS-00TMA0
12.01C01> at ata5-master SATA300
> >
> > You'll need to work backwards to figure out what
is connected to what,
> > e.g.:
> >
> > $ dmesg | grep ata2
> > ata2: <ATA channel 0> on atapci1
> > ata2: [ITHREAD]
> > ad4: 190782MB <WDC WD2000JD-00HBB0 08.02D08>
at ata2-master SATA150
> >
> > $ dmesg | grep atapci1
> > atapci1: <Intel AHCI controller> port
> >
0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30
b0-0x30bf mem
> > 0xe8600400-0xe86007ff irq 19 at device 31.2 on
pci0
> > atapci1: [ITHREAD]
> > atapci1: AHCI Version 01.10 controller with 4
ports detected
> > ata2: <ATA channel 0> on atapci1
> > ata3: <ATA channel 1> on atapci1
> > ata4: <ATA channel 2> on atapci1
> > ata5: <ATA channel 3> on atapci1
> >
> > Otherwise, if none of this works, you'll need to
somehow provide the
> > full output of "pciconf -lv", which will
be many screen fulls of data.
> > You'll probably have to pipe it through
"more", take a shot, hit
> > spacebar, take another shot, etc...
> >
> > Please post URLs to the photos, rather than
attaching them.  The mailing
> > list software does not take kindly to large
attachments.
> >
> > --
> > | 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 |
> >
> >
>
_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote:
> i tried both the 7-stable and 7.0-RELEASE livefs disks
and when i went into
> fixit then to CD/DVD livefs it would ask me for the
livefs cd (which i had
> in the drive and which i booted from) it looks like i
cant even mount the
> image of the livefs disk from the cd-rom drive.

I'd recommend you burn one of the snapshot livefs images to
a CD and
boot it.  This is what I was implying the first time around.
 It should
give you a live FreeBSD system with common utilities.

> also iv noticed that when i
> reboot after booting into the sysinstaller the bios
gets about 2/3 of the
> way booted and stops and i have to hold the power and
reboot to get back
> into opensuse/vista.

I don't understand what this means.  "When I reboot
after booting into
the sysinstaller".  Are you talking about FreeBSD
sysinstall?

Otherwise, any situation where the BIOS does not boot your
hard disks
sounds more like a BIOS or system problem and definitely has
nothing to
do with FreeBSD.

-- 
| 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 |

_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

but then why does it not complain in freebsd 6.2, linux, or
windows but it
does in 7.0? 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 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. 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.

On Thu, May 1, 2008 at 10:56 PM, Jeremy Chadwick
<koitsufreebsd.org> wrote:

> On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo
wrote:
> > i tried both the 7-stable and 7.0-RELEASE livefs
disks and when i went
> into
> > fixit then to CD/DVD livefs it would ask me for
the livefs cd (which i
> had
> > in the drive and which i booted from) it looks
like i cant even mount
> the
> > image of the livefs disk from the cd-rom drive.
>
> I'd recommend you burn one of the snapshot livefs
images to a CD and
> boot it.  This is what I was implying the first time
around.  It should
> give you a live FreeBSD system with common utilities.
>
> > also iv noticed that when i
> > reboot after booting into the sysinstaller the
bios gets about 2/3 of
> the
> > way booted and stops and i have to hold the power
and reboot to get back
> > into opensuse/vista.
>
> I don't understand what this means.  "When I
reboot after booting into
> the sysinstaller".  Are you talking about FreeBSD
sysinstall?
>
> Otherwise, any situation where the BIOS does not boot
your hard disks
> sounds more like a BIOS or system problem and
definitely has nothing to
> do with FreeBSD.
>
> --
> | 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 |
>
>
_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

re-flashed bios with latest version from dell's website. it
was the same
version but i re-flashed anyways and im still seeing the
same behavior where
i cant mount any disks to install or use the livefs.

On Thu, May 1, 2008 at 11:03 PM, Shaun Sabo
<shaun.bsdgmail.com> wrote:

> but then why does it not complain in freebsd 6.2,
linux, or windows but it
> does in 7.0? 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 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. 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.
>
> On Thu, May 1, 2008 at 10:56 PM, Jeremy Chadwick
<koitsufreebsd.org>
> wrote:
>
> > On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun
Sabo wrote:
> > > i tried both the 7-stable and 7.0-RELEASE
livefs disks and when i went
> > into
> > > fixit then to CD/DVD livefs it would ask me
for the livefs cd (which i
> > had
> > > in the drive and which i booted from) it
looks like i cant even mount
> > the
> > > image of the livefs disk from the cd-rom
drive.
> >
> > I'd recommend you burn one of the snapshot livefs
images to a CD and
> > boot it.  This is what I was implying the first
time around.  It should
> > give you a live FreeBSD system with common
utilities.
> >
> > > also iv noticed that when i
> > > reboot after booting into the sysinstaller
the bios gets about 2/3 of
> > the
> > > way booted and stops and i have to hold the
power and reboot to get
> > back
> > > into opensuse/vista.
> >
> > I don't understand what this means.  "When I
reboot after booting into
> > the sysinstaller".  Are you talking about
FreeBSD sysinstall?
> >
> > Otherwise, any situation where the BIOS does not
boot your hard disks
> > sounds more like a BIOS or system problem and
definitely has nothing to
> > do with FreeBSD.
> >
> > --
> > | 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 |
> >
> >
>
_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"

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 |

_______________________________________________
freebsd-hardwarefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hard
ware
To unsubscribe, send any mail to
"freebsd-hardware-unsubscribefreebsd.org"