Teilhard Knight wrote: > From: "Mikkel L. Ellertson" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, June 21, 2005 9:38 AM > Subject: Re: [newbie] mdkcustom missing > > >> Teilhard Knight wrote: >> >>> From: "Mikkel L. Ellertson" <[EMAIL PROTECTED]> >>> To: <[email protected]> >>> Sent: Monday, June 20, 2005 9:29 PM >>> Subject: Re: [newbie] mdkcustom missing >>> >>> >>>> Teilhard Knight wrote: >>>> >>>>> >>>>> >>>>> Of course I thought in doing what you say. Problem is that MCC does >>>>> not >>>>> detect my device. It asks me to load a driver by hand without more >>>>> options. I have checked with "lsmod" that my module is loaded, but the >>>>> device does not show up. HardDrake detects it as "other devices" and >>>>> UsbView detects it quite nicely, as if it was a device just ready to >>>>> use. Any ideas? >>>>> >>>>> Teilhard. >>>>> >>>> If it is not being detected as a NIC, then you are going to have >>>> problems with more then just MCC... >>>> >>>> Dumb question time: >>>> Did you run "depmod -a" or reboot after building the module? This is >>>> needed to update the list hotplug uses for loading modules when devices >>>> are plugged in. (If it was plugged in when you updated things, then you >>>> will need to unplug it, and plug it in again.) >>> >>> >>> >>> >>> No, I didn't do it, but I have done it already without the device >>> plugged, and I have plugged it a nothing has changed. >>> >>> >>>> You may also want to take a look at /proc/bus/usb/devices and see if a >>>> driver is being loaded for the device. Or you can post the output of: >>>> cat /proc/bus/usb/devices >>>> and we can help you decode it. It sounds like the driver is not being >>>> tied to the NIC, and so no Ethernet device is being created. Without >>>> that, none of the network commands are going to work. >>> >>> >>> >>> >>> It seems the driver loads all right as far as I can gather. But I gibve >>> you the file so you can see the otcome. >>> >>> >>> T: Bus=05 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 10 Spd=480 MxCh= 0 >>> D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 >>> P: Vendor=0ace ProdID=1211 Rev=43.30 >>> S: Manufacturer=ZyDAS >>> S: Product=USB2.0 WLAN >>> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA >>> I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=zd1211 >>> E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms >>> E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms >>> E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=125us >>> E: Ad=04(O) Atr=03(Int.) MxPS= 64 Ivl=125us >>> >> Yes, this is the entry for it, and it is using the driver. >> >>> >>> >>>> Another thing to do is check the logs for any error messages from the >>>> module. What I find helpfull is to have "tail -f /var/log/messages" >>>> running on one VT, or in a terminal when I plug a devie in, so I can >>>> see >>>> any messages. (Actualy, I moduified my syslog configuration so that all >>>> messages are displayed on vt12, so I can just hit Ctrl-Alt-F12 to see >>>> what is going on.) >>> >>> >>> >>> When I plug the device, I get: >>> >>> Jun 21 07:23:58 localhost kernel: new high speed device using address 5 >>> >>> ------------------ Release Ver = 4330 >>> ------------------ EEPORM ver = 4330 >>> Jun 21 7:23:59 localhost net.agent[6958]: add event not handled >>> >> Ok - it looks like it is detecting the network device, and trying to >> start it. I find it strange that drakconnect does not find it. Time to >> try something else... >> >> Run "ifconfig -a" and see if it shows eth0 or wlan0. If it does, we can >> work from there. The -a option of ifconfig will show all interfaces, >> even if they are not configured. If it doesn't show ether of them, then >> let us know what it does show. You should see at least the lo interface. > > > Yes, it shows eth0 AND wlan0. it also shows a wlan1-00: link > encapsulated:UNSPEC ........................... > > Thank you for taking the time. > > Teilhard. > > I am not sure why MCC isn't seeing it, but I guess we can get you up and running first, and dig into MCC another time. Quick, cheap, and dirty way to do it - create a file called ifcfg-wlan0 in /etc/sysconfig/network-scripts.
DEVICE=wlan0 BOOTPROTO=dhcp NETMASK=255.255.255.0 ONBOOT=no MII_NOT_SUPPORTED=no WIRELESS_MODE=Managed then run "chmod 755 /etc/sysconfig/network-scripts/ifcfg-wlan0 Some other things you may need in the file, depending on your setup: WIRELESS_ESSID=<access point ID> WIRELESS_ENC_KEY=<encription key> WIRELESS_IWCONFIG="key restricted" After you have created the file, you should be able to bring up the interface by running "ifup wlan0" as root. You can then check on the interface by running "ifconfig" and "iwconfig wlan0". Once you have wlan0 set correctly, plugging in the NIC should bring it up automaticly. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
