Installing fusefs-ntfs and nvidia-drivers fails

[Neil M. Stewart]

Hi All,

I am new to FreeBSD, and I am having an issue installing fusefs-ntfs and 
nvidia-driver.  The error messages are shown below. Any idea what's 
going on here? Thanks in advance.



===  Installing for fusefs-ntfs-2012.1.15
===   fusefs-ntfs-2012.1.15 depends on file: /usr/local/modules/fuse.ko 
- not found
===Verifying install for /usr/local/modules/fuse.ko in 
/usr/ports/sysutils/fusefs-kmod

===  Building for fusefs-kmod-0.3.9.p1.20080208_11
=== fuse_module (all)
/usr/src/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk
/usr/src/sys/conf/kmod.mk, line 112: Malformed conditional 
(${COMPILER_TYPE} != clang)

/usr/src/sys/conf/kmod.mk, line 116: if-less endif
/usr/src/sys/conf/kern.mk, line 18: Malformed conditional 
(${COMPILER_TYPE} == clang)

/usr/src/sys/conf/kern.mk, line 33: if-less endif
/usr/src/sys/conf/kern.mk, line 103: Malformed conditional 
(${COMPILER_TYPE} == clang)

/usr/src/sys/conf/kern.mk, line 109: if-less endif
make: fatal errors encountered -- cannot continue


==  Building for nvidia-driver-304.60
=== src (all)
/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk
/sys/conf/kmod.mk, line 112: Malformed conditional (${COMPILER_TYPE} 
!= clang)

/sys/conf/kmod.mk, line 116: if-less endif
/sys/conf/kern.mk, line 18: Malformed conditional (${COMPILER_TYPE} == 
clang)

/sys/conf/kern.mk, line 33: if-less endif
/sys/conf/kern.mk, line 103: Malformed conditional (${COMPILER_TYPE} 
== clang)

/sys/conf/kern.mk, line 109: if-less endif
make: fatal errors encountered -- cannot continue

-Neil Stewart
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Installing fusefs-ntfs and nvidia-drivers fails

[Arthur Chance]

On 11/08/12 13:30, Neil M. Stewart wrote:

Hi All,

I am new to FreeBSD, and I am having an issue installing fusefs-ntfs and
nvidia-driver.  The error messages are shown below. Any idea what's
going on here? Thanks in advance.


===  Installing for fusefs-ntfs-2012.1.15
===   fusefs-ntfs-2012.1.15 depends on file: /usr/local/modules/fuse.ko
- not found
===Verifying install for /usr/local/modules/fuse.ko in
/usr/ports/sysutils/fusefs-kmod
===  Building for fusefs-kmod-0.3.9.p1.20080208_11
=== fuse_module (all)
/usr/src/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk
/usr/src/sys/conf/kmod.mk, line 112: Malformed conditional
(${COMPILER_TYPE} != clang)
/usr/src/sys/conf/kmod.mk, line 116: if-less endif
/usr/src/sys/conf/kern.mk, line 18: Malformed conditional
(${COMPILER_TYPE} == clang)
/usr/src/sys/conf/kern.mk, line 33: if-less endif
/usr/src/sys/conf/kern.mk, line 103: Malformed conditional
(${COMPILER_TYPE} == clang)
/usr/src/sys/conf/kern.mk, line 109: if-less endif
make: fatal errors encountered -- cannot continue


==  Building for nvidia-driver-304.60
=== src (all)
/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk
/sys/conf/kmod.mk, line 112: Malformed conditional (${COMPILER_TYPE}
!= clang)
/sys/conf/kmod.mk, line 116: if-less endif
/sys/conf/kern.mk, line 18: Malformed conditional (${COMPILER_TYPE} ==
clang)
/sys/conf/kern.mk, line 33: if-less endif
/sys/conf/kern.mk, line 103: Malformed conditional (${COMPILER_TYPE}
== clang)
/sys/conf/kern.mk, line 109: if-less endif
make: fatal errors encountered -- cannot continue


In both cases you've got the message

 /usr/src/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk

(or equivalent as /sys - usr/src)

I've looked at my version of the file (under REL-9.0) and there's no 
mention of bsd.compiler.mk (or ${COMPILER_TYPE}). Please show us what 
you get if you type uname -a so we know what you've installed.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Installing fusefs-ntfs and nvidia-drivers fails

[Neil M. Stewart]

Hi Arthur,

Thanks for your response. The installation works now. It turns out that 
I was working with the wrong version of the source tree.


Regards,
Neil Stewart

On 11/8/12 11:33 AM, Arthur Chance wrote:

On 11/08/12 13:30, Neil M. Stewart wrote:

Hi All,

I am new to FreeBSD, and I am having an issue installing fusefs-ntfs and
nvidia-driver.  The error messages are shown below. Any idea what's
going on here? Thanks in advance.


===  Installing for fusefs-ntfs-2012.1.15
===   fusefs-ntfs-2012.1.15 depends on file: /usr/local/modules/fuse.ko
- not found
===Verifying install for /usr/local/modules/fuse.ko in
/usr/ports/sysutils/fusefs-kmod
===  Building for fusefs-kmod-0.3.9.p1.20080208_11
=== fuse_module (all)
/usr/src/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk
/usr/src/sys/conf/kmod.mk, line 112: Malformed conditional
(${COMPILER_TYPE} != clang)
/usr/src/sys/conf/kmod.mk, line 116: if-less endif
/usr/src/sys/conf/kern.mk, line 18: Malformed conditional
(${COMPILER_TYPE} == clang)
/usr/src/sys/conf/kern.mk, line 33: if-less endif
/usr/src/sys/conf/kern.mk, line 103: Malformed conditional
(${COMPILER_TYPE} == clang)
/usr/src/sys/conf/kern.mk, line 109: if-less endif
make: fatal errors encountered -- cannot continue


==  Building for nvidia-driver-304.60
=== src (all)
/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk
/sys/conf/kmod.mk, line 112: Malformed conditional (${COMPILER_TYPE}
!= clang)
/sys/conf/kmod.mk, line 116: if-less endif
/sys/conf/kern.mk, line 18: Malformed conditional (${COMPILER_TYPE} ==
clang)
/sys/conf/kern.mk, line 33: if-less endif
/sys/conf/kern.mk, line 103: Malformed conditional (${COMPILER_TYPE}
== clang)
/sys/conf/kern.mk, line 109: if-less endif
make: fatal errors encountered -- cannot continue


In both cases you've got the message

 /usr/src/sys/conf/kmod.mk, line 76: Could not find bsd.compiler.mk

(or equivalent as /sys - usr/src)

I've looked at my version of the file (under REL-9.0) and there's no 
mention of bsd.compiler.mk (or ${COMPILER_TYPE}). Please show us what 
you get if you type uname -a so we know what you've installed.







___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Daniel C. Dowse]

On Tue, 3 Nov 2009 13:55:34 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 I'm not able to use the glx settings on my computer.
 RGB comes back as a double buffer error.
 

Hi,

sorry but with that kind of questioning you won`t get any response,
that includes your other posts as well. 
you should all ways try to describe the problem more specified.
you should post your configs (/etc./X11/xorg.conf) and hardware specs
(dmesg) and os release version( uname -a ) ,and the driver version
you have installed, too.

 
 
   
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


greets 

daniel

-- 
[ The only reality is virtual ] 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Super Biscuit]

The reason for multiple posts and the titles is because The original post was 
considered spam by the freebsd-questions mailing list and webmaster. It had all 
of the relevant information in it.
Next time you may want ask me why I do something before making an uninformed 
and asinine response.

Here is the information you asked for: %uname -a
FreeBSD pocket-peoples.xxx.xxx.xxx.xxx 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri 
May  1 08:49:13 UTC 2009 
r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386


--- On Wed, 11/4/09, Daniel C. Dowse dcdo...@gmx.net wrote:

From: Daniel C. Dowse dcdo...@gmx.net
Subject: Re: need help with nvidia drivers
To: Super Biscuit super_bisq...@yahoo.com
Cc: freebsd-questions@freebsd.org
Date: Wednesday, November 4, 2009, 9:52 AM

On Tue, 3 Nov 2009 13:55:34 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 I'm not able to use the glx settings on my computer.
 RGB comes back as a double buffer error.
 

Hi,

sorry but with that kind of questioning you won`t get any response,
that includes your other posts as well. 
you should all ways try to describe the problem more specified.
you should post your configs (/etc./X11/xorg.conf) and hardware specs
(dmesg) and os release version( uname -a ) ,and the driver version
you have installed, too.

 
 
       
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


greets 

daniel

-- 
[ The only reality is virtual ]          



  

xorg.conf
Description: Binary data
Copyright (c) 1992-2009 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.2-RELEASE #0: Fri May  1 08:49:13 UTC 2009
r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
module_register: module dc/miibus already exists!
Module dc/miibus failed to register: 17
module_register: module pci/dc already exists!
Module pci/dc failed to register: 17
module_register: module cardbus/dc already exists!
Module cardbus/dc failed to register: 17
module_register: module miibus/dcphy already exists!
Module miibus/dcphy failed to register: 17
module_register: module miibus/pnphy already exists!
Module miibus/pnphy failed to register: 17
module_register: module uhub/ums already exists!
Module uhub/ums failed to register: 17
module_register: module rl/miibus already exists!
Module rl/miibus failed to register: 17
module_register: module cardbus/rl already exists!
Module cardbus/rl failed to register: 17
module_register: module pci/rl already exists!
Module pci/rl failed to register: 17
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Sempron(tm) Processor 3400+ (1989.82-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x20ff2  Stepping = 2
  
Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
  Features2=0x1SSE3
  AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!
  AMD Features2=0x1LAHF
real memory  = 1877934080 (1790 MB)
avail memory = 1818591232 (1734 MB)
ACPI APIC Table: HP-CPC AWRDACPI
ioapic0 Version 2.1 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: HP-CPC AWRDACPI on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 6fdf (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 32-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: PCI-PCI bridge at device 2.0 on pci0
pci1: PCI bus on pcib1
vgapci0: VGA-compatible display port 0xef00-0xef7f mem 
0xfa00-0xfaff,0xd000-0xdfff,0xf800-0xf9ff irq 18 at 
device 0.0 on pci1
nvidia0: GeForce 8400 GS on vgapci0
vgapci0: child nvidia0 requested pci_enable_busmaster
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: child nvidia0 requested pci_enable_io
nvidia0: [GIANT-LOCKED]
nvidia0: [ITHREAD]
atapci0: ATI IXP400 SATA150 controller port 
0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 
0xfe02f000-0xfe02f1ff irq 22 at device 18.0 on pci0
atapci0: [ITHREAD]
ata2: ATA channel 0 on atapci0
ata2: [ITHREAD]
ata3: ATA channel 1 on atapci0
ata3: [ITHREAD]
ohci0: ATI SB400 USB Controller mem 0xfe02e000-0xfe02efff at device 19.0 on 
pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: ATI SB400 USB Controller on ohci0
usb0: USB revision 1.0
uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
uhub0: 4 ports with 4 removable, self powered
ohci1: ATI SB400 USB Controller mem 0xfe02d000-0xfe02dfff at device 19.1 on 
pci0
ohci1: [GIANT-LOCKED]
ohci1

Re: need help with nvidia drivers

[Daniel C. Dowse]

Hi 

in xorg.conf

Section Module
Load   dbe
Load   extmod
Load   type1
Load   freetype
Load   glx
Load   dri -- REMOVE THIS !
 
Have you checked out this link before ?
http://us.download.nvidia.com/freebsd/173.14.12/README/index.html


On Wed, 4 Nov 2009 04:29:14 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 The reason for multiple posts and the titles is because The original post was 
 considered spam by the freebsd-questions mailing list and webmaster. It had 
 all of the relevant information in it.
 Next time you may want ask me why I do something before making an uninformed 
 and asinine response.
 
 Here is the information you asked for: %uname -a
 FreeBSD pocket-peoples.xxx.xxx.xxx.xxx 7.2-RELEASE FreeBSD 7.2-RELEASE #0: 
 Fri May  1 08:49:13 UTC 2009 
 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
 
 
 --- On Wed, 11/4/09, Daniel C. Dowse dcdo...@gmx.net wrote:
 
 From: Daniel C. Dowse dcdo...@gmx.net
 Subject: Re: need help with nvidia drivers
 To: Super Biscuit super_bisq...@yahoo.com
 Cc: freebsd-questions@freebsd.org
 Date: Wednesday, November 4, 2009, 9:52 AM
 
 On Tue, 3 Nov 2009 13:55:34 -0800 (PST)
 Super Biscuit super_bisq...@yahoo.com wrote:
 
  I'm not able to use the glx settings on my computer.
  RGB comes back as a double buffer error.
  

best regards

daniel

-- 
[ The only reality is virtual ] 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Super Biscuit]

The following files do not exist on my system
/compat/linux/sbin/modprobe
/dev/nvidia1
/dev/nvidia2
%nvidia-settings --glxinfo
GLX Information for pocket-peoples.net.:0.0:
Segmentation fault


--- On Wed, 11/4/09, Daniel C. Dowse dcdo...@gmx.net wrote:

From: Daniel C. Dowse dcdo...@gmx.net
Subject: Re: need help with nvidia drivers
To: Super Biscuit super_bisq...@yahoo.com
Cc: freebsd-questions@freebsd.org
Date: Wednesday, November 4, 2009, 1:50 PM


Hi 

in xorg.conf

Section Module
    Load           dbe
    Load           extmod
    Load           type1
    Load           freetype
    Load           glx
    Load           dri -- REMOVE THIS !
 
Have you checked out this link before ?
http://us.download.nvidia.com/freebsd/173.14.12/README/index.html


On Wed, 4 Nov 2009 04:29:14 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 The reason for multiple posts and the titles is because The original post was 
 considered spam by the freebsd-questions mailing list and webmaster. It had 
 all of the relevant information in it.
 Next time you may want ask me why I do something before making an uninformed 
 and asinine response.
 
 Here is the information you asked for: %uname -a
 FreeBSD pocket-peoples.xxx.xxx.xxx.xxx 7.2-RELEASE FreeBSD 7.2-RELEASE #0: 
 Fri May  1 08:49:13 UTC 2009 
 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
 
 
 --- On Wed, 11/4/09, Daniel C. Dowse dcdo...@gmx.net wrote:
 
 From: Daniel C. Dowse dcdo...@gmx.net
 Subject: Re: need help with nvidia drivers
 To: Super Biscuit super_bisq...@yahoo.com
 Cc: freebsd-questions@freebsd.org
 Date: Wednesday, November 4, 2009, 9:52 AM
 
 On Tue, 3 Nov 2009 13:55:34 -0800 (PST)
 Super Biscuit super_bisq...@yahoo.com wrote:
 
  I'm not able to use the glx settings on my computer.
  RGB comes back as a double buffer error.
  

best regards

daniel

-- 
[ The only reality is virtual ]          




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Super Biscuit]

I downloaded and installed the driver from nvidia with better results.
Now, I have a problem of a broken screen and a workable area of 320x240.
I added the the Modes to the xorg.conf file with no change in results.


--- On Wed, 11/4/09, Daniel C. Dowse dcdo...@gmx.net wrote:

From: Daniel C. Dowse dcdo...@gmx.net
Subject: Re: need help with nvidia drivers
To: Super Biscuit super_bisq...@yahoo.com
Cc: freebsd-questions@freebsd.org
Date: Wednesday, November 4, 2009, 1:50 PM


Hi 

in xorg.conf

Section Module
    Load           dbe
    Load           extmod
    Load           type1
    Load           freetype
    Load           glx
    Load           dri -- REMOVE THIS !
 
Have you checked out this link before ?
http://us.download.nvidia.com/freebsd/173.14.12/README/index.html


On Wed, 4 Nov 2009 04:29:14 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 The reason for multiple posts and the titles is because The original post was 
 considered spam by the freebsd-questions mailing list and webmaster. It had 
 all of the relevant information in it.
 Next time you may want ask me why I do something before making an uninformed 
 and asinine response.
 
 Here is the information you asked for: %uname -a
 FreeBSD pocket-peoples.xxx.xxx.xxx.xxx 7.2-RELEASE FreeBSD 7.2-RELEASE #0: 
 Fri May  1 08:49:13 UTC 2009 
 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
 
 
 --- On Wed, 11/4/09, Daniel C. Dowse dcdo...@gmx.net wrote:
 
 From: Daniel C. Dowse dcdo...@gmx.net
 Subject: Re: need help with nvidia drivers
 To: Super Biscuit super_bisq...@yahoo.com
 Cc: freebsd-questions@freebsd.org
 Date: Wednesday, November 4, 2009, 9:52 AM
 
 On Tue, 3 Nov 2009 13:55:34 -0800 (PST)
 Super Biscuit super_bisq...@yahoo.com wrote:
 
  I'm not able to use the glx settings on my computer.
  RGB comes back as a double buffer error.
  

best regards

daniel

-- 
[ The only reality is virtual ]          




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Daniel C. Dowse]

On Wed, 4 Nov 2009 15:22:42 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 I downloaded and installed the driver from nvidia with better results.
 Now, I have a problem of a broken screen and a workable area of 320x240.
 I added the the Modes to the xorg.conf file with no change in results.
 
 

Have you run nvidia-xconfig ? 


best regards

daniel 
-- 
[ The only reality is virtual ] 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Super Biscuit]

Yes, I did.
I'm thinking that it may be the metamode option.

--- On Thu, 11/5/09, Daniel C. Dowse dcdo...@gmx.net wrote:

From: Daniel C. Dowse dcdo...@gmx.net
Subject: Re: need help with nvidia drivers
To: Super Biscuit super_bisq...@yahoo.com
Cc: freebsd-questions@freebsd.org
Date: Thursday, November 5, 2009, 12:01 AM

On Wed, 4 Nov 2009 15:22:42 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 I downloaded and installed the driver from nvidia with better results.
 Now, I have a problem of a broken screen and a workable area of 320x240.
 I added the the Modes to the xorg.conf file with no change in results.
 
 

Have you run nvidia-xconfig ? 


best regards

daniel 
-- 
[ The only reality is virtual ]          




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Daniel C. Dowse]

On Wed, 4 Nov 2009 16:15:46 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 Yes, I did.
 I'm thinking that it may be the metamode option.
 
 --- On Thu, 11/5/09, Daniel C. Dowse dcdo...@gmx.net wrote:
 

Hi,

well i don`t know, i don`t have any modes specified in xorg.conf here
is what my xorg.conf looks like with geforce fx5500 . 
Sorry but i think i can`t help you any further :-( , maybe you can
join #nvidia on irc.freenode and ask there or use some freebsd
related irc channel on any irc network you may like.

 
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeis...@builder65)  Thu Jul 17 18:26:36 
PDT 2008

[snip]

Section Monitor
Identifier Monitor0
VendorName Unknown
ModelName  Unknown
HorizSync   30.0 - 110.0
VertRefresh 50.0 - 150.0
Option DPMS
EndSection

Section Device
Identifier Device0
Driver nvidia
VendorName NVIDIA Corporation
Option   NvAGP 1
Option   Coolbits 1
Option TripleBuffer True
Option RenderAccel  True
Option AllowGLXWithComposite True
Option EnableAGPSBA 1
Option EnableAGPFW  0
Option   GLX1
EndSection

Section Screen
Identifier Screen0
Device Device0
MonitorMonitor0
DefaultDepth24
Option PixmapCacheSize 20
Option AllowSHMPixmaps 0
SubSection Display
EndSubSection
EndSection


P.S.

i noticed that your quoting is not very good, try to tell your
mail-user-agent to quote a lil` better ;-)

bye 

daniel

-- 
[ The only reality is virtual ] 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: need help with nvidia drivers

[Super Biscuit]

I fixed by using the following method.
Opened the properties and set the screen resolution.
Opened firefox and downloaded the old xorg.conf I sent you earlier.
Logged out and then back in as root.
Used kate to copy the screen layout from the downloaded file to the active 
xorg.conf file.
Saved and restarted x.

Believe it or not, I did need you to walk me through the process. There were 
quite a few things I wasn't able to notice on my own.
Thanks a lot and all that.

--- On Thu, 11/5/09, Daniel C. Dowse dcdo...@gmx.net wrote:

From: Daniel C. Dowse dcdo...@gmx.net
Subject: Re: need help with nvidia drivers
To: Super Biscuit super_bisq...@yahoo.com
Cc: freebsd-questions@freebsd.org
Date: Thursday, November 5, 2009, 12:39 AM

