Re: wireless without network-manager... is it still possible?
On Sat, May 21, 2016 at 10:44 PM, <tomas@tuxteam.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, May 21, 2016 at 09:02:15PM -0800, Britton Kerin wrote:
>> somehow network-manager makes it work. But I've had it with gnome, and none
>> of the command line tools or references I've found work. That
>> includes /etc/network/interfaces,
>> direct use of ifconfig,iw,ip,rfkill,wpa_supplicant,dhclient, and
>> wicd-client (though it's not really what I want.
>
> I have wireless working (right now) without Network Manager, via
> ifupdown, on jessie/sid.
>
>> Is this even still possible or have the systemd assholes decided we
>> shouldn't be doing it?
>
> Now, now. I don't like systemd myself (and manage to avoid it, I'm
> still using SysV init), but treating free software developers as
Nice to hear that's still possible, the general tone I've seen so far as
I look at this is that its a huge pain even on gentoo and almost
impossible elsewhere.
> "assholes" seems highly inappropriate.
Well it's the customary term for people with the attitude that they constantly
and deliberately exhibit.
>> I believe the problem with the traditional wpa_supplicatn approach is
>> related to syslog entries like
>> these:
>>
>> May 21 17:00:06 debian kernel: iwlwifi 0000:02:00.0: can't access the
>> RSA semaphore it is write protected
>
> Sorry I can't help you with that specific one. But search engines give
> some hits which look relevant, like e.g.
>
> <https://bbs.archlinux.org/viewtopic.php?id=210306>
I saw that, but if it needs a new firmware, it seems that network-manager
is pulling it in somehow, so it looks like the problem is that the old
interfaces don't and no one has noticed.
>> But as I say somehow network-manager makes it work.
>>
>> I just got a new laptop after 10 years, I didn't realize how bad the
>> situation has become with systemd udev gnome etc.
>
> Then help others keeping the alternatives up and running. No clients?
> No product!
I'm trying. I'll report when it works. Trying to run nmcli fails from other
window managers with dbus errors, which it absolutely shouldn't do since
network-manager is running. Same with nm-connection-editor and wicd-client,
they are all apparently dependent on dbus now, and dbus doesn't appear to
work correctly without a gnome session going.
So I need gnome running to talk to my network card. How fcking ridiculous. It
should be a kernel function but it looks like the only tested configuration
involves all of this wobbly stack of garbage. Isn't this exactly what we were
promised wasn't going to happen when debian went with systemd?
Britton
Reply to: