Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1200505 > unrolled thread
| Started by | Marco Moock <mm@dorfdsl.de> |
|---|---|
| First post | 2024-06-11 10:00 +0200 |
| Last post | 2024-06-11 18:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.bugs.dist
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1072687: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian Marco Moock <mm@dorfdsl.de> - 2024-06-11 10:00 +0200
Bug#1072687: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian "phamiet@bluewin.ch" <phamiet@bluewin.ch> - 2024-06-11 18:50 +0200
| From | Marco Moock <mm@dorfdsl.de> |
|---|---|
| Date | 2024-06-11 10:00 +0200 |
| Subject | Bug#1072687: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian |
| Message-ID | <IO4Aa-26z6-5@gated-at.bofh.it> |
Am 11.06.2024 um 09:21:55 Uhr schrieb phamiet@bluewin.ch: > Tell me exactly which log you need to solve this problem ? Please enable trace logging in NetworkManager. The dmesg doesn't show anything unusual at the first view. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/introduction-to-networkmanager-debugging_configuring-and-managing-networking#temporarily-setting-log-levels-at-run-time-using-nmcli_introduction-to-networkmanager-debugging nmcli general logging level TRACE domains ALL Then use journalctl -u NetworkManager -b -- Gruß Marco Send unsolicited bulk mail to 1718090515muell@cartoonies.org
[toc] | [next] | [standalone]
| From | "phamiet@bluewin.ch" <phamiet@bluewin.ch> |
|---|---|
| Date | 2024-06-11 18:50 +0200 |
| Subject | Bug#1072687: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian |
| Message-ID | <IOcR3-2bJe-3@gated-at.bofh.it> |
| In reply to | #1200505 |
Hello, Thank you, I will return the result to you as soon as the problem occurs again. While I'm at it, do you know if there is a command that can be run to re-execute the automatic discovery of network hardware and devices connected to it, just like it happens at the beginning of the Debian installation process ? By analogy, tasksel allows this regarding the desktop configuration. Best regards. Philippe ----Message d'origine---- De : mm@dorfdsl.de Date : 11/06/2024 - 09:49 (E) À : phamiet@bluewin.ch, 1072687@bugs.debian.org Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian Am 11.06.2024 um 09:21:55 Uhr schrieb phamiet@bluewin.ch: > Tell me exactly which log you need to solve this problem ? Please enable trace logging in NetworkManager. The dmesg doesn't show anything unusual at the first view. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/introduction-to-networkmanager-debugging_configuring-and-managing-networking#temporarily-setting-log-levels-at-run-time-using-nmcli_introduction-to-networkmanager-debugging nmcli general logging level TRACE domains ALL Then use journalctl -u NetworkManager -b -- Gruß Marco Send unsolicited bulk mail to 1718090515muell@cartoonies.org
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web