Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Kernel & Hardware
  • Search

ipw3945 alternative: Intel's iwlwifi

Kernel not recognizing your hardware? Problems with power management or PCMCIA? What hardware is compatible with Gentoo? See here. (Only for kernels supported by Gentoo.)
Post Reply
Advanced search
373 posts
  • Page 14 of 15
    • Jump to page:
  • Previous
  • 1
  • …
  • 11
  • 12
  • 13
  • 14
  • 15
  • Next
Author
Message
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Thu Jul 24, 2008 11:28 am

gforum wrote:is it because i left mac801 or whatnot built-in, instead of as a module?
Plz read this thread : http://forums.gentoo.org/viewtopic-t-69 ... l3945.html
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Thu Jul 24, 2008 11:30 am

gforum wrote:i tried the given ideas, and it said 'operation not supported', also only now i realize that when i do lspci, it says unknown device, on the network device part that should say intel 4965 or whatnot....
For you unknown hardware, you need to run this :

Code: Select all

# update-pciids 
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Thu Jul 24, 2008 1:49 pm

i did what you said, fixed the kernel, loaded all 3 mods(iwl4965,mac80211,cfg80211) and! ...

well i get the result, ERROR interface wlan0 does not exist, or something like that... when wlan0 does exist.

also, i checked /etc/udev/rules.d/70-persistent-net.rules and it shows my wifi(iwl4965) and the interface as wlan0, so at least its not bogus.
though when i do ifconfig -a
i got eth0, lo, and a weird sit0, no idea what the bleep that is but...
and iwconfig shows, the above 3 and says no wireless extensions, etc... you know.

is this a /net config issue? a wpa one? i thought they where ok, i set them like you showed. :? lost here.

edit:also my wifi led was on, and now its not anymore... so maybe it really doesnt exist, even though if you go to /etc/init.d/ you'll find net.wlan0 there... :lol:
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Thu Jul 24, 2008 2:05 pm

Ok, can you post this :

Code: Select all

# cd /etc/init.d
# ls -la
Also, can you post the result of theses command plz :

Code: Select all

# rmmod iwl4965
# modprobe iwl4965
# dmesg | tail
# ifconfig -a
# iwconfig
I need to see these results to help you :P
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Thu Jul 24, 2008 6:04 pm

i coudnt copy/paste since i dont have x installed yet(no wifi), and i dont think chrooting would give accurate info.(am i wrong?)

but i think that the info you want is,
eht0>net.lo
wlan0>net.lo
iwconfig returns simply no wireless extensions for sit0, eth0 and lo.
ifconfig returns that eth0 is doing great, lo is what it is and that sit0 is ipv6-in-ipv4 or whatnot, no wmaster0 exists btw... shouldn't this be automatically created?

and finally dmesg reports the problem i think, it gives me some error, like error -12 or whatnot when trying to load the driver iwl4965 it says its a algorithm problem.

after all, this started after i set :
Code:

(*) Cryptographic algorithm manager
(M) SHA1 digest algorithm
(M) SHA256 digest algorithm
(M) ECB support
(M) CBC support
(M) PCBC support
(*) AES cipher algorithms
(*) AES cipher algorithms (i586)
(*) ARC4 cipher algorithm
(*) Michael MIC keyed digest algorithm

in the kernel, like it said in the post you linked...

the mod is working fine, loads and unloads...

if this info inst sufficient maybe you know how i cant copy-paste without X.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Thu Jul 24, 2008 7:26 pm

Hi, when you run ifconfig -a or iwconfig, do you see the interface wlan0 and wmaster0.

If not, you have a kernel problem.
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Thu Jul 24, 2008 7:28 pm

then i got a kernel problem... but i just copied what the post you gave me said. which basically was, put nearly everything into M and some into *.

is that post valid for kernel 2.6.26?
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Fri Jul 25, 2008 11:40 am

