| View previous topic :: View next topic |
| Author |
Message |
TrevorCampbell
n00b
Joined: 16 Apr 2006
Posts: 15
|
 Posted: Mon May 15, 2006 10:28 am Post subject: |
 |
|
| VinzC wrote: | @TrevorCampbell
First you should use modprobe -r instead of rmmod. I had also such troubles with ipw3945 but the latest version from portage (1.0.2) seemed to fix these (you'll probably have to unmask them using ~ARCH). |
I seem to have the latest
| Code: | # ACCEPT_KEWORDS="~x86" emerge -pv ipw3945
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] net-wireless/ipw3945-1.0.3 -debug 0 kB |
|
|
| Back to top |
|
 |
Jobbe
n00b
Joined: 24 Feb 2006
Posts: 29
Location: Darmstadt (Germany)
|
| Posted: Sat May 20, 2006 10:32 am Post subject: Kernel tainted |
|
|
Having given up on trying to get gentoo working correctly I decided I had to give it one more shot and threw out Win again.
So I installed ipw3945 from portage, did 'modules-update' as the installer
instructed me to do and also added 'ipw3945' to /etc/modules.autoload.d/kernel-2.6.
| Code: | cat /usr/src/linux/.config|grep IEE80211
# CONFIG_IEEE80211 is not set |
During boot, loading of ipw3945 fails.
This is the end of dmesg:
| Code: | ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, 1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ipw3945: no version for "ieee80211_wx_get_encodeext" found: kernel tainted.
ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.0.3mpr
ipw3945: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Real Time Clock Driver v1.12ac
|
So my kernel set the tainted flag. I read this might have something to do with software
beeing proprietary, but where's the connection to ieee80211?
Well, the thing is, after boot eth1 (my wlan interface) doesn't exist. ipw3945d
does not run either. When start the regulatory daemon manually, the interface pops up and everything works just fine.
Any ideas?
lspci:
| Code: | 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller (rev 01)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
09:09.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b4)
09:09.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 09)
09:09.2 Class 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 18)
09:09.3 System peripheral: Ricoh Co Ltd Unknown device 0843
09:09.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 09)
09:09.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 04)
|
|
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Sat May 20, 2006 12:57 pm Post subject: |
|
|
@Jobbe: Have you installed ieee80211 from portage?
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
Jobbe
n00b
Joined: 24 Feb 2006
Posts: 29
Location: Darmstadt (Germany)
|
| Posted: Sat May 20, 2006 2:45 pm Post subject: |
|
|
| Yeah, that's what I did. I also removed the inkernel stuff with this somewhat lengthy command"/bin/.. ... remove-old ... ..", if you know what I mean. |
|
| Back to top |
|
|
Jobbe
n00b
Joined: 24 Feb 2006
Posts: 29
Location: Darmstadt (Germany)
|
| Posted: Mon May 22, 2006 12:44 am Post subject: |
|
|
Allright guys, I managed to fix it, although this seems like a rather ugly workaround. Anyway, here is what I did:
-removed ipw3945 from /etc/modules.autoload.d/kernel-2.6
-created /etc/init.d/ipw3945
| Code: |
#!/sbin/runscript
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
start() {
modprobe ipw3945
}
stop() {
ipw3945d --kill
sleep 0.5
modprobe -r ipw3945
}
|
-made sure this file was executable: chmod +x /etc/init.d/ipw3945
-added it to default runlevel: rc-update add ipw3945 default
And boom, it worked. Weeeehaaa  |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Mon May 22, 2006 7:43 pm Post subject: |
|
|
Ah I see: ipw3945 must not be in /etc/modules.autoload.d/kernel-2.6 otherwise coldplug/hotplug won't have any chance to trigger the mechanism that makes the daemon run automatically when the module is inserted. That file must be used only with modules that coldplug/hotplug do not succeed in loading or that are loaded incorrectly (e.g. 8139too and 8139cp).
On my laptop that file is almost empty - there is only evdev. coldplug takes care of inserting ipw3945 module when scanning PCI for hotplug devices. Then the daemon is run thanks to the insert/remove instructions in /etc/modules.d/ipw3945.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
Jobbe
n00b
Joined: 24 Feb 2006
Posts: 29
Location: Darmstadt (Germany)
|
| Posted: Mon May 22, 2006 7:54 pm Post subject: |
|
|
Oh, so my little script is useless? Lol. At least it looked like it was working, I guess that's enough. Give me praise. 
Thanks for making things a little clearer 
edit: I tried not using my little script thus leaving everything to coldplug - it doesn't work. So my script is back on duty and I'm happy :] |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Tue May 23, 2006 7:56 am Post subject: |
|
|
This is yet something I don't understand. It works as mentionned by Intel only for a couple of people if I track down the comments that have been posted. Not that I don't trust what they say but I'm really curious as to know what could prevent the daemon from loading...
Maybe one hint: on my machine there are a lot of services that take time to start: MySQL, Apache, XDM, ntp, hald, cups, ssh... Maybe giving some time for the daemon to start is key, I'm not sure. But I already noticed WiFi takes quite a moment to start and I couldn't get rid of some errors until I added a few time-consuming services to my default runlevel.
Something that I find very strange is that the WiFi led starts blinking (i.e. like when scanning WiFi networks) as soon as XDM starts. If I remove XDM from the default runlevel the WiFi led remains still. It starts blinking when I start X again. So there must be an interaction between X and the WiFi led I think - even if it sounds crazy. So I also think that might be another hint as to why many of us can't succeed in having the regulatory daemon automatically start.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
pinky99
n00b
Joined: 19 Nov 2004
Posts: 45
|
| Posted: Tue May 23, 2006 10:33 am Post subject: ieee80211 and kernel |
|
|
Hi all,
so i have a question concerning the ieee80211 software:
As far as I understand from the READMEs and the previous posts, the ieee80211 stack delivered by kernel 2.6.16 has not a sufficient version of this stack, and you have to install it separately.
So at what kernel is a sufficient version included, maybe in 2.6.17?
Has anybody tried that?
I really don't like installing additional kernel modules on its own, because I have to think about them and also reinstall it everytime I change to a new kernel.
So at this state I don't desparately need wireless network, and I therefore would wait until it is included in the normal kernel. But if someone points me, that it's already in 2.6.17mm I would go for that, though I couldn't find any hints about the used 80211 versions in the different kernel versions...
Thanks in advance,
Maximilian |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Tue May 23, 2006 4:52 pm Post subject: Re: ieee80211 and kernel |
|
|
| pinky99 wrote: | | So at this state I don't desparately need wireless network, and I therefore would wait until it is included in the normal kernel. |
IMHO you might have to wait very long for ipw3945 isn't just like a modified ipw2200. See the proprietary daemon from Intel. The complete package depends on that proprietary binary, which doesn't comply with the GPL. Unless devs have reversed engineered that binary I don't expect any kernel built-in feature for that card before long. But I might be wrong.
I personnally don't like the concept of a "regulatory" daemon. As if there were anything a kernel module couldn't do... Such a binary is good for Intel to keep control on their chip but not for Linux. Ok, what about nVidia or ATI then? But we still have the choice (GPL'ed or proprietary drivers) in the latter case. In the former we don't.
So - coming back to your question - feel (hem) free to use the module from portage anyway. That's what all of us do at the moment and I don't think we all change our kernel that often. So it's not (yet) a pain in the ***. Just don't forget to patch for SD-Card reader - which will in turn be included in 2.6.17.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
Jobbe
n00b
Joined: 24 Feb 2006
Posts: 29
Location: Darmstadt (Germany)
|
| Posted: Tue May 23, 2006 5:12 pm Post subject: |
|
|
Hm doesn't anybody want to do some rev-eng and write a nice little GPL'd module that works like a charm and makes our lives easier? 
Nah, but to be honest, I think if the driver works well enough for most people there won't be a really _free_ version too soon... |
|
| Back to top |
|
|
bigmauler
Apprentice
Joined: 25 Apr 2005
Posts: 174
Location: Seattle, WA
|
| Posted: Tue May 23, 2006 5:15 pm Post subject: |
|
|
a new version is out. It is supposed to be a bug fix.
_________________
2GHz celeron, 512MB, Gentoo Media/network server
Main rig is a homemade, e7300 with 4GB ram, Radeon 5850, Asus P5Q SE mobo
My last.fm profile |
|
| Back to top |
|
|
bigmauler
Apprentice
Joined: 25 Apr 2005
Posts: 174
Location: Seattle, WA
|
| Posted: Wed May 24, 2006 6:16 am Post subject: |
|
|
I often run into this after using the web for a little while...
Output of dmesg:
| Code: | ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00030000
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00030000
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd DAEMON (0x10) seq 0x040D ser 0x00030000
ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00030000
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00050000
ipw3945: Can't stop Rx DMA.
|
Has anyone run into this? Solutions?
_________________
2GHz celeron, 512MB, Gentoo Media/network server
Main rig is a homemade, e7300 with 4GB ram, Radeon 5850, Asus P5Q SE mobo
My last.fm profile |
|
| Back to top |
|
|
max2k5
n00b
Joined: 15 May 2006
Posts: 35
|
| Posted: Wed May 24, 2006 7:22 am Post subject: Re: ieee80211 and kernel |
|
|
| VinzC wrote: | | pinky99 wrote: | | So at this state I don't desparately need wireless network, and I therefore would wait until it is included in the normal kernel. |
IMHO you might have to wait very long for ipw3945 isn't just like a modified ipw2200. See the proprietary daemon from Intel. The complete package depends on that proprietary binary, which doesn't comply with the GPL. Unless devs have reversed engineered that binary I don't expect any kernel built-in feature for that card before long. But I might be wrong.
|
Hmm, okay, I see. But if at least just the 80211-stack was of the right version in the kernel, I wouldn't have to patch the kernel as I have to do now to install the latest (not in kernel included) version of the 80211.
BTW, did anyone try the windows drivers via ndisloader, ndiswrapper or linuxant?
max |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Wed May 24, 2006 2:45 pm Post subject: Re: ieee80211 and kernel |
|
|
| max2k5 wrote: | | BTW, did anyone try the windows drivers via ndisloader, ndiswrapper or linuxant? |
Forget about it...
P.S.: I tried ndiswrapper with my Centrino Duo (it's mentionned you have to turn off SMP in your kernel configuration). It didn't work.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Wed May 24, 2006 2:50 pm Post subject: |
|
|
| bigmauler wrote: | I often run into this after using the web for a little while...
Output of dmesg:
| Code: | ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00030000
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00030000
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd DAEMON (0x10) seq 0x040D ser 0x00030000
ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00030000
ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
ipw3945: Microcode SW error detected. Restarting.
ipw3945: Error Reply type 0x000000FF cmd TX (0x1C) seq 0x0000 ser 0x00050000
ipw3945: Can't stop Rx DMA. |
|
I also experience such sort of messages. Before that I got kernel module panics instead. Now all I get at worst is a more or less long hanging period. The computer doesn't respond and seems locked up for a short while and then unfreezes by itself. Everytime I looked at the log there was such a message.
Note however my laptop froze for a very long period (more than I could bear) yesterday evening. I had to forcibly turn it off.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
pinky99
n00b
Joined: 19 Nov 2004
Posts: 45
|
| Posted: Wed May 24, 2006 2:54 pm Post subject: Re: ieee80211 and kernel |
|
|
| VinzC wrote: | | max2k5 wrote: | | BTW, did anyone try the windows drivers via ndisloader, ndiswrapper or linuxant? |
Forget about it...
P.S.: I tried ndiswrapper with my Centrino Duo (it's mentionned you have to turn off SMP in your kernel configuration). It didn't work. |
Actually I tried it today (ndiswrapper-1.15, with W39N51.SYS windows driver) on my Core Duo Thinkpad (SMP, x86, 2.6.16-r7), and it compiled well, and even loaded without a problem!
I just haven't tried to connect to an AP, but I will try that tonight and I'll inform you.
max |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Thu May 25, 2006 10:47 am Post subject: |
|
|
Thanks pinky99. I don't need ndiswrapper anymore for ipw3945 works as expected but I'm sure it'll help others.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
dmartinsca
Guru
Joined: 09 Dec 2005
Posts: 303
Location: Ontario, Canada
|
| Posted: Fri May 26, 2006 9:19 pm Post subject: |
|
|
| I've just moved from x86 to ~x86 and ipw3945d has stopped loading on boot. This update included moving from <udev-089 to udev-090 so I had to remove coldplug as udev(i think?) now includes the same features. I added !net.* to RC_PLUG_SERVICES so that the startup scripts for eth0 and eth1 are not started when the modules are loaded. I get no output from ipw3945d so it seems it's not being run at boot even though the module is loaded automagically. |
|
| Back to top |
|
|
dirtyepic
Developer
Joined: 22 Oct 2004
Posts: 1614
Location: sk.ca
|
| Posted: Sat May 27, 2006 11:05 pm Post subject: |
|
|
blame udev's retarded 'hey let's load every module we find whether the user wants us to or not' mentality. it loads the module but doesn't start the daemon.
here's a bit of a workaround:
| Code: | # cat /etc/conf.d/local.start
/sbin/modprobe --ignore-install ipw3945; sleep 0.5; /sbin/ipw3945d --quiet |
| Code: | # cat /etc/conf.d/local.stop
/sbin/ipw3945d --kill; /sbin/modprobe -r --ignore-remove ipw3945 |
| Code: | # cat /etc/conf.d/net
# ethernet (eth0)
config_eth0=( "dhcp" )
dhcpcd_eth0=( "-t 15" )
# wireless (eth1)
modules=( "iwconfig" )
config_eth1=( "dhcp" )
key_dirtyepic=( "s:************** enc open" )
dhcpcd_eth1=( "-t 20" )
preup() {
case ${IFACE} in
"eth0" )
if ethtool ${IFACE} | grep -q 'Link detected: no'; then
ewarn "No link on ${IFACE}, aborting configuration"
return 1
fi
;;
"*" )
return 0
;;
esac
} |
| Code: | # cat /etc/conf.d/rc | grep "PLUG" | grep -v "#"
RC_HOTPLUG="yes"
RC_COLDPLUG="yes"
RC_PLUG_SERVICES="" |
the preup bit is needed to get the interface automatically configured by /etc/conf.d/net. otherwise you'll have eth1 present but not enabled. it also keeps eth0 from trying to get an address from DHCP when there's no cable plugged in. you'll need to emerge ethtool for it all to work.
_________________
by design, by neglect
for a fact or just for effect |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Mon May 29, 2006 4:44 pm Post subject: |
|
|
| dirtyepic wrote: | | blame udev's retarded 'hey let's load every module we find whether the user wants us to or not' mentality. it loads the module but doesn't start the daemon. |
So if udev can be responsible for the daemon not to start while on my machine the driver loads fine and the daemon activates itself normally then I have a good version of udev, right?
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
agnitio
Tux's lil' helper
Joined: 17 Apr 2004
Posts: 136
|
| Posted: Thu Jun 01, 2006 8:17 am Post subject: |
|
|
I've had the same problem on my Asus A6J. My solution was a simple init-script that started the daemon:
/etc/init.d/ipw3945d:
| Code: |
#!/sbin/runscript
depend() {
before net
}
start() {
ebegin "Starting ipw3945d"
start-stop-daemon --start --quiet --exec /sbin/ipw3945d
eend $?
}
stop() {
ebegin "Stopping ipw3945d"
start-stop-daemon --stop --quiet --pidfile /var/run/ipw3945d.pid
eend $?
}
|
I'm not sure I got the depend part right though because it seems it does not start until after my network interfaces, although it's early enough to make stuff work. |
|
| Back to top |
|
|
YourDoom123
Apprentice
Joined: 06 Mar 2004
Posts: 163
|
| Posted: Sun Jun 04, 2006 6:40 pm Post subject: |
|
|
I'm running an Acer 5672WLMi that uses the intel 3945a/b/g wifi card
The problem:
The driver installs fine... ie, emerge finishes w/o any problems. But, when I try to do a modprobe ipw3945, it spits out a bunch of errors, which I will do my best to type out here (different machine):
| Code: |
WARNING: Error inserting ieee80211_crypt (/lib/modules/2.6.17-rc2/net/ieee80211/ieee80211_crypt.ko): Invalid module format
WARNING: Error inserting ieee80211 (/lib/modules/2.6.17-rc2/net/ieee80211/ieee80211.ko): Invalid module format
WARNING: Error inserting ieee80211_crypt (/lib/modules/2.6.17-rc2/net/ieee80211/ieee80211_crypt.ko): Invalid module format
WARNING: Error inserting ieee80211 (/lib/modules/2.6.17-rc2/net/ieee80211/ieee80211.ko): Invalid module format
FATAL: Error inserting ipw3945 (/lib/modules/2.6.17-rc2/net/wireless/ipw3945.ko): Invalid module format
2006-06-04 00:25:12: ERROR: opening /sys/bus/pci/drivers/ipw3945:
No such file or directory (2)
2006-06-04 00:25:12: ERROR: Could not find Intel PRO/Wireless 3945ABG Network Connection
FATAL: Error running install command for ipw3945
|
my kernel is actually 2.6.17-rc3-no2, but modprobe kept looking for the 2.6.17-rc2 folder, so i created a link to the actual folder, and that fixed my initial problems. Running modules-update yielded the addition of the second set of errors (everything starting with the first 2006). I really need to get my wireless up and running. It's pretty much essential. If I can't, I have to bite the bullet, and switch distros. I love gentoo, and would hate to have to do that, but I've been struggling with this for weeks. Any help is appreciated.
_________________
Acer Aspire 5672 |
|
| Back to top |
|
|
VinzC
Advocate
Joined: 17 Apr 2004
Posts: 4342
Location: Spa (Belgium)
|
| Posted: Sun Jun 04, 2006 7:32 pm Post subject: |
|
|
@YourDoom123: Did you switch GCC recently?
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root” |
|
| Back to top |
|
|
YourDoom123
Apprentice
Joined: 06 Mar 2004
Posts: 163
|
| Posted: Sun Jun 04, 2006 9:58 pm Post subject: |
|
|
damn... and i thought tht went bug free...
no, i didn't switch gcc (this is a fresh install), but i am using gcc 4.2. Someone give me confirmation that this is the problem before i switch it, cause it means hours of recompiling...
EDIT: i should have done it from the start: keep both gcc 4.2 and 4.1.1 installed to switch between when things broke... duh! im such an idiot sometimes...
EDIT: I'm trying another recompile, but the first one did nothing. I get the exact same errors. Any new ideas?
_________________
Acer Aspire 5672 |
|
| Back to top |
|
|
|
Kernel & Hardware
