Porteus 3.2.2 WIFi troubles

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
frederick
White ninja
White ninja
Posts: 16
Joined: 13 Jan 2017, 16:31
Distribution: Porteus 3.2.2 Mate 32bit
Location: toronto

Porteus 3.2.2 WIFi troubles

Post#1 by frederick » 13 Jan 2017, 19:29

Brief introduction: I've been a long time user and lurker of this forums, since 2014 and porteus 2.0, i think. But am a first time poster. I want to say thank you to brokenman, fanthom and everyone that made porteus possible!

And now my problem.
Using porteus 3.2.2 - Mate version, when i try to connect through wifi I get a message saying:

connection failure
Failed to add/activate connection
(0) active connection could not be attached to the device

lspci -knn
  • 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express [14e4:167d] (rev 11)
    Subsystem: IBM ThinkPad Z60t [1014:0577]
    Kernel driver in use: tg3
    Kernel modules: tg3

    04:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
    Subsystem: Intel Corporation Device [8086:2711]
    Kernel driver in use: ipw2200
    Kernel modules: ipw2200, wl
Relevant parts of
dmesg

Code: Select all

[    0.000000] Linux version 4.9.0-porteus (root@porteus) (gcc version 5.3.0 (GCC) ) #1 SMP PREEMPT Sun Dec 18 16:24:27 Local time zone must be set--


[    0.000000] SMBIOS 2.3 present.
[    0.000000] DMI: IBM 18663GU/18663GU, BIOS 75ET60WW (2.06 ) 12/19/2006


[    1.168053] usb 1-4: new high-speed USB device number 2 using ehci-pci
[    1.302507] usb 1-4: New USB device found, idVendor=0951, idProduct=1666
[    1.302511] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.302513] usb 1-4: Product: DataTraveler 3.0
[    1.302516] usb 1-4: Manufacturer: Kingston
[    1.302518] usb 1-4: SerialNumber: 60A44C413CCBBE416B4F237F
[    1.302821] usb-storage 1-4:1.0: USB Mass Storage device detected


[   17.071226] lib80211: common routines for IEEE802.11 drivers
[   17.071229] lib80211_crypt: registered algorithm 'NULL'
[   17.071580] libipw: 802.11 data/management/control stack, git-1.1.13
[   17.071582] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
[   17.073341] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmpr
[   17.073343] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[   17.131343] tg3 0000:02:00.0 eth0: Tigon3 [partno(BCM95751M) rev 4101] (PCI Express) MAC address 00:0a:e4:3c:6f:78
[   17.131349] tg3 0000:02:00.0 eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[   17.131353] tg3 0000:02:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[   17.131356] tg3 0000:02:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]


[   17.207579] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[   17.234244] intel_rng: FWH not detected
[   17.536892] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)


[   18.754795] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   18.903260] wl: loading out-of-tree module taints kernel.
[   18.903267] wl: module license 'MIXED/Proprietary' taints kernel.
[   18.903268] Disabling lock debugging due to kernel taint
[   20.724907] Adding 4415036k swap on /dev/sda2.  Priority:-1 extents:1 across:4415036k FS
[   24.296465] eth1: Setting MAC to b6:66:6e:2c:5a:ac
[   25.810173] tg3 0000:02:00.0 eth0: Link is up at 100 Mbps, full duplex
[   25.810178] tg3 0000:02:00.0 eth0: Flow control is off for TX and off for RX
[   26.300626] NET: Registered protocol family 10
[   26.302486] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  192.777299] eth1: Setting MAC to 00:13:ce:86:0b:28
[  192.881273] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  192.931465] eth1: Setting MAC to 16:68:a2:34:7f:33
[  193.031815] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  193.072002] eth1: Setting MAC to 16:68:a2:34:7f:33
[  193.072285] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
lsmod

Code: Select all

