On 07/07/2016 10:22 PM, meino.cra...@gmx.de wrote:
Hi,
I have bought an ESP8266 Lua NodeMCU board, which has
an FTDI-like chip on board to map USB to serial and
vice versa. It is an CH340 one.
There is an according module in the driver (compiled
and - to get shure - loaded by hand).
When I connect the ESP8266 board to my Gentoo PC
nothing happens (dmesg shows nothing).
When pressing RST on the board, I see this sometimes:
[ 4340.105221] usb 7-4: new full-speed USB device number 9 using ohci-pci
[ 4340.630234] usb 7-4: device not accepting address 9, error -62
(both lines are printed right after another - no delay...)
or this:
[ 4473.567739] usb 7-4: new full-speed USB device number 11 using ohci-pci
[ 4473.712306] usb 7-4: New USB device found, idVendor=1a86, idProduct=7523
[ 4473.712316] usb 7-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 4473.712321] usb 7-4: Product: USB2.0-Serial
[ 4473.763259] usbcore: registered new interface driver ch341
[ 4473.763278] usbserial: USB Serial support registered for ch341-uart
[ 4473.763295] ch341 7-4:1.0: ch341-uart converter detected
[ 4473.786463] usb 7-4: ch341-uart converter now attached to ttyUSB1
[ 4473.888987] usb 7-4: USB disconnect, device number 11
[ 4473.889485] ch341-uart ttyUSB1: ch341-uart converter now disconnected from
ttyUSB1
[ 4473.889511] ch341 7-4:1.0: device disconnected
[ 4474.292773] usb 7-4: new full-speed USB device number 12 using ohci-pci
there is no new device under /dev/.
Do I miss something seriously important here related to using the
CH340 driver...or is this board simply demaged ???
Thank you very much in advance for any help!
Best regards,
Meino
If memory serves, udev/eudev generates the nodes/devices in /dev now.
To get the correct hardware ID, it uses a specific database.
The hardware ID's database may need to be updated ( or supplemented ).
The package "sys-apps/pciutils" has the hardware database included in it.
I have a 990FX chipset MB that is constantly ID as a 880 chipset board.
No info on 990FX chipsets found in the hardware ID's database.
The kernel keeps applying a 880 chipset workaround for the PCI bus,
every boot.
Same problem I think, different hardware.
