SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all, I'm facing some problems with loading those two modules, ndiswrapper and scanner.
My scanner was recognized by the kernel normally, I checked this out by needed commands. Then I installed the drivers with iscan but the scanner module can not be loaded. I try the command bellow (the one that the installation manual says):
Code:
modprobe scanner vendor=0x04b8 product=0x0818
And I get back FATAL: No scanner module was found.
The default 2.4 kernel of Slackware 10.2 had it, and the scanner was working perfectly. What can I do now?
The second issue which I face with the ndiswrapper module has to do with the wireless card. I installed the Windows driver for the card, after following the instrunctions. The driver is installed successfully but again then, when I try to load the module by
Code:
modprobe ndiswrapper
i get back the same error as before FATAL: No ndiswrapper module foun. What should I do here?
If you see your driver, and it sees the hardware, you can do 'ndiswrapper -m' to write the configuration for modprobe. (Don't know if you did this, this is just what I did to get mine working.)
After doing that just one time, modprobe was able to load my driver for me without any problem. Curiously, I have to press my wireless adapter button twice to get it to turn on under Linux, where in Windoze it was automatically on by default (not what I wanted). Took me quite a while to figure out I had to turn the adapter on by pushing the button, and then having to do it twice, not just once.
Also, I had already wrote the configuration to modprobe by that command. If I go to the directory /etc/modprobe.d/ I will find the ndiswrapper file containing information about the wireless card:
Quote:
alias pci:v000017FEd00002220sv*sd*bc*sc*i* ndiswrapper
alias pci:v000017FEd00002220sv00001468sd00000305bc*sc*i* ndiswrapper
But I still try to load the module by modprobe ndiswrapper and I get the same error message. Although, when I press the button to switch on the wireless it lights up normally but no wireless at all. Any other ideas?
Which kernel are you using now? I thought the scanner module was deprecated with newer kernels. I couldn't get iscan to work at all for mine, but sane + backend works ok.
I'm using 2.6.7.13. Well, I run sane-find-scanner and it finds my scanner, but then when I run xsane and try to find the scanner nothing is found.
I checked on SANE site if the scanner is supported and it's supported with status set to "good".
I edit the epson.conf in the folder /etc/sane.d/ with the proper information concerning the scanner, Epson libraries exist in /usr/lib/sane and I also copied the proper backend files into /usr/include/sane. Still the scanner doesn't want to work. I run scanimage and I get "No SANE device found". How did you configure yours?
Last edited by Panagiotis_IOA; 10-13-2006 at 03:00 PM.
I can't help much with the scanner, so I'll let someone more knowledgeable help you there. I found that my XP had two different but similar drivers, and ndiswrapper (or modprobe, can't remember which) didn't recognize the one that XP was using (bcmwl5), but worked fine with the other (bcmwl5a). If you don't have additional drivers for yours, you may want to check if others have found drivers that work with that chipset.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.