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.
I've been seing an odd problem with my pcmcia NIC since I installed Slack. It starts out working fine, dhcp assigns and IP nice and quick and everything works fine.
At some point, after a boot up or two, the NIC stops getting an IP from dhcp when I boot up and my dsl modem/router resets itself. I know it isn't any sort of hardware problem because I don't see it using another *nix such as Gentoo or Mepis LiveCD.
Something to do with the net config or dhcp is changing but I can't seem to determine what it is or what causes it. I've reinstalled Slack three times now as it seems to be the only way to fix the problem. I refuse to reinstall again as it's just stupid to keep having to do that.
Someone must have an idea what's causing this weird behavior or at least where to start looking for it. I've checked the net related config files and rc.d files but don't see anything obvious.
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Rep:
I dual boot with Fedora Core. Fedora Core picks up my NIC and configures my DSL modem fine, but I don't think it closes the connection. So, if I reboot into Slackware it work fine.
Frustrating to have to do this to get online with Slack.
The deleting files that you mentioned, do you have to delete these same files every time you shutdown Slack so that you can get online the next time you boot?
I have a similar problem. Slackware 10.1 sees my nic just fine. I set a static ip on it. I can send maybe 30 packets before it drops the connection altogether. I cant ping any machines on the network and all tcp functions are useless. I reboot the box, I get a connection for a bit and than it just loses connection again. Nothing in messages or any other log file I can look through. I have no idea why its happening.
Have figured some of it out. The connection problem only happend when i shut down or reboot teh machine. Connection is fine when I shut down. next time I start the machine it can't connect until I delete the cache and info files. The pid was a fluke, it's usually not there when inactive.
For some reason, the dhcpcd isn't releasing the lease upon shut down as near as I can tell so the only way to restart the connection is to stop pcmcia, delete the cache and info files in /etc/dhcpc and then restart pcmcia. What a pain.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.