LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 11-21-2009, 04:04 AM   #61
Johnnie.it
Member
 
Registered: Nov 2009
Posts: 32

Original Poster
Rep: Reputation: 15

Update: it happened again, and this time not even modprobe iwlagn was able to bring it up again
 
Old 11-21-2009, 08:33 AM   #62
Johnnie.it
Member
 
Registered: Nov 2009
Posts: 32

Original Poster
Rep: Reputation: 15
happened again; from kern.log:
Code:
Nov 21 14:41:18 localhost kernel: [13772.024263] wlan0: no probe response from AP 00:17:33:9b:de:85 - disassociating
so I unloaded unloaded the driver: sudo modprobe -r iwlagn, and kern.log registered:
Code:
Nov 21 14:45:58 localhost kernel: [14052.379310] iwlagn 0000:0b:00.0: PCI INT A disabled
after a few seconds I reenabled it: sudo modprobe iwlagn, and on kern.log:
Code:
Nov 21 14:46:23 localhost kernel: [14076.606540] cfg80211: Calling CRDA to update world regulatory domain
Nov 21 14:46:23 localhost kernel: [14076.733906] cfg80211: World regulatory domain updated:
Nov 21 14:46:23 localhost kernel: [14076.733910] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 21 14:46:23 localhost kernel: [14076.733913] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 21 14:46:23 localhost kernel: [14076.733915] 	(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 21 14:46:23 localhost kernel: [14076.733917] 	(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 21 14:46:23 localhost kernel: [14076.733920] 	(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 21 14:46:23 localhost kernel: [14076.733922] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 21 14:46:23 localhost kernel: [14076.794682] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27k
Nov 21 14:46:23 localhost kernel: [14076.794686] iwlagn: Copyright(c) 2003-2009 Intel Corporation
Nov 21 14:46:23 localhost kernel: [14076.794793] iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Nov 21 14:46:23 localhost kernel: [14076.794839] iwlagn 0000:0b:00.0: setting latency timer to 64
Nov 21 14:46:23 localhost kernel: [14076.794918] iwlagn 0000:0b:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
Nov 21 14:46:23 localhost kernel: [14076.846332] iwlagn 0000:0b:00.0: Tunable channels: 13 802.11bg, 19 802.11a channels
Nov 21 14:46:23 localhost kernel: [14076.846426] iwlagn 0000:0b:00.0: irq 30 for MSI/MSI-X
Nov 21 14:46:23 localhost kernel: [14076.847473] phy0: Selected rate control algorithm 'iwl-agn-rs'
After a few more seconds I threw in a sudo ifup wlan0:
Code:
Nov 21 14:48:42 localhost kernel: [14216.265138] iwlagn 0000:0b:00.0: firmware: requesting iwlwifi-4965-2.ucode
Nov 21 14:48:42 localhost kernel: [14216.330576] iwlagn 0000:0b:00.0: loaded firmware version 228.61.2.24
Nov 21 14:48:42 localhost kernel: [14216.556099] Registered led device: iwl-phy0::radio
Nov 21 14:48:42 localhost kernel: [14216.556131] Registered led device: iwl-phy0::assoc
Nov 21 14:48:42 localhost kernel: [14216.556162] Registered led device: iwl-phy0::RX
Nov 21 14:48:42 localhost kernel: [14216.556187] Registered led device: iwl-phy0::TX
Nov 21 14:48:43 localhost kernel: [14216.612369] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 21 14:48:45 localhost kernel: [14218.796791] wlan0: authenticate with AP 00:17:33:9b:de:85
Nov 21 14:48:45 localhost kernel: [14218.800142] wlan0: authenticated
Nov 21 14:48:45 localhost kernel: [14218.800145] wlan0: associate with AP 00:17:33:9b:de:85
Nov 21 14:48:45 localhost kernel: [14218.802412] wlan0: RX AssocResp from 00:17:33:9b:de:85 (capab=0x401 status=0 aid=1)
Nov 21 14:48:45 localhost kernel: [14218.802417] wlan0: associated
Nov 21 14:48:45 localhost kernel: [14218.825880] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 21 14:48:57 localhost kernel: [14229.400039] wlan0: no IPv6 routers present
repeat:
Nov 21 14:48:45 localhost kernel: [14218.825880] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Network is up again, no touching wicd needed.

On the other end, wicd.log reports:
Code:
2009/11/21 14:45:59 :: iwconfig wlan0
wlan0     No such device

2009/11/21 14:45:59 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:45:59 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:45:59 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:45:59 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:45:59 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:45:59 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:46:03 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 14:46:03 :: Autoconnecting...
2009/11/21 14:46:03 :: Starting wireless autoconnect...
2009/11/21 14:46:03 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/21 14:46:03 :: scanning start
2009/11/21 14:46:03 :: ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
2009/11/21 14:46:03 :: iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

2009/11/21 14:46:03 :: scanning done
2009/11/21 14:46:03 :: found 0 networks:
2009/11/21 14:46:03 :: Unable to autoconnect, you'll have to manually connect
2009/11/21 14:46:03 :: iwconfig wlan0
wlan0     No such device

2009/11/21 14:46:03 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:46:07 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 14:46:07 :: Autoconnecting...
2009/11/21 14:46:07 :: Starting wireless autoconnect...
2009/11/21 14:46:07 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/21 14:46:07 :: scanning start
2009/11/21 14:46:07 :: ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
2009/11/21 14:46:07 :: iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

2009/11/21 14:46:07 :: scanning done
2009/11/21 14:46:07 :: found 0 networks:
2009/11/21 14:46:07 :: Unable to autoconnect, you'll have to manually connect
2009/11/21 14:46:07 :: iwconfig wlan0
wlan0     No such device

2009/11/21 14:46:07 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:46:11 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 14:46:11 :: Autoconnecting...
2009/11/21 14:46:11 :: Starting wireless autoconnect...
2009/11/21 14:46:11 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/21 14:46:11 :: scanning start
2009/11/21 14:46:11 :: ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
2009/11/21 14:46:11 :: iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

2009/11/21 14:46:11 :: scanning done
2009/11/21 14:46:11 :: found 0 networks:
2009/11/21 14:46:11 :: Unable to autoconnect, you'll have to manually connect
2009/11/21 14:46:11 :: iwconfig wlan0
wlan0     No such device

2009/11/21 14:46:11 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:46:15 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 14:46:15 :: Autoconnecting...
2009/11/21 14:46:15 :: Starting wireless autoconnect...
2009/11/21 14:46:15 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/21 14:46:15 :: scanning start
2009/11/21 14:46:15 :: ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
2009/11/21 14:46:15 :: iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

2009/11/21 14:46:15 :: scanning done
2009/11/21 14:46:15 :: found 0 networks:
2009/11/21 14:46:15 :: Unable to autoconnect, you'll have to manually connect
2009/11/21 14:46:15 :: iwconfig wlan0
wlan0     No such device

2009/11/21 14:46:15 :: SIOCGIWAP failed: [Errno 19] No such device
2009/11/21 14:48:43 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 14:48:48 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 14:48:53 :: GetCurrentNetworkID: Returning -1, current network not found

****about 500 identical lines in between****

2009/11/21 15:22:01 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 15:22:05 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 15:22:09 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 15:22:12 :: scanning start
2009/11/21 15:22:12 :: ifconfig wlan0 up
2009/11/21 15:22:12 :: iwlist wlan0 scan
2009/11/21 15:22:13 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 15:22:14 :: GetCurrentNetworkID: Returning -1, current network not found
2009/11/21 15:22:15 :: scan already in progress, skipping
2009/11/21 15:22:15 :: scanning done
2009/11/21 15:22:15 :: found 3 networks:
2009/11/21 15:22:15 :: found afterscript in configuration None
2009/11/21 15:22:15 :: found postdisconnectscript in configuration None
2009/11/21 15:22:15 :: found dns_domain in configuration None
2009/11/21 15:22:15 :: found gateway in configuration 192.168.1.1
2009/11/21 15:22:15 :: found use_global_dns in configuration 0
2009/11/21 15:22:15 :: found ip in configuration 192.168.1.99
2009/11/21 15:22:15 :: found beforescript in configuration None
2009/11/21 15:22:15 :: found psk in configuration xyz
2009/11/21 15:22:15 :: found netmask in configuration 255.255.255.0
2009/11/21 15:22:15 :: found key in configuration pwd
2009/11/21 15:22:15 :: found predisconnectscript in configuration None
2009/11/21 15:22:15 :: found enctype in configuration None
2009/11/21 15:22:15 :: found dns3 in configuration None
2009/11/21 15:22:15 :: found dns2 in configuration 80.118.196.36
2009/11/21 15:22:15 :: found dns1 in configuration 80.118.192.100
2009/11/21 15:22:15 :: found use_settings_globally in configuration 0
2009/11/21 15:22:15 :: found use_static_dns in configuration 1
2009/11/21 15:22:15 :: found apsk in configuration pwd
2009/11/21 15:22:15 :: found encryption_method in configuration WPA
2009/11/21 15:22:15 :: found automatic in configuration True
2009/11/21 15:22:15 :: found search_domain in configuration None
2009/11/21 15:22:16 :: scanning start
2009/11/21 15:22:16 :: ifconfig wlan0 up
2009/11/21 15:22:16 :: iwlist wlan0 scan
2009/11/21 15:22:16 :: scanning done
2009/11/21 15:22:16 :: found 3 networks:
2009/11/21 15:22:16 :: found afterscript in configuration None
2009/11/21 15:22:16 :: found postdisconnectscript in configuration None
2009/11/21 15:22:16 :: found dns_domain in configuration None
2009/11/21 15:22:16 :: found gateway in configuration 192.168.1.1
2009/11/21 15:22:16 :: found use_global_dns in configuration 0
2009/11/21 15:22:16 :: found ip in configuration 192.168.1.99
2009/11/21 15:22:16 :: found beforescript in configuration None
2009/11/21 15:22:16 :: found psk in configuration xyz
2009/11/21 15:22:16 :: found netmask in configuration 255.255.255.0
2009/11/21 15:22:16 :: found key in configuration pwd
2009/11/21 15:22:16 :: found predisconnectscript in configuration None
2009/11/21 15:22:16 :: found enctype in configuration None
2009/11/21 15:22:16 :: found dns3 in configuration None
2009/11/21 15:22:16 :: found dns2 in configuration 80.118.196.36
2009/11/21 15:22:16 :: found dns1 in configuration 80.118.192.100
2009/11/21 15:22:16 :: found use_settings_globally in configuration 0
2009/11/21 15:22:16 :: found use_static_dns in configuration 1
2009/11/21 15:22:16 :: found apsk in configuration pwd
2009/11/21 15:22:16 :: found encryption_method in configuration WPA
2009/11/21 15:22:16 :: found automatic in configuration True
2009/11/21 15:22:16 :: found search_domain in configuration None
What's wrong with it now???


Anyway, I found several similar bugs filed on http://bugzilla.intellinuxwireless.org/ as well as https://bugs.launchpad.net/dell/ and https://bugs.launchpad.net/ubuntu/
Though similar, most are different in many subtle ways.
Those I "recognized" myself into were actually drivers/bios/acpi issues, where the system could not properly use the drivers to wake up again the device, due to either a drivers problem or a "misunderstanding" between the drivers and the bios' acpi features.
The fact that it actually happens on dell as well as ibm, acer and other machines suggests me that it's not a bios-only issue, but rather how the drivers manage this apci thinghy.

Last edited by Johnnie.it; 11-21-2009 at 08:38 AM.
 
Old 11-21-2009, 10:41 AM   #63
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
I suggest you to read about APIC, and possibility to disable it through 2 command in GRAB - noapic and nolapic.
I use it.

But you have o be prepared, if you won't be able to boot, or something goes wrong with hardware you will need a lifeCD, to boot from it, and remove noapic nolapic fron GRAB settings.

I really believe that there is only 16 IRQ, other is not real.
 
Old 11-21-2009, 10:45 AM   #64
minrich
Member
 
Registered: Aug 2003
Location: Isles of Man & Wight
Distribution: See signature
Posts: 548

Rep: Reputation: 40
I looks to as though the sudo ifup wlan0 reconnected at 14:48:45, but according to the wicd.log, wicd was unable to GetCurrentNetworkID (whatever that is) and the devilish scanning started at 15:22:12 - what is triggering this?

Your first clip from kern.log at 14:42:18 definitely tells why your wlan0 is disassociating -No probe response from your AP. It is unfortunate that you don't have a windows box that you can run Netstumbler on - it produces a graph of each and every channel and access point in my neighbourhood and I can say that nearly all of them intermittantly 'flat-line' from milli-seconds up to 3-4 seconds, however if I am already online (logged in) my connection does not go down - but I am not using any network manager nor am I using any encryption which would entail wpa_supplicant running (I think you confirmed that you are currently running unencrypted while we try to sort your problem). Just to be sure could you run: ps aux | grep wpa
If it returns anything other than the process run by that command line then your wpa_supplicant is still running.

maybe nimnull2 knows whether wicd runs any scans if a connection is still functioning, because I don't have any experience.

I wouldn't worry yourself about bios issues - from my understanding the linux kernel might take hints from bios when starting up but thereafter the kernel does its own thing, and acpi and hald and udev takeover determination of what exists on your system.

I wonder - do you have a Knoppix 5.1 disk? If so, then you can test your wireless without affecting your karmic install. If not, download the iso immediately and burn it to a cd - it is staggeringly brilliant at determining if something is not working on a windows or linux box. I don't know how recent your computer is, nor how recent the iwlagn driver is and whether it is included in Knoppix 5.1 but if necessary I can give you instructions on how to mount your karmic partition - although I have never tried with an ext4 partition if that is what your karmic is using.

Hope this helps.
 
Old 11-22-2009, 05:19 AM   #65
Johnnie.it
Member
 
Registered: Nov 2009
Posts: 32

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by nimnull22 View Post
I suggest you to read about APIC, and possibility to disable it through 2 command in GRAB - noapic and nolapic.
I use it.

But you have o be prepared, if you won't be able to boot, or something goes wrong with hardware you will need a lifeCD, to boot from it, and remove noapic nolapic fron GRAB settings.

I really believe that there is only 16 IRQ, other is not real.
I've already used the "noapic" kernel boot parameter; other people are complaining about the keyboard and touchpad behaving strangely under certain BIOS revision, so I wanted to know first where I was throwing myself into...

Quote:
Originally Posted by minrich View Post
I looks to as though the sudo ifup wlan0 reconnected at 14:48:45, but according to the wicd.log, wicd was unable to GetCurrentNetworkID (whatever that is) and the devilish scanning started at 15:22:12 - what is triggering this?
wicd did not log the reconnection altogether...and that's normal, I think, since it never did anything to get reconnected.
While I was writing my last post, however, I found the network to be unavailable again. While trying to understand what the hell was going on, it came up again by itself.
It's like it went sleeping by inactivity and took a while (like, 10-20 secs) to come back up.
Don't ask me why though. Since then, I have to add, It's working constantly, but it's rather sluggish on latency, especially on dns lookups and first connection to a website (you know, "waiting for an answer from www.linuxquestions.org...").
I didn't reboot yet, I might add.

Quote:
Originally Posted by minrich View Post
Your first clip from kern.log at 14:42:18 definitely tells why your wlan0 is disassociating -No probe response from your AP. It is unfortunate that you don't have a windows box that you can run Netstumbler on
Well I don't have ANOTHER windows box but I do have a windows installation on this machine, though it's a hellish vista upgrade to seven (which actually changed only the startup splash screen...weird) and I didn't boot it up since like 3 or more months...

Quote:
Originally Posted by minrich View Post
Just to be sure could you run: ps aux | grep wpa
If it returns anything other than the process run by that command line then your wpa_supplicant is still running.
Done:
Code:
johnnie@johnnie-xps:~$ ps aux | grep wpa
johnnie   8076  0.0  0.0   3052   800 pts/0    R+   11:59   0:00 grep wpa
johnnie@johnnie-xps:~$
Though I suppose I'd have to check when the network goes down...

Quote:
Originally Posted by minrich View Post
I wouldn't worry yourself about bios issues - from my understanding the linux kernel might take hints from bios when starting up but thereafter the kernel does its own thing, and acpi and hald and udev takeover determination of what exists on your system.
Look, it's not me making things up.
It's engineers from intel and dell saying, so. I'd think they know their trade...

Quote:
Originally Posted by minrich View Post
I wonder - do you have a Knoppix 5.1 disk? If so, then you can test your wireless without affecting your karmic install. If not, download the iso immediately and burn it to a cd - it is staggeringly brilliant at determining if something is not working on a windows or linux box. I don't know how recent your computer is, nor how recent the iwlagn driver is and whether it is included in Knoppix 5.1 but if necessary I can give you instructions on how to mount your karmic partition - although I have never tried with an ext4 partition if that is what your karmic is using.
Sure I can download it right away.
My computer is like 18 months old (it should have learned to walk alone by now :P) and AFAIK I'm using standard iwlwifi drivers included in kernels since 2.6.19 (actually using 2.6.31-14 generic).
Latest kernels also should have built-in ext4 support.
Oh well, I suppose I'll give it a try...
 
Old 11-22-2009, 08:51 AM   #66
minrich
Member
 
Registered: Aug 2003
Location: Isles of Man & Wight
Distribution: See signature
Posts: 548

Rep: Reputation: 40
johnnie.it

Very nice presentation in your last post. Obviously, you wpa_supplicant isn't running, and therefore it is not causing the scanning that starts when you lose your connection - I would have thought that it must be wicd, but I am glad to hear that it got itself up again on it's own - so I suggest that we leave it for the moment.

On the issue of the Knoppix disk, I have been unsucessful in my googling and searching on the knoppix.net site to see if the recently released Knoppix 6.2 (Nov. 18th) will mount ext4 filesystems - but it may not be an issue with your iwlagn driver. I have just finished downloading the CD - not the ADRIANE option which is for the visually impaired - interestingly this 6.2 version has dropped gnome and/or KDE desktop inclusion. Anyway when I have burnt it, I will report back.
 
Old 11-22-2009, 11:32 AM   #67
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
Originally Posted by Johnnie.it


johnnie@johnnie-xps:~$ lspci -vv -s 0b:00.0
...
Kernel driver in use: iwlagn
Kernel modules: iwlagn


According to that page http://wiki.debian.org/iwlwifi,

I suggest you to check if you have iwl4965 driver, and if you have it, you can try it.

Simply modprobe -r iwlagn, and then modprobe iwl4965,

Check daemon log after.
 
Old 11-24-2009, 08:41 AM   #68
esenoy
LQ Newbie
 
Registered: Nov 2009
Posts: 1

Rep: Reputation: 0
Solved (at the moment)

Hello,
I had the same problem, with a RT-61 PCI card, it stopped working randomly.

Something in the ifconfig output called my attention, 2 wlan0 devices, one of them managed by avahi. So I've uninstalled the avahi daemon, and everything is working fine now (but I'm a novice user, and don't know why, sorry).

Hope it helps, it worked for me... 2 days without connection losses.

Tell me if you want logs, and I'll post it here.
 
Old 02-23-2010, 07:37 AM   #69
amanica
LQ Newbie
 
Registered: Dec 2009
Location: Roodepoort, South-Africa
Distribution: Kubuntu 9.10
Posts: 2

Rep: Reputation: 0
Talking reloading the module helped me

Quote:
Originally Posted by nimnull22 View Post
...
In my OpenSuse I can simply type:
modprobe -r 8139too (8139too - this is my ethernet driver, wireless should be the same)
and unload driver, so ethernert stops, then as well simply, I type
modprobe 8139too
...
my wirless network also fails to reconnect about once a week,
but the following worked for me:
rmmod iwlagn
modprobe iwlagn

thanks!
 
  


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
UBUNTU Karmic don't work with SITECOM Wireless 300N USB Adapter (WL-577)? maiden2 Linux - Networking 1 10-14-2009 07:01 PM
Wireless - Domain Name Servers Disappearing johnaaronrose Linux - Laptop and Netbook 1 07-13-2008 09:40 AM
Disappearing Bcm43xx Wireless integrated card B4lulu Linux - Hardware 0 09-25-2007 09:46 PM
Wireless Card Disappearing ekimyerac Debian 0 07-24-2006 10:41 AM
Mandrake 10 and network disappearing for no reason esteeven Linux - Networking 21 09-15-2004 03:04 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 02:30 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
Open Source Consulting | Domain Registration