No network interface for Venus modem

ReYuki · 2024-08-24 05:26:47

I have an old Qualcomm-based Venus mobile cellular modem. I attempted to get it working on my Linux machine by following the instructions on arch wiki page. However, after switching modes, I can't find any additional interfaces using the ip link command, and /dev/ttyUSB* devices are also missing.

I'll provide necessary information through this link, I will provide more if needed.

from the lsusb output, it seems to me that the device wasn't handled by a proper driver or kernel module? But I'm not sure how to fix these things, any help would be greatly appreciated. Thank you in advance for your time!

ReYuki · 2024-08-24 07:42:55

I tried to load option module, but it seems the interface still isn't available

[hemlo@ASUS ~]$  sudo modprobe option
[hemlo@ASUS ~]$  lsmod | grep option
option                 61440  0
usb_wwan               28672  1 option
[hemlo@ASUS ~]$  ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:08:e2:c0 brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether f6:4f:f7:da:f2:36 brd ff:ff:ff:ff:ff:ff permaddr 10:68:38:8d:f3:79

just4arch · 2024-08-24 08:24:14

Have you read https://wiki.archlinux.org/title/USB_3G_Modem?

Your dmesg indicates it loads as storage device and needs to switch modes for modem mode.

ReYuki · 2024-08-24 11:52:51

Yes, I've already install usb_modeswitch and lsusb output on the link provided show additional device after installing usb_modeswitch package

Last edited by ReYuki (2024-08-24 11:53:05)

Lone_Wolf · 2024-08-24 13:36:56

[65810.455242] usb 1-1.1: Product: CDMA 1x/EVDO Rev.A Device

searching for that + linux pointed to https://askubuntu.com/questions/502597/ … -04#748197 which indicates this modem may need the usbserial kernel module .

try running (as root)

modprobe usbserial vendor=0x1d09 product=aef4

ReYuki · 2024-08-25 04:56:41

I tried your instruction, but the interface still not show up

[hemlo@ASUS ~]$  ls /dev/sr0
/dev/sr0
[hemlo@ASUS ~]$  sudo eject sr0
[hemlo@ASUS ~]$  sudo modprobe usbserial vendor=1d09 product=aef4
[hemlo@ASUS ~]$  modinfo usbserial
name:           usbserial
filename:       (builtin)
license:        GPL v2
file:           drivers/usb/serial/usbserial
description:    USB Serial Driver core
author:         Greg Kroah-Hartman <gregkh@linuxfoundation.org>
parm:           vendor:User specified USB idVendor (ushort)
parm:           product:User specified USB idProduct (ushort)

[hemlo@ASUS ~]$  ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:08:e2:c0 brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 2e:bf:21:d1:fc:d0 brd ff:ff:ff:ff:ff:ff permaddr 10:68:38:8d:f3:79

Lone_Wolf · 2024-08-25 10:44:51

but the interface still not show up

Given the age and type of the modem there is a big chance no network interface will be created automagickally.
Once the correct devices to control the modem are present you probably will need to use modemmanager, maybe even wvdial .

After running the modprobe usbserial command
run as root dmesg | tail -n 100 and post the output .

Then look for new devices in /dev , especially those whose names start with ttyUSB .

ReYuki · 2024-08-25 12:40:38

dmesg | tail -n 100 output:

