SUSE / openSUSEThis Forum is for the discussion of Suse 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.
My console loses the directory # etc, and just sits there. Does this mean it is working, or does it mean that it froze / glitched? Im still letting it sit for now, but I dont know how long Im supposed to wait.
you only have to type "modprobe ndiswrapper" The first line followed by # is just a comment for your reference and not to be typed. Or you might know that already, in which case you may indeed be hung. Why? Dunno... Are you operating as root? I assume so since you look for the # prompt to return which is root's own prompt. You can see if nothing happened by presseing CTRL-C and seeing if the prompt returns; and then follow the next step in that script to look for errors. If the prompt doesn't return you could press alt-f2 to get a new tty and login as root there. Run "ps aux" and see if modprobe is still running, if so get it's PID number and kill it using "kill ?some pid?" Then type exit to end that session, and alt-f1 to return to your first tty if necessary.
Last edited by jonnycando; 01-27-2007 at 03:15 PM.
it doesnt freeze, it just asks for another line
after modprobe ndiswrapper (and you press enter)
it seems like it does nothing but you have to now next
iwconfig
it doesnt freeze, it just asks for another line
after modprobe ndiswrapper (and you press enter)
it seems like it does nothing but you have to now next
iwconfig
Actually it was doing something different, was going to new line but not giving the prompt. I finally made it work right, but then I broke some other stuff and ended up reinstalling. Gonna give madwifi another shot.
madwifi installs (or seems to) but.. I dont know what to do next. I have run "madwifi-0.9.2.1-0.1.i586.rpm" and it opens yast and goes through full setup process, but afterwords will not sense network or anything.. and when I try to setup ndiswrapper it fails with a multitude of errors on dmesg | grep ndiswrapper
Though there were errors, I tried the next item (ifup wlan0) and it couldnt find wlan0. Im completely lost and pissed by now :P
read the part that says Installation of kernel modules, so you add the madwifi to your installation source in yast, download and install through yast and then reboot and it should work
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.