usbfs: interface 0 claimed by ch34x while 'brltty' sets config #1

[beautifulzzzz]

make 
sudo make load

then reboot, still can't find ttyUSB.

sudo dmesg | grep ch34x
still show the disconnect msg:

  284.973396] ch34x 3-4.2:1.0: ch34x converter detected
[  284.973894] usb 3-4.2: ch34x converter now attached to ttyUSB0
[  285.019333] usb 3-4.2: usbfs: interface 0 claimed by ch34x while 'brltty' sets config #1
[  285.019883] ch34x ttyUSB0: ch34x converter now disconnected from ttyUSB0
[  285.019895] ch34x 3-4.2:1.0: device disconnected

then, I find : https://unix.stackexchange.com/questions/670636/unable-to-use-usb-dongle-based-on-usb-serial-converter-chip

use:

for f in /usr/lib/udev/rules.d/*brltty*.rules; do
    sudo ln -s /dev/null "/etc/udev/rules.d/$(basename "$f")"
done
sudo udevadm control --reload-rules

sudo systemctl mask brltty.path

then OK (no need to reboot)

[beautifulzzzz]

my pc info:

➜  / screenfetch 
                   -`                 
                  .o+`                 btfz@lt-pc
                 `ooo/                 OS: Arch Linux 
                `+oooo:                Kernel: x86_64 Linux 5.14.14-arch1-1
               `+oooooo:               Uptime: 16m
               -+oooooo+:              Packages: 1469
             `/:-:++oooo+:             Shell: zsh 5.8
            `/++++/+++++++:            Resolution: 3200x1080
           `/++++++++++++++:           DE: Xfce4
          `/+++ooooooooooooo/`         WM: Xfwm4
         ./ooosssso++osssssso+`        WM Theme: Microdeck3
        .oossssso-````/ossssss+`       GTK Theme: Arc-Dark [GTK2]
       -osssssso.      :ssssssso.      Icon Theme: Numix-Circle
      :osssssss/        osssso+++.     Font: Sans 10
     /ossssssss/        +ssssooo/-     Disk: 96G / 215G (47%)
   `/ossssso+/:-        -:/+osssso+-   CPU: Intel Xeon E3-1230 V2 @ 8x 3.7GHz [39.0°C]
  `+sso+:-`                 `.-/+oso:  GPU: AMD/ATI Juniper PRO [Radeon HD 6750]
 `++:.                           `-/+/ RAM: 1234MiB / 7862MiB
 .`                                 `/
➜  / 

[Le Libre Au Quotidien]

Thanks a lot, this fix worked for me !

[Jagoda Górska]

Thank you for your tutorial, I have pinned this thread for others with this problem

[3urobeat]

Thank you so much!

[Dmitry Obrazumov]

or you can use solution without disable all service, just disable rule of matching
brltty has a rule for idVendor=1a86, idProduct=7523, which is the same as the CH340 serial converter.
/usr/lib/udev/rules.d/85-brltty.rules
# ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
comment upper row then reboot os

[beautifulzzzz]

every reboot make load

sudo cp -f ./ch34x.ko /lib/modules/$(shell uname -r)/kernel/drivers/usb/serial

sudo echo "ch34x" > /etc/modules-load.d/ch34x.conf
sudo chmod +x /etc/modules-load.d/ch34x.conf

[Daniel Sena]

thanks man it helped a lot

[Kayra Toprak SAY]

or you can use solution without disable all service, just disable rule of matching brltty has a rule for idVendor=1a86, idProduct=7523, which is the same as the CH340 serial converter. /usr/lib/udev/rules.d/85-brltty.rules # ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run" comment upper row then reboot os

non-invasive & immidiate fix, thanks dude

[Jade Guo]

or you can use solution without disable all service, just disable rule of matching
brltty has a rule for idVendor=1a86, idProduct=7523, which is the same as the CH340 serial converter.
/usr/lib/udev/rules.d/85-brltty.rules
# ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
comment upper row then reboot os

Thanks a lot!! It works for me!!

[AXBreaker]

I just run :

sudo apt remove brltty

[Martian]

I just run :

sudo apt remove brltty

This works

[Huichun Feng]

I just run :

sudo apt remove brltty

So the TLDR is, if you are not a blind and you have this device, simply remove the package.

[mmiller7]

I just run :

sudo apt remove brltty

THANK YOU!

I've spent half an hour trying to figure out why many of my USB-Serial devices no longer work on Mint anymore...no idea where this package came from or why its installed by default. UGH!

And not sure why some other package thought it would be good to randomly take over serial controlled peripherals...