[   38.102619] ------------[ cut here ]------------
[   38.102620] WARNING: CPU: 6 PID: 227 at include/linux/rwsem.h:80 follow_pte+0x1de/0x200
[   38.102622] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_usb_audio snd_usbmidi_lib snd_ump uas snd_rawmidi usb_storage snd_seq_device btusb btrtl btintel btbcm btmtk bluetooth amd_atl intel_rapl_msr vfat fat intel_rapl_common amdgpu snd_sof_amd_acp63 snd_sof
_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_pci_ps snd_amd_sdw_acpi soundwire_amd soundwire_generic_allocation soundwire_bus snd_soc_core amdxcp drm_exec snd_compress gpu_sched ac97_bus kvm_
amd mt7921e snd_pcm_dmaengine drm_buddy mt7921_common snd_rpl_pci_acp6x i2c_algo_bit mt792x_lib snd_acp_pci drm_suballoc_helper mt76_connac_lib kvm snd_acp_legacy_common drm_ttm_helper snd_hda_codec_realtek snd_pci_acp6x mt76 ttm snd_hda_codec_generic snd_pci_acp5x snd_hda
_scodec_component snd_rn_pci_acp3x snd_hda_codec_hdmi crct10dif_pclmul drm_display_helper snd_acp_config crc32_pclmul snd_hda_intel mac80211 snd_soc_acpi polyval_clmulni cec ccp snd_intel_dspcfg snd_pci_acp3x
[   38.102655]  polyval_generic gf128mul snd_intel_sdw_acpi ghash_clmulni_intel snd_hda_codec libarc4 sha512_ssse3 snd_hda_core joydev sha256_ssse3 snd_hwdep sha1_ssse3 mousedev cfg80211 snd_pcm uvcvideo r8169 aesni_intel asus_nb_wmi ucsi_acpi snd_timer asus_wmi videobuf2_
vmalloc typec_ucsi realtek uvc crypto_simd platform_profile snd typec mdio_devres videobuf2_memops sparse_keymap cryptd sp5100_tco hid_multitouch thunderbolt libphy rfkill rapl soundcore nvidia_wmi_ec_backlight pcspkr wmi_bmof i2c_piix4 k10temp roles videobuf2_v4l2 i2c_hid
_acpi amd_pmc i2c_hid videodev mac_hid videobuf2_common mc crypto_user loop dm_mod nfnetlink ip_tables x_tables ext4 hid_generic crc32c_generic crc16 mbcache jbd2 usbhid serio_raw atkbd libps2 vivaldi_fmap nvme nvme_core xhci_pci crc32c_intel i8042 xhci_pci_renesas nvme_au
th serio nvidia_drm(POE) nvidia_uvm(POE) nvidia_modeset(POE) video wmi nvidia(POE)
[   38.102692] CPU: 6 PID: 227 Comm: nv_queue Tainted: P        W  OE      6.10.6-arch1-1 #1 703d152c24f1971e36f16e505405e456fc9e23f8
[   38.102693] Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507XI_FA507XI/FA507XI, BIOS FA507XI.313 03/14/2024
[   38.102694] RIP: 0010:follow_pte+0x1de/0x200
[   38.102695] Code: 12 da 00 48 81 e2 00 00 00 c0 48 09 c2 48 f7 d2 48 85 fa 75 20 e8 b2 f5 ff ff 48 8b 35 6b f1 5c 01 48 81 e6 00 00 00 c0 eb 8d <0f> 0b 48 3b 1f 0f 83 50 fe ff ff bd ea ff ff ff eb b6 49 8b 3c 24
[   38.102696] RSP: 0018:ffffab62c2b17b60 EFLAGS: 00010246
[   38.102698] RAX: 0000000000000000 RBX: 0000787401dfb000 RCX: ffffab62c2b17ba0
[   38.102699] RDX: ffffab62c2b17b98 RSI: 0000787401dfb000 RDI: ffff96a4598d67e8
[   38.102700] RBP: ffffab62c2b17be0 R08: ffffab62c2b17d38 R09: 0000000000000000
[   38.102700] R10: 0000000000000200 R11: 0000000000000003 R12: ffffab62c2b17ba0
[   38.102701] R13: ffffab62c2b17b98 R14: ffff96a44e7f3c80 R15: 0000000000000000
[   38.102702] FS:  0000000000000000(0000) GS:ffff96ab5e700000(0000) knlGS:0000000000000000
[   38.102703] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   38.102704] CR2: 0000620250eb7834 CR3: 000000079aa20000 CR4: 0000000000f50ef0
[   38.102705] PKRU: 55555554
[   38.102705] Call Trace:
[   38.102706]  <TASK>
[   38.102707]  ? follow_pte+0x1de/0x200
[   38.102708]  ? __warn.cold+0x8e/0xe8
[   38.102709]  ? follow_pte+0x1de/0x200
[   38.102711]  ? report_bug+0xff/0x140
[   38.102713]  ? handle_bug+0x3c/0x80
[   38.102715]  ? exc_invalid_op+0x17/0x70
[   38.102716]  ? asm_exc_invalid_op+0x1a/0x20
[   38.102719]  ? follow_pte+0x1de/0x200
[   38.102722]  follow_phys+0x49/0x110
[   38.102724]  untrack_pfn+0x55/0x120
[   38.102726]  unmap_single_vma+0xa6/0xe0
[   38.102729]  zap_page_range_single+0x122/0x1d0
[   38.102733]  unmap_mapping_range+0x116/0x140
[   38.102735]  ? __pfx__main_loop+0x10/0x10 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.102824]  nv_revoke_gpu_mappings+0x67/0xb0 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.102915]  _nv000711rm+0x35/0x100 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103055]  rm_execute_work_item+0x110/0x170 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103195]  os_execute_work_item+0x5e/0x80 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103285]  _main_loop+0x95/0x150 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103375]  kthread+0xcf/0x100
[   38.103377]  ? __pfx_kthread+0x10/0x10
[   38.103379]  ret_from_fork+0x31/0x50
[   38.103381]  ? __pfx_kthread+0x10/0x10
[   38.103382]  ret_from_fork_asm+0x1a/0x30
[   38.103386]  </TASK>
[   38.103386] ---[ end trace 0000000000000000 ]---
[   38.103391] ------------[ cut here ]------------
[   38.103392] WARNING: CPU: 6 PID: 227 at include/linux/rwsem.h:80 follow_pte+0x1de/0x200
[   38.103394] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_usb_audio snd_usbmidi_lib snd_ump uas snd_rawmidi usb_storage snd_seq_device btusb btrtl btintel btbcm btmtk bluetooth amd_atl intel_rapl_msr vfat fat intel_rapl_common amdgpu snd_sof_amd_acp63 snd_sof
_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_pci_ps snd_amd_sdw_acpi soundwire_amd soundwire_generic_allocation soundwire_bus snd_soc_core amdxcp drm_exec snd_compress gpu_sched ac97_bus kvm_
amd mt7921e snd_pcm_dmaengine drm_buddy mt7921_common snd_rpl_pci_acp6x i2c_algo_bit mt792x_lib snd_acp_pci drm_suballoc_helper mt76_connac_lib kvm snd_acp_legacy_common drm_ttm_helper snd_hda_codec_realtek snd_pci_acp6x mt76 ttm snd_hda_codec_generic snd_pci_acp5x snd_hda
_scodec_component snd_rn_pci_acp3x snd_hda_codec_hdmi crct10dif_pclmul drm_display_helper snd_acp_config crc32_pclmul snd_hda_intel mac80211 snd_soc_acpi polyval_clmulni cec ccp snd_intel_dspcfg snd_pci_acp3x
[   38.103428]  polyval_generic gf128mul snd_intel_sdw_acpi ghash_clmulni_intel snd_hda_codec libarc4 sha512_ssse3 snd_hda_core joydev sha256_ssse3 snd_hwdep sha1_ssse3 mousedev cfg80211 snd_pcm uvcvideo r8169 aesni_intel asus_nb_wmi ucsi_acpi snd_timer asus_wmi videobuf2_
vmalloc typec_ucsi realtek uvc crypto_simd platform_profile snd typec mdio_devres videobuf2_memops sparse_keymap cryptd sp5100_tco hid_multitouch thunderbolt libphy rfkill rapl soundcore nvidia_wmi_ec_backlight pcspkr wmi_bmof i2c_piix4 k10temp roles videobuf2_v4l2 i2c_hid
_acpi amd_pmc i2c_hid videodev mac_hid videobuf2_common mc crypto_user loop dm_mod nfnetlink ip_tables x_tables ext4 hid_generic crc32c_generic crc16 mbcache jbd2 usbhid serio_raw atkbd libps2 vivaldi_fmap nvme nvme_core xhci_pci crc32c_intel i8042 xhci_pci_renesas nvme_au
th serio nvidia_drm(POE) nvidia_uvm(POE) nvidia_modeset(POE) video wmi nvidia(POE)
[   38.103465] CPU: 6 PID: 227 Comm: nv_queue Tainted: P        W  OE      6.10.6-arch1-1 #1 703d152c24f1971e36f16e505405e456fc9e23f8
[   38.103466] Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507XI_FA507XI/FA507XI, BIOS FA507XI.313 03/14/2024
[   38.103467] RIP: 0010:follow_pte+0x1de/0x200
[   38.103469] Code: 12 da 00 48 81 e2 00 00 00 c0 48 09 c2 48 f7 d2 48 85 fa 75 20 e8 b2 f5 ff ff 48 8b 35 6b f1 5c 01 48 81 e6 00 00 00 c0 eb 8d <0f> 0b 48 3b 1f 0f 83 50 fe ff ff bd ea ff ff ff eb b6 49 8b 3c 24
[   38.103470] RSP: 0018:ffffab62c2b17b60 EFLAGS: 00010246
[   38.103471] RAX: 0000000000000000 RBX: 0000787401a34000 RCX: ffffab62c2b17ba0
[   38.103472] RDX: ffffab62c2b17b98 RSI: 0000787401a34000 RDI: ffff96a455813d78
[   38.103473] RBP: ffffab62c2b17be0 R08: ffffab62c2b17d38 R09: 0000000000000000
[   38.103474] R10: 0000000000000200 R11: 0000000000000003 R12: ffffab62c2b17ba0
[   38.103475] R13: ffffab62c2b17b98 R14: ffff96a44e7f3c80 R15: 0000000000000000
[   38.103476] FS:  0000000000000000(0000) GS:ffff96ab5e700000(0000) knlGS:0000000000000000
[   38.103477] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   38.103478] CR2: 0000620250eb7834 CR3: 000000079aa20000 CR4: 0000000000f50ef0
[   38.103479] PKRU: 55555554
[   38.103479] Call Trace:
[   38.103480]  <TASK>
[   38.103481]  ? follow_pte+0x1de/0x200
[   38.103482]  ? __warn.cold+0x8e/0xe8
[   38.103483]  ? follow_pte+0x1de/0x200
[   38.103485]  ? report_bug+0xff/0x140
[   38.103487]  ? handle_bug+0x3c/0x80
[   38.103490]  ? exc_invalid_op+0x17/0x70
[   38.103493]  ? asm_exc_invalid_op+0x1a/0x20
[   38.103497]  ? follow_pte+0x1de/0x200
[   38.103500]  follow_phys+0x49/0x110
[   38.103503]  untrack_pfn+0x55/0x120
[   38.103505]  unmap_single_vma+0xa6/0xe0
[   38.103507]  zap_page_range_single+0x122/0x1d0
[   38.103511]  unmap_mapping_range+0x116/0x140
[   38.103514]  ? __pfx__main_loop+0x10/0x10 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103604]  nv_revoke_gpu_mappings+0x67/0xb0 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103698]  _nv000711rm+0x35/0x100 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103849]  rm_execute_work_item+0x110/0x170 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.103990]  os_execute_work_item+0x5e/0x80 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.104094]  _main_loop+0x95/0x150 [nvidia 3face4ec9b037e6f10bf63831564be785338a096]
[   38.104184]  kthread+0xcf/0x100
[   38.104187]  ? __pfx_kthread+0x10/0x10
[   38.104189]  ret_from_fork+0x31/0x50
[   38.104191]  ? __pfx_kthread+0x10/0x10
[   38.104192]  ret_from_fork_asm+0x1a/0x30
[   38.104196]  </TASK>
[   38.104196] ---[ end trace 0000000000000000 ]---
[   56.790454] r8169 0000:03:00.0 enp3s0: Link is Down
[   63.314444] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[   63.691501] r8169 0000:03:00.0 enp3s0: Link is Down
[   77.159856] Generic FE-GE Realtek PHY r8169-0-300:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling!
[   77.159899] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full (downshifted) - flow control off
[  313.477246] EXT4-fs (nvme1n1p3): error count since last fsck: 36
[  313.477255] EXT4-fs (nvme1n1p3): initial error at time 1724585590: ext4_orphan_get:1420
[  313.477259] EXT4-fs (nvme1n1p3): last error at time 1724585590: ext4_orphan_get:1420

I don't see any output related to modem after executing the modprobe usbserial command

and I also check /dev/ttyUSB* with ls and can not find the correspond device.

Lone_Wolf · 2024-08-26 08:39:32

The dmesg output does indeed not show entries related to the venus device, but shows what looks like a coredump .

Also these lines

[  313.477246] EXT4-fs (nvme1n1p3): error count since last fsck: 36
[  313.477255] EXT4-fs (nvme1n1p3): initial error at time 1724585590: ext4_orphan_get:1420
[  313.477259] EXT4-fs (nvme1n1p3): last error at time 1724585590: ext4_orphan_get:1420

suggests data corruption is happening on atleast one of your partitions.

Please reboot and run (as root)

journalctl -b | curl -F 'file=@-' 0x0.st

It will upload a the journal for your current boot to a public hosting site and output a link to it.
Post that link .

You should also run a SMART drivetest, see https://wiki.archlinux.org/title/S.M.A.R.T.

Last edited by Lone_Wolf (2024-08-26 08:40:56)

ReYuki · 2024-08-26 14:16:51

Thanks for sticking with me this far!

Lone_Wolf wrote:

The dmesg output does indeed not show entries related to the venus device, but shows what looks like a coredump .

It seems the coredump is related to the NVidia driver issue, though I don't know exactly what is the problem.

