I just got a new laptop: dell vostro 1320 and it comes with hardware networking hardware(from lspci command):
broadcom corp BCM4312 802.11b/g.
From reading on this website, i discovered i had to download some drivers, but to do this (following the directions) I need to be connected to the internet. I assumed this meant just use a wired connection while i set up the wireless. But, for some reason, i cant even get a wired connection to work (i am sure that it isnt a problem with the internet since the same wire works in a pc.
So, i tried to download the drivers manually and install the rpm package, but i still cant seem to get either to work…
if i use yast to view the network setting, it shows an ethernet network card and RTL111/8168B pci express ethernet controller. So, i am assuming it is finding them (??).
Anyways, i dont consider myself a complete linux noob (using opensuse on this laptop, used to use ubuntu on my old one), but i am at a complete loss about this.
i cant even get the wired connection to work. When i plug it in to a known working wired connection, it still doesnt work. If i type ifconfig, it only recognizes the local loopback (even when plugged in). I did install the drivers from the dell driver cd that it came with. Restart the laptop with the wired connection in. The light on the ethernet port it on. I really dont know why it wouldnt be working…
> Ok, thanks for the redirection to that sticky - was very informative. So
> at this point im pretty confident that i could get my wireless working
> if i could get my wired connection working…
> I think this thread might be in the wrong forum, if it is, please move
> it to the appropriate one.
> Im at a loss as to why the wired connection isnt working… does anyone
> have any suggestions? Could it be a driver issue like the wireless?
It coud be. What version of openSUSE are you using, and what hardware
do you have? Without these answers, we have no ideas.
That one should work using the r8169 driver. What does the command
‘lsmod | grep r8169’ show?
One problem with these devices is that Windows turns the device off,
and the Linux driver cannot turn it on again. Once way around this is
to go into your BIOS and turn on Wake-on-Lan. Once you do that,
Windows will no longer shut it down, and the Linux driver can use it.
> The result of that command:
> r8169 31388 0
> mii 6024 r8169
> Im sorry, i have no clue what this means.
> I will give that bios suggestion a shot.
The command lsmod lists the modules (aka drivers) that are loaded.
Your output says that r8169 is loaded, and has a size of 31,388 bytes.
The next line says that r8169 uses mii - that is for setting the link
> Ok, one last little problem:
> when i run the install_bcm43xx_firmware command, it installs the b43
> firmware, but fails on the b43 legacy:
> Downloading b43legacy firmware
> curl: (7) couldn’t connect to host
> Could not download b43legacy firmware. Please look at
> b43 firmware successfully installed.
> b43legacy firmware installation failed.
It is quite unlikely that you need the b43legacy firmware. That is for
very old hardware, which excludes you.
Look at the output of the command
and find the section that describes your wireless. Post that part, and
that part only. Do NOT post the entire output!!!
> well… I turned on my laptop this morning, and the wired connection no
> longer works.
> The output of lsmod | grep r8169 is blank, and network manager no
> longer recognizes eth0(nic).
> I tried reformatting, and going through the same steps again, to no
> avail. wake-on-lan is still enabled in the bios.
> Could this be a hardware issue?
Does lspci show it? If not then there is a hardware problem. If lspci
shows it, but the module is not loaded, then there is a software problem.