JJ Abrams's questions

When I have my HP (Elitebook 830 G6) turned off and plugged in via the USB-C port, everything is fine: It charges.

As soon as I turn the laptop on and the process passes GRUB it immediateley stops charging.

I tried plugging int the laptop while in the OS, it first charges, but randomly stops charging.

The system:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:    20.04
Codename:   focal

$ uname -a
Linux kernel 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I tried booting off a USB drive (not plugged in the USB-C but the USB-A ;) with Xubuntu 20.04 -> same behaviour. Then I tried Xubuntu 21.10 -> same behaviour.

This all indicates a hardware problem. But I don't understand why the laptop would charge perfectly fine, when the computer is turned off.

Thanks!

* EDIT * I booted 21.10 not 20.10! Fixed above :)

I bought a new HP notebook (elitebook) with an extremely awful keyboard functionality. For example, I don't have an insert key, but I have a phone-dial and phone-hangup key (right upper corner):

The thing is, I am extremely used to the insert key. Therefore I was looking for a way to remap the second key from the right (hangup-key) to the insert key. However, none of the proposed solutions work for me (1, 2, 3).

E.g., when I run xev | grep keycode and press the desired key, I get the following output:

    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    state 0xc, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,

This seems like that key is mapped to the left ALT key? Trying CTRL+ALT+T confirms that suspicion, as it opens the terminal.

Does anybody have any idea how to map that key to the INSERT key I don't have?

• EDIT *

As requested, the LEFT CTRL and LEFT ALT KEY pressed:

    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,

Thanks!

I am running Xubuntu 20.04 and have a problem with wifi reconnects: Sometimes my HP notebook loses connection to the wifi router (3 meters distance, without obstacles) and then cannot reconnect. This is the corresponding excerpt from syslog:

Jun 24 21:50:26 hostname wpa_supplicant[1026]: wlp58s0: SME: Trying to authenticate with 34:xx:xx:xx:xx:xx (SSID='homewifi_5G-2' freq=5500 MHz)
Jun 24 21:50:26 hostname kernel: [ 6469.357476] wlp58s0: send auth to 34:xx:xx:xx:xx:xx (try 1/3)
Jun 24 21:50:26 hostname NetworkManager[7166]: <info>  [1593028226.5142] device (wlp58s0): supplicant interface state: scanning -> authenticating
Jun 24 21:50:26 hostname NetworkManager[7166]: <info>  [1593028226.5142] device (p2p-dev-wlp58s0): supplicant management interface state: scanning -> authenticating
Jun 24 21:50:27 hostname kernel: [ 6469.972019] iwlwifi 0000:3a:00.0: No beacon heard and the time event is over already...
Jun 24 21:50:27 hostname kernel: [ 6469.972083] wlp58s0: Connection to AP 34:xx:xx:xx:xx:xx lost
Jun 24 21:50:27 hostname kernel: [ 6470.021469] wlp58s0: send auth to 34:xx:xx:xx:xx:xx (try 2/3)
Jun 24 21:50:27 hostname kernel: [ 6470.635771] iwlwifi 0000:3a:00.0: No beacon heard and the time event is over already...
Jun 24 21:50:27 hostname kernel: [ 6470.635821] wlp58s0: Connection to AP 34:xx:xx:xx:xx:xx lost
Jun 24 21:50:28 hostname kernel: [ 6471.013103] wlp58s0: send auth to 34:xx:xx:xx:xx:xx (try 3/3)
Jun 24 21:50:28 hostname kernel: [ 6471.627473] iwlwifi 0000:3a:00.0: No beacon heard and the time event is over already...
Jun 24 21:50:28 hostname kernel: [ 6471.627570] wlp58s0: Connection to AP 34:xx:xx:xx:xx:xx lost
Jun 24 21:50:29 hostname kernel: [ 6472.004632] wlp58s0: authentication with 34:xx:xx:xx:xx:xx timed out
Jun 24 21:50:29 hostname wpa_supplicant[1026]: wlp58s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="homewifi_5G-2" auth_failures=1 duration=10 reason=CONN_FAILED
Jun 24 21:50:29 hostname NetworkManager[7166]: <info>  [1593028229.1939] device (wlp58s0): supplicant interface state: authenticating -> disconnected
Jun 24 21:50:29 hostname NetworkManager[7166]: <info>  [1593028229.1940] device (p2p-dev-wlp58s0): supplicant management interface state: authenticating -> disconnected
Jun 24 21:50:30 hostname systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jun 24 21:50:39 hostname NetworkManager[7166]: <info>  [1593028239.1966] device (wlp58s0): supplicant interface state: disconnected -> scanning
Jun 24 21:50:39 hostname NetworkManager[7166]: <info>  [1593028239.1967] device (p2p-dev-wlp58s0): supplicant management interface state: disconnected -> scanning
Jun 24 21:50:40 hostname wpa_supplicant[1026]: wlp58s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="homewifi_5G-2"
Jun 24 21:50:40 hostname wpa_supplicant[1026]: wlp58s0: SME: Trying to authenticate with 34:xx:xx:xx:xx:xx (SSID='homewifi_5G-2' freq=5500 MHz)
Jun 24 21:50:40 hostname kernel: [ 6482.882772] wlp58s0: authenticate with 34:xx:xx:xx:xx:xx
Jun 24 21:50:40 hostname kernel: [ 6482.888639] wlp58s0: send auth to 34:xx:xx:xx:xx:xx (try 1/3)
Jun 24 21:50:40 hostname NetworkManager[7166]: <info>  [1593028240.0444] device (wlp58s0): supplicant interface state: scanning -> authenticating
Jun 24 21:50:40 hostname NetworkManager[7166]: <info>  [1593028240.0445] device (p2p-dev-wlp58s0): supplicant management interface state: scanning -> authenticating
Jun 24 21:50:40 hostname kernel: [ 6483.502938] iwlwifi 0000:3a:00.0: No beacon heard and the time event is over already...
Jun 24 21:50:40 hostname kernel: [ 6483.503033] wlp58s0: Connection to AP 34:xx:xx:xx:xx:xx lost
Jun 24 21:50:41 hostname kernel: [ 6484.037725] wlp58s0: send auth to 34:xx:xx:xx:xx:xx (try 2/3)
Jun 24 21:50:41 hostname kernel: [ 6484.652032] iwlwifi 0000:3a:00.0: No beacon heard and the time event is over already...
Jun 24 21:50:41 hostname kernel: [ 6484.652110] wlp58s0: Connection to AP 34:xx:xx:xx:xx:xx lost
Jun 24 21:50:42 hostname kernel: [ 6484.999095] wlp58s0: send auth to 34:xx:xx:xx:xx:xx (try 3/3)
Jun 24 21:50:42 hostname kernel: [ 6485.613299] iwlwifi 0000:3a:00.0: No beacon heard and the time event is over already...
Jun 24 21:50:42 hostname kernel: [ 6485.613377] wlp58s0: Connection to AP 34:xx:xx:xx:xx:xx lost
Jun 24 21:50:43 hostname kernel: [ 6485.989445] wlp58s0: authentication with 34:xx:xx:xx:xx:xx timed out
Jun 24 21:50:43 hostname wpa_supplicant[1026]: wlp58s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="homewifi_5G-2" auth_failures=2 duration=20 reason=CONN_FAILED
Jun 24 21:50:43 hostname NetworkManager[7166]: <info>  [1593028243.1721] device (wlp58s0): supplicant interface state: authenticating -> disconnected
Jun 24 21:50:43 hostname NetworkManager[7166]: <info>  [1593028243.1722] device (p2p-dev-wlp58s0): supplicant management interface state: authenticating -> disconnected
Jun 24 21:50:50 hostname systemd[1]: systemd-hostnamed.service: Succeeded.
Jun 24 21:50:51 hostname NetworkManager[7166]: <warn>  [1593028251.0630] device (wlp58s0): Activation: (wifi) association took too long, failing activation
Jun 24 21:50:51 hostname NetworkManager[7166]: <info>  [1593028251.0631] device (wlp58s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 24 21:50:51 hostname NetworkManager[7166]: <info>  [1593028251.0648] manager: NetworkManager state is now DISCONNECTED
Jun 24 21:50:51 hostname NetworkManager[7166]: <warn>  [1593028251.0680] device (wlp58s0): Activation: failed for connection 'homewifi_5G-2'
Jun 24 21:50:51 hostname NetworkManager[7166]: <info>  [1593028251.0692] device (wlp58s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

My mobile phone connects without problems, but my Linux notebook doesn't. After a reboot, everything is fine again, but a simple sudo service network-manager restart doesn't do the trick. Any clues?

Some wifi details:

$ sudo lshw -C network
  *-network                 
       description: Wireless interface
       product: Wi-Fi 6 AX200
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:3a:00.0
       logical name: wlp58s0
       version: 1a
       serial: 5c:xx:xx:xx:xx:xx
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-37-generic firmware=48.4fa0041f.0 ip=192.168.1.96 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:19 memory:c8100000-c8103fff

And my kernel information:

$ uname -a
Linux hostname 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

EDIT
As requested:

$ iwlist wlp58s0 freq
wlp58s0   32 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz
          Channel 36 : 5.18 GHz
          Channel 40 : 5.2 GHz
          Channel 44 : 5.22 GHz
          Channel 48 : 5.24 GHz
          Channel 52 : 5.26 GHz
          Channel 56 : 5.28 GHz
          Channel 60 : 5.3 GHz
          Channel 64 : 5.32 GHz
          Channel 100 : 5.5 GHz
          Channel 104 : 5.52 GHz
          Channel 108 : 5.54 GHz
          Channel 112 : 5.56 GHz
          Channel 116 : 5.58 GHz
          Channel 120 : 5.6 GHz
          Channel 124 : 5.62 GHz
          Channel 128 : 5.64 GHz
          Channel 132 : 5.66 GHz
          Channel 136 : 5.68 GHz
          Channel 140 : 5.7 GHz
          Current Frequency:5.26 GHz (Channel 52)

I have installed Xubuntu 20.04 encrypted on an SSD and get the following error on boot time:

/tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory

The boot time is pretty slow, so I think that could be one of the reasons.

Is the reason for the error the double slash after hooks.d?

I just installed the current Xubuntu 20.04 and tried to restore my backup from my backintime backup via sshfs. Unfortunately, this failed. I checked the full log in /home/user/.local/share/backintime/restore_3.log

It has about 450k lines, where the most important ones are:

receiving file list ... done
rsync: failed to set times on "/home": Operation not permitted (1)
home/
home/user/
home/user/.ICEauthority
[... 450k lines of restored files ...]
sent 7.47M bytes  received 464.32G bytes  47.33M bytes/sec
total size is 464.22G  speedup is 1.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1677) [generator=3.1.3]

Restore permissions:
chmod /home/user/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml 100644
chmod /home/user/.config/xfce4/xfconf/xfce-perchannel-xml/thunar.xml 100644

Restore permissions: Done

Some questions I have:

1. Is the only error that backintime couldn't set attributes on /home?
2. If yes to 1): Why would backintime set attributes on /home? I backupped /home/user/
3. If no: How do I find missing files and attributes? I searched for 'error' and 'fail' in the aforementioned log, without success.
4. received 464.32G vs. total size is 464.22G. Why?
5. Backintime didn't finish. It was just at 99% for some time when I lost patience and closed it. How do I know, if it was finished?

