Re: FreeBSD 7.0 nvidia-driver woes

2008-03-27 Thread Martyn Hare
On Thursday 27 March 2008 16:38:20 Darren Spruell wrote:
> On Tue, Mar 18, 2008 at 12:00 PM, Derek Ragona
>
> <[EMAIL PROTECTED]> wrote:
> >  Is it worthwhile to contact NVidia with bug reports? Does the FreeBSD
> >  community amount to much of a blip on their radar? Do we have a direct
> >  liaison in the community?
> >  Never hurts to file a bug report.  It seems to be in the nvidia older
> > driver, I've not heard of the problem with the driver for the current
> > cards.
>
> Four days ago I emailed a problem report to
> [EMAIL PROTECTED] I haven't heard a peep back. The NVIDIA
> support site is structured about like this:
>
> - If your NVIDIA card shipped with the computer direct from the OEM
> manufacturer, it's not our problem. Contact [Dell,HP,Compaq,etc] for
> resolution.
> - If your NVIDIA card was purchased retail, it's not our problem.
> Contact the card manufacturer [Gigabyte,MSI,etc.] for assistance.
>
> Does anyone know a contact in NVIDIA that would have any concern over
> (driver, etc.) issues like this?

Go to nvnews.net and moan a _lot_, NVIDIA staff notice things when people 
moan. Zander is an NVIDIA staffer and FreeBSD-lover on there he will likely 
help, he's very polite and seems to care for users and keep people reasonably 
up to date on things where he's allowed to.

Hope this helps,


Martyn Hare


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 7.0 nvidia-driver woes

2008-03-27 Thread Darren Spruell
On Tue, Mar 18, 2008 at 12:00 PM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
>  Is it worthwhile to contact NVidia with bug reports? Does the FreeBSD
>  community amount to much of a blip on their radar? Do we have a direct
>  liaison in the community?
>  Never hurts to file a bug report.  It seems to be in the nvidia older
> driver, I've not heard of the problem with the driver for the current cards.

Four days ago I emailed a problem report to
[EMAIL PROTECTED] I haven't heard a peep back. The NVIDIA
support site is structured about like this:

- If your NVIDIA card shipped with the computer direct from the OEM
manufacturer, it's not our problem. Contact [Dell,HP,Compaq,etc] for
resolution.
- If your NVIDIA card was purchased retail, it's not our problem.
Contact the card manufacturer [Gigabyte,MSI,etc.] for assistance.

Does anyone know a contact in NVIDIA that would have any concern over
(driver, etc.) issues like this?

-- 
Darren Spruell
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 7.0 nvidia-driver woes

2008-03-19 Thread Mark Ovens

Darren Spruell wrote:

During attempted startup and when using CTRL+ALT+BKSP to kill the
server the Xorg process drives CPU usage to 100%:

PID USERNAMETHR PRI NICE   SIZERES STATE  C   TIME   WCPU COMMAND
1203 root  1 1180 28168K 23960K CPU1   1   1:21 100.00% Xorg



I have exactly the same problem with an ATI card (radeonhd driver) 
except that the STATE of Xorg is *GIANT and recently I've seen CPU usage 
figure exceed 400% - yes *four* hundred!!


In my search for a solution I've found someone with the same problem 
with a Matrox card.


I've come to the conclusion that Xorg 7.3 is a crock - at least on 
FreeBSD - since I've never had some many problems under any previous 
version of Xorg, or XFree86. Is it possible to install Xorg 7.2 on 
FreeBSD 7.0?



FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2,
should be 1; fixing.



Hmm, I see this too (although I think it is freetype on my box, not 
misc) - any idea what it means?


Regards,

Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 7.0 nvidia-driver woes

2008-03-18 Thread Robert Huff

Darren Spruell writes:

>  Is it worthwhile to contact NVidia with bug reports? Does the
>  FreeBSD community amount to much of a blip on their radar? Do we
>  have a direct liaison in the community?

nVidia is perfectly aware their chips aren't supported.  It clains
to be willing to write - and maintain - drivers ...
... provided FreeBSD makes some chages in the kernel.  For more
information, google

+Christian +nVidia +"John Baldwin"

and click on the first result.  I am uqualified to opine on how
much work these changes would take, beyond this being Really Serious
Stuff(tm).  If it's really important, there's always starting a fund
to pay someone to do it.


Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 7.0 nvidia-driver woes

2008-03-18 Thread Derek Ragona

At 01:51 PM 3/18/2008, Darren Spruell wrote:

On Tue, Mar 18, 2008 at 11:07 AM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
>
>
>  At 11:58 AM 3/18/2008, Darren Spruell wrote:
>> Xorg + nvidia-driver woes...
>
>  I also have a server running FreeBSD 7.0 with xorg 7.3 and an older Nvidia
> card.  I first had trouble under 6.3 when I upgraded to xorg 7.3 from 7.1.
> The nvidia driver seems to cause an interupt storm that paralyzes the
> system.  It doesn't freeze, but is so busy it is useless.
>
>  It runs OK, not great, using the native xorg 7.3 driver which has no GL
> support.

Do you (anyone?) know if it is possible to use dual-monitor support in
the X.org nv driver? I don't need 3D acceleration necessarily, but
I've been of the impression that TwinView is needed for usable
dual-monitor capabilities. Someone (I thought) had mentioned earlier
that this driver didn't support Xinerama correctly (everything
stretched across two monitors).


I don't know which drivers support more than one monitor.



>  I don't have any idea what to do except wait for a new driver or xorg
> release that might fix this.

I notice it seems to be an unpopular sentiment in the FreeBSD
community, but as a user I feel it's worth mentioning it's upsetting
being at the mercy of a binary blob kernel driver. I've had pain from
6.3 also, and hoped that a clean installation of 7.0 might have
brought some good changes. Not the case, it seems.

Is it worthwhile to contact NVidia with bug reports? Does the FreeBSD
community amount to much of a blip on their radar? Do we have a direct
liaison in the community?


Never hurts to file a bug report.  It seems to be in the nvidia older 
driver, I've not heard of the problem with the driver for the current cards.


As an aside, you could always replace your video card for a newer one that 
is fully supported.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 7.0 nvidia-driver woes

2008-03-18 Thread Darren Spruell
On Tue, Mar 18, 2008 at 11:07 AM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
>
>
>  At 11:58 AM 3/18/2008, Darren Spruell wrote:
>> Xorg + nvidia-driver woes...
>
>  I also have a server running FreeBSD 7.0 with xorg 7.3 and an older Nvidia
> card.  I first had trouble under 6.3 when I upgraded to xorg 7.3 from 7.1.
> The nvidia driver seems to cause an interupt storm that paralyzes the
> system.  It doesn't freeze, but is so busy it is useless.
>
>  It runs OK, not great, using the native xorg 7.3 driver which has no GL
> support.

Do you (anyone?) know if it is possible to use dual-monitor support in
the X.org nv driver? I don't need 3D acceleration necessarily, but
I've been of the impression that TwinView is needed for usable
dual-monitor capabilities. Someone (I thought) had mentioned earlier
that this driver didn't support Xinerama correctly (everything
stretched across two monitors).

>  I don't have any idea what to do except wait for a new driver or xorg
> release that might fix this.

I notice it seems to be an unpopular sentiment in the FreeBSD
community, but as a user I feel it's worth mentioning it's upsetting
being at the mercy of a binary blob kernel driver. I've had pain from
6.3 also, and hoped that a clean installation of 7.0 might have
brought some good changes. Not the case, it seems.

Is it worthwhile to contact NVidia with bug reports? Does the FreeBSD
community amount to much of a blip on their radar? Do we have a direct
liaison in the community?

-- 
Darren Spruell
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 7.0 nvidia-driver woes

2008-03-18 Thread Derek Ragona

At 11:58 AM 3/18/2008, Darren Spruell wrote:

New installation of FreeBSD 7.0 i386, updated to 7.0-STABLE Mon Mar 17
18:04:24 MST 2008.

Attempting to use the nvidia-driver-169.12 package for:
NVIDIA(0): NVIDIA GPU Quadro FX 3450/4000 SDI (NV41GL) at PCI:7:0:0

When I start X using the Xorg 'nv' driver it starts successfully. Base
xorg.conf created using 'X -configure' and X started using 'X -config
/path/to/xorg.conf.new'. Using nvidia-xconfig to activate the 'nvidia'
driver results in the X server attempting to start up and choking; the
Nvidia logo appears after a few seconds and remains, and a pixelated
black and green screen remains; the X display never loads correctly.
During attempted startup and when using CTRL+ALT+BKSP to kill the
server the Xorg process drives CPU usage to 100%:

