Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Could the encrypted swap be the problem?
In /etc/fstab comment out the /dev/mapper/cryptswap line and reboot and see if that makes a difference.
If you have enough RAM, swap is not needed, and I think PopOS is enabling zram to compress unused memory rather then sending to swap.
I've commented it out but saw no change in boot speed.
I don't worry too much about slow boot - it can be looked at at leisure later as is happening. It can be ameliorated pretty easily too:
- don't boot (so often)
- go get a coffee while it does.
Quote:
Originally Posted by christopherlinux
... it takes around 2 minutes to open applications like chrome, vscode, docker (starting with systemctl), spotify. In addition, file transfer speeds are weirdly slow given that I am on an SSD, but I see around 13mbps transfer speeds when copying files on my SSD.
This however, I would be real worried about. To me that sounds like a dodgy driver although that interrupts listing looks ok (yes, the hw-probe was a great idea). It hadn't been up long though, can you post /proc/interrupts (and uptime output) here after the system has been active for a while for comparison.
Not only is boot slow, but I do also get slow performance when its running and its frequent for my computer to entirely freeze.
This is a symptom set of an SSD doomed to die soon. Make sure your backup system is enabled and working. Try running hdparm -t multiple times to see both how speed compares to the product's claim of speed, and to see how consistent the results. If you're getting results that vary more than around 10MB/s or so, odds are the SSD should be RMA'd. You should definitely not see:
Code:
# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 352 MB in 3.01 seconds = 116.86 MB/sec
# hdparm -t /dev/sdb
/dev/sdb:
Timing buffered disk reads: 2 MB in 3.11 seconds = 659.44 kB/sec
# hdparm -t /dev/sdb12
/dev/sdb12:
Timing buffered disk reads: 6 MB in 3.77 seconds = 1.59 MB/sec
# hdparm -t /dev/sdb23
/dev/sdb23:
Timing buffered disk reads: 528 MB in 3.01 seconds = 175.54 MB/sec
# hdparm -t /dev/sdb34
/dev/sdb34:
Timing buffered disk reads: 698 MB in 3.00 seconds = 232.35 MB/sec
# hdparm -t /dev/sdb36
/dev/sdb36:
Timing buffered disk reads: 334 MB in 3.59 seconds = 92.99 MB/sec
# hdparm -t /dev/sdb27
/dev/sdb27:
Timing buffered disk reads: 508 MB in 3.01 seconds = 169.00 MB/sec
# hdparm -t /dev/sdb18
/dev/sdb18:
Timing buffered disk reads: 610 MB in 3.01 seconds = 202.93 MB/sec
if the manufacturer claims up to 550MB/s, as happened to me over the past several hours. I'm awaiting a response from Silicon Power warranty dept. for its 256G ACE A55 I bought 15 months ago that has seen only 138 hours of use. This is the 5th brand of SSD to die on me since buying my first one in 2017. Compressed imaging this SSD to EXT4 HDD filesystem in preparation for RMA just finished in 03:29:18 HMS @19.45MiB/sec sector throughput, 7.57MiB/sec image write speed to a HDD that reads @116.57 MiB/s with an SATA 2.0/3Gb/s motherboard. Only the sdb34 test result above is near what it should be on this motherboard.
Well. Good thing you followed my hardware check link I showed you.
Scratch my previous update kernel reply. Now with more info I see you are on version 6.xxx .
I am not gaming laptop proficient. All my gear is is usually 100 bucks or less.
dmesg shows a bunch of
Code:
[ 0.020616] On node 0, zone DMA32: 1024 pages in unavailable ranges
[ 0.020618] On node 0, zone DMA32: 1 pages in unavailable ranges
[ 0.020722] On node 0, zone DMA32: 1 pages in unavailable ranges
[ 0.021160] On node 0, zone DMA32: 34647 pages in unavailable ranges
[ 0.072428] On node 0, zone Normal: 7425 pages in unavailable ranges
[ 0.072532] On node 0, zone Normal: 8192 pages in unavailable ranges
For ram. Above my pay grade to interpet that.
This might be serious
Code:
[ 60.077116] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[ 64.453215] rfkill: input handler disabled
Looking through modprobe.d. Sure is a lot of blacklisting going on
Did you md5sum check your PopOS download before your install?
I don't worry too much about slow boot - it can be looked at at leisure later as is happening. It can be ameliorated pretty easily too:
- don't boot (so often)
- go get a coffee while it does.
This however, I would be real worried about. To me that sounds like a dodgy driver although that interrupts listing looks ok (yes, the hw-probe was a great idea). It hadn't been up long though, can you post /proc/interrupts (and uptime output) here after the system has been active for a while for comparison.
My computer has been running for a bit, feels like its about to freeze up again. Here is /proc/interrupts
Did you md5sum check your PopOS download before your install?
I did not, however my laptop installed from the same USB afterwards works great (also pop os).
My laptop also accepted Ubuntu while my Desktop did not.
I did not, however my laptop installed from the same USB afterwards works great (also pop os).
My laptop also accepted Ubuntu while my Desktop did not.
My SSD was also working very well on windows.
OK. Kinda out of ideas here. If I was in your shoes. I'd use Ubuntu with the model number hardware checker shows your gear and start my own exhaustive search to see if anyone else runs into what you are going through using Ubuntu. Since PopOS is ubuntu under the hood.
Example
On Windows, my computer boots in seconds and applications open nearly instantly.
SSDs are typically made with 2 or 4 chips. If Windows is using less than half the disk size, there could be a failing SSD chip that only Linux is trying to use. You could wipe the SSD, install Linux first or force Windows onto the last half of the disk, to see if it is a failing SSD issue. First run smartctl -t long on the SSD, and/or the SSD maker's media evaluation software.
For me and others ubuntu - and derivatives lubuntu, Pop etc are just going to be slow in every situation...
Especially if they have KDE, Xfce or LXQT..
For example Lubuntu uses more than double the resource of my Antix-22 Full LXDE setup – suppose Pop will be same if not worse?
Had a look at dmseg1.txt and it shows hardware errors, bios upgrade recommendation and bugs: [ 44.257385] kernel: dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
Next https://bugzilla.kernel.org/show_bug.cgi?id=201885
Starting at the below in dmesg1.txt I think that's your atheros WNIC [ 46.423363] kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:04:00.0
and next [ 46.283800] kernel: ath10k_pci 0000:04:00.0: enabling device (0000 -> 0002)
And this repeats for awhiiile...
At the below... another bug [ 49.214420] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.PEG0.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
And the other dmesg files you have provided are filled with the errors...
Welcome to the journey towards optimising your linux install for your device/needs ( ͡~ ͜ʖ ͡°)
There could other hurdles later such as your X environment / optimus setup; ssd throughput; etc but first lets clean up those errors.
Last edited by yvesjv; 01-20-2023 at 05:26 PM.
Reason: typos
Had a look at dmseg1.txt and it shows hardware errors, bios upgrade recommendation and bugs: [ 44.257385] kernel: dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
