Re: A few 5.0-Release questions...

2003-03-05 Thread John Wilson
--- Chris Shenton <[EMAIL PROTECTED]> wrote:
> FWIW, I had absolutely no trouble booting and
> installing 5.0-R on my 600SC, with the DELL-supplied
CERC
> RAID card (amr device recognized it, but it drives
4x
> ATA disks rather than SCSI), and an Intel gigabit
> ether card.  Got X11 working on it rather easily
> too.  I don't have any other drives (than the
supplied IDE
> CD) in the box.

The only trouble that I've experienced was with adding
a new video card, an ATI All-In-Wonder VE (Radeon
7500, PCI version).  When the card is not installed,
and I'm using the integrated RageXL video, all works
just great.  However, once a new PCI video card is
installed, I get NMI errors on boot, with a system
hang.

I've tried a few different things to try and resolve
the issue; removing 'options EISA' from the kernel,
and removing 'device agp' from the kernel.  I've
checked the mainboard for jumpers to fully disable the
integrated video; there are none.

Thus far, the only way I can get FreeBSD-5.0 to boot
without incident was to add,
'hw.pci.enable_io_modes=0' to /boot/device.hints. 
Once I do that, no more NMI errors.

I just hope and pray this option remains with FreeBSD
for a long time to come so I can continue to use this
ATI AIW card.  X with the integrated RageXL sucks. :p

- John Wilson <[EMAIL PROTECTED]>

__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message


Re: A few 5.0-Release questions...

2003-03-05 Thread Chris Shenton
John Wilson <[EMAIL PROTECTED]> writes:

> --- Scott Long <[EMAIL PROTECTED]> wrote:
> [Dell PowerEdge]
> > What model?  There are quite a few PowerEdges out
> 
> It's a 600SC - P4 1.8 - Perc3/SC

FWIW, I had absolutely no trouble booting and installing 5.0-R on my
600SC, with the DELL-supplied CERC RAID card (amr device recognized
it, but it drives 4x ATA disks rather than SCSI), and an Intel gigabit
ether card.  Got X11 working on it rather easily too.  
I don't have any other drives (than the supplied IDE CD) in the box.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message


Re: A few 5.0-Release questions...

2003-03-04 Thread John Wilson
--- Scott Long <[EMAIL PROTECTED]> wrote:
[Dell PowerEdge]
> What model?  There are quite a few PowerEdges out

It's a 600SC - P4 1.8 - Perc3/SC

Since new, I've added a Plextor CD-RW (IDE), Lite-On
DVD-ROM (IDE), and an ATI All-In-Wonder VE (7500,
PCI).

> > These machines come with integrated video, an ATI
[Complications with integrated RageXL and PCI version
of the ATI AIW VE...  NMI halts]

> As a wild guess, what happens when you remove the
> EISA device from the kernel?

I tried this as well.  Unfortunately, removing the
EISA device did nothing to relieve the problem with
the NMI.  The only thing that cleared it up was adding
'hw.pci.enable_io_modes=0' in /boot/device.hints.

This was the case, at least, with 5.0-RELEASE.  I've
yet to see what happens with -CURRENT.  Perhaps I'll
try and cvsup -CURRENT, remove
'hw.pci.enable_io_modes=0', and see what happens.

> There have been problems in the past with ATAPI/IDE
> drives that claim DMA capabilities but instead
corrupt data
> and/or cause panics.  Forcing everything to PIO is
the
> easiest way to achieve maximum compatibility.  The
ata manual
> page describes what to put into /boot/loader.conf to
> force them back using DMA.

I pulled these two drives from a WinXP machine, and
based on the transfer method reported in XP, it was
using DMA.  No stability issues were noted, at least
in regard to XP.  I've been running them under 5.0 now
for a few days, burned a few CD's and played a few
DVD's without stability issues either -- thankfully.

I'll check out the above referenced manual page and
make the suggested changes.  Thank you for the tip.

[About permanently disabling the integrated video]
> Does the motherboard have a jumper that will disable
> it?

Unfortunately, no.  I've even contacted Dell regarding
this as I could find no information in the
documentation provided with the system.  They simply
stated that when another video card is installed, the
integrated video is disabled.  They also mentioned
that this type of configuration "is not supported." 
I've looked for jumpers on the motherboard itself and
only found jumpers for clearing the BIOS password...
nothing else.
 
Thank you once again, Scott, for your help.  It was
very much appreciated.

- John Wilson <[EMAIL PROTECTED]>

__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message


Re: A few 5.0-Release questions...

2003-03-04 Thread Scott Long
John Wilson wrote:
Good day,

After spending quite some time trying to get
5.0-RELEASE installed on a Dell PowerEdge machine, it
seems that all is now working quite well.  Being that
these machines are somewhat common, I'll share what
was halting my installation.
What model?  There are quite a few PowerEdges out there.  I
installed 5.0 (actually, I built the official 5.0 release)
on a PowerEdge.
These machines come with integrated video, an ATI
RageXL, which is rather useless for anything other
than console mode. I installed an ATI All- In-Wonder
VE so that I could get somewhat decent performance out
of X. The problem manifested when the kernel probed
the machines hardware, causing an "NMI ISA 30, EISA
ff", and locking up the machine solid. After I began
pulling memory and expansion cards from the system,
the error went away when I removed the ATI AIW card. I
reinstalled the card and attempted to find how to
correct this. My only solution to this issue was to
interrupt the boot process and use the following
command:
set hw.pci.enable_io_modes = 0

This prevented any further halts.
As a wild guess, what happenes when you remove the EISA
device from the kernel?
My first question is as follows: is /boot/device.hints
the most proper place to stick this? Also, are there
any other possible solutions to this issue?
/boot/loader.conf is the best place for this.

My main drives are SCSI, and I have one CD-RW and one
DVD-R on the secondary IDE controller. The kernel
detects the drives just fine, but defaults them both
down to PIO4. The drives are fully UDMA2 capable. I am
able to set the drives to use UDMA2 via atacontrol
without issue.  However, how would one make this more
permanent, such that I wouldn't have to use atacontrol
everytime I boot the machine?
There have been problems in the past with ATAPI/IDE drives
that claim DMA capabilities but instead corrupt data and/or
cause panics.  Forcing everything to PIO is the easiest way
to achieve maximum compatibility.  The ata manual page
describes what to put into /boot/loader.conf to force them
back using DMA.
Back to the topic of video; is there _any_ way to
permanently disable, or at least prevent FreeBSD from
detecting the integrated video on the motherboard?
There is nothing in the machines BIOS that would allow
this. This would just be "nice" to do, as X works just
fine, but it still sticks an entry into the
XFree86Config file for the integrated chip.
Does the motherboard have a jumper that will disable it?

And finally...

Where can one obtain a complete list of allowed hints
for use in /boot/device.hints? I tried searching
around the FBSD site as well as the handbook and found
no listing, other than a line here and a line there.
This has been desired for a long time, yes.  There have
been periodic pushes to do this, but they quickly loose
steam or become outdated.
Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message


A few 5.0-Release questions...

2003-03-04 Thread John Wilson
Good day,

After spending quite some time trying to get
5.0-RELEASE installed on a Dell PowerEdge machine, it
seems that all is now working quite well.  Being that
these machines are somewhat common, I'll share what
was halting my installation.

These machines come with integrated video, an ATI
RageXL, which is rather useless for anything other
than console mode. I installed an ATI All- In-Wonder
VE so that I could get somewhat decent performance out
of X. The problem manifested when the kernel probed
the machines hardware, causing an "NMI ISA 30, EISA
ff", and locking up the machine solid. After I began
pulling memory and expansion cards from the system,
the error went away when I removed the ATI AIW card. I
reinstalled the card and attempted to find how to
correct this. My only solution to this issue was to
interrupt the boot process and use the following
command:

set hw.pci.enable_io_modes = 0

This prevented any further halts.

My first question is as follows: is /boot/device.hints
the most proper place to stick this? Also, are there
any other possible solutions to this issue?

My main drives are SCSI, and I have one CD-RW and one
DVD-R on the secondary IDE controller. The kernel
detects the drives just fine, but defaults them both
down to PIO4. The drives are fully UDMA2 capable. I am
able to set the drives to use UDMA2 via atacontrol
without issue.  However, how would one make this more
permanent, such that I wouldn't have to use atacontrol
everytime I boot the machine?

Back to the topic of video; is there _any_ way to
permanently disable, or at least prevent FreeBSD from
detecting the integrated video on the motherboard?
There is nothing in the machines BIOS that would allow
this. This would just be "nice" to do, as X works just
fine, but it still sticks an entry into the
XFree86Config file for the integrated chip.

And finally...

Where can one obtain a complete list of allowed hints
for use in /boot/device.hints? I tried searching
around the FBSD site as well as the handbook and found
no listing, other than a line here and a line there.

Thank you all very much for your help, and have a
wonderful day.

- John Wilson [EMAIL PROTECTED]

__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message