PID USERNAMETHR PRI NICE   SIZERES STATE  C   TIME   WCPU COMMAND
1203 root  1 1180 28168K 23960K CPU1   1   1:21 100.00% Xorg

Several errors are written to output during the failed X startup:

NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVRM: Xid (0007:00): 1, Channel 0001 Method  Data bfef0005
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)

$ kldstat
Id Refs AddressSize Name
 1   25 0xc040 9119f4   kernel
 21 0xc0d12000 8460 linprocfs.ko
 33 0xc0d1b000 28678linux.ko
 41 0xc0d44000 14324snd_hda.ko
 52 0xc0d59000 4a5acsound.ko
 61 0xc0da4000 22e40smbfs.ko
 73 0xc0dc7000 49b8 libiconv.ko
 83 0xc0dcc000 2c70 libmchain.ko
 91 0xc0dcf000 4d20 atapicam.ko
101 0xc0dd4000 80dc6c   nvidia.ko
111 0xc15e2000 6a2c4acpi.ko
121 0xc72e8000 3000 pflog.ko
131 0xc72eb000 33000pf.ko

$ kldstat -v
Id Refs AddressSize Name
 1   25 0xc040 9119f4   kernel
Contains modules:
...
422 hostb/agp_ali
423 hostb/agp_amd
424 hostb/agp_amd64
425 hostb/agp_ati
426 vgapci/agp_i810
427 hostb/agp_intel
428 hostb/agp_nvidia
429 hostb/agp_sis
430 hostb/agp_via
101 0xc0dd4000 80dc6c   nvidia.ko
Contains modules:
Id Name
13 pci/nvidia

$ dmesg | grep nvidia
nvidia0:  mem
0xdd00-0xddff,0xc000-0xcfff,0xde00-0xdeff irq
16 at device 0.0 on pci7
nvidia0: [GIANT-LOCKED]
nvidia0: [ITHREAD]

$ ls -l /dev/nvidia*
crw-rw-rw-  1 root  wheel0,  43 Mar 17 21:01 /dev/nvidia0
crw-rw-rw-  1 root  wheel0,  44 Mar 17 21:01 /dev/nvidiactl

$ ls -d1 /var/db/pkg/{xorg-*,nvidia-*}
/var/db/pkg/nvidia-driver-169.12
/var/db/pkg/nvidia-xconfig-1.0_2
/var/db/pkg/xorg-7.3_1
/var/db/pkg/xorg-apps-7.3
/var/db/pkg/xorg-docs-1.4,1
/var/db/pkg/xorg-drivers-7.3
/var/db/pkg/xorg-fonts-100dpi-7.3
/var/db/pkg/xorg-fonts-7.3
/var/db/pkg/xorg-fonts-75dpi-7.3
/var/db/pkg/xorg-fonts-cyrillic-7.3
/var/db/pkg/xorg-fonts-miscbitmaps-7.3
/var/db/pkg/xorg-fonts-truetype-7.3
/var/db/pkg/xorg-fonts-type1-7.3
/var/db/pkg/xorg-libraries-7.3_1
/var/db/pkg/xorg-protos-7.3
/var/db/pkg/xorg-server-1.4_4,1




Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #0: Mon Mar 17 18:04:24 MST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU   E5345  @ 2.33GHz (2327.52-MHz 
686-class CPU)

  Origin = "GenuineIntel"  Id = 0x6f7  Stepping = 7

Features=0xbfebfbff

Features2=0x4e3bd
  AMD Features=0x2010
  AMD Features2=0x1
  Cores per package: 4
