Linux - Hardware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
01-19-2023, 06:28 PM
|
#16
|
|
LQ Newbie
Registered: Jan 2023
Posts: 15
Original Poster
Rep: 
|
Quote:
Originally Posted by Debian6to11
blkid output is incomplete
|
Here is the entire output when I run blkid:
Code:
blkid
/dev/sda5: UUID="02481f90-b528-4ccf-8e1a-bfd6aaa81aa7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="419f276c-8856-425d-b477-490191b10cda"
|
|
|
|
|
01-19-2023, 06:38 PM
|
#17
|
|
LQ Newbie
Registered: Jan 2023
Posts: 15
Original Poster
Rep:
|
Quote:
Originally Posted by uteck
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. |
|
|
|
|
01-20-2023, 12:16 AM
|
#19
|
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,392
|
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. |
|
|
|
|
01-20-2023, 03:24 AM
|
#20
|
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,523
|
Quote:
Originally Posted by christopherlinux
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.
Last edited by mrmazda; 01-20-2023 at 03:27 AM.
|
|
|
|
|
01-20-2023, 05:06 AM
|
#21
|
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,392
|
Quote:
Originally Posted by christopherlinux
- On Windows, my computer boots in seconds and applications open nearly instantly.
|
If this is consistently true, I would think there is no reason to doubt the health of the device. |
|
|
|
|
01-20-2023, 10:34 AM
|
#22
|
|
LQ Veteran
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,296
|
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? |
|
|
|
|
01-20-2023, 12:31 PM
|
#23
|
|
LQ Newbie
Registered: Jan 2023
Posts: 15
Original Poster
Rep:
|
Quote:
Originally Posted by syg00
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
Code:
cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12 CPU13 CPU14 CPU15 CPU16 CPU17 CPU18 CPU19
1: 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
8: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 8-edge rtc0
9: 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi
12: 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 12-edge
14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 14-fasteoi INT3450:00
16: 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi i801_smbus, idma64.0, i2c_designware.0
17: 0 0 0 0 0 0 0 0 0 0 0 0 0 4489 0 0 0 0 0 0 IR-IO-APIC 17-fasteoi idma64.1, i2c_designware.1, snd_hda_intel:card1
120: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0
121: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 16384-edge PCIe PME, aerdrv
122: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 442368-edge PCIe PME, aerdrv, pcie-dpc
123: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 458752-edge PCIe PME, aerdrv, pcie-dpc
124: 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 468992-edge PCIe PME, aerdrv, pcie-dpc
125: 0 0 0 0 0 0 0 0 0 911186 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 376832-edge ahci[0000:00:17.0]
126: 0 0 0 0 0 0 0 0 0 0 0 49533307 0 0 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd
127: 0 0 0 0 0 0 0 0 0 0 0 0 62 0 0 0 0 0 0 0 IR-PCI-MSI 1048576-edge nvme0q0
128: 39 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048577-edge nvme0q1
129: 0 54 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048578-edge nvme0q2
130: 0 0 74 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048579-edge nvme0q3
131: 0 0 0 45 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048580-edge nvme0q4
132: 0 0 0 0 27 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048581-edge nvme0q5
133: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048582-edge nvme0q6
134: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048583-edge nvme0q7
135: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048584-edge nvme0q8
136: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048585-edge nvme0q9
137: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048586-edge nvme0q10
138: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048587-edge nvme0q11
139: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048588-edge nvme0q12
140: 0 0 0 0 0 0 0 0 0 0 0 0 58 0 0 0 0 0 0 0 IR-PCI-MSI 1048589-edge nvme0q13
141: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048590-edge nvme0q14
142: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048591-edge nvme0q15
143: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30 0 0 0 0 IR-PCI-MSI 1048592-edge nvme0q16
144: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 1048593-edge nvme0q17
145: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 75 0 0 IR-PCI-MSI 1048594-edge nvme0q18
146: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 27 0 IR-PCI-MSI 1048595-edge nvme0q19
147: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 31 IR-PCI-MSI 1048596-edge nvme0q20
148: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2348672 0 IR-PCI-MSI 1572864-edge enp3s0
149: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 49 0 0 0 0 0 IR-PCI-MSI 360448-edge mei_me
150: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1057963 0 0 0 0 IR-PCI-MSI 524288-edge nvidia
151: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4279 0 0 0 IR-PCI-MSI 514048-edge snd_hda_intel:card0
152: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 107086 0 0 IR-PCI-MSI 2097152-edge ath10k_pci
NMI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Non-maskable interrupts
LOC: 2594769 2532024 2549340 2511248 2538056 2500348 2465245 2431456 2454770 2532615 2498041 2637259 5640400 2580416 2547381 2445718 2481774 2534574 2589198 2483177 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Performance monitoring interrupts
IWI: 3462 2558 3279 4342 3247 3314 3026 3272 3039 4131 3069 3482 3764 3816 2978 4861 3088 3651 3610 2181 IRQ work interrupts
RTR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 APIC ICR read retries
RES: 137606 502854 148052 181811 152554 131644 123475 116161 114781 321738 138829 23071 517670 238608 192759 152165 178633 142435 154122 128619 Rescheduling interrupts
CAL: 843358 695378 562159 588678 553175 552494 558122 567814 566296 562542 571100 726112 599164 565073 550646 522453 518123 548976 538074 535131 Function call interrupts
TLB: 376271 381982 336299 396027 396020 382190 385977 400184 394174 366824 398127 387923 373659 390205 381563 337505 351927 381087 350502 371107 TLB shootdowns
TRM: 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 1620 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 21 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event
|
|
|
|
|
01-20-2023, 12:31 PM
|
#24
|
|
LQ Newbie
Registered: Jan 2023
Posts: 15
Original Poster
Rep:
|
Here is uptime at time of posting
uptime
12:31:28 up 1:48, 1 user, load average: 5.15, 5.54, 6.54
|
|
|
|
|
01-20-2023, 12:33 PM
|
#25
|
|
LQ Newbie
Registered: Jan 2023
Posts: 15
Original Poster
Rep:
|
Quote:
Originally Posted by rokytnji
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.
My SSD was also working very well on windows. |
|
|
|
|
01-20-2023, 02:26 PM
|
#26
|
|
LQ Veteran
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,296
|
Quote:
Originally Posted by christopherlinux
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 |
|
|
|
|
01-20-2023, 02:45 PM
|
#27
|
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,523
|
Quote:
Originally Posted by christopherlinux
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. |
|
|
|
|
01-20-2023, 02:48 PM
|
#28
|
|
Member
Registered: Jan 2023
Posts: 202
Rep:
|
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?
https://www.chippiko.com/lubuntu-vs-antix-ram
Every app needs more resource with Lubuntu - so open those listed with Lubuntu and watch the resources get sucked up. |
|
|
|
|
01-20-2023, 03:13 PM
|
#29
|
|
Member
Registered: Sep 2015
Location: Australia
Distribution: Slackware, Devuan, Freebsd
Posts: 720
Rep: 
|
You are running kernel 6.0.12.
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...
I think you should try testing custom compiling a newer kernel that will be built specifically for just your laptop hardware and booting into it.
https://www.kernel.org/
https://tutorialforlinux.com/2021/01...-pop_os-guide/
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
The rest in the kernel that aren't specific to your device,leave as default.
I'd recommend considering installing the latest nvidia driver for your card directly from nvidiahttps://www.nvidia.com/Download/index.aspx?lang=en-us
Looking at the ath10K wnic online, appears the work is ongoing and the latest commit is quite recent
https://git.kernel.org/pub/scm/linux...ath10k/Kconfig
Can you check if you have the latest firmware blob installed and it's enabled in the kernel config file before you recompile it. See below
http://linuxwireless.sipsolutions.ne...#ath10k_driver
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
|
|
|
1 members found this post helpful.
|
|
01-20-2023, 11:45 PM
|
#30
|
|
LQ Newbie
Registered: Jan 2023
Posts: 15
Original Poster
Rep:
|
Quote:
Originally Posted by yvesjv
You are running kernel 6.0.12.
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 |
Tested this out by booting to Manjaro 22 (kernel 6.17), booted instantly and applications opened FAST. Going to try a full install to confirm! |
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 06:24 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
