Richmond writes:
> Dan Ritter writes:
>
>> Richmond wrote:
>>> Looks like this bug:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
>>
>> Could be.
>>
>> In which case, this will be solved in the new Stable, most
>> likely out in May or June.
>>
>> You could try a backport
On Fri 23 Apr 2021 at 23:11:58 (-0400), Greg Wooledge wrote:
> On Fri, Apr 23, 2021 at 09:59:09PM -0500, David Wright wrote:
> > OTOH my startup files set Mywiredifname for scripts to use, where:
> >
> > Mywiredifname=$(ip -o link show | sed -e '/^[0-9]\+: [^e]/d;s/[0-9]\+:
> > \([^:]\+\): .*/\1/
Greg Wooledge wrote:
> On Fri, Apr 23, 2021 at 09:59:09PM -0500, David Wright wrote:
>
> > (My days of running multiple ethernet cards are long gone,
> > so sed will quit after one match.)
>
> Sounds like a naive assumption. Some motherboards have dual NICs built in,
> don't they?
A fair numbe
On Fri, Apr 23, 2021 at 09:59:09PM -0500, David Wright wrote:
> OTOH my startup files set Mywiredifname for scripts to use, where:
>
> Mywiredifname=$(ip -o link show | sed -e '/^[0-9]\+: [^e]/d;s/[0-9]\+:
> \([^:]\+\): .*/\1/;q')
>
> $ echo $Mywiredifname
> enp3s0
unicorn:~$ ip -o link show |
On Fri 23 Apr 2021 at 13:23:31 (-0400), Cindy Sue Causey wrote:
>
> All of the adapters that come as a single item have worked great. You
> just have to track down the new identifier, e.g. one of mine is
> "enx00909e9dd1ee". That long value goes wherever one normally types in
> eth0, enp1s0, eno1,
Richmond wrote:
> Dan Ritter writes:
>
> > Richmond wrote:
> >> Looks like this bug:
> >>
> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
> >
> > Could be.
> >
> > In which case, this will be solved in the new Stable, most
> > likely out in May or June.
> >
> > You could try
Dan Ritter writes:
> Richmond wrote:
>> Looks like this bug:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
>
> Could be.
>
> In which case, this will be solved in the new Stable, most
> likely out in May or June.
>
> You could try a backports kernel before that.
>
I tried
On 4/23/21, Dan Ritter wrote:
> Richmond wrote:
>> > Let's try from the bottom up?
>> >
>> > ip link show
>> > will show you the interfaces recognized by the kernel. If this
>> > works, it might show you an eth0, an en0, or something like a
>> > enp22s0 device. Let's call it "SAM".
>>
>> Tha
On 4/23/21, David Wright wrote:
> On Fri 23 Apr 2021 at 10:49:00 (+0100), Richmond wrote:
>> Cindy Sue Causey writes:
>>
>> > Questions where answers might help come to mind. Primarily, has this
>> > always occurred, or did it just start up in the last couple days?
>>
>> It has occured since inst
On Fri 23 Apr 2021 at 10:49:00 (+0100), Richmond wrote:
> Cindy Sue Causey writes:
>
> > Questions where answers might help come to mind. Primarily, has this
> > always occurred, or did it just start up in the last couple days?
>
> It has occured since installing debian (10). Prior to that I was
Richmond wrote:
> Looks like this bug:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
Could be.
In which case, this will be solved in the new Stable, most
likely out in May or June.
You could try a backports kernel before that.
-dsr-
Looks like this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
Richmond wrote:
> > Let's try from the bottom up?
> >
> > ip link show
> > will show you the interfaces recognized by the kernel. If this
> > works, it might show you an eth0, an en0, or something like a
> > enp22s0 device. Let's call it "SAM".
>
> Thanks for your reply.
>
> enp2s0: mtu
On Vi, 23 apr 21, 10:46:21, Richmond wrote:
> Dan Ritter writes:
> >
> > If any part of SAM reads "down", do this:
> >
> > sudo ip link set up SAM
>
> ip link set up enp2s0
>
> No output here but the link is still down.
This suggests to me the problem is at a lower level, i.e. the kernel
mod
Dan Ritter writes:
> Richmond wrote:
>> When I resume from suspend there is no networking. I cannot find a way
>> to restart it. I tried these various commands.
>>
>> systemctl restart network
>> /etc/init.d/networking restart
>> systemctl reset-failed
>> systemctl restart networking.service
Thanks for your reply.
Cindy Sue Causey writes:
> Questions where answers might help come to mind. Primarily, has this
> always occurred, or did it just start up in the last couple days?
It has occured since installing debian (10). Prior to that I was using
opensuse.
>
> I'm on a new old secon
On 4/22/21, Richmond wrote:
> When I resume from suspend there is no networking. I cannot find a way
> to restart it. I tried these various commands.
>
> systemctl restart network
> /etc/init.d/networking restart
> systemctl reset-failed
> systemctl restart networking.service
> systemctl restart n
Richmond wrote:
> When I resume from suspend there is no networking. I cannot find a way
> to restart it. I tried these various commands.
>
> systemctl restart network
> /etc/init.d/networking restart
> systemctl reset-failed
> systemctl restart networking.service
> systemctl restart network-on
From: Richmond
Newsgroups: linux.debian.user
Subject: No networking after resume from suspend
Date: Thu, 22 Apr 2021 22:34:07 +0100
Organization: Frantic
Message-ID: <84r1j2knqo@example.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
X-Draft-From: ("linux.debian.
19 matches
Mail list logo
