**** BEGIN LOGGING AT Wed Feb 20 02:59:58 2013 Feb 20 19:52:09 how's the progress of the N800 port? Feb 20 21:17:43 I'm officially impressed; wireless worked the first try without chicken sacrifices or custom firmware. Feb 20 21:17:59 for me on linux it's been like that for years Feb 20 21:18:17 Ah, but I only get garbage hardware :p Feb 20 21:18:31 ...even my ancient prism2_usb devices (all my wireless adapters I have lying around, 802.11b :( ) work fine Feb 20 21:18:35 this is a wireless one that won't even work in windows Feb 20 21:18:58 but anyway. It works great when I do 'ifup wlan0', but it doesn't run itself on boot. How do I nudge that? Feb 20 21:19:19 It's already in /etc/network/interfaces, wpa_supplicant gets along with it, etc. Just doesn't start itself. Feb 20 21:22:25 Hm. 'auto wlan0' might do it. Feb 20 21:27:14 Well that's interesting. That causes it to connect flawlessly on boot, then turn itself off a minute or so later. Feb 20 21:30:23 what device are you using? Feb 20 21:33:25 The system is a beagleboard, using the card that came with it updated to modern angstrom. The wireless device is a Belkin F5D7050 of such lineage even Belkin doesn't support it but nonetheless works. Feb 20 21:36:10 It's not like the card stopped communicating of its own accord, though. wirelessmanager got it up and running first, then it finished booting, then it lost its IP address. iwconfig still showed it as associated. If I put in its IP again with ifconfig it works. Something just decides to give up. Feb 20 21:40:51 Perhaps the GUI is trying to take over. I'll disable it from boot. Feb 20 21:41:21 belkin support is terrible Feb 20 21:41:45 have an old F5D2000 (or was it F2D5000?) ethernet card and its support is terrible Feb 20 21:41:47 It is indeed. The thing is, this is actually working. It's not the driver that's confusing me for a change :p Feb 20 21:42:05 all the drivers didn't work, support for various OSes is spotty... Feb 20 21:42:14 * ampharos wishes he could find a stack of RTL8139s Feb 20 21:43:29 Those were nice. Feb 20 21:44:24 almost anything from the late 90s support them Feb 20 21:45:35 it's nice to have an old PC that has really standard components and a nice BIOS Feb 20 21:45:58 the problem with late 90s syystems is strange HW and spotty BIOSes that never work with any HD Feb 20 21:46:26 i have a good system, works with almost any OS I throw at it (wish Linux would support 3D accel on it without having to use Arch) Feb 20 21:47:15 I've got a stack of compaq Pentium II pizzabox computers I use as remote serverers in remote boxes. Those things are almost indestructible. They don't even have a power-on-after-power-failure setting in the CMOS -- they have a **SWITCH** to do that. So they can't decide "No, I don't feel like working today, I forgot I was supposed to turn on". Feb 20 21:49:00 P3 forever - bring back slotloaders! Feb 20 21:49:23 the boards and BIOSes of the P3 era can be either good or brain damaged Feb 20 21:52:13 Hmm, so here we go again, connected and associated, gets an IP, then gives up. Feb 20 21:54:08 I can understand it not using wireless by default... but to connect then give up? I don't get it. Feb 20 21:58:36 Not even if I disconnect the ethernet cable before booting it will it continue using the wireless. Feb 20 22:29:16 Hello. Feb 21 00:44:25 Figured it out. networkmanager was fighting it. Thought I needed it for /etc/network/interfaces, but disable it and it works great. **** ENDING LOGGING AT Thu Feb 21 02:59:59 2013