LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-08-2021, 08:30 PM   #1
babydr
Member
 
Registered: Aug 2015
Location: Fairbanks , Alaska
Distribution: Slackware-14.2+
Posts: 75

Rep: Reputation: Disabled
No compiled in Ethernet devices in 5.12.9-huge !


There are No compiled in Ethernet devices in 5.12.9-huge ! In fact in the config not even a module is defined .

Has the kernel gone totally module ? Or ???

TIa , JimL
 
Old 06-08-2021, 09:09 PM   #2
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 827

Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
Huh. I didn't have a problem. Did you forget to install the modules package? Or download the generic kernel and didn't have an initrd?
 
Old 06-08-2021, 09:32 PM   #3
lovemeslk
Member
 
Registered: Feb 2020
Location: none of your business
Distribution: Slackware
Posts: 82

Rep: Reputation: Disabled
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]=""
 
Old 06-08-2021, 09:35 PM   #4
lovemeslk
Member
 
Registered: Feb 2020
Location: none of your business
Distribution: Slackware
Posts: 82

Rep: Reputation: Disabled
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.
 
Old 06-08-2021, 09:35 PM   #5
babydr
Member
 
Registered: Aug 2015
Location: Fairbanks , Alaska
Distribution: Slackware-14.2+
Posts: 75

Original Poster
Rep: Reputation: Disabled
@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 .

Thank you for the help .

JimL
 
Old 06-08-2021, 09:40 PM   #6
babydr
Member
 
Registered: Aug 2015
Location: Fairbanks , Alaska
Distribution: Slackware-14.2+
Posts: 75

Original Poster
Rep: Reputation: Disabled
@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 .

Thank you also for your help .
JimL

Last edited by babydr; 06-08-2021 at 09:49 PM.
 
Old 06-08-2021, 10:05 PM   #7
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 827

Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
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.

Last edited by garpu; 06-08-2021 at 10:07 PM.
 
Old 06-08-2021, 10:28 PM   #8
babydr
Member
 
Registered: Aug 2015
Location: Fairbanks , Alaska
Distribution: Slackware-14.2+
Posts: 75

Original Poster
Rep: Reputation: Disabled
Never F'N Mind dumb dumb forgot to 'lilo' !-(
 
Old 06-09-2021, 10:42 AM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,259

Rep: Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845
Quote:
Originally Posted by babydr View Post
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.
 
2 members found this post helpful.
Old 06-09-2021, 07:24 PM   #10
babydr
Member
 
Registered: Aug 2015
Location: Fairbanks , Alaska
Distribution: Slackware-14.2+
Posts: 75

Original Poster
Rep: Reputation: Disabled
@bassmadrigal , Thank you , I should have noticed & known that myself .

There is only one possible size difference maker(s) the "^#.*is not set" being different between them , Very rare as I should have known .

The real clincher was "uname -a' showing the the 5.10.41 kernel being the booted kernel .

JimL
 
Old 06-09-2021, 11:25 PM   #11
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,933

Rep: Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144
Quote:
Originally Posted by babydr View Post
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 View Post
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?
 
Old 06-10-2021, 10:48 AM   #12
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,259

Rep: Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845
Quote:
Originally Posted by rkelsen View Post
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.

Code:
grep -c \=m$ /location/to/config-generic-5.12.9.x64
4398
grep -c \=m$ /location/to/config-huge-5.12.9.x64
4311
grep -c \=y$ /location/to/config-generic-5.12.9.x64
2422
grep -c \=y$ /location/to/config-huge-5.12.9.x64
2335
Quote:
Originally Posted by rkelsen View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Huge kernel boots--Huge.SMP (and generic.smp) kernel will not MTCAT Linux - Newbie 4 02-03-2021 02:11 PM
Compiled program not showing up as compiled and not able to run. hjoshuaj Linux - Newbie 3 03-27-2014 05:49 AM
Slackware 13.1 huge smp is not huge cs_strong Slackware 4 11-16-2010 07:41 AM
Huge amount of "PHP Notice:" -> huge logs Braynid Linux - Software 4 03-18-2008 06:35 AM
Huge Huge Problem With Forums!!! The_Insomniac Linux - General 1 06-07-2004 08:15 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:31 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration