| View previous topic :: View next topic |
| Author |
Message |
alienvenom
Tux's lil' helper
Joined: 12 Jan 2005
Posts: 123
Location: San Francisco, CA
|
 Posted: Wed May 16, 2007 10:14 pm Post subject: |
 |
|
| what does using the kernel patch give you over the ebuild? |
|
| Back to top |
|
 |
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Wed May 16, 2007 10:17 pm Post subject: |
|
|
| alienvenom wrote: | | what does using the kernel patch give you? |
It allows you to skip the driver from portage.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Thu May 17, 2007 6:57 pm Post subject: |
|
|
I don't get a network interface after boot. ipw3945 module is loaded, ipw3945d started.
I have to rmmod ipw3945 and modprobe ipw3945 again, then i get eth2.
Any ideas?.. |
|
| Back to top |
|
|
m@cCo
n00b
Joined: 01 Mar 2005
Posts: 9
|
| Posted: Fri May 18, 2007 6:01 pm Post subject: |
|
|
Hi all.
I've got a problem with the new gentoo-sources 2.6.21 and the ipw3945 driver. When I try to emerge it I get an error saying that the TKIP options isn't enabled in the kernel. The fact is that there's no option for TKIP in the Networking Options of the kernel!
It follows the detailed error:
| Code: | * Checking for suitable kernel configuration options...
* ipw3945-1.2.0 requires support for Wireless LAN drivers (non-hamradio) & Wireless Extensions (CONFIG_NET_RADIO).
* CONFIG_IEEE80211_CRYPT_TKIP: is not set when it should be.
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
* Once you have satisfied these options, please try merging
* this package again. |
|
|
| Back to top |
|
|
xerxesmc
n00b
Joined: 19 Nov 2006
Posts: 54
Location: Fulda/Hessen
|
| Posted: Fri May 18, 2007 7:49 pm Post subject: |
|
|
it shows up, when u activate Device Drivers -> Network Device support -> Wireless LAN drivers (non-hamradio) & Wireless Extensions
cheers |
|
| Back to top |
|
|
m@cCo
n00b
Joined: 01 Mar 2005
Posts: 9
|
| Posted: Fri May 18, 2007 8:10 pm Post subject: |
|
|
| xerxesmc wrote: | it shows up, when u activate Device Drivers -> Network Device support -> Wireless LAN drivers (non-hamradio) & Wireless Extensions
cheers |
That's it, thanks! 
That eth cable around the room wasn't that pleasant |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Sat May 19, 2007 3:27 pm Post subject: |
|
|
| broadcast wrote: | I don't get a network interface after boot. ipw3945 module is loaded, ipw3945d started.
I have to rmmod ipw3945 and modprobe ipw3945 again, then i get eth2.
Any ideas?.. |
Two questions at first:
- Do you have a separate filesystem for /var?
- Is udev loading the driver? If yes you could try to load it manually after your computer has booted. Normally you should get only eth1, no eth2. So first put blacklist ipw3945 in /etc/modules.d/blacklist (>=udev-104, I think) and modprobe the driver manually.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Thu May 24, 2007 10:07 am Post subject: |
|
|
a: No
b: Yes, udev loads the driver. I added blacklist ipw3945 to /etc/modules.d/blacklist but it loads the driver anyway  (udev-104-r12). eth1 is my regular network card (I forgot to say that). |
|
| Back to top |
|
|
boffman
n00b
Joined: 24 May 2007
Posts: 1
|
| Posted: Thu May 24, 2007 12:03 pm Post subject: |
|
|
I also had problem with this, I have a HP dv9000 laptop (centrino core 2 duo).
| Code: |
# lspci | grep Wireless
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
|
It felt totally impossible to get the wlan card working in 2.6.20 .. And when I installed 2.6.21 and also applied that patch mentioned, it wouldn't boot any longer - saying it couldn't mount /dev/sdb3 as root. But, it still worked with the 2.6.20 kernel..
Some googling indicated that this is some kind of bug coming with 2.6.21 (I recall I read that a possible fix could be switching the code in /usr/src/linux/drivers/message/fusion/ back to the .20 version?)
However, I emerged back to gentoo-sources 2.6.18-rc7 and there it worked straight off. (Or, at least it detected the card and I got my eth2 when running iwconfig.  )
I think I'll wait for some newer kernel before I try again.. |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Thu May 24, 2007 12:18 pm Post subject: |
|
|
| broadcast wrote: | | b: Yes, udev loads the driver. I added blacklist ipw3945 to /etc/modules.d/blacklist but it loads the driver anyway (udev-104-r12). eth1 is my regular network card (I forgot to say that). |
So you might want to upgrade to >=udev-110 as on my system udev blacklisting works properly.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Thu May 24, 2007 6:57 pm Post subject: |
|
|
| I upgraded to udev-111-r1. blacklist still doesn't work |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Thu May 24, 2007 10:31 pm Post subject: |
|
|
Sorry I mislead you. File blacklist should reside in /etc/modprobe.d/ . I think /etc/modules.d/ will progressively migrate to /etc/modprobe.d/ .
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Fri May 25, 2007 7:57 am Post subject: |
|
|
ok. now, udev doesn't load the driver. that's what i get:
after boot: no driver loaded, no eth2.
modprobe: | Code: | # modprobe ipw3945
* Starting ipw3945d ... [ ok ] |
still no eth2.
| Code: | # lsmod | grep ipw
ipw3945 171876 0
ieee80211 23560 1 ipw3945
firmware_class 6784 1 ipw3945 |
rmmod & modprobe again:
| Code: | # rmmod ipw3945
# modprobe ipw3945
* WARNING: ipw3945d has already been started. |
-> now, eth2 exists |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Fri May 25, 2007 9:29 am Post subject: |
|
|
@broadcast:
Ok, that seems fine to me as - IIRC - the daemon creates the interface, not the module (although I have to check that again). Anyways there's one thing I don't catch: why would you want eth2? I've got two remarks however:
- You shouldn't use rmmod to unload ipw3945 but modprobe -r as rmmod doesn't execute the remove instructions in /etc/modules.d/ipw3945d. If you use rmmod, ipw3945d will stay in memory although it should be unloaded, hence modprobe -r.
- The next time you run modprobe ipw3945 ipw3945d still runs hence the message
| Quote: | | * WARNING: ipw3945d has already been started. |
Since ipw3945d was already running and is responsible for creating the device node, you get an eth2. Still I don't know if it was the intended purpose. Anyways it all demonstrates ipw3945/udev are working properly this time.
Please make sure you have a symlink /etc/init.d/net.eth1 pointing to /etc/init.d/net.lo and setup /etc/conf.d/net as appropriate. If you modprobe ipw3945 manually the system should give you an eth1 device.
BTW: are you using wpa_supplicant or iwconfig?
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Fri May 25, 2007 1:05 pm Post subject: |
|
|
| VinzC wrote: | @broadcast:
why would you want eth2? |
As I said: eth1 is the network card. eth2 is the wireless card.
ipw3945d still doesn't create the eth2-device when it's started/or ipw3945 modprobed.
Only when it's started and I rmmod & modprobe again. That's the only way/workaround I found to get the device. |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Fri May 25, 2007 1:22 pm Post subject: |
|
|
But then what about eth0? Have you renamed interfaces?
EDIT: IIRC the default device name, which ipw3945d creates is eth1. If you want some other name, like wlan0, you should create udev rules appropriately. Don't know if it's what you did - if you did.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Fri May 25, 2007 3:24 pm Post subject: |
|
|
oh, good question...
| Code: | /etc/init.d/net.eth0 start
* Caching service dependencies ... [ ok ]
* Starting eth0
* Bringing up eth0
* dhcp
* network interface eth0 does not exist
* Please verify hardware or kernel module (driver) [ !! ]
|
| Code: | dmesg | grep eth
eth0: Tigon3 [partno(BCM95789) rev 4201 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:16:d4:1c:84:11
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
tg3: eth1: Link is up at 100 Mbps, full duplex.
tg3: eth1: Flow control is on for TX and on for RX.
|
| Code: | # lspci | grep Eth
04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5789 Gigabit Ethernet PCI Express (rev 21)
|
that should use the module "tg3"
| Code: | # cat /var/log/boot.msg | grep tg3
* Loading module tg3 ...
[ ok ]
|
/etc/conf.d/net
| Code: | # lan
config_eth0=( "dhcp" )
dhcpcd_eth0="-t 5"
# wlan
modules_eth1=( "wpa_supplicant" )
wpa_supplicant_eth1="-Dwext"
config_eth1=( "dhcp" )
dhcp_eth1="nontp nonis" |
confusing |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Sun May 27, 2007 10:31 am Post subject: |
|
|
Well, from all I see here, it looks like tg3 creates *two* interfaces, eth0 and eth1... Maybe tg3 is not the right driver? or could it be that you have it loaded by UDEV and by /etc/modules.autoload.d/kernel-2.6?...
What happens if you load tg3 manually? Basically the test procedure is to load modules and start net scripts manually then see what happens in the logs. Start with the wired Ethernet then the wireless adapter.
EDIT: I'm almost convinced your eth0 is renamed somewhere between
| Quote: | | eth0: dma_rwctrl[76180000] dma_mask[64-bit] |
and
| Quote: | | tg3: eth1: Link is up at 100 Mbps, full duplex. |
Search /etc/udev/rules.d/* for eth1...
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
mikkoc
Apprentice
Joined: 24 May 2007
Posts: 231
|
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Sun May 27, 2007 2:11 pm Post subject: |
|
|
| VinzC wrote: | | Search /etc/udev/rules.d/* for eth1... |
you were right!
| Code: | # PCI device 0x8086:0x4222 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:13:02:90:26:53", NAME="eth2"
# PCI device 0x14e4:0x169d (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:16:d4:1c:84:11", NAME="eth1"
# Firewire device 00023f688b407201)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:02:3f:68:8b:40:72:01", NAME="eth0"
|
I never touched this file.
now:
| Code: | # PCI device 0x8086:0x4222 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:13:02:90:26:53", NAME="eth1"
# PCI device 0x14e4:0x169d (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:16:d4:1c:84:11", NAME="eth0"
# Firewire device 00023f688b407201)
# SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:02:3f:68:8b:40:72:01", NAME="eth0" |
And I just read this in /etc/modprobe.d/blacklist:
| Quote: | # Autoloading eth1394 most of the time re-orders your network
# interfaces, and with buggy kernel 2.6.21, udev persistent-net
# is not able to rename these devices, so you get eth?_rename devices
# plus an exceeded 30sec boot timeout
blacklist eth1394 |
Udev messed up the network-devices?
Anyway:
network card -> eth0.
ipw3945 blacklisted.
modprobe ipw3945 -> no eth1-device
modprobe -r ipw3945; modprobe ipw3945 -> no eth1-device
rmmod ipw3945; modprobe ipw3945 -> eth1 exists
 |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Sun May 27, 2007 3:11 pm Post subject: |
|
|
@broadcast:
This is probably the content of /etc/udev/rules.d/70-persistent-net.rules. On my system too there is such a file which contains the MAC addresses of both my RealTek adapters - it forces 8139too otherwise 8139cp gets loaded. I think that file is created when you install UDEV. Now you should just leave the file as is (in its original state) but comment out each active line in that file.
To see what network devices you have, take a look at /sys/class/net/*. There you should have every one of your network adapters listed, for which there is a driver loaded. Listed interfaces are not necessarily active. Here's an example:
| ls -l /sys/class/net/: | drwxr-xr-x 3 root root 0 mai 26 09:15 eth0
drwxr-xr-x 3 root root 0 mai 26 09:15 eth1
drwxr-xr-x 3 root root 0 mai 26 09:15 lo
drwxr-xr-x 3 root root 0 mai 26 09:15 tun0
drwxr-xr-x 3 root root 0 mai 26 09:15 tunl0 |
First, as I said, load the driver of your Ethernet card. Take a look at dmesg to check what device was created (confirm with the above listing) and start the corresponding script. Repeat with your wireless card.
EDIT: Also make sure the daemon ipw3945d is running (after loading the module) with ps -fC ipw3945d. Wait 2-3 seconds before issuing the ps command. If it is then you should have a /sys/class/net/eth1 and a subdirectory called wireless/.
To be sure your Ethernet card is always eth0, you can compile the driver into the kernel and leave any other one as a module - udev always starts afterwards.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
broadcast
n00b
Joined: 16 May 2006
Posts: 27
|
| Posted: Sun Jun 17, 2007 12:14 pm Post subject: |
|
|
| Code: | # ls -l /sys/class/net/
total 0
drwxr-xr-x 4 root root 0 2007-06-17 14:11 eth0
drwxr-xr-x 4 root root 0 2007-06-17 13:37 lo
drwxr-xr-x 4 root root 0 2007-06-17 13:37 tunl0
|
| Code: | # ps -fC ipw3945d
UID PID PPID C STIME TTY TIME CMD
root 7916 1 0 14:09 pts/1 00:00:00 /sbin/ipw3945d --pid-file=/var/run/ipw3945d/ipw3945d.pid --timeout=-1 --quiet
|
then I activate the wireless-card.
| Code: | # ls -l /sys/class/net/
total 0
drwxr-xr-x 4 root root 0 2007-06-17 14:11 eth0
drwxr-xr-x 4 root root 0 2007-06-17 13:37 lo
drwxr-xr-x 4 root root 0 2007-06-17 13:37 tunl0
|
no device
just for fun:
| Code: | # rmmod ipw3945
# modprobe ipw3945
* WARNING: ipw3945d has already been started.
# ls -l /sys/class/net/
total 0
drwxr-xr-x 4 root root 0 2007-06-17 14:11 eth0
drwxr-xr-x 5 root root 0 2007-06-17 14:18 eth1
drwxr-xr-x 4 root root 0 2007-06-17 13:37 lo
drwxr-xr-x 4 root root 0 2007-06-17 13:37 tunl0 |
|
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Sun Jun 17, 2007 1:56 pm Post subject: |
|
|
@broadcast:
Ok, let's make it the hard way then .
I. After booting your computer make sure a) ipw3945d is *not* running (run ps -fC ipw3945d) and b) ipw3945 is *not* loaded (run lsmod | grep ipw3945). If the module is loaded, unload it (you *must* use modprobe -r instead of rmmod) and redo the above tests. If the daemon is running, run ipw3945d --kill. You will now have a clean startup point.
II. Now load ipw3945 module and see what happens:- run lsmod | grep ipw3945
- run ps -fC ipw3945d
- run dmesg | grep 3945
- run find /sys/class/net/ -name wireless
EDIT: Wireless interfaces have a sub-directory wireless under /sys/class/net/eth?/. Post the results here.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
Phk
Guru
Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time
|
| Posted: Thu Jun 28, 2007 5:40 pm Post subject: |
|
|
(sorry to disturb this 30-page post, but i'm having a few problems with the iwlwifi driver. Now, i believe i loved ipw3945.. it worked sooo well... Can i use it on the new 2.6.22 kernel? Please PM-me or post here the patch link... if there is thanks!)
_________________
"# cat /dev/urandom >> /tmp/life" |
|
| Back to top |
|
|
|
Kernel & Hardware