Module                  Size  Used by
ipv6                  191345  16
wl                   6022460  0
ppdev                   4132  0
input_leds              1760  0
i2c_i801                9452  0
i2c_smbus               1792  1 i2c_i801
rng_core                3160  0
pcmcia                 20872  0
i915                  768736  3
8250_pci               25440  0
snd_intel8x0           18612  2
ipw2200                93972  0
libipw                 15487  1 ipw2200
lib80211                1764  1 libipw
snd_ac97_codec         67037  1 snd_intel8x0
snd_pcm                40940  2 snd_ac97_codec,snd_intel8x0
snd_timer              11096  1 snd_pcm
ac97_bus                 768  1 snd_ac97_codec
yenta_socket           13670  0
pcmcia_rsrc             4832  1 yenta_socket
cfg80211              139900  3 wl,ipw2200,libipw
pcmcia_core             6672  3 yenta_socket,pcmcia,pcmcia_rsrc
tg3                   107968  0
ptp                     6568  1 tg3
pps_core                3780  1 ptp
libphy                 16192  1 tg3
shpchp                 15494  0
intel_agp               6464  0
intel_gtt               7216  2 intel_agp,i915
firmware_class          4112  4 ipw2200,pcmcia,tg3,i915
thinkpad_acpi          41364  0
nvram                   3372  1 thinkpad_acpi
led_class               1892  2 input_leds,thinkpad_acpi
rfkill                  8444  3 thinkpad_acpi,cfg80211
fjes                   13120  0
8250                    8776  1 8250_pci
8250_base              14400  2 8250_pci,8250
serial_core            12480  4 8250,8250_base
parport_pc             18020  0
parport                20716  2 parport_pc,ppdev
nsc_ircc                9288  0
irda                   57536  1 nsc_ircc
crc_ccitt               1024  1 irda
acpi_cpufreq            4852  1
After editing connection by checking in tab General: "all users may connect to this network", and entering wifi password in tab Security, y get the same warning:

connection failure
Failed to add/activate connection
(0) active connection could not be attached to the device

and dmesg adds a lot of: eth1: Setting MAC .....

Code: Select all

[   24.296465] eth1: Setting MAC to b6:66:6e:2c:5a:ac
[   25.810173] tg3 0000:02:00.0 eth0: Link is up at 100 Mbps, full duplex
[   25.810178] tg3 0000:02:00.0 eth0: Flow control is off for TX and off for RX
[   26.300626] NET: Registered protocol family 10
[   26.302486] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  192.777299] eth1: Setting MAC to 00:13:ce:86:0b:28
[  192.881273] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  192.931465] eth1: Setting MAC to 16:68:a2:34:7f:33
[  193.031815] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  193.072002] eth1: Setting MAC to 16:68:a2:34:7f:33
[  193.072285] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  535.022419] eth1: Setting MAC to ee:94:7e:ea:39:a0
[  535.171091] eth1: Setting MAC to ee:94:7e:ea:39:a0
[  851.005000] eth1: Setting MAC to 36:cd:7f:91:72:09
[  851.139494] eth1: Setting MAC to 36:cd:7f:91:72:09
[ 1167.022230] eth1: Setting MAC to e6:e4:de:1d:23:2f
[ 1167.156497] eth1: Setting MAC to e6:e4:de:1d:23:2f
[ 1483.003061] eth1: Setting MAC to 86:14:b9:29:42:8d
[ 1483.138387] eth1: Setting MAC to 86:14:b9:29:42:8d
[ 1799.020488] eth1: Setting MAC to aa:a9:37:c7:f8:21
[ 1799.155842] eth1: Setting MAC to aa:a9:37:c7:f8:21
[ 2115.004421] eth1: Setting MAC to d6:fb:c5:1f:ed:d9
[ 2115.139439] eth1: Setting MAC to d6:fb:c5:1f:ed:d9
[ 2431.008403] eth1: Setting MAC to de:1f:a9:6a:e3:73
[ 2431.143493] eth1: Setting MAC to de:1f:a9:6a:e3:73
[ 2747.008535] eth1: Setting MAC to da:67:1b:65:8b:fb
[ 2747.506162] eth1: Setting MAC to da:67:1b:65:8b:fb
[ 3063.029166] eth1: Setting MAC to 6e:6f:c3:bc:66:be
[ 3063.163798] eth1: Setting MAC to 6e:6f:c3:bc:66:be
[ 3379.009617] eth1: Setting MAC to 1e:7c:6e:cc:b4:7d
[ 3379.492792] eth1: Setting MAC to 1e:7c:6e:cc:b4:7d
[ 3695.001670] eth1: Setting MAC to c6:d3:cb:45:44:be
[ 3695.137481] eth1: Setting MAC to c6:d3:cb:45:44:be
[ 4011.018076] eth1: Setting MAC to c6:48:31:83:7d:7a
[ 4011.153448] eth1: Setting MAC to c6:48:31:83:7d:7a
[ 4327.002863] eth1: Setting MAC to 76:99:48:93:b3:b9
[ 4327.137369] eth1: Setting MAC to 76:99:48:93:b3:b9
[ 4643.013656] eth1: Setting MAC to 46:61:2e:50:90:75
[ 4643.149665] eth1: Setting MAC to 46:61:2e:50:90:75
[ 4959.005774] eth1: Setting MAC to 56:66:80:e4:49:98
[ 4959.140274] eth1: Setting MAC to 56:66:80:e4:49:98
[ 5275.021927] eth1: Setting MAC to b2:05:4e:4c:7d:d1
[ 5275.156735] eth1: Setting MAC to b2:05:4e:4c:7d:d1
[ 5591.006947] eth1: Setting MAC to 7e:f7:10:e3:ec:a7
[ 5591.490278] eth1: Setting MAC to 7e:f7:10:e3:ec:a7
[ 5907.004286] eth1: Setting MAC to 16:a0:51:f1:b2:4d
[ 5907.133528] eth1: Setting MAC to 16:a0:51:f1:b2:4d
[ 6222.917688] eth1: Setting MAC to 00:13:ce:86:0b:28
[ 6223.064435] eth1: Setting MAC to 72:89:34:05:c0:af
[ 6223.212109] eth1: Setting MAC to 72:89:34:05:c0:af
what i don't see is anything connected to WLAN?, and eth1, broadcom ethernet is working ok. BTW it works perfect with 3.0 and 3.1.

