[Bug 339707] Nvidia geforce 8300 GS

https://bugzilla.novell.com/show_bug.cgi?id=339707#c3 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ms@novell.com Status|NEEDINFO |ASSIGNED Info Provider|rob.opensuse.linux@googlemail.com | --- Comment #3 from Stefan Dirsch 2007-11-07 15:21:34 MST --- Date: Wed, 7 Nov 2007 22:09:42 +0000 From: Rob OpenSuSE To: Stefan Dirsch Subject: Re: [Bug 339707] Nvidia geforce 8300 GS Cc: Marcus Schaefer Sorry I try direct email, as I'm having problems using attachment in Bugzilla, nor can I can comment further in bugzilla and the 'attachment function' is freezing on me. This is likely due to some interaction with web cache. I can't remember Bugzilla being so inflexible and troublesome in past, but I didn't have to use it much. Copied in Marcus, as I've found stuff from SaX2 log file that he 'claims' ownership of, and may be he will know why the Monitor settings aren't queried. Anyway...

--- Comment #2 from Stefan Dirsch 2007-11-07 03:12:16 MST --- 1. Robert, I closed Bug #339640 after having verified that the nvidia driver kernel module and the security kernel update are ABI compatible. So I still see no issue here.

The issue is that the YaST rpm install of Nvidia driver rpm's failed silently, it put the modules into the /lib/module/<kernel> tree, and did not notice that it was pointless. No checking means someone like you or me, has to troubleshoot the failed installation. If you don't see that as a problem, then I need to discuss this issue with someone else. Perhaps it is Nvidia that creates those rpms, and they will realise it's an issue for them to deal with. I did not report a bug for a quick fix for Nvidia 3D, the solution to ln the modules was obvious to me! I don't really care for Drier "nvidia" that much and was pretty sure I could get it working myself via src rpm of Nvidia kernel stub module. What I ideally want in end is decent display options configurable with SaX2, where I can later s/nv/nvidia/ & /nvidia/nv/ to run un-tainted or demo 3D games^wgraphic intensive applications as needed.

2. nv driver on 10.3 already supports GeForce 8300 GS cards. What is the output of "sax2 -p" on your system?

fir:~ # sax2 -p Chip: 0 is -> NVIDIA GeForce 8300 GS 02:00:0 0x10de 0x0423 AGP nvidia That's what I've never understood, the card is visible, but is not causing nv 2D driver to be selected for some reason. # /.../ # SaX generated X11 config file # Created on: 2007-11-06T18:31:12+0000. # # Version: 8.1 # Contact: Marcus Schaefer , 2005 . , Section "Device" BoardName "GeForce 8300 GS" BusID "2:0:0" Driver "vesa" Identifier "Device[0]" VendorName "NVIDIA" EndSection I booted a live Sidux Debian 'Sid' plus KDE distro from sidux.com and it using Xorg 1.4 5 sep 2007 release configured to use the 'nv' driver. It auto-chose a sensible screen resolution, something ike 1280x1024 which is fairly standad. May be I could copy their xorg.conf file, and Monitor and Screen (with Modeline entries) from SaX2 to cobble together a 2D solution. My attempt to force the 'nv' driver failed with an error message after SaX2 attempted to start X server. No screen config, and I checked log file which shows : -rw-r--r-- 1 root root 45821 2007-11-03 17:06 Xorg.1.log X Window System Version 7.2.0 Release Date: Wed Oct 24 14:18:36 UTC 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux fir 2.6.22.9-0.4-bigsmp #1 SMP 2007/10/05 21:32:04 UTC i686 Build Date: 24 October 2007 . . (II) LoadModule: "nv" (II) Loading /usr/lib/xorg/modules//drivers/nv_drv.so (II) Module nv: vendor="X.Org Foundation" compiled for 7.2.0, module version = 2.1.3 . . (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (--) PCI:*(2:0:0) nVidia Corporation unknown chipset (0x0423) rev 161, Mem @ 0xf a000000/24, 0xe0000000/28, 0xf8000000/25, I/O @ 0xac00/7, BIOS @ 0xfbfe0000/17 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: That message about "unknown chipset" is what causes me to think the 8300 GS isn't recognised by the driver, and led me to believe I needed the Nvidia binary stuff. I presumed from that , some software update would be needed to support the adapter. YaST installed my system as 'Driver vesa' persuade it to use the 'nv' driver. I don't have any other logs of error reports, or what I tried on that issue, as I figured driver update & new Xorg release would sort it soon enough, without me getting involved like this! The Monitor was not queried or recognised, in Sax2 I had this weird situation where I could chose a higher res screen, but on the test and xfine stage I would only have : [0] screen 1024x780 Or some such, where I regard as 1152x864 the absolute bare minimum for running KDE these days (as developers all have better kit than that, you still have issues with being unable to scroll menus enough or move windows to select a button above a scrolling menu in certain places). Selecting Monitor myself, and then choosing resolutions is how I got a high res display, and I decided to grab 3D drivers from Nvidia website, which is where I found the FAQ, about using YaST to install the stuff via rpm, which didn't work, which lead to me filing bug report.... Now this morning on boot, I increased the AGP aperture in BIOS from the Dell delivered setting which appears to have improved the situation. The 8300 GS has 128MB RAM but "steals" system memory, like an integrated adapter. I've run 1600x1200 setting today and it's been acceptable, it may have improved performance and I'll up it again as I have plenty RAM in this box, and the adapter will use more RAM as I've

2GB.

3. If you try to install/update kernel (sub)systems and these are not kABI compatible, you get a warning by YaST since requirements cannot be resolved any more.

OK, so you will have the problem of needing to patch with YOU because of security fix, and then simultaneously get fresh RPM's (but which won't install to right place), or do quick fix, copying files over, but have problem that YaST won't detect the problem again in future as your Nvidia rpm's are now uninstalled. I had that exactly 3 yrs back on a machine I prepared for offsite, and when I received it back, this year I still didn't get 3D working after, as I had no idea how to sort the GLX stuff out on SuSE 8.2 any more! I remember it used to be a FAQ in SuSE USEnet group. What will happen in reality, is that the "nv" driver will be chosen to get display working and the 3D will get put off, until it's actually needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.