http://qa.mandrakesoft.com/show_bug.cgi?id=3793
------- Additional Comments From [EMAIL PROTECTED] 2003-04-09 10:27 ------- I installed MDK 9.2 RC 1 yesterday evening, and I was surprised to see that the installation tries to set up wlan with the orinoco_pci module AGAIN after the association between the miniPCI card and the orinoco_pci module was suspended in April. Happily, this problem no longer freezes up the system during the installation process. It freezes up the system when trying to start the eth1 service during boot-up instead, meaning that it is possible to turn off and restart the machine, press 'I' during boot for interactive startup and skip eth1. It is then possible to configure the network so that eth1 is _not_ started auomatically at boot time. Has anyone positively demonstrated that this Actiontec miniPCI wlan controller works with orinoco_pci? -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEEDINFO creation_date: description: I have an Elitegroup Green 732 notebook (ECS G732, cf. http://www.ecs.com.tw/products/g732_spec.htm) with an integrated Actiontec miniPCI 802.11b adapter (cf. http://www.actiontec.com/products/broadband/80211bminipci/80211bminipci.pdf). The same wlan device is commonly used in IBM notebooks (cf. e.g. http://www.balukoff.com/~stephen/a30p/ where descriptions of how to get the wlan device to work with linux are given). There is also an integrated SiS900 10/100 Ethernet controller (assigned to eth0; the installation process assigns the wlan device to eth1). /proc/pci identifies the wlan device as: Bus 0, device 5, function 0: Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev 1). IRQ 9. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe8006000 [0xe8006fff]. The vendor device code is 1260:3873 During installation (or later, in DrakConnect), the device is set up with the orinoco_pci kernel module. The module is loaded without incident, but once the system tries connect to the device (e.g. during the installation's network configuration step, unless one skips this step), the system locks up completely, requiring a hard reset (as everything is installed already, MDK 9.1 boots OK afterwards - but without internet connection set up, even on eth0). According to http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Orinoco.html under the header "Issues and release notes", Prism2.5 PCI cards are not supported and neither are miniPCI based on the PCI card (and not using a PCI-PCMCIA bridge). SuSE 8.1 does the same thing as MDK 9.1 as regards identification of the wlan device and (erroneous) relation to orinoco_pci, but as the SuSE installation only attempts to configure the "main" ethernet controller (i.e. no attempt is made to setting up the wlan device), the result is not as disastrous (at least for a newbie linux user!) as with the MDK 9.1 installation. Red Hat 9 doesn't seem to include any wlan kernel modules at all, so RH9 simply ignores the wlan device. As MDK 9.1 comes with the linux-wlan-ng kernel modules as well (prism2_pci etc.), I tried to modprobe prism2_pci - however getting the error described by another user (with the same wlan device) here: http://www.nclug.org/pipermail/nclug/2003-January/004856.html Perhaps the system assumes a PCI-PCMCIA bridge device rather than a "native" PCI device? A _temporary_ solution to the problem, would be to make a patch to the MDK 9.1 installation (and HardDrake / DrakConnect) so that it _ignores_ the device rather than attempting to use the orinoco drivers (which locks up the system). A _permanent_ solution would be to configure the linux-wlan-ng or, possibly, the host-ap driver to work with the device.
