Mailinglist Archive: opensuse (2532 mails)

["A. den Oudsten" <AdenOudsten@xxxxxx>]

Ed Harrison wrote:

> A. den Oudsten wrote:
>
> > Mark Misulich wrote:
> >
> > > A. den Oudsten wrote:
> > >
> > > > I want to connect my Aspire 5315, provided with an Ethernet Network 
> > > > Card,
> > > > In Vista it's no problem but in suse 10.3 I miss a Yast module for 
> > > > such a job.
> > > > Can anybody tell me the steps I have to take to come to a solution?
> > > > I'm a user of OpenSUSE sinds long, but no developer.
> > > > Thanks in advance.
> > > > André den Oudsten
> > >
> > >
> > > Here is a link to a page which links to multiple methods of getting 
> > > wireless going in Opensuse:
> > >
> > > http://www.suseforums.net/index.php?showtopic=22475
> > >
> > > Personally, I use ndiswrapper to install my WinXP or Vista driver , 
> > > and it works great.
> > > Here is a link to the various howtos:
> > >
> > > http://www.andrewd18.com/ndiswrapper/
> > >
> > > Use the 10.2 instructions for Opensuse 10.3.  You have to install 
> > > and use knetwork manager to have a program to detect the various 
> > > wifi networks available.
> > >
> > > Mark
> > From the packman.links2linux.org site I could install wiki-radar for 
> > 10.3, but trieing to start it nothing happened!!
> > KnetworkManager as well as NetworkManager are installed, but I can't 
> > get them to work
> >
> > What to do?
> >
> > André
>
> I haven't been following this thread, but had a time getting wifi up.
>
> 1.  Is there a module loaded?  iwconfig as root will show available 
> wireless devices.  Without a loaded module AND its firmware, you may 
> see a device; but without both you will never see a network no matter 
> what you use.  At least this is the case with my BCM4318.
>
> 2. Assuming no module is loaded, do a hwinfo --netcard to see what you 
> have.
>
> 3. Mine is a BCM4318, so I installed bcm43xx-fwcutter and wireless-tools.
>
> 4. firmware was installed using /usr/sbin/install_bcm43xx_firmware.
>
>
> modprobe bcm43xx gave me a wireless card when invoking iwconfig.  It 
> is not wlan0 as expected, but eth1.  Still connects and works.
>
> Ed Harrison

I ran (as root) iwconfig , hwinfo --netcard and lspci -vvv.
In Yast Hardware I also found something
See attachment

Sorry for the lenght of the document, but shortening by me could be the 
wrong way

I'm very curieus,

André