i tried the new drivers from nvidia today and if i try to load glx it fails
RR wrote:
i tried the new drivers from nvidia today and if i try to load glx it fails
Don't you have to use the matching NVIDIA_kernel module? -- JAY VOLLMER JVOLLMER1@MN.RR.COM TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE
On Fri, 2002-04-05 at 18:41, Jay C Vollmer wrote:
RR wrote:
i tried the new drivers from nvidia today and if i try to load glx it fails
Don't you have to use the matching NVIDIA_kernel module?
-- JAY VOLLMER JVOLLMER1@MN.RR.COM TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE
yes
On Fri, 2002-04-05 at 18:47, Timothy Reaves wrote:
On 05 Apr 2002 18:29:29 -0500 RR
wrote: i tried the new drivers from nvidia today and if i try to load glx it fails
And?
this is the error
XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: SuSE Linux [ELF] SuSE 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: Fri Apr 5 18:56:36 2002 (==) Using config file: "/etc/X11/XF86Config" (II) [GLX]: Calling GlxExtensionInit Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to feedback@suse.de. XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
On Fri, 2002-04-05 at 19:03, RR wrote:
On Fri, 2002-04-05 at 18:47, Timothy Reaves wrote:
On 05 Apr 2002 18:29:29 -0500 RR
wrote: i tried the new drivers from nvidia today and if i try to load glx it fails
And?
this is the error
XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: SuSE Linux [ELF] SuSE
where is this elf coming from
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: Fri Apr 5 18:56:36 2002 (==) Using config file: "/etc/X11/XF86Config" (II) [GLX]: Calling GlxExtensionInit
Fatal server error: Caught signal 11. Server aborting
When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to feedback@suse.de.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
In my case the Kernel module won't initialize and it also says no valid screen found. I ran "sax2 -m 0=nvidia" and sax can't intialize either, tells me to instal mesasoft package. Something obviously isn't getting configed right for the kernel. My kernel is the default 2.4.16-4GB kernal for 7.3. I had a bit of a problem with the version before this, but it was related to GLX drivers and symlinks. I compile the source and made a few of my own symlinks and they worked. I just reinstall the 2802 drivers from source and it works. I know that SuSE has changes some of the sys config files to be put into 8.0 (e.g. change in the /etc files). I wonder if this isn't a case of the packages being configed for this environment by mistake. Cheers, Curtis On Friday 05 April 2002 17:29, RR wrote:
i tried the new drivers from nvidia today and if i try to load glx it fails
Suse 7.1 kernel 2.4.17 kde 2.2.2 XF86-4.2.0 Riva TNT I have similar results with NVIDIA_kernel-1.0-2802.suse71.i386.rpm NVIDIA_kernel-1.0-2880.suse71.i386.rpm Including the "No Screens found" error. Brian Marr On Saturday 06 April 2002 13:58, you wrote:
In my case the Kernel module won't initialize and it also says no valid screen found. I ran "sax2 -m 0=nvidia" and sax can't intialize either, tells me to instal mesasoft package.
Something obviously isn't getting configed right for the kernel. My kernel is the default 2.4.16-4GB kernal for 7.3. I had a bit of a problem with the version before this, but it was related to GLX drivers and symlinks. I compile the source and made a few of my own symlinks and they worked. I just reinstall the 2802 drivers from source and it works. I know that SuSE has changes some of the sys config files to be put into 8.0 (e.g. change in the /etc files). I wonder if this isn't a case of the packages being configed for this environment by mistake.
Cheers, Curtis
On Friday 05 April 2002 17:29, RR wrote:
i tried the new drivers from nvidia today and if i try to load glx it fails
Well, I got them working from source. I just manually deleted any old drivers for the /usr/lib/GL, and then just to make sure I ran "rpm -e NVIDIA_GLX". Then I rebooted to "init 3" and ran the "tar xfvz" of both packages, and cd'ed into their respective dir's and ran "make install". rebooted and ran Sax2 to see if it would run, it did. Then I booted into X and took the lines from my previous XF86Config file and pasted them into the new config file. Logged out of kde, restarted X, and no problems since. I suggest using the source/tar.gz files. Hopefully this will get you up and running. I don't know what the problem is, but I had to install the 2802 packages the same way. I think that SuSE is in a state of transition regarding the file sys/dir layout and this has alot to do with the problems I'm having. Cheers, Curtis. On Saturday 06 April 2002 08:07, Brian Marr wrote:
Suse 7.1 kernel 2.4.17 kde 2.2.2 XF86-4.2.0 Riva TNT
I have similar results with NVIDIA_kernel-1.0-2802.suse71.i386.rpm NVIDIA_kernel-1.0-2880.suse71.i386.rpm
Including the "No Screens found" error.
Brian Marr
On Saturday 06 April 2002 13:58, you wrote:
In my case the Kernel module won't initialize and it also says no valid screen found. I ran "sax2 -m 0=nvidia" and sax can't intialize either, tells me to instal mesasoft package.
Something obviously isn't getting configed right for the kernel. My kernel is the default 2.4.16-4GB kernal for 7.3. I had a bit of a problem with the version before this, but it was related to GLX drivers and symlinks. I compile the source and made a few of my own symlinks and they worked. I just reinstall the 2802 drivers from source and it works. I know that SuSE has changes some of the sys config files to be put into 8.0 (e.g. change in the /etc files). I wonder if this isn't a case of the packages being configed for this environment by mistake.
Cheers, Curtis
On Friday 05 April 2002 17:29, RR wrote:
i tried the new drivers from nvidia today and if i try to load glx it fails
I wouldn't agree Curtis. I've advocated getting the tar.gz files for the longest time and I've not had any issues. I put them in /usr/src/packages/SOURCES and just untar them and do a make. You don't have to go through all that hardship of rebooting and the like. What I do is this. A. I don't use KDM ;) B. Exit X C. rmmod NVdriver (I've renamed NVdriver to NVdriver.o so that it's seen properly). D. cd into the new km dir and do the make. E. cd into /lib/modules/<kernel version directory> and mv NVdriver to NVdriver.o then I execute 'insmod NVdriver' and it loads the new km. F. cd into the GLX dir and do the make. Which should make the correct links and overwrite the current version which is in these directories. 1. Please make sure that all references to the switch2 scripts have been removed from /etc/rc.config because this will screw the last 2 versions of nVidia's GLX because they changed stuff and their make file makes the symlinks so the switch2 scripts are woefully out of date as far as this is concerned. G. Go back into X. :) Remember that you really shouldn't have to reboot unless you've replaced the kernel or you are going to do surgery on the hardware. :) Most everything is fixable without rebooting. Sorry I wasn't paying attention to the earlier thread when this new driver was released..I've been busy as hell lately. :) Cheers! * Curtis Rey (crrey@charter.net) [020406 22:28]: ::Well, I got them working from source. I just manually deleted any old ::drivers for the /usr/lib/GL, and then just to make sure I ran "rpm -e ::NVIDIA_GLX". Then I rebooted to "init 3" and ran the "tar xfvz" of both ::packages, and cd'ed into their respective dir's and ran "make install". ::rebooted and ran Sax2 to see if it would run, it did. Then I booted into X ::and took the lines from my previous XF86Config file and pasted them into the ::new config file. Logged out of kde, restarted X, and no problems since. ::I suggest using the source/tar.gz files. Hopefully this will get you up and ::running. I don't know what the problem is, but I had to install the 2802 ::packages the same way. I think that SuSE is in a state of transition ::regarding the file sys/dir layout and this has alot to do with the problems ::I'm having. :: ::Cheers, Curtis. :: :: :: ::On Saturday 06 April 2002 08:07, Brian Marr wrote: ::> Suse 7.1 kernel 2.4.17 kde 2.2.2 XF86-4.2.0 Riva TNT ::> ::> I have similar results with ::> NVIDIA_kernel-1.0-2802.suse71.i386.rpm ::> NVIDIA_kernel-1.0-2880.suse71.i386.rpm ::> ::> Including the "No Screens found" error. ::> ::> Brian Marr ::> ::> On Saturday 06 April 2002 13:58, you wrote: ::> > In my case the Kernel module won't initialize and it also says no valid ::> > screen found. I ran "sax2 -m 0=nvidia" and sax can't intialize either, ::> > tells me to instal mesasoft package. ::> > ::> > Something obviously isn't getting configed right for the kernel. My ::> > kernel is the default 2.4.16-4GB kernal for 7.3. I had a bit of a ::> > problem with the version before this, but it was related to GLX drivers ::> > and symlinks. I compile the source and made a few of my own symlinks and ::> > they worked. I just reinstall the 2802 drivers from source and it works. ::> > I know that SuSE has changes some of the sys config files to be put into ::> > 8.0 (e.g. change in the /etc files). I wonder if this isn't a case of ::> > the packages being configed for this environment by mistake. ::> > ::> > ::> > Cheers, Curtis ::> > ::> > On Friday 05 April 2002 17:29, RR wrote: ::> > > i tried the new drivers from nvidia today and if i try to load glx it ::> > > fails :: ::-- ::To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ::For additional commands send e-mail to suse-linux-e-help@suse.com ::Also check the archives at http://lists.suse.com :: -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--
On Sat, 6 Apr 2002 08:59, RR wrote:
i tried the new drivers from nvidia today and if i try to load glx it fails Hi there ! Make sure you dissable framebuffer (That fancy console on SuSE - Linux)by changing line in the /etc/lilo.conf - vga = normal, SuSE has framebuffer compiled directly in to the kernel and some hardware drivers don`t like framebuffer in this case the nvidia driver. See ya Alan
Really? Which nVidia cards are these? I have a Diamond Viper 770 (TNT2) and it works fine. Is there a list somewhere? * Alan (ally@chariot.net.au) [020407 03:15]: ::On Sat, 6 Apr 2002 08:59, RR wrote: ::> i tried the new drivers from nvidia today and if i try to load glx it ::> fails ::Hi there ! ::Make sure you dissable framebuffer (That fancy console on SuSE - ::Linux)by changing line in the /etc/lilo.conf - vga = normal, ::SuSE has framebuffer compiled directly in to the kernel and some ::hardware drivers don`t like framebuffer in this case the nvidia driver. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--
Framebuffer works fine on my tnt2ultra here. On Sun, 2002-04-07 at 10:59, Ben Rosenberg wrote:
Really? Which nVidia cards are these? I have a Diamond Viper 770 (TNT2) and it works fine. Is there a list somewhere?
* Alan (ally@chariot.net.au) [020407 03:15]: ::On Sat, 6 Apr 2002 08:59, RR wrote: ::> i tried the new drivers from nvidia today and if i try to load glx it ::> fails ::Hi there ! ::Make sure you dissable framebuffer (That fancy console on SuSE - ::Linux)by changing line in the /etc/lilo.conf - vga = normal, ::SuSE has framebuffer compiled directly in to the kernel and some ::hardware drivers don`t like framebuffer in this case the nvidia driver.
-=Ben
--=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Mark Doucette kranked@oberon.ark.com WinFree and Lovin' it. SuSE Rox Linux! Registered Linux User # 240512 ----////----
Ben Rosenberg wrote:
Really? Which nVidia cards are these? I have a Diamond Viper 770 (TNT2) and it works fine. Is there a list somewhere?
I can say the geforce4 ti440 cards do not like any of the framebuffer stuff as set up in 7.3. If you want to see anything on your screen during bootup or installation you will have to say vga=normal at the command line prompt. But then thats the only card I know of with problems in that area. -- Mark Hounschell dmarkh@cfl.rr.com
On Mon, 8 Apr 2002 03:29, Ben Rosenberg wrote:
Really? Which nVidia cards are these? I have a Diamond Viper 770 (TNT2) and it works fine. Is there a list somewhere?
Hi Ben ! I did this on my friend`s PC. He was getting rather desperate as He couldnt figure out the Xserver ,he upgraded to Xfree 4.2.x version and X would not start.His video card is rather fancy one Elsa DDC4 with nVidia chip.Sax2 would not ,start only if you forced it with sax2 -c 0 option. Than I was able to get X working but again only if I told Sax2 that no 3D was required .I thought that getting just the X working was the first priority than tried to load glx and so on and it would always fail. Similar messages from X err as already mentioned in the previous threads.So I checked what`s up with the framebuffer run fbset -i,and yes framebuffer loaded.Changed the line in the /etc/lilo.conf vga = normal ,rerun the lilo.After reboot I had no framebuffer and absolutely stunning 3D acceleration and no problem with the glx ,however the friend complained that resolution 1200x1028 or something was not good enough because he could get 1600x1200 under w2k out of this card, but thats the another problem ,the linux driver is not capable of that one in this case nVidia has not done that possibility with that particular driver. One interesting thing came up ,after the nvidia kernel driver loads you can`t get virtual consoles anymore just big blue screen. Figure that one! See ya Alan
* Alan
On Mon, 8 Apr 2002 03:29, Ben Rosenberg wrote:
Really? Which nVidia cards are these? I have a Diamond Viper 770 (TNT2) and it works fine. Is there a list somewhere?
Hi Ben ! I did this on my friend`s PC. He was getting rather desperate as He
I can confirm that a variety of NVidia based cards misbehave when the framebuffer deivce is activated. (this is with a 2.4.16 kernel). I've seen it on Geforce3 Ti 500, GEforce 2 (forgot which) and quad. Worked fine with other geforce2 cards .. I just disabled it (I can live without the fancy bootscreen), so I don;t know if a geforce 4 will be bothered by it. I know it works pretty fine without. And since then I just disable it on all linux boxes I configure (wether they have an nvidia card or not )
yes framebuffer loaded.Changed the line in the /etc/lilo.conf vga = normal
vga=6 (which gives you more lines of text)
stunning 3D acceleration and no problem with the glx ,however the friend complained that resolution 1200x1028 or something was not good enough because he could get 1600x1200 under w2k out of this card, but thats the another problem ,the linux driver is not capable of that one
Sorry. I am running 1600x1200 dual head (that is, 2 screens, each at 1600x1200, the card, the driver and the (right) monitor all can go higher than that. I've been running in 1600x1200 mode since the 0.7 series of nvidia drivers on everything from a 16M TNT2 to a Geforce 4 Ti 4400 (well almost everything). It also works just fine on a geforce2go and a geforce4go (the 4go was tested by a co-worker of mine who had just bought a new laptop ;) )
driver. One interesting thing came up ,after the nvidia kernel driver loads you can`t get virtual consoles anymore just big blue screen.
not true either. This is either a config option in an older kde 2 series (I think it was fixed in kde 2.2, it is fixed in kde3) or an AGP issue.fixed in kde3) I can happily jump from nvidia to virtual console and back (excpet that the crappy monitor I have as second head is p[retty much unreadable ;) ) Currently listening to: artist - Track 01 Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Some say the end is near. =`\<, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
participants (10)
-
Alan
-
Ben Rosenberg
-
Brian Marr
-
Curtis Rey
-
Gerhard den Hollander
-
Jay C Vollmer
-
Mark Doucette
-
Mark Hounschell
-
RR
-
Timothy Reaves