From: Andreas M. <an...@us...> - 2003-11-25 08:42:33
|
Hi, On Mon, Nov 24, 2003 at 03:07:07PM +0100, Jakob K=FClzer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On Monday 24 November 2003 10:32, Andreas Mohr wrote: > > Since you're brave enough to use development kernels (ok, it's not th= at > > much of a development kernel any more...) with an even more horrible >=20 > To be honest the 2.6.0-test9 is as stable as a rock... had not any prob= lem=20 > with it so far (o: Yup, test7 also was very good already (stability-wise). But feature-wise? Umm, let's see: problematic ACPI (and many drivers no working power management), ALSA still not as usable as one would like,= ... > > Could you provide some debug 0xffff log? >=20 > Sure.. but its not much.. )o: > Modprobe: modprobe acx100_pci firmware_dir=3D/usr/share/acx100/ debug=3D= 0xffff > dmesg outpout: > - ---------------------->8----------------------------------- > =3D=3D> acx100_init_module > acx100: It looks like you were coaxed into buying a wireless network ca= rd > acx100: that uses the mysterious ACX100 chip from Texas Instruments. > acx100: You should better have bought e.g. a PRISM(R) chipset based car= d, > acx100: since that would mean REAL vendor Linux support. > acx100: Given this info, it's plain evident that this driver is EXPERIM= ENTAL, > acx100: thus your mileage may vary. Visit http://acx100.sf.net for supp= ort. > acx100_init_module: TI acx100_pci.o: Ver 0.2.0pre6 Loaded > acx100_init_module: dev_info is: TI acx100_pci > <=3D=3D acx100_init_module: 00000000 > - ---------------------->8----------------------------------- >=20 > lspci gives me the following additional line after the modprobe:=20 > - ---------------------->8----------------------------------- > 06:00.0 Network controller: Texas Instruments: Unknown device 9066 > - ---------------------->8----------------------------------- >=20 > But that's all... could not find any more clues for the presence of the= card/ > module.... Is it possible that i'm missing some VERY important step?? Well, it'd be *VERY* important to actually HAVE a card which the driver i= s supposed to support. Are you SURE your card DOES have an ACX100 chip and it's not one of the "I make sure to pretend as much as possible to be an ACX100 but for some strange reason I'm not" cards? (somehow I think there has to be a reason for the "Unknown device 9066" a= bove) > Are there any module-dependencies which are not met?? So far i found ou= t that=20 > the pci_hotplug module is needed, are there more required modules? > I could not find something about this in the README....=20 >=20 > > It's NOT supposed to not provide any wlan0 device, though, that's tru= e... >=20 > Ok.... but what does the module provide then, or the other way round, w= ho's=20 > job is it to create the wlanX-device?? Umm... please reread my sentence ;-) Andreas Mohr |