Re: nvidia-driver rebooting machine on X startup
In some situations that will not work... for example 7.2 completely fails on a P35 chipset... see my update post for some ideas. --Aryeh On 9/25/07, Mel <[EMAIL PROTECTED]> wrote: > On Tuesday 25 September 2007 14:22:56 falz wrote: > > > Maybe someone can build a WITNESS/DDB kernel, since dumping seems to be > > > failing? > > > > I compiled these options in last night, but I'm afraid I'm not quite > > sure what special steps I need to do to utilize those options, if any. > > I built that kernel, booted into it, started xorg with the nvidia > > driver, it immediately reboots just as it did before. > > > > Something else that's odd that just started happening that's similar > > to the original poster- their xorg.conf was being truncated to zero > > bytes. Mine somehow gets changed to what appears to be a different > > version. The bottom line in it is about 20 "U"s, and the 'Driver > > "nvidia"' lines I added were gone. I have several xorg.conf files > > named other things, but none have these characteristics. > > > I fear it's a hard reboot then, if DDB doesn't catch anything. DDB is a kernel > debugger, even if dump isn't on, it will catch panic stages. > > Stray bytes and truncated files are another sign of hard reboot. I'm afraid > only nvidia can catch this one. Try downgrading to Xorg 7.2 and use the 97xx > series of the driver, then freeze it until you see some solution posted :p > > -- > Mel > ___ > 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: nvidia-driver rebooting machine on X startup
On Tuesday 25 September 2007 14:22:56 falz wrote: > > Maybe someone can build a WITNESS/DDB kernel, since dumping seems to be > > failing? > > I compiled these options in last night, but I'm afraid I'm not quite > sure what special steps I need to do to utilize those options, if any. > I built that kernel, booted into it, started xorg with the nvidia > driver, it immediately reboots just as it did before. > > Something else that's odd that just started happening that's similar > to the original poster- their xorg.conf was being truncated to zero > bytes. Mine somehow gets changed to what appears to be a different > version. The bottom line in it is about 20 "U"s, and the 'Driver > "nvidia"' lines I added were gone. I have several xorg.conf files > named other things, but none have these characteristics. I fear it's a hard reboot then, if DDB doesn't catch anything. DDB is a kernel debugger, even if dump isn't on, it will catch panic stages. Stray bytes and truncated files are another sign of hard reboot. I'm afraid only nvidia can catch this one. Try downgrading to Xorg 7.2 and use the 97xx series of the driver, then freeze it until you see some solution posted :p -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
> Maybe someone can build a WITNESS/DDB kernel, since dumping seems to be > failing? I compiled these options in last night, but I'm afraid I'm not quite sure what special steps I need to do to utilize those options, if any. I built that kernel, booted into it, started xorg with the nvidia driver, it immediately reboots just as it did before. Something else that's odd that just started happening that's similar to the original poster- their xorg.conf was being truncated to zero bytes. Mine somehow gets changed to what appears to be a different version. The bottom line in it is about 20 "U"s, and the 'Driver "nvidia"' lines I added were gone. I have several xorg.conf files named other things, but none have these characteristics. --falz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On 9/24/07, Mel <[EMAIL PROTECTED]> wrote: > On Monday 24 September 2007 21:14:03 falz wrote: > > I came across this thread on freebsd-questions after some searching on > > google. I have the exact same issue as others here- if xorg is started > > with 'nvidia' as the driver, instant reboot. However, my machine is a > > 100% fresh install with things compiled from source this weekend. > > However, I did have to install some binary vncserver packages, but > > they have since been removed. > > > > I did the 'xorg' meta port which got me the current xorg-7.3_1. The > > machine I did the install on was running Debian Unstable for about a > > year without issue with the same hardware (two cards for 3 monitors): > > > > Sep 24 13:41:24 falz kernel: nvidia0: mem > > 0xdd00-0xddff,0xb000-0xbfff,0xde00-0xdeff irq > > 16 at device 0.0 on pci1 > > Sep 24 13:41:24 falz kernel: nvidia0: [GIANT-LOCKED] > > Sep 24 13:41:24 falz kernel: nvidia1: mem > > 0xdb00-0xdbff,0xc000-0xcfff irq 18 at device 2.0 on > > pci3 > > Sep 24 13:41:24 falz kernel: nvidia1: [GIANT-LOCKED] > > > > I forgot, but was there one person in the thread that has only 1 monitor > attached to 1 card? Cause you're the 3rd I see with multiple monitor issues. > Ironically, we have one system with CRT + TV-OUT through one card, with no > issues whatsoever (500GB HDD, DVDRW, rock on!). However I turned off Xinerama > support from the get go and use TwinView. > > With all the Xorg 7.3 issues, I have not gone that road nor plan to anytime > soon. > > I also think we've had all the different cards by now, a quatro, GeForce 5k, > 7k, 6k... > > Maybe someone can build a WITNESS/DDB kernel, since dumping seems to be > failing? I was the single monitor issue, on the single monitor it does not reboot unless you set probe_all_gpu's *BUT* it does fail to reconize all nVidia cards (so does nv)... as far I can tell neither drive understands 64bit io space and PCI/AGP... the clue is the addr conflicts that everyone seems to get... btw I think it might of fried my 8k but at least gives me vesa with no weird video probs on the 5200 GT I have now (1024x768 ;-()). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On Monday 24 September 2007 21:14:03 falz wrote: > I came across this thread on freebsd-questions after some searching on > google. I have the exact same issue as others here- if xorg is started > with 'nvidia' as the driver, instant reboot. However, my machine is a > 100% fresh install with things compiled from source this weekend. > However, I did have to install some binary vncserver packages, but > they have since been removed. > > I did the 'xorg' meta port which got me the current xorg-7.3_1. The > machine I did the install on was running Debian Unstable for about a > year without issue with the same hardware (two cards for 3 monitors): > > Sep 24 13:41:24 falz kernel: nvidia0: mem > 0xdd00-0xddff,0xb000-0xbfff,0xde00-0xdeff irq > 16 at device 0.0 on pci1 > Sep 24 13:41:24 falz kernel: nvidia0: [GIANT-LOCKED] > Sep 24 13:41:24 falz kernel: nvidia1: mem > 0xdb00-0xdbff,0xc000-0xcfff irq 18 at device 2.0 on > pci3 > Sep 24 13:41:24 falz kernel: nvidia1: [GIANT-LOCKED] > I forgot, but was there one person in the thread that has only 1 monitor attached to 1 card? Cause you're the 3rd I see with multiple monitor issues. Ironically, we have one system with CRT + TV-OUT through one card, with no issues whatsoever (500GB HDD, DVDRW, rock on!). However I turned off Xinerama support from the get go and use TwinView. With all the Xorg 7.3 issues, I have not gone that road nor plan to anytime soon. I also think we've had all the different cards by now, a quatro, GeForce 5k, 7k, 6k... Maybe someone can build a WITNESS/DDB kernel, since dumping seems to be failing? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nvidia-driver rebooting machine on X startup
I came across this thread on freebsd-questions after some searching on google. I have the exact same issue as others here- if xorg is started with 'nvidia' as the driver, instant reboot. However, my machine is a 100% fresh install with things compiled from source this weekend. However, I did have to install some binary vncserver packages, but they have since been removed. I did the 'xorg' meta port which got me the current xorg-7.3_1. The machine I did the install on was running Debian Unstable for about a year without issue with the same hardware (two cards for 3 monitors): Sep 24 13:41:24 falz kernel: nvidia0: mem 0xdd00-0xddff,0xb000-0xbfff,0xde00-0xdeff irq 16 at device 0.0 on pci1 Sep 24 13:41:24 falz kernel: nvidia0: [GIANT-LOCKED] Sep 24 13:41:24 falz kernel: nvidia1: mem 0xdb00-0xdbff,0xc000-0xcfff irq 18 at device 2.0 on pci3 Sep 24 13:41:24 falz kernel: nvidia1: [GIANT-LOCKED] I went through many of the steps people spoke of earlier in this thread, which were some AGP workarounds that are mentioned in Chapter 9: /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-100.14.11/doc/README No matter what is done, always an instant reboot if I use the "nvidia" driver in the xorg.conf. Out of curiosity, is anyone actively using xorg-7.3_1 with nvidia-driver-100.14.11 and having it work? I too am not quite sure what to look for in the output of 'ldconfig -r', but I can see that there is nothing linked against any pre-xorg 7.x stuff there: # ldconfig -R | grep X11 | wc -l 0 Also, the person who had things linked that were stale appears to have been having a different problem that does NOT cause a reboot: http://www.nvnews.net/vbulletin/showthread.php?t=94938 Thanks, falz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On 9/18/07, Eric Ekong <[EMAIL PROTECTED]> wrote:
> Seems there is a new driver in ports as of yesterday for nvidia.
> Anyone tried it as of yet?
The update alone hasn't done anything for me, but I'm thinking I'm
suffering from an issue not directly related to the driver itself;
stale libraries like Mel suggested, or something.
I just completed an update to xorg-7.3_1 following the procedure in
UPDATING 20070519. Now running FreeBSD 6.2-RELEASE-p7 and
nvidia-driver-100.14.11 and the reboot still occurs when starting X.
Something else I noticed is that my xorg.conf gets truncated to 0
bytes when I 'startx' and hit a reboot. I can't figure what would
cause this, and it's intermittent (post reboot I'll sometimes see the
file whole whole, sometimes truncated). Must be connected somehow to
the reboot?
On the off chance it had anything to do with stale libraries, how
would I determine which those were and how to right what is wrong? I
don't see anything notable in the output of ldconfig -r, but I'm not
certain I know what to look for. I'll include the ldconfig* related
configurations from rc.conf and ldconfig -r output below. Any other
ideas?
# grep -i ld /etc/{defaults/rc.conf,rc.conf}
/etc/defaults/rc.conf:# to change the default startup behavior of your
system. You should
/etc/defaults/rc.conf:# The ${rc_conf_files} files should only contain
values which override
/etc/defaults/rc.conf:kldxref_enable="NO" # Build linker.hints files
with kldxref(8).
/etc/defaults/rc.conf:kldxref_clobber="NO" # Overwrite old linker.hints at
boot.
/etc/defaults/rc.conf:kldxref_module_path=""# Override
kern.module_path. A ';'-delimited list.
/etc/defaults/rc.conf:pflog_logfile="/var/log/pflog"# where pflogd
should store the logfile
/etc/defaults/rc.conf: # node, you should stop
advertisement.
/etc/defaults/rc.conf:ldconfig_insecure="NO"# Set to YES to disable
ldconfig security checks
/etc/defaults/rc.conf:ldconfig_paths="/usr/lib/compat /usr/X11R6/lib
/usr/local/lib /usr/local/lib/compat/pkg"
/etc/defaults/rc.conf:ldconfig32_paths="/usr/lib32" # 32-bit
compatibility shared library search paths
/etc/defaults/rc.conf:ldconfig_paths_aout="/usr/lib/compat/aout
/usr/X11R6/lib/aout /usr/local/lib/aout"
/etc/defaults/rc.conf:ldconfig_local_dirs="/usr/local/libdata/ldconfig
/usr/X11R6/libdata/ldconfig"
/etc/defaults/rc.conf: # Local directories with ldconfig
configuration files.
/etc/defaults/rc.conf:ldconfig_local32_dirs="/usr/local/libdata/ldconfig32
/usr/X11R6/libdata/ldconfig32"
/etc/defaults/rc.conf: # Local directories with 32-bit
compatibility ldconfig
/var/run/ld-elf.so.hints:
search directories:
/lib:/usr/lib:/usr/lib/compat:/usr/X11R6/lib:/usr/local/lib:/usr/local/lib/compat/pkg:/usr/local/lib/compat:/usr/local/lib/nss
0:-lcrypt.3 => /lib/libcrypt.so.3
1:-lkvm.3 => /lib/libkvm.so.3
2:-lm.4 => /lib/libm.so.4
3:-lmd.3 => /lib/libmd.so.3
4:-lncurses.6 => /lib/libncurses.so.6
5:-lsbuf.3 => /lib/libsbuf.so.3
6:-lutil.5 => /lib/libutil.so.5
7:-lalias.5 => /lib/libalias.so.5
8:-latm.3 => /lib/libatm.so.3
9:-lbegemot.2 => /lib/libbegemot.so.2
10:-lbsnmp.3 => /lib/libbsnmp.so.3
11:-lc.6 => /lib/libc.so.6
12:-lcam.3 => /lib/libcam.so.3
13:-ldevstat.5 => /lib/libdevstat.so.5
14:-ledit.5 => /lib/libedit.so.5
15:-lbsdxml.2 => /lib/libbsdxml.so.2
16:-lgeom.3 => /lib/libgeom.so.3
17:-lgpib.1 => /lib/libgpib.so.1
18:-lipsec.2 => /lib/libipsec.so.2
19:-lipx.3 => /lib/libipx.so.3
20:-lufs.3 => /lib/libufs.so.3
21:-lkiconv.2 => /lib/libkiconv.so.2
22:-lpcap.4 => /lib/libpcap.so.4
23:-lpthread.2 => /lib/libpthread.so.2
24:-lz.3 => /lib/libz.so.3
25:-lreadline.6 => /lib/libreadline.so.6
26:-lcrypto.4 => /lib/libcrypto.so.4
27:-lbsm.1 => /usr/lib/libbsm.so.1
28:-lcom_err.3 => /usr/lib/libcom_err.so.3
29:-lnetgraph.2 => /usr/lib/libnetgraph.so.2
30:-lradius.2 => /usr/lib/libradius.so.2
31:-lrpcsvc.3 => /usr/lib/librpcsvc.so.3
32:-ltacplus.2 => /usr/lib/libtacplus.so.2
33:-lypclnt.2 => /usr/lib/libypclnt.so.2
34:-larchive.2 => /usr/lib/libarchive.so.2
35:-lbluetooth.2 => /usr/lib/libbluetooth.so.2
36:-lbz2.2 => /usr/lib/libbz2.so.2
37:-lc_r.6 => /usr/lib/libc_r.so.6
38:-lcalendar.3 => /usr/lib/libcalendar.so.3
39:-ldevinfo.3 => /usr/lib/libdevinfo.so.3
40:-lfetch.4 => /usr/lib/libfetch.so.4
41:-lform.3 => /usr/lib/libform.so.3
42:-lftpio.6 => /usr/lib/libftpio.so.6
43:-lmagic.2 => /usr/lib/libmagic.so.2
44:-lmemstat.1 => /usr/lib/libmemstat.so.1
45:-lmenu.3 => /usr/lib/libmenu.so.3
46:-lmilter.3 => /usr/lib/libmilter.so.3
47:-lmp.5 => /usr/lib/libmp.so.5
48:-lncp.2 =>
Fwd: nvidia-driver rebooting machine on X startup
-- Forwarded message -- From: Aryeh Friedman <[EMAIL PROTECTED]> Date: Sep 18, 2007 7:00 PM Subject: Re: nvidia-driver rebooting machine on X startup To: Eric Ekong <[EMAIL PROTECTED]> Just tried it and: 1. It is just a ABI upgrade so it doesn't get rejected by 7.3 (same version as the old driver) 2. Doesn't fix any issues with my P35 chipset and a 5400 GS --Aryeh On 9/18/07, Eric Ekong <[EMAIL PROTECTED]> wrote: > Seems there is a new driver in ports as of yesterday for nvidia. > Anyone tried it as of yet? > > Eric > * Mel <[EMAIL PROTECTED]> [070912 17:43]: > > Date: Wed, 12 Sep 2007 23:43:42 +0200 > > From: Mel <[EMAIL PROTECTED]> > > To: freebsd-questions@freebsd.org > > Subject: Re: nvidia-driver rebooting machine on X startup > > > > On Wednesday 12 September 2007 23:21:57 Eric Ekong wrote: > > > * Darren Spruell <[EMAIL PROTECTED]> [070911 19:20]: > > > > Date: Tue, 11 Sep 2007 16:20:00 -0700 > > > > From: Darren Spruell <[EMAIL PROTECTED]> > > > > To: Bruce Cran <[EMAIL PROTECTED]> > > > > Cc: Mel <[EMAIL PROTECTED]>, > > > > freebsd-questions@freebsd.org > > > > Subject: Re: nvidia-driver rebooting machine on X startup > > > > > > > > On 9/11/07, Bruce Cran <[EMAIL PROTECTED]> wrote: > > > > > Mel wrote: > > > > > > There's 3 things left I can think of: > > > > > > - weird module clash > > > > > > - bug in nvidia-driver (I assume you're running Xorg 7.x) > > > > > > - driver was not built against running kernel > > > > > > > > > > I'm seeing a similar problem, but my system spontaneously reboots > > > > > whenever it uses any 3D - for example any of the 3D xscreensaver > > > > > modules in full screen mode. I'm running 7.0-CURRENT and just > > > > > realised I have PREEMPTION enabled since it's now in GENERIC. I > > > > > remember a while ago this caused stability problems with the nvidia > > > > > driver - does anyone know if this could still be a problem? I think > > > > > there's more going on however, since the driver doesn't seem to know > > > > > about my card during bootup (it shows ) though it clearly > > > > > does > > > > > find it when starting Xorg. Going back to the nvidia-driver-96xx > > > > > port > > > > > appears to fix the problems, and that driver does know what nVidia > > > > > card > > > > > I'm using during boot. > > > > > > > > 3 of us have posted a thread on nvidia forums as problem reports; I've > > > > at least tried an older (legacy) driver version to no luck and > > > > eliminated every suggestion I've gotten from the fbsd community as > > > > well. > > > > > > > > If anyone would like, feel free to piggyback on the thread. There's > > > > been no help response on the forums for a couple of days now. > > > > > > > > http://forums.nvidia.com/index.php?showtopic=45590 > > > > > > > > If this *is* an issue with the nvidia driver, is there a good way for > > > > us to alert Nvidia? Customer support, I guess? > > > > > > > > -- > > > > Darren Spruell > > > > [EMAIL PROTECTED] > > > > ___ > > > > freebsd-questions@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to > > > > "[EMAIL PROTECTED]" > > > > > > Seems like even more than that in the freebsd forums located here... > > > > > > http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 > > > > > > Might want to repost here as well. > > > > Hmm: > > http://www.nvnews.net/vbulletin/showpost.php?p=1313960&postcount=2 > > > > My guess is they were in /usr/local/lib/compat/pkg. Any chance you guys have > > stale libraries hiding away (use ldconfig -r when in doubt)? > > > > > > -- > > Mel > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- > === > Eric I. Ekong[EMAIL PROTECTED] > FreeBSD - The Power to Serve http://www.freebsd.org > K Desktop Environment on FreeBSD http://freebsd.kde.org > Enlightenment E16 and E17http://www.e.org > === > > Laws of Serendipity: > > (1) In order to discover anything, you must be looking for > something. > (2) If you wish to make an improved product, you must already > be engaged in making an inferior one. > > ___ > 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: nvidia-driver rebooting machine on X startup
Seems there is a new driver in ports as of yesterday for nvidia. Anyone tried it as of yet? Eric * Mel <[EMAIL PROTECTED]> [070912 17:43]: > Date: Wed, 12 Sep 2007 23:43:42 +0200 > From: Mel <[EMAIL PROTECTED]> > To: freebsd-questions@freebsd.org > Subject: Re: nvidia-driver rebooting machine on X startup > > On Wednesday 12 September 2007 23:21:57 Eric Ekong wrote: > > * Darren Spruell <[EMAIL PROTECTED]> [070911 19:20]: > > > Date: Tue, 11 Sep 2007 16:20:00 -0700 > > > From: Darren Spruell <[EMAIL PROTECTED]> > > > To: Bruce Cran <[EMAIL PROTECTED]> > > > Cc: Mel <[EMAIL PROTECTED]>, > > > freebsd-questions@freebsd.org > > > Subject: Re: nvidia-driver rebooting machine on X startup > > > > > > On 9/11/07, Bruce Cran <[EMAIL PROTECTED]> wrote: > > > > Mel wrote: > > > > > There's 3 things left I can think of: > > > > > - weird module clash > > > > > - bug in nvidia-driver (I assume you're running Xorg 7.x) > > > > > - driver was not built against running kernel > > > > > > > > I'm seeing a similar problem, but my system spontaneously reboots > > > > whenever it uses any 3D - for example any of the 3D xscreensaver > > > > modules in full screen mode. I'm running 7.0-CURRENT and just > > > > realised I have PREEMPTION enabled since it's now in GENERIC. I > > > > remember a while ago this caused stability problems with the nvidia > > > > driver - does anyone know if this could still be a problem? I think > > > > there's more going on however, since the driver doesn't seem to know > > > > about my card during bootup (it shows ) though it clearly does > > > > find it when starting Xorg. Going back to the nvidia-driver-96xx port > > > > appears to fix the problems, and that driver does know what nVidia card > > > > I'm using during boot. > > > > > > 3 of us have posted a thread on nvidia forums as problem reports; I've > > > at least tried an older (legacy) driver version to no luck and > > > eliminated every suggestion I've gotten from the fbsd community as > > > well. > > > > > > If anyone would like, feel free to piggyback on the thread. There's > > > been no help response on the forums for a couple of days now. > > > > > > http://forums.nvidia.com/index.php?showtopic=45590 > > > > > > If this *is* an issue with the nvidia driver, is there a good way for > > > us to alert Nvidia? Customer support, I guess? > > > > > > -- > > > Darren Spruell > > > [EMAIL PROTECTED] > > > ___ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to > > > "[EMAIL PROTECTED]" > > > > Seems like even more than that in the freebsd forums located here... > > > > http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 > > > > Might want to repost here as well. > > Hmm: > http://www.nvnews.net/vbulletin/showpost.php?p=1313960&postcount=2 > > My guess is they were in /usr/local/lib/compat/pkg. Any chance you guys have > stale libraries hiding away (use ldconfig -r when in doubt)? > > > -- > Mel > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- === Eric I. Ekong[EMAIL PROTECTED] FreeBSD - The Power to Serve http://www.freebsd.org K Desktop Environment on FreeBSD http://freebsd.kde.org Enlightenment E16 and E17http://www.e.org === Laws of Serendipity: (1) In order to discover anything, you must be looking for something. (2) If you wish to make an improved product, you must already be engaged in making an inferior one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On Wednesday 12 September 2007 23:21:57 Eric Ekong wrote: > * Darren Spruell <[EMAIL PROTECTED]> [070911 19:20]: > > Date: Tue, 11 Sep 2007 16:20:00 -0700 > > From: Darren Spruell <[EMAIL PROTECTED]> > > To: Bruce Cran <[EMAIL PROTECTED]> > > Cc: Mel <[EMAIL PROTECTED]>, > > freebsd-questions@freebsd.org > > Subject: Re: nvidia-driver rebooting machine on X startup > > > > On 9/11/07, Bruce Cran <[EMAIL PROTECTED]> wrote: > > > Mel wrote: > > > > There's 3 things left I can think of: > > > > - weird module clash > > > > - bug in nvidia-driver (I assume you're running Xorg 7.x) > > > > - driver was not built against running kernel > > > > > > I'm seeing a similar problem, but my system spontaneously reboots > > > whenever it uses any 3D - for example any of the 3D xscreensaver > > > modules in full screen mode. I'm running 7.0-CURRENT and just > > > realised I have PREEMPTION enabled since it's now in GENERIC. I > > > remember a while ago this caused stability problems with the nvidia > > > driver - does anyone know if this could still be a problem? I think > > > there's more going on however, since the driver doesn't seem to know > > > about my card during bootup (it shows ) though it clearly does > > > find it when starting Xorg. Going back to the nvidia-driver-96xx port > > > appears to fix the problems, and that driver does know what nVidia card > > > I'm using during boot. > > > > 3 of us have posted a thread on nvidia forums as problem reports; I've > > at least tried an older (legacy) driver version to no luck and > > eliminated every suggestion I've gotten from the fbsd community as > > well. > > > > If anyone would like, feel free to piggyback on the thread. There's > > been no help response on the forums for a couple of days now. > > > > http://forums.nvidia.com/index.php?showtopic=45590 > > > > If this *is* an issue with the nvidia driver, is there a good way for > > us to alert Nvidia? Customer support, I guess? > > > > -- > > Darren Spruell > > [EMAIL PROTECTED] > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > Seems like even more than that in the freebsd forums located here... > > http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 > > Might want to repost here as well. Hmm: http://www.nvnews.net/vbulletin/showpost.php?p=1313960&postcount=2 My guess is they were in /usr/local/lib/compat/pkg. Any chance you guys have stale libraries hiding away (use ldconfig -r when in doubt)? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
Mel wrote: > On Wednesday 12 September 2007 01:42:28 Philip M. Gollucci wrote: >> Darren Spruell wrote: >>> If this *is* an issue with the nvidia driver, is there a good way for >>> us to alert Nvidia? Customer support, I guess? >> I've had the same issue, but I think I solved it since its working for >> me. If I had to guess, this was Jul 27, 2007 that I went through this. >> >> I did something similar or harder in May 2007, but the driver versions >> were older then and so was the ports tree -- it was also on 6.2-release-p2. >> >> uname -a >> FreeBSD philip.hq.rws 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Jul 26 >> 16:44:37 EDT 2007 >> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 >> >> nvidia0: port 0xdc80-0xdcff mem >> 0xde00-0xdeff,0xc000-0xcfff,0xdc00-0xddff irq 16 >> at device 0.0 on pci1 >> nvidia0: [GIANT-LOCKED] >> nvidia0: [ITHREAD] > > Did any of you determine whether it's a kernel crash or magical reboot by > allowing the kernel to dump and/or running WITNESS on -current? I did not -- it was my office desktop and I didn't have time to futz with it much. Yeah I know don't run current then. -- Philip M. Gollucci ([EMAIL PROTECTED]) c:323.219.4708 o:703.749.9295x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
* Darren Spruell <[EMAIL PROTECTED]> [070911 19:20]: > Date: Tue, 11 Sep 2007 16:20:00 -0700 > From: Darren Spruell <[EMAIL PROTECTED]> > To: Bruce Cran <[EMAIL PROTECTED]> > Cc: Mel <[EMAIL PROTECTED]>, > freebsd-questions@freebsd.org > Subject: Re: nvidia-driver rebooting machine on X startup > > On 9/11/07, Bruce Cran <[EMAIL PROTECTED]> wrote: > > Mel wrote: > > > There's 3 things left I can think of: > > > - weird module clash > > > - bug in nvidia-driver (I assume you're running Xorg 7.x) > > > - driver was not built against running kernel > > > > > > > I'm seeing a similar problem, but my system spontaneously reboots > > whenever it uses any 3D - for example any of the 3D xscreensaver modules > > in full screen mode. I'm running 7.0-CURRENT and just realised I have > > PREEMPTION enabled since it's now in GENERIC. I remember a while ago > > this caused stability problems with the nvidia driver - does anyone know > > if this could still be a problem? I think there's more going on > > however, since the driver doesn't seem to know about my card during > > bootup (it shows ) though it clearly does find it when starting > > Xorg. Going back to the nvidia-driver-96xx port appears to fix the > > problems, and that driver does know what nVidia card I'm using during boot. > > 3 of us have posted a thread on nvidia forums as problem reports; I've > at least tried an older (legacy) driver version to no luck and > eliminated every suggestion I've gotten from the fbsd community as > well. > > If anyone would like, feel free to piggyback on the thread. There's > been no help response on the forums for a couple of days now. > > http://forums.nvidia.com/index.php?showtopic=45590 > > If this *is* an issue with the nvidia driver, is there a good way for > us to alert Nvidia? Customer support, I guess? > > -- > Darren Spruell > [EMAIL PROTECTED] > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Seems like even more than that in the freebsd forums located here... http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 Might want to repost here as well. Eric -- === Eric I. Ekong[EMAIL PROTECTED] FreeBSD - The Power to Serve http://www.freebsd.org K Desktop Environment on FreeBSD http://freebsd.kde.org Enlightenment E16 and E17http://www.e.org === Laws of Serendipity: (1) In order to discover anything, you must be looking for something. (2) If you wish to make an improved product, you must already be engaged in making an inferior one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
I setup to save dumpcrash, nothing was saved so I think it is just a reboot. Eric * Mel <[EMAIL PROTECTED]> [070912 17:12]: > Date: Wed, 12 Sep 2007 23:12:21 +0200 > From: Mel <[EMAIL PROTECTED]> > To: freebsd-questions@freebsd.org > Cc: Bruce Cran <[EMAIL PROTECTED]>, Darren Spruell <[EMAIL PROTECTED]>, > "Philip M. Gollucci" <[EMAIL PROTECTED]> > Subject: Re: nvidia-driver rebooting machine on X startup > > On Wednesday 12 September 2007 01:42:28 Philip M. Gollucci wrote: > > Darren Spruell wrote: > > > If this *is* an issue with the nvidia driver, is there a good way for > > > us to alert Nvidia? Customer support, I guess? > > > > I've had the same issue, but I think I solved it since its working for > > me. If I had to guess, this was Jul 27, 2007 that I went through this. > > > > I did something similar or harder in May 2007, but the driver versions > > were older then and so was the ports tree -- it was also on 6.2-release-p2. > > > > uname -a > > FreeBSD philip.hq.rws 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Jul 26 > > 16:44:37 EDT 2007 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > > > nvidia0: port 0xdc80-0xdcff mem > > 0xde00-0xdeff,0xc000-0xcfff,0xdc00-0xddff irq 16 > > at device 0.0 on pci1 > > nvidia0: [GIANT-LOCKED] > > nvidia0: [ITHREAD] > > Did any of you determine whether it's a kernel crash or magical reboot by > allowing the kernel to dump and/or running WITNESS on -current? > > -- > Mel > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- === Eric I. Ekong[EMAIL PROTECTED] FreeBSD - The Power to Serve http://www.freebsd.org K Desktop Environment on FreeBSD http://freebsd.kde.org Enlightenment E16 and E17http://www.e.org === Laws of Serendipity: (1) In order to discover anything, you must be looking for something. (2) If you wish to make an improved product, you must already be engaged in making an inferior one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On Wednesday 12 September 2007 01:42:28 Philip M. Gollucci wrote: > Darren Spruell wrote: > > If this *is* an issue with the nvidia driver, is there a good way for > > us to alert Nvidia? Customer support, I guess? > > I've had the same issue, but I think I solved it since its working for > me. If I had to guess, this was Jul 27, 2007 that I went through this. > > I did something similar or harder in May 2007, but the driver versions > were older then and so was the ports tree -- it was also on 6.2-release-p2. > > uname -a > FreeBSD philip.hq.rws 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Jul 26 > 16:44:37 EDT 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > nvidia0: port 0xdc80-0xdcff mem > 0xde00-0xdeff,0xc000-0xcfff,0xdc00-0xddff irq 16 > at device 0.0 on pci1 > nvidia0: [GIANT-LOCKED] > nvidia0: [ITHREAD] Did any of you determine whether it's a kernel crash or magical reboot by allowing the kernel to dump and/or running WITNESS on -current? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
Darren Spruell wrote: > If this *is* an issue with the nvidia driver, is there a good way for > us to alert Nvidia? Customer support, I guess? I've had the same issue, but I think I solved it since its working for me. If I had to guess, this was Jul 27, 2007 that I went through this. I did something similar or harder in May 2007, but the driver versions were older then and so was the ports tree -- it was also on 6.2-release-p2. uname -a FreeBSD philip.hq.rws 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Jul 26 16:44:37 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 nvidia0: port 0xdc80-0xdcff mem 0xde00-0xdeff,0xc000-0xcfff,0xdc00-0xddff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] ls -ld /var/db/pkg/nvidia* drwxr-xr-x 2 root wheel - 512B Sep 4 18:34:47 2007 /var/db/pkg/nvidia-driver-100.14.11/ ls -1d /var/db/pkg/xorg-* /var/db/pkg/xorg-7.2/ /var/db/pkg/xorg-apps-7.2/ /var/db/pkg/xorg-cf-files-1.0.2_2/ /var/db/pkg/xorg-docs-1.3,1/ /var/db/pkg/xorg-drivers-7.2/ /var/db/pkg/xorg-fonts-100dpi-7.2/ /var/db/pkg/xorg-fonts-7.2/ /var/db/pkg/xorg-fonts-75dpi-7.2/ /var/db/pkg/xorg-fonts-cyrillic-7.2/ /var/db/pkg/xorg-fonts-miscbitmaps-7.2/ /var/db/pkg/xorg-fonts-truetype-7.2/ /var/db/pkg/xorg-fonts-type1-7.2/ /var/db/pkg/xorg-libraries-7.2_1/ /var/db/pkg/xorg-protos-7.2/ /var/db/pkg/xorg-server-1.2.0_2,1/ /var/db/pkg/xorg-server-1.2.99.903_1,1/ cat /var/db/ports/nvidia-driver/options # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for nvidia-driver-1.0.9746_5 _OPTIONS_READ=nvidia-driver-1.0.9746_5 WITHOUT_FREEBSD_AGP=true WITHOUT_VM86_INT10CALL=true WITHOUT_ACPI=true WITH_LINUX=true grep LINUX /etc/make.conf OVERRIDE_LINUX_BASE_PORT=fc6 grep compat /etc/sysctl.conf compat.linux.osrelease=2.6.16 cd /usr/ports/x11/nvidia-driver-100> find . . ./files ./files/pkg-message.in ./Makefile ./distinfo ./pkg-descr ./pkg-plist I believe I deleted all the patch files here other then you see listed and tweaked the Makefile accordingly. I also edited the source code to remove a #ifdef around FreeBSD 7.x so that it used the 6.x version even though its on 7.x. (argument list to the function was wrong) This might be fixed by now. This was a hard compile error though, not the coredumps and reboots I do know this drove me f'ing bonkers when I tried to set this and was going to file a PR but $work never game me time. Philip M. Gollucci ([EMAIL PROTECTED]) c:323.219.4708 o:703.749.9295x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On 9/11/07, Bruce Cran <[EMAIL PROTECTED]> wrote: > Mel wrote: > > There's 3 things left I can think of: > > - weird module clash > > - bug in nvidia-driver (I assume you're running Xorg 7.x) > > - driver was not built against running kernel > > > > I'm seeing a similar problem, but my system spontaneously reboots > whenever it uses any 3D - for example any of the 3D xscreensaver modules > in full screen mode. I'm running 7.0-CURRENT and just realised I have > PREEMPTION enabled since it's now in GENERIC. I remember a while ago > this caused stability problems with the nvidia driver - does anyone know > if this could still be a problem? I think there's more going on > however, since the driver doesn't seem to know about my card during > bootup (it shows ) though it clearly does find it when starting > Xorg. Going back to the nvidia-driver-96xx port appears to fix the > problems, and that driver does know what nVidia card I'm using during boot. 3 of us have posted a thread on nvidia forums as problem reports; I've at least tried an older (legacy) driver version to no luck and eliminated every suggestion I've gotten from the fbsd community as well. If anyone would like, feel free to piggyback on the thread. There's been no help response on the forums for a couple of days now. http://forums.nvidia.com/index.php?showtopic=45590 If this *is* an issue with the nvidia driver, is there a good way for us to alert Nvidia? Customer support, I guess? -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
Mel wrote: There's 3 things left I can think of: - weird module clash - bug in nvidia-driver (I assume you're running Xorg 7.x) - driver was not built against running kernel I'm seeing a similar problem, but my system spontaneously reboots whenever it uses any 3D - for example any of the 3D xscreensaver modules in full screen mode. I'm running 7.0-CURRENT and just realised I have PREEMPTION enabled since it's now in GENERIC. I remember a while ago this caused stability problems with the nvidia driver - does anyone know if this could still be a problem? I think there's more going on however, since the driver doesn't seem to know about my card during bootup (it shows ) though it clearly does find it when starting Xorg. Going back to the nvidia-driver-96xx port appears to fix the problems, and that driver does know what nVidia card I'm using during boot. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" Depth 8 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" #Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" #Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Screen 1" Device "GeForce 6600GT_1" Monitor"monitor1" DefaultDepth24 DefaultFbBPP32 Option "HWcursor" "off" Option "DPMS" "on" Option "DigitalScreen2" "on" Option "Busmastering" "on" Option "XFB" "on" Option "AddARGBGLXVisuals" "on" Option "Composite" "on" SubSection "Display" #Modes"1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" Depth 8 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" #Modes"1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" #Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Extensions" Option "Composite" "enable" EndSection X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD blackguy.unixtechs.org 6.2-STABLE FreeBSD 6.2-STABLE #22: Mon Aug 13 23:00:44 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLACKGUY i386 Build Date: 31 August 2007 Eric * Mel <[EMAIL PROTECTED]> [070908 10:59]: > Date: Sat, 8 Sep 2007 16:59:32 +0200 > From: Mel <[EMAIL PROTECTED]> > To: freebsd-questions@freebsd.org > Subject: Re: nvidia-driver rebooting machine on X startup > > On Saturday 08 September 2007 00:43:59 Darren Spruell wrote: > > On 9/7/07, Mel <[EMAIL PROTECTED]> wrote: > > > On Friday 07 September 2007 19:43:03 Darren Spruell wrote: > > > > On 9/6/07, Derek Ragona <[EMAIL PROTECTED]> wrote: > > > > > At 03:10 PM 9/6/2007, Darren Spruell wrote: > > > > > > > > > > Wondering if this is a known issue, or if anyone has suggestions to > > > > > get it working...? > > > > > > > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > > > > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > > > > Linux compatibility enabled. After loading modules 'linux' and > > > > > 'nvidia', I do: > > > > > > > > > > # X -configure > > > > > # X -config /root/xorg.conf.new > > > > > > > > > > At this point the system spontaneously reboots. 'X -configure' runs > > > > > fine and produces a configuration without issue, but the reboot > > > > > occcurs when launching X. Nothing is output to screen (it flickers > > > > > as if starting X), and nothing is written to /var/log/Xorg.0.log. I > > > > > do get the same behavior if running 'xorgcfg'. > > > > > > > > > > Card info: > > > > > > > > > > "NV41 [Quadro
Re: nvidia-driver rebooting machine on X startup
* Mel <[EMAIL PROTECTED]> [070908 10:59]: > Date: Sat, 8 Sep 2007 16:59:32 +0200 > From: Mel <[EMAIL PROTECTED]> > To: freebsd-questions@freebsd.org > Subject: Re: nvidia-driver rebooting machine on X startup > > On Saturday 08 September 2007 00:43:59 Darren Spruell wrote: > > On 9/7/07, Mel <[EMAIL PROTECTED]> wrote: > > > On Friday 07 September 2007 19:43:03 Darren Spruell wrote: > > > > On 9/6/07, Derek Ragona <[EMAIL PROTECTED]> wrote: > > > > > At 03:10 PM 9/6/2007, Darren Spruell wrote: > > > > > > > > > > Wondering if this is a known issue, or if anyone has suggestions to > > > > > get it working...? > > > > > > > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > > > > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > > > > Linux compatibility enabled. After loading modules 'linux' and > > > > > 'nvidia', I do: > > > > > > > > > > # X -configure > > > > > # X -config /root/xorg.conf.new > > > > > > > > > > At this point the system spontaneously reboots. 'X -configure' runs > > > > > fine and produces a configuration without issue, but the reboot > > > > > occcurs when launching X. Nothing is output to screen (it flickers > > > > > as if starting X), and nothing is written to /var/log/Xorg.0.log. I > > > > > do get the same behavior if running 'xorgcfg'. > > > > > > > > > > Card info: > > > > > > > > > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > > > > > > > > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > > > > > rev=0xa2 hdr=0x00 > > > > > vendor = 'NVIDIA Corporation' > > > > > class= display > > > > > subclass = VGA > > > > > > > > > > I've tried an alternate version of the binary driver > > > > > (nvidia-driver-96xx) to see if there was any change, and it also > > > > > reboots on X startup. > > > > > > > > > > > > > > > -- > > > > > Check your AGP settings and consult the readme, chapter 9, for the > > > > > latest driver. You should be running the latest driver with your > > > > > card. > > > > > > > > > > Make sure you have the correct AGP settings, either letting FreeBSD > > > > > do it in the kernel or disable the kernel and let the Nvidia driver > > > > > manage it. > > > > > > > > So, I'm not having terrific luck with any combination of settings I > > > > try. > > > > > > > > The latest FreeBSD driver release from Nvidia is the same as the > > > > version in the ports tree. This is what I've installed. > > > > > > > > Attempting the AGPGART route (building the driver with > > > > "WITH_FREEBSD_AGP=yes" and disabling NvAgp support in xorg.conf) still > > > > results in a reboot. > > > > > > > > Going the NvAGP route (Building without support for AGPGART, setting > > > > NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in > > > > /boot/device.hints) also results in a reboot when X starts. One thing > > > > I notice here; when I specify hint.agp.0.disabled=1, and check the > > > > output of 'kldstat -v' after booting, I still see several agp drivers > > > > loaded: > > > > > > > > $ kldstat -v |grep -i agp > > > > 387 pci/agp_ali > > > > 388 pci/agp_amd > > > > 389 pci/agp_amd64 > > > > 390 pci/agp_ati > > > > 391 pci/agp_i810 > > > > 392 pci/agp_intel > > > > 393 pci/agp_nvidia > > > > 394 pci/agp_sis > > > > 395 pci/agp_via > > > > > > > > Is this a problem? > > > > > > > > I suspect a couple of problems with what I'm doing. Number one, > > > > there's several knobs to turn (in the driver, in the OS, etc.) and > > > > it's possible I'm not getting the correct combination. Other thing is, > > > > I'v
Re: nvidia-driver rebooting machine on X startup
On Saturday 08 September 2007 00:43:59 Darren Spruell wrote: > On 9/7/07, Mel <[EMAIL PROTECTED]> wrote: > > On Friday 07 September 2007 19:43:03 Darren Spruell wrote: > > > On 9/6/07, Derek Ragona <[EMAIL PROTECTED]> wrote: > > > > At 03:10 PM 9/6/2007, Darren Spruell wrote: > > > > > > > > Wondering if this is a known issue, or if anyone has suggestions to > > > > get it working...? > > > > > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > > > Linux compatibility enabled. After loading modules 'linux' and > > > > 'nvidia', I do: > > > > > > > > # X -configure > > > > # X -config /root/xorg.conf.new > > > > > > > > At this point the system spontaneously reboots. 'X -configure' runs > > > > fine and produces a configuration without issue, but the reboot > > > > occcurs when launching X. Nothing is output to screen (it flickers > > > > as if starting X), and nothing is written to /var/log/Xorg.0.log. I > > > > do get the same behavior if running 'xorgcfg'. > > > > > > > > Card info: > > > > > > > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > > > > > > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > > > > rev=0xa2 hdr=0x00 > > > > vendor = 'NVIDIA Corporation' > > > > class= display > > > > subclass = VGA > > > > > > > > I've tried an alternate version of the binary driver > > > > (nvidia-driver-96xx) to see if there was any change, and it also > > > > reboots on X startup. > > > > > > > > > > > > -- > > > > Check your AGP settings and consult the readme, chapter 9, for the > > > > latest driver. You should be running the latest driver with your > > > > card. > > > > > > > > Make sure you have the correct AGP settings, either letting FreeBSD > > > > do it in the kernel or disable the kernel and let the Nvidia driver > > > > manage it. > > > > > > So, I'm not having terrific luck with any combination of settings I > > > try. > > > > > > The latest FreeBSD driver release from Nvidia is the same as the > > > version in the ports tree. This is what I've installed. > > > > > > Attempting the AGPGART route (building the driver with > > > "WITH_FREEBSD_AGP=yes" and disabling NvAgp support in xorg.conf) still > > > results in a reboot. > > > > > > Going the NvAGP route (Building without support for AGPGART, setting > > > NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in > > > /boot/device.hints) also results in a reboot when X starts. One thing > > > I notice here; when I specify hint.agp.0.disabled=1, and check the > > > output of 'kldstat -v' after booting, I still see several agp drivers > > > loaded: > > > > > > $ kldstat -v |grep -i agp > > > 387 pci/agp_ali > > > 388 pci/agp_amd > > > 389 pci/agp_amd64 > > > 390 pci/agp_ati > > > 391 pci/agp_i810 > > > 392 pci/agp_intel > > > 393 pci/agp_nvidia > > > 394 pci/agp_sis > > > 395 pci/agp_via > > > > > > Is this a problem? > > > > > > I suspect a couple of problems with what I'm doing. Number one, > > > there's several knobs to turn (in the driver, in the OS, etc.) and > > > it's possible I'm not getting the correct combination. Other thing is, > > > I've been told by a technician that this is a PCI Express video card, > > > so would AGP even come into play? > > > > Probably not. I'm seeing the same thing on one machine, no AGP on MB, and > > agp kernel modules loaded, but nvidia-driver doesn't care about it. > > Let's kill all red herrings: > > - Is COMPAT5X in the kernel? > > COMPAT5X doesn't show up anywhere in /usr/src/; I do have 'options > COMPAT_FREEBSD5' defined, though (stock SMP kernel). > > > - Does running `nvidia-xconfig --query-gpu-info' reboot the system? > > - If you do not load the nvidia kernel module, but use Xorg's "nv" driver > > does this reboot the system? > > No, doesn't reboot the system. Output attached below. > > With the 'nv' driver, X starts fine. I don't use it because I don't > have success with the two output displays and xinerama window sizing. > > nvidia-xconfig --query-gpu-info: > > Number of GPUs: 1 > > GPU #0: > Name : Quadro FX 3450/4000 SDI > PCI BusID : PCI:7:0:0 > > Number of Display Devices: 2 > > Display Device 0 (CRT-0): > EDID Name : DELL 2001FP > Minimum HorizSync : 31.000 kHz > Maximum HorizSync : 80.000 kHz > Minimum VertRefresh : 56 Hz > Maximum VertRefresh : 76 Hz > Maximum PixelClock: 162.000 MHz > Maximum Width : 1600 pixels > Maximum Height: 1200 pixels > Preferred Width : 1600 pixels > Preferred Height : 1200 pixels > Preferred VertRefresh : 60 Hz > Physical Width: 410 mm > Physical Height : 310 mm > > Display Device 1 (CRT-1): > EDID Name
Re: nvidia-driver rebooting machine on X startup
On 9/7/07, Mel <[EMAIL PROTECTED]> wrote: > On Friday 07 September 2007 19:43:03 Darren Spruell wrote: > > On 9/6/07, Derek Ragona <[EMAIL PROTECTED]> wrote: > > > At 03:10 PM 9/6/2007, Darren Spruell wrote: > > > > > > Wondering if this is a known issue, or if anyone has suggestions to > > > get it working...? > > > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > > Linux compatibility enabled. After loading modules 'linux' and > > > 'nvidia', I do: > > > > > > # X -configure > > > # X -config /root/xorg.conf.new > > > > > > At this point the system spontaneously reboots. 'X -configure' runs > > > fine and produces a configuration without issue, but the reboot > > > occcurs when launching X. Nothing is output to screen (it flickers as > > > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > > > get the same behavior if running 'xorgcfg'. > > > > > > Card info: > > > > > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > > > > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > > > rev=0xa2 hdr=0x00 > > > vendor = 'NVIDIA Corporation' > > > class= display > > > subclass = VGA > > > > > > I've tried an alternate version of the binary driver > > > (nvidia-driver-96xx) to see if there was any change, and it also > > > reboots on X startup. > > > > > > > > > -- > > > Check your AGP settings and consult the readme, chapter 9, for the > > > latest driver. You should be running the latest driver with your card. > > > > > > Make sure you have the correct AGP settings, either letting FreeBSD do > > > it in the kernel or disable the kernel and let the Nvidia driver manage > > > it. > > > > So, I'm not having terrific luck with any combination of settings I try. > > > > The latest FreeBSD driver release from Nvidia is the same as the > > version in the ports tree. This is what I've installed. > > > > Attempting the AGPGART route (building the driver with > > "WITH_FREEBSD_AGP=yes" and disabling NvAgp support in xorg.conf) still > > results in a reboot. > > > > Going the NvAGP route (Building without support for AGPGART, setting > > NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in > > /boot/device.hints) also results in a reboot when X starts. One thing > > I notice here; when I specify hint.agp.0.disabled=1, and check the > > output of 'kldstat -v' after booting, I still see several agp drivers > > loaded: > > > > $ kldstat -v |grep -i agp > > 387 pci/agp_ali > > 388 pci/agp_amd > > 389 pci/agp_amd64 > > 390 pci/agp_ati > > 391 pci/agp_i810 > > 392 pci/agp_intel > > 393 pci/agp_nvidia > > 394 pci/agp_sis > > 395 pci/agp_via > > > > Is this a problem? > > > > I suspect a couple of problems with what I'm doing. Number one, > > there's several knobs to turn (in the driver, in the OS, etc.) and > > it's possible I'm not getting the correct combination. Other thing is, > > I've been told by a technician that this is a PCI Express video card, > > so would AGP even come into play? > > Probably not. I'm seeing the same thing on one machine, no AGP on MB, and agp > kernel modules loaded, but nvidia-driver doesn't care about it. > Let's kill all red herrings: > - Is COMPAT5X in the kernel? COMPAT5X doesn't show up anywhere in /usr/src/; I do have 'options COMPAT_FREEBSD5' defined, though (stock SMP kernel). > - Does running `nvidia-xconfig --query-gpu-info' reboot the system? > - If you do not load the nvidia kernel module, but use Xorg's "nv" driver does > this reboot the system? No, doesn't reboot the system. Output attached below. With the 'nv' driver, X starts fine. I don't use it because I don't have success with the two output displays and xinerama window sizing. nvidia-xconfig --query-gpu-info: Number of GPUs: 1 GPU #0: Name : Quadro FX 3450/4000 SDI PCI BusID : PCI:7:0:0 Number of Display Devices: 2 Display Device 0 (CRT-0): EDID Name : DELL 2001FP Minimum HorizSync : 31.000 kHz Maximum HorizSync : 80.000 kHz Minimum VertRefresh : 56 Hz Maximum VertRefresh : 76 Hz Maximum PixelClock: 162.000 MHz Maximum Width : 1600 pixels Maximum Height: 1200 pixels Preferred Width : 1600 pixels Preferred Height : 1200 pixels Preferred VertRefresh : 60 Hz Physical Width: 410 mm Physical Height : 310 mm Display Device 1 (CRT-1): EDID Name : DELL 2001FP Minimum HorizSync : 31.000 kHz Maximum HorizSync : 80.000 kHz Minimum VertRefresh : 56 Hz Maximum VertRefresh : 76 Hz Maximum PixelClock: 162.000 MHz Maximum Width : 1600 pixels Maximum Height: 1200 pixels Preferred Width
Re: nvidia-driver rebooting machine on X startup
On Friday 07 September 2007 19:43:03 Darren Spruell wrote: > On 9/6/07, Derek Ragona <[EMAIL PROTECTED]> wrote: > > At 03:10 PM 9/6/2007, Darren Spruell wrote: > > > > Wondering if this is a known issue, or if anyone has suggestions to > > get it working...? > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > Linux compatibility enabled. After loading modules 'linux' and > > 'nvidia', I do: > > > > # X -configure > > # X -config /root/xorg.conf.new > > > > At this point the system spontaneously reboots. 'X -configure' runs > > fine and produces a configuration without issue, but the reboot > > occcurs when launching X. Nothing is output to screen (it flickers as > > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > > get the same behavior if running 'xorgcfg'. > > > > Card info: > > > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > > rev=0xa2 hdr=0x00 > > vendor = 'NVIDIA Corporation' > > class= display > > subclass = VGA > > > > I've tried an alternate version of the binary driver > > (nvidia-driver-96xx) to see if there was any change, and it also > > reboots on X startup. > > > > > > -- > > Check your AGP settings and consult the readme, chapter 9, for the > > latest driver. You should be running the latest driver with your card. > > > > Make sure you have the correct AGP settings, either letting FreeBSD do > > it in the kernel or disable the kernel and let the Nvidia driver manage > > it. > > So, I'm not having terrific luck with any combination of settings I try. > > The latest FreeBSD driver release from Nvidia is the same as the > version in the ports tree. This is what I've installed. > > Attempting the AGPGART route (building the driver with > "WITH_FREEBSD_AGP=yes" and disabling NvAgp support in xorg.conf) still > results in a reboot. > > Going the NvAGP route (Building without support for AGPGART, setting > NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in > /boot/device.hints) also results in a reboot when X starts. One thing > I notice here; when I specify hint.agp.0.disabled=1, and check the > output of 'kldstat -v' after booting, I still see several agp drivers > loaded: > > $ kldstat -v |grep -i agp > 387 pci/agp_ali > 388 pci/agp_amd > 389 pci/agp_amd64 > 390 pci/agp_ati > 391 pci/agp_i810 > 392 pci/agp_intel > 393 pci/agp_nvidia > 394 pci/agp_sis > 395 pci/agp_via > > Is this a problem? > > I suspect a couple of problems with what I'm doing. Number one, > there's several knobs to turn (in the driver, in the OS, etc.) and > it's possible I'm not getting the correct combination. Other thing is, > I've been told by a technician that this is a PCI Express video card, > so would AGP even come into play? Probably not. I'm seeing the same thing on one machine, no AGP on MB, and agp kernel modules loaded, but nvidia-driver doesn't care about it. Let's kill all red herrings: - Is COMPAT5X in the kernel? - Does running `nvidia-xconfig --query-gpu-info' reboot the system? - If you do not load the nvidia kernel module, but use Xorg's "nv" driver does this reboot the system? Determine cause of reboot: echo dumpdev="AUTO" >>/etc/rc.conf /etc/rc.d/dumpon start Now, if it reboots again and no core is found, the kernel didn't crash but an error occured in the hardware layer at which point I'd hit nvidia forums. If there's a coredump: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html and file PR. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On 9/6/07, Derek Ragona <[EMAIL PROTECTED]> wrote: > > At 03:10 PM 9/6/2007, Darren Spruell wrote: > > Wondering if this is a known issue, or if anyone has suggestions to > get it working...? > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > Linux compatibility enabled. After loading modules 'linux' and > 'nvidia', I do: > > # X -configure > # X -config /root/xorg.conf.new > > At this point the system spontaneously reboots. 'X -configure' runs > fine and produces a configuration without issue, but the reboot > occcurs when launching X. Nothing is output to screen (it flickers as > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > get the same behavior if running 'xorgcfg'. > > Card info: > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > rev=0xa2 hdr=0x00 > vendor = 'NVIDIA Corporation' > class= display > subclass = VGA > > I've tried an alternate version of the binary driver > (nvidia-driver-96xx) to see if there was any change, and it also > reboots on X startup. > -- > Check your AGP settings and consult the readme, chapter 9, for the latest > driver. You should be running the latest driver with your card. > > Make sure you have the correct AGP settings, either letting FreeBSD do it > in the kernel or disable the kernel and let the Nvidia driver manage it. So, I'm not having terrific luck with any combination of settings I try. The latest FreeBSD driver release from Nvidia is the same as the version in the ports tree. This is what I've installed. Attempting the AGPGART route (building the driver with "WITH_FREEBSD_AGP=yes" and disabling NvAgp support in xorg.conf) still results in a reboot. Going the NvAGP route (Building without support for AGPGART, setting NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in /boot/device.hints) also results in a reboot when X starts. One thing I notice here; when I specify hint.agp.0.disabled=1, and check the output of 'kldstat -v' after booting, I still see several agp drivers loaded: $ kldstat -v |grep -i agp 387 pci/agp_ali 388 pci/agp_amd 389 pci/agp_amd64 390 pci/agp_ati 391 pci/agp_i810 392 pci/agp_intel 393 pci/agp_nvidia 394 pci/agp_sis 395 pci/agp_via Is this a problem? I suspect a couple of problems with what I'm doing. Number one, there's several knobs to turn (in the driver, in the OS, etc.) and it's possible I'm not getting the correct combination. Other thing is, I've been told by a technician that this is a PCI Express video card, so would AGP even come into play? DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On 9/6/07, Jona Joachim <[EMAIL PROTECTED]> wrote: > On Thu, 6 Sep 2007 13:10:42 -0700 > "Darren Spruell" <[EMAIL PROTECTED]> wrote: > > > Wondering if this is a known issue, or if anyone has suggestions to > > get it working...? > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > Linux compatibility enabled. After loading modules 'linux' and > > 'nvidia', I do: > > > > # X -configure > > # X -config /root/xorg.conf.new > > > > At this point the system spontaneously reboots. 'X -configure' runs > > fine and produces a configuration without issue, but the reboot > > occcurs when launching X. Nothing is output to screen (it flickers as > > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > > get the same behavior if running 'xorgcfg'. > > Did you reinstall/upgrade X after having installed nvidia-driver? > X actually overwrites libraries that nvidia-driver installs so you have > to reinstall nvidia-driver every time you upgrade X. > I remember having had some bad crashes some time ago because X overwrote > nvidia GLX libraries. > > Best regards, > Jona > Nope - driver was the most recent thing installed. I'm looking into AGP options as suggested earlier... didn't realize that this _needed_ AGP support to function. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On Thu, 6 Sep 2007 13:10:42 -0700 "Darren Spruell" <[EMAIL PROTECTED]> wrote: > Wondering if this is a known issue, or if anyone has suggestions to > get it working...? > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > Linux compatibility enabled. After loading modules 'linux' and > 'nvidia', I do: > > # X -configure > # X -config /root/xorg.conf.new > > At this point the system spontaneously reboots. 'X -configure' runs > fine and produces a configuration without issue, but the reboot > occcurs when launching X. Nothing is output to screen (it flickers as > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > get the same behavior if running 'xorgcfg'. Did you reinstall/upgrade X after having installed nvidia-driver? X actually overwrites libraries that nvidia-driver installs so you have to reinstall nvidia-driver every time you upgrade X. I remember having had some bad crashes some time ago because X overwrote nvidia GLX libraries. Best regards, Jona ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On Friday 07 September 2007 00:16:44 Darren Spruell wrote: > On 9/6/07, Mel <[EMAIL PROTECTED]> wrote: > > On Thursday 06 September 2007 22:10:42 Darren Spruell wrote: > > > Wondering if this is a known issue, or if anyone has suggestions to > > > get it working...? > > > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > > Linux compatibility enabled. After loading modules 'linux' and > > > 'nvidia', I do: > > > > > > # X -configure > > > # X -config /root/xorg.conf.new > > > > > > At this point the system spontaneously reboots. 'X -configure' runs > > > fine and produces a configuration without issue, but the reboot > > > occcurs when launching X. Nothing is output to screen (it flickers as > > > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > > > get the same behavior if running 'xorgcfg'. > > > > > > Card info: > > > > > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > > > > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > > > rev=0xa2 hdr=0x00 > > > vendor = 'NVIDIA Corporation' > > > class= display > > > subclass = VGA > > > > > > Section "Device" > > > Identifier "Card0" > > > Driver "nvidia" > > > VendorName "nVidia Corporation" > > > BoardName "NV41 [Quadro FX 3450/4000 SDI]" > > > BusID "PCI:7:0:0" > > > EndSection > > > > Removing BusID do anything? All those Displays sounds a bit much too. I > > *strongly* recommend using nvidia-xconfig (x11/nvidia-config). > > Commenting BusID has the same effect - prompt reboot. > > The Display subsections are pretty standard for every X configuration > I've ever used; why would they cause a problem in this case? Cause I checked 3 working nvidia xorg configs for 3 different cards and none of them has Section Display in them, let alone 20 of them :p > > And anything /var/log/Xorg.0.log? Using nvAgp or FreeBSD Agp? > > No, nothing gets to the log before reboot occurs. > > Not using either of nvAgp or FreeBSD Agp, that I'm aware of. I did not > enable FREEBSD_AGP at build time. Run nvidia-xconfig, it'll generate a much cleaner xorg.conf file, enable nvAgp and load a few less extensions. If that one works, you can start diffing and adding things again to figure out the cause (if you're interested :p). Also check /boot/device.hints and disable Agp there. A GeForce 6200 for instance, insists on it, while other cards don't, but I never had one reboot the machine. I just get: agp0: mem 0xf800-0xfbff at device 0.0 on pci0 NVRM: detected agp.ko, aborting NVIDIA AGP setup! echo 'hint.agp.0.disabled="1"' >>/boot/device.hints should do it. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
On 9/6/07, Mel <[EMAIL PROTECTED]> wrote: > On Thursday 06 September 2007 22:10:42 Darren Spruell wrote: > > Wondering if this is a known issue, or if anyone has suggestions to > > get it working...? > > > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > > Linux compatibility enabled. After loading modules 'linux' and > > 'nvidia', I do: > > > > # X -configure > > # X -config /root/xorg.conf.new > > > > At this point the system spontaneously reboots. 'X -configure' runs > > fine and produces a configuration without issue, but the reboot > > occcurs when launching X. Nothing is output to screen (it flickers as > > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > > get the same behavior if running 'xorgcfg'. > > > > Card info: > > > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > > rev=0xa2 hdr=0x00 > > vendor = 'NVIDIA Corporation' > > class= display > > subclass = VGA > > > Section "Device" > > Identifier "Card0" > > Driver "nvidia" > > VendorName "nVidia Corporation" > > BoardName "NV41 [Quadro FX 3450/4000 SDI]" > > BusID "PCI:7:0:0" > > EndSection > > Removing BusID do anything? All those Displays sounds a bit much too. I > *strongly* recommend using nvidia-xconfig (x11/nvidia-config). Commenting BusID has the same effect - prompt reboot. The Display subsections are pretty standard for every X configuration I've ever used; why would they cause a problem in this case? > And anything /var/log/Xorg.0.log? Using nvAgp or FreeBSD Agp? No, nothing gets to the log before reboot occurs. Not using either of nvAgp or FreeBSD Agp, that I'm aware of. I did not enable FREEBSD_AGP at build time. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver rebooting machine on X startup
At 03:10 PM 9/6/2007, Darren Spruell wrote: Wondering if this is a known issue, or if anyone has suggestions to get it working...? Running FreeBSD 6.2-RELEASE-p4 SMP i386. I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), Linux compatibility enabled. After loading modules 'linux' and 'nvidia', I do: # X -configure # X -config /root/xorg.conf.new At this point the system spontaneously reboots. 'X -configure' runs fine and produces a configuration without issue, but the reboot occcurs when launching X. Nothing is output to screen (it flickers as if starting X), and nothing is written to /var/log/Xorg.0.log. I do get the same behavior if running 'xorgcfg'. Card info: "NV41 [Quadro FX 3450/4000 SDI] rev 162" [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= display subclass = VGA I've tried an alternate version of the binary driver (nvidia-driver-96xx) to see if there was any change, and it also reboots on X startup. sysctl.conf, dmesg, and Xorg configuration included below. sysctl.conf: # Recommended settings from xine package: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 # Local settings vfs.usermount=1 /var/run/dmesg.boot Copyright (c) 1992-2007 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 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP acpi_alloc_wakeup_handler: can't alloc wake memory Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz (2327.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f7 Stepping = 7 Features=0xbfebfbff Features2=0x4e3bd,CX16,,,> AMD Features=0x2010 AMD Features2=0x1 Cores per package: 4 real memory = 3219169280 (3070 MB) avail memory = 3140694016 (2995 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 netsmb_dev: loaded ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: irq 16 at device 1.0 on pci2 pci4: on pcib4 pcib5: at device 0.3 on pci1 pci5: on pcib5 fwohci0: mem 0xdceff000-0xdcef irq 26 at device 5.0 on pci5 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:00:d1:00:80:35:7a:57 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:d1:35:7a:57 fwe0: Ethernet address: 02:00:d1:35:7a:57 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib6: at device 3.0 on pci0 pci6: on pcib6 pcib7: at device 4.0 on pci0 pci7: on pcib7 nvidia0: mem 0xdd00-0xddff,0xc000-0xcfff,0xde00-0xdeff irq 16 at device 0.0 on pci7 nvidia0: [GIANT-LOCKED] pcib8: at device 5.0 on pci0 pci8: on pcib8 pcib9: at device 6.0 on pci0 pci9: on pcib9 pcib10: at device 7.0 on pci0 pci10: on pcib10 pci0: at device 27.0 (no driver attached) pcib11: irq 16 at device 28.0 on pci0 pci11: on pcib11 bge0: mem 0xdccf-0xdccf irq 16 at device 0.0 on pci11 bge0: firmware handshake timed out miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:1a:a0:ac:eb:69 uhci0: port 0xff80-0xff9f irq 21 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 22 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2
Re: nvidia-driver rebooting machine on X startup
On Thursday 06 September 2007 22:10:42 Darren Spruell wrote: > Wondering if this is a known issue, or if anyone has suggestions to > get it working...? > > Running FreeBSD 6.2-RELEASE-p4 SMP i386. > > I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), > Linux compatibility enabled. After loading modules 'linux' and > 'nvidia', I do: > > # X -configure > # X -config /root/xorg.conf.new > > At this point the system spontaneously reboots. 'X -configure' runs > fine and produces a configuration without issue, but the reboot > occcurs when launching X. Nothing is output to screen (it flickers as > if starting X), and nothing is written to /var/log/Xorg.0.log. I do > get the same behavior if running 'xorgcfg'. > > Card info: > > "NV41 [Quadro FX 3450/4000 SDI] rev 162" > > [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de > rev=0xa2 hdr=0x00 > vendor = 'NVIDIA Corporation' > class= display > subclass = VGA > Section "Device" > Identifier "Card0" > Driver "nvidia" > VendorName "nVidia Corporation" > BoardName "NV41 [Quadro FX 3450/4000 SDI]" > BusID "PCI:7:0:0" > EndSection Removing BusID do anything? All those Displays sounds a bit much too. I *strongly* recommend using nvidia-xconfig (x11/nvidia-config). And anything /var/log/Xorg.0.log? Using nvAgp or FreeBSD Agp? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nvidia-driver rebooting machine on X startup
Wondering if this is a known issue, or if anyone has suggestions to get it working...? Running FreeBSD 6.2-RELEASE-p4 SMP i386. I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), Linux compatibility enabled. After loading modules 'linux' and 'nvidia', I do: # X -configure # X -config /root/xorg.conf.new At this point the system spontaneously reboots. 'X -configure' runs fine and produces a configuration without issue, but the reboot occcurs when launching X. Nothing is output to screen (it flickers as if starting X), and nothing is written to /var/log/Xorg.0.log. I do get the same behavior if running 'xorgcfg'. Card info: "NV41 [Quadro FX 3450/4000 SDI] rev 162" [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= display subclass = VGA I've tried an alternate version of the binary driver (nvidia-driver-96xx) to see if there was any change, and it also reboots on X startup. sysctl.conf, dmesg, and Xorg configuration included below. sysctl.conf: # Recommended settings from xine package: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 # Local settings vfs.usermount=1 /var/run/dmesg.boot Copyright (c) 1992-2007 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 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP acpi_alloc_wakeup_handler: can't alloc wake memory Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz (2327.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f7 Stepping = 7 Features=0xbfebfbff Features2=0x4e3bd,CX16,,,> AMD Features=0x2010 AMD Features2=0x1 Cores per package: 4 real memory = 3219169280 (3070 MB) avail memory = 3140694016 (2995 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 netsmb_dev: loaded ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: irq 16 at device 1.0 on pci2 pci4: on pcib4 pcib5: at device 0.3 on pci1 pci5: on pcib5 fwohci0: mem 0xdceff000-0xdcef irq 26 at device 5.0 on pci5 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:00:d1:00:80:35:7a:57 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:d1:35:7a:57 fwe0: Ethernet address: 02:00:d1:35:7a:57 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib6: at device 3.0 on pci0 pci6: on pcib6 pcib7: at device 4.0 on pci0 pci7: on pcib7 nvidia0: mem 0xdd00-0xddff,0xc000-0xcfff,0xde00-0xdeff irq 16 at device 0.0 on pci7 nvidia0: [GIANT-LOCKED] pcib8: at device 5.0 on pci0 pci8: on pcib8 pcib9: at device 6.0 on pci0 pci9: on pcib9 pcib10: at device 7.0 on pci0 pci10: on pcib10 pci0: at device 27.0 (no driver attached) pcib11: irq 16 at device 28.0 on pci0 pci11: on pcib11 bge0: mem 0xdccf-0xdccf irq 16 at device 0.0 on pci11 bge0: firmware handshake timed out miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:1a:a0:ac:eb:69 uhci0: port 0xff80-0xff9f irq 21 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 22 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff40-0xff5f irq 18 at device 29.2
