This is the first "blog" of any kind I've ever had, so it's probably not the greatest...
Just a little snippet about me:
I'd like to consider myself relatively tech-savvy; obviously I use Linux (Arch to be precise; K.I.S.S. FTW), and I enjoy learning new things about computers in general (both software and hardware-related).
This blog is mostly just for whenever I feel like telling the world about my experiences with computers/Linux (or just life in general), or just posting for the hell of it.
Just a little snippet about me:
I'd like to consider myself relatively tech-savvy; obviously I use Linux (Arch to be precise; K.I.S.S. FTW), and I enjoy learning new things about computers in general (both software and hardware-related).
This blog is mostly just for whenever I feel like telling the world about my experiences with computers/Linux (or just life in general), or just posting for the hell of it.
Desktop wireless
Moving away from the general theme of depression and existential angst, I'd like to report a (however partial) small success: I'm posting this from my desktop computer, without the need for it to "piggy-back" on my laptop's wireless connection. 
There's a slight catch, though: I'm having to do it roughly the same way I did it on Ubuntu: install ndiswrapper, set up the Windows driver for my Netgear WN111 USB wireless dongle through ndiswrapper, and hope for the best. It does associate successfully each time, but I can only get an IP address via DHCP after several attempts, and setting the IP manually doesn't work.
(Luckily I have a couple shell scripts for easily connecting/disconnecting that are identical on both the lappy and the desktop)
I have another wireless dongle (A D-Link DWA-130) that has a native Linux driver, but a) it has pretty much the same problem as the Netgear adapter WRT getting an IP (it takes a few tries), and b) after it does connect, the system locks up completely after an unspecified amount of time (I'd guess about 10-15 minutes, or something like that; I didn't time it exactly).
Another thing is that I have to keep the connection "alive" by sending a constant ping out every few seconds or so (I have it do ping -i 10 xkcd.com), otherwise it drops it. It was the same way under Ubuntu. I'm guessing this is a problem with the ndiswrapper driver (or more likely the actual NDIS Windows driver that it's using
), since it appears to be cross-distro.
Well, at least I can get this machine online without having to rely on a crossover cable and my laptop...I can put the lappy to sleep and save a little energy!
There's a slight catch, though: I'm having to do it roughly the same way I did it on Ubuntu: install ndiswrapper, set up the Windows driver for my Netgear WN111 USB wireless dongle through ndiswrapper, and hope for the best. It does associate successfully each time, but I can only get an IP address via DHCP after several attempts, and setting the IP manually doesn't work.
(Luckily I have a couple shell scripts for easily connecting/disconnecting that are identical on both the lappy and the desktop)I have another wireless dongle (A D-Link DWA-130) that has a native Linux driver, but a) it has pretty much the same problem as the Netgear adapter WRT getting an IP (it takes a few tries), and b) after it does connect, the system locks up completely after an unspecified amount of time (I'd guess about 10-15 minutes, or something like that; I didn't time it exactly).
Another thing is that I have to keep the connection "alive" by sending a constant ping out every few seconds or so (I have it do ping -i 10 xkcd.com), otherwise it drops it. It was the same way under Ubuntu. I'm guessing this is a problem with the ndiswrapper driver (or more likely the actual NDIS Windows driver that it's using
), since it appears to be cross-distro.Well, at least I can get this machine online without having to rely on a crossover cable and my laptop...I can put the lappy to sleep and save a little energy!
Total Comments 5
Comments
-
Good job!Posted 12-22-2010 at 08:36 PM by lupusarcanus 
-
Hooray!!! Thank **** for that!Quote:Moving away from the general theme of depression and existential angst
Posted 12-23-2010 at 06:52 AM by brianL
-
Quote:Hooray!!! Thank **** for that!
Yeah, don't get the impression that I'm always depressed from those postings. It's just that when I get all existential and start thinking about free will vs. determinism-related whatnot, this is the only place I feel comfortable "venting". I'll try to keep that more "in check" from now on, though; maybe I'll start "venting" by writing local documents (i.e. saved on my HDD, not posted online), so that nobody has to see my rantings. I know now that nobody wants to read it anymore.Posted 12-23-2010 at 08:30 PM by MrCode
-
it may be a little more considerait to ping your own network ip address. either way, it's odd that the windows/ndis driver doesn't work properly.
Posted 12-25-2010 at 10:40 PM by lumak
-
Yeah, I have it ping the router now instead of xkcd.com.Quote:it may be a little more considerait to ping your own network ip address.
I was mostly talking about that particular instance when I wrote this blog entry. I use xkcd.com as a test ping to see if I have internet connectivity, so I used it at first out of habit, but now I use the home router to keep the connection alive.Posted 12-26-2010 at 09:30 AM by MrCode
