Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #65316 > unrolled thread
| Started by | Werner Horsch <werner.horsch@gmail.com> |
|---|---|
| First post | 2019-10-04 03:10 +0200 |
| Last post | 2019-10-11 17:20 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
RTL 8169 driver Werner Horsch <werner.horsch@gmail.com> - 2019-10-04 03:10 +0200
Re: RTL 8169 driver Nicolas Schier <nicolas@fjasle.eu> - 2019-10-10 21:30 +0200
Re: RTL 8169 driver Nicolas Schier <nicolas@fjasle.eu> - 2019-10-11 17:20 +0200
| From | Werner Horsch <werner.horsch@gmail.com> |
|---|---|
| Date | 2019-10-04 03:10 +0200 |
| Subject | RTL 8169 driver |
| Message-ID | <yNkgy-4I3-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Package linux-headers-4.19.0-6-amd64 I'm writing to you after looking for days on a solution to a boot error I'm experiencing with the ethernet board on two machines, both have the same board provider. Both ran Mint in the past with no issues at all [ [0;1;31mFAILED [0m] Failed to start [0;1;39mRaise network interfaces [0m. See 'systemctl status networking.service' for details. I enabled the use of nonfree repositories so as to get RTL drivers, tried several things out with no success at all. I inspect a 3rd box which has the same RTL board but runs LinuxMint flawless, the only difference I could see is that has a different kernel Here some outputs that may help werner@G42 ~ $ lspci | egrep -i --color 'network|ethernet' 02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 02) $ sudo journalctl -xe -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit networking.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Oct 01 22:13:52 G42 systemd[1]: networking.service: Failed with result 'exit-cod -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit networking.service has entered the 'failed' state with result 'exit- Oct 01 22:13:52 G42 systemd[1]: Failed to start Raise network interfaces. -- Subject: A start job for unit networking.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support $ sudo systemctl status networking.service ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese Active: failed (Result: exit-code) since Tue 2019-10-01 22:17:42 -03; 29s ago Docs: man:interfaces(5) Process: 1904 ExecStart=/sbin/ifup -a --read-environment (code=exited, status= Main PID: 1904 (code=exited, status=1/FAILURE) Oct 01 22:17:42 G42 systemd[1]: Starting Raise network interfaces... Oct 01 22:17:42 G42 ifup[1904]: Cannot find device "eth0" Oct 01 22:17:42 G42 ifup[1904]: ifup: failed to bring up eth0 Oct 01 22:17:42 G42 systemd[1]: networking.service: Main process exited, code=ex Oct 01 22:17:42 G42 systemd[1]: networking.service: Failed with result 'exit-cod Oct 01 22:17:42 G42 systemd[1]: Failed to start Raise network interfaces. I appreciate any advice
[toc] | [next] | [standalone]
| From | Nicolas Schier <nicolas@fjasle.eu> |
|---|---|
| Date | 2019-10-10 21:30 +0200 |
| Message-ID | <yPMil-cT-1@gated-at.bofh.it> |
| In reply to | #65316 |
[Multipart message — attachments visible in raw view] — view raw
Hi, (see below for my comment/question) On Thu, Oct 03, 2019 at 09:45:10PM -0300, Werner Horsch wrote: > Package linux-headers-4.19.0-6-amd64 > > I'm writing to you after looking for days on a solution to a boot error I'm > experiencing with the ethernet board on two machines, both have the same > board provider. Both ran Mint in the past with no issues at all > > [ [0;1;31mFAILED [0m] Failed to start [0;1;39mRaise network interfaces [0m. > See 'systemctl status networking.service' for details. > > I enabled the use of nonfree repositories so as to get RTL drivers, tried > several things out with no success at all. I inspect a 3rd box which has > the same RTL board but runs LinuxMint flawless, the only difference I could > see is that has a different kernel > > Here some outputs that may help > werner@G42 ~ $ lspci | egrep -i --color 'network|ethernet' > 02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe > 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E > PCI Express Fast/Gigabit Ethernet controller (rev 02) > > $ sudo journalctl -xe > -- Support: https://www.debian.org/support > -- > -- An ExecStart= process belonging to unit networking.service has exited. > -- > -- The process' exit code is 'exited' and its exit status is 1. > Oct 01 22:13:52 G42 systemd[1]: networking.service: Failed with result > 'exit-cod > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- The unit networking.service has entered the 'failed' state with result > 'exit- > Oct 01 22:13:52 G42 systemd[1]: Failed to start Raise network interfaces. > -- Subject: A start job for unit networking.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > > > $ sudo systemctl status networking.service > ● networking.service - Raise network interfaces > Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor > prese > Active: failed (Result: exit-code) since Tue 2019-10-01 22:17:42 -03; 29s > ago > Docs: man:interfaces(5) > Process: 1904 ExecStart=/sbin/ifup -a --read-environment (code=exited, > status= > Main PID: 1904 (code=exited, status=1/FAILURE) > > Oct 01 22:17:42 G42 systemd[1]: Starting Raise network interfaces... > Oct 01 22:17:42 G42 ifup[1904]: Cannot find device "eth0" > Oct 01 22:17:42 G42 ifup[1904]: ifup: failed to bring up eth0 > Oct 01 22:17:42 G42 systemd[1]: networking.service: Main process exited, > code=ex > Oct 01 22:17:42 G42 systemd[1]: networking.service: Failed with result > 'exit-cod > Oct 01 22:17:42 G42 systemd[1]: Failed to start Raise network interfaces. > > I appreciate any advice on a freshly installed system I would not expect any network device being named 'eth*'. Is your /etc/network/interfaces (or corresponding) auto-generated? It might give a clue if you would forward the output of 'ip link'. Kind regards, Nicolas
[toc] | [prev] | [next] | [standalone]
| From | Nicolas Schier <nicolas@fjasle.eu> |
|---|---|
| Date | 2019-10-11 17:20 +0200 |
| Message-ID | <yQ4RY-3Gy-7@gated-at.bofh.it> |
| In reply to | #65373 |
On Thu, Oct 10, 2019 at 09:22:20PM +0200, Nicolas Schier wrote: > Hi, > > (see below for my comment/question) > > On Thu, Oct 03, 2019 at 09:45:10PM -0300, Werner Horsch wrote: > > Package linux-headers-4.19.0-6-amd64 > > > > I'm writing to you after looking for days on a solution to a boot error I'm > > experiencing with the ethernet board on two machines, both have the same > > board provider. Both ran Mint in the past with no issues at all > > > > [ [0;1;31mFAILED [0m] Failed to start [0;1;39mRaise network interfaces [0m. > > See 'systemctl status networking.service' for details. > > > > I enabled the use of nonfree repositories so as to get RTL drivers, tried > > several things out with no success at all. I inspect a 3rd box which has > > the same RTL board but runs LinuxMint flawless, the only difference I could > > see is that has a different kernel > > > > Here some outputs that may help > > werner@G42 ~ $ lspci | egrep -i --color 'network|ethernet' > > 02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe > > 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E > > PCI Express Fast/Gigabit Ethernet controller (rev 02) > > > > $ sudo journalctl -xe > > -- Support: https://www.debian.org/support > > -- > > -- An ExecStart= process belonging to unit networking.service has exited. > > -- > > -- The process' exit code is 'exited' and its exit status is 1. > > Oct 01 22:13:52 G42 systemd[1]: networking.service: Failed with result > > 'exit-cod > > -- Subject: Unit failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > -- > > -- The unit networking.service has entered the 'failed' state with result > > 'exit- > > Oct 01 22:13:52 G42 systemd[1]: Failed to start Raise network interfaces. > > -- Subject: A start job for unit networking.service has failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > > > > > $ sudo systemctl status networking.service > > ● networking.service - Raise network interfaces > > Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor > > prese > > Active: failed (Result: exit-code) since Tue 2019-10-01 22:17:42 -03; 29s > > ago > > Docs: man:interfaces(5) > > Process: 1904 ExecStart=/sbin/ifup -a --read-environment (code=exited, > > status= > > Main PID: 1904 (code=exited, status=1/FAILURE) > > > > Oct 01 22:17:42 G42 systemd[1]: Starting Raise network interfaces... > > Oct 01 22:17:42 G42 ifup[1904]: Cannot find device "eth0" > > Oct 01 22:17:42 G42 ifup[1904]: ifup: failed to bring up eth0 > > Oct 01 22:17:42 G42 systemd[1]: networking.service: Main process exited, > > code=ex > > Oct 01 22:17:42 G42 systemd[1]: networking.service: Failed with result > > 'exit-cod > > Oct 01 22:17:42 G42 systemd[1]: Failed to start Raise network interfaces. > > > > I appreciate any advice > > on a freshly installed system I would not expect any network device > being named 'eth*'. Is your /etc/network/interfaces (or corresponding) > auto-generated? It might give a clue if you would forward the output of > 'ip link'. > FTR: solution has been found (offlist); there had been a mismatch between the actual device name (enpXXX) and the /etc/network/interfaces* stanza (eth0).
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web