[SOLVED] slackware64 on virt-manager won't connect to internet

agricola7 · 07-04-2018, 10:41 AM

I have Slackware64 in a virt-manager vm with a singular internet connection problem. This arrangement wil run Fedora, OpenSUSE, Alpine linux, for example, perfectly well, with full internet connection on boot, but while Slackware boots well in all other respects seemingly, it makes no internet connection either via cable or wireless.

Logically it must be a problem closely related to the Slackware, but I don't seem able to find any help, certainly at my level of understanding.

How to get ifconfig to show something more than lo?

allend · 07-04-2018, 11:12 AM

Does 'ifconfig -a' show additional interfaces?
If so, you probably need to configure networking correctly. http://docs.slackware.com/slackware:...e_your_network

PS - This post would be better placed in the Slackware forum.

agricola7 · 07-04-2018, 11:55 AM

No. ifconfig shows only lo.

How should I change the thread?

rtmistler · 07-05-2018, 07:36 AM

Moved: This thread is more suitable in Slackware and has been moved accordingly to help your thread/question get the exposure it deserves.

Hit the Report button and write that you'd like the thread moved.

Melke · 07-05-2018, 07:42 AM

you can change the network card to e1000. Then it will work

For some reason Slackware doesnt recognoze the RTL driver.

KR
Mel

ponce · 07-05-2018, 08:12 AM

Quote:

Originally Posted by mmawhin

you can change the network card to e1000. Then it will work

For some reason Slackware doesnt recognoze the RTL driver.

if I remember correctly, regarding realtek 8139x cards, it tries to load the 8139too kernel module, while most of the hardware I encountered (physical or emulated) works with the 8139cp module (in some cases is the vice-versa).
another solution, in these cases, is to blacklist the former

Code:

echo "blacklist 8139too" > /etc/modprobe.d/rtl8139.conf

or, in alternative, the latter

Code:

echo "blacklist 8139cp" > /etc/modprobe.d/rtl8139.conf

and reboot.

Melke · 07-05-2018, 01:08 PM

Quote:

Originally Posted by ponce

if I remember correctly, regarding realtek 8139x cards, it tries to load the 8139too kernel module, while most of the hardware I encountered (physical or emulated) works with the 8139cp module (in some cases is the vice-versa).
another solution, in these cases, is to blacklist the former

Code:

echo "blacklist 8139too" > /etc/modprobe.d/rtl8139.conf

or, in alternative, the latter

Code:

echo "blacklist 8139cp" > /etc/modprobe.d/rtl8139.conf

and reboot.

I fought a little with virt-manager and slackware trying it with these modules. But if the OP is running virt-manager the easiest is probably to choose the e1000.

But you are completely right Ponce

it should work

agricola7 · 07-05-2018, 03:59 PM

Thank you for your replies. I have tried each of the the two blacklistings, but with no success.

agricola7 · 07-06-2018, 06:50 AM

How does one obtain and install e1000? My Slackware64 is running (without internet) in a virt-manager vm which cannot make contact with the outside world.

Melke · 07-06-2018, 07:00 AM

you can go into the settings of the virtual machine and change the network card to E1000. I made a screenshot:

https://imgur.com/a/rSUBfQ4

PhilipH · 07-07-2018, 03:00 PM

virtio should also work. Slackware 14.2 has the driver already installed. It should be somewhat faster as e1000.

agricola7 · 07-08-2018, 09:17 AM

Many thanks for the e1000 suggestion. It worked at once, and this comes by virtue of it.
Again, my thanks!

Melke · 07-08-2018, 09:36 AM

You're welcome