 |
 |
 |
 |
| Laptop Help on using Fedora on laptops. LCD screens, APM, PCMCIA, etc. |

2009-10-17, 10:42 AM CDT
|
 |
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 2,976

|
|
Quote:
Originally Posted by BurningFool
EDIT: Nevermind, forgot to add RPMfusion nonfree repositories. Stupid Burning Fool is stupid.
EDIT: Installed the packages, but my wireless card still doesn't appear when I click on the network icon in the status bar.
|
Hardware switch on ?
Also, you might need a reboot or try IIRC right
|

2009-10-17, 11:14 AM CDT
|
|
Registered User
|
|
Join Date: Oct 2009
Posts: 4

|
|
|
Poifect! Thanks Nokia! Your cellphones are alright!
|

2009-10-28, 02:30 PM CDT
|
 |
Registered User
|
|
Join Date: Aug 2007
Location: Brasil
Posts: 440

|
|
Hmm. Got the same problem here after updating the kernel.
This is what I have:
Code:
[root@leonidas ~]# uname -r
2.6.30.9-90.fc11.x86_64
[root@leonidas ~]# rpm -qa | grep iwl3945
iwl3945-firmware-15.32.2.9-1.fc11.noarch
I have the (bad) habit of deleting the previous kernel after installing a new one.
So can't switch back here.
If i do "ifconfig" wlan0 won't be there. I can see that NetworkManager detects the wifi switch on/off though.
modprobe iwl3945 didn't work
Any ideas?
|

2009-10-28, 03:13 PM CDT
|
 |
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 2,976

|
|
Quote:
Originally Posted by M4rc0
Hmm. Got the same problem here after updating the kernel.
This is what I have:
Code:
[root@leonidas ~]# uname -r
2.6.30.9-90.fc11.x86_64
[root@leonidas ~]# rpm -qa | grep iwl3945
iwl3945-firmware-15.32.2.9-1.fc11.noarch
I have the (bad) habit of deleting the previous kernel after installing a new one.
So can't switch back here.
If i do "ifconfig" wlan0 won't be there. I can see that NetworkManager detects the wifi switch on/off though.
modprobe iwl3945 didn't work
Any ideas?
|
Post
Code:
rpm -qa|grep -e kernel -e NetworkManager
|

2009-10-29, 12:22 AM CDT
|
 |
Registered User
|
|
Join Date: Aug 2007
Location: Brasil
Posts: 440

|
|
Code:
[root@leonidas ~]# rpm -qa | grep -e kernel -e NetworkManager
NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64
kerneloops-0.12-5.fc11.x86_64
NetworkManager-vpnc-0.7.0.99-1.fc11.x86_64
kernel-headers-2.6.30.9-90.fc11.x86_64
NetworkManager-0.7.1-8.git20090708.fc11.x86_64
NetworkManager-openvpn-0.7.0.99-1.fc11.x86_64
kernel-devel-2.6.30.9-90.fc11.x86_64
NetworkManager-glib-0.7.1-8.git20090708.fc11.x86_64
kernel-firmware-2.6.30.9-90.fc11.noarch
kernel-2.6.30.9-90.fc11.x86_64
NetworkManager-openconnect-0.7.0.99-5.fc11.x86_64
|

2009-10-29, 08:13 AM CDT
|
|
Registered User
|
|
Join Date: Dec 2008
Location: India
Age: 21
Posts: 25

|
|
|
did u try to run modprobe wl as root?
|

2009-10-29, 08:37 AM CDT
|
|
Community Manager
|
|
Join Date: Jun 2006
Posts: 3,624

|
|
Quote:
|
Originally Posted by blueboy
did u try to run modprobe wl as root?
|
I think the topic has moved from broadcom-wl to iwl3945.
Quote:
|
Originally Posted by M4rc0
modprobe iwl3945 didn't work
|
Maybe it's already loaded and something else is wrong. Check with lsmod | sort.
Last edited by stoat; 2009-10-29 at 08:41 AM CDT.
|

2009-10-30, 12:22 PM CDT
|
 |
Registered User
|
|
Join Date: Aug 2007
Location: Brasil
Posts: 440

