On Thu, 2016-05-26 at 12:15 -0800, Britton Kerin wrote:
> On Thu, May 26, 2016 at 4:35 AM, Andrew Shadura
> wrote:
> > There's no need in any of this, ifupdown already supports this mode
> > without anything apart from wpa-conf.
> >
> > See /usr/share/doc/wpasupplicant/README.Debian.gz for more d
On Thu, 2016-05-26 at 10:24 +0200, Michael Biebl wrote:
> It's hard to say though. For this we'd need proper debug logs to
> further investigate this.
You shamed me into doing something about it. But now I test it,
network-manager works. It's been 3 months and a similar number of
kernels, so who
On Thu, May 26, 2016 at 4:35 AM, Andrew Shadura wrote:
> On 26 May 2016 at 09:16, Russell Stuart wrote:
>> auto wifi_interface
>> iface wifi_interface inet dhcp
>> pre-up systemctl stop wpa_supplicant || :
>> post-down systemctl start
On Thu, 2016-05-26 at 05:26 +, darkestkhan wrote:
[...]
> It is worth remembering that network manager depends indirectly on
> systemd - not all of us have systemd installed. And not all of us know
> (or knew in this case) the invocation to bring up the wifi connection.
It doesn't require syst
Am 26.05.2016 um 09:16 schrieb Russell Stuart:
> partly. Among the things that didn't work were wicd (kept on
> reinitialising the interface every 10 seconds or so) and network-
> manager (didn't recognise the interface at all). This initially caused
> a lot of head scratching and wasted time bec
On Mon, 2016-05-23 at 08:28 +0200, Adam Borowski wrote:
> Using low-level tools can indeed be tricky, so while they're more
> powerful than anything NM or wicd can do, they're an overkill and a
> waste of learning time if what you want is regular use of a single
> interface.
I have a new laptop on
On Mon, May 23, 2016 at 7:45 PM, Andrew Shadura
wrote:
>
> On 23 May 2016 15:50, "Wookey" wrote:
>>
>> +++ Adam Borowski [2016-05-23 12:10 +0200]:
>>
>> > we keep wicd for non-Gnome users who want a clicky-clicky wifi manager.
>> >
>> > The rest, well, are on their own with console tools.
>>
>> w
On Mon, May 23, 2016 at 10:06 PM, Adam Borowski wrote:
> On Mon, May 23, 2016 at 01:17:08PM +0100, Ben Hutchings wrote:
>> On Mon, 2016-05-23 at 12:10 +0200, Adam Borowski wrote:
>> > On Mon, May 23, 2016 at 11:39:06AM +0200, Abou Al Montacir wrote:
>> > > Login in Gnome once, activate wifi and as
On May 24 2016, Britton Kerin wrote:
> On Mon, May 23, 2016 at 2:35 PM, Nikolaus Rath wrote:
>> On May 22 2016, Britton Kerin wrote:
>>> Got a new laptop after 10 years of excellent stable ancient debian,
>>> and my wireless works from gnome, and only from gnome. Unfortunately
>>> I find that g
On Mon, May 23, 2016 at 2:35 PM, Nikolaus Rath wrote:
> On May 22 2016, Britton Kerin wrote:
>> Got a new laptop after 10 years of excellent stable ancient debian,
>> and my wireless works from gnome, and only from gnome. Unfortunately
>> I find that gnome3 is not for me. I've been trying dwm.
Adam Borowski writes ("Re: trying to use wireless not from gnome... what's the
incantation?"):
> But it's not without problems. The one Britton met is that NM's interface
> is closely married to Gnome. Yes, you can use nm-cli but it's nowhere near
> prett
On 23 May 2016 10:12:12 am IST, Britton Kerin wrote:
>No combination of nmcli ifconfig iw ip rfkill unblock wpa_supplicant
>/etc/network/interfaces etc. that I've tried makes wireless work
>outside of gnome,
I've been using nmcli without GNOME and it worked just fine. network-manager is
one of
On Tue, 2016-05-24 at 00:06 +0200, Adam Borowski wrote:
> On Mon, May 23, 2016 at 01:17:08PM +0100, Ben Hutchings wrote:
> >
> > On Mon, 2016-05-23 at 12:10 +0200, Adam Borowski wrote:
> > >
> > > On Mon, May 23, 2016 at 11:39:06AM +0200, Abou Al Montacir wrote:
> > > >
> > > > Login in Gnome on
On May 22 2016, Britton Kerin wrote:
> Got a new laptop after 10 years of excellent stable ancient debian,
> and my wireless works from gnome, and only from gnome. Unfortunately
> I find that gnome3 is not for me. I've been trying dwm.
What trouble did you have? Network manager works perfectly
On May 24 2016, Adam Borowski wrote:
> But it's not without problems. The one Britton met is that NM's interface
> is closely married to Gnome.
I am not sure what you mean by "closely married", but NM works perfectly
well for me in an i3 "environment". I am not disputing that it pulls in
some Gn
On Mon, May 23, 2016 at 01:17:08PM +0100, Ben Hutchings wrote:
> On Mon, 2016-05-23 at 12:10 +0200, Adam Borowski wrote:
> > On Mon, May 23, 2016 at 11:39:06AM +0200, Abou Al Montacir wrote:
> > > Login in Gnome once, activate wifi and ask that the connection should be
> > > used by
> > > all user
On 23 May 2016 15:50, "Wookey" wrote:
>
> +++ Adam Borowski [2016-05-23 12:10 +0200]:
>
> > we keep wicd for non-Gnome users who want a clicky-clicky wifi manager.
> >
> > The rest, well, are on their own with console tools.
>
> wicd has curses and command-line interfaces too (as well as the
> gtk
+++ Adam Borowski [2016-05-23 12:10 +0200]:
> we keep wicd for non-Gnome users who want a clicky-clicky wifi manager.
>
> The rest, well, are on their own with console tools.
wicd has curses and command-line interfaces too (as well as the
gtk one). One of its nice features.
Wookey
--
Principal
❦ 23 mai 2016 12:10 +0200, Adam Borowski :
>> > NM is closely tied to Gnome so regressions in non-Gnome use aren't
>> > surprising.
>> Login in Gnome once, activate wifi and ask that the connection should be
>> used by
>> all users.
>> Then NM will save the password some were so that it connect
On Mon, 2016-05-23 at 12:10 +0200, Adam Borowski wrote:
> On Mon, May 23, 2016 at 11:39:06AM +0200, Abou Al Montacir wrote:
> >
> > On Mon, 2016-05-23 at 08:28 +0200, Adam Borowski wrote:
> > >
> > > >
> > > >
> > > > I'm posting here both in hope of a solution, and because this seems
> > > > l
On Mon, May 23, 2016 at 11:39:06AM +0200, Abou Al Montacir wrote:
> On Mon, 2016-05-23 at 08:28 +0200, Adam Borowski wrote:
> > >
> > > I'm posting here both in hope of a solution, and because this seems
> > > like a bug. How come this only works from gnome? nmcli in particular
> > > looks like
On Mon, 2016-05-23 at 08:28 +0200, Adam Borowski wrote:
> >
> > I'm posting here both in hope of a solution, and because this seems
> > like a bug. How come this only works from gnome? nmcli in particular
> > looks like it's trying to be a general-purpose solution, but somehow
> > it too only wo
Hello,
For Lan and WLan i use network-manager under XFCE succesfully.
Regards
Mechtilde
Am 23.05.2016 um 08:28 schrieb Adam Borowski:
> On Sun, May 22, 2016 at 08:42:12PM -0800, Britton Kerin wrote:
>> Got a new laptop after 10 years of excellent stable ancient debian,
>> and my wireless works
On Sun, May 22, 2016 at 08:42:12PM -0800, Britton Kerin wrote:
> Got a new laptop after 10 years of excellent stable ancient debian,
> and my wireless works from gnome, and only from gnome. Unfortunately
> I find that gnome3 is not for me. I've been trying dwm.
>
> No combination of nmcli ifconf
On Mon, May 23, 2016 at 12:42 PM, Britton Kerin wrote:
> Got a new laptop after 10 years of excellent stable ancient debian,
> and my wireless works from gnome, and only from gnome.
Please ask about this on a Debian user support channel:
https://www.debian.org/support
--
bye,
pabs
https://wik
Got a new laptop after 10 years of excellent stable ancient debian,
and my wireless works from gnome, and only from gnome. Unfortunately
I find that gnome3 is not for me. I've been trying dwm.
No combination of nmcli ifconfig iw ip rfkill unblock wpa_supplicant
/etc/network/interfaces etc. that
26 matches
Mail list logo
