LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 11-15-2017, 09:47 AM   #1
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Rep: Reputation: 16
wicd wireless problems


Hi:
On a VAIO with debian9 (stretch), wicd, Zyxel router WPA 1/2 pass, wired connection is OK, also on long connection to far clusters and remote visualization. In contrast, wireless connection normally fails. However, when it is established, it is as reliable as wired.

When wireless fails, the terminal reads:

Quote:
francesco@vaio64:~$ wicd-client
Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 230, in maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/share/wicd/gtk/gui.py", line 287, in handle_connection_results
error(self.window, language[results], block=False)
KeyError: dbus.String(u'dhcp_failed')
refreshing...
ESSID : ZyXEL
ESSID : Telecom-13632009
ESSID : FRITZ!Box 3272
^CTraceback (most recent call last):
File "/usr/share/wicd/gtk/wicd-client.py", line 1204, in <module>
main(sys.argv)
File "/usr/share/wicd/gtk/wicd-client.py", line 103, in wrapper
return func(*args, **kwargs)
File "/usr/share/wicd/gtk/wicd-client.py", line 1200, in main
mainloop.run()
KeyboardInterrupt
francesco@vaio64:~$ wicd-client
Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 230, in maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/share/wicd/gtk/gui.py", line 287, in handle_connection_results
error(self.window, language[results], block=False)
KeyError: dbus.String(u'dhcp_failed')
Launching wicd-client or wicd-curses normally raises empty windows.

When I am in Austria, with the same vaio, never experienced problems with wi-fy from another router. Otherwise, as I said, when wirelles is established through the Zyxels, it never fails on constant RMV with far cluster.

Thanks for advice, should what I reported being enough for grasping the problem.

chiendarret
 
Old 11-15-2017, 11:45 AM   #2
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Ceni bails me out when wicd fails to connect for whatever reason. It is command line used in a terminal. Real small also.

Code:
wget -c http://packages.siduction.org/base/pool/main/c/ceni/ceni_2.38_all.deb
To install

Code:
dpkg -i ceni_2.38_all.deb
In case of dependecy errors

Code:
apt-get -f install
to launch it

Code:
ceni
It takes up hardly any space and I have had wicd fail where the router and wicd showed connected. But the router needed to be reset before wicd would interface with it. Hint: I also learned bad password in Wicd means reset the router also. You can try CENI or not. Just giving choice here.

Next time you get this problem in Wicd. A

Code:
sudo ifconfig -a
May not hurt to be posted either. WICD has been pretty good using my Samsung S7 Edge as a router out in the wilderness when I am on my motorcycle.
 
Old 11-16-2017, 01:19 PM   #3
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
Here on failure to connect with wicd. Thanks
Quote:
ifconfig -a
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:be:bf:f1:bf txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18

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 1300 bytes 105760 (103.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1300 bytes 105760 (103.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 7a:9f:33:26:17:92 txqueuelen 1000 (Ethernet)
RX packets 102 bytes 33001 (32.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35 bytes 5982 (5.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
 
Old 11-16-2017, 02:57 PM   #4
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Well. Looks like wlan0 is seen. How about posting a last 20 or so lines relating to wicd and wlan0 running dmesg in terminal when it fails.

Just to be sure. I'll include sudo.

Code:
sudo dmesg | tail -20
 
Old 11-16-2017, 03:36 PM   #5
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
Here it is:

Quote:
dmesg | tail -20
[ 85.846599] hid-generic 0003:04F2:0939.0002: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1d.0-1.6/input0
[ 126.214510] wlan0: deauthenticating from 00:13:49:a3:15:37 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 126.248494] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 126.437504] sky2 0000:04:00.0 eth0: disabling interface
[ 126.446252] sky2 0000:04:00.0 eth0: enabling interface
[ 126.446824] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 126.774930] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 127.694038] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 127.898641] sky2 0000:04:00.0 eth0: disabling interface
[ 127.907556] sky2 0000:04:00.0 eth0: enabling interface
[ 127.908147] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 128.953425] wlan0: authenticate with 00:13:49:a3:15:37
[ 128.966672] wlan0: send auth to 00:13:49:a3:15:37 (try 1/3)
[ 128.968533] wlan0: authenticated
[ 128.968560] ath9k 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 128.968565] ath9k 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 128.969084] wlan0: associate with 00:13:49:a3:15:37 (try 1/3)
[ 128.971627] wlan0: RX AssocResp from 00:13:49:a3:15:37 (capab=0x471 status=0 aid=2)
[ 128.971808] wlan0: associated
[ 128.971870] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
"wlan0: link becomes ready": that is always seen, no matter whether wireless connection occurs or not (when "# dhclient" is silent, also "startx" only raises X11 for xfce.
 
Old 11-16-2017, 03:49 PM   #6
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Might wanna google search

Quote:
3=DEAUTH_LEAVING
My results

Gotta admit. This is a toughy for me.
 
Old 11-16-2017, 03:56 PM   #7
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Just curious. Anything spit out when you run.

Code:
dmesg | grep firmware
I'm wondering if this is a hardware limitation having to do with

Quote:
Zyxel router
and

Quote:
ath9k

Last edited by rokytnji; 11-16-2017 at 04:02 PM.
 
Old 11-16-2017, 04:39 PM   #8
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Just to make sure yours matches mine.

Code:
cat /etc/default/wicd
Mine has

START_DAEMON=yes

DAEMON_ARGS=”–keep-connection”
 
Old 11-17-2017, 01:51 AM   #9
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
when wireless connection is established

Quote:
ifconfig -a
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:be:bf:f1:bf txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18

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 340 bytes 27216 (26.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 340 bytes 27216 (26.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.45 netmask 255.255.255.0 broadcast 192.168.1.255
ether 4a:3c:b2:72:0c:5f txqueuelen 1000 (Ethernet)
RX packets 973 bytes 886438 (865.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 840 bytes 108145 (105.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Quote:
dmesg | tail -20
[ 47.342071] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 86.456035] usb 2-1.6: USB disconnect, device number 3
[ 87.954670] usb 2-1.6: new low-speed USB device number 4 using ehci-pci
[ 88.065813] usb 2-1.6: New USB device found, idVendor=04f2, idProduct=0939
[ 88.065897] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 88.065976] usb 2-1.6: Product: USB Optical Mouse
[ 88.066029] usb 2-1.6: Manufacturer: PixArt
[ 88.068753] input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:04F2:0939.0002/input/input15
[ 88.125143] hid-generic 0003:04F2:0939.0002: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1d.0-1.6/input0
[ 148.921631] usb 2-1.6: USB disconnect, device number 4
[ 150.422710] usb 2-1.6: new low-speed USB device number 5 using ehci-pci
[ 150.534950] usb 2-1.6: New USB device found, idVendor=04f2, idProduct=0939
[ 150.535044] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 150.535123] usb 2-1.6: Product: USB Optical Mouse
[ 150.535176] usb 2-1.6: Manufacturer: PixArt
[ 150.538134] input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:04F2:0939.0003/input/input16
[ 150.538990] hid-generic 0003:04F2:0939.0003: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1d.0-1.6/input0
[ 758.042207] perf: interrupt took too long (2514 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 882.608847] perf: interrupt took too long (3156 > 3142), lowering kernel.perf_event_max_sample_rate to 63250
[ 1944.114051] perf: interrupt took too long (3959 > 3945), lowering kernel.perf_event_max_sample_rate to 50500
Quote:
dmesg grep firmware

Usage:
dmesg [options]

Display or control the kernel ring buffer.

Options:
-C, --clear clear the kernel ring buffer
-c, --read-clear read and clear all messages
-D, --console-off disable printing messages to console
-E, --console-on enable printing messages to console
-F, --file <file> use the file instead of the kernel log buffer
-f, --facility <list> restrict output to defined facilities
-H, --human human readable output
-k, --kernel display kernel messages
-L, --color[=<when>] colorize messages (auto, always or never)
colors are enabled by default
-l, --level <list> restrict output to defined levels
-n, --console-level <level> set level of messages printed to console
-P, --nopager do not pipe output into a pager
-r, --raw print the raw message buffer
-S, --syslog force to use syslog(2) rather than /dev/kmsg
-s, --buffer-size <size> buffer size to query the kernel ring buffer
-u, --userspace display userspace messages
-w, --follow wait for new messages
-x, --decode decode facility and level to readable string
-d, --show-delta show time delta between printed messages
-e, --reltime show local time and time delta in readable format
-T, --ctime show human-readable timestamp (may be inaccurate!)
-t, --notime don't show any timestamp with messages
--time-format <format> show timestamp using the given format:
[delta|reltime|ctime|notime|iso]
Suspending/resume will make ctime and iso timestamps inaccurate.

-h, --help display this help and exit
-V, --version output version information and exit

Supported log facilities:
kern - kernel messages
user - random user-level messages
mail - mail system
daemon - system daemons
auth - security/authorization messages
syslog - messages generated internally by syslogd
lpr - line printer subsystem
news - network news subsystem

Supported log levels (priorities):
emerg - system is unusable
alert - action must be taken immediately
crit - critical conditions
err - error conditions
warn - warning conditions
notice - normal but significant condition
info - informational
debug - debug-level messages
Quote:
cat /etc/default/wicd
# Start the daemon by default, let the user disable it.
# Use "no" (without quotes) to make /etc/init.d/wicd *NOT* start the WICD daemon.
START_DAEMON=yes

# By default don't kill connections on daemon shutdown, see
# https://bugs.debian.org/816076 and
# https://bazaar.launchpad.net/~wicd-d...l/revision/851
DAEMON_ARGS="--keep-connection"
 
Old 11-17-2017, 10:42 AM   #10
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Quote:
dmesg grep firmware
You left out the pipe symbol in that command.

Anyways. Everything looks like it is good to me. I suspect your problem lies between your Zyxel router and your Internet Provider Servers that get you on the net.

I run into this from time time myself. Usually resetting my router and running wicd again fixes this. I am not sure if it is my router starting to fail because it is years old or my crappy ISP provider server is dropping out for what ever reason.

Like I said. A short walk. Unplug my router for 10 seconds. Plug it back in. Usually fixes this for me. Unless somebody ran into a telephone pole or my ISP is down for scheduled maintenance.

Living in the boon docks. I live with compromises.
 
Old 11-17-2017, 12:55 PM   #11
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
Last October in Austria I had a wireless-only router of unknown brand, got from the Internet provider. Never a failure to establish wireless connection with my vaio. That points to your suspicion about Zyxel-Italian provider. Switching off both Zyxel and vaio, and restarting them in the given order, wireless connection was established:

Quote:
dmesg | tail -20
[ 34.431246] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 34.447369] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 34.456430] NET: Registered protocol family 3
[ 34.470705] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 34.492973] NET: Registered protocol family 5
[ 34.929674] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 41.676632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 41.881467] sky2 0000:04:00.0 eth0: disabling interface
[ 41.890446] sky2 0000:04:00.0 eth0: enabling interface
[ 41.891207] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 42.087963] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 45.277117] wlan0: authenticate with 00:13:49:a3:15:37
[ 45.296827] wlan0: send auth to 00:13:49:a3:15:37 (try 1/3)
[ 45.298495] wlan0: authenticated
[ 45.298560] ath9k 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 45.298627] ath9k 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 45.300606] wlan0: associate with 00:13:49:a3:15:37 (try 1/3)
[ 45.303287] wlan0: RX AssocResp from 00:13:49:a3:15:37 (capab=0x471 status=0 aid=2)
[ 45.303518] wlan0: associated
[ 45.303560] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Switching off vaio only, and restarting it, no wireless connection:

Quote:
dmesg | tail -20
[ 122.243018] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 129.217968] wlan0: deauthenticating from 00:13:49:a3:15:37 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 129.251550] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 130.611237] sky2 0000:04:00.0 eth0: disabling interface
[ 130.618557] sky2 0000:04:00.0 eth0: enabling interface
[ 130.619137] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 131.173575] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 132.510881] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 133.230376] sky2 0000:04:00.0 eth0: disabling interface
[ 133.238724] sky2 0000:04:00.0 eth0: enabling interface
[ 133.239301] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 133.360262] wlan0: authenticate with 00:13:49:a3:15:37
[ 133.373834] wlan0: send auth to 00:13:49:a3:15:37 (try 1/3)
[ 133.375677] wlan0: authenticated
[ 133.375710] ath9k 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 133.375714] ath9k 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 133.379897] wlan0: associate with 00:13:49:a3:15:37 (try 1/3)
[ 133.382492] wlan0: RX AssocResp from 00:13:49:a3:15:37 (capab=0x471 status=0 aid=2)
[ 133.382663] wlan0: associated
[ 133.382719] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Restarting the router was no cure, however there must be something wrong with my Zyxel-Provider.
 
Old 11-17-2017, 01:01 PM   #12
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
However, I forgot to mention that my Lenny3 smart-phone with Android 6.0, never had problems with my Zyxel.
 
Old 11-17-2017, 07:12 PM   #13
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 5,903
Blog Entries: 21

Rep: Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958Reputation: 2958
Quote:
However, I forgot to mention that my Lenny3 smart-phone with Android 6.0, never had problems with my Zyxel.
I know you said re-starting the vaio don't help plus restarting the router don't help. But then re-setting both at once does.

But. My next trouble shooting step if this was my gear would be to suspect the wireless card is getting hot in the vaio and dropping out. Then after it cools off. It connects again. I've seen this before on older gear also. Vaio might need cleaning with can of compressed air.

I don't think you have a wicd problem . I could be wrong. But we covered a lot of commands and text files. Things look OK to me as far as how wicd is working, and, ath9k driver has a good track record also.

Last edited by rokytnji; 11-17-2017 at 07:14 PM.
 
Old 11-18-2017, 10:11 AM   #14
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
Cleaning my vintage vaio laptop from dust is a good idea. An additional move I am thinking about is updating the firmware (currently V3.40 (AGL3 of 05/29/2001), available V3.40 (AGL10 of 03/04/2013). Delayed to after the week end, when shops are open. Updating the modem is nonsense here in Italy, as we are at the copper age. Luckily my vaio only serves to access the login nodes of a NextScale.
chiendarret
Beer entails a lot of sucrose, far beyond the need, but beer+much bike may be OK.
 
Old 11-20-2017, 03:34 AM   #15
chiendarret
Member
 
Registered: Mar 2007
Posts: 245

Original Poster
Rep: Reputation: 16
You were right: cleaning vaio from dust let it access wireless consistently. Now vaio operates without previous noise and heating. Thanks. This is not saying that vaio-Zyxel are in optimal conditions, however. For example:

Quote:
dmesg | grep -i cpus
[ 0.556415] mtrr: your CPUs had inconsistent variable MTRR settings
[ 0.556499] mtrr: probably your BIOS does not setup all CPUs.
however,

Quote:
lscpu
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
Model name: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
which, in my opinion, means that BIOS should be updated. Something I have no experience with.

Also, as I wrote, Zyxel's firmware is 16 years old, while a 2013 edition is available. This should be easy to update. Well, this is a vintage notebook from a company that stopped doing PCs. I got it for an ice-cream from people that found it unmanageably slow with recent microsoft software. With amd64 it does what a i3 CPU can do, surely not my computations, but fast enough to access a NextScale, also for remote visualization, or getting Lucio Dalla's Canzone from youtube. If anything, I don't like working without mirror raid, as with vaio, under the prospect that should the single HD get stopped, the OS should be reinstalled.

chiendarret
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
WICD wireless client myselfdeepakvasisht Linux - Software 3 10-21-2010 01:03 AM
Need help getting WICD to work with wireless. Barnaby Slackware 16 03-20-2010 08:13 AM
Do I need rc.inet[d,1,2], rc.pcmcia, & rc.wireless at boot if I use wicd w/wireless? agi93 Slackware 6 01-03-2010 08:07 AM
[SOLVED] Atheros Wireless and WICD tronayne Slackware 8 12-24-2009 10:01 AM
Wicd / wireless can't get IP address Innervision Slackware 23 06-05-2009 12:29 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 07:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration