Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
14.2 x86_64 , wicd finds no wlan0
74 views
Skip to first unread message
walter
Jan 15, 2017, 6:42:57 AM1/15/17
to
Hello all.
The problem is that wicd does not find the wlan.
I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC
8260 Wlan thing that requires iwlwifi-8000C-13.ucode.
Tuxedo delivered the notebook with an elementary os, i think this
is an ubuntu clone, that connected to the internet via wlan with
no problems, thus the required hardware seems to work.
OK I deleted ubuntu and installed Slackware 14.2 x86_64.
Now wicd-client does not find the wireless. Slackware comes with
the iwlwifi&c installed in /lib/firmware where wicd seems to look
for it. Then there is an Airplain mode key, i tried it, but no effect.
Perhaps the key is not working, on the other hand the Fn-key
controlling the keyboard illumination works flawless, and then there is
an led-indicator for the Airplane Mode which does not show his white
light, so i rather think that it is more a problem to switch the
airplane mode _on_ .
I then tried the slackware-current live, no success, somehow
slackware does not find the device. /sbin/ifconfig only shows eth0
and lo, no wlan0.
The wired connection works. I searched the net but found no answer. OK
I could use the wired connection, but the cable is somewhat clumsy, and
I always have to sit near the speedport...
Thanks for any help,
walter
The problem is that wicd does not find the wlan.
I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC
8260 Wlan thing that requires iwlwifi-8000C-13.ucode.
Tuxedo delivered the notebook with an elementary os, i think this
is an ubuntu clone, that connected to the internet via wlan with
no problems, thus the required hardware seems to work.
OK I deleted ubuntu and installed Slackware 14.2 x86_64.
Now wicd-client does not find the wireless. Slackware comes with
the iwlwifi&c installed in /lib/firmware where wicd seems to look
for it. Then there is an Airplain mode key, i tried it, but no effect.
Perhaps the key is not working, on the other hand the Fn-key
controlling the keyboard illumination works flawless, and then there is
an led-indicator for the Airplane Mode which does not show his white
light, so i rather think that it is more a problem to switch the
airplane mode _on_ .
I then tried the slackware-current live, no success, somehow
slackware does not find the device. /sbin/ifconfig only shows eth0
and lo, no wlan0.
The wired connection works. I searched the net but found no answer. OK
I could use the wired connection, but the cable is somewhat clumsy, and
I always have to sit near the speedport...
Thanks for any help,
walter
Doug713705
Jan 15, 2017, 6:58:49 AM1/15/17
to
Le 15-01-2017, walter nous expliquait dans
alt.os.linux.slackware
(<o5fn4v$dug$3...@dont-email.me>) :
> Hello all.
Hi,
> The problem is that wicd does not find the wlan.
>
> I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC
> 8260 Wlan thing that requires iwlwifi-8000C-13.ucode.
>
> Tuxedo delivered the notebook with an elementary os, i think this
> is an ubuntu clone, that connected to the internet via wlan with
> no problems, thus the required hardware seems to work.
>
> OK I deleted ubuntu and installed Slackware 14.2 x86_64.
> Now wicd-client does not find the wireless. Slackware comes with
> the iwlwifi&c installed in /lib/firmware where wicd seems to look
> for it. Then there is an Airplain mode key, i tried it, but no effect.
>
> Perhaps the key is not working, on the other hand the Fn-key
> controlling the keyboard illumination works flawless, and then there is
> an led-indicator for the Airplane Mode which does not show his white
> light, so i rather think that it is more a problem to switch the
> airplane mode _on_ .
Then rfkill shoud help you.
man rfkill to enable/disable you WiFi interface (airplane mode).
You may also look/grep at dmesg to see if the suitable driver is loaded
for your hardware.
> I then tried the slackware-current live, no success, somehow
> slackware does not find the device. /sbin/ifconfig only shows eth0
> and lo, no wlan0.
Depending on the driver it may have another name.
--
Je ne connaîtrai rien de tes habitudes
Il se peut même que tu sois décédée
Mais j'demanderai ta main pour la couper
-- H.F. Thiéfaine, L'ascenceur de 22H43
alt.os.linux.slackware
(<o5fn4v$dug$3...@dont-email.me>) :
> Hello all.
Hi,
> The problem is that wicd does not find the wlan.
>
> I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC
> 8260 Wlan thing that requires iwlwifi-8000C-13.ucode.
>
> Tuxedo delivered the notebook with an elementary os, i think this
> is an ubuntu clone, that connected to the internet via wlan with
> no problems, thus the required hardware seems to work.
>
> OK I deleted ubuntu and installed Slackware 14.2 x86_64.
> Now wicd-client does not find the wireless. Slackware comes with
> the iwlwifi&c installed in /lib/firmware where wicd seems to look
> for it. Then there is an Airplain mode key, i tried it, but no effect.
>
> Perhaps the key is not working, on the other hand the Fn-key
> controlling the keyboard illumination works flawless, and then there is
> an led-indicator for the Airplane Mode which does not show his white
> light, so i rather think that it is more a problem to switch the
> airplane mode _on_ .
man rfkill to enable/disable you WiFi interface (airplane mode).
You may also look/grep at dmesg to see if the suitable driver is loaded
for your hardware.
> I then tried the slackware-current live, no success, somehow
> slackware does not find the device. /sbin/ifconfig only shows eth0
> and lo, no wlan0.
--
Je ne connaîtrai rien de tes habitudes
Il se peut même que tu sois décédée
Mais j'demanderai ta main pour la couper
-- H.F. Thiéfaine, L'ascenceur de 22H43
walter
Jan 15, 2017, 8:02:52 AM1/15/17
to
Doug713705 (Sun, 15 Jan 2017 11:58:48 +0000) :
> Le 15-01-2017, walter nous expliquait dans alt.os.linux.slackware
> (<o5fn4v$dug$3...@dont-email.me>) :
>> Hello all.
> Hi,
>> The problem is that wicd does not find the wlan.
>> I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC 8260
>> Wlan thing that requires iwlwifi-8000C-13.ucode.
[...]
> Then rfkill shoud help you.
Thank you for looking into it.
rfkill only lists bluetooth:
# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
> You may also look/grep at dmesg to see if the suitable driver is loaded
> for your hardware.
dmesg | iwl yields no result, neither does dmesg | lan -
> Depending on the driver it may have another name.
Perhaps I don't know what to look for?
Even if i *explicitely* search the name of my wlan, it doesn't find
anything.
w.
> Le 15-01-2017, walter nous expliquait dans alt.os.linux.slackware
> (<o5fn4v$dug$3...@dont-email.me>) :
>> Hello all.
> Hi,
>> The problem is that wicd does not find the wlan.
>> I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC 8260
>> Wlan thing that requires iwlwifi-8000C-13.ucode.
> Then rfkill shoud help you.
rfkill only lists bluetooth:
# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
> You may also look/grep at dmesg to see if the suitable driver is loaded
> for your hardware.
> Depending on the driver it may have another name.
Even if i *explicitely* search the name of my wlan, it doesn't find
anything.
w.
walter
Jan 15, 2017, 8:04:51 AM1/15/17
to
walter (Sun, 15 Jan 2017 13:01:14 +0000) :
[...]
dmesg | grep iwl yields no result, neither does dmesg | lan -
of course.
w
[...]
> dmesg | iwl yields no result, neither does dmesg | lan -
Excuse me, I meant
dmesg | grep iwl yields no result, neither does dmesg | lan -
of course.
w
Doug713705
Jan 15, 2017, 8:26:01 AM1/15/17
to
Le 15-01-2017, walter nous expliquait dans
alt.os.linux.slackware
(<o5frqq$us7$5...@dont-email.me>) :
alt.os.linux.slackware
You can have a look at the precise hardware with lspci and then find the
missing driver if any.
When the apropriate kernel module is loaded, you may have some
information aboput it in dmesg.
You can also try to have a look at the modules loaded by the previous
installed system if still available.
Last thing you may *not* want to install both NetworkManager and Wicd
(NM comes with standard Slackware installation while Wicd is "extra"
package. Both installation may conflict each other).
I did not have used wicd since a while. Nowdays NetworkManager is
reliable in most of use cases.
root
Jan 15, 2017, 10:03:18 AM1/15/17
to
what kernel was running? You can try to update 14.2 to a later kernel
to see if your hardware is now covered.
Here is a link which sounds applicable:
http://askubuntu.com/questions/697279/installing-intel-iwlwifi-firmware-for-unclaimed-wireless-8260
Lew Pitcher
Jan 15, 2017, 11:02:14 AM1/15/17
to
On Sunday January 15 2017 06:41, in alt.os.linux.slackware, "walter"
Have you customized the WLAN settings in /etc/rc.d/rc.inet1.conf ?
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request
walter
Jan 15, 2017, 11:37:02 AM1/15/17
to
root (Sun, 15 Jan 2017 15:03:17 +0000) :
> walter <gn...@yahoo.de> wrote:
>> Hello all.
>>
>> The problem is that wicd does not find the wlan.
[...]
But the idea of upgrading has its charm, although I'll have to learn
that first. Will try slackware64-current first.
BTW tried to install that e1000e driver, but it didn't compile.
This process will take some time, starting tomorrow my job will claim
me.
> Here is a link which sounds applicable:
> http://askubuntu.com/questions/697279/installing-intel-iwlwifi-firmware-
for-unclaimed-wireless-8260
(this is strange because as I said the iwlwifi firmware is there, 14.2
ships it.)
Thanks for looking into it, I'll report the results.
walter
> walter <gn...@yahoo.de> wrote:
>> Hello all.
>>
>> The problem is that wicd does not find the wlan.
>>
> Can you restore the ubuntu clone and run tests on that? For instance,
> what kernel was running? You can try to update 14.2 to a later kernel to
> see if your hardware is now covered.
I think this is good advice. Ubuntu is just another linux, after all.
> Can you restore the ubuntu clone and run tests on that? For instance,
> what kernel was running? You can try to update 14.2 to a later kernel to
> see if your hardware is now covered.
But the idea of upgrading has its charm, although I'll have to learn
that first. Will try slackware64-current first.
BTW tried to install that e1000e driver, but it didn't compile.
This process will take some time, starting tomorrow my job will claim
me.
> Here is a link which sounds applicable:
> http://askubuntu.com/questions/697279/installing-intel-iwlwifi-firmware-
for-unclaimed-wireless-8260
ships it.)
Thanks for looking into it, I'll report the results.
walter
walter
Jan 15, 2017, 11:41:42 AM1/15/17
to
Lew Pitcher (Sun, 15 Jan 2017 11:02:11 -0500) :
> On Sunday January 15 2017 06:41, in alt.os.linux.slackware, "walter"
> <gn...@yahoo.de> wrote:
>> Hello all.
>> The problem is that wicd does not find the wlan.
>> I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC 8260
>> Wlan thing that requires iwlwifi-8000C-13.ucode.
[...]
> Have you customized the WLAN settings in /etc/rc.d/rc.inet1.conf ?
Tried to. Thanks for looking into it. Meanwhile I think this is a
hardware / driver problem. But I'll keep that in mind.
walter
> On Sunday January 15 2017 06:41, in alt.os.linux.slackware, "walter"
> <gn...@yahoo.de> wrote:
>> Hello all.
>> The problem is that wicd does not find the wlan.
>> I bought a new notebook, a Tuxedo N350DW, with a Intel Dual AC 8260
>> Wlan thing that requires iwlwifi-8000C-13.ucode.
> Have you customized the WLAN settings in /etc/rc.d/rc.inet1.conf ?
hardware / driver problem. But I'll keep that in mind.
walter
Edwin Johnson
Jan 15, 2017, 12:33:35 PM1/15/17
to
> slackware does not find the device. /sbin/ifconfig only shows eth0
use ifconfig -a to show all devices, as only ifconfig shows devices that are
up. If you don't see it using the switch -a then bet you have a driver
module not loading or not there for the device. lsmod can sometimes help
determine which are loading and their names.
I went through that with raspberry pi with 14.1 and ended up importing the
module from ubuntu (ugg!) But sounds like you are sans driver for that chip.
Hopefully not.
...Edwin
____________________________________________________________
"Once you have flown, you will walk the earth with your eyes
turned skyward, for there you have been, there you long to
return."-da Vinci http://kd5zlb.org
Henrik Carlqvist
Jan 16, 2017, 1:23:13 AM1/16/17
to
On Sun, 15 Jan 2017 16:35:24 +0000, walter wrote:
> BTW tried to install that e1000e driver, but it didn't compile.
The e1000e driver is not for wlan but for wired intel NICs. That driver
> BTW tried to install that e1000e driver, but it didn't compile.
is already a part of the standard Linux kernel and as such included in
Slackware. During the years, when I have been running old Slackware
versions together with new versions of intel NICs I have had to download
the source for a newer version of the e1000e kernel module and compile
it. So far I haven't seen any problem doing so.
As you said that your wired network connection was working, what do you
need the newly compiled e1000e driver for?
If you really need a new e1000e driver, what error message do you get
when trying to compile?
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
Chick Tower
Jan 16, 2017, 11:20:02 PM1/16/17
to
On 2017-01-15, walter wrote:
> Lew Pitcher (Sun, 15 Jan 2017 11:02:11 -0500) :
> Lew Pitcher (Sun, 15 Jan 2017 11:02:11 -0500) :
>> Have you customized the WLAN settings in /etc/rc.d/rc.inet1.conf ?
>
> Tried to. Thanks for looking into it. Meanwhile I think this is a
> hardware / driver problem. But I'll keep that in mind.
Note that Lew wasn't suggesting you do that. He simply asked if you
>
> Tried to. Thanks for looking into it. Meanwhile I think this is a
> hardware / driver problem. But I'll keep that in mind.
had done that. I don't mess with my rc.inet1.conf and my wireless
adapter connects just fine at public hotspots.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
walter
Jan 17, 2017, 9:58:20 AM1/17/17
to
Henrik Carlqvist (Mon, 16 Jan 2017 06:21:35 +0000) :
> On Sun, 15 Jan 2017 16:35:24 +0000, walter wrote:
>> BTW tried to install that e1000e driver, but it didn't compile.
[...]
> As you said that your wired network connection was working, what do you
> need the newly compiled e1000e driver for?
Obviously I got that wrong and I don't need it.
[...]
So it is the iwlwifi-8000C-13.ucode I need. Before installing that,
I checked and saw that Slackware already has it under /lib/firmware.
So perhaps I should upgrade the kernel. OTOH that elementary os
which was installed on this box before seems to have had an 4.4 kernel,
slackware as well.
I never had such a problem, perhaps I am describing it wrongly. But
thanks!
walter
> On Sun, 15 Jan 2017 16:35:24 +0000, walter wrote:
>> BTW tried to install that e1000e driver, but it didn't compile.
> As you said that your wired network connection was working, what do you
> need the newly compiled e1000e driver for?
[...]
So it is the iwlwifi-8000C-13.ucode I need. Before installing that,
I checked and saw that Slackware already has it under /lib/firmware.
So perhaps I should upgrade the kernel. OTOH that elementary os
which was installed on this box before seems to have had an 4.4 kernel,
slackware as well.
I never had such a problem, perhaps I am describing it wrongly. But
thanks!
walter
walter
Jan 17, 2017, 10:10:56 AM1/17/17
to
Edwin Johnson (Sun, 15 Jan 2017 17:33:31 +0000) :
> On 2017-01-15, walter <gn...@yahoo.de> wrote:
>> The problem is that wicd does not find the wlan.
>> slackware does not find the device. /sbin/ifconfig only shows eth0
> use ifconfig -a to show all devices, as only ifconfig shows devices that
> are up. If you don't see it using the switch -a then bet you have a
> driver module not loading or not there for the device.
yes, that is the case. Here is the ifconfig -a:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.112 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::82fa:5bff:fe3a:8739 prefixlen 64 scopeid 0x20<link>
ether 80:fa:5b:3a:87:39 txqueuelen 1000 (Ethernet)
RX packets 45776 bytes 61443636 (58.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 34304 bytes 2934670 (2.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdfc00000-dfc20000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 2 bytes 100 (100.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 100 (100.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> lsmod can
> sometimes help determine which are loading and their names.
What do I have to look for?
> I went through that with raspberry pi with 14.1 and ended up importing
> the module from ubuntu (ugg!)
How did you do that?
> But sounds like you are sans driver for
> that chip.
> Hopefully not.
I thought the driver was iwlwifi-8000C-13.ucode, but Slackware ships it
under /lib/firmware where it seems to belong.
Oh my....thanks for your help,
walter
> On 2017-01-15, walter <gn...@yahoo.de> wrote:
>> The problem is that wicd does not find the wlan.
>> slackware does not find the device. /sbin/ifconfig only shows eth0
> use ifconfig -a to show all devices, as only ifconfig shows devices that
> are up. If you don't see it using the switch -a then bet you have a
> driver module not loading or not there for the device.
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.112 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::82fa:5bff:fe3a:8739 prefixlen 64 scopeid 0x20<link>
ether 80:fa:5b:3a:87:39 txqueuelen 1000 (Ethernet)
RX packets 45776 bytes 61443636 (58.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 34304 bytes 2934670 (2.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdfc00000-dfc20000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 2 bytes 100 (100.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 100 (100.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> lsmod can
> sometimes help determine which are loading and their names.
> I went through that with raspberry pi with 14.1 and ended up importing
> the module from ubuntu (ugg!)
> But sounds like you are sans driver for
> that chip.
> Hopefully not.
under /lib/firmware where it seems to belong.
Oh my....thanks for your help,
walter
Ed Wilson
Jan 17, 2017, 1:30:31 PM1/17/17
to
walter wrote:
> Edwin Johnson (Sun, 15 Jan 2017 17:33:31 +0000) :
>
> Edwin Johnson (Sun, 15 Jan 2017 17:33:31 +0000) :
>
>> But sounds like you are sans driver for
>> that chip.
>> Hopefully not.
>
> I thought the driver was iwlwifi-8000C-13.ucode, but Slackware ships it
> under /lib/firmware where it seems to belong.
>
I think the driver is iwlmvm, and iwlwifi-8000c-13.ucode is the firmware
>> that chip.
>> Hopefully not.
>
> I thought the driver was iwlwifi-8000C-13.ucode, but Slackware ships it
> under /lib/firmware where it seems to belong.
>
that the driver sends to the hardware. That is my understanding after
finding the kernel.org page for the driver.
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
running "insmod iwlmvm" as root should load the driver if you have it
installed.
less kernel-modules-4.4.14-x86_64-1.txz|grep iwlmvm
-rw-r--r-- root/root 308672 2016-06-24 14:32
lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko
walter
Jan 17, 2017, 2:22:13 PM1/17/17
to
Ed Wilson (Tue, 17 Jan 2017 13:29:57 -0500) :
> walter wrote:
[...]
Thank you for doing thiThank you for doing this!
> https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
The kernel-modules-4.4.14-x86_64-1 package is installed, and a "locate"
succeeds with a
#> locate iwlmvm
#> /usr/src/linux-4.4.14/include/config/iwlmvm.h
#> /lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko
> less kernel-modules-4.4.14-x86_64-1.txz|grep iwlmvm -rw-r--r-- root/root
> 308672 2016-06-24 14:32
> lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko
Like you wrote.
#> modinfo iwlmvm
yields:
#> filename: /lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/
mvm/iwlmvm.ko
#> license: GPL
#> author: Copyright(c) 2003- 2015 Intel Corporation
<i...@linux.intel.com>
#> description: The new Intel(R) wireless AGN driver for Linux
#> depends: iwlwifi,mac80211,cfg80211
#> intree: Y
#> vermagic: 4.4.14 SMP mod_unload
#> parm: init_dbg:set to true to debug an ASSERT in INIT fw
(default: false (bool)
#> parm: power_scheme:power management scheme: 1-active, 2-
balanced, 3-low power, default: 2 (int)
#> parm: tfd_q_hang_detect:TFD queues hang detection (default:
true (bool)
So I think, I have it installed.
> running "insmod iwlmvm" as root should load the driver if you have it
> installed.
I did that and got:
sudo insmod iwlmvm
insmod: ERROR: could not load module iwlmvm: No such file or directory
while "sudo modprobe iwlmvm" :
#> modprobe iwlmvm
gives no output. Still no wlan0.
Thanks a lot,
Erich
> walter wrote:
[...]
>> I thought the driver was iwlwifi-8000C-13.ucode, but Slackware ships it
>> under /lib/firmware where it seems to belong.
> I think the driver is iwlmvm, and iwlwifi-8000c-13.ucode is the firmware
> that the driver sends to the hardware.
AAH!
>> under /lib/firmware where it seems to belong.
> I think the driver is iwlmvm, and iwlwifi-8000c-13.ucode is the firmware
> that the driver sends to the hardware.
Thank you for doing thiThank you for doing this!
> https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
The kernel-modules-4.4.14-x86_64-1 package is installed, and a "locate"
succeeds with a
#> locate iwlmvm
#> /usr/src/linux-4.4.14/include/config/iwlmvm.h
#> /lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko
> less kernel-modules-4.4.14-x86_64-1.txz|grep iwlmvm -rw-r--r-- root/root
> 308672 2016-06-24 14:32
> lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko
#> modinfo iwlmvm
yields:
#> filename: /lib/modules/4.4.14/kernel/drivers/net/wireless/iwlwifi/
mvm/iwlmvm.ko
#> license: GPL
#> author: Copyright(c) 2003- 2015 Intel Corporation
<i...@linux.intel.com>
#> description: The new Intel(R) wireless AGN driver for Linux
#> depends: iwlwifi,mac80211,cfg80211
#> intree: Y
#> vermagic: 4.4.14 SMP mod_unload
#> parm: init_dbg:set to true to debug an ASSERT in INIT fw
(default: false (bool)
#> parm: power_scheme:power management scheme: 1-active, 2-
balanced, 3-low power, default: 2 (int)
#> parm: tfd_q_hang_detect:TFD queues hang detection (default:
true (bool)
So I think, I have it installed.
> running "insmod iwlmvm" as root should load the driver if you have it
> installed.
sudo insmod iwlmvm
insmod: ERROR: could not load module iwlmvm: No such file or directory
while "sudo modprobe iwlmvm" :
#> modprobe iwlmvm
gives no output. Still no wlan0.
Thanks a lot,
Erich
Sylvain Robitaille
Jan 17, 2017, 2:44:04 PM1/17/17
to
On 2017-01-17, walter wrote:
>> running "insmod iwlmvm" as root should load the driver if you have it
>> installed.
>
> I did that and got:
>
> sudo insmod iwlmvm
> insmod: ERROR: could not load module iwlmvm: No such file or directory
>
> while "sudo modprobe iwlmvm" :
>
> #> modprobe iwlmvm
>
> gives no output. Still no wlan0.
"modprobe -v iwlmvm" might give you a *bit* more insight, though most
>> running "insmod iwlmvm" as root should load the driver if you have it
>> installed.
>
> I did that and got:
>
> sudo insmod iwlmvm
> insmod: ERROR: could not load module iwlmvm: No such file or directory
>
> while "sudo modprobe iwlmvm" :
>
> #> modprobe iwlmvm
>
> gives no output. Still no wlan0.
likely only that the module is indeed loading (you can confirm with
"lsmod |grep -w ^iwlmvm", anyway)
Either way, I would suggest also checking the output of "dmesg"
immediately after loading the module, as that might provide
some insight. Check also for anything logged by the kernel
(/var/log/messages in a stock syslogd configuration?) That's where
you're most likely going to get the insight you need.
I hope that helps.
--
----------------------------------------------------------------------
Sylvain Robitaille s...@encs.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
Jerry Peters
Jan 17, 2017, 4:19:39 PM1/17/17
to
and dependencies.
>
> while "sudo modprobe iwlmvm" :
>
> #> modprobe iwlmvm
dependencies.
Look in /var/log/messages & search for iwl.
Henrik Carlqvist
Jan 18, 2017, 1:19:33 AM1/18/17
to
On Tue, 17 Jan 2017 19:44:03 +0000, Sylvain Robitaille wrote:
> Either way, I would suggest also checking the output of "dmesg"
> immediately after loading the module, as that might provide some
> insight. Check also for anything logged by the kernel
> (/var/log/messages in a stock syslogd configuration?) That's where
> you're most likely going to get the insight you need.
Also, look at the output of "/sbin/lspci" and "/sbin/lspci -n" which
> Either way, I would suggest also checking the output of "dmesg"
> immediately after loading the module, as that might provide some
> insight. Check also for anything logged by the kernel
> (/var/log/messages in a stock syslogd configuration?) That's where
> you're most likely going to get the insight you need.
shows PCI vendor and device ID. For intel the vendor ID should be 8086
and unless that vendor ID is together with the device ID in /lib/modules/
*/modules.pcimap no installed driver will fit to your hardware. If so,
googling for "Linux 8086:xxxx" might be the best start, where xxxx is
your PCI device ID.
walter
Jan 18, 2017, 1:20:55 AM1/18/17
to
Tue, 17 Jan 2017 19:20:34 +0000 (walter) :
[...]
> sudo insmod iwlmvm insmod: ERROR: could not load module iwlmvm: No such
> file or directory
Folks I got a new problem. Because of those modules problem I upgraded
the kernel by going to the slackware home page and downloading the
patches, which I wanted to do anyway because of the security updates.
Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
Xorg. The logfile says that it does not find some modules in directory:
/lib/modules/4.4.14
which is logical, as in /lib/modules are the 4.4.38 modules.
This is the first time I am using elilo instead of lilo. After a
kernel upgrade under lilo, I have to re-run /sbin/lilo, I know that,
but elilo is different, isn't it? At least
http://www.linuxquestions.org/questions/slackware-14/elilo-and-kernel-
upgrade-4175483900/
says so. Nonetheless I reinstalled elilo, but this keeps popping up.
Excuse me for having so much to ask and to learn....
w
[...]
> sudo insmod iwlmvm insmod: ERROR: could not load module iwlmvm: No such
> file or directory
the kernel by going to the slackware home page and downloading the
patches, which I wanted to do anyway because of the security updates.
Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
Xorg. The logfile says that it does not find some modules in directory:
/lib/modules/4.4.14
which is logical, as in /lib/modules are the 4.4.38 modules.
This is the first time I am using elilo instead of lilo. After a
kernel upgrade under lilo, I have to re-run /sbin/lilo, I know that,
but elilo is different, isn't it? At least
http://www.linuxquestions.org/questions/slackware-14/elilo-and-kernel-
upgrade-4175483900/
says so. Nonetheless I reinstalled elilo, but this keeps popping up.
Excuse me for having so much to ask and to learn....
w
Edwin Johnson
Jan 18, 2017, 10:19:01 AM1/18/17
to
uname -a tells me it mine is 4.4.37-v7-arm kernel in my raspberry pi 3.
Yours may be different. Also, my Slackware Arm is 14.2, 64 bit.
> What do I have to look for?
lsmod will give a list of loaded modules, and the actual chip driver for the
80211 appears to be brcmfac. If the actual chip driver isn't correct for the
chip in the rasp pi you will not see the wlan0. In mine part of the info
looks like this:
brcmfmac 185901 0
brcmutil 5725 1 brcmfmac
cfg80211 428926 1 brcmfmac
That module is found here in my computer:
/lib/modules/4.4.37-v7-arm/kernel/drivers/net/wireless/brcm80211/brcmfmac
Earlier I installed 14.1 and it didn't have the correct driver for the chip
and imported one from Ubuntu after finding some info from a google of the
problem on the net, but in this current 14.2 I didn't have to do anything.
Yours may be different. Also, my Slackware Arm is 14.2, 64 bit.
> What do I have to look for?
80211 appears to be brcmfac. If the actual chip driver isn't correct for the
chip in the rasp pi you will not see the wlan0. In mine part of the info
looks like this:
brcmfmac 185901 0
brcmutil 5725 1 brcmfmac
cfg80211 428926 1 brcmfmac
That module is found here in my computer:
/lib/modules/4.4.37-v7-arm/kernel/drivers/net/wireless/brcm80211/brcmfmac
Earlier I installed 14.1 and it didn't have the correct driver for the chip
and imported one from Ubuntu after finding some info from a google of the
problem on the net, but in this current 14.2 I didn't have to do anything.
walter
Jan 18, 2017, 11:43:59 AM1/18/17
to
Wed, 18 Jan 2017 06:19:16 +0000 (walter) :
[...]
4.4.14.
Is it possible to change that?
w
[...]
> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
> Xorg. The logfile says that it does not find some modules in directory:
> /lib/modules/4.4.14
> which is logical, as in /lib/modules are the 4.4.38 modules.
The problem is, that I upgraded the kernel, but uname -r still outputs
> Xorg. The logfile says that it does not find some modules in directory:
> /lib/modules/4.4.14
> which is logical, as in /lib/modules are the 4.4.38 modules.
4.4.14.
Is it possible to change that?
w
walter
Jan 18, 2017, 11:47:45 AM1/18/17
to
Wed, 18 Jan 2017 15:18:59 +0000 (Edwin Johnson) :
> On 2017-01-17, walter <gn...@yahoo.de> wrote:
>> Edwin Johnson (Sun, 15 Jan 2017 17:33:31 +0000) :
[...]
I managed to contact my vendor. The kernel version of the working
ubuntu clone elementaryOS is 4.9 Mainline Kernel.
Thus, it burns down to either renounce or compile that kernel. - ???
w
> On 2017-01-17, walter <gn...@yahoo.de> wrote:
>> Edwin Johnson (Sun, 15 Jan 2017 17:33:31 +0000) :
> lsmod will give a list of loaded modules, and the actual chip driver for
> the 80211 appears to be brcmfac. If the actual chip driver isn't correct
> for the chip in the rasp pi you will not see the wlan0. In mine part of
> the info looks like this:
[...]
> the 80211 appears to be brcmfac. If the actual chip driver isn't correct
> for the chip in the rasp pi you will not see the wlan0. In mine part of
> the info looks like this:
I managed to contact my vendor. The kernel version of the working
ubuntu clone elementaryOS is 4.9 Mainline Kernel.
Thus, it burns down to either renounce or compile that kernel. - ???
w
Sylvain Robitaille
Jan 18, 2017, 12:31:03 PM1/18/17
to
On 2017-01-18, walter wrote:
> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
> Xorg. The logfile says that it does not find some modules in
> directory:
>
> /lib/modules/4.4.14
>
> which is logical, as in /lib/modules are the 4.4.38 modules.
Based on your followup message, it seems as though your kernel update
> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
> Xorg. The logfile says that it does not find some modules in
> directory:
>
> /lib/modules/4.4.14
>
> which is logical, as in /lib/modules are the 4.4.38 modules.
didn't complete (perhaps you didn't run "(e)lilo" after updating?).
I would boot from an installation disk, but with "root=/dev/sda1"
(as appropriate for your root partition, of course), and retry the
kernel update (check, of course that that's the problem, and make
sure it completes properly before trying to reboot). If the kernel
update looks sane, chances are the boot loader hasn't been "notified"
of the change and it's still loading the old kernel.
remake your initrd, if that's required. I don't have any experience
with elilo, but with lilo you need to re-run "/sbin/lilo" in order
for the new initrd and the updated kernel to be used.
I hope this helps.
walter
Jan 18, 2017, 12:32:32 PM1/18/17
to
Wed, 18 Jan 2017 16:42:20 +0000 (walter) :
Excuse me for insisting.
I can log into the 14.2 slackware, but the x window cannot start because
the kernel version is 4.4.38, and uname -r responds 4.4.14.
I googled that, re-upgraded the kernel packages, then removepkg'd the
*kernel*.tgz and reinstalled. uname -r keeps responding 4.4.14.
On my old (outdated) notebook (the one from which I'm writing) the
upgrading to 4.4.38 went flawlessly.
Ready and willing to read & learn anything, where can I go?
walter
I can log into the 14.2 slackware, but the x window cannot start because
the kernel version is 4.4.38, and uname -r responds 4.4.14.
I googled that, re-upgraded the kernel packages, then removepkg'd the
*kernel*.tgz and reinstalled. uname -r keeps responding 4.4.14.
On my old (outdated) notebook (the one from which I'm writing) the
upgrading to 4.4.38 went flawlessly.
Ready and willing to read & learn anything, where can I go?
walter
Doug713705
Jan 18, 2017, 12:34:41 PM1/18/17
to
Le 18-01-2017, walter nous expliquait dans
alt.os.linux.slackware
(<o5o5tc$ruf$1...@dont-email.me>) :
So you did *not* upgraded the kernel !
> Is it possible to change that?
Yes, by upgrading the kernel :D
If your new kernel is correctly installed, you may have this dir entry:
- /lib/modules/<kernel-version>
If you don't have this directory entry, then you may have missed one step
while installing your kernel
Supposing that you have upgraded the kernel, you may have forgotten to
update your boot loader configuration file and/or depending on the boot
loader forgotten to run it.
If lilo is the installed boot loader:
- Edit /etc/lilo.conf
- Run lilo (as root)
- Reboot.
--
dis-moi qui tu suis... je te dirais qui je hais !
-- H.F. Thiéfaine, L'agence des amants de madame Müller
alt.os.linux.slackware
(<o5o5tc$ruf$1...@dont-email.me>) :
> Is it possible to change that?
If your new kernel is correctly installed, you may have this dir entry:
- /lib/modules/<kernel-version>
If you don't have this directory entry, then you may have missed one step
while installing your kernel
Supposing that you have upgraded the kernel, you may have forgotten to
update your boot loader configuration file and/or depending on the boot
loader forgotten to run it.
If lilo is the installed boot loader:
- Edit /etc/lilo.conf
- Run lilo (as root)
- Reboot.
--
dis-moi qui tu suis... je te dirais qui je hais !
-- H.F. Thiéfaine, L'agence des amants de madame Müller
Doug713705
Jan 18, 2017, 12:36:59 PM1/18/17
to
Le 18-01-2017, walter nous expliquait dans
alt.os.linux.slackware
(<o5o8od$dpn$1...@dont-email.me>) :
alt.os.linux.slackware
>
> I googled that, re-upgraded the kernel packages, then removepkg'd the
> *kernel*.tgz and reinstalled. uname -r keeps responding 4.4.14.
>
> On my old (outdated) notebook (the one from which I'm writing) the
> upgrading to 4.4.38 went flawlessly.
>
> Ready and willing to read & learn anything, where can I go?
loader still load the old kernel.
Lew Pitcher
Jan 18, 2017, 1:01:25 PM1/18/17
to
On Wednesday January 18 2017 12:34, in alt.os.linux.slackware, "Doug713705"
kernel is to
cat /proc/version
or
cat /proc/sys/kernel/osrelease
FWIW, uname(1) just reads (through the uname(2) syscall) the same info that is
externalized through the /proc/version and /proc/sys/kernel/* pseudo-files
> If your new kernel is correctly installed, you may have this dir entry:
> - /lib/modules/<kernel-version>
[snip]
HTH
<doug.l...@free.fr> wrote:
> Le 18-01-2017, walter nous expliquait dans
> alt.os.linux.slackware
> (<o5o5tc$ruf$1...@dont-email.me>) :
>
>> Wed, 18 Jan 2017 06:19:16 +0000 (walter) :
>>
>> [...]
>>> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
>>> Xorg. The logfile says that it does not find some modules in directory:
>>
>>> /lib/modules/4.4.14
>>
>>> which is logical, as in /lib/modules are the 4.4.38 modules.
>>
>> The problem is, that I upgraded the kernel, but uname -r still outputs
>> 4.4.14.
>>
>
> So you did *not* upgraded the kernel !
>
>> Is it possible to change that?
>
> Yes, by upgrading the kernel :D
FWIW, a direct way to determine the kernel version of the *currently running*
> Le 18-01-2017, walter nous expliquait dans
> alt.os.linux.slackware
> (<o5o5tc$ruf$1...@dont-email.me>) :
>
>> Wed, 18 Jan 2017 06:19:16 +0000 (walter) :
>>
>> [...]
>>> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
>>> Xorg. The logfile says that it does not find some modules in directory:
>>
>>> /lib/modules/4.4.14
>>
>>> which is logical, as in /lib/modules are the 4.4.38 modules.
>>
>> The problem is, that I upgraded the kernel, but uname -r still outputs
>> 4.4.14.
>>
>
> So you did *not* upgraded the kernel !
>
>> Is it possible to change that?
>
> Yes, by upgrading the kernel :D
kernel is to
cat /proc/version
or
cat /proc/sys/kernel/osrelease
FWIW, uname(1) just reads (through the uname(2) syscall) the same info that is
externalized through the /proc/version and /proc/sys/kernel/* pseudo-files
> If your new kernel is correctly installed, you may have this dir entry:
> - /lib/modules/<kernel-version>
HTH
walter
Jan 18, 2017, 2:59:03 PM1/18/17
to
Sylvain Robitaille (Wed, 18 Jan 2017 17:31:01 +0000) :
> On 2017-01-18, walter wrote:
>> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
>> Xorg. The logfile says that it does not find some modules in
>> directory:
>> /lib/modules/4.4.14
>> which is logical, as in /lib/modules are the 4.4.38 modules.
> Based on your followup message, it seems as though your kernel update
> didn't complete (perhaps you didn't run "(e)lilo" after updating?).
[...]
People you all helped and you set me on the right track. Excuses that I
don't answer to each of you, i appreciate everything and follow that.
Not being a native english speaker, I fear the right term for me
might be "nincompoop" (non compos mentis)
It is right that I didn't update elilo. Before with (non-e-)lilo,
I had a separate partition with just a non X slackware installation,
manageing only lilo, and emergencies. As my needs are not so great,
I always had 3 installations: the OnlyBoot system, the working system,
and an experimental system.
There was the lilo.conf on the OnlyBoot, and every time a new kernel
was installed, I run /sbin/lilo on OnlyBoot, never touching the
lilo.conf because this file pointed to the right vmlinuz'es on the
3 partitions.
Now this time because of the gpt partition table I started using elilo.
Being used to lilo, I had to learn something, because I thought,
elilo and lilo, no difference. Stupid. Googling i.e. in my case
Startpageing the topic I learned that there should be no need to update
efi elilo &c after an installation. This turned out to be not the
case at my system. (Took some time and tries.) It did not help only
to update elilo, i.e. run /usr/sbin/eliloconfig from my BootOnly
partition, but I *had* to run it from *the* partition where the new
kernel is installed or updated. This was new to me.
Now, updating elilo via /usr/sbin/eliloconfig (or via pkgtool) means
overwriting /boot/efi/EFI/Slackware/elilo.config and in this file,
analogous to lilo.conf, are my 3 slackware systems stored.
In my lilo times I just re-run /sbin/lilo from the OnlyBoot-System,
now I have to run it from the system where the new kernel is installed
or updated *and* then reinstall (re-copy) my original elilo.config.
Excuse my verbosity. Perhaps there is a guy out there struggling with
a similiar problem, and I remember it as good style to summarize a
(even partial) solution to whatever. I myself have profited many
times this way from other people. The friendly discussion in this group
has not only helped me by pointing to a solution, but also keep on
trying and searching.
Now the next step, installing the 4.9 kernel. Found an address:
https://extonlinux.wordpress.com/2016/12/23/run-your-slackware-
installation-with-the-latest-kernel-4-9/
See what I'll make of that.
walter
> On 2017-01-18, walter wrote:
>> Now after upgrading the kernel from 4.4.14 to 4.4.38 I cannot log into
>> Xorg. The logfile says that it does not find some modules in
>> directory:
>> /lib/modules/4.4.14
>> which is logical, as in /lib/modules are the 4.4.38 modules.
> Based on your followup message, it seems as though your kernel update
> didn't complete (perhaps you didn't run "(e)lilo" after updating?).
People you all helped and you set me on the right track. Excuses that I
don't answer to each of you, i appreciate everything and follow that.
Not being a native english speaker, I fear the right term for me
might be "nincompoop" (non compos mentis)
It is right that I didn't update elilo. Before with (non-e-)lilo,
I had a separate partition with just a non X slackware installation,
manageing only lilo, and emergencies. As my needs are not so great,
I always had 3 installations: the OnlyBoot system, the working system,
and an experimental system.
There was the lilo.conf on the OnlyBoot, and every time a new kernel
was installed, I run /sbin/lilo on OnlyBoot, never touching the
lilo.conf because this file pointed to the right vmlinuz'es on the
3 partitions.
Now this time because of the gpt partition table I started using elilo.
Being used to lilo, I had to learn something, because I thought,
elilo and lilo, no difference. Stupid. Googling i.e. in my case
Startpageing the topic I learned that there should be no need to update
efi elilo &c after an installation. This turned out to be not the
case at my system. (Took some time and tries.) It did not help only
to update elilo, i.e. run /usr/sbin/eliloconfig from my BootOnly
partition, but I *had* to run it from *the* partition where the new
kernel is installed or updated. This was new to me.
Now, updating elilo via /usr/sbin/eliloconfig (or via pkgtool) means
overwriting /boot/efi/EFI/Slackware/elilo.config and in this file,
analogous to lilo.conf, are my 3 slackware systems stored.
In my lilo times I just re-run /sbin/lilo from the OnlyBoot-System,
now I have to run it from the system where the new kernel is installed
or updated *and* then reinstall (re-copy) my original elilo.config.
Excuse my verbosity. Perhaps there is a guy out there struggling with
a similiar problem, and I remember it as good style to summarize a
(even partial) solution to whatever. I myself have profited many
times this way from other people. The friendly discussion in this group
has not only helped me by pointing to a solution, but also keep on
trying and searching.
Now the next step, installing the 4.9 kernel. Found an address:
https://extonlinux.wordpress.com/2016/12/23/run-your-slackware-
installation-with-the-latest-kernel-4-9/
See what I'll make of that.
walter
0 new messages