How do I get access to usb ports?

I’ve looked through the archives, I’ve done an internet search, and just cannot find anything relaed to my problem. My problem is that I cannot access the usb ports. I’m using a Lenovo T540p with the latest Manjaro installed. I’ve used Debian for decades and cannot find the usb anything on Manjaro. I did read that, as the only user on the machine, I SHOULD have access to everything root has. So, am I to undestand ‘root’ doesn’t have access to usb ports? WHY not, and how do I give myself access?

1 Like

What do you mean by that?

It works the same no matter the distribution.
Unless your USB controller is broken - then it won’t work in any distribution. :grimacing:

What do you mean by “access the usb ports”?

… I assume you installed via some kind of USB device - so the ports clearly do work. :man_shrugging:

You said you searched, but really everything you need to know about accessing a USB drive is here USB storage devices - ArchWiki Not to mention many of us just use file manager (Dolphin if you use Plasma),

Please supply the following, in the CLI type:

inxi -zv8

paste the CLI output between 2 sets of triple back ticks “`”

USB offers a lot of functionality.

Could you please specify in more detail what isn’t working for you?

For example, you can connect the following via USB:

  • a mouse
  • a USB storage device
  • a USB-to-serial adapter
  • a USB oscilloscope
  • a camera

:footprints:

2 Likes

It would help a lot if you were to disclose which device you are expecting find and access.

If your intention is to access an usb port directly in order to write directly to the device attached e.g. an USB serial port you will need to add yourself to uucp group.

Such device USB-RS232 will likely be available at /dev/ttyUSB<x>.

If the device is a HID it will be located at /dev/usb/hiddev<x>.

There is also /dev/hidraw<x>

1 Like

I’m trying to access the USB port connected through an interface for Ham radio digital mode. I’ve done that for years on the Debian machine. Manjaro doesn’t see the serial/usb adapter in the app(s) even though the CAT cable has partial function. I’m used to seeing some version of /dev/usb0, but all I get in Manjaro is a list of tty ports with no usb listed.

The only method I know is to watch what the system sees when the device gets plugged in/removed:

journalctl -f
(journalctl --follow)
or
sudo dmesg -w (for: --follow)
or
sudo dmesg -W (for: --follow-new)

It’ll also be in the full system log, but this is easier to watch and find in real time.

We know nothing about your machine or the device.
I know nothing about Ham radio and have used a modem through a real serial port for the last time probably two decades ago.

2 Likes

It may be one of those tty device files. Best check like @Nachlese said.

1 Like

The name can vary considerably.
It can begin with tty, or it can contain USB or another specific abbreviation.
For example, /dev/ttyACM0 /dev/ttyUSB0 may be the names of the devices.

The name is generated by a udev rule. If the specific udev rule for the device doesn’t exist, no device name is shown.

It is best to use dmesg to look into this

:footprints:
(I’ve also had to adjust udev rules to get specific devices to show up.)

2 Likes

:up_arrow: Yes! This. :up_arrow:

I have used /dev/ttyUSB* more commonly, for decades!

Plug the device in. The device should appear in /dev/ (I am used to /dev/tty*).

Still waiting on the system information @tracyanne requested 20 hours ago:

Please, help us to help you by providing the output of:

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8
Running `inxi` in `chroot`

Note that any code or command output (such as inxi output) should be placed within a scrollable pre-formatted text enclosure according to forum guidelines.

See here for instructions: :point_down:


[MiniHowTo] Present code or command output

Note: Grave accent (or, backtick) characters are used. :eyes:

For inline code or to show a single command:

  • for example, typing: `code here` will display the text as code here.

For multi-line command output:

  • place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
  • use the </> button in the Compose window to achieve the same result.

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter.
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.

System:
  Kernel: 6.18.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
    root=UUID=6754c18b-60e8-4737-b65d-6b482b63c373 rw rootflags=subvol=@
    quiet splash resume=UUID=502d64e6-7357-48df-9b43-1a93e800629a
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.21.0
    wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Latitude E5470 v: N/A
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0VHKV0 v: A00 serial: <superuser required> part-nu: 06DE
    uuid: <superuser required> Firmware: UEFI-[Legacy] vendor: Dell v: 1.23.3
    date: 08/04/2020
Battery:
  ID-1: BAT0 charge: 53.9 Wh (100%) condition: 53.9/53.9 Wh (100%) volts: 8.52
    min: 7.7 model: LGC-LGC4.20 DELL HK6DV type: Li-ion serial: <filter>
    charging: status: full control: start: 50% end: 90% type: adaptive
    avail: adaptive,custom,fast,standard,trickle cycles: N/A
Memory:
  System RAM: total: 8 GiB available: 7.43 GiB used: 3.63 GiB (48.8%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 1 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: DIMM A type: no module installed
  Device-2: DIMM B type: DDR4 detail: synchronous size: 8 GiB
    speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M471A1G43EB1-CPB serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-6300U bits: 64 type: MT MCP arch: Skylake
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x4E (78) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
    smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
    desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2900 min/max: 400/3000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 2900 2: 2900 3: 2900 4: 2900 bogomips: 19999
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell driver: i915
    v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1916
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x05f3 built: 2013 res: mode: 1366x768
    hz: 60 scale: 100% (1) dpi: 112 gamma: 1.2 chroma: red: x: 0.573 y: 0.357
    green: x: 0.341 y: 0.588 blue: x: 0.161 y: 0.098 white: x: 0.314 y: 0.329
    size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9
    modes: 1366x768
  EDID-Warnings: 1: parse_edid: unknown flag 0
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 520 (SKL GT2)
    device-ID: 8086:1916 memory: 7.25 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 2 device: 0 type: integrated-gpu name: Intel
    HD Graphics 520 (SKL GT2) driver: mesa intel v: 25.3.3-arch1.1
    device-ID: 8086:1916 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:9d70
    class-ID: 0403
  API: ALSA v: k6.18.4-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:156f class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24f3 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8:6 chip-ID: 8087:0a2b
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 10 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.93 TiB used: 358.32 GiB (18.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SUV500120G
    size: 111.79 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 56R6 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: Portable
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B type: USB
    rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 9300 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: Portable
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
    fw-rev: 9300 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 102.99 GiB size: 102.99 GiB (100.00%)
    used: 23.61 GiB (22.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 6754c18b-60e8-4737-b65d-6b482b63c373
  ID-2: /home raw-size: 102.99 GiB size: 102.99 GiB (100.00%)
    used: 23.61 GiB (22.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 6754c18b-60e8-4737-b65d-6b482b63c373
  ID-3: /run/media/james/Linux Data raw-size: 419.92 GiB
    size: 412.26 GiB (98.18%) used: 334.19 GiB (81.1%) fs: ext4 dev: /dev/sdb2
    maj-min: 8:18 label: Linux Data uuid: 06581fee-0c42-43c4-8944-09cb077e8f6b
  ID-4: /var/cache raw-size: 102.99 GiB size: 102.99 GiB (100.00%)
    used: 23.61 GiB (22.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 6754c18b-60e8-4737-b65d-6b482b63c373
  ID-5: /var/log raw-size: 102.99 GiB size: 102.99 GiB (100.00%)
    used: 23.61 GiB (22.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 6754c18b-60e8-4737-b65d-6b482b63c373
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 541.3 MiB (6.0%)
    priority: -2 dev: /dev/sda2 maj-min: 8:2 label: swap
    uuid: 502d64e6-7357-48df-9b43-1a93e800629a
Unmounted:
  ID-1: /dev/sdb1 maj-min: 8:17 size: 49.8 GiB fs: ntfs
    label: Windows Files, etc. uuid: 06EEE42E261D098A
  ID-2: /dev/sdb3 maj-min: 8:19 size: 461.78 GiB fs: ext4 label: Backup&Data
    uuid: f0992e22-86a6-499e-a278-87db44aee60c
  ID-3: /dev/sdc1 maj-min: 8:33 size: 931.51 GiB fs: btrfs label: Media
    uuid: 1978f343-4cff-4931-885c-75780de0eaa8
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-4:3 info: USB2.0 HUB ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 2148:7022 class-ID: 0900
  Device-1: 1-4.2:5 info: MosArt Wireless Keyboard/Mouse
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 062a:4101 class-ID: 0301
  Hub-3: 1-4.4:13 info: USB2.0 HUB ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 2148:7022 class-ID: 0900
  Device-1: 1-4.4.2:18 info: Seagate RSS LLC Portable type: mass storage
    driver: uas interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 0bc2:2343 class-ID: 0806 serial: <filter>
  Device-2: 1-7:4 info: Broadcom BCM5880 Secure Applications Processor
    Smartcard reader type: smart card driver: N/A interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0a5c:5832 class-ID: 0b00 serial: <filter>
  Device-3: 1-8:6 info: Intel Bluetooth wireless interface type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 8087:0a2b class-ID: e001
  Hub-4: 2-0:1 info: super-speed hub ports: 6 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-1:2 info: Seagate RSS LLC Portable type: mass storage
    driver: uas interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
    mode: 3.2 gen-1x1 power: 144mA chip-ID: 0bc2:2343 class-ID: 0806
    serial: <filter>
Sensors:
  System Temperatures: cpu: 66.0 C pch: 54.0 C mobo: 40.0 C
  Fan Speeds (rpm): cpu: 0
Repos:
  Packages: 1533 pm: pacman pkgs: 1510 libs: 413 tools: pamac pm: flatpak
    pkgs: 23
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.dimensiondata.com/mirrors/manjaro.org/stable/$repo/$arch
    2: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    3: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    4: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    5: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    6: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    7: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    8: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    9: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    10: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    11: https://manjaro.grena.ge/stable/$repo/$arch
    12: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    13: https://mirrors2.manjaro.org/stable/$repo/$arch
    14: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    15: https://mirror.23m.com/manjaro/stable/$repo/$arch
    16: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    17: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    18: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    19: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    20: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    21: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    22: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    23: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    24: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    25: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    26: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    27: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    28: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    29: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    30: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    31: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    32: https://mirror.init7.net/manjaro/stable/$repo/$arch
    33: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    34: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    35: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    36: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    37: https://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    38: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    39: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    40: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    41: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    42: https://manjaro.ynh.ovh/stable/$repo/$arch
    43: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    44: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    45: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    46: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    47: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
    48: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    49: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    50: https://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
    51: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    52: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    53: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    54: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    55: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    56: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
    57: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    58: https://manjaro.mirror-services.net/pub/stable/$repo/$arch
    59: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    60: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    61: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    62: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    63: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    64: https://mirror.mobinhost.com/manjaro/stable/$repo/$arch
    65: https://manjaro.syxpi.fr/manjaro/stable/$repo/$arch
    66: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    67: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    68: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    69: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    70: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    71: https://manjaro.mirror.ac.za/stable/$repo/$arch
    72: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    73: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    74: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    75: https://linorg.usp.br/manjaro/stable/$repo/$arch
    76: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    77: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    78: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    79: https://mirrors.pku.edu.cn/manjaro/stable/$repo/$arch
    80: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    81: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    82: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
    83: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    84: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    85: https://manjaro.nic.cz/stable/$repo/$arch
    86: https://mirror.komelt.dev/manjaro/stable/$repo/$arch
    87: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    88: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    89: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    90: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    91: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    92: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    93: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    94: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    95: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    96: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    97: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    98: https://mirror.bakertelekom.fr/manjaro/stable/$repo/$arch
    99: https://mirror.leitecastro.com/manjaro/stable/$repo/$arch
    100: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    101: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    102: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    103: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    104: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    105: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    106: https://mirror.meowsmp.net/manjaro/stable/$repo/$arch
    107: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    108: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    109: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    110: https://manjaro.kurdy.org/stable/$repo/$arch
    111: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    112: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    113: https://mirrors.aliyun.com/manjaro/stable/$repo/$arch
    114: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    115: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    116: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    117: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    118: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    119: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    120: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    121: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    122: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    123: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    124: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 256
  1: cpu: 71.3% command: wesnoth pid: 23076 mem: 294.4 MiB (3.8%)
  2: cpu: 19.9% command: firefox pid: 90433 mem: 633.3 MiB (8.3%)
  3: cpu: 10.1% command: firefox pid: 90887 mem: 373.4 MiB (4.9%)
  4: cpu: 6.0% command: firefox pid: 90729 mem: 510.7 MiB (6.7%)
  5: cpu: 2.8% command: kwin_wayland pid: 791 mem: 178.2 MiB (2.3%)
  Memory top: 5 of 256
  1: mem: 692.2 MiB (9.1%) command: plasmashell pid: 974 cpu: 1.8%
  2: mem: 633.3 MiB (8.3%) command: firefox pid: 90433 cpu: 19.9%
  3: mem: 510.7 MiB (6.7%) command: firefox pid: 90729 cpu: 6.0%
  4: mem: 373.4 MiB (4.9%) command: firefox pid: 90887 cpu: 10.1%
  5: mem: 363.7 MiB (4.7%) command: xdg-desktop-portal-kde pid: 1281
    cpu: 0.0%
Info:
  Processes: 256 Power: uptime: 4d 8h 48m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 7 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 2.96 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.40

Mod edit: added three backticks ``` to empty lines before & after the terminal output so that it is correctly formatted as code. In future, please follow the MiniHowTo instructions on presenting code/command output as per the previous post in this topic.