On Wed, 4 Nov 2009 16:15:46 -0800 (PST)
Super Biscuit super_bisq...@yahoo.com wrote:

 Yes, I did.
 I'm thinking that it may be the metamode option.
 
 --- On Thu, 11/5/09, Daniel C. Dowse dcdo...@gmx.net wrote:
 

Hi,

well i don`t know, i don`t have any modes specified in xorg.conf here
is what my xorg.conf looks like with geforce fx5500 . 
Sorry but i think i can`t help you any further :-( , maybe you can
join #nvidia on irc.freenode and ask there or use some freebsd
related irc channel on any irc network you may like.

 
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeis...@builder65)  Thu Jul 17 18:26:36 
PDT 2008

[snip]

Section Monitor
    Identifier     Monitor0
    VendorName     Unknown
    ModelName      Unknown
    HorizSync       30.0 - 110.0
    VertRefresh     50.0 - 150.0
    Option         DPMS
EndSection

Section Device
    Identifier     Device0
    Driver         nvidia
    VendorName     NVIDIA Corporation
    Option        NvAGP 1
    Option         Coolbits 1
    Option         TripleBuffer True
    Option         RenderAccel  True
    Option         AllowGLXWithComposite True
    Option         EnableAGPSBA 1
    Option        EnableAGPFW  0
    Option        GLX      1
EndSection

Section Screen
    Identifier     Screen0
    Device         Device0
    Monitor        Monitor0
    DefaultDepth    24
    Option         PixmapCacheSize 20
    Option         AllowSHMPixmaps 0
    SubSection     Display    
    EndSubSection
EndSection


P.S.

i noticed that your quoting is not very good, try to tell your
mail-user-agent to quote a lil` better ;-)

bye 

daniel

-- 
[ The only reality is virtual ]          




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

need help with nvidia drivers

[Super Biscuit]

I'm not able to use the glx settings on my computer.
RGB comes back as a double buffer error.



  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

nvidia-drivers crash computer on X start

[Anders Holmström]

I'm having something of a problem. X.org will not start whenever I
load the drivers installed from the latest nvidia-drivers port. The
error also happens with the older versions of said drivers. The error
doesn't occur with the normal nv drivers.

What happens:

1) $ startx
2) The normal startup stuff flickers by on screen. I'm not sure
exactly what it says as the screen goes black to load up X in less
than a second (it always does this).
3) It then switches display mode or something like that. It goes from
proper this screen is currently not showing anything at all-black to
this screen is on and is rendering black pixels-black. It might
sound strange but I can't describe it any better. The black gets a
different hue which isn't displayed when I start X with the default nv
drivers. Not sure if this is relevant or not.
4) Everything just locks up. The new black stays. I can't switch to
another terminal with CTRL+ALT+F#, I can't CTRL+ALT+BACKSPACE nor
CTRL+ALT+DELETE. I was playing music with the CLI player herrie once
and it repeated the same millisecond of sound over and over and over.
A proper lock-up.
5) I hit the reboot button.

There's no log produced in /var/log/Xorg.0.log when this happens, nor
can I find anything in the messages log. The only relevant log I have
is the one created when I run X -configure, which lists no errors.
This is the log:

###
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.1-RELEASE i386
Current Operating System: FreeBSD sino.plas.se 7.1-RELEASE FreeBSD
7.1-RELEASE #0: Thu Jan  1 14:37:25 UTC 2009
r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Build Date: 27 March 2009  01:00:57AM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Sat Mar 28 09:46:07 2009
(II) Loader magic: 0x81bcde0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on freebsd
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9

(--) PCI:*(0...@1:0:0) nVidia Corporation GeForce 8800 GTS 512 rev 162,
Mem @ 0xfd00/0, 0xd000/0, 0xfa00/0, I/O @ 0xbc00/0,
BIOS @ 0x/131072
List of video drivers:
nvidia
(II) LoadModule: nvidia

(II) Loading /usr/local/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor=NVIDIA Corporation
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) System resource ranges:
[0] -1  0   0x0010 - 0x3fff (0x3ff0) MX[B]E(B)
[1] -1  0   0x000f - 0x000f (0x1) MX[B]
[2] -1  0   0x000c - 0x000e (0x3) MX[B]
[3] -1  0   0x - 0x0009 (0xa) MX[B]
[4] -1  0   0x - 0x (0x1) IX[B]
[5] -1  0   0x - 0x00ff (0x100) IX[B]
(II) Primary Device is: PCI 0...@00:00:0
(II) NVIDIA dlloader X Driver  180.29  Tue Feb  3 10:12:46 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(++) Using config file: /home/lillis/xorg.conf.new
(==) ServerLayout X.org Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Including the default font path
/usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/.
(**) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/OTF,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/100dpi/,
/usr/local/lib/X11/fonts/75dpi/,
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/OTF,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/100dpi/,
/usr/local/lib/X11/fonts/75dpi/
(**) ModulePath set to /usr/local/lib/xorg/modules
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse'
will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loading sub module fb
(II) LoadModule: fb

(II) Loading /usr/local/lib/xorg/modules//libfb.so
(II) Module fb: vendor=X.Org Foundation
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module wfb
(II) LoadModule: wfb

(II) Loading /usr/local/lib/xorg

Re: nvidia-drivers crash computer on X start

[RW]

On Sat, 28 Mar 2009 13:53:43 +0100
Anders Holmström holmstrom.and...@gmail.com wrote:

 The current xorg.conf I'm using is listed below. It was generated with
 X -configure. I've used many different xorg.confs, but they've all
 more or less been using the same settings as below,

I don't know if it will help, but the nvidia driver has its own utility
for generating xorg.conf:

x11/nvidia-xconfig





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: nvidia-drivers crash computer on X start

[rasz]

RW wrote:

On Sat, 28 Mar 2009 13:53:43 +0100
Anders Holmström holmstrom.and...@gmail.com wrote:

  

The current xorg.conf I'm using is listed below. It was generated with
X -configure. I've used many different xorg.confs, but they've all
more or less been using the same settings as below,



I don't know if it will help, but the nvidia driver has its own utility
for generating xorg.conf:

x11/nvidia-xconfig





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

  

did you try
Option AllowEmptyInput off

in Serverlayout section under screen, keyboard, mouse?


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: nvidia-drivers crash computer on X start

[rasz]

Anders Holmström wrote:

did you try
Option AllowEmptyInput off

in Serverlayout section under screen, keyboard, mouse?



I was  told by a guy on the nvnews.net forums that I should put
machdep.disable_mtrrs=1 in my /boot/loader.conf. Apparently he had had
the same problem and he said it was because he had more than 2 gigs of
ram. He had solved it by that setting, and later by simply removing
the ram. I have 4 gigs, and the setting did work for me. HOWEVER, now
that I startx it's impossible to move the mouse/use the keyboard. It
also complaints about not being able to locate driver kbd and driver
mouse, plus mentions AllowEmptyInput as the culprit. I tried
disabling it but it in xorg.conf, but didn't help on the input device
issue. X still started though.

I didn't think the two were related, but based on your post I guess
they are. You could (or somebody else) possibly enlighten me a bit
more about the relationship, or point me in the right direction? man
xorg.conf didn't give much info.

  
i am not sure about the machdep setting there so i cc'd the mailing list 
maybe someone else can help you there.
about the AllowEmptyInput however, there is some info in ports/UPDATING 
round about when xorg was updated because I
am not sure if you said you disabled the mouse from xorg config instead 
of moused in etc/rc.conf ( if that is what you said).
i have moused_enable=NO in etc/rc.conf and add Option 
AllowEmptyInput off in xorg.conf.new right after a Xorg -configure.
also, i think you have to test cuz ppl get different setting to work 
depending their hardware, but i have had similar problem as you

with moused enabled and AllowEm...added. ( i have only 1gb memory fyi)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: nvidia-drivers crash computer on X start

[Mel Flynn]

On Saturday 28 March 2009 13:53:43 Anders Holmström wrote:

 The current xorg.conf I'm using is listed below. It was generated with
 X -configure. I've used many different xorg.confs, but they've all
 more or less been using the same settings as below, except when I
 tried NvAGP which didn't seem to work either (unless I was missing
 something).

When using NvAGP, /boot/device.hints MUST contain a line that disables agp.

 In dmesg.boot this is displayed:
 ###
 nvidia0: GeForce 8800 GTS 512 on vgapci0
 vgapci0: child nvidia0 requested pci_enable_busmaster
 vgapci0: child nvidia0 requested pci_enable_io
 vgapci0: child nvidia0 requested pci_enable_io

Harmless, as these interfaces are still supported. It should be seen as 
deprecation warning.

 nvidia0: [GIANT-LOCKED]
 nvidia0: [ITHREAD]
 ###

 I have tried reinstalling xorg-server and nvidia-driver many times.
 I've also had the same problem on a completely different FreeBSD
 install on the same computer, before a broken HDD forced me to
 reinstall completely. It was the same BSD version. I've made sure that
 the driver is actually loaded with kldstat, and have not used kldload
 nvidia as it's said that it's best to put an entry in
 /boot/loader.conf and restart instead. /dev/nvidia0 and /dev/nvidiactl
 show up after the drivers are installed and the computer rebooted.
 I've tried disabling FreeBSD AGP and using NvAGP instead, but the
 exact same thing happens. My card is a GeForce 8800 GTS 512 MB, and is
 supported by the drivers.

You properly walked all avenues that would resolve a configuration issue on 
your part. There's one more to try, disable the composite extension, yet this 
is a long shot if not using a window manager that uses composite.

Section Extensions
Option Composite disable
EndSection

If that does not help, then the proper action would be to file a bug report 
with nvidia, using the nvidia-bug-report.sh script, that unfortunately isn't 
installed by the port.

