SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Fresh install, used netconfig to set up dhcp, and dhcpcd gives the message:
Code:
dhcpcd[2026]: version 5.5.6 starting
dhcpcd[2026]: wlan0: up_interface: No such file or directory
dhcpcd[2026]: no interfaces have a carrier
dhcpcd[2026]: forked to background, child pid 2063
ifconfig doesn't show a connection on eth0 even though eth0 is up, but does have the loopback connecting to 127.0.0.0 like it should.
Contents of /etc/rc.d/rc.inet1.conf
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
GATEWAY=""
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"
The rest of the file is commented out examples and explanations.
Not sure where to go from here.
EDIT: Turns out it was the ethernet cable I was using. I tested the cable on another computer and was able to connect with it, so I figured the cable was fine, but I thought I should test a new cable anyway. I ran a new line from the junction switch to my laptop and it works, so it had to be something with the old cable.
Thanks for all the help
Last edited by slacker_; 09-16-2013 at 09:11 PM.
Reason: Edit #1: Had to add rc.inet1.conf info. Edit #2: Solved thread
What appears if you run "ifconfig -a" to show all interfaces.
This controller is a wired card, isn't it? Would appear as eth0.
It shows all my interfaces all right. But eth0 doesn't have any connection at all. I see the hardware address, and the device is up, but it's not connecting.
Quote:
Originally Posted by slacktroll
what about
killall -9 dhcpcd
dhcpcd eth0
i've had what you describe myself
This returns the following:
Code:
dhcpcd[3351]: open_control: Connection refused
dhcpcd[3351]: version 5.5.6 starting
dhcpcd[3351]: eth0: waiting for carrier
dhcpcd[3351]: timed out
dhcpcd[3351]: allowing 8 seconds for IPv4LL timeout
dhcpcd[3351]: timed out
I think that if "ifconfig" doesn't show eth0 and "ifconfig -a" shows, eth0 isn't up.
Code:
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
Code:
wlan0: flags=4098<BROADCAST,MULTICAST> mtu 1500
There is an UP if interface is up (this is my wireless card, I'm not using it right now)
Try "ifconfig eth0 up", then slacktroll's commands.
There is Wicd in X, I use it to setup my connections.
ifconfig and ifconfig -a both show eth0, they both show the device as up. How did you get that it didn't show in ifconfig?
The device is UP, the rc.inet.conf is set up for dhcp, dhcpcd command is timing out. That is where I'm at right now.
Also, I'm using primarily cli right now until I get the networking fixed. Wireless is an entirely different problem I'm having (go back through my threads if you'd like to see that), currently I'm just worried about getting my wired connection working.
Since the card is up, doesn't look like a driver problem.
Try to set ip manually, an ip from dhcp network not in use.
I think that this is the command
Code:
ip addr add ip/mask dev eth0
See if ip was assigned "ifconfig" or "ip addr show"
Set to 192.168.1.245, ifconfig shows it as 192.168.1.245. Now how do I take this info and use it to connect to my network? I'm not network admin, but the network is setup to accept any new connection and assign it an address with dhcp so it's definitely not network side.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Try to ping the gateway (maybe 192.168.1.1), if all packets reach the gateway then ok,
you must be connected to the machine that has the dhcp server.
If not, try adding a route. It would be done with "ip" command, but I don't know how,
so I will paste the "route" command.
Code:
route add -net 192.168.1.0/24 gw 192.168.1.1
(is mask 255.255.255.0 ?)
The fact that there is a dhcp server doesn't exclude manual setup, it will accept connections
if you put an ip from the same network. The only care is not use someone's ip.
Is this your thread about wireless? http://www.linuxquestions.org/questi...hy-4175474924/
I have an HP Compaq with Broadcom onboard, but unfortunately video chipset has died.
I installed Slackware 13.37 and it worked with b43 driver, but this was a year and a half ago,
I don't remember if it worked right out of the box or with some tweak.
Last edited by Paulo2; 09-16-2013 at 07:38 PM.
Reason: make some phrases more clear ( and excuse me my English :)
Try to ping the gateway (maybe 192.168.1.1), if all packets reach the gateway then ok,
you must be connected to the machine that has the dhcp server.
If not, try adding a route. It would be done with "ip" command, but I don't know how,
so I will paste the "route" command.
Code:
route add -net 192.168.1.0/24 gw 192.168.1.1
(is mask 255.255.255.0 ?)
The fact that there is a dhcp server doesn't exclude manual setup, it will accept connections
if you put an ip from the same network. The only care is not use someone's ip.
Is this your thread about wireless? http://www.linuxquestions.org/questi...hy-4175474924/
I have an HP Compaq with Broadcom onboard, but unfortunately video chipset has died.
I installed Slackware 13.37 and it worked with b43 driver, but this was a year and a half ago,
I don't remember if it worked right out of the box or with some tweak.
I'm still getting this:
Code:
connect: Network is unreachable
Yes, that's my wifi thread. I was really hoping to get 14 working, but I could probably try 13.37 and see if it works.
EDIT: Issue solved I tested the ethernet cable on another computer and it worked fine so I figured it couldn't be the cable, but I ran a new cable for my laptop and it I can now connect to the network. So it's something to do with the old cable. Thread marked solved. Thanks for all the help!
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Maybe a straight cable instead of crossover one?
Code:
Yes, that's my wifi thread. I was really hoping to get 14 working, but I could probably try 13.37 and see if it works.
About the wireless problem, I just remembered of something about pcmcia cards
being configured by another script, and searching I found that actually this
is only for 16-bit pcmcia, not 32-bit.
13.37 worked for me, but the notebook broke before I could upgrade to 14.
I saw that you tested some other kernel versions, maybe upgrading
to -current bring some results.
Both are crossover, so I think one of the wires in the old cable might've pinched off or something.
Quote:
Originally Posted by Paulo2
About the wireless problem, I just remembered of something about pcmcia cards
being configured by another script, and searching I found that actually this
is only for 16-bit pcmcia, not 32-bit.
What do you mean "This is only for 16bit pcmcia" ?
Quote:
Originally Posted by Paulo2
13.37 worked for me, but the notebook broke before I could upgrade to 14.
I saw that you tested some other kernel versions, maybe upgrading
to -current bring some results.
The kernel I'm trying to use is 3.10.11 (currently having to compile it). Is 'current' beyond 3.10*?
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
What do you mean "This is only for 16bit pcmcia" ?
I mean the different place for configuration.
This is from /etc/rc.d/rc.wireless
Quote:
#!/bin/sh
# /etc/rc.d/rc.wireless
# $Id: rc.wireless,v 1.13 2007/04/13 14:14:43 eha Exp eha $
#
# Wireless network card setup.
#
# This script sets up PCI, USB, and 32-bit Cardbus wireless devices
# NOT 16-bit PCMCIA cards! Those are configured in /etc/pcmcia/.
# Single parameter to this script is the name of a network interface.
# Normally this script is called from rc.inet1 rather than run
# directly.
That configuration for 16-bit pcmcia is too old I think, makes reference
to ISA bus and interrupts (maybe those ISA cards that are not plug and play,
you have to configure interrupt and IO ports manually).
Quote:
The kernel I'm trying to use is 3.10.11 (currently having to compile it). Is 'current' beyond 3.10*?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
(this is my wireless card, I'm not using it right now)