1 Like

Probably unrelated, but your BIOS is out of date, new one HERE

The first user created by the installer will be member of the group wheel which has super user permissions.

Even so - the user does not have direct access to e.g. USB devices or other system related devices, folders etc.

You will still need group membership to have GUI applications access devices. For accessing devices through command line interfaces you will often use sudo to alter or access devices directly.

For accessing and manipulating ttyUSBx devices, membership of the group uucp is required.

what is the output of

lsusb

I have several usb->serial devices - all of them is accessible through /dev/ttyUSB<num> - but do ensure you have added yourself to the uucp group

sudo gpasswd -a $USER uucp

You can monitor udev events by opening a terminal and switch to root context

sudo su

Remove your USB device and run the following command udevadm monitor, then attach your device. You should get an output similar to

# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[2890.147158] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
KERNEL[2890.187702] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
KERNEL[2890.187811] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
UDEV  [2890.212716] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
KERNEL[2890.217979] add      /bus/usb/drivers/ch341 (drivers)
KERNEL[2890.218044] add      /bus/usb-serial/drivers/ch341-uart (drivers)
KERNEL[2890.218097] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
UDEV  [2890.219053] add      /bus/usb/drivers/ch341 (drivers)
UDEV  [2890.219656] add      /bus/usb-serial/drivers/ch341-uart (drivers)
KERNEL[2890.229674] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0/tty/ttyUSB0 (tty)
KERNEL[2890.229743] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
KERNEL[2890.229870] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
UDEV  [2890.230032] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
KERNEL[2890.230110] add      /module/ch341 (module)
UDEV  [2890.230891] add      /module/ch341 (module)
UDEV  [2890.251640] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
UDEV  [2890.256290] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
UDEV  [2890.261106] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0/tty/ttyUSB0 (tty)
UDEV  [2890.262566] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
UDEV  [2890.263572] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
 $ lsusb
