Hi there I am currently using linux gentoo 2.6.13-rc3 and I am very much willing to switch to openSuse, but first I have to check some points: The madwifi driver, which I need for my Atheros a/b card is NOT in the kernel, I always had to "emerge" it seperately, how does Suse handle it? I saw under http://www.opensuse.org/HCL/Laptops/IBM that my T40P with it's card was supported under SuSe, but I still wanted to get this straight: Will my card 0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab NIC (rev 01) work, what overlay/init-script will be used and will I have to install extra stuff for configuration (WEP, Channel, AP restriction, etc: on a local config file or only using iwconfig, iwlist, wireless-tools)? Thanks for your consideration Best regards Patrick Fehr
On Sun, Sep 25, 2005 at 09:26:57PM +0200, Patrick Fehr wrote:
Hi there I am currently using linux gentoo 2.6.13-rc3 and I am very much willing to switch to openSuse, but first I have to check some points:
The madwifi driver, which I need for my Atheros a/b card is NOT in the kernel, I always had to "emerge" it seperately, how does Suse handle it? I saw under http://www.opensuse.org/HCL/Laptops/IBM that my T40P with it's card was supported under SuSe, but I still wanted to get this straight: Will my card
It is in the kernel, you will need the kernel-default-nongpl RPM from the external instsource howerver. Ciao, Marcus (typing this via a atheros wireless card ;)
Am Sonntag 25 September 2005 21:43 schrieb Marcus Meissner:
On Sun, Sep 25, 2005 at 09:26:57PM +0200, Patrick Fehr wrote:
Hi there I am currently using linux gentoo 2.6.13-rc3 and I am very much willing to switch to openSuse, but first I have to check some points:
The madwifi driver, which I need for my Atheros a/b card is NOT in the kernel, I always had to "emerge" it seperately, how does Suse handle it? I saw under http://www.opensuse.org/HCL/Laptops/IBM that my T40P with it's card was supported under SuSe, but I still wanted to get this straight: Will my card
It is in the kernel, you will need the kernel-default-nongpl RPM from the external instsource howerver.
Ciao, Marcus (typing this via a atheros wireless card ;)
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
You are my hero! Grabbed the sources from ftp://mirror.switch.ch/mirror/suse/suse/i386/10.0/SUSE-Linux10.0-RC1-Extra/kernel-modules+firmware/suse/i586/kernel-default-nongpl-2.6.13-8.i586.rpm Installed and it worked! No I need to find out how to gain more control over it, like how to use vpn and turn wlan manually on and off, is this easy? I don't want it to start everytime at boot and I don't want the wired conn there either. I'd like the ethernet to start at plugging in the cable and the wireless to start when an appropriate AP is nearby OR manually. best regards patrick
Am Montag, 3. Oktober 2005 08:51 schrieb Patrick Fehr:
Am Sonntag 25 September 2005 21:43 schrieb Marcus Meissner:
On Sun, Sep 25, 2005 at 09:26:57PM +0200, Patrick Fehr wrote:
The madwifi driver, which I need for my Atheros a/b card is NOT in the kernel, I always had to "emerge" it seperately, how does Suse handle it? I saw under It is in the kernel, you will need the kernel-default-nongpl RPM from the external instsource howerver. Grabbed the sources from ftp://mirror.switch.ch/mirror/suse/suse/i386/10.0/SUSE-Linux10.0-RC1- Extra/kernel-modules+firmware/suse/i586/kernel-default-nongpl-2.6.13-8 .i586.rpm Installed and it worked! No I need to find out how to gain more control over it, like how to use vpn and turn wlan manually on and off, is this easy? I don't want it to start everytime at boot
Hi, Startmode ifplugd, but not tested for wlan.
and I don't want the wired conn there either. I'd like the ethernet to start at plugging in the cable
Set the startmode of the interface to ifplugd. It writes "PHY reset until link up" every 5 seconds to the log, but works. Have a look at your /var/log/messages...
and the wireless to start when an appropriate AP is nearby OR manually.
Can't say, my wlan card (broadcom) is not supported (maybe ndiswrapper) and it's the only wlan device I own. So no chance to test. -- mdc
participants (3)
-
Marcus Meissner -
meister＠netz00.com -
Patrick Fehr