It's easiest to get a hold of that script using:
make -C /usr/ports/x11/nvidia-driver extract
cp `make -C /usr/ports/x11/nvidia-driver -V WRKSRC`/obj/*.sh .
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: [Solved] Official Nvidia Drivers, Toshiba Laptop, GeForce 4440 Cards: Always causes Freeze

[C. Michailidis]

On Fri, 07 Apr 2006 Sean Murphy wrote:
 I have finally come up with a way to use the official drivers

That's great news Sean, kudos! I would suggest that it's more appropriate to 
use the x11/nvidia-driver port, e.g.:

cd /usr/ports/x11/nvidia-driver
sudo make install clean

Then set your tunables (i.e hw.nvidia.registry.SoftEDIDs and 
hw.nvidia.registry.Mobile) via '/etc/sysctl.conf'.

Finally, you would apply the changes to xorg.conf as you recommend.

The nvidia readme file for their freebsd driver mentions this in the section 
titled 'CONFIGURING LOW-LEVEL PARAMETERS'.  Regardless, using ports to 
install things and sysctl.conf to control the low-level parameters is more 
traditional.

Of course the beauty of FLOSS systems is you can solve problems in a way that 
works best for your particular situation ;-)

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

[Solved] Official Nvidia Drivers, Toshiba Laptop, GeForce 4 440 Cards: Always causes Freeze

[Sean Murphy]

   I have finally come up with a way to use the official drivers from
   nvidia on Toshiba notebooks with a GeForce4 440 Go (and similar) video
   card.  Normally, using either linux or freebsd and the drivers from
   nvidia (instead of the default nv driver) would result in a hard
   freeze as soon as X was started.  I gave up trying to fix it, but then
   came across a solution for Linux last night, which I used as a basis
   for this FreeBSD solution...
   First of all, much credit goes to [1]this [2]information from the
   Ubuntu Document Storage Facility (check out Problem 8 at the
   bottom).
   Here's how I applied the same modifications to a FreeBSD system:
   The first step under Linux was to change some options in the nvidia
   kernel, which was done in Linux under /etc/modprobe.conf (or
   /etc/modprobe.d).  FreeBSD doesn't use modprobe, which I believe is
   used for the loading of a kernel module.
   Instead, we can modify the option in the source for nvidia's drivers,
   and then compile the nvidia kernel module with this already set the
   way we want:
   1. First, download the [3]latest[4] nvidia source here.  Extract (tar
   zxvf NVIDIA-FreeBSD-x86-1.0-8178.tar.gz) and move into the newly
   created directory.

   2.  Edit /src/nvidia_os_registry.c using your fav text editor:

   Change the values of the following variables:
   - NVreg_SoftEDIDs = 0 (was 1)
   - NVreg_Mobile = 1 (was ~0)
   Save nvidia_os_registry.c and exit.
   3. I didn't want linux compatability built into my nvidia kernel
   module, so I changed the following:
   Comment out (or undefine) this line:
   #define NV_SUPPORT_LINUX_COMPAT
   4.  Under the NVIDIA-FreeBSD-x86-1.0-8178 directory, compile and
   install the drivers:
   make install
   5.  Finally, this part is identical to the linux instructions.  We
   need to make some tweaks to xorg.conf (and tell X to use the nvidia
   drivers also):
   Your device directive should have something similar to:
   Section Device
   IdentifierNVIDIA Corporation NV17 [GeForce4 420 Go]
   Drivernvidia
   BusIDPCI:1:0:0
Option RenderAccel true
   Option AllowGLXWithComposite true
   OptionIgnoreEDIDtrue
   OptionIgnoreEdidFreqstrue
   OptionGenerateRTList0
   OptionOverridePolarity1
   EndSection
   That's all!  This time when you startx with the real nvidia drivers,
   it won't crash.  This is tested to work on both of my Toshiba
   laptops.  If there are any errors in this howto, feel free to correct
   it!  Now, us toshiba users can have 3d acceleration along with support
   for OpenGL  :).
   Hope this helps someone!
   - Murph

References

   1. http://doc.gwos.org/index.php/Latest_Nvidia_Dapper
   2. http://doc.gwos.org/index.php/Latest_Nvidia_Dapper
   3. http://www.nvidia.com/object/freebsd_1.0-8178.html
   4. http://www.nvidia.com/object/freebsd_1.0-8178.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: [Solved] Official Nvidia Drivers, Toshiba Laptop, GeForce 4 440 Cards: Always causes Freeze

[Sean Murphy]

Sorry for the formatting of my solution...a few things got mangled up.

For easier reading, check out my post on freebsdforums.org.

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

Re: [Solved] Official Nvidia Drivers, Toshiba Laptop, GeForce 4 440 Cards: Always causes Freeze

[Sean Murphy]

On Apr 7, 2006, at 7:34 PM, Sean Murphy wrote:


Sorry for the formatting of my solution...a few things got mangled up.

For easier reading, check out my post on freebsdforums.org.

- Murph


I'm having a conversation with myself here...three posts to get this  
right :)


You can find the post at http://www.bsdforums.org/forums/ 
showthread.php?t=40336.
(freebsd.org was supposed to be a link last message, but didn't  
work right)

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

Re: Slow 2d performance in X / opera / nvidia drivers

[Martin Tournoy]

Don't see any XOrg log file, you forgot to attatch it?

And what is Xinerama, i thought it was a window manager like KDE or gnome...?

Try loading from the open-source driver, or generic vga or vesa, will
that improve preformance?

You said problems started to occur with Opera 8 and later, did you try
using opera 7.x or 6.x? it those work alright I think opera support
would be the best place to be

On 12/01/06, Josh Paetzel [EMAIL PROTECTED] wrote:
 On Thursday 12 January 2006 04:25 am, Joseph Kerian wrote:
  On 1/11/06, Martin Tournoy [EMAIL PROTECTED] wrote:
   On 10/01/06, Josh Paetzel [EMAIL PROTECTED] wrote:
 
  *many helpful attachments snipped*
 
I've been having terrible 2d performance with opera
(linux-opera and native 8.51 and 9.0) using the nvidia drivers.
 When I windowshade it and then restore it there is a sizeable
delay while it redraws the window.  If I rapidly shade and
restore the window my idle CPU time goes to 0% and mp3 playback
will occassionally skip.
   
The problem first started when Opera 8 was released, I hoped
that further releases would address it but so far that has not
been the case.  Any suggestions for a fix welcome.
   
(Yes, I have been seeking support on opera.com but this feels
like a FreeBSD mis-configuration of some sort on my end. :)
  
   You might try turning the twinview of, it takes up heaps of
   resources on my machine, then again, your machine has 300% more
   RAM and clockspeed, so it should be able to handle it fine
  
   Try using freebsd AGP, the nvidia should work better but you
   might want to try it anyway...
 
  The other useful file for this might be your Xorg log.
 
   Which window manager do you use, I noted that KDE can be really,
   really slow even on newer machines (Krap Desktop Enviorment)
 
  *bites the troll*
 
   Is this problem ONLY with opera? or with other applications to?
   if you have another QT application you might want try how that
   runs. Also check you QT version, maybe it's ancient?
  
   Did you try using both the static/shared QT versions? If not, it
   might make a diffrence.
 
  I haven't had this problem at all with Opera on the ports KDE,
  using a far inferior nvidia card.
  I have had a bit of shared library wierdness, but Opera simply
  refused to run until I fixed that.
 
  If this is a PCI-Express card, note the discussion of 3d
  performance here:
  http://www.nvnews.net/vbulletin/showthread.php?t=59981

 Well, I think I may have found the problem but can't seem to find a
 fix to test my theory.  Xorg is loading Xinerama and I've found some
 noise via google that there is a 'nvidia-xinerama' that is faster
 than the native 'xorg-xinerama'.  I've tried disabling xinerama in my
 Xorg conf file but it loads anyways.

 Attached is my xorg.log

 --
 Thanks,

 Josh Paetzel


 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [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: Slow 2d performance in X / opera / nvidia drivers

[Joseph Kerian]

On 1/11/06, Martin Tournoy [EMAIL PROTECTED] wrote:
 On 10/01/06, Josh Paetzel [EMAIL PROTECTED] wrote:
*many helpful attachments snipped*
  I've been having terrible 2d performance with opera (linux-opera and
  native 8.51 and 9.0) using the nvidia drivers.  When I windowshade it
  and then restore it there is a sizeable delay while it redraws the
  window.  If I rapidly shade and restore the window my idle CPU time
  goes to 0% and mp3 playback will occassionally skip.
 
  The problem first started when Opera 8 was released, I hoped that
  further releases would address it but so far that has not been the
  case.  Any suggestions for a fix welcome.
 
  (Yes, I have been seeking support on opera.com but this feels like a
  FreeBSD mis-configuration of some sort on my end. :)

 You might try turning the twinview of, it takes up heaps of resources
 on my machine, then again, your machine has 300% more RAM and
 clockspeed, so it should be able to handle it fine

 Try using freebsd AGP, the nvidia should work better but you might
 want to try it anyway...
The other useful file for this might be your Xorg log.

 Which window manager do you use, I noted that KDE can be really,
 really slow even on newer machines (Krap Desktop Enviorment)
*bites the troll*

 Is this problem ONLY with opera? or with other applications to? if you
 have another QT application you might want try how that runs.
 Also check you QT version, maybe it's ancient?

 Did you try using both the static/shared QT versions? If not, it might
 make a diffrence.

I haven't had this problem at all with Opera on the ports KDE, using a
far inferior nvidia card.
I have had a bit of shared library wierdness, but Opera simply refused
to run until I fixed that.

If this is a PCI-Express card, note the discussion of 3d performance here:
 http://www.nvnews.net/vbulletin/showthread.php?t=59981
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Slow 2d performance in X / opera / nvidia drivers

[Josh Paetzel]

On Thursday 12 January 2006 04:25 am, Joseph Kerian wrote:
 On 1/11/06, Martin Tournoy [EMAIL PROTECTED] wrote:
  On 10/01/06, Josh Paetzel [EMAIL PROTECTED] wrote:

 *many helpful attachments snipped*

   I've been having terrible 2d performance with opera
   (linux-opera and native 8.51 and 9.0) using the nvidia drivers.
When I windowshade it and then restore it there is a sizeable
   delay while it redraws the window.  If I rapidly shade and
   restore the window my idle CPU time goes to 0% and mp3 playback
   will occassionally skip.
  
   The problem first started when Opera 8 was released, I hoped
   that further releases would address it but so far that has not
   been the case.  Any suggestions for a fix welcome.
  
   (Yes, I have been seeking support on opera.com but this feels
   like a FreeBSD mis-configuration of some sort on my end. :)
 
  You might try turning the twinview of, it takes up heaps of
  resources on my machine, then again, your machine has 300% more
  RAM and clockspeed, so it should be able to handle it fine
 
  Try using freebsd AGP, the nvidia should work better but you
  might want to try it anyway...

 The other useful file for this might be your Xorg log.

  Which window manager do you use, I noted that KDE can be really,
  really slow even on newer machines (Krap Desktop Enviorment)

 *bites the troll*

  Is this problem ONLY with opera? or with other applications to?
  if you have another QT application you might want try how that
  runs. Also check you QT version, maybe it's ancient?
 
  Did you try using both the static/shared QT versions? If not, it
  might make a diffrence.

 I haven't had this problem at all with Opera on the ports KDE,
 using a far inferior nvidia card.
 I have had a bit of shared library wierdness, but Opera simply
 refused to run until I fixed that.

 If this is a PCI-Express card, note the discussion of 3d
 performance here:
 http://www.nvnews.net/vbulletin/showthread.php?t=59981

Well, I think I may have found the problem but can't seem to find a 
fix to test my theory.  Xorg is loading Xinerama and I've found some 
noise via google that there is a 'nvidia-xinerama' that is faster 
than the native 'xorg-xinerama'.  I've tried disabling xinerama in my 
Xorg conf file but it loads anyways.

Attached is my xorg.log

-- 
Thanks,

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

Re: Slow 2d performance in X / opera / nvidia drivers

[Martin Tournoy]

On 10/01/06, Josh Paetzel [EMAIL PROTECTED] wrote:
 gimpy# uname -a
 FreeBSD gimpy.tcbug.org 5.4-RELEASE-p8 FreeBSD 5.4-RELEASE-p8 #9: Fri
 Jan  6 20:26:44 CST 2006
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GIMPY  i386

 dmesg attached

 Xorg config attached

 Kernel config attached

 I've been having terrible 2d performance with opera (linux-opera and
 native 8.51 and 9.0) using the nvidia drivers.  When I windowshade it
 and then restore it there is a sizeable delay while it redraws the
 window.  If I rapidly shade and restore the window my idle CPU time
 goes to 0% and mp3 playback will occassionally skip.

 The problem first started when Opera 8 was released, I hoped that
 further releases would address it but so far that has not been the
 case.  Any suggestions for a fix welcome.

 (Yes, I have been seeking support on opera.com but this feels like a
 FreeBSD mis-configuration of some sort on my end. :)

 --
 Thanks,

 Josh Paetzel


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




You might try turning the twinview of, it takes up heaps of resources
on my machine, then again, your machine has 300% more RAM and
clockspeed, so it should be able to handle it fine

Try using freebsd AGP, the nvidia should work better but you might
want to try it anyway...

Which window manager do you use, I noted that KDE can be really,
really slow even on newer machines (Krap Desktop Enviorment)

Is this problem ONLY with opera? or with other applications to? if you
have another QT application you might want try how that runs.
Also check you QT version, maybe it's ancient?

Did you try using both the static/shared QT versions? If not, it might
make a diffrence.


Don't post your dmesg again please, it makes me drool which makes my
keyboard dirty..
95 gig SCSI HDD *drool*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Slow 2d performance in X / opera / nvidia drivers

[Josh Paetzel]

gimpy# uname -a
FreeBSD gimpy.tcbug.org 5.4-RELEASE-p8 FreeBSD 5.4-RELEASE-p8 #9: Fri 
Jan  6 20:26:44 CST 2006 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GIMPY  i386

dmesg attached

Xorg config attached

Kernel config attached

I've been having terrible 2d performance with opera (linux-opera and 
native 8.51 and 9.0) using the nvidia drivers.  When I windowshade it 
and then restore it there is a sizeable delay while it redraws the 
window.  If I rapidly shade and restore the window my idle CPU time 
goes to 0% and mp3 playback will occassionally skip.

The problem first started when Opera 8 was released, I hoped that 
further releases would address it but so far that has not been the 
case.  Any suggestions for a fix welcome.

(Yes, I have been seeking support on opera.com but this feels like a 
FreeBSD mis-configuration of some sort on my end. :)

-- 
Thanks,

Josh Paetzel
Copyright (c) 1992-2005 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 5.4-RELEASE-p8 #9: Fri Jan  6 20:26:44 CST 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GIMPY
ACPI APIC Table: A M I  OEMAPIC 
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3500+ (2202.84-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x20ff2  Stepping = 2
  
Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
  AMD Features=0xe050NX,AMIE,LM,DSP,3DNow!
real memory  = 1073414144 (1023 MB)
avail memory = 1036673024 (988 MB)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 Version 0.3 irqs 0-23 on motherboard
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: A M I OEMRSDT on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-safe frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
nvidia0: GeForce 6600 GT mem 
0xfa00-0xfaff,0xe000-0xefff,0xfb00-0xfbff irq 16 at 
device 0.0 on pci1
pcm0: Creative EMU10K1 port 0xa400-0xa41f irq 16 at device 9.0 on pci0
pcm0: eMicro EM28028 AC97 Codec
pci0: network, ethernet at device 10.0 (no driver attached)
xl0: 3Com 3c905-TX Fast Etherlink XL port 0xb400-0xb43f irq 19 at device 14.0 
on pci0
miibus0: MII bus on xl0
nsphy0: DP83840 10/100 media interface on miibus0
nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:60:97:d8:ad:bd
atapci0: VIA 6420 SATA150 controller port 
0xb800-0xb8ff,0xc000-0xc00f,0xc400-0xc403,0xc800-0xc807,0xd000-0xd003,0xd400-0xd407
 irq 20 at device 15.0 on pci0
ata2: channel #0 on atapci0
ata3: channel #1 on atapci0
atapci1: VIA 8237 UDMA133 controller port 
0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
ata0: channel #0 on atapci1
ata1: channel #1 on atapci1
uhci0: VIA 83C572 USB controller port 0xd800-0xd81f irq 21 at device 16.0 on 
pci0
usb0: VIA 83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: VIA 83C572 USB controller port 0xe000-0xe01f irq 21 at device 16.1 on 
pci0
usb1: VIA 83C572 USB controller on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: VIA 83C572 USB controller port 0xe400-0xe41f irq 21 at device 16.2 on 
pci0
usb2: VIA 83C572 USB controller on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: VIA 83C572 USB controller port 0xe800-0xe81f irq 21 at device 16.3 on 
pci0
usb3: VIA 83C572 USB controller on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0: VIA VT6202 USB 2.0 controller mem 0xf9e0-0xf9e000ff irq 21 at 
device 16.4 on pci0
usb4: waiting for BIOS to give up control
usb4: timed out waiting for BIOS
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: VIA VT6202 USB 2.0 controller on ehci0
usb4: USB revision 2.0
uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
umass0: Jabil Circuit Seagate External Drive, rev 2.00/2.40, addr 2
isab0: PCI-ISA bridge at device 17.0 on pci0
isa0: ISA bus on isab0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on 
acpi0
fd0: 1440-KB 3.5 drive on fdc0 drive 0
ppc0: Standard

Re: nvidia drivers

[Bob Johnson]

On 9/15/05, Sean [EMAIL PROTECTED] wrote:
 I am using a test system and have been try to get the nvidia drivers 
 working.
 
 I am running freebsd 5.3 release, nvidia ultra 6800 256mb, and tried 
 installing the drivers using the port.
 

I have installed the nvidia driver a few times and it has worked, but
I've gone to the nvidia website and followed their directions, rather
than using the port.

 Went through all the info I can find and tried various things and no luck.

Have you read nvidia's README at
http://www.nvidia.com/object/freebsd_1.0-7676.html ?

In the default version distributed by nVidia, you have to disable
FreeBSD's AGP support or the nvidia driver will refuse to load.  I
don't know if the port builds it with that configuration or not.

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

Re: nvidia drivers

[Gregory Nou]

Bob Johnson wrote:




In the default version distributed by nVidia, you have to disable
FreeBSD's AGP support or the nvidia driver will refuse to load.  I
don't know if the port builds it with that configuration or not.

 

I do not agree. I now compile the kernel without agp, but I used to 
compile with it until recently and never had such problems. Iirc, 
nvidia-drivers do not care about which version (i mean, freebsd's or 
nvidia's one) you have of agp.ko. It even give you the choice of which 
you want to use. (only if you load the native agp in module, not if it 
is statically compiled). That's in the X configuration file, something 
like NvAgp, and should be set to 0,1 or 2 (it's explained in the 
documentation).

I'd like to add that the port nvidia-driver works just fine.

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

Re: nvidia drivers

[Lowell Gilbert]

Sean [EMAIL PROTECTED] writes:

 I am using a test system and have been try to get the nvidia drivers
 working.
 
 I am running freebsd 5.3 release, nvidia ultra 6800 256mb, and tried
 installing the drivers using the port.
 
 Went through all the info I can find and tried various things and no luck.
 
 On a fresh install of 5.3, I installed te nvidia driver using the port
 and after startx, (with no .xinitrc), it started fine. When I exited
 this test there were two lines about this kernel (generic) and version
 of FreeBSD not being able to support agp.
 
 I cvs'd up and rebuilt all ports. Kernel still running generic install
 and now have the below error.
 
 dmesg does show the nvidia0: geforce 6800 Ultra with various info after.
 dmesg also show on the next line nvidia0: [giant-locked]
 The final line of dmesg shows 'interrupt storm detected on irq16:
 nvidia0:; throttling interrupt source'
 
 Doing a startx, there is no .xinitrc in place, it fails.
 One line shows 'nvidia: could not open the device file /dev/nvidiactl
 (unknown error: 999).
 The some lines about failing to initialize the NVIDIA kernel module,
 and check to see if there is a supported GPU in the system.
 
 Also a line about Screen(s) found, but none have usable configuration.
 Fatal server error:
 no screens found.
 
 Checking the Xorg log it even states a NVIDIA GPU is found.
 The only thing that catches my attention is that it states (II)
 UnloadableModule nvidia.
 
 Anyone have success getting the nidia driver to run?

Start from the beginning.  You need to get the nvidia kernel module
loaded.  That apparently means you need AGP in your kernel.  It *was*
in the GENERIC kernel for 5.3, so you need to look more closely into
why it thinks that is a problem.  Look at the error messages in detail.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

nvidia drivers

[Sean]

I am using a test system and have been try to get the nvidia drivers 
working.


I am running freebsd 5.3 release, nvidia ultra 6800 256mb, and tried 
installing the drivers using the port.


Went through all the info I can find and tried various things and no luck.

On a fresh install of 5.3, I installed te nvidia driver using the port 
and after startx, (with no .xinitrc), it started fine. When I exited 
this test there were two lines about this kernel (generic) and version 
of FreeBSD not being able to support agp.


I cvs'd up and rebuilt all ports. Kernel still running generic install 
and now have the below error.


dmesg does show the nvidia0: geforce 6800 Ultra with various info after.
dmesg also show on the next line nvidia0: [giant-locked]
The final line of dmesg shows 'interrupt storm detected on irq16: 
nvidia0:; throttling interrupt source'


Doing a startx, there is no .xinitrc in place, it fails.
One line shows 'nvidia: could not open the device file /dev/nvidiactl 
(unknown error: 999).
The some lines about failing to initialize the NVIDIA kernel module, and 
check to see if there is a supported GPU in the system.


Also a line about Screen(s) found, but none have usable configuration.
Fatal server error:
no screens found.

Checking the Xorg log it even states a NVIDIA GPU is found.
The only thing that catches my attention is that it states (II) 
UnloadableModule nvidia.


Anyone have success getting the nidia driver to run?

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

Re: jerky opengl, nvidia drivers

[zork]

hmm.. it turned out that the problem was not
in the drivers or anywhere relevant.
Some stupid network monitoring desktop applet (which counts 
incoming/outgoing IP packets)
i had enabled just for fun was somehow causing this weird behavior.

Since it didn't show up in the 'top' program or anywhere else
for that matter I was fooled into believing that the
problem might be in the drivers or somewhere..
I have no idea how it could manage to do something like that,
it's also funny that some apps were unaffected.
Anyway, now it all works for me.
Thanks for the agp advice!
Louis LeBlanc wrote:
On 01/11/05 10:29 PM, zork sat at the `puter and typed:
ok.. even though there wasn't anything useful in the Xorg logfile,
after recompiling the kernel i get:
hw.nvidia.agp.status.status: enabled
hw.nvidia.agp.status.driver: nvidia
hw.nvidia.agp.status.rate: 4x
hw.nvidia.agp.status.fw: disabled
hw.nvidia.agp.status.sba: disabled
Now this almost doubles the frame rates, which is nice to see :)

Most Excellent Dude.

Alas, the problem still remains :(

Totally Bogus.
What app are you getting the hinky video from?

Will try upgrading everything tomorrow..

Most Righteous.
Just make sure you get all the dependencies when you do.
Good luck
Lou

Louis LeBlanc wrote:
Ok, according to your sysctls, you aren't getting the AGP acceleration
at all.
Try adding these lines to your card device section:
   Option RenderAccel True
   Option NvAGP 1 # Use NVIDIAs agp
Then restart X.
Check your hw.nvidia.agp sysctls, particularly these:
hw.nvidia.agp.status.status: disabled
hw.nvidia.agp.status.rate: n/a (disabled)
You want status to be enabled, and rate to be 2x or 4x.
From the sysctls below, it looks like the NvAGP setting is already
turned on, so that appears to be a default.
Since it's still not working, I suspect that if you check your
/var/log/Xorg.0.log file for warnings (WW) or errors (EE) related to AGP
use, you'll find something about the native FreeBSD AGP.  If you are
using a GENERIC kernel (uname -a will tell you), that's almost
certainly what's happening.
From what I've read, the native FreeBSD AGP doesn't always work with
NVidia cards.  You'll have to compile a custom kernel with the following
line removed:
device  agp
Check here for details:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html
Also, I'd recommend updating your ports and upgrading Xorg.  You might
also want to build and install the x11/nvidia-drivers port.
Lou
On 01/11/05 08:24 PM, zork sat at the `puter and typed:

well, Xorg -version says
X Protocol Version 11, Revision 0, Release 6.7
I think it was installed by sysinstall as a package.
I downloaded the drivers from nvidia.
the device section:
Section Device
   Identifier  MyGeForce
   Driver  nvidia
   VendorName  NVIDIA
   BoardName   GeForce4 MX 440
EndSection
the sysctls:
hw.nvidia.agp.card.rates: 4x 2x 1x
hw.nvidia.agp.card.fw: supported
hw.nvidia.agp.card.sba: not supported
hw.nvidia.agp.card.registers: 0x1f17:0x
hw.nvidia.agp.status.status: disabled
hw.nvidia.agp.status.driver: n/a (unused)
hw.nvidia.agp.status.rate: n/a (disabled)
hw.nvidia.agp.status.fw: n/a (disabled)
hw.nvidia.agp.status.sba: n/a (disabled)
hw.nvidia.version: NVIDIA FreeBSD x86 NVIDIA Kernel Module  1.0-6113 
Mon Aug  2 16:08:32 PDT 2004
hw.nvidia.registry.EnableVia4x: 0
hw.nvidia.registry.EnableALiAGP: 0
hw.nvidia.registry.NvAGP: 1
hw.nvidia.registry.EnableAGPSBA: 0
hw.nvidia.registry.EnableAGPFW: 0
hw.nvidia.registry.SoftEDIDs: 1
hw.nvidia.registry.Mobile: 4294967295
hw.nvidia.registry.ResmanDebugLevel: 4294967295
hw.nvidia.registry.FlatPanelMode: 0
hw.nvidia.cards.0.model: GeForce4 MX 440
hw.nvidia.cards.0.irq: 16
hw.nvidia.cards.0.vbios: 04.17.00.24.00
hw.nvidia.cards.0.type: AGP

kernel is basically the default one, built with agp device.
I *am* getting the acceleration, however, something is not quite right.
As i said, tuxracer runs just fine, so maybe it's some OpenGL feature
which most of the apps use, but tuxracer doesn't?
Anyway, i should probably try updating everything to the latest
versions and see what happens then.
Not so sure that it would help though :(
One more thing, I can't find any line in Xorg config relating
to agp. How is it enabled?
Louis LeBlanc wrote:

Top Posting to try keeping this readable
Next set of questions:
Are you running Xorg?  What version?  Did you install it from ports or
as a package?
Did you install the binaries from nvidia or did you install them from
ports?  If installed from ports, how did you build?
What is the card def block in your X config?
What are your hw.nvidia sysctls (command: sysctl hw.nvidia just in
case)?
Caveat:  Nvidia driver problems have come up twice already in the last
week, and several times in the last month or two.  Every time it seems
there is a magic sword hiding there that causes some poor guy to just
not be able to get it working.
My setup:  FreeBSD 5.3 RELEASE.
   My kernel

jerky opengl, nvidia drivers

[zork]

To get accelerated OpenGL, i installed Nvidia's drivers
for my Geforce4 MX 440 on a FreeBSD 5.3-release machine.
The problem is, most of the games and apps that use OpenGL
do not run smoothly - every second or so they would freeze
for a little while which makes it impossible to enjoy them.
At first I thought my system could be too slow or something,
however, this also happens with simple apps, even screensavers.
What's more, the game Tuxracer runs smoothly without any problems,
and since it's a pretty fancy one, i guess that rules
out system performance.
Does anybody have a clue as to what could be causing this?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: jerky opengl, nvidia drivers

[Louis LeBlanc]

On 01/11/05 06:01 PM, zork sat at the `puter and typed:
 To get accelerated OpenGL, i installed Nvidia's drivers
 for my Geforce4 MX 440 on a FreeBSD 5.3-release machine.
 
 The problem is, most of the games and apps that use OpenGL
 do not run smoothly - every second or so they would freeze
 for a little while which makes it impossible to enjoy them.
 
 At first I thought my system could be too slow or something,
 however, this also happens with simple apps, even screensavers.
 
 What's more, the game Tuxracer runs smoothly without any problems,
 and since it's a pretty fancy one, i guess that rules
 out system performance.
 
 Does anybody have a clue as to what could be causing this?


Are you loading the glx module in your Xorg config?

Lou
-- 
Louis LeBlanc   [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ

QOTD:
  I used to get high on life but lately I've built up a resistance.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: jerky opengl, nvidia drivers

[zork]

well, yes. the module section looks like this:
Section Module
Load  freetype
# Load xtt
Load  extmod
Load  glx
Load  dri
Load  dbe
Load  record
Load  xtrap
Load  type1
Load  speedo
EndSection
Louis LeBlanc wrote:
On 01/11/05 06:01 PM, zork sat at the `puter and typed:
To get accelerated OpenGL, i installed Nvidia's drivers
for my Geforce4 MX 440 on a FreeBSD 5.3-release machine.
The problem is, most of the games and apps that use OpenGL
do not run smoothly - every second or so they would freeze
for a little while which makes it impossible to enjoy them.
At first I thought my system could be too slow or something,
however, this also happens with simple apps, even screensavers.
What's more, the game Tuxracer runs smoothly without any problems,
and since it's a pretty fancy one, i guess that rules
out system performance.
Does anybody have a clue as to what could be causing this?

Are you loading the glx module in your Xorg config?
Lou
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: jerky opengl, nvidia drivers

[Louis LeBlanc]

Top Posting to try keeping this readable

Next set of questions:
Are you running Xorg?  What version?  Did you install it from ports or
as a package?

Did you install the binaries from nvidia or did you install them from
ports?  If installed from ports, how did you build?

What is the card def block in your X config?

What are your hw.nvidia sysctls (command: sysctl hw.nvidia just in
case)?

Caveat:  Nvidia driver problems have come up twice already in the last
week, and several times in the last month or two.  Every time it seems
there is a magic sword hiding there that causes some poor guy to just
not be able to get it working.

My setup:  FreeBSD 5.3 RELEASE.
 My kernel is build WITHOUT the agp device.
   NVidia GeForce FX5200.
   Drivers built from ports with Linux and ACPI support.
   Xorg 6.8.1 built from ports
   Xorg config enables the NVidia AGP.

I am getting OpenGL acceleration, 8X AGP, and have two monitors
presenting an extended desktop.  I still haven't figured out the tiny
ingredient that makes it all work for me, but keeps it eluding others.
That's kinda bugging me - and, I'm sure, those others that can't get it
working.

Present the info requested above; if I see anything that looks off, you
can try it.  Maybe we'll finally find the missing link.

Good luck.
Lou

On 01/11/05 06:59 PM, zork sat at the `puter and typed:
 well, yes. the module section looks like this:
 
 Section Module
  Load  freetype
  # Load xtt
  Load  extmod
  Load  glx
  Load  dri
  Load  dbe
  Load  record
  Load  xtrap
  Load  type1
  Load  speedo
 EndSection
 
 Louis LeBlanc wrote:
  On 01/11/05 06:01 PM, zork sat at the `puter and typed:
  
 To get accelerated OpenGL, i installed Nvidia's drivers
 for my Geforce4 MX 440 on a FreeBSD 5.3-release machine.
 
 The problem is, most of the games and apps that use OpenGL
 do not run smoothly - every second or so they would freeze
 for a little while which makes it impossible to enjoy them.
 
 At first I thought my system could be too slow or something,
 however, this also happens with simple apps, even screensavers.
 
 What's more, the game Tuxracer runs smoothly without any problems,
 and since it's a pretty fancy one, i guess that rules
 out system performance.
 
 Does anybody have a clue as to what could be causing this?
  
  
  
  Are you loading the glx module in your Xorg config?
  
  Lou
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

-- 
Louis LeBlanc   [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ

Nick the Greek's Law of Life:
  All things considered, life is 9 to 5 against.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: jerky opengl, nvidia drivers

[zork]

well, Xorg -version says
X Protocol Version 11, Revision 0, Release 6.7
I think it was installed by sysinstall as a package.
I downloaded the drivers from nvidia.
the device section:
Section Device
Identifier  MyGeForce
Driver  nvidia
VendorName  NVIDIA
BoardName   GeForce4 MX 440
EndSection
the sysctls:
hw.nvidia.agp.card.rates: 4x 2x 1x
hw.nvidia.agp.card.fw: supported
hw.nvidia.agp.card.sba: not supported
hw.nvidia.agp.card.registers: 0x1f17:0x
hw.nvidia.agp.status.status: disabled
hw.nvidia.agp.status.driver: n/a (unused)
hw.nvidia.agp.status.rate: n/a (disabled)
hw.nvidia.agp.status.fw: n/a (disabled)
hw.nvidia.agp.status.sba: n/a (disabled)
hw.nvidia.version: NVIDIA FreeBSD x86 NVIDIA Kernel Module  1.0-6113 
Mon Aug  2 16:08:32 PDT 2004
hw.nvidia.registry.EnableVia4x: 0
hw.nvidia.registry.EnableALiAGP: 0
hw.nvidia.registry.NvAGP: 1
hw.nvidia.registry.EnableAGPSBA: 0
hw.nvidia.registry.EnableAGPFW: 0
hw.nvidia.registry.SoftEDIDs: 1
hw.nvidia.registry.Mobile: 4294967295
hw.nvidia.registry.ResmanDebugLevel: 4294967295
hw.nvidia.registry.FlatPanelMode: 0
hw.nvidia.cards.0.model: GeForce4 MX 440
hw.nvidia.cards.0.irq: 16
hw.nvidia.cards.0.vbios: 04.17.00.24.00
hw.nvidia.cards.0.type: AGP

kernel is basically the default one, built with agp device.
I *am* getting the acceleration, however, something is not quite right.
As i said, tuxracer runs just fine, so maybe it's some OpenGL feature
which most of the apps use, but tuxracer doesn't?
Anyway, i should probably try updating everything to the latest
versions and see what happens then.
Not so sure that it would help though :(
One more thing, I can't find any line in Xorg config relating
to agp. How is it enabled?
Louis LeBlanc wrote:
Top Posting to try keeping this readable
Next set of questions:
Are you running Xorg?  What version?  Did you install it from ports or
as a package?
Did you install the binaries from nvidia or did you install them from
ports?  If installed from ports, how did you build?
What is the card def block in your X config?
What are your hw.nvidia sysctls (command: sysctl hw.nvidia just in
case)?
Caveat:  Nvidia driver problems have come up twice already in the last
week, and several times in the last month or two.  Every time it seems
there is a magic sword hiding there that causes some poor guy to just
not be able to get it working.
My setup:  FreeBSD 5.3 RELEASE.
 My kernel is build WITHOUT the agp device.
   NVidia GeForce FX5200.
   Drivers built from ports with Linux and ACPI support.
   Xorg 6.8.1 built from ports
   Xorg config enables the NVidia AGP.
I am getting OpenGL acceleration, 8X AGP, and have two monitors
presenting an extended desktop.  I still haven't figured out the tiny
ingredient that makes it all work for me, but keeps it eluding others.
That's kinda bugging me - and, I'm sure, those others that can't get it
working.
Present the info requested above; if I see anything that looks off, you
can try it.  Maybe we'll finally find the missing link.
Good luck.
Lou
On 01/11/05 06:59 PM, zork sat at the `puter and typed:
well, yes. the module section looks like this:
Section Module
Load  freetype
# Load xtt
Load  extmod
Load  glx
Load  dri
Load  dbe
Load  record
Load  xtrap
Load  type1
Load  speedo
EndSection
Louis LeBlanc wrote:
On 01/11/05 06:01 PM, zork sat at the `puter and typed:

To get accelerated OpenGL, i installed Nvidia's drivers
for my Geforce4 MX 440 on a FreeBSD 5.3-release machine.
The problem is, most of the games and apps that use OpenGL
do not run smoothly - every second or so they would freeze
for a little while which makes it impossible to enjoy them.
At first I thought my system could be too slow or something,
however, this also happens with simple apps, even screensavers.
What's more, the game Tuxracer runs smoothly without any problems,
and since it's a pretty fancy one, i guess that rules
out system performance.
Does anybody have a clue as to what could be causing this?

Are you loading the glx module in your Xorg config?
Lou
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [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: jerky opengl, nvidia drivers

[Louis LeBlanc]

Ok, according to your sysctls, you aren't getting the AGP acceleration
at all.

Try adding these lines to your card device section:
Option RenderAccel True
Option NvAGP 1 # Use NVIDIAs agp

Then restart X.

Check your hw.nvidia.agp sysctls, particularly these:
hw.nvidia.agp.status.status: disabled
hw.nvidia.agp.status.rate: n/a (disabled)

You want status to be enabled, and rate to be 2x or 4x.

From the sysctls below, it looks like the NvAGP setting is already
turned on, so that appears to be a default.

Since it's still not working, I suspect that if you check your
/var/log/Xorg.0.log file for warnings (WW) or errors (EE) related to AGP
use, you'll find something about the native FreeBSD AGP.  If you are
using a GENERIC kernel (uname -a will tell you), that's almost
certainly what's happening.

From what I've read, the native FreeBSD AGP doesn't always work with
NVidia cards.  You'll have to compile a custom kernel with the following
line removed:
device  agp
Check here for details:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html

Also, I'd recommend updating your ports and upgrading Xorg.  You might
also want to build and install the x11/nvidia-drivers port.

Lou

On 01/11/05 08:24 PM, zork sat at the `puter and typed:
 well, Xorg -version says
 X Protocol Version 11, Revision 0, Release 6.7
 
 I think it was installed by sysinstall as a package.
 
 I downloaded the drivers from nvidia.
 
 the device section:
 
 Section Device
  Identifier  MyGeForce
  Driver  nvidia
  VendorName  NVIDIA
  BoardName   GeForce4 MX 440
 EndSection
 
 the sysctls:
 
 hw.nvidia.agp.card.rates: 4x 2x 1x
 hw.nvidia.agp.card.fw: supported
 hw.nvidia.agp.card.sba: not supported
 hw.nvidia.agp.card.registers: 0x1f17:0x
 hw.nvidia.agp.status.status: disabled
 hw.nvidia.agp.status.driver: n/a (unused)
 hw.nvidia.agp.status.rate: n/a (disabled)
 hw.nvidia.agp.status.fw: n/a (disabled)
 hw.nvidia.agp.status.sba: n/a (disabled)
 hw.nvidia.version: NVIDIA FreeBSD x86 NVIDIA Kernel Module  1.0-6113 
 Mon Aug  2 16:08:32 PDT 2004
 hw.nvidia.registry.EnableVia4x: 0
 hw.nvidia.registry.EnableALiAGP: 0
 hw.nvidia.registry.NvAGP: 1
 hw.nvidia.registry.EnableAGPSBA: 0
 hw.nvidia.registry.EnableAGPFW: 0
 hw.nvidia.registry.SoftEDIDs: 1
 hw.nvidia.registry.Mobile: 4294967295
 hw.nvidia.registry.ResmanDebugLevel: 4294967295
 hw.nvidia.registry.FlatPanelMode: 0
 hw.nvidia.cards.0.model: GeForce4 MX 440
 hw.nvidia.cards.0.irq: 16
 hw.nvidia.cards.0.vbios: 04.17.00.24.00
 hw.nvidia.cards.0.type: AGP
 
 kernel is basically the default one, built with agp device.
 
 I *am* getting the acceleration, however, something is not quite right.
 
 As i said, tuxracer runs just fine, so maybe it's some OpenGL feature
 which most of the apps use, but tuxracer doesn't?
 
 Anyway, i should probably try updating everything to the latest
 versions and see what happens then.
 Not so sure that it would help though :(
 
 One more thing, I can't find any line in Xorg config relating
 to agp. How is it enabled?
 
 Louis LeBlanc wrote:
  Top Posting to try keeping this readable
  
  Next set of questions:
  Are you running Xorg?  What version?  Did you install it from ports or
  as a package?
  
  Did you install the binaries from nvidia or did you install them from
  ports?  If installed from ports, how did you build?
  
  What is the card def block in your X config?
  
  What are your hw.nvidia sysctls (command: sysctl hw.nvidia just in
  case)?
  
  Caveat:  Nvidia driver problems have come up twice already in the last
  week, and several times in the last month or two.  Every time it seems
  there is a magic sword hiding there that causes some poor guy to just
  not be able to get it working.
  
  My setup:  FreeBSD 5.3 RELEASE.
   My kernel is build WITHOUT the agp device.
 NVidia GeForce FX5200.
 Drivers built from ports with Linux and ACPI support.
 Xorg 6.8.1 built from ports
 Xorg config enables the NVidia AGP.
  
  I am getting OpenGL acceleration, 8X AGP, and have two monitors
  presenting an extended desktop.  I still haven't figured out the tiny
  ingredient that makes it all work for me, but keeps it eluding others.
  That's kinda bugging me - and, I'm sure, those others that can't get it
  working.
  
  Present the info requested above; if I see anything that looks off, you
  can try it.  Maybe we'll finally find the missing link.
  
  Good luck.
  Lou
  
  On 01/11/05 06:59 PM, zork sat at the `puter and typed:
  
 well, yes. the module section looks like this:
 
 Section Module
  Load  freetype
  # Load xtt
  Load  extmod
  Load  glx
  Load  dri
  Load  dbe
  Load  record
  Load  xtrap
  Load  type1
  Load  speedo
 EndSection
 
 Louis LeBlanc wrote:
 
 On 01/11/05 06:01 PM, zork sat at the `puter and typed

Re: jerky opengl, nvidia drivers

[zork]

ok.. even though there wasn't anything useful in the Xorg logfile,
after recompiling the kernel i get:
hw.nvidia.agp.status.status: enabled
hw.nvidia.agp.status.driver: nvidia
hw.nvidia.agp.status.rate: 4x
hw.nvidia.agp.status.fw: disabled
hw.nvidia.agp.status.sba: disabled
Now this almost doubles the frame rates, which is nice to see :)
Alas, the problem still remains :(
Will try upgrading everything tomorrow..
Louis LeBlanc wrote:
Ok, according to your sysctls, you aren't getting the AGP acceleration
at all.
Try adding these lines to your card device section:
Option RenderAccel True
Option NvAGP 1 # Use NVIDIAs agp
Then restart X.
Check your hw.nvidia.agp sysctls, particularly these:
hw.nvidia.agp.status.status: disabled
hw.nvidia.agp.status.rate: n/a (disabled)
You want status to be enabled, and rate to be 2x or 4x.
From the sysctls below, it looks like the NvAGP setting is already
turned on, so that appears to be a default.
Since it's still not working, I suspect that if you check your
/var/log/Xorg.0.log file for warnings (WW) or errors (EE) related to AGP
use, you'll find something about the native FreeBSD AGP.  If you are
using a GENERIC kernel (uname -a will tell you), that's almost
certainly what's happening.
From what I've read, the native FreeBSD AGP doesn't always work with
NVidia cards.  You'll have to compile a custom kernel with the following
line removed:
device  agp
Check here for details:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html
Also, I'd recommend updating your ports and upgrading Xorg.  You might
also want to build and install the x11/nvidia-drivers port.
Lou
On 01/11/05 08:24 PM, zork sat at the `puter and typed:
well, Xorg -version says
X Protocol Version 11, Revision 0, Release 6.7
I think it was installed by sysinstall as a package.
I downloaded the drivers from nvidia.
the device section:
Section Device
Identifier  MyGeForce
Driver  nvidia
VendorName  NVIDIA
BoardName   GeForce4 MX 440
EndSection
the sysctls:
hw.nvidia.agp.card.rates: 4x 2x 1x
hw.nvidia.agp.card.fw: supported
hw.nvidia.agp.card.sba: not supported
hw.nvidia.agp.card.registers: 0x1f17:0x
hw.nvidia.agp.status.status: disabled
hw.nvidia.agp.status.driver: n/a (unused)
hw.nvidia.agp.status.rate: n/a (disabled)
hw.nvidia.agp.status.fw: n/a (disabled)
hw.nvidia.agp.status.sba: n/a (disabled)
hw.nvidia.version: NVIDIA FreeBSD x86 NVIDIA Kernel Module  1.0-6113 
Mon Aug  2 16:08:32 PDT 2004
hw.nvidia.registry.EnableVia4x: 0
hw.nvidia.registry.EnableALiAGP: 0
hw.nvidia.registry.NvAGP: 1
hw.nvidia.registry.EnableAGPSBA: 0
hw.nvidia.registry.EnableAGPFW: 0
hw.nvidia.registry.SoftEDIDs: 1
hw.nvidia.registry.Mobile: 4294967295
hw.nvidia.registry.ResmanDebugLevel: 4294967295
hw.nvidia.registry.FlatPanelMode: 0
hw.nvidia.cards.0.model: GeForce4 MX 440
hw.nvidia.cards.0.irq: 16
hw.nvidia.cards.0.vbios: 04.17.00.24.00
hw.nvidia.cards.0.type: AGP

kernel is basically the default one, built with agp device.
I *am* getting the acceleration, however, something is not quite right.
As i said, tuxracer runs just fine, so maybe it's some OpenGL feature
which most of the apps use, but tuxracer doesn't?
Anyway, i should probably try updating everything to the latest
versions and see what happens then.
Not so sure that it would help though :(
One more thing, I can't find any line in Xorg config relating
to agp. How is it enabled?
Louis LeBlanc wrote:
Top Posting to try keeping this readable
Next set of questions:
Are you running Xorg?  What version?  Did you install it from ports or
as a package?
Did you install the binaries from nvidia or did you install them from
ports?  If installed from ports, how did you build?
What is the card def block in your X config?
What are your hw.nvidia sysctls (command: sysctl hw.nvidia just in
case)?
Caveat:  Nvidia driver problems have come up twice already in the last
week, and several times in the last month or two.  Every time it seems
there is a magic sword hiding there that causes some poor guy to just
not be able to get it working.
My setup:  FreeBSD 5.3 RELEASE.
My kernel is build WITHOUT the agp device.
  NVidia GeForce FX5200.
  Drivers built from ports with Linux and ACPI support.
  Xorg 6.8.1 built from ports
  Xorg config enables the NVidia AGP.
I am getting OpenGL acceleration, 8X AGP, and have two monitors
presenting an extended desktop.  I still haven't figured out the tiny
ingredient that makes it all work for me, but keeps it eluding others.
That's kinda bugging me - and, I'm sure, those others that can't get it
working.
Present the info requested above; if I see anything that looks off, you
can try it.  Maybe we'll finally find the missing link.
Good luck.
Lou
On 01/11/05 06:59 PM, zork sat at the `puter and typed:

well, yes. the module section looks like this:
Section Module
   Load  freetype
   # Load xtt
   Load  extmod

Re: jerky opengl, nvidia drivers

[Louis LeBlanc]

On 01/11/05 10:29 PM, zork sat at the `puter and typed:
 ok.. even though there wasn't anything useful in the Xorg logfile,
 after recompiling the kernel i get:
 
 hw.nvidia.agp.status.status: enabled
 hw.nvidia.agp.status.driver: nvidia
 hw.nvidia.agp.status.rate: 4x
 hw.nvidia.agp.status.fw: disabled
 hw.nvidia.agp.status.sba: disabled
 
 Now this almost doubles the frame rates, which is nice to see :)

Most Excellent Dude.

 Alas, the problem still remains :(

Totally Bogus.

What app are you getting the hinky video from?

 Will try upgrading everything tomorrow..

Most Righteous.

Just make sure you get all the dependencies when you do.

Good luck
Lou

 Louis LeBlanc wrote:
  Ok, according to your sysctls, you aren't getting the AGP acceleration
  at all.
  
  Try adding these lines to your card device section:
  Option RenderAccel True
  Option NvAGP 1 # Use NVIDIAs agp
  
  Then restart X.
  
  Check your hw.nvidia.agp sysctls, particularly these:
  hw.nvidia.agp.status.status: disabled
  hw.nvidia.agp.status.rate: n/a (disabled)
  
  You want status to be enabled, and rate to be 2x or 4x.
  
 From the sysctls below, it looks like the NvAGP setting is already
  turned on, so that appears to be a default.
  
  Since it's still not working, I suspect that if you check your
  /var/log/Xorg.0.log file for warnings (WW) or errors (EE) related to AGP
  use, you'll find something about the native FreeBSD AGP.  If you are
  using a GENERIC kernel (uname -a will tell you), that's almost
  certainly what's happening.
  
 From what I've read, the native FreeBSD AGP doesn't always work with
  NVidia cards.  You'll have to compile a custom kernel with the following
  line removed:
  device  agp
  Check here for details:
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html
  
  Also, I'd recommend updating your ports and upgrading Xorg.  You might
  also want to build and install the x11/nvidia-drivers port.
  
  Lou
  
  On 01/11/05 08:24 PM, zork sat at the `puter and typed:
  
 well, Xorg -version says
 X Protocol Version 11, Revision 0, Release 6.7
 
 I think it was installed by sysinstall as a package.
 
 I downloaded the drivers from nvidia.
 
 the device section:
 
 Section Device
  Identifier  MyGeForce
  Driver  nvidia
  VendorName  NVIDIA
  BoardName   GeForce4 MX 440
 EndSection
 
 the sysctls:
 
 hw.nvidia.agp.card.rates: 4x 2x 1x
 hw.nvidia.agp.card.fw: supported
 hw.nvidia.agp.card.sba: not supported
 hw.nvidia.agp.card.registers: 0x1f17:0x
 hw.nvidia.agp.status.status: disabled
 hw.nvidia.agp.status.driver: n/a (unused)
 hw.nvidia.agp.status.rate: n/a (disabled)
 hw.nvidia.agp.status.fw: n/a (disabled)
 hw.nvidia.agp.status.sba: n/a (disabled)
 hw.nvidia.version: NVIDIA FreeBSD x86 NVIDIA Kernel Module  1.0-6113 
 Mon Aug  2 16:08:32 PDT 2004
 hw.nvidia.registry.EnableVia4x: 0
 hw.nvidia.registry.EnableALiAGP: 0
 hw.nvidia.registry.NvAGP: 1
 hw.nvidia.registry.EnableAGPSBA: 0
 hw.nvidia.registry.EnableAGPFW: 0
 hw.nvidia.registry.SoftEDIDs: 1
 hw.nvidia.registry.Mobile: 4294967295
 hw.nvidia.registry.ResmanDebugLevel: 4294967295
 hw.nvidia.registry.FlatPanelMode: 0
 hw.nvidia.cards.0.model: GeForce4 MX 440
 hw.nvidia.cards.0.irq: 16
 hw.nvidia.cards.0.vbios: 04.17.00.24.00
 hw.nvidia.cards.0.type: AGP
 
 kernel is basically the default one, built with agp device.
 
 I *am* getting the acceleration, however, something is not quite right.
 
 As i said, tuxracer runs just fine, so maybe it's some OpenGL feature
 which most of the apps use, but tuxracer doesn't?
 
 Anyway, i should probably try updating everything to the latest
 versions and see what happens then.
 Not so sure that it would help though :(
 
 One more thing, I can't find any line in Xorg config relating
 to agp. How is it enabled?
 
 Louis LeBlanc wrote:
 
 Top Posting to try keeping this readable
 
 Next set of questions:
 Are you running Xorg?  What version?  Did you install it from ports or
 as a package?
 
 Did you install the binaries from nvidia or did you install them from
 ports?  If installed from ports, how did you build?
 
 What is the card def block in your X config?
 
 What are your hw.nvidia sysctls (command: sysctl hw.nvidia just in
 case)?
 
 Caveat:  Nvidia driver problems have come up twice already in the last
 week, and several times in the last month or two.  Every time it seems
 there is a magic sword hiding there that causes some poor guy to just
 not be able to get it working.
 
 My setup:  FreeBSD 5.3 RELEASE.
  My kernel is build WITHOUT the agp device.
NVidia GeForce FX5200.
Drivers built from ports with Linux and ACPI support.
Xorg 6.8.1 built from ports
Xorg config enables the NVidia AGP.
 
 I am getting OpenGL acceleration, 8X AGP, and have two monitors
 presenting an extended desktop.  I still haven't figured out the tiny
 ingredient that makes it all

nvidia drivers on ASUS A8X-Deluxe in 32-bit mode (5.2.1-RELEASE) / 5.3-RELEASE crash

[Gautham Ganapathy]

Hello,

Has anyone been able to get the nvidia display drivers (6113) to work
on the ASUS A8V-Deluxe motherboard (K8T800-Pro chipset) in 32-bit mode
(5.2.1-RELEASE)? I have tried nvidia's internal GART support as well
as freebsd's, but the system hangs on starting X and requires a hard
reset. I also found a couple of postings on the net with similar
issues.

Is this only for this chipset or are other amd64 chipsets affected also?

Also, the keyboard does not seem to work on 5.3-RELEASE (i386 and
amd64). the installation goes through fine, but when the system
restarts, the keyboard does not respond, although it is powered up
(LEDs work). How can I fix this?

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

nvidia drivers do not want to work Sony-Vaio PCG-GRT100 FreeBSD 5.3 Release

[dkouroun]

Dear FreeBSD users,
 I tried and tried and tried again to make Nvidia Drivers
 work on my Laptop(Sony-Vaio PCG-GRT100), with Release 5.3.
 I followed all the instrunctions in the README.
 I am sending you my 
 /boot/loader.conf
 /boot/defaults/loader.conf
 kernel-config: SONY-VAIO-NVIDIA
 my xorg.conf,
 my Xorg.0.log
 my kldstat output.
 
 you can find averything in the attached tarball!
 Any ideas?

 Thank you in advance!
 Drosos.___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FBSD 5.3 + Nvidia drivers

[John Murphy]

Cargnini wrote:

Someone knows if the driver is working on 5.3 release ?

Yes.  I installed the nvidia driver from ports
(/usr/ports/X11/nvidia-driver).

I must apply all the patchs like in 5.2.1, in 5.3 ??

No.  If you use the port it even makes an entry in
/boot/loader.conf for you.

Change the 'Driver nv' line to 'Driver nvidia' and add
'Load glx' in the Modules section of xorg.conf.

You may need to compile and install a custom kernel without
'device agp'.  Although it seems to work for me with GENERIC.
I didn't use GENERIC with anything more demanding than screen
savers though (GeForce4 Ti 4200 with AGP8).

The screen needs to run at a depth of 16 or 24 bit.
(the default is 8).

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

Re: FBSD 5.3 + Nvidia drivers

[Luís Vitório Cargnini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

OOPS, to GLX work and hardware acceleration i needed to apply all the three
patchs from nvidia, because this i asked if i need to apply this patchs again

On
Mon, 8 Nov 2004 17:10:30-0800 Derrick Ryalls [EMAIL PROTECTED] wrote:

 On Mon, 8 Nov 2004 07:45:20 -0200, Luís Vitório Cargnini
 [EMAIL PROTECTED] wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
  
  
  OOKKK i'll trty so, thanks god for this wonderful OS.
  (no more Nvidia Patchs YES).
  Thanks Velox.
  
  On Sun, 7 Nov 2004 21:24:20 -0600
  
  
  Vulpes Velox [EMAIL PROTECTED] wrote:
  
   On Mon, 8 Nov 2004 00:56:07 -0200
   Luís Vitório Cargnini [EMAIL PROTECTED] wrote:
  
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
   
Someone knows if the driver is working on 5.3 release ?
I must apply all the patchs like in 5.2.1, in 5.3 ??
Or it is not more necessary ???
  
   Not applied here and am not having any problems.
  
  
  
 
 Just updated to 5.3 this weekend.  Didn't try the port, just went to
 nvidia and downloaded their driver.  Installed and is running fine,
 though I have DRI and GLX disabled as it wasn't working before my
 upgrade and haven't yet checked it on this version.
 
 


- -- 
Thanks  Regards
Luís Vitório Cargnini
Computer Science Bachelor
OpenCores Member www.opencores.org
EuropeSwPatentFree http://EuropeSwPatentFree.hispalinux.es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBkLLrII4c9KZOcnoRAiiNAJ9byni2nFSiWPNFlAClcX1/zkhr7QCbBSS2
E39IjVb8cUPaaVWLQA6PjCU=1qs4
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FBSD 5.3 + Nvidia drivers

[Luís Vitório Cargnini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


OOKKK i'll trty so, thanks god for this wonderful OS.
(no more Nvidia Patchs YES).
Thanks Velox.

On Sun, 7 Nov 2004 21:24:20 -0600
Vulpes Velox [EMAIL PROTECTED] wrote:

 On Mon, 8 Nov 2004 00:56:07 -0200
 Luís Vitório Cargnini [EMAIL PROTECTED] wrote:
 
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
  
  Someone knows if the driver is working on 5.3 release ?
  I must apply all the patchs like in 5.2.1, in 5.3 ??
  Or it is not more necessary ???
 
 Not applied here and am not having any problems.
 
 


- -- 
Thanks  Regards
Luís Vitório Cargnini
Computer Science Bachelor
OpenCores Member www.opencores.org
EuropeSwPatentFree http://EuropeSwPatentFree.hispalinux.es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBj0AwII4c9KZOcnoRAtFlAJ9fGKzYOXJLeTPhPgolGbKXWRRdmACZAUlL
ecC+tMcEDBQ/3UUbWPf3qMc=WNQT
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FBSD 5.3 + Nvidia drivers

[Derrick Ryalls]

On Mon, 8 Nov 2004 07:45:20 -0200, Luís Vitório Cargnini
[EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 OOKKK i'll trty so, thanks god for this wonderful OS.
 (no more Nvidia Patchs YES).
 Thanks Velox.
 
 On Sun, 7 Nov 2004 21:24:20 -0600
 
 
 Vulpes Velox [EMAIL PROTECTED] wrote:
 
  On Mon, 8 Nov 2004 00:56:07 -0200
  Luís Vitório Cargnini [EMAIL PROTECTED] wrote:
 
   -BEGIN PGP SIGNED MESSAGE-
   Hash: SHA1
  
   Someone knows if the driver is working on 5.3 release ?
   I must apply all the patchs like in 5.2.1, in 5.3 ??
   Or it is not more necessary ???
 
  Not applied here and am not having any problems.
 
 
 

Just updated to 5.3 this weekend.  Didn't try the port, just went to
nvidia and downloaded their driver.  Installed and is running fine,
though I have DRI and GLX disabled as it wasn't working before my
upgrade and haven't yet checked it on this version.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

FBSD 5.3 + Nvidia drivers

[Luís Vitório Cargnini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Someone knows if the driver is working on 5.3 release ?
I must apply all the patchs like in 5.2.1, in 5.3 ??
Or it is not more necessary ???

- -- 
Thanks  Regards
Luís Vitório Cargnini
Computer Science Bachelor
OpenCores Member www.opencores.org
EuropeSwPatentFree http://EuropeSwPatentFree.hispalinux.es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (FreeBSD)

iD4DBQFBjuBHII4c9KZOcnoRAirAAJiIsNX6YCfELooDcLtqDODJUOXFAJ9IYJ5G
Y3UO9I3PBLOpCHlhix05rw==RqZC
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FBSD 5.3 + Nvidia drivers

[Emanuel Strobl]

Am Montag, 8. November 2004 03:56 schrieb Luís Vitório Cargnini:
 Someone knows if the driver is working on 5.3 release ?
 I must apply all the patchs like in 5.2.1, in 5.3 ??

Just use it from ports (x11/nvidia-drivers), its working perfectly!

-Mano

 Or it is not more necessary ???


pgpAiDpUuwE4G.pgp
Description: PGP signature

Re: FBSD 5.3 + Nvidia drivers

[Vulpes Velox]

On Mon, 8 Nov 2004 00:56:07 -0200
Luís Vitório Cargnini [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Someone knows if the driver is working on 5.3 release ?
 I must apply all the patchs like in 5.2.1, in 5.3 ??
 Or it is not more necessary ???

Not applied here and am not having any problems.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Nvidia drivers and mem.ko module

[Ricardo Britto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I'm running FreeBSD 5.2.1-RELEASE-p9 #3 on my machine and I'm having problems 
on installing nvidia-driver from ports.
I get the following error: ERROR: Failed to load the NVIDIA module!
KLD nvidia.ko: depends on mem - not available.

That's saying about mem.ko module. Well, I cvsuped my tree - 'cause mem.ko 
doesn't exit on my /boot/kernel directory - and it's not available for my 
tag=RELENG_5_2. I tried to update my tree with the tag=. and it downloads mem 
source, but it's incompatible to my freebsd version (when I try to build and 
install my kernel I get errors about options that aren't available for that 
version of kernel).

I searched google about more info and all I could get was a discussion between 
commiters about cvsup war/bug fix.
In the end: I can't install nvidia-driver because it needs mem.ko module and I 
can't install mem.ko module because it isn't cvsuped to my tree (or because 
I'm too dummy :( ).

Could anyone help?

I appreciate in advance,

Ricardo Britto
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBNCPJV/QugxV6rm4RAs+8AJwP/UzfDe8FVrQTSGIWwsQCApqAtQCeLNKL
shgFdWnyClMUtpalavF3obk=
=V36G
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Nvidia drivers and mem.ko module

[Henrik W Lund]

Ricardo Britto wrote:
Hi,
I'm running FreeBSD 5.2.1-RELEASE-p9 #3 on my machine and I'm having problems 
on installing nvidia-driver from ports.
I get the following error: ERROR: Failed to load the NVIDIA module!
KLD nvidia.ko: depends on mem - not available.

That's saying about mem.ko module. Well, I cvsuped my tree - 'cause mem.ko 
doesn't exit on my /boot/kernel directory - and it's not available for my 
tag=RELENG_5_2. I tried to update my tree with the tag=. and it downloads mem 
source, but it's incompatible to my freebsd version (when I try to build and 
install my kernel I get errors about options that aren't available for that 
version of kernel).

I searched google about more info and all I could get was a discussion between 
commiters about cvsup war/bug fix.
In the end: I can't install nvidia-driver because it needs mem.ko module and I 
can't install mem.ko module because it isn't cvsuped to my tree (or because 
I'm too dummy :( ).

Could anyone help?
I appreciate in advance,
Ricardo Britto
Greetings!
. is the -CURRENT branch tag, and the config file for the kernel may 
have changed since the creation of RELENG_5_2. You should use the 
GENERIC config file and modify it instead of using your old one.

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

problem in Linux-emulation and may be in NVidia drivers

[Roman Vasiliev]

Hi.
I have two question. I hope what someone helps me.
First:
  I have NVidia fx5600 and installs drivers from
/usr/ports/x11/nvidia-driver

# cat /boot/loader.conf
hw.ata.ata_dma=0
nvidia_load=YES
linux_load=YES # Linux emulation

First run glxgears shows ~2000 fps but second ~10 fps. And whole OpenGL
application lags.
Problem solves in changing on NVidia mx 4400. All works fine.
Second:
I have Maya 6.0 and 5.0. And on 4.10 Jul

# stat /usr/src/UPDATING
291840 340045 -rw-r--r-- 1 root wheel 1395128 43781 Jul 28 13:45:10
2004 Jul 17 18:33:11 2004 Jul 17 18:33:11 2004 16384 88 0
/usr/src/UPDATING

17 18:33:11 2004
After normal start. and showing interface both Maya 5.0 and 6.0 fails.

%/compat/linux/bin/csh /compat/linux/usr/aw/maya5.0/bin/maya
Maya (R), Version 5.0, 2003 04 01 00 02
Copyright 1997-2003 Alias|Wavefront, a division of Silicon Graphics Limited.
All rights reserved.
Graph Layout Toolkit
Copyright 1992-1997 Tom Sawyer Software, Berkeley, California
All rights reserved.
maya encountered a fatal error
Signal: 4 (Unknown Signal)
Attempting to save in
   /usr/tmp/romis.20040728.1326.ma

The same result on 5.2.1 current.
But near by 2 years ago i runs Maya 4.5 on FreeBSD somthing like 4.6.
And all works fine.
Please help. For me very convinient development on FreeBSD. And for that
me needed Maya.
But old version I haven't now.

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

Re: problem in Linux-emulation and may be in NVidia drivers

[Uwe Laverenz]

On Tue, Aug 03, 2004 at 10:08:19AM +0400, Roman Vasiliev wrote:

 First run glxgears shows ~2000 fps but second ~10 fps. And whole OpenGL
 application lags.
 
 Problem solves in changing on NVidia mx 4400. All works fine.

I have the same problem with a GF4-Ti/4200: first run is fast, second
is slow. An older GF2 works perfectly. I guess the only solution is
to wait for the release of new NVidia drivers, which are said to be
released fairly soon.

cu,
Uwe

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

Re: Nvidia Drivers

[Radu MOLNAR]

i've been using the nvidia drivers on riva tnt2 and geforce2 mx400 and
every tiem i installed the drivers on the nvidia site. worked perfectly
every time and except for the kernel options no other tweaking was
required


Radu Molnar
Babes-Bolyai Comunication Center



On Thu, 15 Apr 2004, Remko Lodder wrote:

 Mateusz Rajca wrote:
  Hi,
 
  I have Nvidia Ge Force 4 MX 440. How should I install drivers for Nvidia Ge Force 
  on
  FreeBSD 5.1 because FreeBSD won't work untill I install them?

 Hello,

 I have the same card, you can find drivers for it in the
 /usr/ports/x11/nvidia-driver directory.

 Note that i had to copy the nvidia.ko file from that directory to
 /boot/kernel myself. Perhaps i did something wrong, but when copied
 manually and added to /boot/loader.conf

 (nvidia_load=YES) it works like a sunshine.

 Oh and could you do a little favor for me in return, wrap your lines at
 80 chars or something. Thanks

 Cheers


 p.s little sidenote, FreeBSD works fine without the drivers, even VESA
 mode under X works. But when working dualscreen and for getting it all
 out of your card, it's better to  use the driver.

 
  Thanks
 
  Zdzislaws
 


 --

 Kind regards,

 Remko Lodder
 Elvandar.org/DSINet.org
 www.mostly-harmless.nl A Dutch community for helping newcomers on the
 hackerscene
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

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

Nvidia Drivers

[Mateusz Rajca]

Hi,
 
I have Nvidia Ge Force 4 MX 440. How should I install drivers for Nvidia Ge Force on 
FreeBSD 5.1 because FreeBSD won't work untill I install them?
 
Thanks
 
Zdzislaws


-
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Nvidia Drivers

[Peter Schuller]

 I have Nvidia Ge Force 4 MX 440. How should I install drivers for Nvidia Ge
 Force on FreeBSD 5.1 because FreeBSD won't work untill I install them?

Well. I haven't used the nvidia driver on FreeBSD yet, but there is a port, 
so:

cd /usr/ports/x11/nvidia-driver  make install

should do the trick; and follow the instructions 
in /usr/ports/x11/nvidia-driver/pkg-message

-- 
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0xE9758B7D or 'Peter Schuller [EMAIL PROTECTED]'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org

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

Re: Nvidia Drivers

[Remko Lodder]

Mateusz Rajca wrote:
Hi,
 
I have Nvidia Ge Force 4 MX 440. How should I install drivers for Nvidia Ge Force on 
FreeBSD 5.1 because FreeBSD won't work untill I install them?
Hello,

I have the same card, you can find drivers for it in the 
/usr/ports/x11/nvidia-driver directory.

Note that i had to copy the nvidia.ko file from that directory to 
/boot/kernel myself. Perhaps i did something wrong, but when copied 
manually and added to /boot/loader.conf

(nvidia_load=YES) it works like a sunshine.

Oh and could you do a little favor for me in return, wrap your lines at 
80 chars or something. Thanks

Cheers

p.s little sidenote, FreeBSD works fine without the drivers, even VESA 
mode under X works. But when working dualscreen and for getting it all 
out of your card, it's better to  use the driver.

 
Thanks
 
Zdzislaws



--

Kind regards,

Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl A Dutch community for helping newcomers on the 
hackerscene
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

GeForce FX 5800 Ultra with Nvidia Drivers on 5.2

[Shaun Friedle]

Hi,
I am having trouble using my FX 5800 Ultra with the FreeBSD Nvidia
driver, which I installed from the ports collection. If I try to use the
Nvidia driver when I start X I get a garbled screen with a few letters
and symbols (like the smiley face) and some blocks of flashing colour,
but mostly just a grey pattern character. The machine does not respond
to input at this point, I have to hard restart the machine because
Ctrl+Alt+Backspace (or Delete) do nothing.

The card works fine with the vesa drivers, but not with the nv drivers
which makes the display show a sort of pink fuzzy pattern with scrolls
upwards (nothing to do with frequency at my monitor just blanks the
screen if it is out of range). The machine is still responsive with the
nv drivers though.

I have tried the nvidia drivers with the NvAgp setting set to all
possible settings and it is the same (don't know if that should make a
difference or not).

I have taken a photo of the screen which is at
http://www.insipidity.co.uk/nvidia.jpg

Is anyone else using the nvidia drivers with a FX 5800 Ultra, and did
you encounter any problems? I hope I can fix this because I am trying to
rid myself of Windows, but I need hardware acceleration so I can play
games.

The log looks like this:

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: FreeBSD 5.2 i386 [ELF] 
Build Date: 07 December 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Tue Apr 13 13:37:40 2004
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout Layout0
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Keyboard0
(**) Option XkbModel pc104
(**) XKB: model: pc104
(**) Option XkbLayout gb
(**) XKB: layout: gb
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Mouse0
(==) FontPath set to
/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9

(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on freebsd
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.3.0, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2578 card 1043,80f6 rev 02 class 06,00,00
hdr 00
(II) PCI: 00:01:0: chip 8086,2579 card , rev 02 class 06,04,00
hdr 01
(II) PCI: 00:1d:0: chip 8086,24d2 card 1043,80a6 rev 02 class 0c,03,00
hdr 80
(II) PCI: 00:1d:1: chip 8086,24d4 card 1043,80a6 rev 02 class 0c,03,00
hdr 00
(II) PCI: 00:1d:2: chip 8086,24d7 card 1043,80a6 rev 02 class 0c,03,00
hdr 00
(II) PCI: 00:1d:3: chip 8086,24de card 1043,80a6 rev 02 class 0c,03,00
hdr 00
(II) PCI: 00:1d:7: chip 8086,24dd card 1043,80a6 rev 02 class 0c,03,20
hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00
hdr 01
(II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00
hdr 80
(II) PCI: 00:1f:1: chip 8086,24db card 1043,80a6 rev 02 class 01,01,8a
hdr 00
(II) PCI: 00:1f:2: chip 8086,24d1 card 1043,80a6 rev 02 class 01,01,8f
hdr 00
(II) PCI: 00:1f:3: chip 8086,24d3 card 1043,80a6 rev 02 class 0c,05,00
hdr 00
(II) PCI: 00:1f:5: chip 8086,24d5 card 1043,80f3 rev 02 class 04,01,00
hdr 00
(II) PCI: 01:00:0: chip 10de,0330 card , rev a1 class 03,00,00
hdr 00
(II) PCI: 02:03:0: chip 1106,3044 card 1043,808a rev 80 class 0c,00,10
hdr 00
(II) PCI: 02:04:0: chip 105a,3373 card 1043,80f5 rev 02 class 01,04,00
hdr 00
(II) PCI: 02:05:0: chip 10b7,1700 card 1043,80eb rev 12 class 02,00,00
hdr 00
(II) PCI: 02:0a:0: chip 11c1,0458 card 141d,9300 rev 02 class 07,80,00
hdr 00
(II) PCI: 02:0d:0: chip 1102,0004 card 1102,1007 rev 04 class 04,01,00
hdr 80
(II) PCI: 02:0d:1

Re: GeForce FX 5800 Ultra with Nvidia Drivers on 5.2

[Doug Poland]

On Tue, Apr 13, 2004 at 03:04:03PM +0100, Shaun Friedle wrote:
 Hi,
 I am having trouble using my FX 5800 Ultra with the FreeBSD Nvidia
 driver, which I installed from the ports collection. If I try to use the
 Nvidia driver when I start X I get a garbled screen with a few letters
 and symbols (like the smiley face) and some blocks of flashing colour,
 but mostly just a grey pattern character. The machine does not respond
 to input at this point, I have to hard restart the machine because
 Ctrl+Alt+Backspace (or Delete) do nothing.
 
I found this site to be useful: 

  http://www.soulwax.net/nvidia/

Especially the Do This First section.  I had the same problem until I
disabled ACPI.

For the record, I've got a GeForce4 Ti 4200 running dual-head under
5.2.1-RELEASE.  I boot with ACPI disabled (Option #2) and load the
driver via /boot/loader.conf (nvidia_load=YES).  I built a custom
kernel but can't tell you if that was required as I did that before
disabling ACPI.

On another box, I've got an FX 5700 Ultra that does NOT work.  On this
machine I'm running XFree86-4-Server-snap cause I read somewhere that
the nv driver for the 5700 will not work on XFree86-FontServer-4.3.0_3.
This machine is running 5.2-CURRENT with a custom kernel.
Unfortunately, I cannot disable ACPI on this ASUS P4C800-E Deluxe board
as the kernel dumps on errors 9 every time.  

So for me, ACPI was the key.  If I could just get this bloody ASUS board
to boot without ACPI I think I'd be in business.

Good luck to you and I'd appreciate any info you have if successful.

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

Re: GeForce FX 5800 Ultra with Nvidia Drivers on 5.2

[Shaun Friedle]

On Tue, 2004-04-13 at 17:14, Doug Poland wrote:
I built a custom kernel but can't tell you if that was required as I did that
 before disabling ACPI.

Well, if I disable SMP, I seem to be going in the right direction as
the machine no longer locks up.

 Unfortunately, I cannot disable ACPI on this ASUS P4C800-E Deluxe board
 as the kernel dumps on errors 9 every time.  

Well, I'm obviously very unlucky since I have an Asus P4C800 Deluxe and get the
same thing! The message is:

Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x58: 0x2d5c
stack pointer   = 0x10: 0xf80
frame pointer   = 0x10: 0x0
code segment= base 0xc00f000, limit 0x, type 0x1b
= DPL 0, pres 1, def32 0, gran 0
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
trap number = 0
panic: general protection fault


 So for me, ACPI was the key.  If I could just get this bloody ASUS board
 to boot without ACPI I think I'd be in business.

I think you're right. After searching on Google for a while (as I am sure you have 
done)
I have found no solution. 

 Good luck to you and I'd appreciate any info you have if successful.

I don't think I'm going to be able to solve this. Hopefully it will be fixed soon, 
apparently
the problem is 5.x has grown a regression in its handling of BIOS32 calls somehow. I 
found
that in this thread: 
http://lists.freebsd.org/pipermail/freebsd-current/2004-March/023392.html



-- 
Shaun Friedle
[EMAIL PROTECTED]

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

Re: GeForce FX 5800 Ultra with Nvidia Drivers on 5.2

[Josh Paetzel]

On Tue, Apr 13, 2004 at 06:50:38PM +0100, Shaun Friedle wrote:
 On Tue, 2004-04-13 at 17:14, Doug Poland wrote:
 I built a custom kernel but can't tell you if that was required as I did that
  before disabling ACPI.
 
 Well, if I disable SMP, I seem to be going in the right direction as
 the machine no longer locks up.

Ditto here.

 
  Unfortunately, I cannot disable ACPI on this ASUS P4C800-E Deluxe board
  as the kernel dumps on errors 9 every time.  

Haven't tried that yet.

 
 Well, I'm obviously very unlucky since I have an Asus P4C800 Deluxe and get the
 same thing! The message is:
 
 Fatal trap 9: general protection fault while in kernel mode
 instruction pointer   = 0x58: 0x2d5c
 stack pointer = 0x10: 0xf80
 frame pointer = 0x10: 0x0
 code segment  = base 0xc00f000, limit 0x, type 0x1b
   = DPL 0, pres 1, def32 0, gran 0
 processor eflags  = interrupt enabled, resume, IOPL = 0
 current process   = 0 (swapper)
 trap number   = 0
 panic: general protection fault
 
 
  So for me, ACPI was the key.  If I could just get this bloody ASUS board
  to boot without ACPI I think I'd be in business.
 
 I think you're right. After searching on Google for a while (as I am sure you have 
 done)
 I have found no solution. 
 
  Good luck to you and I'd appreciate any info you have if successful.
 
 I don't think I'm going to be able to solve this. Hopefully it will be fixed soon, 
 apparently
 the problem is 5.x has grown a regression in its handling of BIOS32 calls somehow. 
 I found
 that in this thread: 
 http://lists.freebsd.org/pipermail/freebsd-current/2004-March/023392.html
 
  Shaun Friedle
 [EMAIL PROTECTED]

My issue is that SMP + Nvidia Drivers + GF4 ti 4200 + 5.2.1-RELEASE, 
4.10-RELEASE or -STABLE or CURRENT hangs the system.  I've mailed the 
-questions mailing list once, and found someone with the exact same issue that 
I am having, but I suspect it's arcane enough that no one is going to try to 
fix it.  For now running the nv driver is acceptable.

Josh Paetzel

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

RE: nVidia drivers on FreeBSD 5.2.1 (Dell Inspiron 8100 laptop)

[Ralph M. Los]

Tried /usr/ports/x11/nvidia-driver and doing make install...worked great
and gave some instructions about doing a make setup which doesn't
exist.  After thatstill getting this when I try to get X running.
I've included my XF86Config snip at the bottom just for giggles.

ERROR SNIP
(WW) NVIDIA: Chipset GeForce2 Go in Device section NVIDIA GeForce 2
isn't valid for this driver.
(EE) No devices detected

Fatal server error:
No screens found

/ERROR SNIP

My XF86Config file snip
Section Device
Identifier NVIDIA GeForce 2
VendorName NVIDIA
BoardName  GeForce2 Go
Driver nvidia
BoardName  GeForce2 Go
ChipSetGeForce2 Go
BusID  PCI:1:0:0
EndSection

Section Screen
Identifier Screen0
Device NVIDIA GeForce 2
MonitorMonitor0
...
...
EndSection

/My XF86Config file snip




ARG

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

SOLVED: RE: nVidia drivers on FreeBSD 5.2.1 (Dell Inspiron 8100 laptop)

[Ralph M. Los]

OK - I resolve to the fact that I just can't read error messages.  I
commented out the chipset portion...and voila...everything works like a
CHARM.  Sorry to waste everyone's time with a completely stupid mistake.

-Original Message-
From: Ralph M. Los 
Sent: Wednesday, March 10, 2004 6:48 PM
To: [EMAIL PROTECTED]
Cc: Frank Knobbe
Subject: RE: nVidia drivers on FreeBSD 5.2.1 (Dell Inspiron 8100 laptop)


Tried /usr/ports/x11/nvidia-driver and doing make install...worked great
and gave some instructions about doing a make setup which doesn't
exist.  After thatstill getting this when I try to get X running.
I've included my XF86Config snip at the bottom just for giggles.

ERROR SNIP
(WW) NVIDIA: Chipset GeForce2 Go in Device section NVIDIA GeForce 2
isn't valid for this driver.
(EE) No devices detected

Fatal server error:
No screens found

/ERROR SNIP

My XF86Config file snip
Section Device
Identifier NVIDIA GeForce 2
VendorName NVIDIA
BoardName  GeForce2 Go
Driver nvidia
BoardName  GeForce2 Go
ChipSetGeForce2 Go
BusID  PCI:1:0:0
EndSection

Section Screen
Identifier Screen0
Device NVIDIA GeForce 2
MonitorMonitor0
...
...
EndSection

/My XF86Config file snip




ARG

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

nVidia drivers on FreeBSD 5.2.1 (Dell Inspiron 8100 laptop)

[Ralph M. Los]

Hi,
 Me again...now that I have my Cisco 350 working...I have X working fine
- and I've downloaded what appears to be the latest 1.0-4365 driver from
nVidia.com.  I've tried to get the driver working - but no luck.  Below
is my XF86Config file...but it doesn't appear to work - how can I
determine what the proper parameters are?

Section Monitor
Identifier   Monitor0
VendorName   Monitor Vendor
ModelNameMonitor Model
HorizSync31.5 - 82.0
VertRefresh  50.0 - 100.0
EndSection
 

Section Device
 

### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz
### [arg]: arg optional
#Option SWcursor  # [bool]
#Option HWcursor  # [bool]
#Option NoAccel   # [bool]
#Option ShowCache # [bool]
#Option ShadowFB  # [bool]
#Option UseFBDev  # [bool]
#Option Rotate# [str]
#Option VideoKey  # i
#Option FlatPanel # [bool]
#Option FPDither  # [bool]
#Option CrtcNumber# i
Identifier  Device
Driver  nvidia
VendorName  nVidia Corporation
BoardName   NV11 [GeForce2 Go]
ChipSet GeForce2 Go
BusID   PCI:1:0:0
EndSection
 
Section Screen
Identifier Screen0
Device Device
MonitorMonitor0
DefaultDepth 24
SubSection Display
Depth 16
EndSubSection

The line marked above is the one that causes me the concern.  Please
help - I'm trying to get this working with the official nVidia drivers.

Ralph

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+  Ralph | Internet Systems  Security   +
+   Boundariez.com   | -Specializing in Paranoia-  +
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+  ralph[!at]boundariez[dot!]com |  Never understimate the power +
+AIM: SekurityWizard | stupid people +
+ICQ: 2206039|in large groups+
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

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

Re: nVidia drivers on FreeBSD 5.2.1 (Dell Inspiron 8100 laptop)

[Kris Kennaway]

On Mon, Mar 08, 2004 at 11:19:01PM -0500, Ralph M. Los wrote:
 Hi,
  Me again...now that I have my Cisco 350 working...I have X working fine
 - and I've downloaded what appears to be the latest 1.0-4365 driver from
 nVidia.com.  I've tried to get the driver working - but no luck.  Below
 is my XF86Config file...but it doesn't appear to work - how can I
 determine what the proper parameters are?

Try using the nvidia-driver port, it may set things up differently
(correctly) on 5.x.

Kris


pgp0.pgp
Description: PGP signature

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Adam Olsen]

Ok,

The file can be found at http://linuxhelp.homeunix.com/xfree.log and my 
XF86Config at http://linuxhelp.homeunix.com/XF86Config

Thanks,

Adam Olsen

Daniela wrote:

On Thursday 15 January 2004 21:35, Adam Olsen wrote:
 

Daniela,

When I press ctrl+alt+F1, I am on the virtual console, but I cannot see
it because I'm getting the mode out of range error.  X does not
terminate - and if I press ctrl+alt+F9, I can get back to X just fine -
no more out of range error on the monitor.
I can be on the virtual console until I startx, and which point if I
switch back to a virtual console or exit X I get the mode out of range
error.
So basically, after I startx, something happens to the virtual console
that makes it so that if I go back to it I get the mode out of range error.
   

OK, do the following: use the command startx  somefile and send me the 
file it produces. This will hopefully tell us what the problem is.

 

Thanks,

Adam Olsen

Daniela wrote:
   

On Thursday 15 January 2004 20:00, Adam Olsen wrote:
 

Daniela,

Ok - Everything works perfectly in X.  When I switch to the VT, I get a
mode out of range error.  I can switch back to X just fine.  Just the VT
has this problem.
   

OK, when you press, say, ctrl+alt+F1 to switch to the VT, are you still
in X or at the console? Is the error message at the console or on the VT
from where you entered startx? Does X terminate?
 

I never get the wavy text while in X.  If by chance I am able to switch
to the VT for some reason without getting the mode out of range error,
all the text is waving around.  This has not happened in FreeBSD 5.2,
but I did see it a few times in 4.8 (I don't know if I'll be able to
reproduce it).
   

If you switch back to X when you get the wavy text, is everything OK
there? Can you start X from inside a debugger? What do you have in your
XF86Config?
I'll go to sleep now, good night.

 

Thanks,

Adam Olsen

Daniela wrote:
   

On Thursday 15 January 2004 19:29, Adam Olsen wrote:
 

Daniela,

I see it when I switch to a virtual console only.  When I switch back
to X, I'm ok again.  Also, if I exit X, I get it the error, but I can
blindly startx again.
   

I don't quite understand what you mean. I thought you can't switch back
to VT?
 

At one point in FreeBSD 4.8 I could switch to the virtual console, but
everything was wavy - text was moving around (it was really weird).
   

Could you describe this a bit more? I'm often seeing text moving around,
and weird colorful stripes on the screen when I switch to X. Viewing a
specific page in Mozilla triggers this. Unfortunately, I can't just open
the debugger and see what's going on at this time, because I can hardly
see anything on the screen.
When you're able to reproduce it, then have a look at the on-screen menu
of your monitor and check the frequencies, they're probably way too
high.
 

Thanks,

Adam Olsen

Daniela wrote:
   

On Thursday 15 January 2004 17:06, Adam Olsen wrote:
 

Hello,

I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
drivers available.  Everything works ok _except_ once I load X I
cannot switch back to the virtual console.  I get a mode out of
range error. I had this problem with FreeBSD 4.8 as well.
   

This isn't necessarily nvidia-specific, I have this too with ATI.
Where and when exactly do you see the mode out of range error?
My best guess would be that this is an XFree86 bug.

Daniela
 

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

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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Daniela]

On Saturday 17 January 2004 15:24, Adam Olsen wrote:
 Ok,

 The file can be found at http://linuxhelp.homeunix.com/xfree.log and my
 XF86Config at http://linuxhelp.homeunix.com/XF86Config

You have the generic NVIDIA driver specified, this could be the problem.
Try to run the following commands:

XFree86 -configure
XFree86 -xf86config ~/XF86Config.new

Do you still get the error when switching to VT?
If no, you will probably have to reconfigure X using the ~/XF86Config.new as 
the basis, but the problem is solved.
If yes, send the file /var/log/XFree86.0.log.


 Thanks,

 Adam Olsen

 Daniela wrote:
 On Thursday 15 January 2004 21:35, Adam Olsen wrote:
 Daniela,
 
 When I press ctrl+alt+F1, I am on the virtual console, but I cannot see
 it because I'm getting the mode out of range error.  X does not
 terminate - and if I press ctrl+alt+F9, I can get back to X just fine -
 no more out of range error on the monitor.
 
 I can be on the virtual console until I startx, and which point if I
 switch back to a virtual console or exit X I get the mode out of range
 error.
 
 So basically, after I startx, something happens to the virtual console
 that makes it so that if I go back to it I get the mode out of range
  error.
 
 OK, do the following: use the command startx  somefile and send me the
 file it produces. This will hopefully tell us what the problem is.
 
 Thanks,
 
 Adam Olsen
 
 Daniela wrote:
 On Thursday 15 January 2004 20:00, Adam Olsen wrote:
 Daniela,
 
 Ok - Everything works perfectly in X.  When I switch to the VT, I get a
 mode out of range error.  I can switch back to X just fine.  Just the
  VT has this problem.
 
 OK, when you press, say, ctrl+alt+F1 to switch to the VT, are you still
 in X or at the console? Is the error message at the console or on the VT
 from where you entered startx? Does X terminate?
 
 I never get the wavy text while in X.  If by chance I am able to switch
 to the VT for some reason without getting the mode out of range error,
 all the text is waving around.  This has not happened in FreeBSD 5.2,
 but I did see it a few times in 4.8 (I don't know if I'll be able to
 reproduce it).
 
 If you switch back to X when you get the wavy text, is everything OK
 there? Can you start X from inside a debugger? What do you have in your
 XF86Config?
 
 I'll go to sleep now, good night.
 
 Thanks,
 
 Adam Olsen
 
 Daniela wrote:
 On Thursday 15 January 2004 19:29, Adam Olsen wrote:
 Daniela,
 
 I see it when I switch to a virtual console only.  When I switch back
 to X, I'm ok again.  Also, if I exit X, I get it the error, but I can
 blindly startx again.
 
 I don't quite understand what you mean. I thought you can't switch
  back to VT?
 
 At one point in FreeBSD 4.8 I could switch to the virtual console,
  but everything was wavy - text was moving around (it was really
  weird).
 
 Could you describe this a bit more? I'm often seeing text moving
  around, and weird colorful stripes on the screen when I switch to X.
  Viewing a specific page in Mozilla triggers this. Unfortunately, I
  can't just open the debugger and see what's going on at this time,
  because I can hardly see anything on the screen.
 When you're able to reproduce it, then have a look at the on-screen
  menu of your monitor and check the frequencies, they're probably way
  too high.
 
 Thanks,
 
 Adam Olsen
 
 Daniela wrote:
 On Thursday 15 January 2004 17:06, Adam Olsen wrote:
 Hello,
 
 I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
 drivers available.  Everything works ok _except_ once I load X I
 cannot switch back to the virtual console.  I get a mode out of
 range error. I had this problem with FreeBSD 4.8 as well.
 
 This isn't necessarily nvidia-specific, I have this too with ATI.
 Where and when exactly do you see the mode out of range error?
 
 My best guess would be that this is an XFree86 bug.
 
 Daniela
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
  [EMAIL PROTECTED]

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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Daniela]

On Thursday 15 January 2004 21:35, Adam Olsen wrote:
 Daniela,

 When I press ctrl+alt+F1, I am on the virtual console, but I cannot see
 it because I'm getting the mode out of range error.  X does not
 terminate - and if I press ctrl+alt+F9, I can get back to X just fine -
 no more out of range error on the monitor.

 I can be on the virtual console until I startx, and which point if I
 switch back to a virtual console or exit X I get the mode out of range
 error.

 So basically, after I startx, something happens to the virtual console
 that makes it so that if I go back to it I get the mode out of range error.

OK, do the following: use the command startx  somefile and send me the 
file it produces. This will hopefully tell us what the problem is.


 Thanks,

 Adam Olsen

 Daniela wrote:
  On Thursday 15 January 2004 20:00, Adam Olsen wrote:
 Daniela,
 
 Ok - Everything works perfectly in X.  When I switch to the VT, I get a
 mode out of range error.  I can switch back to X just fine.  Just the VT
 has this problem.
 
  OK, when you press, say, ctrl+alt+F1 to switch to the VT, are you still
  in X or at the console? Is the error message at the console or on the VT
  from where you entered startx? Does X terminate?
 
 I never get the wavy text while in X.  If by chance I am able to switch
 to the VT for some reason without getting the mode out of range error,
 all the text is waving around.  This has not happened in FreeBSD 5.2,
 but I did see it a few times in 4.8 (I don't know if I'll be able to
 reproduce it).
 
  If you switch back to X when you get the wavy text, is everything OK
  there? Can you start X from inside a debugger? What do you have in your
  XF86Config?
 
  I'll go to sleep now, good night.
 
 Thanks,
 
 Adam Olsen
 
 Daniela wrote:
 On Thursday 15 January 2004 19:29, Adam Olsen wrote:
 Daniela,
 
 I see it when I switch to a virtual console only.  When I switch back
  to X, I'm ok again.  Also, if I exit X, I get it the error, but I can
  blindly startx again.
 
 I don't quite understand what you mean. I thought you can't switch back
 to VT?
 
 At one point in FreeBSD 4.8 I could switch to the virtual console, but
 everything was wavy - text was moving around (it was really weird).
 
 Could you describe this a bit more? I'm often seeing text moving around,
 and weird colorful stripes on the screen when I switch to X. Viewing a
 specific page in Mozilla triggers this. Unfortunately, I can't just open
 the debugger and see what's going on at this time, because I can hardly
 see anything on the screen.
 When you're able to reproduce it, then have a look at the on-screen menu
 of your monitor and check the frequencies, they're probably way too
  high.
 
 Thanks,
 
 Adam Olsen
 
 Daniela wrote:
 On Thursday 15 January 2004 17:06, Adam Olsen wrote:
 Hello,
 
 I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
 drivers available.  Everything works ok _except_ once I load X I
  cannot switch back to the virtual console.  I get a mode out of
  range error. I had this problem with FreeBSD 4.8 as well.
 
 This isn't necessarily nvidia-specific, I have this too with ATI.
 Where and when exactly do you see the mode out of range error?
 
 My best guess would be that this is an XFree86 bug.
 
 Daniela

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

Cannot switch back to virtual terminal w/ nvidia drivers

[Adam Olsen]

Hello,

I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia 
drivers available.  Everything works ok _except_ once I load X I cannot 
switch back to the virtual console.  I get a mode out of range error. 
 I had this problem with FreeBSD 4.8 as well.

This used to happen to me in Linux as well until the latest two releases 
of the driver.

I am running the KT133 chipset on my motherboard (yeah yeah, I know).

Any help in this matter would be appreciated.

Thanks,

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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Daniela]

On Thursday 15 January 2004 17:06, Adam Olsen wrote:
 Hello,

 I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
 drivers available.  Everything works ok _except_ once I load X I cannot
 switch back to the virtual console.  I get a mode out of range error.
   I had this problem with FreeBSD 4.8 as well.

This isn't necessarily nvidia-specific, I have this too with ATI.
Where and when exactly do you see the mode out of range error?

My best guess would be that this is an XFree86 bug.

Daniela


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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Adam Olsen]

Daniela,

I see it when I switch to a virtual console only.  When I switch back to 
X, I'm ok again.  Also, if I exit X, I get it the error, but I can 
blindly startx again.

At one point in FreeBSD 4.8 I could switch to the virtual console, but 
everything was wavy - text was moving around (it was really weird).

Thanks,

Adam Olsen

Daniela wrote:
On Thursday 15 January 2004 17:06, Adam Olsen wrote:

Hello,

I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
drivers available.  Everything works ok _except_ once I load X I cannot
switch back to the virtual console.  I get a mode out of range error.
 I had this problem with FreeBSD 4.8 as well.


This isn't necessarily nvidia-specific, I have this too with ATI.
Where and when exactly do you see the mode out of range error?
My best guess would be that this is an XFree86 bug.

Daniela


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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Daniela]

On Thursday 15 January 2004 19:29, Adam Olsen wrote:
 Daniela,

 I see it when I switch to a virtual console only.  When I switch back to
 X, I'm ok again.  Also, if I exit X, I get it the error, but I can
 blindly startx again.

I don't quite understand what you mean. I thought you can't switch back to VT?


 At one point in FreeBSD 4.8 I could switch to the virtual console, but
 everything was wavy - text was moving around (it was really weird).

Could you describe this a bit more? I'm often seeing text moving around, and 
weird colorful stripes on the screen when I switch to X. Viewing a specific 
page in Mozilla triggers this. Unfortunately, I can't just open the debugger 
and see what's going on at this time, because I can hardly see anything on 
the screen.
When you're able to reproduce it, then have a look at the on-screen menu of 
your monitor and check the frequencies, they're probably way too high.


 Thanks,

 Adam Olsen

 Daniela wrote:
  On Thursday 15 January 2004 17:06, Adam Olsen wrote:
 Hello,
 
 I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
 drivers available.  Everything works ok _except_ once I load X I cannot
 switch back to the virtual console.  I get a mode out of range error.
   I had this problem with FreeBSD 4.8 as well.
 
  This isn't necessarily nvidia-specific, I have this too with ATI.
  Where and when exactly do you see the mode out of range error?
 
  My best guess would be that this is an XFree86 bug.
 
  Daniela

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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Adam Olsen]

Daniela,

Ok - Everything works perfectly in X.  When I switch to the VT, I get a 
mode out of range error.  I can switch back to X just fine.  Just the VT 
has this problem.

I never get the wavy text while in X.  If by chance I am able to switch 
to the VT for some reason without getting the mode out of range error, 
all the text is waving around.  This has not happened in FreeBSD 5.2, 
but I did see it a few times in 4.8 (I don't know if I'll be able to 
reproduce it).

Thanks,

Adam Olsen

Daniela wrote:
On Thursday 15 January 2004 19:29, Adam Olsen wrote:

Daniela,

I see it when I switch to a virtual console only.  When I switch back to
X, I'm ok again.  Also, if I exit X, I get it the error, but I can
blindly startx again.


I don't quite understand what you mean. I thought you can't switch back to VT?



At one point in FreeBSD 4.8 I could switch to the virtual console, but
everything was wavy - text was moving around (it was really weird).


Could you describe this a bit more? I'm often seeing text moving around, and 
weird colorful stripes on the screen when I switch to X. Viewing a specific 
page in Mozilla triggers this. Unfortunately, I can't just open the debugger 
and see what's going on at this time, because I can hardly see anything on 
the screen.
When you're able to reproduce it, then have a look at the on-screen menu of 
your monitor and check the frequencies, they're probably way too high.



Thanks,

Adam Olsen

Daniela wrote:

On Thursday 15 January 2004 17:06, Adam Olsen wrote:

Hello,

I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
drivers available.  Everything works ok _except_ once I load X I cannot
switch back to the virtual console.  I get a mode out of range error.
I had this problem with FreeBSD 4.8 as well.
This isn't necessarily nvidia-specific, I have this too with ATI.
Where and when exactly do you see the mode out of range error?
My best guess would be that this is an XFree86 bug.

Daniela


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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Jez Hancock]

On Thu, Jan 15, 2004 at 01:00:25PM -0700, Adam Olsen wrote:
 Daniela,
 
 Ok - Everything works perfectly in X.  When I switch to the VT, I get a 
 mode out of range error.  I can switch back to X just fine.  Just the VT 
 has this problem.
How are you 'switching to the VT' exactly?

-- 
Jez Hancock
 - System Administrator / PHP Developer

http://munk.nu/
http://jez.hancock-family.com/  - Another FreeBSD Diary
http://ipfwstats.sf.net/- ipfw peruser traffic logging
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Adam Olsen]

CTRL+ALT+F1 etc...

Jez Hancock wrote:
On Thu, Jan 15, 2004 at 01:00:25PM -0700, Adam Olsen wrote:

Daniela,

Ok - Everything works perfectly in X.  When I switch to the VT, I get a 
mode out of range error.  I can switch back to X just fine.  Just the VT 
has this problem.
How are you 'switching to the VT' exactly?

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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Daniela]

On Thursday 15 January 2004 20:00, Adam Olsen wrote:
 Daniela,

 Ok - Everything works perfectly in X.  When I switch to the VT, I get a
 mode out of range error.  I can switch back to X just fine.  Just the VT
 has this problem.

OK, when you press, say, ctrl+alt+F1 to switch to the VT, are you still in X 
or at the console? Is the error message at the console or on the VT from 
where you entered startx? Does X terminate?


 I never get the wavy text while in X.  If by chance I am able to switch
 to the VT for some reason without getting the mode out of range error,
 all the text is waving around.  This has not happened in FreeBSD 5.2,
 but I did see it a few times in 4.8 (I don't know if I'll be able to
 reproduce it).

If you switch back to X when you get the wavy text, is everything OK there?
Can you start X from inside a debugger? What do you have in your XF86Config?

I'll go to sleep now, good night.


 Thanks,

 Adam Olsen

 Daniela wrote:
  On Thursday 15 January 2004 19:29, Adam Olsen wrote:
 Daniela,
 
 I see it when I switch to a virtual console only.  When I switch back to
 X, I'm ok again.  Also, if I exit X, I get it the error, but I can
 blindly startx again.
 
  I don't quite understand what you mean. I thought you can't switch back
  to VT?
 
 At one point in FreeBSD 4.8 I could switch to the virtual console, but
 everything was wavy - text was moving around (it was really weird).
 
  Could you describe this a bit more? I'm often seeing text moving around,
  and weird colorful stripes on the screen when I switch to X. Viewing a
  specific page in Mozilla triggers this. Unfortunately, I can't just open
  the debugger and see what's going on at this time, because I can hardly
  see anything on the screen.
  When you're able to reproduce it, then have a look at the on-screen menu
  of your monitor and check the frequencies, they're probably way too high.
 
 Thanks,
 
 Adam Olsen
 
 Daniela wrote:
 On Thursday 15 January 2004 17:06, Adam Olsen wrote:
 Hello,
 
 I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
 drivers available.  Everything works ok _except_ once I load X I cannot
 switch back to the virtual console.  I get a mode out of range error.
  I had this problem with FreeBSD 4.8 as well.
 
 This isn't necessarily nvidia-specific, I have this too with ATI.
 Where and when exactly do you see the mode out of range error?
 
 My best guess would be that this is an XFree86 bug.
 
 Daniela

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

Re: Cannot switch back to virtual terminal w/ nvidia drivers

[Adam Olsen]

Daniela,

When I press ctrl+alt+F1, I am on the virtual console, but I cannot see 
it because I'm getting the mode out of range error.  X does not 
terminate - and if I press ctrl+alt+F9, I can get back to X just fine - 
no more out of range error on the monitor.

I can be on the virtual console until I startx, and which point if I 
switch back to a virtual console or exit X I get the mode out of range 
error.

So basically, after I startx, something happens to the virtual console 
that makes it so that if I go back to it I get the mode out of range error.

Thanks,

Adam Olsen

Daniela wrote:
On Thursday 15 January 2004 20:00, Adam Olsen wrote:

Daniela,

Ok - Everything works perfectly in X.  When I switch to the VT, I get a
mode out of range error.  I can switch back to X just fine.  Just the VT
has this problem.


OK, when you press, say, ctrl+alt+F1 to switch to the VT, are you still in X 
or at the console? Is the error message at the console or on the VT from 
where you entered startx? Does X terminate?



I never get the wavy text while in X.  If by chance I am able to switch
to the VT for some reason without getting the mode out of range error,
all the text is waving around.  This has not happened in FreeBSD 5.2,
but I did see it a few times in 4.8 (I don't know if I'll be able to
reproduce it).


If you switch back to X when you get the wavy text, is everything OK there?
Can you start X from inside a debugger? What do you have in your XF86Config?
I'll go to sleep now, good night.



Thanks,

Adam Olsen

Daniela wrote:

On Thursday 15 January 2004 19:29, Adam Olsen wrote:

Daniela,

I see it when I switch to a virtual console only.  When I switch back to
X, I'm ok again.  Also, if I exit X, I get it the error, but I can
blindly startx again.
I don't quite understand what you mean. I thought you can't switch back
to VT?

At one point in FreeBSD 4.8 I could switch to the virtual console, but
everything was wavy - text was moving around (it was really weird).
Could you describe this a bit more? I'm often seeing text moving around,
and weird colorful stripes on the screen when I switch to X. Viewing a
specific page in Mozilla triggers this. Unfortunately, I can't just open
the debugger and see what's going on at this time, because I can hardly
see anything on the screen.
When you're able to reproduce it, then have a look at the on-screen menu
of your monitor and check the frequencies, they're probably way too high.

Thanks,

Adam Olsen

Daniela wrote:

On Thursday 15 January 2004 17:06, Adam Olsen wrote:

Hello,

I'm using FreeBSD 5.2-RELEASE and have installed the latest nvidia
drivers available.  Everything works ok _except_ once I load X I cannot
switch back to the virtual console.  I get a mode out of range error.
I had this problem with FreeBSD 4.8 as well.
This isn't necessarily nvidia-specific, I have this too with ATI.
Where and when exactly do you see the mode out of range error?
My best guess would be that this is an XFree86 bug.

Daniela


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

RE: Any Ideas On X Freezing up with NVIDIA Drivers?

[Chris Readle]

Hi,

What Nvidia card are you using?  What drivers are you using?  Can you post
your dmesg, uname -a and XF86Config?

chris

--- Brian Black [EMAIL PROTECTED] wrote:
 Hi,
 I am also having  alot of problems, my problem is when i load the 
 driver and try to run X i am getting crazy matrix like characters on the
 
 screen.  X does not come up and the char's stay present until i reboot. 
 
 I have been reading the postings but have been unsuccessful with finding
 
 a solution.  It seems like others are having similar problems but i dont
 
 see any type of solution or it there is one for this card.   It would be
 
 nice to be able to use the new card.  Any Ideas?
 
 
 


__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Any ideas on X freezing up with NVIDIA drivers?

[Chris Readle]

Sorry for the delayed response, was out with a sick child yesterday and
had no web access at the Dr's office (they really need to put hotspots in
waiting rooms! ;).

At any rate, I also haven't had a chance to look at my files yet, but I
wanted to make sure to remind you to set option NvAgp 2 if you do,
which I know for a fact I'm using in my file.

chris

--- Don Whitteker [EMAIL PROTECTED] wrote:
 ( I am sorry if this was duplicated...mistyped address
 and it was returned)
 
 --- Chris Readle [EMAIL PROTECTED] wrote:
  Fellow newb here, but I've also been working on X
  issues with my GForceFX
  in Linux *and* FBSD so I might (and I stress might)
  be able to help.
 
 Hey man...any help at all is appreciated = )
 
  First things first, can you post your
  /etc/X11/XF86Config file?
 here ya go..
 
 Section ServerLayout
 Identifier Layout0
 Screen  0  Screen0 0 0
 InputDeviceKeyboard0 CoreKeyboard
 InputDeviceMouse0 CorePointer
 EndSection
 
 Section Files
 EndSection
 
 Section Module
 
 # Load freetype
 # Load xtt
 Load  extmod
 Load  glx
 #Load  dri
 Load  dbe
 #Load  record
 Load  xtrap
 Load  type1
 Load  speedo
 EndSection
 
 Section InputDevice
 Identifier  Mouse0
 Driver  mouse
 Option  Protocol Auto
 Option  Device /dev/sysmouse
 Option  ZAxisMapping 4 5
 EndSection
 
 Section InputDevice
 Identifier  Keyboard0
 Driver  keyboard
 Option  XkbModel pc104
 Option  XkbLayout us
 EndSection
 
 Section Monitor
 Identifier   Monitor0
 HorizSync31.5 - 48.5
 VertRefresh  50.0 - 70.0
 EndSection
 
 Section Device
 Identifier  Card0
 Driver  nvidia
 Option  NvAgp 1 #was tring this out 
 #when I
 was experimenting with the nvidia AGPGART
 EndSection
 
 Section Screen
 Identifier Screen0
 Device Card0
 MonitorMonitor0
 DefaultDepth 24
 SubSection Display
 Depth 24
 Modes1024x768 800x600
 640x480
 EndSubSection
 EndSection
  Are you using *dm (xdm, kdm, gdm, etc) or are you
  booting to CLI and doing
  startx?  I've had more issues with kdm and my FX
  than with CLI + startx.
 
 Actually I start up in the CLI and startx to get in
 
  As for AGP and kernel config, I've gotten mine
  working with AGP in the
  kernel and compiled with no optimizations other than
  CPUTYPE.
 
 I will try again with it like that
 
  Once I get a look at your files (and compare them to
  mine at home) I might
  have some more suggestions.
  
  chris
 
 That would be very cool = )
 
 Don
 
 __
 Do you Yahoo!?
 The New Yahoo! Shopping - with improved product search
 http://shopping.yahoo.com


__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Any ideas on X freezing up with NVIDIA drivers?

[Don Whitteker]

Hello all and thank you in advance...first off I am
still a bit of a
newbie with FreeBSD (and *NIX in general) but am
learning more every
day = ) I hope I got this on the correct list but feel
free to point
me in the right direction if I did not

OK...here's the problem. I have an A7N8X board
(deluxe) and am trying
to use the nvidia driver with my GeForceFX. I've
installed 5.1-Release
(I tries 4.8 too but the 5.1 just seemed to flow
better with me) and
have ACPI turned off in my BIOS and in FBSD. However
no matter what I
do all I seem to be able to get when I start up X is
the nvidia logo.
I lose all keyboard function and thus have to do a
hard reboot. I have
been working on this particular little problem for a
number of weeks
now to no avail. I have searched any relevant docs I
could find
(nvidia, handbook,XFree86 site, nforce2 site) to no
avail. I have
googles so much I have trouble remembering which
keyword combination I
used to get to a particular page. Basically I am
clueless on what to
try next. I have tried make setup with the
WITH_FREEBSD_AGP with agp
in the kernel, tried the WITH_FREEBSD_AGP with it not
in the kernel
but as a module, I have tried with no agp in kernel or
agp.ko and
using the cards AGPGART. I have even tried
combinations between them.
I have compiled and recompiled with optimizations
(-march=athlon-xp
CHFLAGS= -o -pipe) and without but nothing seems to
change.

The only errors I am getting in my XFree86.0.log is a
couple of
warnings about some resolution I don't use anyway not
working with my
monitor and of course it not being able to verify AGP
usage when I am
using freebsd's agpgart. Other than that everything
looks peachy keen.
Everything works fine with nv

Looking back I probably would not have gotten such a
problematic
chipset if I had known I was going to be giving up
windows and moving
to something a little more fun = )...btw besides the
whole video
driver thing I am loving this OS.

oh yeahif you need me to post my dmesg or config
file or log or
anything just let me know

= )
Don Whitteker

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Any ideas on X freezing up with NVIDIA drivers?

[Don Whitteker]

( I am sorry if this was duplicated...mistyped address
and it was returned)

--- Chris Readle [EMAIL PROTECTED] wrote:
 Fellow newb here, but I've also been working on X
 issues with my GForceFX
 in Linux *and* FBSD so I might (and I stress might)
 be able to help.

Hey man...any help at all is appreciated = )

 First things first, can you post your
 /etc/X11/XF86Config file?
here ya go..

Section ServerLayout
Identifier Layout0
Screen  0  Screen0 0 0
InputDeviceKeyboard0 CoreKeyboard
InputDeviceMouse0 CorePointer
EndSection

Section Files
EndSection

Section Module

# Load freetype
# Load xtt
Load  extmod
Load  glx
#Load  dri
Load  dbe
#Load  record
Load  xtrap
Load  type1
Load  speedo
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol Auto
Option  Device /dev/sysmouse
Option  ZAxisMapping 4 5
EndSection

Section InputDevice
Identifier  Keyboard0
Driver  keyboard
Option  XkbModel pc104
Option  XkbLayout us
EndSection

Section Monitor
Identifier   Monitor0
HorizSync31.5 - 48.5
VertRefresh  50.0 - 70.0
EndSection

Section Device
Identifier  Card0
Driver  nvidia
Option  NvAgp 1 #was tring this out 
#when I
was experimenting with the nvidia AGPGART
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
DefaultDepth 24
SubSection Display
Depth 24
Modes1024x768 800x600
640x480
EndSubSection
EndSection
 Are you using *dm (xdm, kdm, gdm, etc) or are you
 booting to CLI and doing
 startx?  I've had more issues with kdm and my FX
 than with CLI + startx.

Actually I start up in the CLI and startx to get in

 As for AGP and kernel config, I've gotten mine
 working with AGP in the
 kernel and compiled with no optimizations other than
 CPUTYPE.

I will try again with it like that

 Once I get a look at your files (and compare them to
 mine at home) I might
 have some more suggestions.
 
 chris

That would be very cool = )

Don

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Nvidia Drivers + FreeBSD AGP + Big textures = Problems

[Karel J. Bosschaart]

On Fri, Aug 01, 2003 at 12:25:37AM +0200, Mica Telodico wrote:
 Hi all ,
 
 I'm getting problems with FreeBSD AGP driver and
 Nvidia DRVs.
 
 My system is composed by a Geforce3 Ti200 (by
 Creative) and an MSI KT4Ultra (KT400) . I've decided
 to use the FreeBSD AGP driver instead of the Nvidia
 one , but I'm getting the following problem:
 
 When I play to Enemy Territory (for now is the only
 game that I've tried) using HIGH_QUALITY options
 (1280x1024 + all 32bit +all effect to their max +
 texture compression NO ) after few time the textures
 start to flicker. The colors are strange , and after 1
 minute the Video Card starts to draw the textures in
 the wrong place (for examples it draws the texture of
 a  tank on the floor ) , after a couple of seconds all
 the screen starts to flicker , and then the system
 freeze. If I only enable the Texture compression (and
 so I reduce a bit the dimension of the textures) the
 problem disappears , and also if I reduce the quality
 of the textures (also reducing the size). I think that
 may be a memory allocation error in the AGP when it
 needs to write into the main memory , or something
 like this. 

Is the main menu OK now?

 Someone have my problem? 

Not this problem (well didn't try those options), but
the Nvidia driver causes my ttyv's to fail miserably:
any switch to a ttyv will cause the system to freeze,
which means that I can't even shutdown properly since
the system goes to ttyv first when doing a shutdown
from KDE/kdm. Games run fine though.

 Can someone solve it? I'd like to use the FreeBSD drv
 instead of the Nvidia one (I'd like to be more open
 that I can) 
 
After all, the Nvidia driver is still beta, so problems
can be expected.

 Ah , Nvidia AGP drv solve the problem 
 
I also have Nvidia AGP. FreeBSD AGP didn't change anything
for me with my ttyv problem. I'll try another resolution
(already tried colordepth). Have a look at 
http://www.soulwax.net/nvidia/faq.shtml ,
I found this an excellent FAQ.

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

Nvidia Drivers + FreeBSD AGP + Big textures = Problems

[Mica Telodico]

Hi all ,

I'm getting problems with FreeBSD AGP driver and
Nvidia DRVs.

My system is composed by a Geforce3 Ti200 (by
Creative) and an MSI KT4Ultra (KT400) . I've decided
to use the FreeBSD AGP driver instead of the Nvidia
one , but I'm getting the following problem:

When I play to Enemy Territory (for now is the only
game that I've tried) using HIGH_QUALITY options
(1280x1024 + all 32bit +all effect to their max +
texture compression NO ) after few time the textures
start to flicker. The colors are strange , and after 1
minute the Video Card starts to draw the textures in
the wrong place (for examples it draws the texture of
a  tank on the floor ) , after a couple of seconds all
the screen starts to flicker , and then the system
freeze. If I only enable the Texture compression (and
so I reduce a bit the dimension of the textures) the
problem disappears , and also if I reduce the quality
of the textures (also reducing the size). I think that
may be a memory allocation error in the AGP when it
needs to write into the main memory , or something
like this. 

Someone have my problem? 

Can someone solve it? I'd like to use the FreeBSD drv
instead of the Nvidia one (I'd like to be more open
that I can) 

Ah , Nvidia AGP drv solve the problem 

Thanks  for your help

Bye 

Marcello 

__
Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro 
Anti-spam
http://it.yahoo.com/mail_it/foot/?http://it.mail.yahoo.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Problem with NVIDIA drivers

[ydg]

one thing you'll want to do is comment out the Load dri line in
XF86Config.
what is /var/log/XFree86.0.log report?
you might also want to try making your default depth 16, ive had
experiences with 24bpp creating unexpected problems.

yussef

 On Fri, 25 Jul 2003
15:54:24-0400 Marc LeMaire[EMAIL PROTECTED] wrote:

 Hello,
 I've installed the nvidia drivers from the ports. I've followed the 
 instructions, and all the files are in their directory. But when I'm 
 trying to start X, the machine crash and reboot. I've looked into the 
 archives to see if someone had this problem but they are presently 
 unavailable.
 
 p.s.: Could it be possible that this line that I received everytime
 that I fired up X be the culprit ?
 bad display name gryphon.krockmitaine.org:0 in remove command.
 How can I correct this ?
 
 This is a fresh install, 4.8, with the latest cvsup. Also, the
 equipment is a GeForce 256 with a ViewSonic E790. I've included my
 XF86Config and the config file for my kernel.
 
 Thanks in advance
 
 Marc
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Problem with NVIDIA drivers

[Marc LeMaire]

Hello,
I've installed the nvidia drivers from the ports. I've followed the 
instructions, and all the files are in their directory. But when I'm 
trying to start X, the machine crash and reboot. I've looked into the 
archives to see if someone had this problem but they are presently 
unavailable.

p.s.: Could it be possible that this line that I received everytime that 
I fired up X be the culprit ?
bad display name gryphon.krockmitaine.org:0 in remove command. How 
can I correct this ?

This is a fresh install, 4.8, with the latest cvsup. Also, the equipment 
is a GeForce 256 with a ViewSonic E790. I've included my XF86Config and 
the config file for my kernel.

Thanks in advance

Marc
Section ServerLayout
Identifier XFree86 Configured
Screen  0  Screen0 0 0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
EndSection

Section Files
RgbPath  /usr/X11R6/lib/X11/rgb
ModulePath   /usr/X11R6/lib/modules
FontPath /usr/X11R6/lib/X11/fonts/misc/
FontPath /usr/X11R6/lib/X11/fonts/Speedo/
FontPath /usr/X11R6/lib/X11/fonts/Type1/
FontPath /usr/X11R6/lib/X11/fonts/75dpi/
FontPath /usr/X11R6/lib/X11/fonts/100dpi/
EndSection

Section Module
Load  dbe
Load  dri
Load  extmod
Load  glx
Load  record
Load  xtrap
Load  speedo
Load  type1
EndSection

Section InputDevice
Identifier  Keyboard0
Driver  keyboard
Option  XkbRules xfree86
Option  XkbModel pc101
Option  XkbLayout us
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol Auto
Option  Device /dev/sysmouse
Option  Buttons 5
Option  ZAxisMapping 4 5
EndSection

Section Monitor

#DisplaySize  360   270 # mm
Identifier   Mon Moniteur
VendorName   VSC
ModelNameE790-3
HorizSync30.0 - 95.0
VertRefresh  50.0 - 160.0
Option  DPMS
EndSection

Section Device

### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz
### [arg]: arg optional
#Option SWcursor  # [bool]
#Option HWcursor  # [bool]
#Option NoAccel   # [bool]
#Option ShowCache # [bool]
#Option ShadowFB  # [bool]
#Option UseFBDev  # [bool]
#Option Rotate# [str]
#Option VideoKey  # i
#Option FlatPanel # [bool]
#Option FPDither  # [bool]
#Option CrtcNumber# i
Identifier  Ma Carte
Driver  nvidia
VendorName  nVidia Corporation
BoardName   NV10 [GeForce 256 SDR]
#ChipSet GeForce 256
BusID   PCI:1:0:0
EndSection

Section Screen
Identifier Screen0
Device Ma Carte
MonitorMon Moniteur
DefaultDepth 24
SubSection Display
Depth 1
Virtual 1152 864
Virtual 1024 768
EndSubSection
SubSection Display
Depth 4
Virtual 1152 864
Virtual 1024 768
EndSubSection
SubSection Display
Depth 8
Virtual 1152 864
Virtual 1024 768
EndSubSection
SubSection Display
Depth 15
Virtual 1152 864
Virtual 1024 768
EndSubSection
SubSection Display
Depth 16
Virtual 1152 864
Virtual 1024 768
EndSubSection
SubSection Display
Depth 24
Virtual 1152 864
Virtual 1024 768
EndSubSection
EndSection

#
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ./LINT configuration file. If you are
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.51.2.2 2003/03/25 23:35:15 jhb Exp $

machine i386
#cpuI386_CPU
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident

Re: Problem with NVIDIA drivers

[Vulpes Velox]

After installing it run XFree86 -configure and that should create a config file.
Test that. If it still crashes it is most likely a driver problem.

On Fri, 25 Jul 2003 15:54:24 -0400
Marc LeMaire [EMAIL PROTECTED] wrote:

 Hello,
 I've installed the nvidia drivers from the ports. I've followed the 
 instructions, and all the files are in their directory. But when I'm 
 trying to start X, the machine crash and reboot. I've looked into the 
 archives to see if someone had this problem but they are presently 
 unavailable.
 
 p.s.: Could it be possible that this line that I received everytime that 
 I fired up X be the culprit ?
 bad display name gryphon.krockmitaine.org:0 in remove command. How 
 can I correct this ?
 
 This is a fresh install, 4.8, with the latest cvsup. Also, the equipment 
 is a GeForce 256 with a ViewSonic E790. I've included my XF86Config and 
 the config file for my kernel.
 
 Thanks in advance
 
 Marc
 

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

Re: Problem with NVIDIA drivers

[sweetleaf]

On Fri, 25 Jul 2003 15:54:24 -0400
Marc LeMaire [EMAIL PROTECTED] wrote:

 Hello,
 I've installed the nvidia drivers from the ports. I've followed the 
 instructions, and all the files are in their directory. But when I'm 
 trying to start X, the machine crash and reboot. I've looked into the 
 archives to see if someone had this problem but they are presently 
 unavailable.
 
 p.s.: Could it be possible that this line that I received everytime that 
 I fired up X be the culprit ?
 bad display name gryphon.krockmitaine.org:0 in remove command. How 
 can I correct this ?
 
 This is a fresh install, 4.8, with the latest cvsup. Also, the equipment 
 is a GeForce 256 with a ViewSonic E790. I've included my XF86Config and 
 the config file for my kernel.
 
 Thanks in advance
 
 Marc
 


Nvidia just released a new freebsd drivers tar ball. I am using it fine, just go to 
their website and d/l the freebsd tar.gz untar it and type make setup.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

5.1 and nvidia drivers

[brakje]

hi! 
 
I have just installed 5.1 on my laptop and everything was going smooth. but 
when i was trying to install the nvidia drivers for my GF2 go i got stuck. 
They worked perfectly in 5.0, but now i get some errors while doing make 
setup. 
In 5.1, modules are put in /boot/modules/ instead of /modules as they where in 
5.0. The release notes for 5.1 say modules designed for 4.x are likely to 
panic when loaded into a 5.1 kernel. 
I think this might be the reason behind the error. if so, is it possible to 
use this driver?  
I need this driver to enable agp support and to use my s-video output. As far 
as i know the drivers in XFree86 for my video adapter does not support this. 
 
# make setup 
=== module 
cc -O -pipe -mcpu=pentiumpro 
-I/usr/download/NVIDIA_FreeBSD-1.0-3203/module/../src -D__KERNEL__ 
-DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=3203 -DNV_UNIX   
-DNV_BSD   -DNVCPU_X86  -D_KERNEL -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I-  
-I/usr/download/NVIDIA_FreeBSD-1.0-3203/module/../src -I. -I@ -I@/dev 
-I@/../include -fno-common  -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -fformat-extensions -std=c99 -c 
/usr/download/NVIDIA_FreeBSD-1.0-3203/module/../src/nvidia_dev.c 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:23: warning: 
initialization makes integer from pointer without a cast 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:24: warning: 
initialization makes integer from pointer without a cast 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:25: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:26: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:27: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:28: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:29: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:30: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:31: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:32: warning: 
initialization makes pointer from integer without a cast 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:33: warning: 
initialization from incompatible pointer type 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:35: warning: 
initialization makes pointer from integer without a cast 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:39: warning: excess 
elements in struct initializer 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:39: warning: (near 
initialization for `nvidia_dev_cdevsw') 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:140: conflicting types 
for `nvidia_dev_mmap' 
/usr/download/NVIDIA_FreeBSD-1.0-3203/src/nvidia_dev.c:20: previous 
declaration of `nvidia_dev_mmap' 
*** Error code 1 
 
Stop in /usr/download/NVIDIA_FreeBSD-1.0-3203/module. 
*** Error code 1 
 
Stop in /usr/download/NVIDIA_FreeBSD-1.0-3203. 
 
kjetil 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Nvidia drivers

[Wayne Swart]

Hi there everyone

A while ago I emailed this list regarding my network interfaces stop
responding when I am running x windows.
I have now installed the latest nvidia drivers on FreeBSD 4.8-RC and I
have found that it is indeed those drivers that causes that.

I have two dc type cards in my box, and if i start transfering a lot of
data through dc0, it stops responding (only when xwindows is running)

I am using an AMD K-6 333, is it because of this?
Has anyone seen this before?
Thanks

Wayne

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

Uninstalling nvidia drivers on freebsd-5.0

[Erik Sabowski]

I installed the nvidia drivers on freebsd-5.0 by commenting out
the appropiate lines in src/nv-freebsd.h, but all it does is make
my machine freeze. So I tried to go back to the nv driver, but
when I did X gave me this error:

Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is 
unresolved!
Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is 
unresolved!

I reinstalled Mesa thinging that might fix the problem (since it
seems to be a gl thing) but that didn't change anything. So I
tried to just take Load dri out of the X config file. When I
do that, X crashes on [GLX]: Calling GlxExtensionInit. How can I
restore my system back to normal? Or better yet, how can I get the
nvidia drivers working on freebsd-5.0? I think I have heard at
least one person on here had them working.

erik

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

RE: nVidia drivers w/ 4.7-RELEASE

[Gautham Ganapathy]

On Friday, November 22, 2002 5:05 AM, Laszlo Vagner wrote

 lewiz wrote:

 On Thu, Nov 21, 2002 at 08:25:39AM +0530, Gautham Ganapathy wrote:
 
 
 Will the nvidia drivers work with 4.7-RELEASE? 4.7-STABLE won't have
 ISOs, right?
 
 
 
 You need 4.7-STABLE to get the NVidia drivers working.  I don't know
 exactly what -RELEASE is missing but I'm quite sure.  There are still
 problems with them (they hang my machine all the time) so be prepared
 for trouble.
 
 -lewiz.
 
 
 
 Yes I just installed the nvidia drivers for my TI 4200 card and
 ymessenger crashes the machine,
 it just makes some clicking sounds from the sound card and
 then reboots
 without syncing disks.

 I am running  Xfree 4.2.0_1, libraries 4.2.1_3, server 4.2.1_5 and
 client 4.2.1_2 this is greater than
 required by the nvidia instructions. The driver did get rid of the
 missing pixels in the xterm window
 but you cant use the machine reliable anymore.

 I am getting this error in netscape now also, translation
 table unknown
 keysym name somekeyname
 I tried deinstalling it and reinstalling 4.8 without change.

 next is to change the xserver driver and see if that changes anything.


I just downloaded and tried out quake3 demo. worked fine. no crashes. i
have to try out the timedemo and ut2003. Running 'timedemo demoname'
will give me the fps, right? Rather than instantaneous, can I get an
average fps with this command?

Regards
Gautham


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

New NVidia drivers and tuxracer

[Grzybowski Rafa]

Hi,

I have installed lately released NVidia driver on 4.7-STABLE and everything 
looked fine till I tried to run tuxracer. I got:

Fatal signal: Segmentation Fault (SDL Parachute Deployed)

I tried to use NVidia AGP Gart driver and system one with the same effect.

Any ideas ?

Thank You


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

Re: nVidia drivers w/ 4.7-RELEASE

[Karel J. Bosschaart]

On Sun, Nov 24, 2002 at 10:11:28AM +, Alex Drummond wrote:
 Interesting to see that other people found they worked fine with RELEASE. I 
 had to update my system to STABLE before GLX would work, although I had no 
 problems otherwise. Also, GLX would only work with an XFree86 installed from 
 ports, not with one installed from the FreeBSD binaries on xfree86.org (my 
 original X installation was done befroe XFree86 4 was in ports).

This is documented in the accompanied README.txt:

 - XFree86 4.2 or greater, the precise minimum packages required are:
   XFree86-4.2.0_1
   XFree86-libraries-4.2.1_1.tgz
   XFree86-Server-4.2.1_3
   XFree86-clients-4.2.1_1.tgz
   (please note that it is *not* sufficient to download 4.2.1 binaries from 
   ftp.xfree86.org -- you must have XFree86-Server-4.2.1_3 or later).

Notice the port version with the packages.
Karel.

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

Re: nVidia drivers w/ 4.7-RELEASE

[Alex Drummond]

Interesting to see that other people found they worked fine with RELEASE. I 
had to update my system to STABLE before GLX would work, although I had no 
problems otherwise. Also, GLX would only work with an XFree86 installed from 
ports, not with one installed from the FreeBSD binaries on xfree86.org (my 
original X installation was done befroe XFree86 4 was in ports).

Alex

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

Re: nVidia drivers w/ 4.7-RELEASE

[lewiz]

On Thu, Nov 21, 2002 at 08:25:39AM +0530, Gautham Ganapathy wrote:
 Will the nvidia drivers work with 4.7-RELEASE? 4.7-STABLE won't have
 ISOs, right?

You need 4.7-STABLE to get the NVidia drivers working.  I don't know
exactly what -RELEASE is missing but I'm quite sure.  There are still
problems with them (they hang my machine all the time) so be prepared
for trouble.

-lewiz.

-- 
There's no future in time travel.

--|| url: http://lewiz.info/ | http://www.westwood.karoo.net/pgpkey ||--



msg09657/pgp0.pgp
Description: PGP signature

Re: nVidia drivers w/ 4.7-RELEASE

[Kenneth Culver]

I had them working just fine on -RELEASE.

Ken

On Thu, 21 Nov 2002, lewiz wrote:

 On Thu, Nov 21, 2002 at 08:25:39AM +0530, Gautham Ganapathy wrote:
  Will the nvidia drivers work with 4.7-RELEASE? 4.7-STABLE won't have
  ISOs, right?

 You need 4.7-STABLE to get the NVidia drivers working.  I don't know
 exactly what -RELEASE is missing but I'm quite sure.  There are still
 problems with them (they hang my machine all the time) so be prepared
 for trouble.

 -lewiz.

 --
 There's no future in time travel.
 
 --|| url: http://lewiz.info/ | http://www.westwood.karoo.net/pgpkey ||--



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

nVidia drivers w/ 4.7-RELEASE

[Gautham Ganapathy]

Hi

Will the nvidia drivers work with 4.7-RELEASE? 4.7-STABLE won't have
ISOs, right?

Regards
Gautham


BEGIN:VCARD
VERSION:2.1
N:Ganapathy;Gautham
FN:Gautham Ganapathy
ORG:Wipro Technologies;TI PIC (DSP)
TITLE:Technical Support Engg
TEL;WORK;VOICE:+91-80-8520408x4277
TEL;HOME;VOICE:+91-80-6542292
TEL;CELL;VOICE:+91-9844263180
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;Plot No 76,=0D=0AElectronics City,=0D=0AHosur Road;Bangalore;Karnataka;;In=
dia
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Plot No 76,=0D=0AElectronics City,=0D=0AHosur Road=0D=0ABangalore, Karnataka=
=0D=0AIndia
ADR;HOME;ENCODING=QUOTED-PRINTABLE:;;B010, Spartacus Apartments,=0D=0AJayanagar 4T Block, 30th Cross,;Bangalore=
;Karnataka;561041;India
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:B010, Spartacus Apartments,=0D=0AJayanagar 4T Block, 30th Cross,=0D=0ABangal=
ore, Karnataka 561041=0D=0AIndia
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
EMAIL;INTERNET:[EMAIL PROTECTED]
EMAIL;INTERNET:[EMAIL PROTECTED]
EMAIL;INTERNET:[EMAIL PROTECTED]
EMAIL;INTERNET:[EMAIL PROTECTED]
REV:20020920T053748Z
END:VCARD

Re: nVidia drivers w/ 4.7-RELEASE

[Matthew Seaman]

On Wed, Nov 20, 2002 at 01:38:56PM +0530, Gautham Ganapathy wrote:

 Will the nvidia drivers work with 4.7-RELEASE?

The release notes say:

 - FreeBSD -STABLE, version 4.7 or later

which should include 4.7-RELEASE.  There have been various reports
around the mailing lists of people getting the nvidia drivers working
on other versions, including 5-CURRENT, but NVIDIA won't support that.

 4.7-STABLE won't have ISOs, right?

Probably not, but see http://www.freebsdmirrors.org/FBSDsites.php3 for
sites where you can do a network install of a more recent snapshot.
Or read Chapter 21 of the Handbook about how to track -STABLE:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
  Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK

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

Re: nVidia drivers w/ 4.7-RELEASE

[John Bleichert]

On Wed, 20 Nov 2002, Kenneth Culver wrote:

 Date: Wed, 20 Nov 2002 07:43:39 -0500 (EST)
 From: Kenneth Culver [EMAIL PROTECTED]
 To: Gautham Ganapathy [EMAIL PROTECTED]
 Cc: Questions @ FreeBSD [EMAIL PROTECTED]
 Subject: Re: nVidia drivers w/ 4.7-RELEASE
 
 It works fine with -RELEASE.
 
 Ken
 
 On Wed, 20 Nov 2002, Gautham Ganapathy wrote:
 
  Hi
 
  Will the nvidia drivers work with 4.7-RELEASE? 4.7-STABLE won't have
  ISOs, right?
 
  Regards
  Gautham
 
 
 
 

Yep - I'm using them on 4.7-RELEASE right now. Myth II runs great :)

#  John Bleichert 
#  http://vonbek.dhs.org/latest.jpg


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

Re: nVidia drivers w/ 4.7-RELEASE

[Kenneth Culver]

 Yep - I'm using them on 4.7-RELEASE right now. Myth II runs great :)

Quake 3, Wolfenstein, tuxracer, and UT2003 all work on my machine.
However, ut2003 refused to work on my hardware while using the nvidia
agpgart. I had to switch to using FreeBSD's agpgart.

Ken


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