robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

[SOLVED] Slow start to Budgie desktop with new Ryzen UEFI MBD and Samsung DVD

Sat Jan 20, 2018 11:23 pm

Hi, I've just upgraded my Athlon XII 640 rig to a Ryzen 3 1300X. My graphics cards is a Nvidia GTX1050.

All was fine with Solus and the Athlon which was quite old and legacy BIOS.

This new board is my first foray into UEFI: I have disabled legacy (it's an ASUS board - they call it CSM) and I removed the PK key to disable secure boot and so Solus installation went fine and it correctly created a GPT partition and installed without error.

But..... the blinkin cursor in the top left just before the mouse pointer appears (signalling Budgie is about to display), stays blinking for about 1 minute. I have installed the Nvidia drivers from doflicky and this made no difference.

I am using the same 2 SSDs (the 1st has been re-written for Solus completely for this installation, and the 2nd is a GPT partition for a Steam library and so hasn't been changed).

I ran systemd-analyze blame and udisks2 takes 22.7s - what is happening?

Code: Select all

robert@solus ~ $ systemd-analyze blame
         22.684s udisks2.service
           747ms apparmor.service
           348ms dev-sda3.device
           344ms lightdm.service
           273ms dev-loop0.device
           252ms dev-loop1.device
           210ms systemd-udevd.service
           149ms initrd-switch-root.service
           146ms NetworkManager.service
            95ms snap-chromium-128.mount
            73ms systemd-resolved.service
            72ms systemd-journal-flush.service
            71ms snap-core-3748.mount
            69ms auditd.service
            54ms upower.service
            48ms initrd-parse-etc.service
            47ms systemd-logind.service
            46ms systemd-tmpfiles-setup-dev.service
            43ms on-demand-cpupower.service
            43ms nvidia-persistenced.service
            41ms systemd-timesyncd.service
            40ms systemd-udev-trigger.service
            33ms colord.service
robert@solus ~ $ 
Also, once the desktop appears, my icons for trashcan etc take more than 10 seconds.

Please help...
Last edited by robgriff444 on Tue Feb 20, 2018 5:12 pm, edited 2 times in total.

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 12:47 am

And by the way, I installed this time from a downloaded iso I got today, the previous setup was installed from the 1st solus3 iso and updated as and when without error.

User avatar
kyrios
Posts: 2284
Joined: Thu Sep 22, 2016 4:20 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 11:38 am

robgriff444 wrote:
Sun Jan 21, 2018 12:47 am
And by the way, I installed this time from a downloaded iso I got today, the previous setup was installed from the 1st solus3 iso and updated as and when without error.
Have you had a look at the help center already ?

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 12:51 pm

@kyrios I have already read it but I forgot about it, partly because this is a fresh install and the error was there from the beginning so I didn't think it would apply.

However, I've looked again and there is a discrepancy in that my root UUID in the kernel parameters isn't the same as in my fstab and isn't in /dev/disks/by-uuid. The UUID which begins with 2c33d243 doesn't appear elsewhere but the UUID for / in fstab (beginning 3fb46666) does appear in the by-uuid folder.

Code: Select all

robert@solus ~ $ cat /proc/cmdline
initrd=\EFI\com.solus-project\initrd-com.solus-project.current.4.14.14-47 root=PARTUUID=2c33d243-4873-4dcd-81ff-41706769cec5 quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 resume=UUID=a933a6d2-3c33-4b8d-8990-b203392716f8

Code: Select all

# /etc/fstab: static file system information.
#
# <fs>      <mountpoint> <type> <opts>      <dump/pass>

# /dev/ROOT   /            ext3    noatime        0 1
# /dev/SWAP   none         swap    sw             0 0
# /dev/fd0    /mnt/floppy  auto    noauto         0 0
none        /proc        proc    nosuid,noexec  0 0
none        /dev/shm     tmpfs   defaults       0 0
UUID=a933a6d2-3c33-4b8d-8990-b203392716f8	swap	swap	sw	0	0
# /dev/sda3 at time of installation
UUID=3fb46666-d5da-4165-a740-637b5918b036	/	ext4	rw,relatime,errors=remount-ro	0	1
So how do I change the kernel command line on a UEFI system? (I looked at help but this only showed how to append), and why has this happened? I simply booted from a USB stick and installed to 1 disk by erasing it in the install.

Actually, before this, I installed to my PC while it was still in legacy mode (which was how I knew it was in legacy mode doh!) so is it possible the UUID came from then?

User avatar
kyrios
Posts: 2284
Joined: Thu Sep 22, 2016 4:20 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 1:22 pm

robgriff444 wrote:
Sun Jan 21, 2018 12:51 pm
@kyrios I have already read it but I forgot about it, partly because this is a fresh install and the error was there from the beginning so I didn't think it would apply.

However, I've looked again and there is a discrepancy in that my root UUID in the kernel parameters isn't the same as in my fstab and isn't in /dev/disks/by-uuid. The UUID which begins with 2c33d243 doesn't appear elsewhere but the UUID for / in fstab (beginning 3fb46666) does appear in the by-uuid folder.

So how do I change the kernel command line on a UEFI system? (I looked at help but this only showed how to append), and why has this happened? I simply booted from a USB stick and installed to 1 disk by erasing it in the install.

Actually, before this, I installed to my PC while it was still in legacy mode (which was how I knew it was in legacy mode doh!) so is it possible the UUID came from then?
I think you'll find the answer in this post
Sorry for not elaborating more... Sunday laziness

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 1:41 pm

That didn't fix it - I only have 1 resume UUID anyway and it was correct but I removed the 10* file to see if it made a difference but no.

Is it a red-herring that the root UUID in kernel params doesn't exist elsewhere because the post you pointed me to showed his output to be like mine in this way i.e. his root UUID wasn't in his fstab. So maybe i'm fixated on something that isn't to blame?

And...

Code: Select all

Startup finished in 9.827s (firmware) + 128ms (loader) + 638ms (kernel) + 1min 8.303s (initrd) + 1.615s (userspace) = 1min 20.513s
Mine starts up in less than 90s so it can't be the missing UUID??

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 1:56 pm

This is something I just found at https://unix.stackexchange.com/question ... ith-a-uuid which confirms what I just posted:
There are two types: UUID, which is stored in the filesystem and is not available to the kernel at boot-time, and PARTUUID, which is stored in the partition table and IS available at boot time.
So it's not an incorrect root UUID, and it's not an incorrect resume UUID, I only have Solus on this machine so it's not a shared swap, it's the same with nouveau and nvidia, and systemd-analyze blame always shows udisks2 at the top with ~28s.

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 2:14 pm

This is getting stranger, I plugged in the USB stick I installed from and this is what I get:

Code: Select all

robert@solus ~ $ systemd-analyze blame
          1.335s udisks2.service
           500ms lightdm.service
           456ms dev-sda3.device
           405ms apparmor.service
           398ms NetworkManager.service
           392ms dev-loop0.device
           176ms systemd-hostnamed.service
           169ms on-demand-cpupower.service
           166ms systemd-journal-flush.service
           146ms initrd-switch-root.service
           121ms upower.service
            62ms auditd.service
            58ms systemd-udevd.service
            55ms systemd-resolved.service
            50ms initrd-parse-etc.service
            46ms systemd-udev-trigger.service
            44ms systemd-localed.service
            42ms systemd-timesyncd.service
            40ms systemd-tmpfiles-setup-dev.service
            35ms systemd-tmpfiles-setup.service
            31ms org.cups.cupsd.service
            30ms user@1000.service
            22ms colord.service
lines 1-23
So it's now NOT udisks2 but it wasn't any faster:

Code: Select all

robert@solus ~ $ systemd-analyze
Startup finished in 14.646s (firmware) + 129ms (loader) + 636ms (kernel) + 1min 8.295s (initrd) + 1.519s (userspace) = 1min 25.227s

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 2:35 pm

I have just updated my BIOS (I had to reset legacy mode to disabled again), the USB stick is still in, and during this boot udisks2 took 28s so I have no idea why I saw a reduction, especially as the overall time is consistent.

robgriff444
Posts: 59
Joined: Sat Sep 09, 2017 12:49 pm

Re: Slow start to Budgie desktop with new Ryzen UEFI MBD

Sun Jan 21, 2018 3:44 pm

This is the dmesg output from ~70s to the end - it jumps to 2114s in a few lines:

Code: Select all

[   70.401721] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready
[   70.416421] r8169 0000:05:00.0 enp5s0: link down
[   70.416479] r8169 0000:05:00.0 enp5s0: link down
[   70.416517] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready
[   70.650774] nvidia-modeset: Allocated GPU:0 (GPU-87dd23e0-c030-c82c-fcde-e89627ac5008) @ PCI:0000:07:00.0
[   71.202606] fuse init (API version 7.26)
[   71.762409] rfkill: input handler disabled
[   72.035430] r8169 0000:05:00.0 enp5s0: link up
[   72.035439] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
[   99.818133] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   99.818150] ata5.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 19 pio 16392 in
                        Get event status notification 4a 01 00 00 10 00 00 00 08 00res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   99.818152] ata5.00: status: { DRDY }
