| 1 |
On 07/07/2016 10:22 PM, Meino.Cramer@×××.de wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I have bought an ESP8266 Lua NodeMCU board, which has |
| 5 |
> an FTDI-like chip on board to map USB to serial and |
| 6 |
> vice versa. It is an CH340 one. |
| 7 |
> There is an according module in the driver (compiled |
| 8 |
> and - to get shure - loaded by hand). |
| 9 |
> |
| 10 |
> When I connect the ESP8266 board to my Gentoo PC |
| 11 |
> nothing happens (dmesg shows nothing). |
| 12 |
> When pressing RST on the board, I see this sometimes: |
| 13 |
> |
| 14 |
> [ 4340.105221] usb 7-4: new full-speed USB device number 9 using ohci-pci |
| 15 |
> [ 4340.630234] usb 7-4: device not accepting address 9, error -62 |
| 16 |
> |
| 17 |
> (both lines are printed right after another - no delay...) |
| 18 |
> |
| 19 |
> or this: |
| 20 |
> |
| 21 |
> [ 4473.567739] usb 7-4: new full-speed USB device number 11 using ohci-pci |
| 22 |
> [ 4473.712306] usb 7-4: New USB device found, idVendor=1a86, idProduct=7523 |
| 23 |
> [ 4473.712316] usb 7-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 |
| 24 |
> [ 4473.712321] usb 7-4: Product: USB2.0-Serial |
| 25 |
> [ 4473.763259] usbcore: registered new interface driver ch341 |
| 26 |
> [ 4473.763278] usbserial: USB Serial support registered for ch341-uart |
| 27 |
> [ 4473.763295] ch341 7-4:1.0: ch341-uart converter detected |
| 28 |
> [ 4473.786463] usb 7-4: ch341-uart converter now attached to ttyUSB1 |
| 29 |
> [ 4473.888987] usb 7-4: USB disconnect, device number 11 |
| 30 |
> [ 4473.889485] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1 |
| 31 |
> [ 4473.889511] ch341 7-4:1.0: device disconnected |
| 32 |
> [ 4474.292773] usb 7-4: new full-speed USB device number 12 using ohci-pci |
| 33 |
> |
| 34 |
> there is no new device under /dev/. |
| 35 |
> |
| 36 |
> Do I miss something seriously important here related to using the |
| 37 |
> CH340 driver...or is this board simply demaged ??? |
| 38 |
> |
| 39 |
> Thank you very much in advance for any help! |
| 40 |
> |
| 41 |
> Best regards, |
| 42 |
> Meino |
| 43 |
> |
| 44 |
> |
| 45 |
> |
| 46 |
> |
| 47 |
> |
| 48 |
> |
| 49 |
> |
| 50 |
> |
| 51 |
If memory serves, udev/eudev generates the nodes/devices in /dev now. |
| 52 |
To get the correct hardware ID, it uses a specific database. |
| 53 |
|
| 54 |
The hardware ID's database may need to be updated ( or supplemented ). |
| 55 |
The package "sys-apps/pciutils" has the hardware database included in it. |
| 56 |
|
| 57 |
I have a 990FX chipset MB that is constantly ID as a 880 chipset board. |
| 58 |
No info on 990FX chipsets found in the hardware ID's database. |
| 59 |
The kernel keeps applying a 880 chipset workaround for the PCI bus, |
| 60 |
every boot. |
| 61 |
|
| 62 |
Same problem I think, different hardware. |
Archives