That command didn’t restart the network manager. Is anyone able to help with a command to restart it, as it infrequently loads before the USB NIC is seen?
I am unsure if this is possible, but how about a systemd-timer for NetworkManager.service to delay the service starting ? Or some mod to dbus-org.freedesktop.NetworkManager.service
https://wiki.archlinux.org/title/systemd/Timers
There is also the following, though I have no idea if this is applicable to manjaro or if it would work. I would be very careful with this one and if you try it have a very good backup in place. Maybe somebody who knows will chime in here.
It seems to me that something else is not right about your system. You should not have to do all of this workaround stuff. Driver issue, maybe. You haven’t posted any system information to help with figuring out what the problem or solution might be.
It might turn out that the USB adapter is incompatible and a different adapter would be option with the least amount of headaches.
If you are talking about the “network manager” the command i gave is the only one…
If it didnt restart it, then you are obviously talking about something else, which no one can guess without info…
@TriMoon, it is the default network manager for the XFCE install and the terminal output said the service couldn’t be found. I honestly have no clue why you need hardware information in order to figure out what service is running in a default install. Guessing I’ll have to stick with rebooting when the issue occurs, since it is only once in every 15-20 startups.
My first post shows the USB NIC in question. How do I find which driver is in use for the network card?
Welcome to Manjaro! 
- Please read the information behind this link. It will help you to post necessary information.
[HowTo] Provide System Information
- Please press the three dots … below your post and then press the
- If you give us information about your system, we can see what we’re talking about and make better suggestions.
- You can do this by using
inxiin a terminal or in console.
sudo inxi --admin --verbosity=7 --filter --no-host --width
- Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
- Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
- Copy the output from inxi (including the command) and paste it into your post.
- To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.
(Wisdom lies in reading 
)
It would be in the system info that was requested multiple times.
If it should not be in there that also would be worth knowing.
systemctl restart NetworkManager.service
is the command that indeed restarts the service
systemctl restart NetworkManager
will do the very same
so that remark:
is simply incorrect 
on the other hand:
is not a valid command
exactly.
Prior to the inxi command with args shared by andreas85, no command was listed that showed more than the active kernel, storage space, and RAM.
Here’s the information relative to the USB NIC;
Device-1: 2-1.2:3 info: Microchip (formerly SMSC) LAN7500 Ethernet
10/100/1000 Adapter type: Network driver: smsc75xx interfaces: 1 rev: 2.0
speed: 480 Mb/s power: 100mA chip-ID: 0424:7500 class-ID: ff00
Not explicitly but “behind” the links that @TriMoon gave in the hope that you peruse them 
Device-1: 2-1.2:3 info: Microchip (formerly SMSC) LAN7500 Ethernet
10/100/1000 Adapter type: Network driver: smsc75xx interfaces: 1 rev: 2.0
speed: 480 Mb/s power: 100mA chip-ID: 0424:7500 class-ID: ff00
From what section in the full output is this? There is no context … don’t be so stingy with information if you want help.
ps:
it could be that power saving features/software like TLP is interfering with proper and steady operation
2 Likes
I guess I am out.
It was under the USB section. Here’s censored view of the full output;
System:
Kernel: 6.1.19-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
root=UUID=e59da214-fb08-4e4a-9a0b-2f4d6e46e2c5 rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
v: 4.18.0 dm: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop System: v: N/A serial: <filter> Chassis:
type: 3 serial: <filter>
Mobo:
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Memory:
RAM: total: 5.77 GiB used: 2.52 GiB (43.6%)
Array-1: capacity: 32 GiB slots: 4 EC: None max-module-size: 8 GiB
note: est.
Device-1: DIMM3 type: DDR3 detail: synchronous size: 1024 MiB
speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: Samsung part-no: M378B2873FH0-CH9 serial: <filter>
Device-2: DIMM1 type: DDR3 detail: synchronous size: 2 GiB speed: 1333 MT/s
volts: N/A width (bits): data: 64 total: 64 manufacturer: Nanya
part-no: NT2GC64B88B0NF-CG serial: <filter>
Device-3: DIMM4 type: DDR3 detail: synchronous size: 1024 MiB
speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: Samsung part-no: M378B2873FH0-CH9 serial: <filter>
Device-4: DIMM2 type: DDR3 detail: synchronous size: 2 GiB speed: 1333 MT/s
volts: N/A width (bits): data: 64 total: 64 manufacturer: Nanya
part-no: NT2GC64B88B0NF-CG serial: <filter>
CPU:
Info: model: Intel Core i5-2320 bits: 64 type: MCP arch: Sandy Bridge
gen: core 2 level: v2 built: 2010-12 process: Intel 32nm family: 6
model-id: 0x2A (42) stepping: 7 microcode: 0x2F
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz):
Flags:
Vulnerabilities:
Type:
Graphics:
Device-1:
Audio:
Network:
Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor:
Device-2: Ralink RT2790 Wireless 802.11n 1T/2R PCIe vendor:
Device-3: Microchip (formerly SMSC) LAN7500 Ethernet 10/100/1000 Adapter
type: USB driver: smsc75xx bus-ID: 2-1.2:3 chip-ID: 0424:7500 class-ID: ff00
serial: <filter>
IF: enp0s29u1u2 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Drives:
Unmounted:
Message: No unmounted partitions found.
USB:
Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900
Device-1: 1-1.1:3 info: Logitech G105 Gaming Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s
power: 200mA chip-ID: 046d:c248 class-ID: 0300
Device-2: 1-1.4:4 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
power: 98mA chip-ID: 046d:c52b class-ID: 0300
Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900
Device-1: 2-1.2:3 info: Microchip (formerly SMSC) LAN7500 Ethernet
10/100/1000 Adapter type: Network driver: smsc75xx interfaces: 1 rev: 2.0
speed: 480 Mb/s power: 100mA chip-ID: 0424:7500 class-ID: ff00
serial: <filter>
Device-2: 2-1.4:4 info: Video,Audio
driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s
power: 500mA chip-ID: 046d:08e5 class-ID: 0102 serial: <filter>
Device-3: 2-1.8:5 info: Alcor Micro Flash Card Reader/Writer
type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s
power: 250mA chip-ID: 058f:6362 class-ID: 0806 serial: <filter>
Sensors:
System Temperatures: cpu: 41.0 C mobo: N/A gpu: radeon temp: 49.0 C
Fan Speeds (RPM): cpu: 861 mobo: 897
Info:
Processes: 227 Uptime: 5h 13m wakeups: 9 Init: systemd v: 252
default: graphical tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7
Packages: pm: pacman pkgs: 1518 libs: 402 tools: pamac,yay pm: flatpak
pkgs: 0 Shell: Bash (sudo) v: 5.1.16 running-in: gnome-terminal inxi: 3.3.25
I do appreciate your help/thoughts. @jrichard326 Sorry man. Going through the process of setting timers is a good idea and I might do that if a future update makes this a more repetitive occurrence.
To all, I apologize for not reading the linked URLs. I helped people on UF for more than ten years without ever saying “go read this, then come back” as I found it easier to just share the command to be run for getting the information.
You have to help people to help you…
No one is telepathic and none can read minds…
Anyhow, don’t mind me to exit and attend to topics where i can see info together with the problem without pulling single hairs to get what is needed to make a correct diagnosis…
It’s all good. I just wrote a script to restart the network manager on login. The hardware info wasn’t needed to find the command needed to add to the script.
But you and we could not know that.
One has to start somewhere …
Your script is also just working around the issue instead of addressing/solving the cause.
But if it works, it works …
Ever looked into power saving as the possible trigger?
Good luck!
No problem but in future:
If you know what info is needed or not then please don’t ask for help on the forum, because you obviously know better as the rest here how to solve your “problem”…
It only happened when booting from an off state, so power management shouldn’t be causing it. Installing a driver manually will just break with every new set of updates, so I’d rather just use the easiest band-aid. Thanks!
I originally asked for a command to restart the service because I knew that was the best fix for my crusty old hardware. I’ve been using one distro or another for the past fifteen years and know that updates sometimes break things and the best fixes are usually to apply band-aids until another kernel update happens and either fixes or completely drops support. Sorry for the complicated ask.
Peace out.
We all know how a jigsaw puzzle looks like with bandages all over it, if that is your way of doing then keep doing it but don’t ask for help doing that…
The majority like to put a jigsaw puzzle together with all it’s pieces fitting by them self without any bandages that let go after one piece gets updated…
PS: 15 years means you’ve just started compared to some here
Changing drivers or making custom edits to the kernel would just get broken with every new update, while writing a simple script won’t break during an update unless the service itself gets replaced. It’s the price one pays for having old hardware.