....
Bus 003 Device 016: ID 1a86:7523 QinHeng Electronics CH340 serial converter
....

This is another adapter

# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[3079.608902] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
KERNEL[3079.661599] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
KERNEL[3079.661727] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
UDEV  [3079.687462] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
KERNEL[3079.693242] add      /bus/usb/drivers/pl2303 (drivers)
KERNEL[3079.693303] add      /bus/usb-serial/drivers/pl2303 (drivers)
UDEV  [3079.695382] add      /bus/usb-serial/drivers/pl2303 (drivers)
UDEV  [3079.695473] add      /bus/usb/drivers/pl2303 (drivers)
KERNEL[3079.721441] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
KERNEL[3079.721552] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0/tty/ttyUSB0 (tty)
KERNEL[3079.721630] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
UDEV  [3079.721756] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
KERNEL[3079.721869] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)
KERNEL[3079.721927] add      /module/pl2303 (module)
UDEV  [3079.722528] add      /module/pl2303 (module)
UDEV  [3079.735294] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3 (usb)
UDEV  [3079.740975] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
UDEV  [3079.747353] add      /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0/tty/ttyUSB0 (tty)
UDEV  [3079.749123] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0/ttyUSB0 (usb-serial)
UDEV  [3079.751346] bind     /devices/pci0000:00/0000:00:03.1/0000:02:00.0/0000:03:08.0/0000:04:00.1/usb3/3-3/3-3:1.0 (usb)

 $ lsusb
....
Bus 003 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Phone Data Cable
....
2 Likes

You either misunderstood whatever you read, or whatever you read was far from accurate. There is no correlation between being the only configured user and having root privileges.

No matter whether there is one user, or many users configured on a Linux system, each user is generally able to use sudo to gain privileges necessary to perform tasks that might otherwise only be available to the Super User (root).

Failing that, there is always the option to switch to the Super User directly to perform a series of tasks – this should only be considered a temporary option – there is no world in which running as root continually is recommended.

  • su - – switches to the Super User
  • exit – switches back to the current user

As someone who has “used Debian for decades” I imagine you should already have known of all of this.

Regards.

inxi output is now here - but none of this:

How do I get access to usb ports? - #8 by Nachlese

It’s for your information.
It doesn’t need to be here if it tells you enough to begin to solve your problem.

The easiest way to check for the device file is ls /dev, then plug the device in and ls /dev again - see what’s different.

If nothing changes then you need to check logs etc for clues.

We are waiting for this information, so we can try to help you.

I was just going by what the install program said. And yes, in Debian I’d have already figured it out, since I did before. The specific commands differ just enough to complicate things. I’m giving Manjaro a chance. Snarkiness from Manjaro users is not a plus.

THAT’s what I needed. Thanks for your help!