Thanks in advance for your help, and best regards!
Frederick

User avatar
Blaze
DEV Team
DEV Team
Posts: 1501
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus 3.2.2 WIFi troubles

Post#2 by Blaze » 13 Jan 2017, 19:37

Hi Frederick.
Try to disable IPv6 in NetworkManager
Image
then restart NetworkManager

Code: Select all

su
toor
/etc/rc.d/rc.networkmanager restart
Regards,
Blaze
Linux porteus 4.13.3-porteus #1 SMP PREEMPT Sat Sep 23 18:22:13 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

frederick
White ninja
White ninja
Posts: 16
Joined: 13 Jan 2017, 16:31
Distribution: Porteus 3.2.2 Mate 32bit
Location: toronto

Re: Porteus 3.2.2 WIFi troubles

Post#3 by frederick » 13 Jan 2017, 20:41

Blaze, tried what you suggested. Although I don't read Russian, I assumed it has got to be the "Ignore" setting in IPv6, and got another set of problems.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# /etc/rc.d/rc.networkmanager restart
Stopping NetworkManager: /etc/rc.d/rc.networkmanager: line 63: kill: ?: arguments must be process or job IDs
stopped
Starting NetworkManager daemon:  /usr/sbin/NetworkManager
Seems the network doen's reestart. The applet says "network manager not running". Tried

Code: Select all

root@porteus:/home/guest# /etc/rc.d/rc.networkmanager start
NetworkManager is already running (will not start it twice).
root@porteus:/home/guest# 
Although network is up and running, the applet still says "network manager not running" and has an small red x on it.
Made a save.dat file, rebooted, changes are now there and permanent, but still getting the same message and unable to connect.
Don't know if this thread should remain here or someone in the know should move it to Bug Reports.
Btw am using 32bits version, haven't figured out how to change it in my profile.

Thanks!!

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus 3.2.2 WIFi troubles

Post#4 by Bogomips » 13 Jan 2017, 21:29

Welcome to Porteus.

Under Board index

User Control Panel > Profile (tab) > Edit profile
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

frederick
White ninja
White ninja
Posts: 16
Joined: 13 Jan 2017, 16:31
Distribution: Porteus 3.2.2 Mate 32bit
Location: toronto

Re: Porteus 3.2.2 WIFi troubles

Post#5 by frederick » 13 Jan 2017, 21:51

Bogomips wrote:Welcome to Porteus.

Under Board index

User Control Panel > Profile (tab) > Edit profile
Bogomips, thank you for the welcome and the help.
Already changed my profile.

Regards!

