Re: 3dfx.o -- SOLVED!!!
One question, if I may: Is the kernel that this module is working with installed from the 2.2.17 kernel image deb or did you compile it from the kernel sources? It seemed to me that the fact that I installed the sources, but tried to run the module with the precompiled kernel might have caused the problem described by you (and experienced by me). Thanks, Juergen David Bellows wrote: [...] OK, here's what I did. 1)I apt-get removed my existing device3dfx-source and also removed /usr/src/modules/ which is where the source was. 2) apt-get install device3dfx-source. 3) cd /usr/src/ 4) tar zxfv device3dfx-source 5) cd modules # This dir is created by the above command 6) cd modules/device3dfx 7) ./debian/buildpkg # This as per the docs in /usr/share/doc/device3dfx-source/README.Debian 8) This time it compiled. Before when I ran this command it wouldn't compile, apparently I needed to clean up some stuff but I didn't know how. Re-installing the whole package provided me with a clean script. 9) The module will be located in /usr/src/modules/device3dfx as 3dfx.o 10) cp 3dfx.o /lib/modules/2.2.17/misc/ # obviously sub 2.2.17 for wherever your modules are. 11) According to /usr/src/modules/device3dfx/debian/README.debian do the following A) mknod /dev/3dfx c 107 0 B) make the group audio have rw permissions for /dev/3dfx C) make sure whatever user you want to use belongs to the group audio 12) insmod 3dfx 13) Start fragging # hopefully, this worked for me. Hope this helps, David Bellows -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: 3dfx.o -- SOLVED!!!
Hello, Juergen Fiedler wrote: One question, if I may: Is the kernel that this module is working with installed from the 2.2.17 kernel image deb or did you compile it from the kernel sources? It seemed to me that the fact that I installed the sources, but tried to run the module with the precompiled kernel might have caused the problem described by you (and experienced by me). The kernel I am using is 2.2.17 from woody. Potato comes with 2.2.17pre6. I had to upgrade to the newer kernel in order to get the newest debian ALSA to work with my SB Live!. So anyway, yes you have to get the kernel source (and probably headers) and compile the 3dfx-source against that (I think you have to link /usr/src/linux to kernel-souce). Even going from 2.2.17pre6 to 2.2.17 breaks the 3dfx module. In addition, the kernel image I'm using is the precompiled one available from woody, so installing that kernel deb, along with the sources deb and possibly the headers deb using apt-get (a few other things might need upgrading too) along with a fresh 3dfx-device-source worked for me as I described in my last posting. Good luck! David Bellows
Re: 3dfx.o
Joel Dinel wrote: /lib/modules/2.2.17/misc/3dfx.o: unresolved symbol register_chrdev_R06af9881 /lib/modules/2.2.17/misc/3dfx.o: insmod /lib/modules/2.2.17/misc/3dfx.o failed /lib/modules/2.2.17/misc/3dfx.o: insmod 3dfx failed Did you move your module from your old kernel to your new one ? If you had kernel 2.2.15, you'd need to move /lib/modules/2.2.15/misc/3dfx.o to /lib/modules/2.2.17/misc/. Try that. Yep, I had already done that -- still the same errors. Thanks, David Bellows
Re: 3dfx.o
dave, this isn't the reply you wanted, but fwiw, i can't get the 3dfx driver to work for the life of me. i've been at it for a couple of days now. i emailed the packager, steve hasam(sp?) twice, and he hasn't replied at all. not even a RTFM. (i'll leave my opinion of his maintainer's status unsaid). i've read a number of people in the same predicament on this list. i'd say 4 or 5 people by now, in the past 2 weeks. one person emailed me and said his driver worked. i emailed him back and got no reply. i also tried using rpm2cpio on the rpms offered on 3dfx's website. they compiled and didn't work either, but i should try that again. if someone here has their voodoo 3 working, a bunch of people would really like to hear from you! pete On Sun, 29 Oct 2000, David Bellows wrote: Hello all, At one point I had my Voodoo 3 working perfectly in Debian, but then I installed a new SB Live! which is where things went south. In order to get sound to work I upgraded to the latest (unstable) ALSA which in turn required a kernel update, etc. After a few hours I got it all working with the new kernel (2.2.17 as opposed to 2.2.17pre6 -- the default from potato). But when I tried to load the 3dfx module I got these errors: /lib/modules/2.2.17/misc/3dfx.o: unresolved symbol register_chrdev_R06af9881 /lib/modules/2.2.17/misc/3dfx.o: insmod /lib/modules/2.2.17/misc/3dfx.o failed /lib/modules/2.2.17/misc/3dfx.o: insmod 3dfx failed As I said before, I did have all this working with kernel 2.2.17pre6. So I attempted to follow the directions and recompile the 3dfx source for my new kernel. No go. I can't for the life of me get anything to work. So my question is, has anyone got their Voodoo3 working with the woody kernel 2.2.17? And would the compiled module 3dfx.o also work on my machine (AMD K6II-300)? And so, would somebody please send me a copy? Thanks, David Bellows -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: 3dfx.o
what do you do and what errors do you get? I had no problems until I introduced epoch, it looks like package does not understand it properly (see my other post or other reply to this thread) in response to David: you probably need to recompile 3dfx (build a new package and install it) erik Peter Jay Salzman wrote: dave, this isn't the reply you wanted, but fwiw, i can't get the 3dfx driver to work for the life of me. i've been at it for a couple of days now. i emailed the packager, steve hasam(sp?) twice, and he hasn't replied at all. not even a RTFM. (i'll leave my opinion of his maintainer's status unsaid). i've read a number of people in the same predicament on this list. i'd say 4 or 5 people by now, in the past 2 weeks. one person emailed me and said his driver worked. i emailed him back and got no reply. i also tried using rpm2cpio on the rpms offered on 3dfx's website. they compiled and didn't work either, but i should try that again. if someone here has their voodoo 3 working, a bunch of people would really like to hear from you! pete On Sun, 29 Oct 2000, David Bellows wrote: Hello all, At one point I had my Voodoo 3 working perfectly in Debian, but then I installed a new SB Live! which is where things went south. In order to get sound to work I upgraded to the latest (unstable) ALSA which in turn required a kernel update, etc. After a few hours I got it all working with the new kernel (2.2.17 as opposed to 2.2.17pre6 -- the default from potato). But when I tried to load the 3dfx module I got these errors: /lib/modules/2.2.17/misc/3dfx.o: unresolved symbol register_chrdev_R06af9881 /lib/modules/2.2.17/misc/3dfx.o: insmod /lib/modules/2.2.17/misc/3dfx.o failed /lib/modules/2.2.17/misc/3dfx.o: insmod 3dfx failed As I said before, I did have all this working with kernel 2.2.17pre6. So I attempted to follow the directions and recompile the 3dfx source for my new kernel. No go. I can't for the life of me get anything to work. So my question is, has anyone got their Voodoo3 working with the woody kernel 2.2.17? And would the compiled module 3dfx.o also work on my machine (AMD K6II-300)? And so, would somebody please send me a copy? Thanks, David Bellows -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: 3dfx.o -- SOLVED!!!
Hello Peter and anyone else having problems Peter Jay Salzman wrote: dave, this isn't the reply you wanted, but fwiw, i can't get the 3dfx driver to work for the life of me. i've been at it for a couple of days now. i emailed the packager, steve hasam(sp?) twice, and he hasn't replied at all. not even a RTFM. (i'll leave my opinion of his maintainer's status unsaid). i've read a number of people in the same predicament on this list. i'd say 4 or 5 people by now, in the past 2 weeks. one person emailed me and said his driver worked. i emailed him back and got no reply. i also tried using rpm2cpio on the rpms offered on 3dfx's website. they compiled and didn't work either, but i should try that again. if someone here has their voodoo 3 working, a bunch of people would really like to hear from you! OK, here's what I did. 1)I apt-get removed my existing device3dfx-source and also removed /usr/src/modules/ which is where the source was. 2) apt-get install device3dfx-source. 3) cd /usr/src/ 4) tar zxfv device3dfx-source 5) cd modules # This dir is created by the above command 6) cd modules/device3dfx 7) ./debian/buildpkg # This as per the docs in /usr/share/doc/device3dfx-source/README.Debian 8) This time it compiled. Before when I ran this command it wouldn't compile, apparently I needed to clean up some stuff but I didn't know how. Re-installing the whole package provided me with a clean script. 9) The module will be located in /usr/src/modules/device3dfx as 3dfx.o 10) cp 3dfx.o /lib/modules/2.2.17/misc/ # obviously sub 2.2.17 for wherever your modules are. 11) According to /usr/src/modules/device3dfx/debian/README.debian do the following A) mknod /dev/3dfx c 107 0 B) make the group audio have rw permissions for /dev/3dfx C) make sure whatever user you want to use belongs to the group audio 12) insmod 3dfx 13) Start fragging # hopefully, this worked for me. Hope this helps, David Bellows
Re: 3dfx.o
what particular problems do you have? I have just upgraded 2.2.14 to 2.2.17 and recompiled modules (alsa and 3dfx) and everything worked fine. however, I introduced epochs (so that my kenrel/modules packages are not overwritten by debian ones) and now 3dfx complains about incorrect version, here's my post about the problem, do you have same problem or a different one? here's copy of my e-mail: I have compiled a kernel with --revision 99:jojda.2 kernel compiled OK, kernal package kernel-image-2.2.17_jojda.2_i386.deb (why is there no epoch in name?) I have 3dfx and alsa modules sources so I went on and did: make-kpkg modules_image (set MODULE_LOC first) it looks like alsa moduels where built correctly: make[2]: Leaving directory `/usr/src/modules/alsa-driver' make[1]: Leaving directory `/usr/src/modules/alsa-driver' Module /usr/src/modules/alsa-driver processed fine and package was created: alsa-modules-2.2.17_0.5.9d-1+jojda.2_i386.deb however 3dfx module failed: dh_builddeb --destdir=/usr/src/linux/.. dpkg-deb: parse error, in file `debian/tmp/DEBIAN/control' near line 2 package `device3dfx-module-2.2.17': error in Version string `2.3.4-2+99:jojda.2': epoch in version is not number dh_builddeb: command returned error code make[1]: *** [kdist_image] Error 1 make[1]: Leaving directory `/usr/src/modules/device3dfx' Module /usr/src/modules/device3dfx failed. Hit return to Continue no package created. is it a problem of 3dfx package builder? strange thing I noticed (epoch is in different places!): Package: alsa-modules-2.2.17 Version: 99:0.5.9d-1+jojda.2 Package: device3dfx-module-2.2.17 Version: 2.3.4-2+99:jojda.2 system: debian unstable, kernel 2.2.17 TIA erik David Bellows wrote: Hello all, At one point I had my Voodoo 3 working perfectly in Debian, but then I installed a new SB Live! which is where things went south. In order to get sound to work I upgraded to the latest (unstable) ALSA which in turn required a kernel update, etc. After a few hours I got it all working with the new kernel (2.2.17 as opposed to 2.2.17pre6 -- the default from potato). But when I tried to load the 3dfx module I got these errors: /lib/modules/2.2.17/misc/3dfx.o: unresolved symbol register_chrdev_R06af9881 /lib/modules/2.2.17/misc/3dfx.o: insmod /lib/modules/2.2.17/misc/3dfx.o failed /lib/modules/2.2.17/misc/3dfx.o: insmod 3dfx failed As I said before, I did have all this working with kernel 2.2.17pre6. So I attempted to follow the directions and recompile the 3dfx source for my new kernel. No go. I can't for the life of me get anything to work. So my question is, has anyone got their Voodoo3 working with the woody kernel 2.2.17? And would the compiled module 3dfx.o also work on my machine (AMD K6II-300)? And so, would somebody please send me a copy? Thanks, David Bellows -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