|
|
|
Hi!
I guess the modprobe did work.
Next time I turned on the laptop, the wifi led started blinking and voila, got internet.
|

2009-10-30, 12:39 PM CDT
|
|
Community Manager
|
|
Join Date: Jun 2006
Posts: 3,624

|
|
Quote:
|
Originally Posted by M4rc0
I guess the modprobe did work.
Next time I turned on the laptop, the wifi led started blinking and voila, got internet.
|
Good. But I don't know about modprobe doing it. I have always believed that the manual modprobe command will load a kernel module but not configure anything that will survive a reboot (I'm willing to be taught something new though). It's been my impression that sometimes we can modprobe and restart services and whatever without success, but then a reboot can sometimes work wonders. And this is not the first time I have read about that happening regarding wireless.
|

2009-10-30, 04:40 PM CDT
|
 |
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 2,976

|
|
Quote:
Originally Posted by stoat
Good. But I don't know about modprobe doing it. I have always believed that the manual modprobe command will load a kernel module but not configure anything that will survive a reboot (I'm willing to be taught something new though). It's been my impression that sometimes we can modprobe and restart services and whatever without success, but then a reboot can sometimes work wonders. And this is not the first time I have read about that happening regarding wireless.
|
The strange thing to me was the report on iwl3945. I ran it on all the kernels in F7->F11 (albeit on i386 only due to CPU limitation) and never had a glitch. Modprobe was only supposed to load a driver but perhaps ifup was needed or a hardware off/on switch to make it visible to NM.
|

2009-11-06, 12:44 PM CST
|
|
Registered User
|
|
Join Date: Dec 2008
Location: India
Age: 21
Posts: 25

|
|
|
Wifi again stopped working in 2.6.27.38-170.2.113.fc10.i686
|

2009-11-06, 01:19 PM CST
|
|
Community Manager
|
|
Join Date: Jun 2006
Posts: 3,624

|
|
Quote:
|
Originally Posted by blueboy
Wifi again stopped working in 2.6.27.38-170.2.113.fc10.i686
|
Hello blueboy,
Well, the kmods for that kernel are in the RPM Fusion repo. So do all the usual things. - Review the installed packages. They should all make sense...
Code:
rpm -qa | grep -e kernel -e kmod-wl -e broadcom-wl | sort
- Review the loaded modules. As you know, wl should be there and conflicting modules should not be there...
- Reboot into the previous kernel and check for wireless there (to rule out other parts of the network).
P.S.: I'm not sure your situation was ever really right. You should not have had to add that modprobe command to rc.local. That's usually not necessary to make the wl module load.
Last edited by stoat; 2009-11-06 at 07:11 PM CST.
|

2009-11-06, 02:21 PM CST
|
 |
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 2,976

|
|
Quote:
Originally Posted by blueboy
Wifi again stopped working in 2.6.27.38-170.2.113.fc10.i686
|
Don't want to sound cynical, but F10 will be an an EOL product in a matter of weeks. Therefore no more updates, no more support whatsoever. It's best to backup data and install and install F12. Read this post on Adam Williamson's blog too. http://www.happyassassin.net/2009/11...2-crunch-time/
As I see F12 right now, you should have a hassle free experience installing/running it, and as long as you keep updating it regularly (daily would be best) I don't think you'll have any more problems. And even if you do, you'll have a swift resolution provided you file a bug report.
|

2009-11-07, 07:56 AM CST
|
|
Registered User
|
|
Join Date: Dec 2008
Location: India
Age: 21
Posts: 25

|
|
|
Thing got solved today after the kmod-wl got updated.
|

2009-11-07, 10:46 AM CST
|
 |
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 2,976

|
|
Quote:
Originally Posted by blueboy
Thing got solved today after the kmod-wl got updated.
|
Next time -and even now- you could avoid this complication and spare us the time trying to troubleshoot a non-issue. All you need to do is install akmod-wl package and your much needed driver will be built automagically regardless of the kernel installed. You need rpmfusion nonfree enabled, but I think you already have it.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Automatic Translations (Powered by  ):
All times are GMT -7. The time now is 07:16 AM CST.
|
|
 |
 |
 |
 |
|
|