Hello, I’m new to Linux. I spent sometime researching best Linux OS and found openSUSE to have better ratings, so I decided to install it. So, now I have openSUSE 12.1-KDE on my computer. I’ve dual OS [Win XP SP3 and openSUSE 12.1] on my desktop [Dell Dimension E310]. I tried YaST > Network Settings > Configure the my home wireless router options and typed in my IP address and wireless password and everything, and still it shows that I’m not connected to the internet! When I boot using Windows, the internet works fine, but I haven’t been able to configure the internet using openSUSE.
but it lists everything other than the “14e4:xxxx” PCI-ID codes (PCI model). So, I haven’t still figured out how to proceed further.
So any help (step-wise) will be appreciated! Thanks.
On 04/30/2012 04:56 PM, ap1985 wrote:
>
> Hello, I’m new to Linux. I spent sometime researching best Linux OS and
> found openSUSE to have better ratings, so I decided to install it. So,
> now I have openSUSE 12.1-KDE on my computer. I’ve dual OS [Win XP SP3
> and openSUSE 12.1] on my desktop [Dell Dimension E310]. I tried YaST>
> Network Settings> Configure the my home wireless router options and
> typed in my IP address and wireless password and everything, and still
> it shows that I’m not connected to the internet! When I boot using
> Windows, the internet works fine, but I haven’t been able to configure
> the internet using openSUSE.
>
> I have a Cisco-Linksys WMP54G Wireless-G PCI Adapter wireless card on
> my desktop [http://tinyurl.com/c38zaul. I researched further and found
> out that my wireless card is a Broadcom type and have to do some
> tweaking to successfully configure my internet on openSUSE. I tried few
> commands on the terminal [as suggested by
> http://linuxwireless.org/en/users/Drivers/b43], such as:
>
> Code:
> --------------------
> /sbin/lspci -vnn -d 14e4:
> --------------------
>
> but it lists everything other than the “14e4:xxxx” PCI-ID codes (PCI
> model). So, I haven’t still figured out how to proceed further.
> So any help (step-wise) will be appreciated! Thanks.
That command should be “/sbin/lspci -nn | grep 14e4”.
Have you installed the b43 firmware? If not, the command is
sudo /usr/sbin/install_bcm43xx_firmware
For that command to execute correctly, you will need to have a network
connection by wire. If that is not possible, then report back and we will work
out the process.
Is there an alternative to wired connection… a website where i can download this firmware from Windows and copying it to openSUSE on a USB drive? I tried to google it, but couldn’t fine one!
On 04/30/2012 08:36 PM, ap1985 wrote:
>
> Is there an alternative to wired connection… a website where i can
> download this firmware from Windows and copying it to openSUSE on a USB
> drive? I tried to google it, but couldn’t fine one!
so, since the command “/sbin/lspci -nn” gave an output “03:01.0 Network controller [0280]: Ralink corp. RT2500 802.11g [1814:0201] (rev 01)”, the firmware link download instructions that you posted earlier wouldn’t work, right?
>
> After playing for few minutes with the above command, I got an output:
>
> Code:
> --------------------
> 03:01.0 Network controller [0280]: Ralink corp. RT2500 802.11g
> [1814:0201] (rev 01)
> --------------------
>
>
> So, it seems like my wireless card is Ralink and not Broadcom type. So,
> what should I do next now?
>
>
Use NetworkManager applet (that depends on the desktop You’re using) or go
with static ifup and use YaST.
On 04/30/2012 09:26 PM, ap1985 wrote:
>
> so, since the command “/sbin/lspci -nn” gave an output “03:01.0 Network
> controller [0280]: Ralink corp. RT2500 802.11g [1814:0201] (rev 01)”,
> the firmware link download instructions that you posted earlier wouldn’t
> work, right?
That is right. You use the rt2500pci driver. Look at the output of the dmesg
command to see if it found the firmware. If not, you will need the
kernel-firmware package.
While I am very pleased that you find out about the CODE tags and that you use them, IMHO it would be better to show the command and it’s output complete from prompt to prompt, like:
boven:~ # /sbin/lspci -nn | grep 14e4
boven:~ #
This does show to advantage that you get “no output” without the need of saying so. It also shows (not very important in this case, but it may be for other commands) that I was root doing this and what my working directory was doing this.
On 05/01/2012 07:16 PM, ap1985 wrote:
>
> Here is the dmesg output:
>
>
> Code:
> --------------------
> ap1985@linux-71ux:~>dmesg | grep rt2500pci
> 11.233999] rt2500pci 0000:03:01.0: PCI INT A → GSI 17 (level, low) → IRQ 17
> 11.260816] Registered led device: rt2500pci-phy0::radio
> 11.260900] Registered led device: rt2500pci-phy0::quality
> --------------------
>
>
> Here’s what I found on Google:
>
> ‘Install Serial Monkey Drivers for RT2x00 Wireless cards in openSUSE
> 10.3& 11 | SUSE& openSUSE’ (http://tinyurl.com/7qcrtv2)
>
> ‘Bonrom’ (http://bonrom.cbbknet.com/)
>
> I’m wondering which one to download and I can follow the directions as
> outlined on susegeek link above.
Did you notice the ages of those versions of openSUSE? Would you follow
instructions for Windows ME for a problem with Win 7?
The driver is built in NOW. Do not use any out-of-kernel solution!
On 05/02/2012 08:16 PM, ap1985 wrote:
>
> I apologize to keep bothering you, but if the driver is inbuilt, why
> isn’t my computer connecting to my wireless internet?
Either you don’t have the correct firmware installed, or you are not configuring
it correctly.
OK. My LAN (wired internet connection) works fine… just the wireless isn’t working… are you aware of any specific firmware that I need to install? and the procedure to download/save the firmware to a specific location??
On 05/05/2012 01:06 AM, ap1985 wrote:
>
> OK. My LAN (wired internet connection) works fine… just the wireless
> isn’t working… are you aware of any specific firmware that I need to
> install? and the procedure to download/save the firmware to a specific
> location??
If you look at the output of the dmesg command, you will see messages about
firmware failures and the name of files needed. Most firmware is included in the
kernel-firmware package. Use YaST to verify that it is available.