Ixthusdan Posted June 13, 2007 Share Posted June 13, 2007 I did not think that I am an idiot, but perhaps I am wrong. What I am trying to do (again) is get Fedora going wireless without plugging in the ethernet. I have downloaded the 2 files, one for ndiswrapper and the matching kdml for the running kernel. Although ndiswrapper is claimed to be installed by rpm, the system does not recognize the command "ndiswrapper" and so I cannot insert the driver so that the system sees the device. No device, no configuration. I can get Mandriva going without ever having to plug in the ethernet, so I should be able to do the same with Fedora. What am I missing? Link to comment Share on other sites More sharing options...
JonEberger Posted June 13, 2007 Share Posted June 13, 2007 I'm going to play stupid and ask the following although i bet you've already thought of this. 1.) Are you root? 2.) /sbin/ndiswrapper? 3.) How'd you install the .rpm file? -Uvh? Any warnings? Just a few thoughts right off the bat. Keep the comments coming. Jon Link to comment Share on other sites More sharing options...
iphitus Posted June 13, 2007 Share Posted June 13, 2007 yeah, by default fedora does not have /usr/sbin and /sbin in root's path. Append the full path, either /sbin/ndiswrapper or /usr/sbin/ndiswrapper. Additionally, it doesnt enable networkmanager by default, enable this in services, and start it and you'll get a new icon in your systray you can use for wireless instead of the pathetic fedora tool. James Link to comment Share on other sites More sharing options...
ianw1974 Posted June 13, 2007 Share Posted June 13, 2007 In Fedora/Red Hat, just typing su is not enough, you must type: su - to get the paths correctly. Alternatively, edit /etc/bashrc and add: alias su="su -" this is what I do on my Fedora/Red Hat installs. I noticed no ndiswrapper packages on my system, but if you add the freshrpms repo, you can get a dkms-ndiswrapper package installed. Link to comment Share on other sites More sharing options...
Ixthusdan Posted June 13, 2007 Author Share Posted June 13, 2007 Thanks for the clues, everybody. I guess I am too Mandrivacintric or something. I'll be back after I give this a shot. Link to comment Share on other sites More sharing options...
Ixthusdan Posted June 13, 2007 Author Share Posted June 13, 2007 OK. From Fedora 7, I am a partial idiot. B) The su - thing was what I did not know. So now I can be a "successful" root as opposed to a "fake" root in Fedora. The next thing I forgot, and why I am an idiot, is that I did not blacklist bcm43xx, which I have as yet not been able to work on any system, including Mandriva. I always use ndiswrapper. At any rate, the network service also is much better than the Fedora tool. Thank you all for the help. Link to comment Share on other sites More sharing options...
ianw1974 Posted June 14, 2007 Share Posted June 14, 2007 In case you're not sure of where in Fedora 7, it's /etc/modprobe.d/blacklist and you list the module here. Although I expect you already tried that for blacklisting the module. Hope it works/worked. Link to comment Share on other sites More sharing options...
jlc Posted June 14, 2007 Share Posted June 14, 2007 Alternatively, edit /etc/bashrc and add: alias su="su -" Keep in mind there are some good reason not to alias it ;) If you want to fire a gui installer as root you wont get X widgets so you will need to use just "su" not "su -". You can always add sbin to your path to make things like that easier. vi ~/.bash_profile And add. PATH=$PATH:$HOME/bin:/sbin:/usr/sbin Link to comment Share on other sites More sharing options...
ianw1974 Posted June 14, 2007 Share Posted June 14, 2007 Not sure I understand what you mean, I use su - aliased, and yet, I can stil launch X apps for installing? :unsure: Link to comment Share on other sites More sharing options...
jlc Posted June 14, 2007 Share Posted June 14, 2007 Hurm, it does work now. It didn't used to. Maybe I'm getting to old...... Link to comment Share on other sites More sharing options...
iphitus Posted June 15, 2007 Share Posted June 15, 2007 Hurm, it does work now. It didn't used to. Maybe I'm getting to old...... i did it the path way too. makes more sense to me -- and it's global, not just for my user. Link to comment Share on other sites More sharing options...
ianw1974 Posted June 15, 2007 Share Posted June 15, 2007 If you edit /etc/bashrc, then it is also global for all users ;) This is what I did :) And less typing too ;) Link to comment Share on other sites More sharing options...
iphitus Posted June 15, 2007 Share Posted June 15, 2007 If you edit /etc/bashrc, then it is also global for all users ;) This is what I did :) And less typing too ;) i was a bit fancier, i made /etc/profile.d/sbin.sh and added the PATH change there. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now