donald
Full of knowledge
Full of knowledge
Posts: 1221
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Porteus 3.2.2 WIFi troubles

Post#6 by donald » 14 Jan 2017, 16:21

Hello frederick

Please reboot with ethernet detached into "always fresh" mode.
Is your wifi card working?

Code: Select all

rfkill list all
ifconfig -a
if yes, does it scan for networks

Code: Select all

iwlist scan
if yes, does it show your network?

if no,
what is the outcome of

Code: Select all

dmesg | grep ipw2200
any (firmware) errors?

does the firmware exist?

Code: Select all

ls /lib/firmware | grep ipw
network enabled?

Code: Select all

cat /var/lib/NetworkManager/NetworkManager.state
If all looks good, set up your connection (as guest)


btw.
what i have seen from others is:
Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
Subsystem: Intel Corporation Device [8086:2711]
Kernel driver in use: ipw2200
Kernel modules: ipw2200
so i'm not sure what the wl module in your "Kernel modules: ipw2200, wl" is good for.
maybe try:

Code: Select all

modprobe -r wl
modprobe -r ipw2200 && modprobe ipw2200
good luck.. :wink:

frederick
White ninja
White ninja
Posts: 16
Joined: 13 Jan 2017, 16:31
Distribution: Porteus 3.2.2 Mate 32bit
Location: toronto

Re: Porteus 3.2.2 WIFi troubles

Post#7 by frederick » 15 Jan 2017, 23:14

Hey Donald

Thanks to your suggestions, was able to discover a lot of things.
I was making a mistake on the definitions of the network adapters. Don't know why yet, but sometimes, linux uses eth instead of wlan for the wireless adapter. In my particular case eth1 is the wireless. And that the firmware, modules and adapter were loaded and working correctly.


After many tries without success, and even more tries following this wiki page, :wall:

http://alien.slackbook.org/dokuwiki/dok ... s_networks

was able to connect to the network using wpa_supplicant. Even then, the nm-applet keeps saying the network is disconnected.

reference
https://postimg.org/image/lms26eyop

Tried in a different computer, a thinkpad T60, the previous one is a thinkpad X41t, with exactly the same results. Granted, this computers are pretty old, but porteus 3.1 works like a champ in both of them.

reference
https://postimg.org/image/n20abvcvb/

At this point have to assume the problem lies with network manager or something else in porteus 3.2.2, 32 bits. Sadly, I lack the knowledge and experience necessary to follow this further, and someone with more know-how than I will be able to check on it.
Meanwhile, 3.1 it is, and a lot of learning about modules in the future.

regards!
frederick

frederick
White ninja
White ninja
Posts: 16
Joined: 13 Jan 2017, 16:31
Distribution: Porteus 3.2.2 Mate 32bit
Location: toronto

Re: Porteus 3.2.2 WIFi troubles

Post#8 by frederick » 26 Jan 2017, 07:59

Hello all!

First, I apologize in advance. This one is long, but might be some useful information in it.

Second let me say that I don't understand how all of you using 3.2.2-32 bits are able to connect trough wireless. Downloaded two clean iso's, mate and xfce, from: http://ftp.nluug.nl/os/Linux/distr/port ... us-v3.2.2/. Tried on three laptops with completely different hardware, lenovo, thinkpad and one hp, and none of them is able to connect to a wireless network in either release. :%)

So, returned to the original thinkpad.

Code: Select all

guest@porteus:~$ nmcli radio wifi
enabled
guest@porteus:~$ nmcli device wifi list
*  SSID         MODE   CHAN  RATE       SIGNAL  BARS  SECURITY  
   SmartRG7912  Infra  11    54 Mbit/s  100     ▂▄▆█  WPA1 WPA2 
   parev2       Infra  11    54 Mbit/s  95      ▂▄▆█  WPA1 WPA2 
   --           Infra  11    54 Mbit/s  92      ▂▄▆█  WPA2      
   --           Infra  2     54 Mbit/s  87      ▂▄▆█  WPA1 WPA2 
   Rogers57944  Infra  11    54 Mbit/s  82      ▂▄▆█  WPA1 WPA2 
   BELL586      Infra  1     54 Mbit/s  80      ▂▄▆_  WPA2      