[   99.818157] ata5: hard resetting link
[  100.279142] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  100.881278] ata5.00: configured for UDMA/100
[  101.482183] ata5: EH complete
[  318.774061] ISOFS: Unable to identify CD-ROM format.
[ 2114.185214] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 2287.394768] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 2287.394784] ata5.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 18 pio 16392 in
                        Get event status notification 4a 01 00 00 10 00 00 00 08 00res 40/00:02:00:48:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 2287.394786] ata5.00: status: { DRDY }
[ 2287.394791] ata5: hard resetting link
[ 2287.855332] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2288.457598] ata5.00: configured for UDMA/100
[ 2289.058203] ata5: EH complete
[ 2642.136325] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 2642.136341] ata5.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 18 pio 16392 in
                        Get event status notification 4a 01 00 00 10 00 00 00 08 00res 40/00:02:00:48:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 2642.136343] ata5.00: status: { DRDY }
[ 2642.136348] ata5: hard resetting link
[ 2642.597297] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2643.200152] ata5.00: configured for UDMA/100
[ 2643.800851] ata5: EH complete
[ 2675.416500] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 2675.416516] ata5.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 15 pio 16392 in
                        Get event status notification 4a 01 00 00 10 00 00 00 08 00res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 2675.416518] ata5.00: status: { DRDY }
[ 2675.416523] ata5: hard resetting link
[ 2675.877473] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2676.480373] ata5.00: configured for UDMA/100
[ 2677.081000] ata5: EH complete
robert@solus ~ $ 

Return to “Hardware”