LinuxQuestions.org - [SOLVED] Internet connection problems on a fresh install of Slackware 14.1

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Internet connection problems on a fresh install of Slackware 14.1 (https://www.linuxquestions.org/questions/slackware-14/internet-connection-problems-on-a-fresh-install-of-slackware-14-1-a-4175537080/)

Internet connection problems on a fresh install of Slackware 14.1

Hi, there.
I have just recently installed Slackware 14.1 on my computer, and I am having troubles connecting my computer to the internet with the Ethernet cord. The Slack Book has been very helpful with the installation method but for networking I am at a standstill.

Here is what I did so far:
During the installation process I completed the procedure for the network setup and the computer is configured to DHCP, but that did not seem to work.
After the installation, I used the netconfig command to set up the network, but still no internet.
The book and much of the research I have done seem to point towards me editing the rc.inet1.conf. The problem is that I can't open the rc.inet1.conf to edit it. With the other "rc.’s" (the purple-coloured text files) in the /etc/rc.d/ folder, I was able to right click them and use either Emacs or Vi to edit them. Yet, when I right click the rc.inet1.conf I don’t see the option to launch it with Emacs or Vim. The icon even has a grey “X” on the corner. (It’s not even purple)
I also installed WICD from the fourth install CD which has the /etc/ folder, and there seemed to be some progress. When I restarted my computer after installing WICD, the network icon appeared on the taskbar. Unfortunately, there does not seem to be any connection even though the Ethernet cord is plugged into the computer.
If it helps, the computer in question is an old Dell Dimensions 2400 and I am running the Xfce desktop. I avoided using the third CD during installation because KDE is over kill for this old computer. The network card is a Broadcom 4401 Integrated NIC Rev AO3. Is my network card too old for Slackware 14.1?
What am I doing wrong?
I am sorry for sounding noobish; I tried to avoid Slackware on the advice of almost every site warning about its complexity, but I am now determined to make it work because the other distros I tried pale in comparison to Slackware when it comes to this troublesome computer. It runs like a dream and the firefox browser, although useless at this point, does not hang like it does on my newer laptops. The whole thing is like butter.
Thanks.

Ok, Thanks for the response. I followed the instructions from the link you sent me. Is there anything in particular I am supposed to make note of? Should I just find a way to post the whole response?

Ok, here is what I got. Sorry it took so long.

([ bash-4.2# source netdiag.ksh
bash: netdiag.ksh: No such file or directory
bash-4.2# source net-diag.ksh
bash: $'\r': command not found
uname
bash: $'\r': command not found
lspci
bash: $'\r': command not found
lsusb
bash: $'\r': command not found
lsmod
bash: $'\r': command not found
ifconfig
bash: $'\r': command not found
ifconfig -a
bash: $'\r': command not found
iwconfig
bash: $'\r': command not found
rfkill
bash: $'\r': command not found
iwlist
bash: $'\r': command not found
resolv.conf
bash: $'\r': command not found
route
bash: $'\r': command not found
ping router
ping dns server
ping using ip
ping using dns
bash: $'\r': command not found
==> /tmp/00-uname.schneidz <==
Linux dell 3.10.17-smp #2 SMP Wed Oct 23 17:13:14 CDT 2013 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux

==> /tmp/01-lspci.schneidz <==
01:09.0 Ethernet controller [0200]: Broadcom Corporation BCM4401 100Base-T [14e4:4401] (rev 01)
Subsystem: Dell Device [1028:8127]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fe9ee000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at fea00000 [disabled] [size=16K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: b44
Kernel modules: b44

==> /tmp/02-lsusb.schneidz <==
Bus 001 Device 002: ID 0951:1666 Kingston Technology
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

==> /tmp/03-lsmod.schneidz <==
Module Size Used by
usb_storage 36220 1
ipv6 246794 18
lp 7199 0
fuse 65066 5
i915 508710 2
b44 23779 0
video 10142 1 i915
drm_kms_helper 31358 1 i915
ssb 45260 1 b44
mmc_core 78434 1 ssb
mii 3335 1 b44
pcmcia 30709 1 ssb
drm 186279 3 i915,drm_kms_helper
mperf 919 0
pcmcia_core 10252 1 pcmcia
i2c_algo_bit 4575 1 i915
snd_intel8x0 23649 1
snd_ac97_codec 89231 1 snd_intel8x0
psmouse 72582 0
gpio_ich 3581 0
ppdev 4710 0
processor 24543 0
intel_agp 8680 1 i915
lpc_ich 11413 0
intel_gtt 10512 3 i915,intel_agp
shpchp 22189 0
thermal_sys 19013 2 video,processor
i2c_dev 4551 0
i2c_i801 12393 0
i2c_core 17388 6 drm,i915,i2c_i801,i2c_dev,drm_kms_helper,i2c_algo_bit
parport_pc 16728 1
agpgart 22075 3 drm,intel_agp,intel_gtt
freq_table 2176 1 thermal_sys
serio_raw 3545 0
hwmon 1021 1 thermal_sys
dcdbas 4287 0
evdev 7552 5
snd_pcm 62870 2 snd_ac97_codec,snd_intel8x0
parport 25305 3 lp,ppdev,parport_pc
uhci_hcd 19872 0
snd_page_alloc 6062 2 snd_intel8x0,snd_pcm
snd_timer 14870 1 snd_pcm
snd 44159 6 snd_ac97_codec,snd_intel8x0,snd_timer,snd_pcm
soundcore 4318 1 snd
ac97_bus 834 1 snd_ac97_codec
ehci_pci 2980 0
ehci_hcd 34699 1 ehci_pci
microcode 8880 0
button 3704 1 i915
loop 14786 0

==> /tmp/04-ifconfig.schneidz <==
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:0f:1f:59:7c:c8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

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 0 (Local Loopback)
RX packets 12 bytes 736 (736.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 736 (736.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

==> /tmp/05-ifconfig-a.schneidz <==
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:0f:1f:59:7c:c8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

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 0 (Local Loopback)
RX packets 12 bytes 736 (736.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 736 (736.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

==> /tmp/06-iwconfig.schneidz <==
lo no wireless extensions.

eth0 no wireless extensions.

==> /tmp/07-rfkill.schneidz <==
Can't open RFKILL control device: No such file or directory

==> /tmp/08-iwlist.schneidz <==
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

==> /tmp/10-route.schneidz <==
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

==> /tmp/11-ping-router.schneidz <==
Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I interface]
[-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
[-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option]
[-w deadline] [-W timeout] [hop1 ...] destination

==> /tmp/12-ping-dns-server.schneidz <==
Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I interface]
[-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
[-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option]
[-w deadline] [-W timeout] [hop1 ...] destination

==> /tmp/13-ping-using-ip.schneidz <==
connect: Network is unreachable}])

Not sure how to do the code tag, Sorry.

Did you perform a full install? It seems you are missing a lot of stuff (all those "Command not found")

bopeetion,
Some of the commands in the script made by schneidz reqiuire root privileges.
I would not go this route.
The first thing you want to do is make sure /etc/rc.d/rc.wicd is executable.

Code:

chmod +x /etc/rc.d/rc.wicd

Then go like this:

Code:

/etc/rc.d/rc.wicd start

Just like that as root.
As for your onboard NIC, you can find all you need to know about it from lspci.
Broadcom is generally troublesome with Linux, but I'd be really surprised if the BCM4400
driver wasn't in the kernel by now.

Quote:

Originally Posted by moisespedro (Post 5333810)

Did you perform a full install? It seems you are missing a lot of stuff (all those "Command not found")

Hmm, I barely touched anything during the installation. The only thing I did was that I unchecked the KDE environment. As a result, I only used the first two disks. I checked the md5 and the checksums matched.

Quote:

Originally Posted by STDOUBT (Post 5333811)

bopeetion,
Some of the commands in the script made by schneidz reqiuire root privileges.
I would not go this route.
The first thing you want to do is make sure /etc/rc.d/rc.wicd is executable.

Code:

chmod +x /etc/rc.d/rc.wicd

Then go like this:

Code:

/etc/rc.d/rc.wicd start

I followed your instructions and the response was "WICD appears to already be running". "If this is not the case, then remove /var/run/wicd.pid and try again"

I restarted the computer just to be sure, but there has not been any changes.

I used your Lpci command and the network card is listed.

Quote:

bash: $'\r': command not found

Quote:

==> /tmp/01-lspci.schneidz <==
01:09.0 Ethernet controller [0200]: Broadcom Corporation BCM4401 100Base-T [14e4:4401] (rev 01)
Subsystem: Dell Device [1028:8127]
...
Kernel driver in use: b44
Kernel modules: b44

This is your network device and the required kernel module is being loaded.

Quote:

==> /tmp/04-ifconfig.schneidz <==
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

This shows that your network device is up and running.
However, there is no network address assigned to the device. This suggests there is a problem with DHCP. (Also confirmed by the Kernel IP routing table.)
From the email to root titled " Welcome to Linux (Slackware 14.1)! "a

Quote:

With NetworkManager or wicd, it's
a good idea to remove any existing network configuration in
/etc/rc.d/rc.inet1.conf first. This can be done by running netconfig
and setting the machine to use loopback.

Quote:

Originally Posted by bopeetion (Post 5333812)

seems like ms-windows copy-pasta errors beacause of the carriage-returns (the programs did actually run -- next time please use [code] tags (highlight the text and clik on the # sign) since it will be easier to read a formatted wall of text).

edit: ^ jinx allend.

Quote:

Originally Posted by allend (Post 5333998)

Those errors suggest that the script posted by schneidz has been copied and pasted using Windows, which has introduced CRLF line endings in place of the Linux LF line endings. The additional CR is the \r that you see.

This is your network device and the required kernel module is being loaded.

This shows that your network device is up and running.
However, there is no network address assigned to the device. This suggests there is a problem with DHCP. (Also confirmed by the Kernel IP routing table.)
From the email to root titled " Welcome to Linux (Slackware 14.1)! "a

You are correct. I made the script in Windows by copy/pasting the source into Notepad and changing the file type from .txt to .ksh, then I moved the file to the desktop through a usb drive. I didn't know that would affect it much.

Was I supposed to set it to loopback? I just did but it did not seem to do the trick. Is there anything I am missing?

Hi,

Welcome to LQ & Slackware!

You should look at: Slackware Doc Project links;

Quote:

Slackware installation: a guide through the whole process of installing and configuring Slackware Linux; written for new and experienced users alike.

Configure your new Slackware System; how to proceed after the installation has completed.

Quote:

Originally Posted by onebuck (Post 5334103)

Hi,

Welcome to LQ & Slackware!

You should look at: Slackware Doc Project links;

Hi, thanks for the response. I stated in the original post that I already looked through those documents and I have yet to find a proper solution to my problem. Sorry.

Hi,

Quote:

Originally Posted by bopeetion (Post 5334117)

Hi, thanks for the response. I stated in the original post that I already looked through those documents and I have yet to find a proper solution to my problem. Sorry.

Sorry!

I re-read the OP and still do not see references to Slackware Doc Project

Just references to SlackBook which is now linked;

Quote:

The Slackware Linux Essentials Book: a valuable resource for those venturing into Slackware (or Linux in general) for the first time. The original SlackBook can be found on your Slackware CDROM or DVD, and it can also be read online: http://slackbook.org/beta/

You could also look at the SlackBook Beta

Please note if you are using network manager or wicd then you should revert '/etc/rc.d/rc.inet1.conf' to original state;From http://docs.slackware.com/slackware:beginners_guide

Quote:

Graphical Network Configuration Services

Slackware currently has some alternatives to configure and monitor your network connections. These install a daemon (aka a background service) which will allow you to switch between wired and wireless connections easily. That makes them perfectly suited for mobile users. They come with graphical configuration utilities and do not depend on the traditional Slackware configuration files - in fact, those files will cause conflicts if they contain network configuration.

You will find wicd in the extra section of the Slackware release tree (the word extra means that it is not part of the core distribution and will not have been installed as part of a full installation).
After installing the wicd package, you have to make its init script executable so that the network daemon automatically starts at boot: # chmod +x /etc/rc.d/rc.wicd You can then configure your network using the graphical tool wicd-client or if you are running Slackware 14 you can use the KDE widget for wicd instead. For console lovers, there is also wicd-curses which offers the same configuration capabilities as the X-based counterparts.
Starting with Slackware 14, there is also Networkmanager. It will be installed as part of a full install, but the network daemon will not be started by default. As with wicd, you have to make its init script executable: # chmod +x /etc/rc.d/rc.networkmanager which will make NetworkManager start at boot. You will have to configure NetworkManager using an X-based graphical utility.
Slackware 14 includes a KDE widget for Networkmanager. If you are using another Desktop Environment like XFCE, you can install the Gnome network-manager-applet from SlackBuilds.org

Hope this helps.
Have fun & enjoy!
:hattip:

Quote:

Originally Posted by onebuck (Post 5334133)

Hi,

Sorry!

I re-read the OP and still do not see references to Slackware Doc Project

Just references to SlackBook which is now linked; You could also look at the SlackBook Beta

Please note if you are using network manager or wicd then you should revert '/etc/rc.d/rc.inet1.conf' to original state;From http://docs.slackware.com/slackware:beginners_guideHope this helps.
Have fun & enjoy!
:hattip:

If you misunderstood my original post, then I apologise for being vague. When I stated I did some research over the web that research, that includes the solution you provided in your second quote. In fact, I installed WICD after going through the source material you provided; i already used it before I made this thread. The problem is that WICD options in all of the tabs are all greyed out and there does not seem to be any room for edit, and yes I also entered that command in your quote. The KDE option is a no go because the computer can not handle KDE. (256MB ram)

I was under the assumption that it maybe the router/modem combo I got from my ISP, so I borrowed my neighbour's modem to test this out, but the problem persists.

Thanks.