guest@porteus:~$
Lost the screen, but believe me, was able to connect trough nmcli. Also booted into runlevel 3, and connected with pns-tools in 30 seconds.
The only thing am sure of, is that is not a hardware problem.
All that I read points to problems between slim and gnome-keyring. Once again, don't know, the set-up works great in 3.1.
But Syslog points to something of that order.

Code: Select all

Jan 25 23:30:30 porteus NetworkManager[840]: <warn>  [1485387030.4603] keyfile: 'hostname' option is deprecated and has no effect
Jan 25 23:30:31 porteus NetworkManager[840]: <warn>  [1485387031.1090] device (eth1): set-hw-addr: new MAC address 16:DE:5F:66:B8:1A not successfully set (scanning)
Jan 25 23:30:36 porteus console-kit-daemon[909]: WARNING: Failed to open connection to cgmanager. Is the cgmanager daemon running? 
Jan 25 23:30:39 porteus mate-session[919]: WARNING: AT-SPI: Could not obtain desktop path or name  
Jan 25 23:30:39 porteus mate-session[919]: WARNING: atk-bridge: GetRegisteredEvents returned message with unknown signature 
Jan 25 23:30:39 porteus mate-session[919]: WARNING: atk-bridge: get_device_events_reply: unknown signature


[Jan 25 23:32:14 porteus gnome-keyring-daemon[1264]: couldn't create socket directory: /root/.cache/keyring-KPADUY: No such file or directory
Jan 25 23:32:14 porteus gnome-keyring-daemon[1264]: couldn't bind to control socket: /root/.cache/keyring-KPADUY/control: No such file or directory


Jan 25 23:34:59 porteus NetworkManager[840]: <warn>  [1485387299.1430] device (eth1): set-hw-addr: new MAC address 00:13:CE:86:0B:28 not successfully set-cloned (permanent)
For guest, the directory with keyring, doesn't match the one that mate-session is looking for in Syslog.

Code: Select all

root@porteus:/home/guest/.cache# ls -al
total 0
drwx------  6 guest users 120 Jan 25 23:33 ./
drwxr-xr-x 23 guest users 440 Jan 25 23:30 ../
drwx------  2 guest users  60 Jan 25 23:58 dconf/
drwx------  2 guest users 120 Jan 25 23:33 keyring-CASQUY/
drwx------  3 guest users  60 Jan 25 23:30 mate/
root@porteus:/home/guest/.cache#


Killed nm-applet and run it from terminal to see if could log what's going on
KPADUY directory seems to be root keyring-directory.

Code: Select all

root@porteus:/home/guest# killall nm-applet
root@porteus:/home/guest# eval "'gnome-keyring-daemon'"

** (gnome-keyring-daemon:1264): WARNING **: couldn't create socket directory: /root/.cache/keyring-KPADUY: No such file or directory

** (gnome-keyring-daemon:1264): WARNING **: couldn't bind to control socket: /root/.cache/keyring-KPADUY/control: No such file or directory
root@porteus:/home/guest# exit
exit
Going as guest

Code: Select all

guest@porteus:~$ eval "'gnome-keyring-daemon'"
GNOME_KEYRING_CONTROL=/home/guest/.cache/keyring-CASQUY
SSH_AUTH_SOCK=/home/guest/.cache/keyring-CASQUY/ssh
GPG_AGENT_INFO=/home/guest/.cache/keyring-CASQUY/gpg:0:1
guest@porteus:~$ export GNOME_KEYRING_PID
guest@porteus:~$ export GNOME_KEYRING_SOCKET
guest@porteus:~$ nm-applet
This is while trying to connect for the first time

Code: Select all

** (nm-applet:1272): WARNING **: AT-SPI: Could not obtain desktop path or name

** (nm-applet:1272): WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature

** (nm-applet:1272): WARNING **: atk-bridge: get_device_events_reply: unknown signature

** (nm-applet:1272): WARNING **: atk-bridge: get_device_events_reply: unknown signature

(nm-applet:1272): nm-applet-WARNING **: Failed to add/activate connection: (0) Active connection could not be attached to the device
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

(nm-applet:1272): nm-applet-WARNING **: Connection activation failed: (0) Active connection could not be attached to the device
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

** (nm-connection-editor:1318): WARNING **: AT-SPI: Could not obtain desktop path or name

** (nm-connection-editor:1318): WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature

** (nm-connection-editor:1318): WARNING **: atk-bridge: get_device_events_reply: unknown signature

** (nm-connection-editor:1318): WARNING **: atk-bridge: get_device_events_reply: unknown signature
** Message: Cannot save connection due to error: Editor initializing...
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.GPhoto2VolumeMonitor: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gtk.vfs.GPhoto2VolumeMonitor exited with status 127 (g-dbus-error-quark, 25)
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 0. Must be [8,63] bytes or 64 hex digits

(nm-connection-editor:1318): Gtk-WARNING **: Failed to fetch network locations: The specified location is not mounted
This is while editing the connection parameters

Code: Select all

(nm-connection-editor:1318): Gtk-WARNING **: Failed to fetch network locations: The specified location is not mounted
invalid key-length 0. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 1. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 2. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 3. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 4. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 5. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 6. Must be [8,63] bytes or 64 hex digits
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid wpa-psk: invalid key-length 7. Must be [8,63] bytes or 64 hex digits
** Message: Connection validates and can be saved
Finished editing, and try to connect

Code: Select all

(nm-applet:1272): nm-applet-WARNING **: Connection activation failed: (0) Active connection could not be attached to the device
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

(nm-applet:1272): nm-applet-WARNING **: Connection activation failed: (0) Active connection could not be attached to the device
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Once again, sorry for the length of the post! Hopefully might help someone with more knowledge, to figure this one out, or give me a direction to where or what to look for.

Thanks a lot for reading! and my best regards.
frederick

frederick
White ninja
White ninja
Posts: 16
Joined: 13 Jan 2017, 16:31
Distribution: Porteus 3.2.2 Mate 32bit
Location: toronto

Re: Porteus 3.2.2 WIFi troubles

Post#9 by frederick » 28 Jan 2017, 00:39

Have it working... Kinda. :Yahoo!:
Reading some thinkpad forums for old hardware, someone was suggesting to try with another kernel version.

Donwnloaded vmliuz and 000-kernel.xzm from http://ftp.nluug.nl/os/Linux/distr/port ... eus-4.7.2/, dropped them into /boot/syslinux/ and /porteus/modules/, booted up, edited connection and bingo!.

Edit
that is /porteus/base/ for 000-kernel.xzm

Code: Select all

root@porteus:/home/guest# uname -a
Linux porteus 4.7.2-porteus #1 SMP PREEMPT Fri Sep 2 19:03:01 Local time zone must be set--s i686 Intel(R) Pentium(R) M processor 1.50GHz GenuineIntel GNU/Linux
root@porteus:/home/guest# 
Cat /var/log/messages

Code: Select all

Jan 27 18:12:18 porteus NetworkManager[809]: <info>  [1485540738.2291] device (eth1): Activation: starting connection 'SmartRG7912' (XXXXXXXX-YYYY-XXXX-YYYY-XXXXXXXXXXXX)
Jan 27 18:12:18 porteus NetworkManager[809]: <info>  [1485540738.2305] keyfile: update /etc/NetworkManager/system-connections/SmartRG7912 (XXXXXXXX-YYYY-YYYY-XXXX-YYYYYYYYYYYY,"SmartRG7912") and persist connection
Jan 27 18:12:18 porteus NetworkManager[809]: <info>  [1485540738.2312] audit: op="connection-add-activate" uuid="47264ff2-8152-479c-988e-9ae770295363" name="SmartRG7912" pid=1039 uid=1000 result="success"
Jan 27 18:12:18 porteus NetworkManager[809]: <info>  [1485540738.2409] manager: NetworkManager state is now CONNECTING
Jan 27 18:12:18 porteus kernel: [   67.325065] eth1: Setting MAC to 00:13:ce:86:0b:28
Jan 27 18:12:18 porteus NetworkManager[809]: <info>  [1485540738.3467] device (eth1): state change: prepare -> success (reason 'managed') [40 120 0]
Jan 27 18:12:18 porteus NetworkManager[809]: <info>  [1485540738.3471] manager: NetworkManager state is now CONNECTED
Jan 27 18:12:18 porteus kernel: [   67.429263] IPv6: ADDRCONF(NETDEV_UP): eth1: link is ready
Trying to find the difference in between kernels is way up above me. Some fun for the future, though!

Regards
frederick

Post Reply