-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have a via motherboard (on loan from work, mine's broke) and a nV ti 4400. AGP simple won't work.
I have tried: Latest Gentoo stable drivers: (4496) Latest nVidia stable drivers (5336) These were supposed to fix some issues with via and agp.
I have tried AGP: agpgart built in, nvidia drivers using mode 3 (try aggart then nvAgp) agpgart not built, nvidia drivers set to NvAGP mode 1 (nvagp only) or 3 (try agp, then nvidia) agpgart built as module, trying nvidia only (nope) then mode 3 again (loaded agpgart fine)
The host bridge claims it's supported by agpgart and nvagp.
now, debugging outputs:
- -------lspci------- 00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) 00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 80) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a2)
- -------proc------- ~ cat /proc/driver/nvidia/agp/card Fast Writes: Supported SBA: Supported AGP Rates: 4x 2x 1x Registers: 0x1f000217:0x00000000
cat /proc/driver/nvidia/agp/host-bridge Host Bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge Fast Writes: Not Supported SBA: Supported AGP Rates: 4x 2x 1x Registers: 0x1f000207:0x00000000
cat /proc/driver/nvidia/agp/status Status: Disabled
- -------XF86Config------- (clipped) Section "Device" ~ Identifier "ti" ~ Driver "nvidia" # Driver "nv" ~ #VideoRam 131072
# ---AGP--- # 0 = Off # 1 = NvAGP only # 2 = AGPGart only # 3 = Try AGPGart, then NvAGP - default
Option "NvAGP" "1" # use AGPGart if poss. then use agpgart, if poss.
Option "NoDDC" "false" Option "DPMS" Option "RenderAccel" "true" Option "AGPMode" "4" #Option "AGPFastWrite" "true" Option "EnableDepthMoves" "true" Option "EnablePageFlip" "true" Option "HWCursor" "true" Option "CursorShadow" "true"
Option "Xinerama" "on"
Option "TwinView" Option "SecondMonitorHorizSync" "30-95" Option "SecondMonitorVertRefresh" "60-100" Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768; NULL,1280x1024; NULL,800x600" Option "TwinViewOrientation" "LeftOf" Option "ConnectedMonitor" "CRT, CRT" ~ # Insert Clocks lines here if appropriate EndSection
- -------lsmod------- Module Size Used by nvidia 2068168 12 via_agp 5184 1 agpgart 26408 1 via_agp
- -------dmesg------- (agpgart as module) Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected VIA PM266/KM266 chipset agpgart: Maximum main memory to use for agp memory: 690M agpgart: AGP aperture is 256M @ 0xe0000000 eth0: Setting full-duplex based on MII #1 link partner capability of 45e1. smbfs: Unrecognized mount option umask smbfs: Unrecognized mount option umask smbfs: Unrecognized mount option umask smbfs: Unrecognized mount option umask smbfs: Unrecognized mount option umask atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. nvidia: no version magic, tainting kernel. nvidia: module license 'NVIDIA' taints kernel. 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004 0: NVRM: not using NVAGP, AGPGART is loaded!!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Bugger. its kernel 2.6.4 ~ uname -a Linux temp.home.tristanscott.co.uk 2.6.4-rc1 #11 Sun Apr 18 00:46:10 GMT 2004 i686 AMD Athlon(tm) XP 2000+ AuthenticAMD GNU/Linux
Tristan Scott wrote: | I have a via motherboard (on loan from work, mine's broke) | and a nV ti 4400. AGP simple won't work. | | I have tried: | Latest Gentoo stable drivers: (4496) | Latest nVidia stable drivers (5336) | These were supposed to fix some issues with via and agp. | | I have tried AGP: | agpgart built in, nvidia drivers using mode 3 (try aggart then nvAgp) | agpgart not built, nvidia drivers set to NvAGP mode 1 (nvagp only) or 3 | (try agp, then nvidia) | agpgart built as module, trying nvidia only (nope) then mode 3 again | (loaded agpgart fine) | | The host bridge claims it's supported by agpgart and nvagp. | | now, debugging outputs: | | -------lspci------- | 00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host | Bridge | 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] | 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) | 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) | 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) | 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) | 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge | 00:11.1 IDE interface: VIA Technologies, Inc. | VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) | 00:11.5 Multimedia audio controller: VIA Technologies, Inc. | VT8233/A/8235 AC97 Audio Controller (rev 50) | 00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 | Modem] (rev 80) | 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] | (rev 74) | 01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti | 4400] (rev a2) | | | -------proc------- | ~ cat /proc/driver/nvidia/agp/card | Fast Writes: Supported | SBA: Supported | AGP Rates: 4x 2x 1x | Registers: 0x1f000217:0x00000000 | | cat /proc/driver/nvidia/agp/host-bridge | Host Bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge | Fast Writes: Not Supported | SBA: Supported | AGP Rates: 4x 2x 1x | Registers: 0x1f000207:0x00000000 | | cat /proc/driver/nvidia/agp/status | Status: Disabled | | -------XF86Config------- (clipped) | Section "Device" | ~ Identifier "ti" | ~ Driver "nvidia" | # Driver "nv" | ~ #VideoRam 131072 | | # ---AGP--- | # 0 = Off | # 1 = NvAGP only | # 2 = AGPGart only | # 3 = Try AGPGart, then NvAGP - default | | Option "NvAGP" "1" # use AGPGart if poss. then use agpgart, if poss. | | Option "NoDDC" "false" | Option "DPMS" | Option "RenderAccel" "true" | Option "AGPMode" "4" | #Option "AGPFastWrite" "true" | Option "EnableDepthMoves" "true" | Option "EnablePageFlip" "true" | Option "HWCursor" "true" | Option "CursorShadow" "true" | | Option "Xinerama" "on" | | Option "TwinView" | Option "SecondMonitorHorizSync" "30-95" | Option "SecondMonitorVertRefresh" "60-100" | Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768; | NULL,1280x1024; NULL,800x600" | Option "TwinViewOrientation" "LeftOf" | Option "ConnectedMonitor" "CRT, CRT" | ~ # Insert Clocks lines here if appropriate | EndSection | | | -------lsmod------- | Module Size Used by | nvidia 2068168 12 | via_agp 5184 1 | agpgart 26408 1 via_agp | | -------dmesg------- (agpgart as module) | Linux agpgart interface v0.100 (c) Dave Jones | agpgart: Detected VIA PM266/KM266 chipset | agpgart: Maximum main memory to use for agp memory: 690M | agpgart: AGP aperture is 256M @ 0xe0000000 | eth0: Setting full-duplex based on MII #1 link partner capability of 45e1. | smbfs: Unrecognized mount option umask | smbfs: Unrecognized mount option umask | smbfs: Unrecognized mount option umask | smbfs: Unrecognized mount option umask | smbfs: Unrecognized mount option umask | atkbd.c: Unknown key released (translated set 2, code 0x7a on | isa0060/serio0). | atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. | atkbd.c: Unknown key released (translated set 2, code 0x7a on | isa0060/serio0). | atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. | nvidia: no version magic, tainting kernel. | nvidia: module license 'NVIDIA' taints kernel. | 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed | Jan 14 18:29:26 PST 2004 | 0: NVRM: not using NVAGP, AGPGART is loaded!!
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Sun, Apr 18, 2004 at 11:17:36AM +0000, Tristan Scott wrote:
Bugger. its kernel 2.6.4 ~ uname -a Linux temp.home.tristanscott.co.uk 2.6.4-rc1 #11 Sun Apr 18 00:46:10 GMT 2004 i686 AMD Athlon(tm) XP 2000+ AuthenticAMD GNU/Linux
Have you loadeded/compiled the modules for the agp chipset as well as the generic agpgart module? I made this mistake when I moved to 2.6, I needed to load agpgart and via_agp to get my 3D acceleration to work properly.
JD
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jonathan Dye wrote: | On Sun, Apr 18, 2004 at 11:17:36AM +0000, Tristan Scott wrote: | |>Bugger. its kernel 2.6.4 |>~ uname -a |>Linux temp.home.tristanscott.co.uk 2.6.4-rc1 #11 Sun Apr 18 00:46:10 GMT |>2004 i686 AMD Athlon(tm) XP 2000+ AuthenticAMD GNU/Linux | | | Have you loadeded/compiled the modules for the agp chipset as well as | the generic agpgart module? I made this mistake when I moved to 2.6, I | needed to load agpgart and via_agp to get my 3D acceleration to work | properly.
yep. built in or as modules. neither works. see other response
| | JD |
On Sun, Apr 18, 2004 at 10:54:05AM +0000, Tristan Scott wrote:
I have a via motherboard (on loan from work, mine's broke) and a nV ti 4400. AGP simple won't work.
I have tried: Latest Gentoo stable drivers: (4496) Latest nVidia stable drivers (5336) These were supposed to fix some issues with via and agp.
The host bridge claims it's supported by agpgart and nvagp.
Hmmmm, non-free software, I shouldn't really reply to this but then I also use the Nvidia non-free driver on my desktop (I unfortunately have an addiction to FPS games).
Does XFree86 actually work? as in you have a GUI but no AGP? I ask as this isn't clear in the original email. If XFree86 won't start then it could be something to do with the glx bits needing to be installed in a different manner to work with kernel 2.6, I had a problem with that on my Debian machine in the past.
Anyhow I would recommend that you checkout the Nvidia support forum which is linked to from Nvidias site (and Nvidia people do post there) and can be found at http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 you will probably find a solution there, or some people who have the same problems.
Adam
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
adam@thebowery.co.uk wrote: | On Sun, Apr 18, 2004 at 10:54:05AM +0000, Tristan Scott wrote: | <snip> | Hmmmm, non-free software, I shouldn't really reply to this but then I also use | the Nvidia non-free driver on my desktop (I unfortunately have an addiction to | FPS games). The nv driver does double-buffering but not glx (therefore no ut2004 et al)
| Does XFree86 actually work? as in you have a GUI but no AGP? I ask as this Yup, double-buffering seems to be broken too. 3d work respectably, such as ut2004 in 800x600, every effect off, ~30 fps. consistent with a pci card methinks. | isn't clear in the original email. If XFree86 won't start then it could be | something to do with the glx bits needing to be installed in a different manner they seem to work. /usr/lib/tls does not exist, and nvidia 5336 via gentoo's portage made no mention of it. | to work with kernel 2.6, I had a problem with that on my Debian machine in the | past. | | Anyhow I would recommend that you checkout the Nvidia support forum which is | linked to from Nvidias site (and Nvidia people do post there) and can be found | at http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 you will | probably find a solution there, or some people who have the same problems. Will do... in the morning *looks at clock* later this morning I mean. | | Adam
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Havent found anyone else on nvnews or gentoo forums with my problem.. or even a particularly similar problem. I ought to have mentioned I'd looked at forums, but thought nvnews might be new one... well, it was early morning.
Changed kernel to 2.6.6 and rebuilt config from scratch. agpgart built in - no go. changed card to a Ti4600 (from Ti4400) - no go
The AGP did work back in the days before windows stopped working, with either card.
I'm thinking this motherboard will never do it under linux, people have mentioned agp/via problems, but are always saved by switching to nvAGP or agpgart.
If you want to nvidia driver to work under 2.6.6, you've got to leave 4k stacks off, lave register arguments off and reverse a module move patch. While it will function with register arguments on, its unstable i'm told. i didnt try it.
Tristan Scott wrote: | adam@thebowery.co.uk wrote: | | On Sun, Apr 18, 2004 at 10:54:05AM +0000, Tristan Scott wrote: | | | <snip> | | Hmmmm, non-free software, I shouldn't really reply to this but then I | also use | | the Nvidia non-free driver on my desktop (I unfortunately have an | addiction to | | FPS games). | The nv driver does double-buffering but not glx (therefore no ut2004 et al) | | | Does XFree86 actually work? as in you have a GUI but no AGP? I ask as | this | Yup, double-buffering seems to be broken too. 3d work respectably, such | as ut2004 in 800x600, every effect off, ~30 fps. consistent with a pci | card methinks. | | isn't clear in the original email. If XFree86 won't start then it | could be | | something to do with the glx bits needing to be installed in a | different manner | they seem to work. /usr/lib/tls does not exist, and nvidia 5336 via | gentoo's portage made no mention of it. | | to work with kernel 2.6, I had a problem with that on my Debian | machine in the | | past. | | | | Anyhow I would recommend that you checkout the Nvidia support forum | which is | | linked to from Nvidias site (and Nvidia people do post there) and can | be found | | at http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 you | will | | probably find a solution there, or some people who have the same | problems. | Will do... in the morning *looks at clock* later this morning I mean. | | | | Adam |
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tristan Scott wrote: | Havent found anyone else on nvnews or gentoo forums with my problem.. or | even a particularly similar problem. I ought to have mentioned I'd | looked at forums, but thought nvnews might be new one... well, it was | early morning. | | Changed kernel to 2.6.6 and rebuilt config from scratch. | agpgart built in - no go.
Compiled it out, tried nvAGP. nope. Compiled it back in, changed XF86Config from nvAGP to AGPGART, rebuilt with the non-gentoo-recommended 5336 drivers using nvidia installer. AND IT WORKED! 4n1c8 in ~ [26916]: cat /proc/driver/nvidia/agp/status Status: Enabled Driver: AGPGART AGP Rate: 4x Fast Writes: Disabled SBA: Disabled
no idea what i did though. ive tried the nvidia drivers before via nvidia installer. this combination hasnt been tried - nvidia 5336, compiled in agpgart, ti4600, 2.6.6 kernel
Lesson for all you people out there: Dont buy a 00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
| changed card to a Ti4600 (from Ti4400) - no go | | The AGP did work back in the days before windows stopped working, with | either card. | | I'm thinking this motherboard will never do it under linux, people have | mentioned agp/via problems, but are always saved by switching to nvAGP | or agpgart. | | If you want to nvidia driver to work under 2.6.6, you've got to leave 4k | stacks off, lave register arguments off and reverse a module move patch. | While it will function with register arguments on, its unstable i'm | told. i didnt try it. | | Tristan Scott wrote: | | adam@thebowery.co.uk wrote: | | | On Sun, Apr 18, 2004 at 10:54:05AM +0000, Tristan Scott wrote: | | | | | <snip> | | | Hmmmm, non-free software, I shouldn't really reply to this but then I | | also use | | | the Nvidia non-free driver on my desktop (I unfortunately have an | | addiction to | | | FPS games). | | The nv driver does double-buffering but not glx (therefore no ut2004 | et al) | | | | | Does XFree86 actually work? as in you have a GUI but no AGP? I ask as | | this | | Yup, double-buffering seems to be broken too. 3d work respectably, such | | as ut2004 in 800x600, every effect off, ~30 fps. consistent with a pci | | card methinks. | | | isn't clear in the original email. If XFree86 won't start then it | | could be | | | something to do with the glx bits needing to be installed in a | | different manner | | they seem to work. /usr/lib/tls does not exist, and nvidia 5336 via | | gentoo's portage made no mention of it. | | | to work with kernel 2.6, I had a problem with that on my Debian | | machine in the | | | past. | | | | | | Anyhow I would recommend that you checkout the Nvidia support forum | | which is | | | linked to from Nvidias site (and Nvidia people do post there) and can | | be found | | | at http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 you | | will | | | probably find a solution there, or some people who have the same | | problems. | | Will do... in the morning *looks at clock* later this morning I mean. | | | | | | Adam | | | | _______________________________________________ | main@lists.alug.org.uk | http://www.alug.org.uk/ | http://lists.alug.org.uk/mailman/listinfo/main | Unsubscribe? See message headers or the web site above! | |
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Tue, Apr 20, 2004 at 09:42:35AM +0000, Tristan Scott wrote:
Lesson for all you people out there: Dont buy a 00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
I would have thought the lesson learned would be don't use Gentoo or buy an Nvidia card to use with Linux :)
Adam
On Tuesday 20 April 2004 12:59, adam@thebowery.co.uk wrote:
I would have thought the lesson learned would be don't use Gentoo or buy an Nvidia card to use with Linux :)
Can't argue with the first bit, as I haven't really spent a lot of time playing with Gentoo.
But
If you want/need functional 3D with comparative performance to a Windows system, what other options are there ?
At the moment if you buy any Nvidia card there is a reasonable chance that you can make it work, yes they are closed drivers, no it doesn't work in 100% of cases (in this case I think it was more to do with AGP support on the chipset rather than the drivers) and yes if Nvidia opened their driver spec we could have nice open source drivers, but the point is it does work.
Not all ATI cards are linux friendly, the drivers they offer are also not open and no other manufacturer I can think of can offer such performance.
If Nvidia moved some IP from the driver to the card then maybe they could open the drivers, but then we would have a more expensive card and one that probably didn't get incremental performance improvements with every driver release.
I am pretty sure that if Nvidia could open up the drivers without some huge financial or intellectual cost then they would. Why would they not, why maintain linux drivers and pay people to write installers etc when there is a community that would do it for free ?
The reason I think is that there is either a. Some clever stuff going on in the driver that they don't want competitors to see or b. Some licensed technology that they are not allowed to release.
W
On Tue, Apr 20, 2004 at 10:59:05PM +0000, Wayne Stallwood wrote:
Not all ATI cards are linux friendly, the drivers they offer are also not open and no other manufacturer I can think of can offer such performance.
Anything thats Radeon 9200 or lower has very nice free drivers, but yes they are slow cards. The newer ATI stuff does suck more than Nvidia I agree on the driver front.
The reason I think is that there is either a. Some clever stuff going on in the driver that they don't want competitors to see or b. Some licensed technology that they are not allowed to release.
The problem is mainly the licensed technology in the drivers, there is also other bits that they try to keep close to their chests because of the clever stuff going on. Now of course if they released the bits of the driver that did clever stuff some clever hacker could of course make the drivers/hardware go even faster but they don't appear to have realised this yet. Of course this means that a few bits will get dropped from the driver *but* what would be great if they make the kernel module free software and let the community improve the driver and do the same with the OpenGL implementation. Then if you need the non-free bits of the driver that are patent and license encumbered then you could resort to a non-free library that Nvidia could distribute seperately.
In that situation I see that Nvidia get a big win over all the other cards as they get faster and better (and even supported!) drivers for free without breaking their contracts and NDAs with whoever else they have licensed tech from. The community gets better drivers and we can say how great Nvidia are and they can shift lots more cards to the growing Linux community.
Doubt I will see it happen though :(
Adam
On Tuesday 20 April 2004 22:43, adam@thebowery.co.uk wrote:
Of course this means that a few bits will get dropped from the driver *but* what would be great if they make the kernel module free software and let the community improve the driver and do the same with the OpenGL implementation. Then if you need the non-free bits of the driver that are patent and license encumbered then you could resort to a non-free library that Nvidia could distribute seperately.
I guess that depends on what exactly are the juicy bits, I find it suspicious that the reverse engineering/OS community have completely failed to extract any sort of 3D capability from the card whatsoever, Quite complicated things have been successfully worked out in the past. So I am guessing that there is something very weird going on with the way the driver and card interact when doing 3D.
This also ties up very well with past problems Nvidia have had with their cards being fussy about chipsets/AGP settings/memory types/Power Supplies/ BIOS versions/Price of tea etc....What if say Nvidia know a way of making the AGP bus work in a more efficient way, and what if that mode is the only way you can talk 3D to the card......purely speculation I know but what if that "interface" is the bit Nvidia can't let out ? then they could only really give us what we already have with the "nv" XFree driver.
On Wed, Apr 21, 2004 at 12:08:32AM +0000, Wayne Stallwood wrote:
I guess that depends on what exactly are the juicy bits, I find it suspicious that the reverse engineering/OS community have completely failed to extract any sort of 3D capability from the card whatsoever, Quite complicated things have been successfully worked out in the past. So I am guessing that there is something very weird going on with the way the driver and card interact when doing 3D.
My guess is that reverse engineering the drivers is just too hard, apparently the Linux driver is based on the Windows NT driver (as in very heavily, i did read somewhere that it even emulates parts of the Windows registry!) and I figure that people who care about the driver being free have bought an older ATI card and those that don't care just use the Nvidia driver. I could imagine that reverse engineering a driver/card to produce a driver worse than one that is already available isn't a very attractive option for most people.
Adam
On Wed, Apr 21, 2004 at 12:36:41AM +0100, adam@thebowery.co.uk wrote:
My guess is that reverse engineering the drivers is just too hard, apparently the Linux driver is based on the Windows NT driver (as in very heavily, i did read somewhere that it even emulates parts of the Windows registry!) and I figure that people who care about the driver being free have bought an older ATI card and those that don't care just use the Nvidia driver. I could imagine that reverse engineering a driver/card to produce a driver worse than one that is already available isn't a very attractive option for most people.
Yup - swat I did, I go me an ATI Radeon 9200 (and very pleased with it I am too) for my home machine... And am just not using 3d on the Nvidea card that I got for my work machine (might get round to it one day, if I decide that it's worth having non-free, binary nastiness, drivers in my kernel).
What would be *really* nice is if someone designed some open hardware for talking GL over AGP... and then someone wrote so nice GPL drivers for it... But I think that'd involve too much outlay in the first case, and that it's probably not of the highest importance to the people in the know.
Right - back to work.
On 2004-04-21 01:08:32 +0100 Wayne Stallwood ALUGlist@digimatic.plus.com wrote:
[...] I find it suspicious that the reverse engineering/OS community have completely failed to extract any sort of 3D capability from the card whatsoever
I don't think it suspicious. This hardware seems to be made more troublesome by the manufacturer producing their own inVidious proprietary drivers, which reduces the number putting effort into a free software one, as well as the common problems with lack of manufacturer documentation.
On Thursday 22 April 2004 00:13, MJ Ray wrote:
I don't think it suspicious. This hardware seems to be made more troublesome by the manufacturer producing their own inVidious proprietary drivers, which reduces the number putting effort into a free software one, as well as the common problems with lack of manufacturer documentation.
So are you saying that Nvidia producing a closed linux driver actually has a more negative impact on the community than then doing nothing for Linux at all. I'd never thought of it that way.
Maybe this is why we see so little Linux support from other manufacturers. They either can't get their heads around (or can't for technical/political or legal reasons) releasing open drivers or open hardware documentation. They think as you do that releasing proprietary drivers simply stops the development of an open solution, so figure the best they can do for linux support is nothing and let the reverse engineering gurus figure it out.
I see the logic behind your argument, but I still feel the motivation behind Nvidia not providing open drivers or proper hardware documentation is more a technical or legal one.
There is far more to the Nvidia drivers than just hardware interfacing, how else do you explain the speed improvements between releases, what if those optimisations have some relevance to other Graphics hardware for example.
On 2004-04-22 19:49:27 +0100 Wayne Stallwood ALUGlist@digimatic.plus.com wrote:
So are you saying that Nvidia producing a closed linux driver actually has a more negative impact on the community than then doing nothing for Linux at all. I'd never thought of it that way.
I wrote it reduces demand and effort for a free software one and let everyone draw their own conclusions, as you have done. Far be it for me to tell you what the effect is on the community.
I see the logic behind your argument, but I still feel the motivation behind Nvidia not providing open drivers or proper hardware documentation is more a technical or legal one.
No, it's commercial. It's cheaper for them to do it that way, probably because of some short-sighted contracts.
There is far more to the Nvidia drivers than just hardware interfacing, how else do you explain the speed improvements between releases, what if those optimisations have some relevance to other Graphics hardware for example.
Maybe they just removed really boneheaded errors from their drivers? I think those nVidia kernel modules were part of the motivation for the kernel taint warnings, so I'd guess the early ones were not good.
If those optimisations have some relevance to other graphics hardware, it would be better for me as a consumer if they were available from a choice of suppliers sooner than author life+70 years (or whatever copyright currently is where nVidia live... not really important, as it'll be ancient history long before then).
On Friday 23 April 2004 3:36 pm, MJ Ray wrote:
Maybe they just removed really boneheaded errors from their drivers? I think those nVidia kernel modules were part of the motivation for the kernel taint warnings, so I'd guess the early ones were not good.
I had problems building nVidia drivers last year; after a lot of head scratching it turned out to be a handful of typos in their makefile. Jen