real memory  = 3219169280 (3070 MB)
avail memory = 3136241664 (2990 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
ioapic0: Changing APIC ID to 8
ioapic1: Changing APIC ID to 9
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 24-47 on motherboard
kbd1 at kbdmux0
netsmb_dev: loaded
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
cpu0:  on acpi0
est0:  on cpu0
est: CPU supports Enhanced Sp

FreeBSD 7.0 nvidia-driver woes

2008-03-18 Thread Darren Spruell
New installation of FreeBSD 7.0 i386, updated to 7.0-STABLE Mon Mar 17
18:04:24 MST 2008.

Attempting to use the nvidia-driver-169.12 package for:
NVIDIA(0): NVIDIA GPU Quadro FX 3450/4000 SDI (NV41GL) at PCI:7:0:0

When I start X using the Xorg 'nv' driver it starts successfully. Base
xorg.conf created using 'X -configure' and X started using 'X -config
/path/to/xorg.conf.new'. Using nvidia-xconfig to activate the 'nvidia'
driver results in the X server attempting to start up and choking; the
Nvidia logo appears after a few seconds and remains, and a pixelated
black and green screen remains; the X display never loads correctly.
During attempted startup and when using CTRL+ALT+BKSP to kill the
server the Xorg process drives CPU usage to 100%:

PID USERNAMETHR PRI NICE   SIZERES STATE  C   TIME   WCPU COMMAND
1203 root  1 1180 28168K 23960K CPU1   1   1:21 100.00% Xorg

Several errors are written to output during the failed X startup:

NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVRM: Xid (0007:00): 1, Channel 0001 Method  Data bfef0005
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)
NVIDIA: failed to set MTRR 0xc000, 0M (write-combining)

$ kldstat
Id Refs AddressSize Name
 1   25 0xc040 9119f4   kernel
 21 0xc0d12000 8460 linprocfs.ko
 33 0xc0d1b000 28678linux.ko
 41 0xc0d44000 14324snd_hda.ko
 52 0xc0d59000 4a5acsound.ko
 61 0xc0da4000 22e40smbfs.ko
 73 0xc0dc7000 49b8 libiconv.ko
 83 0xc0dcc000 2c70 libmchain.ko
 91 0xc0dcf000 4d20 atapicam.ko
101 0xc0dd4000 80dc6c   nvidia.ko
111 0xc15e2000 6a2c4acpi.ko
121 0xc72e8000 3000 pflog.ko
131 0xc72eb000 33000pf.ko

$ kldstat -v
Id Refs AddressSize Name
 1   25 0xc040 9119f4   kernel
Contains modules:
...
422 hostb/agp_ali
423 hostb/agp_amd
424 hostb/agp_amd64
425 hostb/agp_ati
426 vgapci/agp_i810
427 hostb/agp_intel
428 hostb/agp_nvidia
429 hostb/agp_sis
430 hostb/agp_via
101 0xc0dd4000 80dc6c   nvidia.ko
Contains modules:
Id Name
13 pci/nvidia

$ dmesg | grep nvidia
nvidia0:  mem
0xdd00-0xddff,0xc000-0xcfff,0xde00-0xdeff irq
16 at device 0.0 on pci7
nvidia0: [GIANT-LOCKED]
nvidia0: [ITHREAD]

$ ls -l /dev/nvidia*
crw-rw-rw-  1 root  wheel0,  43 Mar 17 21:01 /dev/nvidia0
crw-rw-rw-  1 root  wheel0,  44 Mar 17 21:01 /dev/nvidiactl

$ ls -d1 /var/db/pkg/{xorg-*,nvidia-*}
/var/db/pkg/nvidia-driver-169.12
/var/db/pkg/nvidia-xconfig-1.0_2
/var/db/pkg/xorg-7.3_1
/var/db/pkg/xorg-apps-7.3
/var/db/pkg/xorg-docs-1.4,1
/var/db/pkg/xorg-drivers-7.3
/var/db/pkg/xorg-fonts-100dpi-7.3
/var/db/pkg/xorg-fonts-7.3
/var/db/pkg/xorg-fonts-75dpi-7.3
/var/db/pkg/xorg-fonts-cyrillic-7.3
/var/db/pkg/xorg-fonts-miscbitmaps-7.3
/var/db/pkg/xorg-fonts-truetype-7.3
/var/db/pkg/xorg-fonts-type1-7.3
/var/db/pkg/xorg-libraries-7.3_1
/var/db/pkg/xorg-protos-7.3
/var/db/pkg/xorg-server-1.4_4,1




Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #0: Mon Mar 17 18:04:24 MST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU   E5345  @ 2.33GHz (2327.52-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6f7  Stepping = 7
  
Features=0xbfebfbff
  Features2=0x4e3bd
  AMD Features=0x2010
  AMD Features2=0x1
  Cores per package: 4
real memory  = 3219169280 (3070 MB)
avail memory = 3136241664 (2990 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
ioapic0: Changing APIC ID to 8
ioapic1: Changing APIC ID to 9
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 24-47 on motherboard
kbd1 at kbdmux0
netsmb_dev: loaded
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
cpu0:  on acpi0
est0:  on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendo