Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
11-13-2013, 04:20 AM
|
#16
|
Member
Registered: Feb 2003
Location: Almere, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep: 
|
if you can ping your router, than you will need to check your router config.
because your network works.
so it would leave 2 options.
1: router config is wrong (the wireless part)
2: your route is wrong.
|
|
|
11-13-2013, 10:02 AM
|
#17
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Original Poster
Rep:
|
My router config is fine. I initially upgraded this machine over the network via slackpkg, and haven't changed anything in my router config since. There are 3 other devices at home that connect through the router, and they are all working as expected.
I'm going to try downgrading to 14.0 tonight to see what happens.
|
|
|
11-13-2013, 10:48 AM
|
#18
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Original Poster
Rep:
|
Actually, here's an interesting piece to add to the puzzle. I'm at work (so different network), on my work laptop, which is running 14.0, and ping is behaving the same way. I can ping the name servers listed in /etc/resolv.conf, but not 8.8.8.8. I also am unable to ping google, via either domain name or ip address. But, I can browse to google.com as expected using my browser.
Now I'm really confused...
|
|
|
11-13-2013, 01:22 PM
|
#19
|
Member
Registered: Jun 2010
Distribution: Slackware Current 64 bit KDE 5
Posts: 380
Rep:
|
It looks like both your wireless and ethernet cards are from Broadcom. I also have the broadcom wireless card as you (the 4312). I'm at work right now and doin't have the link, but when I get home I can point you in the right direction for getting your wireless card set up. Another patch is required to get the 4312 wireless drivers working starting with kernels 3.8 and later. It looks like broadcom also released new drivers for the ethernet card (see link below), but I do not have any experience with the broadcom ethernet cards. So I am not sure how to get that working yet. I'll do some more research when I get home.
http://www.broadcom.com/support/ethe...ic/netlink.php
|
|
1 members found this post helpful.
|
11-13-2013, 01:43 PM
|
#20
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Original Poster
Rep:
|
Quote:
Originally Posted by Bertman123
It looks like both your wireless and ethernet cards are from Broadcom. I also have the broadcom wireless card as you (the 4312). I'm at work right now and doin't have the link, but when I get home I can point you in the right direction for getting your wireless card set up. Another patch is required to get the 4312 wireless drivers working starting with kernels 3.8 and later. It looks like broadcom also released new drivers for the ethernet card (see link below), but I do not have any experience with the broadcom ethernet cards. So I am not sure how to get that working yet. I'll do some more research when I get home.
http://www.broadcom.com/support/ethe...ic/netlink.php
|
Thanks for the tip about the updated driver, I'll try that out when I get home tonight. I haven't even looked at wireless yet, one thing at a time I guess.
|
|
|
11-13-2013, 07:35 PM
|
#21
|
Member
Registered: Jun 2010
Distribution: Slackware Current 64 bit KDE 5
Posts: 380
Rep:
|
Quote:
Originally Posted by mattca
Thanks for the tip about the updated driver, I'll try that out when I get home tonight. I haven't even looked at wireless yet, one thing at a time I guess.
|
Since it looks like your ethernet card is a broadcom card as well the only thing I can think of (that makes sense to me anyway) is the new driver on their website. Not having a broadcom ethernet card I'm not sure if it would use the same drivers as the wireless. Probably not that lucky, but at least if you were able to get the wireless working that would give us an idea where the problem might be.
For the wireless drivers check out this post: ( http://www.linuxquestions.org/questi...53#post5032753) as it doesn't look like the slackbuild was updated yet with the new driver.
Which kernel are you using? I use the huge kernel as I had issues with getting my wireless card to work with the generic kernel.
|
|
1 members found this post helpful.
|
11-14-2013, 06:29 AM
|
#22
|
LQ 5k Club
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,526
|
Quote:
07:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
|
That device is supported by the tg3 kernel module.
|
|
|
11-14-2013, 06:46 AM
|
#23
|
Senior Member
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,160
Rep: 
|
I notice that you have ipv6 configured (inet6). Try disabling that. I've had issues in the past where ipv6 and ipv4 conflict, and disabling ipv6 restored normal operation.
Did you have ipv6 configured in your previous (working) installations?
|
|
|
11-14-2013, 01:24 PM
|
#24
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Original Poster
Rep:
|
Quote:
Originally Posted by pchristy
I notice that you have ipv6 configured (inet6). Try disabling that. I've had issues in the past where ipv6 and ipv4 conflict, and disabling ipv6 restored normal operation.
Did you have ipv6 configured in your previous (working) installations?
|
Thanks for the suggestion, I'll try that.
As an update, I reistalled 14.0 last night and am seeing the same issue with my wired connection. So, it's not something new to 14.1. I seem to recall that when I installed 14.0 on this machine I got the wireless working, but don't think I ever tried the wired connection. So perhaps it's something that was introduced in 14.0? Maybe if ipv6 was enabled by default starting in 14.0 that would explain it. Or the new device driver.
In any case, over the weekend I'll reinstall 14.1 and try some of the new suggestions here.
|
|
|
11-15-2013, 06:37 PM
|
#25
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Original Poster
Rep:
|
Another update... I've gotten the wireless to work using the broadcom-sta slackbuild for 14.0, and the patch linked in this thread:
http://www.linuxquestions.org/questi...-a-4175473176/
No luck on the wired, but I pretty much never use it anyway so I'm calling this solved.
Thanks for the help everyone, now to enjoy 14.1!
Edit: I also added this to my module blacklist:
# lets see if this helps my internet issue
blacklist ipv6
# Deprecated BCM4318 driver.
blacklist bcm43xx
# user-added wireless modules
blacklist b43
blacklist b43legacy
blacklist bcma
blacklist ssb
blacklist brcmsmac
blacklist brcmfmac
Last edited by mattca; 11-15-2013 at 06:40 PM.
|
|
|
All times are GMT -5. The time now is 01:20 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|