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 05-10-2017, 12:07 PM   #1
bormant
Member
 
Registered: Jan 2008
Posts: 332

Rep: Reputation: 192Reputation: 192
/isolinux/initrd.img of -current cleanup


The -current's /isolinux/initrd.img contains virtio modules that can not be loaded by huge.s kernel.

The huge kernel config is:
Code:
$ wget -qO- http://slackware.osuosl.org/slackware64-current/kernels/huge.s/config | grep _VIRTIO
CONFIG_VIRTIO_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS_COMMON=m
CONFIG_NET_9P_VIRTIO=y
CONFIG_VIRTIO_BLK=y
CONFIG_SCSI_VIRTIO=y
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM_VIRTIO=y
CONFIG_DRM_VIRTIO_GPU=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_INPUT=m
CONFIG_VIRTIO_MMIO=y
# CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set
The /isolinux/initrd.img contains these virtio modules:
Code:
$ wget http://slackware.osuosl.org/slackware64-current/isolinux/initrd.img
$ zcat initrd.img | cpio --quiet -it | grep /virtio.*\.ko
lib/modules/4.9.27/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko.gz
lib/modules/4.9.27/kernel/drivers/virtio/virtio_input.ko.gz
lib/modules/4.9.27/kernel/drivers/virtio/virtio_ring.ko.gz
lib/modules/4.9.27/kernel/drivers/virtio/virtio_balloon.ko.gz
lib/modules/4.9.27/kernel/drivers/virtio/virtio_mmio.ko.gz
lib/modules/4.9.27/kernel/drivers/virtio/virtio_pci.ko.gz
lib/modules/4.9.27/kernel/drivers/virtio/virtio.ko.gz
lib/modules/4.9.27/kernel/drivers/net/virtio_net.ko.gz
lib/modules/4.9.27/kernel/drivers/block/virtio_blk.ko.gz
Most of them are built into the huge kernel (=y).

When try to load them:
Code:
# for m in \
 virtio-gpu virtio_input virtio_ring virtio_balloon \
 virtio_mmio virtio_pci virtio virtio_net virtio_blk 
do modprobe $m ; done
modprobe: ERROR: could not insert 'virtio_gpu': Exec format error
modprobe: ERROR: could not insert 'virtio_input': Exec format error
modprobe: ERROR: could not insert 'virtio_ring': Exec format error
modprobe: ERROR: could not insert 'virtio_balloon': Exec format error
modprobe: ERROR: could not insert 'virtio_mmio': Exec format error
modprobe: ERROR: could not insert 'virtio_pci': Exec format error
modprobe: ERROR: could not insert 'virtio': Exec format error
modprobe: ERROR: could not insert 'virtio_net': Exec format error
modprobe: ERROR: could not insert 'virtio_blk': Exec format error

# dmesg | tail -n9
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio_ring: exports duplicate symbol virtio_break_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
virtio: exports duplicate symbol register_virtio_device (owned by kernel)
All as expected...

So there is no value to have them in /isolinux/initrd.img.

Last edited by bormant; 05-10-2017 at 02:09 PM.
 
Old 05-10-2017, 01:35 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,546

Rep: Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922
The modules are needed with the generic kernel, which is what the initrd is really for. The huge kernel should not be used really, except when installing your system.
 
Old 05-10-2017, 01:55 PM   #3
bormant
Member
 
Registered: Jan 2008
Posts: 332

Original Poster
Rep: Reputation: 192Reputation: 192
Quote:
Originally Posted by Alien Bob View Post
The huge kernel should not be used really, except when installing your system.
Yes, it's all about the install environment located in /isolinux/initrd.img on install media or in the Slackware tree:
http://slackware.osuosl.org/slackwar...nux/initrd.img

It's not about a/kernel-modules package.

There are no chance to boot installer with generic kernel, there are no generic kernels in /kernels/ on install media or in the Slackware tree.

Last edited by bormant; 05-10-2017 at 03:42 PM.
 
1 members found this post helpful.
Old 05-10-2017, 02:42 PM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,546

Rep: Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922Reputation: 5922
Ah, I misunderstood you then!
 
  


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
[SOLVED] Why root now has a password set in /etc/shadow in slackware64-current/isolinux/initrd.img? Didier Spaier Slackware 4 02-24-2016 09:36 AM
[SOLVED] How to rebuild RedHat 6.2 isolinux/initrd.img? xiebiwu Red Hat 3 01-11-2012 02:25 AM
How to rebuild RedHat 6.2 isolinux/initrd.img? xiebiwu Linux - Kernel 2 01-10-2012 05:19 AM
Looking for script to generate isolinux/initrd.img Skaperen Slackware 19 05-31-2009 09:32 AM

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

All times are GMT -5. The time now is 11:41 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration