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