Ubuntu 18.04.2 LTS boots slow

I have a ThinkPad, t480s, and it is supported by Ubuntu pretty well. Upgrading from Ubuntu 16 to Ubuntu 18.04 brought me mainly advantages, but also 1 big disanvatage: boot time increased. I use password to login and while I boot my pc, it takes like ~5 to load on this ubuntu purple screen. This was not the case with Ubuntu 16. Same thing happens also on some HP laptops.

Here is the output from systemd-analyze blame :

          6.289s NetworkManager-wait-online.service           5.309s fwupd.service           3.621s snapd.service           3.315s apt-daily-upgrade.service           2.241s plymouth-quit-wait.service           1.347s plymouth-start.service           1.059s systemd-backlight@backlight:intel_backlight.service            842ms dev-nvme0n1p2.device            619ms apparmor.service            572ms plymouth-read-write.service            410ms docker.service            390ms snap-gnome\x2dcalculator-260.mount            380ms snap-core18-731.mount            375ms snap-gnome\x2dsystem\x2dmonitor-57.mount            341ms snap-gnome\x2dcalculator-352.mount            318ms snap-gnome\x2dlogs-37.mount            305ms systemd-resolved.service            284ms systemd-timesyncd.service            274ms snap-gnome\x2d3\x2d26\x2d1604-82.mount            271ms dev-loop13.device            263ms snap-gnome\x2dcalculator-180.mount            259ms dev-loop10.device            255ms dev-loop11.device            247ms dev-loop15.device            245ms dev-loop8.device            242ms dev-loop12.device            233ms dev-loop9.device            233ms snap-gnome\x2dsystem\x2dmonitor-51.mount            232ms dev-loop16.device            217ms dev-loop14.device            217ms dev-loop17.device            211ms snap-gimp-113.mount            209ms dev-loop18.device            190ms NetworkManager.service            186ms snap-core-6531.mount            184ms dev-loop1.device            181ms dev-loop19.device            178ms dev-loop3.device 

iphone imessage hijacked by “Puss N. Boots”

When I tap imessage icon animated GIF comes up with 2 serial pages with a lot of animation “! Share your GIFs”, then moves on to page “2 Copy & paste stickers” with a lot of complex animation. Of course I’ve done neither. The whole screen is taken up by the animation. There is nowhere to navigate anywhere else in imessage–I can only get out by going to home screen. Anyone else have this?…know how to get rid of it? Thanks. :-)Shawn

New PC fails EFI-boot on USB installation xUbuntu-18.04; BIOS boots USB

New Acer-PC Aspire-T Intel i5 core processor 8400 internal memory 8 Gb DDR4 250 Gb Solid-State-Disk 2 Tb sata-Disk

USB-installation medium several times used: always successful on BIOS-boot. If the PC boots in BIOS-mode, then the USB-installation can be started, but then the GUID-partitions show up as undefined. This is normal. If the PC boots in UEFI-mode, then the only boot-choice is to start the Micr$ oft Windblows-installation, this is not what we want to happen.

2 questions:

.q1. How do we get this PC to boot in UEFI-mode and start xUbuntu-installation using the USB-stick ? … without having to do the W-installation first.

.q2. Any suggestions for a clever Partition-set: must we use the Solid-State disk as * boot, * root, * swap ?!?

I assume your answer will look like:

  • Solid-State p1: Guid-Efi-Partition (1 Gb fat-32; necessary for UEFI-boot)
  • Solid-State p2: root (240 Gb ext4)
  • Solid-State p3: swap-Partition (14 Gb swap)
  • 2 Tb p1 : home-partition (ext4)

On the web several completely suggestions are found. None of them worked for UEFI-booting the USB-installation.

We appreciate your time and suggestions!

Wim

Ubuntu only boots when iommu=soft

Ok, so I’ve been battling with this problem for few weeks now.

I’m currently rocking:

  • fx-8320E

  • GA-970A-DS3P

  • RX-480 4GB

and I’ve been having a problem with the IOMMU boot.

So, if I try to boot with anything other than the soft mode on iommu in grub, I get stuck on booting, no matter what the amd_iommu setting is set to.

Also, I’ve checked the BIOS and I have enabled SVM and IOMMU for my cpu, and both CPU and the MB support AMD-Vi