Lone_Wolf wrote:

Also these lines

[  313.477246] EXT4-fs (nvme1n1p3): error count since last fsck: 36
[  313.477255] EXT4-fs (nvme1n1p3): initial error at time 1724585590: ext4_orphan_get:1420
[  313.477259] EXT4-fs (nvme1n1p3): last error at time 1724585590: ext4_orphan_get:1420

suggests data corruption is happening on atleast one of your partitions.

Sorry, I didn’t realize that. Will this issue affect the modem's functionality?

Lone_Wolf wrote:

Please reboot and run (as root)
journalctl -b | curl -F 'file=@-' 0x0.st
It will upload a the journal for your current boot to a public hosting site and output a link to it.
Post that link .

I've reboot my laptop and post the journalctl on this link as you suggest.

Lone_Wolf wrote:

You should also run a SMART drivetest, see https://wiki.archlinux.org/title/S.M.A.R.T.

unfortunately, the SMART support was not available on my NVMe drives (you can visit my hw-info probe if you need):

root@ASUS reyuki]#  smartctl --smart=on /dev/nvme1n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.6-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

[root@ASUS reyuki]# smartctl --info /dev/nvme1n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.6-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       MSI M461 2TB
Serial Number:                      511231006031000638
Firmware Version:                   ELFMC1.0
PCI Vendor/Subsystem ID:            0x1987
IEEE OUI Identifier:                0x6479a7
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,000,398,934,016 [2.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            6479a7 845ac01783
Local Time is:                      Mon Aug 26 20:49:18 2024 WIB

[root@ASUS reyuki]#  smartctl --info /dev/nvme1n1 | grep 'SMART support is:'

Currently, my modem isn’t plugged into my laptop. and although this isn’t directly related to our discussion, I’ll provide the following information to clarify the usb error on journalctl logs, I connected my phone to usb 1-2 while trying to use ADB, but it seems the phone isn’t being detected by the Linux kernel. I’m not sure if the issue is caused by the usb_modeswitch package or if the USB cable might be broken.

I tried one of the solutions I found on the internet, but it didn’t work:

[hemlo@ASUS ~]$  modinfo usbcore
name:           usbcore
filename:       (builtin)
license:        GPL
file:           drivers/usb/core/usbcore
parm:           quirks:Add/modify USB quirks by specifying quirks=vendorID:productID:quirks
parm:           usbfs_snoop:true to log all usbfs traffic (bool)
parm:           usbfs_snoop_max:maximum number of bytes to print while snooping (uint)
parm:           usbfs_memory_mb:maximum MB allowed for usbfs buffers (0 = no limit) (uint)
parm:           authorized_default:Default USB device authorization: 0 is not authorized, 1 is authorized (default), 2 is authorized for internal devices, -1 is authorized (same as 1) (int)
parm:           blinkenlights:true to cycle leds on hubs (bool)
parm:           initial_descriptor_timeout:initial 64-byte descriptor request timeout in milliseconds (default 5000 - 5.0 seconds) (int)
parm:           old_scheme_first:start with the old device initialization scheme (bool)
parm:           use_both_schemes:try the other device initialization scheme if the first one fails (bool)
parm:           nousb:bool
parm:           autosuspend:default autosuspend delay (int)
[hemlo@ASUS ~]$  sudo modprobe usbcore autosuspend=-1
[sudo] password for reyuki:
[hemlo@ASUS ~]$  sudo modprobe usbcore autosuspend=0

Last edited by ReYuki (2024-08-26 14:25:01)

ReYuki · 2024-08-26 14:51:49

by the way, problem with phone usb connection solved, I just need to make sure it's set to -1 on /sys/module/usbcore/parameters/autosuspend file.

Lone_Wolf · 2024-08-27 11:46:53

ReYuki wrote:

Lone_Wolf wrote:
Also these lines
[  313.477246] EXT4-fs (nvme1n1p3): error count since last fsck: 36
[  313.477255] EXT4-fs (nvme1n1p3): initial error at time 1724585590: ext4_orphan_get:1420
[  313.477259] EXT4-fs (nvme1n1p3): last error at time 1724585590: ext4_orphan_get:1420
suggests data corruption is happening on atleast one of your partitions.
Sorry, I didn’t realize that. Will this issue affect the modem's functionality?

hard to tell . but data corruption is often a symptom of hardware issues and always a bad sign.
It should be looked at.

ReYuki wrote:

unfortunately, the SMART support was not available on my NVMe drives (you can visit my hw-info probe if you need):

They do support smart and the hw-info probe does include smarctl logs from june 30 .

Use smartctl -a / --all instead of --info to get error related info .

I'll look at the journal later today.

ReYuki · 2024-08-28 04:03:15

on the log it says no error logged:

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

but it mention some failure (?):

Read Self-test Log failed: Invalid Field in Command (0x002)

Lone_Wolf · 2024-08-28 11:52:03

https://bbs.archlinux.org/viewtopic.php … 6#p2128176 should help investigating further.

The journal doesn't show disk errors, so it may have been a temporary issue like those sometimes caused by an unexpected hard poweroff.

Your system has 2 graphics car, an integrated amdgpu and a nvidia card .
It looks very much like a hybrid graphics system and the nvidia drivers are loaded before the amdgpu has even started to initialise .

In your mkinitcpio.conf add amdgpu to the modules=- line before any other listed modules.

Also post the full output of lspci -k

ReYuki · 2024-08-29 03:25:40

Lone_Wolf wrote:

Your system has 2 graphics car, an integrated amdgpu and a nvidia card .
It looks very much like a hybrid graphics system and the nvidia drivers are loaded before the amdgpu has even started to initialise .
In your mkinitcpio.conf add amdgpu to the modules=- line before any other listed modules.

is there any problem if the nvidia drivers are loaded before the amdgpu?

Lone_Wolf wrote:

Also post the full output of lspci -k

0x0.st

ReYuki · 2024-08-29 05:18:06

Lone_Wolf wrote:

[65810.455242] usb 1-1.1: Product: CDMA 1x/EVDO Rev.A Device
searching for that + linux pointed to https://askubuntu.com/questions/502597/ … -04#748197 which indicates this modem may need the usbserial kernel module .
try running (as root)
modprobe usbserial vendor=0x1d09 product=aef4

I discovered how to create /dev/ttyUSB* from this post:

# echo 1d09 aef4  >/sys/bus/usb-serial/drivers/generic/new_id
#  ls /dev/ttyUSB*
/dev/ttyUSB0  /dev/ttyUSB1  /dev/ttyUSB2
#  lsusb -vt
<omitted output>
    |__ Port 002: Dev 009, If 0, Class=Vendor Specific Class, Driver=usbserial_generic, 12M
        ID 1d09:aef4 TechFaith Wireless Technology Limited
    |__ Port 002: Dev 009, If 1, Class=Vendor Specific Class, Driver=usbserial_generic, 12M
        ID 1d09:aef4 TechFaith Wireless Technology Limited
    |__ Port 002: Dev 009, If 2, Class=Vendor Specific Class, Driver=usbserial_generic, 12M
        ID 1d09:aef4 TechFaith Wireless Technology Limited
    |__ Port 002: Dev 009, If 3, Class=Mass Storage, Driver=usb-storage, 12M
<omitted output>

Before setting up a network interface, establishing an internet connection, or reading/writing SMS messages, I want to ensure my laptop can communicate properly with the modem. I tried using mmcli, but it wasn’t able to detect the modem:

#  mmcli -S
successfully requested to scan devices
#  mmcli -L
No modems were found

Lone_Wolf · 2024-08-29 08:55:46

Although it's unclear if that user ever managed to get things working, the stackexchange posts give useful info.

Before creating those ports , run lsmod | grep option
If option is loaded, rmmod it.

create the ttyUSB ports

Run and post the outputs

# modprobe option
# lsmod | grep option
# dmesg | tail -n 100

Added

is there any problem if the nvidia drivers are loaded before the amdgpu?

If this was a hybrid graphics system, yes .

The lspci -k output shows both cards as vga compatible controllers which indicates they act independent and are not using hybrid graphics .

Which card is your primary monitor connected to ?
If nvidia then setup is fine.

Last edited by Lone_Wolf (2024-08-29 09:06:03)

ReYuki · 2024-08-30 01:41:23

Lone_Wolf wrote:

Added
is there any problem if the nvidia drivers are loaded before the amdgpu?
If this was a hybrid graphics system, yes .
The lspci -k output shows both cards as vga compatible controllers which indicates they act independent and are not using hybrid graphics .
Which card is your primary monitor connected to ?
If nvidia then setup is fine.

my primary monitor use amd by default (I install the nvidia driver and leave the rest of Xorg configuration to default settings)

[hemlo@ASUS ~]$  xrandr --listproviders --listmonitors
Providers: number : 2
Provider 0: id: 0x5b cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 9 associated providers: 1 name:AMD Radeon 780M @ pci:0000:66:00.0
Provider 1: id: 0x1fd cap: 0x2, Sink Output crtcs: 4 outputs: 4 associated providers: 1 name:NVIDIA-G0
Monitors: 2
 0: +*eDP-1 1920/344x1080/193+0+0  eDP-1
 1: +HDMI-1-0 1920/480x1080/270+1920+0  HDMI-1-0

and for hybrid mechanism, I use prime-run and only use it when necessary

alright, I will insert amdgpu as you suggest:

MODULES=(amdgpu nvidia nvidia-modeset nvidia-uvm nvidia-drm)

ReYuki · 2024-08-30 02:04:22

Lone_Wolf wrote:

Although it's unclear if that user ever managed to get things working, the stackexchange posts give useful info.

Before creating those ports , run lsmod | grep option
If option is loaded, rmmod it.
create the ttyUSB ports
Run and post the outputs
# modprobe option
# lsmod | grep option
# dmesg | tail -n 100

Are you suggesting that to start fresh by undoing the previous changes and recreating the device node? alright then: here's the log

[root@ASUS reyuki]#  lsmod | grep option
option                 61440  0
usb_wwan               28672  1 option
[root@ASUS reyuki]#  rmmod option
[root@ASUS reyuki]#  echo 1d09 aef4  >/sys/bus/usb-serial/drivers/option1/new_id
bash: /sys/bus/usb-serial/drivers/option1/new_id: No such file or directory
[root@ASUS reyuki]#  modprobe option
[root@ASUS reyuki]#  echo 1d09 aef4  >/sys/bus/usb-serial/drivers/option1/new_id
[root@ASUS reyuki]#  lsmod | grep option
option                 61440  0
usb_wwan               28672  1 option
[root@ASUS reyuki]#  dmesg | tail -n 100
[    6.981745] fbcon: amdgpudrmfb (fb0) is primary device
[    6.981942] [drm] DSC precompute is not needed.
[    6.984477] amdgpu 0000:66:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:223
[    6.986744] amdgpu 0000:66:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:231
[    6.987623] usb 1-1.4: New USB device found, idVendor=0406, idProduct=2814, bcdDevice= 1.10
[    6.987628] usb 1-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    6.987630] usb 1-1.4: Product: 2.4G Composite Devic
[    6.989061] amdgpu 0000:66:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:239
[    6.991566] amdgpu 0000:66:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:247
[    6.998257] Console: switching to colour frame buffer device 240x67
[    7.007076] amdgpu 0000:66:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[    7.081917] input: 2.4G Composite Devic as /devices/pci0000:00/0000:00:08.1/0000:66:00.3/usb1/1-1/1-1.4/1-1.4:1.0/0003:0406:2814.0008/input/input30
[    7.140610] hid-generic 0003:0406:2814.0008: input,hidraw7: USB HID v1.10 Keyboard [2.4G Composite Devic] on usb-0000:66:00.3-1.4/input0
[    7.145776] input: 2.4G Composite Devic Mouse as /devices/pci0000:00/0000:00:08.1/0000:66:00.3/usb1/1-1/1-1.4/1-1.4:1.1/0003:0406:2814.0009/input/input31
[    7.145851] input: 2.4G Composite Devic Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:66:00.3/usb1/1-1/1-1.4/1-1.4:1.1/0003:0406:2814.0009/input/input32
[    7.200578] input: 2.4G Composite Devic System Control as /devices/pci0000:00/0000:00:08.1/0000:66:00.3/usb1/1-1/1-1.4/1-1.4:1.1/0003:0406:2814.0009/input/input33
[    7.200665] hid-generic 0003:0406:2814.0009: input,hidraw8: USB HID v1.10 Mouse [2.4G Composite Devic] on usb-0000:66:00.3-1.4/input1
[    7.300418] scsi 1:0:0:0: Direct-Access     Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
[    7.301490] scsi 0:0:0:0: Direct-Access     Buildwin Media-Player     1.00 PQ: 0 ANSI: 2
[    7.302321] scsi 1:0:0:1: CD-ROM            Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
[    7.305328] sd 1:0:0:0: [sdb] Media removed, stopped polling
[    7.305613] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[    7.307449] sd 0:0:0:0: [sda] Media removed, stopped polling
[    7.307653] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    8.937173] Bluetooth: hci0: Device setup in 2603363 usecs
[    8.937184] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[    8.998752] sr 1:0:0:1: [sr0] scsi-1 drive
[    8.998762] cdrom: Uniform CD-ROM driver Revision: 3.20
[    9.014170] Bluetooth: hci0: AOSP extensions version v1.00
[    9.014179] Bluetooth: hci0: AOSP quality report is supported
[    9.136951] sr 1:0:0:1: Attached scsi CD-ROM sr0
[    9.698717] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[   10.178630] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
[   10.533806] usb 1-1.1: USB disconnect, device number 4
[   11.880782] usb 1-1.1: new full-speed USB device number 10 using xhci_hcd
[   12.107667] usb 1-1.1: New USB device found, idVendor=1d09, idProduct=aef4, bcdDevice= 0.00
[   12.107683] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[   12.107689] usb 1-1.1: Product: CDMA 1x/EVDO Rev.A Device
[   12.107693] usb 1-1.1: Manufacturer: Co.,Ltd
[   12.107697] usb 1-1.1: SerialNumber: 000000000002
[   12.174655] usb-storage 1-1.1:1.3: USB Mass Storage device detected
[   12.175191] scsi host1: usb-storage 1-1.1:1.3
[   13.195134] scsi 1:0:0:0: Direct-Access     Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
[   13.198013] sd 1:0:0:0: [sdb] Media removed, stopped polling
[   13.198547] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[   35.109281] usb 1-2: 2:1: cannot get freq at ep 0x2
[  438.608110] r8169 0000:03:00.0 enp3s0: Link is Down
[  441.518042] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  445.988068] r8169 0000:03:00.0 enp3s0: Link is Down
[  449.114812] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  466.764312] r8169 0000:03:00.0 enp3s0: Link is Down
[  469.667251] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  475.842713] r8169 0000:03:00.0 enp3s0: Link is Down
[  478.697416] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  479.211002] r8169 0000:03:00.0 enp3s0: Link is Down
[  482.041583] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  490.738917] r8169 0000:03:00.0 enp3s0: Link is Down
[  493.667467] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  575.835655] r8169 0000:03:00.0 enp3s0: Link is Down
[  578.661476] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  601.443562] r8169 0000:03:00.0 enp3s0: Link is Down
[  604.370977] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[  709.570525] r8169 0000:03:00.0 enp3s0: Link is Down
[  712.404161] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 1038.529313] r8169 0000:03:00.0 enp3s0: Link is Down
[ 1041.369738] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 1666.447543] r8169 0000:03:00.0 enp3s0: Link is Down
[ 1669.389684] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 1670.830563] r8169 0000:03:00.0 enp3s0: Link is Down
[ 1673.656293] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 1853.744527] r8169 0000:03:00.0 enp3s0: Link is Down
[ 1856.575554] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 2672.331534] r8169 0000:03:00.0 enp3s0: Link is Down
[ 2675.180381] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 4567.673324] r8169 0000:03:00.0 enp3s0: Link is Down
[ 4570.507608] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 4598.440290] r8169 0000:03:00.0 enp3s0: Link is Down
[ 4601.293522] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 4714.182996] r8169 0000:03:00.0 enp3s0: Link is Down
[ 4717.112835] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 6118.872029] perf: interrupt took too long (2564 > 2500), lowering kernel.perf_event_max_sample_rate to 78000
[ 6682.734872] perf: interrupt took too long (3265 > 3205), lowering kernel.perf_event_max_sample_rate to 61200
[10033.156841] r8169 0000:03:00.0 enp3s0: Link is Down
[10036.152500] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[12434.798907] usbcore: registered new interface driver option
[12434.798932] usbserial: USB Serial support registered for GSM modem (1-port)
[12720.421735] usbserial: USB Serial deregistering driver GSM modem (1-port)
[12720.446671] usbcore: deregistering interface driver option
[12741.202483] usbcore: registered new interface driver option
[12741.202497] usbserial: USB Serial support registered for GSM modem (1-port)
[13331.284282] usbserial: USB Serial deregistering driver GSM modem (1-port)
[13331.300115] usbcore: deregistering interface driver option
[13413.345864] usbcore: registered new interface driver option
[13413.345878] usbserial: USB Serial support registered for GSM modem (1-port)
[13414.794685] option 1-1.1:1.0: GSM modem (1-port) converter detected
[13414.794900] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB0
[13414.794954] option 1-1.1:1.1: GSM modem (1-port) converter detected
[13414.795019] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB1
[13414.795063] option 1-1.1:1.2: GSM modem (1-port) converter detected
[13414.795132] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB2
[root@ASUS reyuki]#

