[06:46] <calc> BenC: looks like tribe2 doesn't work for me for 3945 but i think it might be network manager at fault, can't really tell for certain
[06:46] <calc> BenC: it can see both wireless ap's at my house but can't connect properly to either
[06:48] <calc> BenC: guess i'll have to stick to feisty until the sprint and get someone to take a look at the gutsy on my box
[06:48] <crimsun> I'd try the interfaces(5) mode of wpasupplicant.
[06:49] <crimsun> /usr/share/doc/wpasupplicant/README.modes.gz
[06:49] <crimsun> iface eth0 inet dhcp
[06:49] <crimsun>     wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
[06:49] <crimsun> etc.
[06:50] <crimsun> then scrap NM temporarily, and test the "normal" if{up,down} methods.
[06:50] <calc> crimsun: whats really odd is it sees the network can tell one is protected and one is not, tries to connect brings up the iface (seen in ifconfig) but doesn't get an address
[06:50] <calc> i'll see if i can do all that via the boot cd, i dont really want to do an install then have to reinstall feisty again
[06:51] <calc> bbiab, laptop is in other room
[07:04] <calc> crimsun: ok
[07:05] <calc> crimsun: i set wpa-driver wext and wpa-ssid myssid
[07:05] <calc> eg:
[07:05] <calc> iface eth3 inet dhcp
[07:05] <calc>   wpa-driver wext
[07:05] <calc>   wpa-ssid foo
[07:05] <calc> then ifup eth3
[07:05] <calc> and it tries to get a dhcp address but can't
[07:05] <calc> works perfect with network manager on feisty
[07:06] <crimsun> you'd have to use wpa_cli to set the PSK or whatnot, then.
[07:06] <crimsun> I prefer to use /etc/wpa_supplicant/wpa_supplicant.conf
[07:06] <calc> i have no security on the AP
[07:06] <calc> its wide open
[07:06] <crimsun> oh, wide open?  Hmm.  What's in dmesg?
[07:06] <calc> not much
[07:06] <calc> iwconfig can see the ap from what i can tell
[07:07] <calc> i ran iwconfig eth3 ssid foo and it associated with it
[07:07] <calc> i haven't tried running the dhclient against the eth3 directly bypassing ifup yet
[07:08] <crimsun> worth a try
[07:08] <calc> bbiab
[07:11] <calc> ok i got it to work
[07:11] <calc> so WTF?
[07:12] <calc> ifupdown is broken or something?
[07:12] <calc> that is insane
[07:12] <calc> if i ifup eth3 it can't get an address with dhclient
[07:12] <calc> or dhclient3 not sure which it is running on the cd
[07:12] <calc> if i run dhclient eth3 it works
[07:13] <calc> at least i know how to get by making it work for now
[07:13] <calc> but what could be wrong with ifup that causes it not to get an address using the same dhclient
[07:14] <calc> dhclient and dhclient3 on the cd both worked fine so it can't be a bad binary (afaict anyway)
[07:29] <calc> crimsun: any ideas?
[07:29] <crimsun> (sorry, switching buffers)
[07:31] <crimsun> if it's an open AP, you could just skip wpasupplicant completely.  I was under the impression you're on a "secured" net.
[07:32] <crimsun> (/usr/share/doc/wireless-tools/README.Debian)
[07:34] <calc> crimsun: ah so i am skipping wpa i forgot about that
[07:34] <calc> so it could be wpa that is broken for my machine
[07:35] <calc> and that was a new upload of wpa in mid june
[07:35] <calc> so i should try downgrading if i can once i install gutsy and see if that fixes the issue
[07:36] <calc> well and a new kernel as well
[07:36] <calc> so it could either be the kernel and wpa no longer get along or something in wpa is just off vs the old version
[09:05] <kraut> moin
[09:05] <BFTS> hi
[02:51] <BenC> mjg59: anything new in 2.6.22 libata (compared to 2.6.20) that would start making my hd spin down more aggressively while on battery?
[03:02] <Nafallo> that sounds like a good thing though :-P
[03:41] <mjg59> BenC: I'd noticed that, but I'm not sure why
[04:54] <jeromeg> hello
[04:54] <jeromeg> i'm triaging and I wanted to know if bug 123559 is really a kernel issue
[04:54] <jeromeg> can someone help me ?
[04:55] <zul> which version?
[04:56] <jeromeg> 2.6.22 I think
[04:56] <jeromeg> 2.6.22-7 to be precise
[04:56] <zul> i tink it might be a udev bug but im not 100% sure
[04:56] <jeromeg> happens for at least two persons
[04:57] <jeromeg> ok
[04:57] <jeromeg> I should report this upstream ? or ubuntu guys will deal with this problem ?
[04:58] <kylem> jeromeg, do you have an /etc/mactab?
[04:58] <kylem> jeromeg, it's not a kernel issue.
[04:59] <jeromeg> kylem : I'm only triaging so I can't help you with this
[04:59] <kylem> oh.
[05:00] <kylem> well. not very useful then.
[05:00] <jeromeg> but I can ask the question nothe bug report
[05:00] <jeromeg> *on the
[05:01] <jeromeg> I have another question, who deals with pcmcia, the kernel team ?
[05:02] <kylem> jeromeg, yes.
[05:02] <jeromeg> so bug #52510 should be for you ?
[05:03] <jeromeg> there seems to be a missing file in pcmcia-utils
[05:03] <jeromeg> I'm triaging old bugs and a lot of them are kernel one's, so sorry if I mess with old stuff
[05:04] <kylem> it's fine. thanks for doing it.
[05:05] <jeromeg> most of them are fixed, but some remain :)
[10:17] <mjg59> BenC: You seem to have dropped the hotkeys over acpi patch from toshiba_acpi
[10:21] <mjg59> BenC: And the lack of history makes it kind of difficult to work out when