feisty needs newer ndiswrapper

2007-02-24 Thread golfer
I see feisty currently has only ndiswrapper 1.30, while current stable version is 1.37. I need at least 1.31 to get my wireless card working. Could we get an upgrade? golfbuf :~$ modinfo ndiswrapper filename: /lib/modules/2.6.20-8-generic/kernel/ubuntu/misc/ndiswrapper/ndiswrapper.ko license:

kernel 2.6.17 build from source fails

2007-03-13 Thread golfer
I'm trying to rebuild the kernel packages from the source package (linux-source-2.6.17_2.6.17.1.orig.tar.gz). I'm using this command: golfbuf:~/Desktop/bld.linux/linux-source-2.6.17-2.6.17.1$ dpkg-buildpackage -rfakeroot -uc -us after about 4 hours, it fails with this message: install -p-m

cant find fglrx kernel source for feisty

2007-03-15 Thread golfer
I'm trying to build the fglrx module for my custom kernel on feisty, using module-assistant. But, it appears there is no fglrx-kernel-src in the archive. Anyone know where it is or how I can get it to build for my custom kernel? The ATI version will not compile on current kernels, so I need the

feisty ndiswrapper 1.38 windows driver not 32-bit error

2007-03-17 Thread golfer
I'm running feisty and was unable to get my dell 1500n wireless working under ndiswrapper 1.30. But, the wifi works under edgy with ndiswrapper 1.3.1. On feisty, the latest update to ndiswrapper 1.38 should have fixed it, but now I get a strange error about 32-bit. golfbuf :~$ modinfo ndiswrappe

Re: feisty ndiswrapper 1.38 windows driver not 32-bit error

2007-03-18 Thread golfer
On 3/18/07, Mark Reitblatt <[EMAIL PROTECTED]> wrote: > I'm sorry that you're having this problem, but this is not the > appropriate place to get help on this. Please file a bug against > ndiswrapper: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+filebug > . Feel free to email me the bug n

Re: [Bug 89896] Re: [herd-5] no wlan0 device after loading ndiswrapper

2007-03-18 Thread golfer
On 3/18/07, Mark Reitblatt <[EMAIL PROTECTED]> wrote: > The problem you are describing sounds like a different bug than the one > reported here. Please open another bug, and put all of that info in > there. Feel free to let me know the number of the new bug report. ok, it's bug 93566. regards, -