Lone_Wolf · 2024-08-30 10:51:24

Looking better now, time to verify what happens in what order .

Cold boot the system without the venus connected .
verify usbserial & option are not loaded .

run & post dmesg -T | tail -n 100
(the -T shows regular timestamps making the output a bit more readable)

insert the venus device,
post fresh dmesg -T | tail -n 100 and the output of lsmod | grep -i option .
Also run journalctl -b | curl -F 'file=@-' 0x0.st and post the link to ensure we get enough info.

Which further steps are needed depends on the outputs.

ReYuki · 2024-08-31 02:19:27

Lone_Wolf wrote:

Cold boot the system without the venus connected .
verify usbserial & option are not loaded .
run & post dmesg -T | tail -n 100
(the -T shows regular timestamps making the output a bit more readable)

the terminal output (it's full with nvidia error, and I doubt it'll be useful)

Lone_Wolf wrote:

insert the venus device,
post fresh dmesg -T | tail -n 100 and the output of lsmod | grep -i option .
Also run journalctl -b | curl -F 'file=@-' 0x0.st and post the link to ensure we get enough info.
Which further steps are needed depends on the outputs.

dmesg log and the journalctl log

and for option module, it'll not loaded automatically when the modem inserted, I need to modprobe it manually

Lone_Wolf · 2024-08-31 13:27:33

The first dmesg was to ensure the 2nd caught everything after that .

Create an udev rules & script file as described in the SO post with the ids for your modem.

Reboot, insert the modem and post the dmesg tail part.

ReYuki · 2024-09-01 04:47:54

Here's the dmesg output

Lone_Wolf · 2024-09-01 10:39:01

The ttyusb* ports are created, verify option & usbserial are loaded .

If they are , try giving the modem ports AT commands .

One of the things we need to do is to identify which port is the communication port.
(usually 3G modems have 1 communication port, the others are control ports or have some special purpose)

You can try wvdial & mm to see if their autodetection can handle this modem, but if they don't we'll have to use lower level tools.
minicom and socat are both in repos and can send AT commands to (serial) ports.

For mincom https://www.thegeekstuff.com/2013/05/modem-at-command/ should be helpful, socat is mentioned at https://unix.stackexchange.com/question … m-in-linux .

Note that a large part of my advice in this thread is based on experiences with a Vodafone 3G PCMCIA modem I used from 2008 to 2011 in windows AND archlinux on 2 different laptops .

ReYuki · 2024-09-02 12:10:25

the minicom program seems successfully communicate with the device through usb serial, but it can not fetch the IMEI information, does this problem are related to the SIM card by phone carrier and not a problem of modem anymore?

[root@ASUS reyuki]#  wvdialconf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: S0   S1   S2   S3   S4   S5   S6   S7
Modem Port Scan<*1>: S8   S9   S10  S11  S12  S13  S14  S15
Modem Port Scan<*1>: S16  S17  S18  S19  S20  S21  S22  S23
Modem Port Scan<*1>: S24  S25  S26  S27  S28  S29  S30  S31
ttyUSB0<*1>: ATQ0 V1 E1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB0<*1>: Modem Identifier: ATI -- Manufacturer:
ttyUSB0<*1>: Speed 9600: AT -- OK
ttyUSB0<*1>: Max speed is 9600; that should be safe.
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB2<*1>: ATQ0 V1 E1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB2<*1>: Modem Identifier: ATI -- Manufacturer:
ttyUSB2<*1>: Speed 9600: AT -- OK
ttyUSB2<*1>: Max speed is 9600; that should be safe.
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB0.
/etc/wvdial.conf<Warn>: Can't open '/etc/wvdial.conf' for reading: No such file or directory
/etc/wvdial.conf<Warn>: ...starting with blank configuration.
Modem configuration written to /etc/wvdial.conf.
ttyUSB0<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
ttyUSB2<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"

and the output from minicom:

[root@ASUS reyuki]#  minicom -s

Welcome to minicom 2.9

OPTIONS: I18n
Compiled on May  3 2024, 16:19:02.
Port /dev/ttyUSB0, 16:47:55

Press CTRL-A Z for help on special keys

AT
OK
AT+CGMI
ERROR

Last edited by ReYuki (2024-09-02 12:11:56)

Arch Linux

#1 2024-08-24 05:26:47

No network interface for Venus modem

#2 2024-08-24 07:42:55

Re: No network interface for Venus modem

#3 2024-08-24 08:24:14

Re: No network interface for Venus modem

#4 2024-08-24 11:52:51

Re: No network interface for Venus modem

#5 2024-08-24 13:36:56

Re: No network interface for Venus modem

#6 2024-08-25 04:56:41

Re: No network interface for Venus modem

#7 2024-08-25 10:44:51

Re: No network interface for Venus modem

#8 2024-08-25 12:40:38

Re: No network interface for Venus modem

#9 2024-08-26 08:39:32

Re: No network interface for Venus modem

#10 2024-08-26 14:16:51

Re: No network interface for Venus modem

#11 2024-08-26 14:51:49

Re: No network interface for Venus modem

#12 2024-08-27 11:46:53

Re: No network interface for Venus modem

#13 2024-08-28 04:03:15

Re: No network interface for Venus modem

#14 2024-08-28 11:52:03

Re: No network interface for Venus modem

#15 2024-08-29 03:25:40

Re: No network interface for Venus modem

#16 2024-08-29 05:18:06

Re: No network interface for Venus modem

#17 2024-08-29 08:55:46

Re: No network interface for Venus modem

#18 2024-08-30 01:41:23

Re: No network interface for Venus modem

#19 2024-08-30 02:04:22

Re: No network interface for Venus modem

#20 2024-08-30 10:51:24

Re: No network interface for Venus modem

#21 2024-08-31 02:19:27

Re: No network interface for Venus modem

#22 2024-08-31 13:27:33

Re: No network interface for Venus modem

#23 2024-09-01 04:47:54

Re: No network interface for Venus modem

#24 2024-09-01 10:39:01

Re: No network interface for Venus modem

#25 2024-09-02 12:10:25

Re: No network interface for Venus modem

Board footer