Hello,
My Arduino UNO R3 is not getting recognised in the IDE (v2 (via flatpak) & 1.8.19 (via apt)).
How can I solve this?
OS: Kali Linux (64 bit)
Hello,
My Arduino UNO R3 is not getting recognised in the IDE (v2 (via flatpak) & 1.8.19 (via apt)).
How can I solve this?
OS: Kali Linux (64 bit)
Open a terminal and type: groups
Do you see "dialout" ?
Yes. I see it.
Can you install a serial terminal program that shows the available ports ?
Perhaps you can try the Arduino board on an other computer ?
Do you have other boards that work ?
If you do a lsusb
before and after connecting the board, then it should appear.
Hi @tct123.
I'm not sure I understood correctly what you mean by "not getting recognised". Please add a forum reply here that provides a more detailed description to help us to understand it, including:
Make sure to include the full and exact text of any error or warning messages you might have encountered.
Without arduino:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 005: ID 04ca:703c Lite-On Technology Corp. Integrated Camera
Bus 002 Device 016: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 002 Device 017: ID 1199:a001 Sierra Wireless, Inc. Sierra Wireless EM7345 4G LTE
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
With arduino:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 005: ID 04ca:703c Lite-On Technology Corp. Integrated Camera
Bus 002 Device 016: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 002 Device 017: ID 1199:a001 Sierra Wireless, Inc. Sierra Wireless EM7345 4G LTE
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
This board works with other systems.
I don't have other working arduino boards.
I'm going to ask you to run the dmesg
command from the command line and post the output.
This procedure is not intended to solve the problem. The purpose is to gather more information.
sudo dmesg | tail --lines=60
<CODE/>
icon on the post composer toolbar.```
) to your reply to make sure the output is correctly formatted.Please let me know if you have any questions or problems while following those instructions.
[146690.646227] RDX: 0000000000000000 RSI: 0000000000000189 RDI: 00005633815122d0
[146690.646228] RBP: 00007f06dd9fd760 R08: 0000000000000000 R09: 00000000ffffffff
[146690.646229] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[146690.646230] R13: 0000000000000000 R14: 0000000000000000 R15: 00005633815122d0
[146690.646231] </TASK>
[146690.646232] INFO: task arduino-ide:78111 blocked for more than 120 seconds.
[146690.646233] Tainted: G OE 6.6.15-amd64 #1 Kali 6.6.15-2kali1
[146690.646234] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[146690.646235] task:arduino-ide state:D stack:0 pid:78111 ppid:78016 flags:0x00004002
[146690.646236] Call Trace:
[146690.646237] <TASK>
[146690.646238] __schedule+0x3da/0xb20
[146690.646241] schedule+0x5e/0xd0
[146690.646243] do_exit+0x117/0xb00
[146690.646245] ? __futex_unqueue+0x29/0x40
[146690.646247] do_group_exit+0x31/0x80
[146690.646249] get_signal+0x9fe/0xa30
[146690.646252] arch_do_signal_or_restart+0x3e/0x290
[146690.646255] exit_to_user_mode_prepare+0x195/0x1e0
[146690.646257] syscall_exit_to_user_mode+0x1b/0x40
[146690.646258] do_syscall_64+0x6c/0xc0
[146690.646261] ? __fget_light+0x99/0x100
[146690.646264] ? ksys_write+0xd8/0xf0
[146690.646267] ? exit_to_user_mode_prepare+0x40/0x1e0
[146690.646268] ? syscall_exit_to_user_mode+0x2b/0x40
[146690.646270] ? do_syscall_64+0x6c/0xc0
[146690.646272] ? syscall_exit_to_user_mode+0x2b/0x40
[146690.646273] ? do_syscall_64+0x6c/0xc0
[146690.646276] ? do_syscall_64+0x6c/0xc0
[146690.646278] ? do_syscall_64+0x6c/0xc0
[146690.646281] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[146690.646282] RIP: 0033:0x7f07a4bc3709
[146690.646283] RSP: 002b:00007f06dd1fc730 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
[146690.646284] RAX: fffffffffffffe00 RBX: 0000000000000000 RCX: 00007f07a4bc3709
[146690.646285] RDX: 0000000000000000 RSI: 0000000000000189 RDI: 00005633815122d4
[146690.646286] RBP: 00007f06dd1fc760 R08: 0000000000000000 R09: 00000000ffffffff
[146690.646287] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[146690.646288] R13: 0000000000000000 R14: 0000000000000001 R15: 00005633815122d4
[146690.646289] </TASK>
[146690.646290] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
[149759.937320] cdc_ncm 2-4:1.0 usb0: entered promiscuous mode
[149759.952629] cdc_ncm 2-4:1.0 usb0: left promiscuous mode
[149779.416440] usb 2-3: new full-speed USB device number 26 using xhci_hcd
[149779.544412] usb 2-3: device descriptor read/64, error -71
[149779.780347] usb 2-3: device descriptor read/64, error -71
[149780.020424] usb 2-3: new full-speed USB device number 27 using xhci_hcd
[149780.148454] usb 2-3: device descriptor read/64, error -71
[149780.384436] usb 2-3: device descriptor read/64, error -71
[149780.492469] usb usb2-port3: attempt power cycle
[149780.904419] usb 2-3: new full-speed USB device number 28 using xhci_hcd
[149780.904609] usb 2-3: Device not responding to setup address.
[149781.112585] usb 2-3: Device not responding to setup address.
[149781.320413] usb 2-3: device not accepting address 28, error -71
[149781.448235] usb 2-3: new full-speed USB device number 29 using xhci_hcd
[149781.448382] usb 2-3: Device not responding to setup address.
[149781.656399] usb 2-3: Device not responding to setup address.
[149781.864278] usb 2-3: device not accepting address 29, error -71
[149781.864358] usb usb2-port3: unable to enumerate USB device
[149783.121136] cdc_ncm 2-4:1.0 usb0: entered promiscuous mode
[149783.136493] cdc_ncm 2-4:1.0 usb0: left promiscuous mode
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.