LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Major Slackware Installation Whine re Networking (https://www.linuxquestions.org/questions/slackware-installation-40/major-slackware-installation-whine-re-networking-4175654694/)

Captain Brillo 05-27-2019 07:28 PM

Major Slackware Installation Whine re Networking
 
So after 20 years I'm taking another whack at getting Slackware up and running. Back then, it was all hardware issues - didn't have the bucks to do anything about it then.

This time, I cannot get Slackware's networking up and running. No other apparent install issues. Umpteen-gazillion attempts - and I don't understand why.

I've gone through the Slack-Docs, the Slack Book, multiple Linux forums, yada yada yada. Even my searches of this site have come up empty (- but I'm now used to my choice of search terms comin' up empty.)

Need help, folks. And I'm now so confused, I no longer no where to start fixing this. Without networking, I have to reboot for every last bit of info - no other boxes available nearby to get online with while I try this.

I have no problem with networking, per se. I have the modem/router set up to lease IPs forever, (for now, to avoid DHCP leasing being a problem). Works fine with all other distros I've tried.

I've tried a static IP. Works fine with all.....

Everything I've tried works with other distros, but NOT Slack. The issue is that I can't find any distros other than Mint 18 that will work acceptably on this box. They all SUCK big-time, (even and especially Mint 19 - which just won't function without crashing) - and this is a Lenovo box on the "famous" Ubuntu Hardware List. (And I'll do without a PC if I have to use Windows.) I've also run every hardware test I can find on this box - it's good.

Can somebody come onboard and help me with this?

frankbell 05-27-2019 07:40 PM

If you are interested in some assistance, please provide some information.

When I did the Slackware install, did you do the bit about setting up you network? (I'm assuming you did.)

Are you referring the wired or wireless networking? Please provide information about your network adaptor(s).

If wired, did you use a known-good cable?

What is the output of the command ip addr?

cwizardone 05-27-2019 08:33 PM

Run, as root, netconfig
and choose to have NetworkManager setup you network "automatically."
That should do it.

bassmadrigal 05-28-2019 01:01 PM

If cwizardone's suggestion doesn't work, we would need more info like frankbell mentioned. To start (and I'll reask some questions he did), how are you connecting to the network? Is it wired or wireless? And is your device recognized properly by Slackware? Providing the output of the following three commands could help with diagnosing:

Code:

lspci -k | grep -iA3 net
ifconfig
iwconfig

And you said you did set a static IP, have you tried with a DHCP? Sometimes static can cause issues if there's a conflict on the network or things like the route weren't set up.

johnmeehan 05-28-2019 01:39 PM

Slackware does not work and play well with some Broadcom cards.

If you have a Broadcom card my suggestion would be to check the SlackBuild site and if you cannot find something there that solves the problem use ndiswrapper.

I AM NOT A SLACKWARE EXPERT, merely a novice trying to help.

Richard Cranium 05-29-2019 02:44 PM

The version of Slackware that you installed would also be an important bit of information.

gus3 06-03-2019 09:52 PM

Realtek 8139 Ethernet chipsets are also known to be flaky under load. (An old version of the FreeBSD driver had a comment in the source code that the 8139 chipset "brings new meaning to the term 'low-end'." Ouch.)

Captain Brillo 06-08-2019 11:58 AM

Sorry -delayed getting back to this, and thanks for the replies...

First, as root, I ran netconfig and set to automatic. (I know I did this in the install, too...)
And then I ran lspci as suggested, with ifconfig and iwconfig, which I'll post below.
Now at startup it connects to Ethernet card and immediately disconnects, starting a loop of connect/disconnect.
Did a Duckduckgo search for "+linux network connects then disconnects immediately" but got nothing helpful (that I could see)

Code:

bash-4.3# lspci -k | grep -iA3 net
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
        Subsystem: Lenovo 82579LM Gigabit Network Connection
        Kernel driver in use: e1000e
        Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
bash-4.3# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.10  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::221:86ff:fe28:4f88  prefixlen 64  scopeid 0x20<link>
        inet6 fd00:30b7:d4ff:d1d2:221:86ff:fe28:4f88  prefixlen 64  scopeid 0x0<global>
        inet6 2607:fea8:61f:fb99:221:86ff:fe28:4f88  prefixlen 64  scopeid 0x0<global>
        ether 00:21:86:28:4f:88  txqueuelen 1000  (Ethernet)
        RX packets 8  bytes 2091 (2.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 21  bytes 2649 (2.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7c00000-f7c20000 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 420  bytes 35568 (34.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 420  bytes 35568 (34.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
bash-4.3# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

bash-4.3#


Captain Brillo 06-08-2019 12:56 PM

Ok, got it.
Did another search and found my solution here at LQ.

Edited /etc/NetworkManager/conf.d/00-dhcp-client.conf
to
dhcp=dhcpclient

Network is working.


All times are GMT -5. The time now is 06:15 AM.