Setting up Wireless 3945ABG [Golan] [8086:4227]
Forum rules
We don't support installations in VirtualBox, VMWare, qemu or others. We ignore posts about WINE, PlayOnLinux, Steam and Skype. We don't support btrfs, lvm, UEFI, side-by-side installations with GPT or dualboot with anything newer than Windows XP.
Google your problem first. Check the Wiki. Read the existing threads. It's okay to "hijack" an existing thread, yes! If your problem is not yet covered, open a new thread. To get the quickest possible help, mention the exact release codename in your post (uname -a is a good idea, too). Due to the lack of crystal balls, attach the output of lspci -nnk if you encounter hardware problems.
We don't support installations in VirtualBox, VMWare, qemu or others. We ignore posts about WINE, PlayOnLinux, Steam and Skype. We don't support btrfs, lvm, UEFI, side-by-side installations with GPT or dualboot with anything newer than Windows XP.
Google your problem first. Check the Wiki. Read the existing threads. It's okay to "hijack" an existing thread, yes! If your problem is not yet covered, open a new thread. To get the quickest possible help, mention the exact release codename in your post (uname -a is a good idea, too). Due to the lack of crystal balls, attach the output of lspci -nnk if you encounter hardware problems.
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Setting up Wireless 3945ABG [Golan] [8086:4227]
I tried this. rfkill unblock all seemed to work. But on running "echo "blacklist hp_wmi" > /etc/modprobe.d/hp.conf" I got access denied
output on lspci | grep Net
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
03:00.0 Network control
I assume it is the problem above as the wifi on !# works out of the box on my t61
output on lspci | grep Net
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
03:00.0 Network control
I assume it is the problem above as the wifi on !# works out of the box on my t61
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
- ivanovnegro
- Minister of Truth
- Posts: 5449
- Joined: Wed Oct 17, 2012 11:12 pm
Re: Kernel 3.10 and Wifi madness (iwlwifi)
Access denied, did you run the commands as root and which kernel are you using? Plain Sid is already on 3.11 as should be the BBQ.
Of course, the drivers could be also different.
Of course, the drivers could be also different.
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Kernel 3.10 and Wifi madness (iwlwifi)
Ivan is right, simply enter:
then enter your password, and then echo the command again. Leave the sudo session with
If you just put a sude before the echo, it makes the 'echo' run as root but not the pipe, IIRC.
Code: Select all
sudo -i
Code: Select all
exit
..gnutella..
Re: Kernel 3.10 and Wifi madness (iwlwifi)
^ wow, did not know that about the 'sudo' with pipes...
little point too: please use code-boxes when posting code-shit. look at bacon's example. makes shit way easier to read :)
little point too: please use code-boxes when posting code-shit. look at bacon's example. makes shit way easier to read :)
All statements are true in some sense, false in some sense, meaningless in some sense, true and false in some sense, true and meaningless in some sense, false and meaningless in some sense, and true and false and meaningless in some sense.
- ivanovnegro
- Minister of Truth
- Posts: 5449
- Joined: Wed Oct 17, 2012 11:12 pm
Re: Kernel 3.10 and Wifi madness (iwlwifi)
^^ Yep, correct or use your root account with su.
Re: Kernel 3.10 and Wifi madness (iwlwifi)
Or
Use the -a option to tee if you want to append.
Code: Select all
echo "blacklist hp_wmi" | sudo tee /etc/modprobe.d/hp.conf
Connected. Take this REPL, brother, and may it serve you well.
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Kernel 3.10 and Wifi madness (iwlwifi)
That sorted me out running the code, but nothing happened with getting wifi. On #! it worked out of the box. Anybody who have any sugetstions of why it is different on darkside?
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
- ivanovnegro
- Minister of Truth
- Posts: 5449
- Joined: Wed Oct 17, 2012 11:12 pm
Re: Kernel 3.10 and Wifi madness (iwlwifi)
^ I blame the kernel, so you cannot compare it to #!. What is the kernel driver exactly:
Edit: Did you reboot?
After a reboot check this with sudo or root:
Code: Select all
lspci -knn
After a reboot check this with sudo or root:
Code: Select all
rfkill list
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Kernel 3.10 and Wifi madness (iwlwifi)
On the first command I get a wall of text. What exactly am I looking for, maybe this?
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
Output on second command is
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
Output on second command is
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Kernel 3.10 and Wifi madness (iwlwifi)
sorry after the reboot the rfkill list gives this output
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I dont know if the change in order makes any difference
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I dont know if the change in order makes any difference
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
- wuxmedia
- Grasshopper
- Posts: 6454
- Joined: Wed Oct 17, 2012 11:32 am
- Location: Back in Blighty
- Contact:
Re: Kernel 3.10 and Wifi madness (iwlwifi)
'Ethernet controller' != wifi.
look for one that says wifi. or wireless mine reads 'network controller'
it should be listed, the -knn bit shows which driver has been loaded, if any.
try
looks like you cut/missed some text from you first lspci post
all no's means nothing is blocked. which is good.
but doesn't solve your prob.
BTW;
Use code tags means wrap them in special BBCode, try the 'full editor' next to submit, or type [ code ]Code goes here [ /code] (without the spaces in the square brackets)
the 3.11 kernel ignores my laptops ethernet, for some unknown reason. (modprobe b44 sorts it)
look for one that says wifi. or wireless mine reads 'network controller'
it should be listed, the -knn bit shows which driver has been loaded, if any.
try
Code: Select all
lspci -knn | grep Net
all no's means nothing is blocked. which is good.
but doesn't solve your prob.
BTW;
Use code tags means wrap them in special BBCode, try the 'full editor' next to submit, or type [ code ]Code goes here [ /code] (without the spaces in the square brackets)
the 3.11 kernel ignores my laptops ethernet, for some unknown reason. (modprobe b44 sorts it)
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Kernel 3.10 and Wifi madness (iwlwifi)
Ok, thanks. found this
Code: Select all
Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4227] (rev 02)
Subsystem: Intel Corporation ThinkPad R60e/X60s [8086:1011]
Kernel driver in use: iwl3945
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Kernel 3.10 and Wifi madness (iwlwifi)
Follow this, especially step 3
https://wiki.debian.org/iwlegacy
How I found it: google for "8086:4227 debian"
https://wiki.debian.org/iwlegacy
How I found it: google for "8086:4227 debian"
..gnutella..
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Kernel 3.10 and Wifi madness (iwlwifi)
I checked that the package was install and then I ran
I also restarted the box, but no effect. Am I missing something?
Code: Select all
# modprobe -r iwl3945 iwl4965
# modprobe iwl3945 ; modprobe iwl4965
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
Re: Kernel 3.10 and Wifi madness (iwlwifi)
Post output of
Code: Select all
dmesg | grep -Ei 'net|wlan|firmw|wpa|dhc'
Connected. Take this REPL, brother, and may it serve you well.
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Kernel 3.10 and Wifi madness (iwlwifi)
apt-getter here it is;
Code: Select all
[ 0.007678] Initializing cgroup subsys net_cls
[ 0.053213] NET: Registered protocol family 16
[ 0.067841] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query honored via DMI
[ 0.095367] pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.104749] pci 0000:15:00.0: MMC cards are now supported by standard SDHCI controller
[ 0.117260] NetLabel: Initializing
[ 0.117262] NetLabel: domain hash size = 128
[ 0.117264] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.117276] NetLabel: unlabeled traffic allowed by default
[ 0.133125] NET: Registered protocol family 2
[ 0.141207] NET: Registered protocol family 1
[ 0.475820] audit: initializing netlink socket (disabled)
[ 0.562623] NET: Registered protocol family 10
[ 0.799640] e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
[ 0.878513] sdhci: Secure Digital Host Controller Interface driver
[ 0.878517] sdhci: Copyright(c) Pierre Ossman
[ 0.931116] sdhci-pci 0000:15:00.2: SDHCI controller found [1180:0822] (rev 21)
[ 0.932274] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
[ 0.932283] sdhci-pci 0000:15:00.2: setting latency timer to 64
[ 0.933316] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
[ 0.958032] mmc0: SDHCI controller on PCI [0000:15:00.2] using DMA
[ 0.981078] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 0.993085] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
[ 1.050293] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
[ 1.107280] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
[ 1.114115] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.164291] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
[ 9.558153] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 9.909591] NET: Registered protocol family 31
[ 10.279061] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
[ 15.847408] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 15.913040] NET: Registered protocol family 17
[ 16.834739] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 17.347098] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 30.596479] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 33.518705] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
[ 33.586622] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
-
- Baconator
- Posts: 10253
- Joined: Thu Sep 16, 2010 11:03 am
- Location: Pfälzerwald
- Contact:
Re: Setting up Wireless 3945ABG [Golan] [8086:4227]
/moved support-relevant posts from HOWTO to here.
..gnutella..
Re: Setting up Wireless 3945ABG [Golan] [8086:4227]
Insufficient info...
Run the command
And post the output please.
Run the command
Code: Select all
sudo cat /var/log/syslog | grep -Ei 'net|wlan|firmw|wpa|dhc'
Connected. Take this REPL, brother, and may it serve you well.
-
- Riesenpenis
- Posts: 34
- Joined: Tue Oct 22, 2013 5:54 pm
- Location: In the boiler room
Re: Setting up Wireless 3945ABG [Golan] [8086:4227]
Here it is,
Code: Select all
Oct 26 07:22:32 lightside dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Oct 26 07:22:32 lightside dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct 26 07:22:32 lightside dhclient: DHCPOFFER from 10.43.57.1
Oct 26 07:22:33 lightside dhclient: DHCPACK from 10.43.57.1
Oct 26 07:22:33 lightside dhclient: bound to 10.43.57.251 -- renewal in 1630 seconds.
Oct 26 07:45:02 lightside dhclient: DHCPREQUEST on eth0 to 80.71.128.19 port 67
Oct 26 07:45:02 lightside dhclient: DHCPACK from 80.71.128.19
Oct 26 07:45:02 lightside dhclient: bound to 10.43.57.254 -- renewal in 1740 seconds.
Oct 26 07:45:02 lightside NetworkManager[942]: <info> (eth0): DHCPv4 state changed bound -> renew
Oct 26 07:45:02 lightside NetworkManager[942]: <info> address 10.43.57.254
Oct 26 07:45:02 lightside NetworkManager[942]: <info> prefix 24 (255.255.255.0)
Oct 26 07:45:02 lightside NetworkManager[942]: <info> gateway 10.43.57.1
Oct 26 07:45:02 lightside NetworkManager[942]: <info> nameserver '80.71.128.11'
Oct 26 07:45:02 lightside NetworkManager[942]: <info> nameserver '80.71.128.27'
Oct 26 07:45:02 lightside NetworkManager[942]: <info> domain name 'parknet.dk'
Oct 26 07:49:43 lightside dhclient: DHCPREQUEST on eth0 to 80.71.128.19 port 67
Oct 26 07:49:43 lightside dhclient: DHCPACK from 80.71.128.19
Oct 26 07:49:43 lightside dhclient: bound to 10.43.57.251 -- renewal in 1455 seconds.
Oct 26 08:15:01 lightside kernel: [ 0.007291] Initializing cgroup subsys net_cls
Oct 26 08:15:01 lightside kernel: [ 0.052211] NET: Registered protocol family 16
Oct 26 08:15:01 lightside kernel: [ 0.067083] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query honored via DMI
Oct 26 08:15:01 lightside kernel: [ 0.094095] pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
Oct 26 08:15:01 lightside kernel: [ 0.103731] pci 0000:15:00.0: MMC cards are now supported by standard SDHCI controller
Oct 26 08:15:01 lightside kernel: [ 0.116243] NetLabel: Initializing
Oct 26 08:15:01 lightside kernel: [ 0.116246] NetLabel: domain hash size = 128
Oct 26 08:15:01 lightside kernel: [ 0.116248] NetLabel: protocols = UNLABELED CIPSOv4
Oct 26 08:15:01 lightside kernel: [ 0.116261] NetLabel: unlabeled traffic allowed by default
Oct 26 08:15:01 lightside kernel: [ 0.132027] NET: Registered protocol family 2
Oct 26 08:15:01 lightside kernel: [ 0.140104] NET: Registered protocol family 1
Oct 26 08:15:01 lightside kernel: [ 0.474493] audit: initializing netlink socket (disabled)
Oct 26 08:15:01 lightside kernel: [ 0.561568] NET: Registered protocol family 10
Oct 26 08:15:01 lightside kernel: [ 0.804494] e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
Oct 26 08:15:01 lightside kernel: [ 0.861378] sdhci: Secure Digital Host Controller Interface driver
Oct 26 08:15:01 lightside kernel: [ 0.861381] sdhci: Copyright(c) Pierre Ossman
Oct 26 08:15:01 lightside kernel: [ 0.915129] sdhci-pci 0000:15:00.2: SDHCI controller found [1180:0822] (rev 21)
Oct 26 08:15:01 lightside kernel: [ 0.916180] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 26 08:15:01 lightside kernel: [ 0.916188] sdhci-pci 0000:15:00.2: setting latency timer to 64
Oct 26 08:15:01 lightside kernel: [ 0.917219] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 26 08:15:01 lightside kernel: [ 0.939030] mmc0: SDHCI controller on PCI [0000:15:00.2] using DMA
Oct 26 08:15:01 lightside kernel: [ 0.948982] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
Oct 26 08:15:01 lightside kernel: [ 0.972669] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 26 08:15:01 lightside kernel: [ 1.029283] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 26 08:15:01 lightside kernel: [ 1.086282] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 26 08:15:01 lightside kernel: [ 1.128257] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Oct 26 08:15:01 lightside kernel: [ 1.143377] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 26 08:15:01 lightside kernel: [ 9.558497] NET: Registered protocol family 31
Oct 26 08:15:01 lightside kernel: [ 9.652539] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
Oct 26 08:15:01 lightside kernel: [ 10.313232] thinkpad_acpi: http://ibm-acpi.sf.net/
Oct 26 08:15:01 lightside kernel: [ 16.456031] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
Oct 26 08:15:01 lightside kernel: [ 16.733388] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 26 08:15:01 lightside kernel: [ 16.797357] NET: Registered protocol family 17
Oct 26 08:15:01 lightside kernel: [ 18.102112] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 26 08:15:02 lightside avahi-daemon[899]: Network interface enumeration completed.
Oct 26 08:15:02 lightside NetworkManager[937]: <info> NetworkManager (version 0.9.8.0) is starting...
Oct 26 08:15:02 lightside NetworkManager[937]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Oct 26 08:15:02 lightside NetworkManager[937]: <info> WEXT support is enabled
Oct 26 08:15:02 lightside systemd[1]: Started WPA supplicant.
Oct 26 08:15:02 lightside kernel: [ 27.058770] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 26 08:15:04 lightside NetworkManager[937]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
Oct 26 08:15:04 lightside NetworkManager[937]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Oct 26 08:15:04 lightside NetworkManager[937]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Oct 26 08:15:04 lightside NetworkManager[937]: SCPlugin-Ifupdown: init!
Oct 26 08:15:04 lightside NetworkManager[937]: SCPlugin-Ifupdown: update_system_hostname
Oct 26 08:15:04 lightside NetworkManager[937]: SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: adding eth0 to connections
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: adding iface eth0 to eni_ifaces
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: autoconnect
Oct 26 08:15:05 lightside NetworkManager[937]: SCPluginIfupdown: management mode: managed
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0)
Oct 26 08:15:05 lightside NetworkManager[937]: SCPluginIfupdown: locking wired connection setting
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0)
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: end _init.
Oct 26 08:15:05 lightside NetworkManager[937]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
Oct 26 08:15:05 lightside NetworkManager[937]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: (21902512) ... get_connections.
Oct 26 08:15:05 lightside NetworkManager[937]: SCPlugin-Ifupdown: (21902512) connections count: 1
Oct 26 08:15:05 lightside NetworkManager[937]: claim_connection: assertion `nm_connection_get_path (NM_CONNECTION (connection)) == NULL' failed
Oct 26 08:15:05 lightside NetworkManager[937]: <info> monitoring kernel firmware directory '/lib/firmware'.
Oct 26 08:15:05 lightside NetworkManager[937]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Oct 26 08:15:05 lightside NetworkManager[937]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill1) (driver iwl3945)
Oct 26 08:15:05 lightside NetworkManager[937]: <info> WiFi hardware radio set enabled
Oct 26 08:15:05 lightside systemd[1]: Started Network Manager.
Oct 26 08:15:05 lightside NetworkManager[937]: <info> WiFi enabled by radio killswitch; enabled by state file
Oct 26 08:15:05 lightside NetworkManager[937]: <info> WWAN enabled by radio killswitch; enabled by state file
Oct 26 08:15:05 lightside NetworkManager[937]: <info> WiMAX enabled by radio killswitch; enabled by state file
Oct 26 08:15:05 lightside NetworkManager[937]: <info> Networking is enabled by state file
Oct 26 08:15:05 lightside NetworkManager[937]: <warn> failed to allocate link cache: (-10) Operation not supported
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): carrier is ON
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): preparing device.
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): deactivating device (reason 'managed') [2]
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (wlan0): using nl80211 for WiFi device control
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwl3945' ifindex: 3)
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (wlan0): bringing up device.
Oct 26 08:15:05 lightside kernel: [ 29.758712] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0): preparing device.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0): deactivating device (reason 'managed') [2]
Oct 26 08:15:04 lightside kernel: [ 29.831144] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 26 08:15:04 lightside NetworkManager[937]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Oct 26 08:15:04 lightside NetworkManager[937]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Oct 26 08:15:04 lightside NetworkManager[937]: <info> wpa_supplicant started
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Auto-activating connection 'Ifupdown (eth0)'.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) starting connection 'Ifupdown (eth0)'
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 26 08:15:04 lightside openvpn[1221]: Starting virtual private network daemon:.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> dhclient started with pid 1244
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Beginning IP6 addrconf.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Oct 26 08:15:04 lightside dhclient: Internet Systems Consortium DHCP Client 4.2.4
Oct 26 08:15:04 lightside dhclient: Copyright 2004-2012 Internet Systems Consortium.
Oct 26 08:15:04 lightside dhclient: All rights reserved.
Oct 26 08:15:04 lightside dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct 26 08:15:04 lightside dhclient:
Oct 26 08:15:04 lightside NetworkManager[937]: <info> modem-manager is now available
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0) supports 4 scan SSIDs
Oct 26 08:15:04 lightside NetworkManager[937]: <warn> Trying to remove a non-existant call id.
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0): supplicant interface state: starting -> ready
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0): supplicant interface state: ready -> inactive
Oct 26 08:15:04 lightside NetworkManager[937]: <info> (wlan0) supports 4 scan SSIDs
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Oct 26 08:15:05 lightside dhclient: Listening on LPF/eth0/00:1c:25:1c:85:b6
Oct 26 08:15:05 lightside dhclient: Sending on LPF/eth0/00:1c:25:1c:85:b6
Oct 26 08:15:05 lightside dhclient: Sending on Socket/fallback
Oct 26 08:15:05 lightside dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct 26 08:15:05 lightside dhclient: DHCPACK from 10.43.57.1
Oct 26 08:15:05 lightside NetworkManager[937]: <info> (eth0): DHCPv4 state changed preinit -> reboot
Oct 26 08:15:05 lightside NetworkManager[937]: <info> address 10.43.57.254
Oct 26 08:15:05 lightside NetworkManager[937]: <info> prefix 24 (255.255.255.0)
Oct 26 08:15:05 lightside NetworkManager[937]: <info> gateway 10.43.57.1
Oct 26 08:15:05 lightside NetworkManager[937]: <info> nameserver '80.71.128.11'
Oct 26 08:15:05 lightside NetworkManager[937]: <info> nameserver '80.71.128.27'
Oct 26 08:15:05 lightside NetworkManager[937]: <info> domain name 'parknet.dk'
Oct 26 08:15:05 lightside NetworkManager[937]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct 26 08:15:05 lightside NetworkManager[937]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Oct 26 08:15:05 lightside dhclient: bound to 10.43.57.254 -- renewal in 1750 seconds.
Oct 26 08:15:06 lightside NetworkManager[937]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Oct 26 08:15:06 lightside NetworkManager[937]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Oct 26 08:15:06 lightside NetworkManager[937]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 26 08:15:06 lightside NetworkManager[937]: <info> Policy set 'Ifupdown (eth0)' (eth0) as default for IPv4 routing and DNS.
Oct 26 08:15:06 lightside NetworkManager[937]: <info> Writing DNS information to /sbin/resolvconf
Oct 26 08:15:06 lightside NetworkManager[937]: <info> Activation (eth0) successful, device activated.
Oct 26 08:15:25 lightside NetworkManager[937]: <info> (eth0): IP6 addrconf timed out or failed.
Oct 26 08:15:25 lightside NetworkManager[937]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Oct 26 08:15:25 lightside NetworkManager[937]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Oct 26 08:15:25 lightside NetworkManager[937]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
I am here from downtown, I am here from Mitch & Murray, on a mission of mercy....
Re: Setting up Wireless 3945ABG [Golan] [8086:4227]
My guess is the wired connection is set up as 'automatic', the wireless not.
So NetworkManager fires up eth0 and that's it, thinking 'That is all that is expected of me, I can sit back and watch the state of that connection.'
So NetworkManager fires up eth0 and that's it, thinking 'That is all that is expected of me, I can sit back and watch the state of that connection.'
Connected. Take this REPL, brother, and may it serve you well.