|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast ignoring WLAN configuration | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Marcus Schneider <herr-schneider.m> |
| Component: | YaST2 | Assignee: | Joachim Gleissner <joachim.gleissner> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | axel.braun, felix, locilka |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Yast2 logs
Hardware info hwinfo y2logs screenshot1 screenshot 2 |
||
Created attachment 157821 [details]
Hardware info
Christian, how we (yast2 & sysconfig) will handle this? Should ndiswrapper be writen into udev rules? I have seen this one too. Yes, yast2 should write a udev rule for ndiswrapper. For all devices where the user wants a special driver to be loaded we will simply modify the MODALIAS environment variable in udev. Then the default 'modprobe'-rules will load this driver.
Write to 79-yast2-drivers.rules:
ENV{MODALIAS}=="<modalias>", ENV{MODALIAS}="<module name>"
<modalias> is the original modalias that can be read from /sys/<devpath>/modalias. maybe hwinfo provides that info.
fixed in yast2-network-2.15.66 *** Bug 306266 has been marked as a duplicate of this bug. *** Coming from bug 306266, I find that this is not fixed in beta3: - module cant be added in the hardware tab - now three cards show up in the network settings: the build-in ethernet, the Netgear cardbus, and another wireless adapter with the hint 'cant be configured' (see mentioned bug) Axel, more details please and attach yast logs Created attachment 176872 [details]
hwinfo
Created attachment 176873 [details]
y2logs
Created attachment 177188 [details]
screenshot1
What I did: I set prism54 onto the blacklist to prevent it from loading, then inserted the card and called up the Yast module for network card. The picture according to the screenshot is shown. I select 'new', wireless device, and enter 'p54pci' as module.
I click 'Next' and reach the 'network card Setup'
Created attachment 177189 [details]
screenshot 2
As you can see from this screenshot, the module name is *not* taken over.
After finishing the card setup, the overview screen shows 3 cards: 2 wireless (one configured, one that cant be configured) and one wired. Now save the settings.
When I enter the Network setup again, now only 2 cards are shown, and the module is shown as prism54 for the wireless card (yes, thats the one on the blacklist).
The loaded module is p54:
a30:~ # lsmod
Module Size Used by
p54pci 15744 0
p54common 15488 1 p54pci
mac80211 158216 2 p54pci,p54common
cfg80211 10120 1 mac80211
ip6t_LOG 10496 8
nf_conntrack_ipv6 22848 4
Finally I got it working, but its somewhat confusing....
Hm, ah yes The problem is I disabled configuration of device without "Device File" in hwinfo output. Now I see only warning or text is enought. But in this case we can blacklist prism54 for this device id, Joachim? It is a bit unlucky to black list the prism54 driver by default, as it is a reasonable fallback in case p54-kmp is not installed. Is it a problem when prism54 gets loaded? This is for kernel maintainers. Please update modules database for modules.aliases to not load prism54 for this device I don't understand how the kernel developers can address this. Do you think that this specific device should never be grabbed by this device? If so, do you have the pci id of it? Take for example this one, the lovely Netgear WG511: axel@a30:~> /sbin/lspci -s 03:00.0 03:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01) axel@a30:~> /sbin/lspci -s 03:00.0 -n 03:00.0 Class 0280: 1260:3890 (rev 01) We cannot remove the PCI ID from the driver. Unfortunately, Intersil seems to considered it as a good idea to use the same ID for the fullmac (supported by prism54) and the softmac chip (not supported by prism54). For softmac cards p54 can be used, which should be preferred anyway, as it is the new mac80211 based driver. p54 is now part of the mainline kernel, so I see no problem in blacklisting prism54 by default anymore. I'll just add a modprobe.conf snippet to wireless-tools, like I did for other drivers already. That would be fine, thanks Submitted to STABLE. |
Created attachment 157820 [details] Yast2 logs When trying to create a new WLAN entry for my system via Yast -> Network Devices -> Network Card, I am first presented with the usual Add Dialog. There I choose "WLAN" from the device type select list, leave configuration name as it is ("1"), manually input "ndiswrapper" into the modul name dialog box, and click on "advance". Now the next page is the usual set up page for the NIC's ip configuration, the adapter shown is of type Ethernet and no configuration name is present. On clicking advance, I immediately get back to the list of configured NICs, my newly created NIC not shown. Ndiswrapper + kernel module are installed, ndiswrapper device driver is installed too: wg311v3 : driver installed device (11AB:1FAA) present lsmod shows ndiswrapper, depmod gives no error. I will attach y2log and hwinfo. Regards, Marcus (P.S., I will be off the next 17 days, so I can not answer...)