If I run dmesg | grep iommu -i I get this output:

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=087205d6-21bf-4c57-87d6-3621a0f04b6c ro iommu=soft [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=087205d6-21bf-4c57-87d6-3621a0f04b6c ro iommu=soft [    5.003506] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de> [    5.003507] AMD IOMMUv2 functionality not available on this system 

I’m assuming that it’s saying that functionality is not available because I’m not running the motherboard iommu, but the software one.

So, I’d like to know if there’s anything else I can try or check to fix this “problem” and maybe get a Windows VM running with GPU passthrough.

Thanks in advance.

EDIT

When running virt-host-validate I receive this output:

  QEMU: Checking for hardware virtualization                                 : PASS   QEMU: Checking if device /dev/kvm exists                                   : PASS   QEMU: Checking if device /dev/kvm is accessible                            : PASS   QEMU: Checking if device /dev/vhost-net exists                             : PASS   QEMU: Checking if device /dev/net/tun exists                               : PASS   QEMU: Checking for cgroup 'memory' controller support                      : PASS   QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS   QEMU: Checking for cgroup 'cpu' controller support                         : PASS   QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS   QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS   QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS   QEMU: Checking for cgroup 'cpuset' controller support                      : PASS   QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS   QEMU: Checking for cgroup 'devices' controller support                     : PASS   QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS   QEMU: Checking for cgroup 'blkio' controller support                       : PASS   QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS   QEMU: Checking for device assignment IOMMU support                         : PASS   QEMU: Checking if IOMMU is enabled by kernel                               : WARN (IOMMU appears to be disabled in kernel. Add iommu=pt iommu=1 to kernel cmdline arguments)    LXC: Checking for Linux >= 2.6.26                                         : PASS    LXC: Checking for namespace ipc                                           : PASS    LXC: Checking for namespace mnt                                           : PASS    LXC: Checking for namespace pid                                           : PASS    LXC: Checking for namespace uts                                           : PASS    LXC: Checking for namespace net                                           : PASS    LXC: Checking for namespace user                                          : PASS    LXC: Checking for cgroup 'memory' controller support                      : PASS    LXC: Checking for cgroup 'memory' controller mount-point                  : PASS    LXC: Checking for cgroup 'cpu' controller support                         : PASS    LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS    LXC: Checking for cgroup 'cpuacct' controller support                     : PASS    LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS    LXC: Checking for cgroup 'cpuset' controller support                      : PASS    LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS    LXC: Checking for cgroup 'devices' controller support                     : PASS    LXC: Checking for cgroup 'devices' controller mount-point                 : PASS    LXC: Checking for cgroup 'blkio' controller support                       : PASS    LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS    LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS 

and the problem is that the iommu=pt iommu=1 don’t work for me, as they don’t seem to boot.

I wiped Windows and installed ubuntu but it boots to black screen and recovery mode does not boot

I installed Ubuntu and wiped my windows OS in the process. I cannot boot Ubuntu, run recovery mode or anything.

nomodeset didn’t work or anything.

I can open the grub page and run memtest, but that is it.

Please can somebody help. I’ve seen similar problems on here but nothing like my own.

The laptop is an Acer One 11.

Thanks in advance.

Using Spring Boot’s @ConfigurationProperties without violating Law of Demeter

My apps commonly have one or more prop holders. These holders contain config data used in the app such as:

@Component @ConfigurationProperties(prefix="app.orders") @Data //lombok public class OrderProps {       private int maxItems;      // other order props } 

Various components that use one or more of these props get injected with the prop holder:

@Service public class OrderService {      private int maxSize;      public OrderService(OrderProps props) {          maxSize = props.getMaxSize();     }   } 

In this example, OrderService is only dependent on maxSize. Other classes may have also a varying number of properties needed from OrderProps.

Doesn’t injecting @ConfigurationProperties classes violate the Law of Demeter. Specifically, doesn’t it mask the real dependency (in this case an int) as described here?

Is there way to design without violating? Littering code with @Value("$ {order.maxItems}") or perhaps less problematic @Value("#{orderProps.maxItems}") seems to have its own set of problems especially when refactoring / maintenance.

Initial boot after installation works, all subsequent boots freeze on Dell Inspiron Mini

So I am having a weird issue, I actually noticed it with Linux Mint, but I decided to try Ubuntu to see if the problem originated there, and it does seem to. I have a little Dell Inspiron Mini 1012. Ubuntu 15.04 and older will install and works great. The trouble starts when I try to install 15.10 or 16.04. The installer boots fine, and I am able to install. I remove the USB drive I used and reboot. The system will fully reboot into the desktop, I am able to use the system if I choose. But when I shut it down and try to start up again, the system will freeze every time. I hit escape so I can view the list of what the system is doing, and it doesn’t seem to freeze on any particular thing each time, but it does freeze solid every time. No blinking cursor, no hard drive activity, nothing. After the first initial boot after installation, the system will never boot again. I am completely at a loss as for what to do, and would love to get the newer versions working on this system. If anyone needs more info, just let me know. Thank you.