I've always had a networking problem with Slackware as a guest VM under Citrix XenServer (or Citrix Hypervisor, I guess is what they call it these days). I still prefer Slackware as a desktop and so I set about solving this again recently - this time I would not be thwarted!
I ran across this article: How do I disable 8139too network driver... because lsmod lead me to search for 8139too networking module. This was an Ubuntu article, so, I'll transmorgify it a bit for Slackware users. The first thing it suggested was to blacklist 8139 in the modules. Like the author of this I did not have any luck with that. It was suggested you use the 8139cp instead (cool! I didn't even know of its existence before this article).
# lsmod | grep 8139
This revealed 8139too in use and bound with mii, so...
# rmmod 8139too
# rmmod mii
# modprobe 8139cp
# modprobe mii
# /etc/rc.d/rc.inet1 restart
At this point, I had, for the first time ever as a Slackware XenServer guest, a working eth0!
In order to keep it (and use less resources) I created a smaller kernel /boot/initrd.gz by running mkinitrd.
# /usr/share/mkinitrd/mkinird_command_generator.sh
I appended :8130cp to the suggested mkinitrd script:
# mkinitrd -c -k 4.4.14 -f ext4 -r /dev/sda2 -m jbd2:mbcache:ext4:8139cp -u -o /boot/initrd.gz
This seemed to work nicely so I doctored up the boot area a bit:
# cd /boot
# rm System.map
# ln -s System.map-generic-4.4.14 System.map
# rm config
# ln -s config-generic-4.4.14 config
Then I added a section to the /etc/lilo.conf:
image = /boot/vmlinuz-generic
label = Slackware
initrd = /boot/initrd.gz
root = /dev/sda2
read-only
And I always add default = Slackware before running lilo -v.
After that, I rebooted and had a Slackware install with a nice lean kernel with a eth0 running as a guest VM under Citrix XenServer (or Hypervisor - I can't get used to that!).
Monday, October 14, 2019
Subscribe to:
Posts (Atom)