You must be booted into the desired kernel, first.
Reboot, use the Advanced Options For Zorin to select the 6.2.0-39 kernel and on ce booted, ensure you are on that kernel
uname -r
Then run
sudo update-grub
Interesting - I did that, but as indicated, the kernel didn't change.
Tried again per your instruction and it appears the kernel is now the selected one - 6.2.0-39-generic.
Unfortunately - this does not resolve the issues I've been experiencing.
Left the computer suspended overnight. Unsuspending it, the primary mouse button was non-functional. Couldn't select to restart, power off, or anything else. I had screen sharing enabled, so connected to the computer from another computer and attempted to control it - the mouse button issue was present even across screen sharing.
Fortunately, the keyboard on the computer in question still worked, so I was able to launch terminal and shut down from there.
After starting back up - still getting USB errors on startup:
After achieving a desktop, everything functioned as expected.
Once the computer suspends, or suspends and is then taken off of suspension - this is where the issues seem to be the worst. Today, it once again lost network connectivity over ethernet, and something new - no audio. I have my speakers plugged into the audio port on the Dell D3100 docking station. The audio quit when the computer suspended - it was playing music.
Interestingly, I have the computer to suspend only when on battery power, and for the screen to blank after 15 minutes:
It is not only plugged into electrical power - it is plugged into a UPS. It should never go on battery power, and thus - should never automatically suspend. The only thing that should happen is the screen (I have an external monitor attached, plugged directly into the HDMI port on the computer) should go black after 15 minutes.
For further testing, I've turned off automatic suspend. I don't mind if the computer stays on - I do want the monitor to go off after a period of inactivity, however.
I'll keep an eye on it over the next couple of days, but sadly - it appears rolling back the kernel did not resolve the issues at hand.
Was there anything else that resulted in this post that may have contributed to it appearing successful?
I hesitate to think a later kernel is needed, due to the D3100 gaining support pretty early on.
Check your BIOS / UEFI... I had a computer once that had a 'handoff' type thing where the options were that the BIOS continue controlling USB devices after initial startup, or control was handed off to the OS during boot.
Likely you don't have it, but my computer was a Dell, so...
I wish my BIOS/UEFI was that advanced. The only mention of USB is in the Advanced>USB Configuration>USB Mass Storage Driver Support [Enabled], and in Security>I/O Interface Security>USB Interface Security - all items set as unlocked.
Screenshots:
At this juncture - I have no idea. The issues appear to be random. For instance - I restarted just now into BIOS to get the screenshots I provided. Restarted from that, and the error messages I've posted earlier did not show up. However, the mouse was unresponsive for about a minute on the desktop, then became available. About 30 seconds after that, I achieved network access via ethernet.
The only constants appear to be:
-
related to the USB bus
-
related to the Dell D3100 Dock
-
issues are present on power on, restart, or related to suspend (either entering into, being in, or coming out of suspend)
Since previously mentioned, I've disabled suspend and set the monitor to blank after 15 minutes. I'll leave it that way overnight and see what occurs tomorrow morning.
Looking at this Aptio BIOS screen. The status of USB is ambiguous "UNLOCK". Does that really mean USB is unlocked or asking to click to unlock. What are the options when you click that item. i.e. is the alternative to "UNLOCK" actually "LOCKED"?
Out of curiosity I have been doing some websearches re "Dell D3100 Dock Ubuntu". There are a few cases of displaylink problems with external monitors on D3100, resolved by updating displaylink driver. I assume you have been doing similar web searches as well.
https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=939cy
1 Like
Indeed, "UNLOCK" indicates that USB is currently unlocked. The other alternative is indeed, "LOCKED."
I am quite familiar with these issues. When the D3100 worked (for video) it worked really well. At one point in time, I was running dual monitors via the D3100; then, after various updates, I had loads of issues with it. Eventually, I ditched the dual monitors and now use a single large monitor plugged directly into the HDMI port of the computer in question, bypassing the video capabilities of the D3100.
Essentially, I'm not using the D3100 to its fullest effect. I use it as a USB hub and for the ethernet connection. For a lot of complicated reasons, I need to use ethernet in my office, and the computer I'm currently using doesn't have an ethernet port on it. So, it's Ethernet Connection>D3100>Computer's USB 3.0 port that gives me my network connection. Up until using Zorin 17, this all just worked and wasn't an issue.
Speaking of which...
Changed some of the settings and have been running with them for the past 24 hours.
Settings>Power>Screen Blank - 15 minutes
Settings>Power>Automatic Power Saver - OFF
Settings>Power>Automatic Suspend - OFF
Settings>Privacy>Screen>Blank Screen Display - 15 minutes
Settings>Privacy>Screen>Automatic Screen Lock - ON
Settings>Privacy>Screen>Automatic Screen Lock Display - 3 Minutes
Settings>Privacy>Screen>Lock Screen On Suspend - OFF
In theory, The unit stays on, and after a period of time, the external monitor shuts down.
[I say in theory, because the power indicator on the computer shows the computer is in sleep mode after a period of inactivity - which is actually desired behavior.]
Past 24 hours - power on the external monitor, input some keystrokes on the external USB keyboard, the computer has come out of suspend (if it ever actually was truly suspended), and the computer achieves a desktop with no issue - all devices and network connection intact.
So, that's a step in the right direction. Very positive.
Still - when booting up - takes a LONG time to boot as it still shows the error codes indicated in the previous screenshots.
On the occasion it does NOT show these error codes, unit quickly achieves a desktop but the keyboard and mouse are unavailable for about a minute, and the network connection comes online about 30 seconds after the keyboard and mouse have started functioning.
This is rolled back to the older kernel as previously mentioned (6.2.0-39-generic).
That is the current state of affairs.
I did a websearch re those errors. Most refer to timeout, which maybe due to a USB power issue, i.e. USB device/hub taking too much power from USB port. Or maybe you have other USB devices attached to other USB ports that are strain on +5V motherboard supply?
Maybe some comments in these links may help resolve your Dell hub errors.
Some comments suggest success from complete shut down and power off the computer and the hub for some minutes, then power on and reboot.
EDIT: Another thought. Is your laptop battery fairly new and performing well. This may be an issue affecting +5V supply, even when laptop is plugged in to mains power source.
So, the only things that were plugged into the Dell D3100:
-
An ethernet cable
-
a 64 GB USB stick (for backing up my browser bookmarks)
an Atolla USB 3.0 Hub (which shows as a Genesys Logic Inc. hub in the CLI via lsusb ):
The Atolla hub has a Micro USB power supply attached. plugged into this hub are a webcam, a microphone (Blue Snowball), and an external USB drive (8TB Seagate). The last port is left open to plug a phone into for charging.
The Seagate drive has its own power supply. As the other devices may draw more power than the D3100 may provide across its port(s), the Atolla can be powered by a Micro-USB power adapter. I have such a power adapter plugged into it.
BTW - the D3100 also has its own power supply.
Per the links you provided, I did indeed disconnect everything, and also disconnected the power supply connected to the D3100. Additionally, I unplugged the D3100's power supply from its outlet, and left it that way for about 10 minutes.
Plugged everything back in, and restarted. Issue persisted.
Then, to test - disconnected the Atolla.
shut down, started back up.
NO ERRORS on startup.
Everything worked - no lag with the keyboard and mouse.
Unplugged the power supply to the Atolla, and reconnected it. Issues were back.
Disconnected all peripherals from the Atolla (they were all turned off prior to this, but I figured let's be thorough), and reconnected it back to the D3100. Previously described issues were present.
Left the Atolla disconnected, then powered on the system - no issues. Plugged in the Atolla while the system was up and running - could use the attached peripherals.
So, as a temporary workaround - I figured I'd leave the Atolla disconnected.
Then, a new issue was introduced. It is documented here:
Now when the computer exits from suspend - I now consistently lose my network connection via ethernet and access to my external speakers - both plugged into the D3100. Interestingly, the USB stick which is attached to the D3100 shows up just fine and can be accessed.
In some ways, this is now worse. That said - while they may certainly be related, I consider the suspend a separate issue, hence creating a different thread to troubleshoot it.
That's the story as of today...
Update - I was able to successfully prevent the computer from suspending while preserving other options I feel are necessary.
Startup and login now function normally, and all usb devices currently attached function with no issue.
This is when the Atolla/Genesys Logic, Inc. Hub is disconnected.
The issues are re-introduced when the hub is attached - even if nothing is connected to it, including a power supply for it.
As a work around, I can leave the hub disconnected until I need access to the devices normally connected to it.
That said - this is not an ideal solution ("Doctor, it hurts when I do xyz." "Then, don't do xyz."), especially when there were no issues with the hub connected in this configuration using Zorin 15.3.
Well said. Drivers that are compatible are necessary for the hardware to work. What is uncertain, in my mind at least, is whether these drivers are available for GnuLniux or not.
I have tried some searching, but have also been overwhelmed with other tasks and have had less time available.
Using a work-around as a bandaid until a solution is still better than nothing at all.
I would also consider your laptop battery. I had some Weird BSOD's on my Win laptop. Whilst battery worked OK and PC also connected to mains. But new battery has improved things.
Laptop battery acts as a power regulator, so if its outpout is compromised then internal voltages may also be compromised, including USB functionality.
mainadmin@Office:~$ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: ASUSTeK
model: ASUS Battery
power supply: yes
updated: Wed 24 Jan 2024 04:31:15 PM MST (116 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: fully-charged
warning-level: none
energy: 29.209 Wh
energy-empty: 0 Wh
energy-full: 29.209 Wh
energy-full-design: 37.13 Wh
energy-rate: 0 W
voltage: 7.85 V
charge-cycles: 7
percentage: 100%
capacity: 78.6668%
technology: lithium-ion
icon-name: 'battery-full-charged-symbolic'
mainadmin@Office:~$ acpi -V
Battery 0: Not charging, 100%
Battery 0: design capacity 4729 mAh, last full capacity 3720 mAh = 78%
Adapter 0: on-line
Thermal 0: ok, 43.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 103.0 degrees C
Cooling 0: Processor 0 of 0
Cooling 1: iwlwifi_1 no state information available
Cooling 2: TCC Offset 5 of 63
Cooling 3: Processor 0 of 0
Cooling 4: INT3400 Thermal no state information available
Cooling 5: Processor 0 of 0
Cooling 6: B0D4 no state information available
Cooling 7: intel_powerclamp no state information available
Cooling 8: x86_pkg_temp no state information available
Cooling 9: Processor 0 of 0
Cooling 10: SEN1 no state information available
I don't know how accurate that info is. But says battery design capacity is 4729 mAh but you only got 3720 mAh = 78% when 100% charged. Have you done some battery calibration cycles e.g. full drain then full charge and repeat?
I would think that offers some evidence that a new battery may be a good investment, especially if you are attaching several devices to USB, whether they are self powered or not.
If a new battery does not help, then nothing is lost as you can keep it as a spare. Just keep it charged at about 50-60% when removed.
1 Like
Issue still persists.
Are you reporting this after having taken action such as calibration or battery replacement?
Battery has been calibrated:
As well as there have been several software updates since this issue was initially reported, and none of them have resolved the issue.
Work around which has been employed - I stopped using the hub. This is not desirable, but gets the job done.
A potential alternate work around - I could use another distro which does not exhibit the issue, but I do prefer to use Zorin. It would be nice to see this issue resolved.
1 Like
I agree. This does imply that the issue lies with the HUB and some Zorin system issue.
Can I ask which distro has this corrected? That may help to look for a solution within the open source community.
Haven't attempted this. As I wrote, I could use another distro which does not exhibit the issue. Haven't tried, yet.
My next attempt will be with Debian - it checks most of the boxes I need, so I can give that a go and see if the most current version resolves the issue.
1 Like