On Tue, Jul 12, 2022 at 10:28 AM Peter Ehlert wrote:
>
> On 7/11/22 21:35, Tixy wrote:
> > On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
> > [...]
> >> I decided to try a fresh netinstall alongside and Boom:
> >>
> >> ===
> >> multiple network interfaces
> >>
> >> eno1: Intel Corporation
On Tue 12 Jul 2022 at 15:44:41 (+0100), Tixy wrote:
> Another idea, is looking for that network name in the logs for the
> current boot.
>
> journalctl -b | grep -B3 enx00e04c534458
>
> That'll give you matches with the three lines before so you can see the
> context.
I'd use grep -B3 -A3 -i
On Tue, 2022-07-12 at 05:35 +0100, Tixy wrote:
> On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
> [...]
> >
> > I decided to try a fresh netinstall alongside and Boom:
> >
> > ===
> > multiple network interfaces
> >
> > eno1: Intel Corporation Ethernet Connection (2) I218-LM
> > enp5s0:
On 7/11/22 21:35, Tixy wrote:
On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
[...]
I decided to try a fresh netinstall alongside and Boom:
===
multiple network interfaces
eno1: Intel Corporation Ethernet Connection (2) I218-LM
enp5s0: Intel Corporation 1210 Gigabit Network Connection
On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
[...]
>
> I decided to try a fresh netinstall alongside and Boom:
>
> ===
> multiple network interfaces
>
> eno1: Intel Corporation Ethernet Connection (2) I218-LM
> enp5s0: Intel Corporation 1210 Gigabit Network Connection
> enx00e04c534458
after a system update and a new kernel I rebooted.
all seemed fine but the network would not connect...
Debian Mate, network install, it just works and I never have messed with
the settings.
not a clue what was going on.
long story short, messing around a live USB did log in fine.
I decided t
6 matches
Mail list logo