Thanks!

I have oh-my-zsh installed on my Xubuntu 19.10. Sometimes, as (X)ubuntu usually does, it freezes together with the whole X server. Therefore I wanted to switch to tty1. Once I provided my credentials, the tty is stuck.

I tried to reproduce the issue without having a frozen X server on tty7, so I logged into tty1 again and then back to tty7. Looking at the processes I see zsh using a whole core. If I kill the process, the login sequence in the tty1 is killed and I would need to login again.

Watching auth.log the user get logged in as well, so that's another reason why it could be ZSH:

Apr 23 21:52:29 laptop systemd[1]: Started Session 8 of user userr.
Apr 23 21:52:40 laptop systemd[1]: [email protected]: Succeeded.
Apr 23 21:52:40 laptop systemd[1]: session-8.scope: Succeeded.
Apr 23 21:52:40 laptop systemd[1]: [email protected]: Service has no hold-off time (RestartSec=0), scheduling restart.
Apr 23 21:52:40 laptop systemd[1]: [email protected]: Scheduled restart job, restart counter is at 3.
Apr 23 21:52:40 laptop systemd[1]: Stopped Getty on tty1.
Apr 23 21:52:40 laptop systemd[1]: Started Getty on tty1.

Please let me know if you need any more logs :)

I recently bought a new HP Laptop (HP 830 G6) and installed Xubuntu 19.10 with full disk encryption (LUKS). I noticed slow startup times, but not from decryption of the disk, but more until I actually land at the decryption prompt. Between the first image here:

And the second image here, there are 5-10 seconds of waiting time:

I post this in Askubuntu, since the startup times are way faster in Windows 10 (yes, I realized that Windows hibernates most of the time and there is no disk encryption when booting Windows. But imho, it's not the enc-/decryption that's taking so long but something else. Once the passphrase for the decryption is entered, I am in the OS in <5 seconds).

Some information about the system:
Disk: Samsung 970 EVO Plus SSD (1000GB, M.2 2280)
RAM: 32 GB