Yes, but your need to enable the generic RFKillSwitch and the RFKillSwitch for the specific Iwl3945 driver.

I didn't test the kernel 2.6.26, but I know the man responsable of the Iwl3945 Intel projet and he told me that yesterday.

For the record, did you had IPW3945 driver before ?
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Fri Jul 25, 2008 11:50 am

The config that I posted is for the kernel 2.6.24 or 2.6.25.
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Fri Jul 25, 2008 2:38 pm

(*) Cryptographic algorithm manager
(M) SHA1 digest algorithm
(M) SHA256 digest algorithm
(M) ECB support
(M) CBC support
(M) PCBC support
(*) AES cipher algorithms
(*) AES cipher algorithms (i586)
(*) ARC4 cipher algorithm
(*) Michael MIC keyed digest algorithm

dont recommend this to people...

basically i removed this and set it back to built in, and now everything is working fine.
thanks for the parts that helped D2!
(like wpa assistance). :)
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Sat Jul 26, 2008 2:30 pm

No problem.
Top
kienjakenobi
n00b
n00b
User avatar
Posts: 28
Joined: Tue Dec 25, 2007 8:51 pm

  • Quote

Post by kienjakenobi » Sun Jul 27, 2008 3:31 am

I just thought I might add that I am using the iwlwifi driver that is built into Gentoo-sources 2.6.25-r7 with my Intel 4965ABGN card on AMD64 with great success. I have been able to download things over my wireless connection at the same rates that I can when I am hard wired to the same connection. The connection automatically starts on boot with WPA encryption (Using wpa_supplicant) and I have not noticed it drop the connection once during my usage of Gentoo, despite an idle system for hours at a time.
Avatar: Background = Adobe stock photo Tux = Vector by Anja Gerwinski (http://ngc224.gerwinski.de/~anja/gnuart/penguin/)
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Sun Jul 27, 2008 4:18 am

did you set the mac80211 and cfg80211 as mods or as built-in?
or in general, what things did you leave as mod(regarding wifi ofcourse).
Top
breakerfall
Guru
Guru
Posts: 509
Joined: Sat Aug 02, 2003 11:13 pm
Location: Manchester, UK

  • Quote

Post by breakerfall » Sun Jul 27, 2008 12:36 pm

Hi, I'm having some trouble configuring my wifi...

I'm using the kernel driver, iwl3945 compiled as a module.

I'm running vanilla-sources 2.6.25.8

Output from ifconfig -a

Code: Select all

eth1      Link encap:Ethernet  HWaddr 00:13:A9:49:C0:45  
          inet addr:192.168.1.104  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:166 errors:0 dropped:0 overruns:0 frame:0
          TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:139894 (136.6 Kb)  TX bytes:26107 (25.4 Kb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:18:DE:77:91:FD  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wmaster0  Link encap:UNSPEC  HWaddr 00-18-DE-77-91-FD-60-57-00-00-00-00-00-00-00-00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
(Not sure why I have eth1 instead of eth0...)

The module loads just fine, however, when trying to manually start net.wlan0, this is the output:

Code: Select all

/etc/init.d/net.wlan0 start
 * Starting wlan0
SIOCSIFFLAGS: No such device
SIOCSIFFLAGS: No such device
 *   Wireless radio has been killed for interface wlan0
 *   wpa_supplicant will launch, but not associate until
 *   wireles radio is re-enabled for interface wlan0
 *   Starting wpa_supplicant on wlan0 ...
SIOCSIFFLAGS: No such device
SIOCSIFFLAGS: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCSIWAUTH]: Operation not supported                                                           [ ok ]th param 4 value 0x0 - 
 *   Starting wpa_cli on wlan0 ...                                                             [ ok ]
 *     Backgrounding ...

Code: Select all

cat /etc/conf.d/net
config_eth1=("dhcp")
dhcpcd_eth1="-t 10" # 10 second timeout
dhcp_eth1="release nodns nontp nonis"

modules=("wpa_supplicant")
config_wlan0=("dhcp")

Code: Select all

cat /etc/wpa_supplicant/wpa_supplicant.conf 
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
network={
	key_mgmt=NONE
	priority=-9999999
}

network={
	ssid="xxxx"
	psk="xxxxxxxxx"
	proto=WPA2
	key_mgmt=WPA-PSK
	pairwise=CCMP
	group=CCMP
	priority=5
}
I'm have WPA2 "mixed" setup on the router.

Where am I going wrong? Is there a step-by-step guide to getting wifi on gentoo? Something that takes you from installing the kernel drivers, right the way through to configuring your setup to connect to different AP protocols (such as WPA2), all in one location?

Thanks
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Sun Jul 27, 2008 7:59 pm

Hi, can you try that :

Code: Select all

# rmmod iwl3945
# modprobe iwl3945
# dmesg | tail
* Wireless radio has been killed for interface wlan0
* wpa_supplicant will launch, but not associate until
* wireles radio is re-enabled for interface wlan0
Are you sure that your switch is on physically on your laptop ?

Double check your switch on the side or the front of your laptop.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Sun Jul 27, 2008 8:38 pm

Are you sure that your wlan0 interface was up ?

Code: Select all

# ifconfig wlan0 up
# ifconfig -a
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Sun Jul 27, 2008 11:34 pm

there is no central resource that i know of... but you will find some, at least half-baked ones, in the gentoo wiki.

maybe you need to add:

Code: Select all

modules="wpa_supplicant"
wpa_supplicant_wlan0="-Dwext"
in the /etc/conf.d/net file... least to say of course.

also, i think that:
config_wlan0=("dhcp")
and, config_eth1=("dhcp")
are unnecessary since dhcp is standard ops.

and finally, read around the main wpa_supp. site and files, to see if the config you have matches what you need for your network. if you scroll a few posts back you'll see what i have, for instance. (just as an example -i use wep atm)
oh, and i would also, update my kernel. 2.6.26 is great. i love having my leds fully operational.

hope that helps. :wink:
Top
breakerfall
Guru
Guru
Posts: 509
Joined: Sat Aug 02, 2003 11:13 pm
Location: Manchester, UK

  • Quote

Post by breakerfall » Mon Jul 28, 2008 10:11 pm

d2_racing wrote:Hi, can you try that :

Code: Select all

# rmmod iwl3945
# modprobe iwl3945
# dmesg | tail
* Wireless radio has been killed for interface wlan0
* wpa_supplicant will launch, but not associate until
* wireles radio is re-enabled for interface wlan0
Are you sure that your switch is on physically on your laptop ?

Double check your switch on the side or the front of your laptop.
The switch is definitely on. I can find other networks (my own doesn't broadcast the ssid), but I can't connect. I've run the same commands you've asked me to run here already, but here are the results:

Code: Select all

 dmesg | tail
PM: Writing back config space on device 0000:06:00.0 at offset 1 (was 100002, writing 100006)
ACPI: PCI interrupt for device 0000:06:00.0 disabled
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23ks
iwl3945: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:06:00.0 to 64
iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
phy1: Selected rate control algorithm 'iwl-3945-rs'
ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 18 (level, low) -> IRQ 18
Running /etc/init.d/net.wlan0 after this returns the same thing it did previously:

Code: Select all

/etc/init.d/net.wlan0 status
 * Caching service dependencies ...                                            [ ok ]
 * status:  inactive
mini ~ # /etc/init.d/net.wlan0 restart
 * Stopping wlan0
 *   Bringing down wlan0
 *     Shutting down wlan0 ...                                                 [ ok ]
 *     Stopping wpa_cli on wlan0 ...                                           [ ok ]
 *     Stopping wpa_supplicant on wlan0 ...                                    [ ok ]
 * Starting wlan0
 *   Starting wpa_supplicant on wlan0 ...
ioctl[SIOCSIWAUTH]: Operation not supported                                           [ ok ]th param 4 value 0x0 - 
 *   Starting wpa_cli on wlan0 ...                                             [ ok ]
 *     Backgrounding ...
Any other ideas?

Thanks!


PS

gforum, thanks for the information. I set dhcp manually so as to avoid the messages during bootup that state no config is defined, defaulting to dhcp. It would be great to have a central repository of wireless information for each card / chipset, from installing the drivers, right upto configuring the card with wpa_supplicant fully.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Tue Jul 29, 2008 1:41 am

hi, can you post this plz :

Code: Select all

# cat /etc/udev/rules.d/70-persistent-net.rules
Top
breakerfall
Guru
Guru
Posts: 509
Joined: Sat Aug 02, 2003 11:13 pm
Location: Manchester, UK

  • Quote

Post by breakerfall » Tue Jul 29, 2008 6:03 pm

d2_racing wrote:hi, can you post this plz :

Code: Select all

# cat /etc/udev/rules.d/70-persistent-net.rules
Here's the output:

Code: Select all

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:50:8d:b2:4e:4f", NAME="eth0"

# PCI device 0x8086:0x1092 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:a9:49:c0:45", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:de:77:91:fd", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
Just to be certain I haven't done anything wrong along the way, this is the process so far:

Fully working system.
Alter kernel to include relevent wifi drivers (compiled in).
The iwl3945 driver is compiled as a module.

I have installed wpa_supplicant (and later on, I installed wireless-tools).

I have the following in /etc/conf.d/net

Code: Select all

config_eth1=("dhcp")
dhcpcd_eth1="-t 10" # 10 second timeout
dhcp_eth1="release nodns nontp nonis"

modules=("wpa_supplicant")
config_wlan0=("dhcp")
wpa_supplicant_wlan0="-Dwext"
I have the following in /etc/wpa_supplicant/wpa_supplicant.conf

Code: Select all

network={
	key_mgmt=NONE
	priority=-9999999
}

network={
	ssid="xxx"
	psk="xxx"
	proto=WPA2
	key_mgmt=WPA-PSK
	pairwise=CCMP
	group=CCMP
	priority=5
}
During bootup, when wlan0 starts during boot I get the ioctl[SIOCSIWAUTH]: Operation not permitted warning.

ifconfig -a shows

Code: Select all

eth1      Link encap:Ethernet  HWaddr 00:13:A9:49:C0:45  
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:205 errors:0 dropped:0 overruns:0 frame:0
          TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:19473 (19.0 Kb)  TX bytes:20428 (19.9 Kb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:18:DE:77:91:FD  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wmaster0  Link encap:UNSPEC  HWaddr 00-18-DE-77-91-FD-70-E0-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
Output of iwconfig

Code: Select all

lo        no wireless extensions.

eth1      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:""  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


Do you see anywhere that I could be going wrong? Am I missing any configuration?

Thanks
Top
jeanfrancis
Veteran
Veteran
User avatar
Posts: 1482
Joined: Sat Dec 17, 2005 3:22 pm
Location: Québec, Canada

  • Quote

Post by jeanfrancis » Wed Jul 30, 2008 1:36 am

Hi there ! Well, your wireless driver seems to be working. I also get this ioctl warning and my network works anyway...

Can you manage to connect to any WEP access point ? Try to set up your AP in WEP temporarilly and try to connect to it :) You can use wpa_gui, scan and double-click on your AP (broadcast your ssid :)), then set the key_tx0, just for this little test :)

Post the results here.

If it don't works, post the output of dmesg | tail after.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Wed Jul 30, 2008 2:33 am

Also, are you using KDE ? If so, can you install wlassistant and check if you can connect to your router with this little program.
Top
gforum
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 140
Joined: Mon Mar 31, 2008 8:13 am

  • Quote

Post by gforum » Wed Jul 30, 2008 6:22 am

breakerfall wrote:
d2_racing wrote:hi, can you post this plz :

Code: Select all

# cat /etc/udev/rules.d/70-persistent-net.rules
Here's the output:

Code: Select all

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:50:8d:b2:4e:4f", NAME="eth0"

# PCI device 0x8086:0x1092 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:a9:49:c0:45", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:de:77:91:fd", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
Just to be certain I haven't done anything wrong along the way, this is the process so far:

Fully working system.
Alter kernel to include relevent wifi drivers (compiled in).

stop right there...

you need mac80211 and cfg80211 compiled as a MODULE, that should fix it for you.
(read the description of the wifi 'stuffs' to find what is the mac and the cfg, you prob already got them enabled, but as built-in. somehow they dont like being built-in...)

cheers. :wink:
Top
VinzC
Watchman
Watchman
User avatar
Posts: 5100
Joined: Sat Apr 17, 2004 1:51 pm
Location: Dark side of the mood

  • Quote

Post by VinzC » Wed Jul 30, 2008 7:29 am

breakerfall wrote:(Not sure why I have eth1 instead of eth0...)

Code: Select all

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:50:8d:b2:4e:4f", NAME="eth0"

# PCI device 0x8086:0x1092 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:a9:49:c0:45", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:de:77:91:fd", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
For the record the driver for your eth0 is that of an nVidia nForce. Do you have one on your computer?

BTW 70-persistent-net.rules is a file that is created automatically and maintained by UDEV. It holds the names of devices found on your system. So if you want to change the name of a device (say, an ethernet device) that's the right place :) .

If you want your Intel Ethernet (e100) to be eth0 then you can safely delete the lines that say

Code: Select all

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:50:8d:b2:4e:4f", NAME="eth0"
and replace eth1 with eth0. Next time you reboot UDEV will append a line like the one you removed but with the nForce as eth1 this time. You'll also have to replace eth1 with eth0 in your network configuration file:

Code: Select all

config_eth1=("dhcp")
dhcpcd_eth0="-t 10" # 10 second timeout
dhcp_eth0="release nodns nontp nonis"
...
breakerfall wrote:During bootup, when wlan0 starts during boot I get the ioctl[SIOCSIWAUTH]: Operation not permitted warning.
That is perfectly «normal» (in fact I have that too and it doesn't prevent association). The reason why your wireless card doesn't seem to associate is that an encryption driver probably lacks from your kernel configuration. See [post=5162369]gforum's post[/post] as to what drivers to include.
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Top
breakerfall
Guru
Guru
Posts: 509
Joined: Sat Aug 02, 2003 11:13 pm
Location: Manchester, UK

  • Quote

Post by breakerfall » Wed Jul 30, 2008 6:29 pm

gforum wrote: stop right there...

you need mac80211 and cfg80211 compiled as a MODULE, that should fix it for you.
(read the description of the wifi 'stuffs' to find what is the mac and the cfg, you prob already got them enabled, but as built-in. somehow they dont like being built-in...)

cheers. :wink:
Ah, I'll try compiling them as modules too.

VinzC, thanks for the info - when I pasted the contents of that file (on request), I realised where I could change it.

The laptop doesn't have an nforce ethernet card, but my desktop does. I just recently (a few days ago) did a "stage 4" backup, tarring my root directory, bar a few that I wanted to exclude, then untarring that into a freshly formatted drive on my laptop.

It's a nice quick and easy way to get my desktop install, with configs I'm happy with and all my fave apps, over to my laptop with no compilation. :)

d2_racing, I'm not using KDE.


I'll post back with the results after I compile the stack as a module... thanks again.
Top
Post Reply

373 posts
  • Page 14 of 15
    • Jump to page:
  • Previous
  • 1
  • …
  • 11
  • 12
  • 13
  • 14
  • 15
  • Next

Return to “Kernel & Hardware”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic