[SOLVED] No compiled in Ethernet devices in 5.12.9-huge !
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
you really need to google search this forum on this issue.
please read run netconfig
please read this. https://mirrors.kernel.org/slackware.../rc.inet1.conf
Then set the first two devices to yes even if you only have one eth device.
Search around I remember while back. One of the Slackware Dev's explained why.
Code:
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
#
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
#
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
#
# Several other parameters are available; the end of this file contains a
# comprehensive set of examples.
#
# Important note for IPv6 stateless auto configuration (SLAAC) users:
# From Slackware 15.0 onwards, you need to set USE_SLAAC[0]="yes" below.
# =============================================================================
# IPv4 config options for eth0:
IPADDRS[0]=""
USE_DHCP[0]="yes"
# IPv6 config options for eth0:
IP6ADDRS[0]=""
USE_SLAAC[0]="yes"
USE_DHCP6[0]=""
# Generic options for eth0:
DHCP_HOSTNAME[0]=""
# IPv4 config options for eth1:
IPADDRS[1]=""
USE_DHCP[1]="yes"
# IPv6 config options for eth1:
IP6ADDRS[1]=""
USE_SLAAC[1]="yes"
USE_DHCP6[1]=""
# Generic options for eth1:
DHCP_HOSTNAME[1]=""
you really need to google search this forum on this issue.
please read run netconfig
please read this. https://mirrors.kernel.org/slackware.../rc.inet1.conf
Then set the first two devices to yes even if you only have one eth device.
Search around I remember while back. One of the Slackware Dev's explained why.
Code:
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
#
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
#
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
#
# Several other parameters are available; the end of this file contains a
# comprehensive set of examples.
#
# Important note for IPv6 stateless auto configuration (SLAAC) users:
# From Slackware 15.0 onwards, you need to set USE_SLAAC[0]="yes" below.
# =============================================================================
# IPv4 config options for eth0:
IPADDRS[0]=""
USE_DHCP[0]="yes"
# IPv6 config options for eth0:
IP6ADDRS[0]=""
USE_SLAAC[0]="yes"
USE_DHCP6[0]=""
# Generic options for eth0:
DHCP_HOSTNAME[0]=""
# IPv4 config options for eth1:
IPADDRS[1]=""
USE_DHCP[1]="yes"
# IPv6 config options for eth1:
IP6ADDRS[1]=""
USE_SLAAC[1]="yes"
USE_DHCP6[1]=""
# Generic options for eth1:
DHCP_HOSTNAME[1]=""
how to test
ifconfig eth1 up
then ifconfig
now you will see it. as eth1.
Like I said there is a reason why. But I forgot. Somthing to do with cache etc.
I think Robby Workman posted about it.
@garpu , This is the HUGE Kernel not the generic .
This is the kernel used by the usual install cd/dvd .
The previous ie:5.10.41-HUGE had all the ethernets compiled in ,
This one has NO Ether device config'd or even as modules .
It does appear that the HUGE .config is the same size as the generic tho .
This was doing a slackpkg update .
The system running 5.10.41-huge without a initrd was funcioning fine .
@lovemesic , a "dmesg | grep -i ether" produces emtpy output . How would rc.inet1 use a non-existant ether device ?
Since the system at present is NOT available for me to present the present difficulty all I have are hand typed entries .
I am at present recompiling the kernel to have the intel drivers active at boot .
Then I can reboot into that kernel & Then post the previous dmesg output .
What's the ethernet card you have? And which module did it use?
Edit: You said Intel? Did you need to download any drivers from them to get it working on the 5.10 kernel? You'll need to install it again. Like if you use the Nvidia binary driver, you have to reinstall the kernel module for it every time you upgrade the kernel.
It does appear that the HUGE .config is the same size as the generic tho .
Just FYI, but this is to be expected. They should be pretty much the same size as they're going to contain the same variables for the various settings of the kernel. The selection between built in and a module is a single character (y vs m respectively) for the variable.
You'll see a big difference in the resulting kernel file between the two.
There are No compiled in Ethernet devices in 5.12.9-huge ! In fact in the config not even a module is defined .
Can I ask where you were looking?
Of course, you realise that the point of the huge kernel is that it is supposed to have almost everything built in? It's meant to be a mega monolith which supports a ton of hardware out of the box.
Quote:
Originally Posted by babydr
Never F'N Mind dumb dumb forgot to 'lilo' !-(
That's quite a fundamental mistake, which (IME) would have had nothing to do with your issue. Please explain how the two are connected?
Of course, you realise that the point of the huge kernel is that it is supposed to have almost everything built in? It's meant to be a mega monolith which supports a ton of hardware out of the box.
The huge kernel still builds a TON of modules. If you do a count of how many modules are built using config-huge-5.12.9.x64, you get 4319. If you check the generic, it's 4398. That means there's only 79 extra modules in the generic kernel vs the huge kernel. When you compare built-in from huge to generic, it's a similar 87 more items are built in on the huge vs the generic.
That's quite a fundamental mistake, which (IME) would have had nothing to do with your issue. Please explain how the two are connected?
If they upgraded their kernel packages without upgrading lilo, lilo would still boot the old kernel -- even if the file was removed from /boot -- as long as the sectors on the hard drive weren't overwritten, but no modules would be present when the boot completed. I understand how babydr could come to the conclusion that modules weren't included with the new kernel until they realized they were still booting the old kernel.
The problem is, I think, prior expectations. The huge kernel doesn't have as much built in as it used to, anymore.
I found out the hard way when I tried to jump start with my installation DVD (burned ISO) using root= to fix the bootloader. I think the show stopper was that my keyboard didn't work. In order for that to be usable I had to install the correct modules package (from the same kernel on the DVD) to /lib/modules on the slackware system. Now I just keep that there in case I need to boot with that DVD. If I make a new one I'll do the same with the appropriate modules tree. It had been a long time since I've had to do that. I never needed modules before just to jump start and reinstate the boot loader.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
