| Linux - Kernel This forum is for all discussion relating to the Linux kernel. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-01-2024, 09:56 AM
|
#1
|
|
Senior Member
Registered: Mar 2010
Distribution: Slackware
Posts: 2,412
|
Why does kernel 6.11.6 name my network interface eth126 instead of usb0?
My network adaptor connects via usb. Beginning 2022 August 13 the kernel registered the interface as usb0
Quote:
|
rndis_host 2-1.3:1.0 usb0: register 'rndis_host' at usb-0000:00:1d.0-1.3, RNDIS device, b6:12:4c:86:3c:36
|
. I had built kernel 5.19.1 2022 August 11 and booted into it that day. Beginning this morning with the first boot into 6.11.6 the kernel registers the interface as eth126.
Quote:
rndis_host 1-1:1.0 eth0: register 'rndis_host' at usb-0000:00:14.0-1, RNDIS device, 86:12:5e:7d:f5:eb
rndis_host 1-1:1.0 eth126: renamed from eth0
|
Why? It works, I just had to figure it out. The network hardware is the same.
|
|
|
|
11-01-2024, 11:03 PM
|
#3
|
|
Senior Member
Registered: Mar 2010
Distribution: Slackware
Posts: 2,412
Original Poster
|
Quote:
Originally Posted by mrmazda
... provide the why.
|
Those are both systemd, which I don't have - does it still apply? The first says it's obsoleted.
kernel-parameters.txt doesn't have net.ifnames . I see netdev, which would seem to address the matter.
Last edited by RandomTroll; 11-01-2024 at 11:24 PM.
|
|
|
|
11-01-2024, 11:51 PM
|
#4
|
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 6,978
|
I don't spend much time booted to sysvinit installations any more, don't remember the various net setup configuration options, so can't answer if it still applies.
Code:
> inxi -Sz
System:
Kernel: 5.14.21-150500.55.80-default arch: x86_64 bits: 64
Desktop: KDE v: 3.5.10 Distro: openSUSE Leap 15.5
> cat /proc/cmdline
root=LABEL=<redacted> ipv6.disable=1 net.ifnames=0 noresume consoleblank=0 preempt=full mitigations=auto vga=791 video=1440x900@60
> ip a | grep 2:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
>
|
|
|
|
All times are GMT -5. The time now is 06:31 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|