Re: systemd warning

2016-04-13 Thread Mathieu Malaterre
Hi, On Thu, Apr 14, 2016 at 1:04 AM, Riccardo Mottola wrote: > Hi, > > in my dmesg I see this: > > [ 268.896698] systemd-logind[1976]: New seat seat0. > [ 268.941156] systemd-logind[1976]: Failed to start user service, ignoring: > Unknown unit: user@1000.service > > > should I worry? where does

Re: Airport wireless and current Debian

2016-04-13 Thread Dan DeVoto
I don't have a solution, but I remember coming across a forum post awhile back saying WEP no longer worked with 1st generation Airport cards due to a bug. Looks like they didn't fix it. Regards, Dan On Wed, 4/13/16, Riccardo Mottola wrote: Subje

Re: Airport wireless and current Debian

2016-04-13 Thread Mathieu Malaterre
On Thu, Apr 14, 2016 at 1:02 AM, Riccardo Mottola wrote: > Hi, > > I just upgraded everything. > > I noticed that I cannot connect to my home wifi anymore, which is a pretty > simple WEP encrypted network, which always used to work. > > I noticed that the Airport card is detected as a device and t

Re: Airport wireless and current Debian

2016-04-13 Thread Risto Suominen
What firmware version did you have before? Looks like the card has 8.70, and Debian loads 9.48. You could try to rename the file agere_sta_fw.bin, forcing the card to use its own firmware. I have seen situations where loading 9.48 gives me WPA but takes away WEP. Risto

systemd warning

2016-04-13 Thread Riccardo Mottola
Hi, in my dmesg I see this: [ 268.896698] systemd-logind[1976]: New seat seat0. [ 268.941156] systemd-logind[1976]: Failed to start user service, ignoring: Unknown unit: user@1000.service should I worry? where does it come from? Riccardo

Airport wireless and current Debian

2016-04-13 Thread Riccardo Mottola
Hi, I just upgraded everything. I noticed that I cannot connect to my home wifi anymore, which is a pretty simple WEP encrypted network, which always used to work. I noticed that the Airport card is detected as a device and that I can configure it with iwconfig to the correct ESSID and KEY: