2012/12/11 Dan Williams <dcbw at redhat.com>: > On Tue, 2012-12-11 at 15:00 -0300, Silvio Quadri wrote: >> 2012/12/11 Dan Williams <dcbw at redhat.com>: >> > On Mon, 2012-12-10 at 20:14 -0300, Silvio Quadri wrote: >> >> 2012/12/10 Silvio Quadri <silvioq at gmail.com>: >> >> > 2012/12/10 Silvio Quadri <silvioq at gmail.com>: >> >> >> 2012/12/10 <hypnos75 at gmail.com>: >> >> >>> Silvio, >> >> >>> >> >> >>> What does 'lsub -v' show? Here's the first part of the entry for my >> >> >>> WiMAX device: >> >> >>> >> >> >>> Bus 008 Device 002: ID 8086:1405 Intel Corp. WiMAX Connection 2400m >> >> >>> Device Descriptor: >> >> >>> bLength 18 >> >> >>> bDescriptorType 1 >> >> >>> bcdUSB 2.00 >> >> >>> bDeviceClass 0 (Defined at Interface level) >> >> >>> bDeviceSubClass 0 >> >> >>> bDeviceProtocol 0 >> >> >>> bMaxPacketSize0 64 >> >> >>> idVendor 0x8086 Intel Corp. >> >> >>> idProduct 0x1405 WiMAX Connection 2400m >> >> >>> bcdDevice 0.00 >> >> >>> iManufacturer 1 Intel(R) Corporation >> >> >>> iProduct 2 Intel(R) WiMAX Link 5350 >> >> >>> iSerial 0 >> >> >>> bNumConfigurations 1 >> >> >>> >> >> >>> >> >> >>> My device works fine with ClearWire in the US under Gentoo Linux, using >> >> >>> kernel 3.3.8 with firmware v. 1.5.0 . Here's my dmesg when the kernel >> >> >>> sees my WiMAX after resuming from sleep: >> >> >>> >> >> >>> usb 8-3: new high-speed USB device number 3 using ehci_hcd >> >> >>> i2400m_usb 8-3:1.0: WiMAX interface wmx0 (00:1d:e1:02:7a:92) ready >> >> >>> i2400m_usb 8-3:1.0: firmware interface version 9.3.2 >> >> >>> >> >> >>> Hope this helps. >> >> >>> >> >> >>> >> >> >>> Best, >> >> >>> >> >> >>> H7 >> >> >> >> >> >> Hi! Thanks for you response ... Tonight I check lsub command (There is >> >> >> not a Classmate here), but the dmesg log is here >> >> >> http://pastebin.com/5DPugnvb >> >> >> There is not a i2400m message. I run "modprobe i2400m" after, but no >> >> >> new message in dmesg appears. >> >> >> >> >> >> Silvio >> >> >> >> >> > >> >> > >> >> > 'lsusb -v' result at http://pastebin.com/1nrJCxag >> >> > Check line 678 and below >> >> > >> >> > Thank you >> >> > >> >> > >> >> > >> >> >> >> The first lines are ... >> >> >> >> Bus 001 Device 002: ID 8087:07d6 Intel Corp. >> >> Device Descriptor: >> >> bLength 18 >> >> bDescriptorType 1 >> >> bcdUSB 2.00 >> >> bDeviceClass 0 (Defined at Interface level) >> >> bDeviceSubClass 0 >> >> bDeviceProtocol 0 >> >> bMaxPacketSize0 64 >> >> idVendor 0x8087 Intel Corp. >> >> idProduct 0x07d6 >> >> bcdDevice 0.00 >> >> iManufacturer 1 Intel Corporation >> >> iProduct 2 Intel(R) Centrino(R) Wireless-N + WiMAX 6150 >> >> iSerial 0 >> >> bNumConfigurations 1 >> > >> > There's three of these new device IDs that don't appear in the >> > i2400m_usb driver, I'm trying to figure out from Intel contacts if these >> > devices are expected to work with the existing driver. I'm pretty >> > hopeful they will, as the Intel WiMAX hardware hasn't changed in a few >> > years, just the WiFi stuff that it's packaged with. >> > >> > Dan >> > >> >> Thanks Dan. >> Maybe must I recompile i2400m the driver for support device id? I >> forced the driver through new_id way. > > Yeah, should be an easy add to drivers/net/wimax/i2400m/usb.c near the > bottom. > > Dan Well. I maked this steps. 1. Compile i2400m module, version 3.2.28 with usb.c modified. 2. Install the module. 3. blacklist iwlwifi 4. reboot the machine. Now, the device is detected on boot, but the message is the same ... Complete dmesg at http://pastebin.com/hgf2fuXm (usb errors at line 728) "rfkill list" shows: 0: cmpc_rfkill: Wireless LAN Soft blocked: no Hard blocked: no After a. rebooting in Win7, b. activate WiMAX/Deactivate Wifi, c. shutdown and count to 10, d. startup the classmate in Linux, I get the same result. -- Silvio Quadri