And some commands that show the startup time:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 19.10
Release:    19.10
Codename:   eoan

Startup times:

$ systemd-analyze

Startup finished in 9.208s (firmware) + 6.187s (loader) + 49.805s (kernel) + 3.223s (userspace) = 1min 8.425s 
graphical.target reached after 3.218s in userspace


$ systemd-analyze critical-chain

graphical.target @3.218s
└─lightdm.service @1.109s +481ms
  └─systemd-user-sessions.service @1.085s +7ms
    └─network.target @1.068s
      └─NetworkManager.service @1.002s +63ms
        └─dbus.service @949ms
          └─basic.target @932ms
            └─sockets.target @931ms
              └─snapd.socket @923ms +7ms
                └─sysinit.target @910ms
                  └─systemd-timesyncd.service @716ms +191ms
                    └─systemd-tmpfiles-setup.service @701ms +10ms
                      └─local-fs.target @693ms
                        └─boot-efi.mount @684ms +8ms
                          └─boot.mount @677ms +5ms
                            └─systemd-fsck@dev-disk-by\x2duuid-d58888fc\x288848\x2888e4\x288820\x2d5888889e42e8.service @644ms +31ms
                              └─dev-disk-by\x2duuid-d58888fc\x288848\x2888e4\x288820\x2d5888889e42e8.device @643ms

Grub Bootloader:

$ cat /etc/default/grub

GRUB_DEFAULT=0
GRUB_TIMEOUT=10
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

So far I disabled NetworkManager-wait, without a significant improvement:

$ sudo systemctl disable NetworkManager-wait-online.service

And I am kinda shocked by the 50 seconds of the kernel boot time...

Is there anything else I can try or do to speed up the startup times?

I am running an ASUS Chromebox2 with Ubuntu server 18.04. The Chromebox2 is connected to the wifi router right next to it over 2.4Ghz and my host is in the same network, also right next to the wifi router.

When typing into the shell over SSH I can see the characters appearing with a slight delay. When I plug the Chromebox into the ethernet port of the router, it's fast. However, in the longterm the Chromebox should be connected via wifi. How can I troubleshoot that problem?

My network related hardware details:

$ sudo lshw -class network
  *-network                 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0
       version: 0c
       serial: a8:1e:84:da:92:7a
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.1.135 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
       resources: irq:18 ioport:2000(size=256) memory:e1100000-e1100fff memory:e1000000-e1003fff
  *-network DISABLED
       description: Wireless interface
       product: Wireless 7260
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: bb
       serial: 34:f6:4b:73:41:6e
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-58-generic firmware=17.948900127.0 ip=192.168.1.180 latency=0 link=no multicast=yes wireless=IEEE 802.11
       resources: irq:52 memory:e1200000-e1201fff

I installed Ubuntu Server 18.04 on my ASUS Chromebox2. When issuing the command cat /sys/class/thermal/thermal_zone*/temp it returns the following:

43000
96500
42000

The numbers shown, indicate the temperature in millidegrees Celsius (m°C). So 96.5°C celsius is way to high. Since this is a newly bought Chromebox, is it possible that I misinterpreted the numbers or do I need to replace the hardware right after buying it?

EDIT: Running lm-senors after some time of letting the Chromebox run, reports the following:

$ sudo sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +45.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:        +45.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:        +44.0°C  (high = +105.0°C, crit = +105.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +45.0°C  (crit = +104.0°C)

pch_wildcat_point-virtual-0
Adapter: Virtual device
temp1:        +99.0°C

I have Ubuntu 18.04.1 installed on my Raspberry Pi and two USB devices attached: One small bluetooth adapter and one small Wifi adapter. I am connecting to the wifi network with wpa_supplicant like that:

sudo wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf

and then requesting an IP address from the router with dhclient:

sudo dhclient wlan0

However, now syslog and kern.log are growing and being polluted with CPU frequency errors:

Oct 12 21:52:45 ubuntu kernel: [83711.483509] cpufreq: __target_index: Failed to change cpu frequency: -22
Oct 12 21:52:46 ubuntu kernel: [83711.554489] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 600000 (-12)
Oct 12 21:52:46 ubuntu kernel: [83711.626640] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:175: Error occurred setting a new frequency (600000)

To "solve" the problem I just set the max frequency in the kernel:

echo 60000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq

Pro: The pollution in the logs stop. Con: The Rpi gets unusable. Number of Zombie processes grows, starting new processes takes way longer, ...

Can anybody help? Preferably with an explanatory answer :)