Ubuntu 26.04, new installation. Although I tell Libreoffice Writer to print multiples it doesn't.
Do I need to edit a config file? If so, how do I access them?
Is there any laptop that is near-perfectly compatible with Ubuntu?
Why is this like in Apple-computers ? In terminal I cannot use char for (.) and not for (;) when I want to type in new password ?
The char for (.) and for (;) is declared as wrong char in /bin/bash when I want to type in new password ?
These chars (.) and for (;) are not accepted inside a password ?
This was not the case in earlier versions of bash ?
I am facing a crash when I try to start my system with plasma-login-manager and multiple monitors. I'd like to report the crash, but
coredumpctl info PID
Shows me the core dump, but with several placeholders (n/a) like
Stack trace of thread 1521:
#0 0x00007d8d73898d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x00007d8d7389b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x00007d8d70b99edd n/a (libgallium-25.2.8-0ubuntu0.24.04.2.so + 0x599edd)
#3 0x00007d8d70b65fbb n/a (libgallium-25.2.8-0ubuntu0.24.04.2.so + 0x565fbb)
#4 0x00007d8d70b99e0c n/a (libgallium-25.2.8-0ubuntu0.24.04.2.so + 0x599e0c)
#5 0x00007d8d7389caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x00007d8d73929c6c __clone3 (libc.so.6 + 0x129c6c)
So I guess there are missing debug symbols. But apt search libgallium does not list any debug symbol package. I already added the ddebs repo as explained (here and there).
Where do I get the debug symbols from?
My distribution: KDE Neon / Ubuntu 24.04
I'm a complete Linux newbie and I'm trying to install the GMP library on Kubuntu 26.04 to run some computations, since everything on Linux runs faster (good job Microslop).
While running the configure file for GMP i get the following error:
leona@leona:~/Downloads/PARI/gmp-6.3.0$ sudo ./configure --enable-cxx
checking build system type... raptorlake-pc-linux-gnu
checking host system type... raptorlake-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=64
checking compiler gcc -O2 -pedantic -fomit-frame-pointer -m64 ... no, long long reliability test 1
checking whether cc is gcc... yes
checking compiler cc -O2 -pedantic -fomit-frame-pointer -m64 ... no, long long reliability test 1
checking ABI=x32
checking compiler gcc -O2 -pedantic -fomit-frame-pointer -mx32 ... no, program does not run
checking whether cc is gcc... yes
checking compiler cc -O2 -pedantic -fomit-frame-pointer -mx32 ... no, program does not run
checking ABI=32
checking compiler gcc -m32 -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
checking compiler gcc -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
checking compiler icc -no-gcc ... no
checking whether cc is gcc... yes
checking compiler cc -m32 -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
checking compiler cc -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
configure: error: could not find a working compiler, see config.log for details
I can confirm that gcc and g++ are correctly installed and working. Looking this error up online I also found out that adding the build option --build=x86_64-linux might solve the issue but I had no luck.
Lastly, having installed gcc from apt, I saw that it has been installed in /usr instead of the classical /usr/local, but adding --prefix=/usr does not help again.
I am lost, if somebody could help I'd really appreciate it. Thank you!
I have laptop Intel NUC P14E (i3-1155g4). After install any Linux distribution (arch, Ubuntu and etc.) I have scratch sound. Any one knows how to get right sound ?
I have a Sony VAIO VPCCW13FX with an Nvidia GeForce 310M GPU in it. I can get Lubuntu to install and run as long as I have nomodeset put next to quiet splash. I tried Ubuntu, but I can't get the installer to load even with nomodeset. I've tried everything to get drivers for the Nvidia 310M, but everything I find is either outdated or broken. The Additional Drivers tool doesn't detect the GPU, and I tried in the terminal too, but it still didn't work. I'm using Lubuntu 26.04.
I am trying to sign in ubuntu website but website not working and give error like Nagina(ubuntu)
Hardware: RTX 3090, LG 32LF510Z TV over HDMI Software: NVIDIA 595.84, kernel 7.0.0-28, Ubuntu 24.04, GDM/Xorg
Symptom Plymouth / Ubuntu boot logos display correctly on the TV. Once GDM starts, the TV shows “No signal.” The box is not headless — nvidia-smi works, another monitor works fine over the same GPU.
What the logs say Xorg init prints:
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-1 (--) NVIDIA(GPU-0): DFP-5: connected ... (WW) NVIDIA(0): No valid modes for "1360x768+0+0"; removing. (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode (II) NVIDIA(0): Setting mode "DFP-5:nvidia-auto-select"
So Xorg sees the connector, but cannot read EDID. Without EDID it rejects every forced candidate and falls back to nvidia-auto-select, which the TV then refuses.
What was tried (all failed)
| Fix | Result |
|---|---|
| video=HDMI-A-2:1360x768@60e boot param | No signal; kernel DRM rejects 1366x768 |
| video=HDMI-A-2:1360x768@60e nvidia_drm.fbdev=1 | Same |
| Xorg Option "ConnectedMonitor" "DFP-5" + AllowNonEdidModes + metamodes 1360x768, 1366x760, 1366x762, 1366x765 | All rejected: “No valid modes … removing.” |
| Stock config (no overrides) | Same EDID read failure, blank TV |
| Different HDMI port + different cable | Same |
| Different monitor | Works immediately |
Diagnosis The TV’s EDID reports 1360x768 as preferred timing, but the panel is natively 1366x768. Early boot (firmware/kernel fbcon) ignores EDID and pushes a mode anyway, so logos appear. Xorg’s NVIDIA DDX respects EDID, cannot read it cleanly on this driver/kernel combo, and ends up with a timing the TV won’t lock onto.
Open question / workaround Has anyone gotten this TV (or any EDID-lying panel with preferred != native) working under NVIDIA 595 + kernel 7.0 without a custom EDID blob? The untested path is capturing the EDID, patching the preferred timing to 1366x768, and loading it via Xorg CustomEDID.
TL;DR — Box is healthy. This is an NVIDIA + LG EDID handshake bug. Boot path works; Xorg path does not.
Hardware
Carrier
Problem
The carrier provides two APNs:
These APNs allocate different public IP pools, so it is easy to determine which APN is actually being used.
Windows:
When I select internet2, I receive an IP address from the internet2 pool.
Linux:
My NetworkManager profile is configured with:
APN = internet2
ModemManager reports the same:
mmcli -b 0
Properties: apn: internet2
and
mmcli -m 0
3GPP EPS: initial bearer apn: internet2
The modem also reports:
AT+CGDCONT?
CGDCONT: 0 ... "internet" CGDCONT: 1 ... "internet2"
The active bearer reports:
connected: yes apn: internet2
Everything appears to be configured for internet2.
However, the public IP address always belongs to the internet APN pool, never the internet2 pool.
Things I have already tried:
Confirmed that ModemManager still reports internet2.
Nothing changes the assigned public IP.
Question
Has anyone seen this behaviour?
Could the iosm driver (or the Intel ModemManager plugin) still activate the default PDP context (internet) while ModemManager reports the configured APN (internet2)?
Or is there another place where the actual attach APN is selected?
During 26.04 instal, got message, No internet e computer but I had the Net on the Mac I was converting. Now can’t connect online. What can I do?
I installed the latest version of Ubuntu, but it isn't detecting any Wi-Fi networks. I used to use Windows, and honestly, I have no idea how to get it to detect the networks.
I am using btrfs and have updated my version a few times. In a quest to figure out why df -h says I'm using almost all my disk space when according to du I should have a few hundred GB left, I started looking at my btrfs snapshots/subvolumes. I have not touched anything to do with btrfs, so all settings should be completely default. The full output of sudo btrfs subvolume list / is
ID 256 gen 1349500 top level 5 path @
ID 257 gen 1349500 top level 5 path @home
ID 259 gen 1349466 top level 256 path @swap
ID 260 gen 44402 top level 5 path @apt-snapshot-release-upgrade-lunar-2023-04-10_17:54:12
ID 261 gen 44404 top level 5 path @apt-snapshot-release-upgrade-lunar-2023-04-10_17:54:13
ID 262 gen 44407 top level 5 path @apt-snapshot-release-upgrade-lunar-2023-04-10_17:54:53
ID 263 gen 297583 top level 5 path @apt-snapshot-release-upgrade-mantic-2024-01-05_20:15:08
ID 264 gen 297584 top level 5 path @apt-snapshot-release-upgrade-mantic-2024-01-05_20:15:09
ID 265 gen 297586 top level 5 path @apt-snapshot-release-upgrade-mantic-2024-01-05_20:15:32
ID 266 gen 330309 top level 5 path @apt-snapshot-release-upgrade-noble-2024-02-03_22:47:22
ID 267 gen 330310 top level 5 path @apt-snapshot-release-upgrade-noble-2024-02-03_22:47:24
ID 268 gen 330312 top level 5 path @apt-snapshot-release-upgrade-noble-2024-02-03_22:47:46
ID 269 gen 712315 top level 5 path @apt-snapshot-release-upgrade-oracular-2025-03-26_11:29:55
ID 270 gen 712316 top level 5 path @apt-snapshot-release-upgrade-oracular-2025-03-26_11:29:57
ID 271 gen 712344 top level 5 path @apt-snapshot-release-upgrade-oracular-2025-03-26_11:42:38
ID 272 gen 789646 top level 5 path @apt-snapshot-release-upgrade-plucky-2025-05-26_20:48:01
ID 273 gen 789647 top level 5 path @apt-snapshot-release-upgrade-plucky-2025-05-26_20:48:02
ID 274 gen 789648 top level 5 path @apt-snapshot-release-upgrade-plucky-2025-05-26_20:48:27
ID 275 gen 947600 top level 5 path @apt-snapshot-release-upgrade-questing-2025-10-29_23:44:22
ID 276 gen 947601 top level 5 path @apt-snapshot-release-upgrade-questing-2025-10-29_23:44:27
ID 277 gen 1309244 top level 5 path @apt-snapshot-release-upgrade-resolute-2026-06-20_22:27:47
ID 278 gen 1309245 top level 5 path @apt-snapshot-release-upgrade-resolute-2026-06-20_22:27:52
There seem to be some very old snapshots here that I don't need anymore, but I cannot figure out how to delete them. Every guide out there says to just run btrfs subvolume delete /path/to/subvolume but every possible way I can think of to insert the "paths" that I'm given just result in ERROR: Could not statfs: No such file or directory
Edit: I also figured out why my filesystem was full when it shouldn't have been. Btrfs needs to be rebalanced and defragmented every so often. I believe it was the rebalancing that did it, as per this thread https://askubuntu.com/a/464531/2483935, but I also ran a defragment without checking filesystem usage in between so maybe just run both.
I'm trying to install Ubuntu Desktop 26.04 on a chassis that was manufactured as a backup appliance. The installer keeps failing with no specific error message, I only get the curtin logs and that's it. (The UI shows me a log file and then I figured out how to get the same log file through terminal so I could start saving and comparing logs.)
The OS drive is a refurbished solid state drive that I just got, because the old OS drive in the device was bad.
I figured out some things that I think are helping it get a bit further than it used to:
I haven't been trying to boot Ubuntu after most of these installs. The one time that I did, it was when it thought it had an internet connection but couldn't actually use it due to having no DNS, and it was missing a bunch of basic utilities. I gave up and tried to reinstall when I hit something I needed (forget which command unfortunately) that normally comes with Ubuntu but was absent, and is installed with a deb file instead of apt, but I couldn't find the deb file online anywhere because it's supposed to come with the OS.
Here are the most recent two logs. One was taken with an additional USB drive plugged in that I use to store the log files, the other one I waited til after it had run before plugging in the log storage USB.
Here's the last little bit of the log that seemed to get the farthest:
Applying debconf selections
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'debconf-set-selections'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'dpkg-query', '--list'] with allowed return codes [0] (capture=True)
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.006
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.009
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
UEFI remove old olders efi state:
EFIBootState(current='0009', timeout='1 seconds', order=['000A', '0009', '0005'], entries={'0005': EFIBootEntry(name='Hard Drive', path='BBS(HD,,0x0)414d474f414d4e4fa5000000010000006f0057004400430020005700440042004e0043004500320035003000300050004e00430000000501090002000000007fff040002010c00d041030a0000000001010600021f03120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63800310032003400370032003200340030003100350037002000200020002000200020002000200000007fff0400414d424f414d4e4f9b000000010000006300200055005300420020004400490053004b00200032002e003000200050004d004100500000000501090002000000007fff040002010c00d041030a000000000101060000140305060001007fff040001043600ef47642dc93ba041ac194d51d01b4ce6300037003000310039003700360032004600380042003200440045003000380000007fff0400414d424f'), '0009': EFIBootEntry(name='UEFI: USB DISK 2.0 PMAP', path='PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,2fdf80be-e145-40c5-aa51-61a53ab5282e,0xc21d04,0x2838)AMBO'), '000A': EFIBootEntry(name='UEFI: WDC WDBNCE2500PNC', path='PciRoot(0x0)/Pci(0x1f,0x2)/Sata(4,65535,0)/HD(1,GPT,502aff24-45b2-456a-a358-7eafc504c6f4,0x800,0x219800)AMBO')})
installing grub to target=/target devices=['/dev/sda1'] [replace_defaults=True]
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'dpkg', '--print-architecture'] with allowed return codes [0] (capture=True)
updated /target/etc/default/grub to set: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Using grub install command: /usr/lib/grub/grub-multi-install
Grub install cmds:
[['efibootmgr', '-v'], ['dpkg-reconfigure', 'grub-efi-amd64'], ['update-grub'], ['/usr/lib/grub/grub-multi-install'], ['efibootmgr', '-v']]
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'dpkg-reconfigure', 'grub-efi-amd64'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'update-grub'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', '/usr/lib/grub/grub-multi-install'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.004
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
Skipped reordering of UEFI boot methods.
Currently booted UEFI loader might no longer boot.
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.008
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: SUCCESS: installing grub to target devices
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: SUCCESS: configuring target system bootloader
start: cmd-install/stage-curthooks/builtin/cmd-curthooks/copy-cdrom-metadata: copying metadata from /cdrom
copying media-info into target
/cdrom/.disk/ubuntu_dist_channel not found, skipping
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/copy-cdrom-metadata: SUCCESS: copying metadata from /cdrom
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: SUCCESS: curtin command curthooks
{'current': '0009', 'timeout': '1 seconds', 'order': '000A,0009,0005'}
{'current': '0009', 'timeout': '1 seconds', 'order': '000A,0009,0005'}
{'current': '0009', 'timeout': '1 seconds', 'order': '0000,000A,0009,0005'}
curtin: Installation finished.
I've been struggling with this device for multiple days at this point. I've installed earlier versions of Ubuntu desktop on laptops without issue several times before (currently I'm posting this from 24.04), but this particular hardware just hates me or something.
I'm trying to open a new xterm window with a different PS1. I've tried:
xterm -e '/bin/bash -i -l -c "export PS1=foo"'
This immediately closes xterm. So I tried:
xterm -hold -e '/bin/bash -i -l -c "export PS1=foo"'
which keeps xterm open, but I can't use it, i.e.: there is no prompt. Then played around with various options like:
xterm -e "export PS1=foo; $SHELL"
and so on ... But none seem to work. Can you please help?
$ xterm -version
XTerm(390)
$ bash --version
GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)
I had a Lenovo Thinkpad T490 with a 256GB NVMe 2280 SSD loading Windows 11.
I want to install Kubuntu 26.04 on this laptop. For this I got another 256GB NVMe 2230 SSD and connected it to the WLAN port of the laptop.
Windows recognised this drive correctly. Then I boot from Kubuntu Live USB and that recognises both drives as well.
I installed Kubuntu on the new SSD with a partition configuration of 300MB FAT32 partition mounted to /boot/efi and boot flag on, and the rest of the drive formatted to ext4 mounted to /.
Install process goes on smoothly and it says "Finished". However, on reboot (after removing the live USB), it directly boots to Windows without the dual boot options.
So, as suggested in a Youtube video, I removed the original 2280 SSD and then reinstalled Kubuntu on the new 2230 SSD using the live USB (this time used Erase Disk option instead of manual partitioning).
This time again, the install went on smoothly, but when I rebooted after removing the liveusb, it doesn't show boot screen at all. Instead the BIOS asks for a medium to boot from.
I'd like to mention that in case of both installs, Kubuntu shows in the BIOS boot priority list and it didn't work even after putting it on the top of the list.
I am returning to Linux after 15 years, so please be patient with me.
Output of efibootmgr from live USB is:
kubuntu@kubuntu:~$ efibootmgr
BootCurrent: 001F
Timeout: 2 seconds
BootOrder: 0001,001C,0010,0011,0012,0013,0014,0015,001B,001F,0019,001A,0000,001D,001E,0020,0021,0022,0023
Boot0000* Windows Boot Manager HD(1,GPT,76f26192-bf42-41dc-b9e9-43d8205dd33d,0x800,0x32000)/\EFI\ubuntu\grubx64.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000033000100000010000000040000007fff0400
Boot0001* Kubuntu HD(1,GPT,96c89b38-a577-4bde-a1c4-8ded1adb3746,0x1000,0x96000)/\EFI\ubuntu\shimx64.efi
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014 Regulatory Information FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot0015 ThinkShield secure wipe FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0016 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0017 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0018 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0019* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001A* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001B* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001C* NVMe1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a401)
Boot001D* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot001E* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot001F* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0020* PXE BOOT VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0021* LENOVO CLOUD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0022 Other CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
Boot0023 Other HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
Boot0024* IDER BOOT CDROM PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot0025* IDER BOOT Floppy PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0026* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0027* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
After installing Ubuntu 26.04 in Asus Expertbook Ultra (X7 385H) why getting problem in some function keys. Like brightness increase / decrease, fingerprint option not showing in settings, and IR facial recognition login option is not working.
im having a really annoying problem on my dell latitude e7450 (intel graphics) where Ubuntu won't turn the screen back on after sleep. the laptop wakes up, but the screen just stays totally black.
I'm on the latest version of Ubuntu and I'm using Wayland. (just to be clear, I want to stick with Wayland and I haven't tried xorg at all for this).
Here's a list of what I've tried so far using Kate to edit the config files:
I tried fixing the Intel power-saving stuff:
I added i915.enable_dc=0 and i915.enable_psr=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.
Forced deep sleep:
I also added mem_sleep_default=deep to the grub cmdline to make sure it's actually going into a real sleep state.
Enabled early KMS for the graphics driver:
I added i915 to the bottom of my /etc/initramfs-tools/modules file so the driver loads early.
After doing all that, i ran sudo update-grub and sudo update-initramfs -u and rebooted.
Even after updating Ubuntu to the latest version and applying all these fixes, it still doesn't fix the screen wake up problem. Does anyone know what else I can try to fix this black screen issue on Wayland?
Date generated: 2026-07-22 20:42:03
Hardware Information:
Hardware Model: Dell Inc. Latitude E7450
Memory: 16.0 GiB
Processor: Intel Core i7-5600U × 4
Graphics: Intel HD Graphics 5500 (BDW GT2)
Disk Capacity: 512.1 GB
Software Information:
Firmware Version: A24
OS: Ubuntu 26.04
OS Build: (null)
OS Type: 64-bit
GNOME Version: 50
Windowing System: Wayland
Kernel Version: Linux 7.0.0-28-generic
Note: This is definitely an Ubuntu specific software issue. The laptop wakes from sleep perfectly fine on other operating systems like MX Linux,Fedora, EndeavourOS so the hardware and screen are fully functional.
After a routine fwupd firmware update my laptop's built-in screen became very dim, even at "100%" brightness. An external monitor on the same machine looks completely normal.
Laptop: Dell Latitude 5430, Intel Iris Xe (Alder Lake, i915), internal eDP panel (AU Optronics).
OS: Ubuntu 24.04, GNOME.
Trigger: fwupd auto-flashed the Dell system BIOS from 1.36.0 to 1.39.1 (check with fwupdmgr get-history). The screen was fine before that.
What I already ruled out (none of these help):
Not a kernel regression — dim on every kernel I tried; the panel is only bright in recovery mode / with nomodeset (i.e. when i915 is not driving it).
Not gamma/ICC — xrandr Brightness 1.0, Gamma 1.0, no VCGT in the ICC profile.
Not a software brightness slider — /sys/class/backlight/intel_backlight reports brightness == actual_brightness == max_brightness (1023), yet the panel is dim.
Brightness keys only make it dimmer, never brighter.
Downgrading the BIOS is blocked: LVFS only offers 1.39.1, so fwupdmgr / GNOME Firmware cannot roll back.
How do I get the panel bright again without a BIOS downgrade?
I've been trying to get my UB600 Bluetooth dongle to work, however it seems that it's not compatible out of the box. In fact, there's only 1 place with a solution how to get it to work however it seems the explanation on how to do it goes over my head. I've tried using what they gave me in konsole but some things just error and I can't seem to get around that. The fix I've been attempting is this. The issue I'm having is, it detects the Bluetooth dongle, but the computer is then unable to detect any Bluetooth devices at all. The lsusb is exactly as shown on that link as is the journalctl.
Results of lsusb | grep -i 'tp-link':
Bus 001 Device 012: ID 37ad:0600 TP-Link Bluetooth USB Adapter
Results of journalctl:
usb 1-1: new full-speed USB device number 12 using xhci_hcd
usb 1-1: New USB device found, idVendor=37ad, idProduct=0600, bcdDevice= 2.00
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: TP-Link Bluetooth USB Adapter
usb 1-1: Manufacturer:
usb 1-1: SerialNumber: 18694530DB8B
Bluetooth: MGMT ver 1.23
I ran sudo dmesg | grep -i bluetooth and got this:
server@server-z87hd3:~$ sudo dmesg | grep -i bluetooth
[sudo] password for server:
[647887.635955] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[647887.709668] Bluetooth: MGMT ver 1.23
[648046.220743] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648046.221733] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648046.222744] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648046.222748] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648046.224331] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648046.224378] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648046.376751] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648046.443866] Bluetooth: MGMT ver 1.23
[648062.029928] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648062.105001] Bluetooth: MGMT ver 1.23
[648220.950989] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648220.951983] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648220.952966] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648220.952969] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648220.953197] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648220.953223] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648221.105982] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648221.173128] Bluetooth: MGMT ver 1.23
[648256.225222] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648256.298247] Bluetooth: MGMT ver 1.23
[649742.374342] Bluetooth: MGMT ver 1.23
[682771.713073] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[682771.785356] Bluetooth: MGMT ver 1.23
Is there any chance somebody could explain to me like I'm a 5 year old how to apply that patch, or better yet, create a solution for me? I am running Kubuntu 26.04 on kernel 7.0.0-27-27.
Edit: Following "david" in the comments advice results.
server@server-z87hd3:~$ sudo apt install bluetooth bluez -y
[sudo: authenticate] Password:
bluez is already the newest version (5.85-4ubuntu0.1).
bluez set to manually installed.
Installing:
bluetooth
Suggested packages:
bluez-meshd
Summary:
Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 3
Download size: 6,600 B
Space needed: 36.9 kB / 180 GB available
Get:1 http://archive.ubuntu.com/ubuntu resolute-updates/universe amd64 bluetooth all 5.85-4ubuntu0.1 [6,600 B]
Fetched 6,600 B in 0s (121 kB/s)
Selecting previously unselected package bluetooth.
(Reading database… 268329 files and directories currently installed.)
Preparing to unpack …/bluetooth_5.85-4ubuntu0.1_all.deb…
Unpacking bluetooth (5.85-4ubuntu0.1)…
Setting up bluetooth (5.85-4ubuntu0.1)…
server@server-z87hd3:~$ sudo systemctl start bluetooth
server@server-z87hd3:~$ sudo systemctl enable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable bluetooth
server@server-z87hd3:~$ bluetoothctl show | grep "Powered"
Powered: yes
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 18:69:45:30:DB:8B Discovering: yes
[bluetoothctl]> power on#
Invalid argument on#
[bluetoothctl]> power on
Changing power on succeeded
[bluetoothctl]> agent on
Agent is already registered
[bluetoothctl]> default-agent
Default agent request successful
[bluetoothctl]> discoverable on
hci1 new_settings: powered connectable bondable ssp br/edr le secure-conn ll-privacy
[CHG] Controller 18:69:45:30:DB:8B Connectable: yes
hci1 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn ll-privacy
Changing discoverable on succeeded
[CHG] Controller 18:69:45:30:DB:8B Discoverable: yes
[bluetoothctl]> pairable on
Changing pairable on succeeded
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[bluetoothctl]>
I have disabled Secure Boot and run Bluetoothctl show:
server@server-z87hd3:~$ bluetoothctl show
Controller 18:69:45:30:DB:8B (public)
Manufacturer: 0x005d (93)
Version: 0x0a (10)
Name: server-z87hd3 #2
Alias: server-z87hd3 #2
Class: 0x006c0104 (7078148)
Powered: yes
PowerState: on
Discoverable: yes
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Client (0000112e-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (185f3df4-3268-4e3f-9fca-d4d5059915bd)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0555
Discovering: yes
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
SupportedCapabilities.MinTxPower: 0xffffffa6 (-90)
SupportedCapabilities.MaxTxPower: 0x0000 (0)
SupportedCapabilities.MaxAdvLen: 0xfb (251)
SupportedCapabilities.MaxScnRspLen: 0xfb (251)
SupportedFeatures: CanSetTxPower
SupportedFeatures: HardwareOffload
server@server-z87hd3:~$
This is what my results are like with my 5.0 dongle for comparison:
server@server-z87hd3:~$ bluetoothctl show
Controller 04:42:1A:54:A8:55 (public)
Manufacturer: 0x005d (93)
Version: 0x0a (10)
Name: server-z87hd3 #2
Alias: Asus 5.0
Class: 0x006c0104 (7078148)
Powered: yes
PowerState: on
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (185f3df4-3268-4e3f-9fca-d4d5059915bd)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Client (0000112e-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0555
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
SupportedCapabilities.MinTxPower: 0xffffffed (-19)
SupportedCapabilities.MaxTxPower: 0x0017 (23)
SupportedCapabilities.MaxAdvLen: 0xfb (251)
SupportedCapabilities.MaxScnRspLen: 0xfb (251)
SupportedFeatures: CanSetTxPower
SupportedFeatures: HardwareOffload
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[NEW] Media /org/bluez/hci0
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 04:42:1A:54:A8:55 Discovering: yes
[G522 Gaming Headset]> scan on
SetDiscoveryFilter success
Discovery started
[NEW] Device DE:B6:45:46:3D:0B Govee_H6076_3D0B
[NEW] Device FF:02:3C:C8:FA:46 BLE MF8470
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbd (-67)
[NEW] Device D0:C8:03:C6:6F:76 Govee_H61D5_6F76
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[NEW] Device 33:36:9F:00:1E:8B 33-36-9F-00-1E-8B
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device FF:02:3C:C8:FA:46 UUIDs: 19fe1b3d-4c5b-36b8-4043-c09ddc76099e
[NEW] Device DE:CD:2F:A8:FA:1A ET-2850 Series
[NEW] Device DC:6E:02:C6:22:87 Govee_H7078_2287
[NEW] Device DE:B6:41:06:19:77 Govee_H6022_1977
[NEW] Device C8:FF:77:CB:9B:32 VW1-UK-MAA1830A
[NEW] Device 13:12:70:E3:1C:0B 13-12-70-E3-1C-0B
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffab (-85)
[NEW] Device DC:B4:D9:F4:2A:42 DC-B4-D9-F4-2A-42
[NEW] Device D6:50:84:C6:55:17 Govee_H6099_5517
[NEW] Device 00:00:00:00:00:00 00-00-00-00-00-00
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffad (-83)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb3 (-77)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbf (-65)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbf (-65)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device D6:50:84:C6:55:17 AdvertisingFlags:
00 .
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffad (-83)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffb9 (-71)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device D6:50:84:C6:55:17 AdvertisingFlags:
06 .
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffaf (-81)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbf (-65)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa7 (-89)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffaf (-81)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbd (-67)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbf (-65)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffcd (-51)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbd (-67)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffab (-85)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffb1 (-79)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffc7 (-57)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[DEL] Device 13:12:70:E3:1C:0B 13-12-70-E3-1C-0B
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffad (-83)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffc7 (-57)
Edit: I should specify this dongle is a Bluetooth 6.0 dongle.
After upgrading from Ubuntu 25.10 to Ubuntu 26.04, randomly when starting Thunderbird the screen freezes and says kernel panic fatal exception in interrupt After restarting it continues to work, but randomly crashes again.
I am a newbie, so i am sorry in advance.
I have a very old scanner/printer. It worked on Windows 11 but every since i changed to ubundu (24.04.3), i cannot make it work.
I read that the transition package libpango1.0-0 was dropped in ubundu 24, and i dont know how to tell my scanner's drivers which depend on libpango1.0-0 that it's the same as libpango-1.0-0.
sudo apt-get install libpango1.0-0 did not work
scanner driver is from there https://asia.canon/en/support/0100551901?model=8330B, (there was also a source file , but i did not get any better results https://asia.canon/en/support/0100553202?model=8330B)
I tried to creat sym link as follows:
sudo
ln -s /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
/usr/lib/libpango1.0.so.0
and rebooted but it did not get any results , i think maybe because i dont know where install.sh is looking for dependencies . I nano-ed into install.sh, but i could not figure it out.
I appreciate ur help.
Best wishes
I'm looking for a reliable WhatsApp client that works well on Ubuntu 24.04 LTS. Ideally, the client should have:
How to set this up?
I have a new Logitech LIFT mouse and want to remap the thumb buttons. Now the buttons are assigned to go back one page in the web browser and forward, essentially as Alt+← and Alt+→, repsectively.
I want to remap them to Ctrl+Tab and Ctrl+Shift+Tab instead, so I can cycle through my tabs in the browser and other applications.
I have tried to map them with Solaar following THIS POST but it does not seem to recognize the thumb buttons there. It might also be that I do not understand how "Key Button Diversion" works.
I am unsure how to approach this further, and where to look.
I am running Ubuntu 24.10 and GNOME 47 (Wayland), but am still very new to this.
Running on Ubuntu 24.04 (Noble Numbat) I get the following error:
$ classicmenu-indicator
Traceback (most recent call last):
File "/usr/bin/classicmenu-indicator", line 11, in <module>
load_entry_point('classicmenu-indicator==0.11', 'console_scripts', 'classicmenu-indicator')()
File "/usr/lib/python3/dist-packages/classicmenu_indicator/cmindicator.py", line 578, in main
indicator = ClassicMenuIndicator()
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/classicmenu_indicator/cmindicator.py", line 152, in __init__
gettext.bind_textdomain_codeset(settings.GETTEXT_DOMAIN, 'UTF-8')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'gettext' has no attribute 'bind_textdomain_codeset'
My python version is :
$ python3 Python 3.12.3
I don't understand the significance of Ubuntu version numbers, especially the last portion (ex. ".4")
On the Ubuntu download page, there are the following options:
Standard support
LTS Releases
Ubuntu 22.04 LTS (Jammy Jellyfish) ›
Ubuntu 20.04.4 LTS (Focal Fossa) ›
Ubuntu 18.04.6 LTS (Bionic Beaver) ›
FROM: https://wiki.ubuntu.com/Releases
Version End of Standard Support End of Life
Ubuntu 22.04 LTS April 2027 April 2032
Ubuntu 20.04.4 LTS July 2022 July 2022
What is the difference between Jammy Jellyfish and Focal Fossa?
Is 22.04 newer than 20.04.4?
Does this have anything to do with the "End of Life" date?
I just discovered thermald for preventing machines from overheating. I'd like some basic suggestions on how to modify the xml configuration file. Below is the one I have at /etc/thermald/thermal-conf.xml. From some examples I have skimmed online, it seems it is set to start preventing overheating at 55 C (if I am reading the <Temperature>55000</Temperature> line correctly), but my cores reach even 94 C with fans going on.
I am using a Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz machine.
<?xml version="1.0"?>
<!--
use "man thermal-conf.xml" for details
-->
<!-- BEGIN -->
<ThermalConfiguration>
<Platform>
<Name>Generic X86 Laptop Device</Name>
<ProductName>EXAMPLE_SYSTEM</ProductName>
<Preference>QUIET</Preference>
<ThermalSensors>
<ThermalSensor>
<Type>TSKN</Type>
<AsyncCapable>1</AsyncCapable>
</ThermalSensor>
</ThermalSensors>
<ThermalZones>
<ThermalZone>
<Type>SKIN</Type>
<TripPoints>
<TripPoint>
<SensorType>TSKN</SensorType>
<Temperature>55000</Temperature>
<type>passive</type>
<ControlType>SEQUENTIAL</ControlType>
<CoolingDevice>
<index>1</index>
<type>rapl_controller</type>
<influence> 100 </influence>
<SamplingPeriod> 16 </SamplingPeriod>
</CoolingDevice>
<CoolingDevice>
<index>2</index>
<type>intel_powerclamp</type>
<influence> 100 </influence>
<SamplingPeriod> 12 </SamplingPeriod>
</CoolingDevice>
</TripPoint>
</TripPoints>
</ThermalZone>
</ThermalZones>
</Platform>
<!-- Thermal configuration example only -->
<Platform>
<Name>Example Platform Name</Name>
<!--UUID is optional, if present this will be matched -->
<!-- Both product name and UUID can contain
wild card "*", which matches any platform
-->
<UUID>Example UUID</UUID>
<ProductName>Example Product Name</ProductName>
<Preference>QUIET</Preference>
<ThermalSensors>
<ThermalSensor>
<!-- New Sensor with a type and path -->
<Type>example_sensor_1</Type>
<Path>/some_path</Path>
<AsyncCapable>0</AsyncCapable>
</ThermalSensor>
<ThermalSensor>
<!-- Already present in thermal sysfs,
enable this or add/change config
For example, here we are indicating that
sensor can do async events to avoid polling
-->
<Type>example_thermal_sysfs_sensor</Type>
<!-- If async capable, then we don't need to poll -->
<AsyncCapable>1</AsyncCapable>
</ThermalSensor>
<ThermalSensor>
<!-- Examle of a virtual sensor. This sensor
depends on other real sensor or
virtual sensor.
E.g. here the temp will be
temp of example_sensor_1 * 0.5 + 10
-->
<Type>example_virtual_sensor</Type>
<Virtual>1</Virtual>
<SensorLink>
<SensorType>example_sensor_1</SensorType>
<Multiplier> 0.5 </Multiplier>
<Offset> 10 </Offset>
</SensorLink>
</ThermalSensor>
</ThermalSensors>
<ThermalZones>
<ThermalZone>
<Type>Example Zone type</Type>
<TripPoints>
<TripPoint>
<SensorType>example_sensor_1</SensorType>
<!-- Temperature at which to take action -->
<Temperature> 75000 </Temperature>
<!-- max/passive/active
If a MAX type is specified, then
daemon will use PID control
to aggresively throttle to avoid
reaching this temp.
-->
<type>max</type>
<!-- SEQUENTIAL | PARALLEL
When a trip point temp is violated, then
number of cooling device can be activated.
If control type is SEQUENTIAL then
It will exhaust first cooling device before trying
next.
-->
<ControlType>SEQUENTIAL</ControlType>
<CoolingDevice>
<index>1</index>
<type>example_cooling_device</type>
<!-- Influence will be used order cooling devices.
First cooling device will be used, which has
highest influence.
-->
<influence> 100 </influence>
<!-- Delay in using this cdev, this takes some time
too actually cool a zone
-->
<SamplingPeriod> 12 </SamplingPeriod>
</CoolingDevice>
</TripPoint>
</TripPoints>
</ThermalZone>
</ThermalZones>
<CoolingDevices>
<CoolingDevice>
<!--
Cooling device can be specified
by a type and optionally a sysfs path
If the type already present in thermal sysfs
no need of a path.
Compensation can use min/max and step size
to increasing cool the system.
Debounce period can be used to force
a waiting period for action
-->
<Type>example_cooling_device</Type>
<MinState>0</MinState>
<IncDecStep>10</IncDecStep>
<ReadBack> 0 </ReadBack>
<MaxState>50</MaxState>
<DebouncePeriod>5000</DebouncePeriod>
<!--
If there are no PID parameter
compensation increase step wise and exponentaially
if single step is not able to change trend.
Alternatively a PID parameters can be specified
then next step will use PID calculation using
provided PID constants.
-->>
<PidControl>
<kp>0.001</kp>
<kd>0.0001</kd>
<ki>0.0001</ki>
</PidControl>
</CoolingDevice>
</CoolingDevices>
</Platform>
</ThermalConfiguration>
<!-- END -->
Following the suggestion from @heynnema, I have deleted the configuration file, stopped thermald, and ran sudo thermald --no-daemon --loglevel=info. Following is the output, but how is this supposed to help me construct a new, more efficient configuration file?
$ sudo thermald --no-daemon --loglevel=info
[1649408071][INFO]RAPL domain count 1
[1649408071][INFO]RAPL domain count 1
[1649408071][MSG]22 CPUID levels; family:model:stepping 0x6:a5:2 (6:165:2)
[1649408071][INFO]Running on a vanilla kernel
[1649408071][MSG]Polling mode is enabled: 4
[1649408071][INFO]sensor_update: type TSKN
[1649408071][INFO]sensor_update: type acpitz
[1649408071][INFO]sensor_update: type x86_pkg_temp
[1649408071][INFO]sensor_update: type pch_cometlake
[1649408071][INFO]sensor_update: type NGFF
[1649408071][INFO]sensor_update: type TMEM
[1649408071][INFO]sensor_update: type B0D4
[1649408071][INFO]sensor_update: type TVGA
[1649408071][INFO]thd_read_default_thermal_sensors loaded 8 sensors
[1649408071][INFO]dts /sys/devices/platform/coretemp.0/name doesn't exist
[1649408071][WARN]sensor id 11 : No temp sysfs for reading raw temp
[1649408071][WARN]sensor id 11 : No temp sysfs for reading raw temp
[1649408071][WARN]sensor id 11 : No temp sysfs for reading raw temp
[1649408071][INFO]INT3400 Base path is
[1649408071][INFO]failed to open /dev/acpi_thermal_rel
[1649408071][INFO]failed to open /dev/acpi_thermal_rel
[1649408071][INFO]TRT/ART read failed
[1649408071][INFO]Using config file /etc/thermald/thermal-conf.xml
I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
[1649408071][WARN]error: could not parse file /etc/thermald/thermal-conf.xml
[1649408071][INFO]sensor index:2 TSKN /sys/class/thermal/thermal_zone2/ Async:0
[1649408071][INFO]sensor index:0 acpitz /sys/class/thermal/thermal_zone0/ Async:0
[1649408071][INFO]sensor index:7 x86_pkg_temp /sys/class/thermal/thermal_zone7/ Async:1
[1649408071][INFO]sensor index:5 pch_cometlake /sys/class/thermal/thermal_zone5/ Async:0
[1649408071][INFO]sensor index:3 NGFF /sys/class/thermal/thermal_zone3/ Async:0
[1649408071][INFO]sensor index:1 TMEM /sys/class/thermal/thermal_zone1/ Async:0
[1649408071][INFO]sensor index:6 B0D4 /sys/class/thermal/thermal_zone6/ Async:0
[1649408071][INFO]sensor index:4 TVGA /sys/class/thermal/thermal_zone4/ Async:0
[1649408071][INFO]sensor index:8 hwmon /sys/class/hwmon/hwmon5/temp1_input Async:0
[1649408071][INFO]sensor index:9 hwmon /sys/class/hwmon/hwmon5/temp2_input Async:0
[1649408071][INFO]sensor index:10 hwmon /sys/class/hwmon/hwmon5/temp3_input Async:0
[1649408071][INFO]thd_read_default_cooling devices loaded 14 cdevs
[1649408071][INFO]ppcc limits max:47000000 min:10000000 min_win:28000000 step:1000000
[1649408071][INFO]set_pid_param 14 [-1000.100,10]
[1649408071][INFO]Use Default pstate drv settings
[1649408071][INFO]sysfs create failed
[1649408071][INFO]INT3400 Base path is
[1649408071][INFO]failed to open /dev/acpi_thermal_rel
[1649408071][INFO]failed to open /dev/acpi_thermal_rel
[1649408071][INFO]TRT/ART read failed
[1649408071][INFO]Using config file /etc/thermald/thermal-conf.xml
I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
[1649408071][WARN]error: could not parse file /etc/thermald/thermal-conf.xml
[1649408071][INFO]name = package-0
[1649408071][INFO]name = dram
[1649408071][INFO]sysfs read failed /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2/constraint_0_max_power_uw
[1649408071][INFO]:powercap RAPL invalid max power limit range
[1649408071][INFO]Calculate dynamically phy_max
[1649408071][INFO]set_pid_param 18 [-0.4.0,0]
[1649408071][INFO]13: ath10k_thermal, C:0 MN: 0 MX:100 ST:1 pt:/sys/class/thermal/ rd_bk 1
[1649408071][INFO]1: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]11: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]8: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]6: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]4: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]2: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]12: intel_powerclamp, C:-1 MN: 0 MX:50 ST:5 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]0: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]10: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]9: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]7: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]5: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]3: Processor, C:0 MN: 0 MX:3 ST:1 pt:/sys/class/thermal/ rd_bk 0
[1649408071][INFO]14: rapl_controller, C:47000000 MN: 47000000 MX:10000000 Inc ST:-2000000 Dec ST:-1000000 pt:/sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/ rd_bk 1
[1649408071][INFO]15: intel_pstate, C:0 MN: 0 MX:10 ST:1 pt:/sys/devices/system/cpu/intel_pstate/ rd_bk 1
[1649408071][INFO]16: rapl_controller_dram, C:100000000 MN: 100000000 MX:0 ST:-500000 pt:/sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2/ rd_bk 1
[1649408071][INFO]17: LCD, C:0 MN: 0 MX:120000 ST:12000 pt:/sys/class/backlight/intel_backlight/ rd_bk 1
[1649408071][INFO]18: amdgpu, C:0 MN: 0 MX:0 ST:0 pt: rd_bk 1
[1649408071][INFO]thd_read_default_thermal_zones loaded 7 zones
[1649408071][INFO]INT3400 Base path is
[1649408071][INFO]zone cpu will be created
[1649408071][INFO]dts zone /sys/devices/platform/coretemp.0/name doesn't exist
[1649408071][INFO]/sys/class/hwmon/hwmon6/name->dell_smm
[1649408071][INFO]/sys/class/hwmon/hwmon4/name->pch_cometlake
[1649408071][INFO]/sys/class/hwmon/hwmon2/name->BAT0
[1649408071][INFO]/sys/class/hwmon/hwmon0/name->AC
[1649408071][INFO]/sys/class/hwmon/hwmon7/name->ath10k_hwmon
[1649408071][INFO]/sys/class/hwmon/hwmon5/name->coretemp
[1649408071][INFO]Buggy max temp: to close to critical 90000
[1649408071][INFO]Core temp DTS :critical 100000, max 90000, psv 95000
[1649408071][INFO]node type: Element, name: CoolingDevice value: rapl_controller
[1649408071][INFO]node type: Element, name: CoolingDevice value: intel_pstate
[1649408071][INFO]node type: Element, name: CoolingDevice value: intel_powerclamp
[1649408071][INFO]node type: Element, name: CoolingDevice value: cpufreq
[1649408071][INFO]node type: Element, name: CoolingDevice value: Processor
[1649408071][INFO]CDEVS order specified in thermal-cpu-cdev-order.xml
[1649408071][INFO]/sys/class/hwmon/hwmon3/name->nouveau
[1649408071][INFO]/sys/class/hwmon/hwmon1/name->acpitz
[1649408071][INFO]INT3400 Base path is
[1649408071][INFO]failed to open /dev/acpi_thermal_rel
[1649408071][INFO]failed to open /dev/acpi_thermal_rel
[1649408071][INFO]TRT/ART read failed
[1649408071][INFO]Using config file /etc/thermald/thermal-conf.xml
I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
[1649408071][WARN]error: could not parse file /etc/thermald/thermal-conf.xml
[1649408071][INFO]
ZONE DUMP BEGIN
[1649408071][INFO]
[1649408071][INFO]Zone 8: cpu, Active:1 Bind:0 Sensor_cnt:1
[1649408071][INFO]..sensors..
[1649408071][INFO]sensor index:7 x86_pkg_temp /sys/class/thermal/thermal_zone7/ Async:1
[1649408071][INFO]..trips..
[1649408071][INFO]index 0: type:passive temp:95000 hyst:0 zone id:8 sensor id:65535 control_type:1 cdev size:4
[1649408071][INFO]cdev[0] rapl_controller, Sampling period: 0
[1649408071][INFO] target_state:not defined
[1649408071][INFO]cdev[1] intel_pstate, Sampling period: 0
[1649408071][INFO] target_state:not defined
[1649408071][INFO]cdev[2] intel_powerclamp, Sampling period: 0
[1649408071][INFO] target_state:not defined
[1649408071][INFO]cdev[3] Processor, Sampling period: 0
[1649408071][INFO] target_state:not defined
[1649408071][INFO]index 1: type:polling temp:85500 hyst:0 zone id:8 sensor id:7 control_type:0 cdev size:0
[1649408071][INFO]
[1649408071][INFO]
ZONE DUMP END
[1649408071][INFO]Current user preference is 0
[1649408071][INFO]thd_engine_thread begin
After the edit, this is my configuration file, yet cores temp goes up to 90 C:
~$ cat /etc/thermald/thermal-conf.xml
<?xml version="1.0"?>
<ThermalConfiguration>
<Platform>
<Name>Generic X86 Laptop Device</Name>
<ProductName>*</ProductName>
<Preference>QUIET</Preference>
<ThermalZones>
<ThermalZone>
<Type>cpu</Type>
<TripPoints>
<TripPoint>
<SensorType>x86_pkg_temp</SensorType>
<Temperature>55000</Temperature>
<type>passive</type>
<ControlType>PARALLEL</ControlType>
</TripPoint>
</TripPoints>
</ThermalZone>
</ThermalZones>
</Platform>
</ThermalConfiguration>
Additional info:
~$ ls -al /etc/thermald
total 32
drwxr-xr-x 2 root root 4096 Apr 8 16:32 .
drwxr-xr-x 159 root root 12288 Apr 5 09:03 ..
-rw-r--r-- 1 root root 4605 Jan 15 2019 backup
-rw-rw-r-- 1 username username 816 Apr 8 16:32 thermal-conf.xml
-rw-r--r-- 1 root root 508 Jan 15 2019 thermal-cpu-cdev-order.xml
And also this seems relevant (thermald inactive?):
$ sudo systemctl status thermald
● thermald.service - Thermal Daemon Service
Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2022-04-08 10:54:28 CEST; 1 weeks 0 days ago
Main PID: 1328 (code=exited, status=0/SUCCESS)
Apr 07 11:51:51 Precision-3551 thermald[1328]: error: could not parse file /etc/thermald/thermal-conf.xml
Apr 07 11:51:51 Precision-3551 thermald[1328]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Apr 07 11:51:51 Precision-3551 thermald[1328]: error: could not parse file /etc/thermald/thermal-conf.xml
Apr 07 11:51:51 Precision-3551 thermald[1328]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Apr 07 11:51:51 Precision-3551 thermald[1328]: error: could not parse file /etc/thermald/thermal-conf.xml
Apr 08 10:54:26 Precision-3551 systemd[1]: Stopping Thermal Daemon Service...
Apr 08 10:54:26 Precision-3551 thermald[1328]: Terminating ...
Apr 08 10:54:27 Precision-3551 thermald[1328]: terminating on user request ..
Apr 08 10:54:28 Precision-3551 systemd[1]: thermald.service: Succeeded.
Apr 08 10:54:28 Precision-3551 systemd[1]: Stopped Thermal Daemon Service.
I have now reactivated it with sudo service thermald restart and now:
$ sudo systemctl status thermald
● thermald.service - Thermal Daemon Service
Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-04-15 22:26:23 CEST; 2s ago
Main PID: 609438 (thermald)
Tasks: 2 (limit: 18622)
Memory: 1.3M
CGroup: /system.slice/thermald.service
└─609438 /usr/sbin/thermald --systemd --dbus-enable --adaptive
Apr 15 22:26:23 Precision-3551 systemd[1]: Starting Thermal Daemon Service...
Apr 15 22:26:23 Precision-3551 systemd[1]: Started Thermal Daemon Service.
Apr 15 22:26:23 Precision-3551 thermald[609438]: 22 CPUID levels; family:model:stepping 0x6:a5:2 (6:165:2)
Apr 15 22:26:23 Precision-3551 thermald[609438]: 22 CPUID levels; family:model:stepping 0x6:a5:2 (6:165:2)
Apr 15 22:26:23 Precision-3551 thermald[609438]: Polling mode is enabled: 4
Apr 15 22:26:23 Precision-3551 thermald[609438]: sensor id 11 : No temp sysfs for reading raw temp
Apr 15 22:26:23 Precision-3551 thermald[609438]: sensor id 11 : No temp sysfs for reading raw temp
Apr 15 22:26:23 Precision-3551 thermald[609438]: sensor id 11 : No temp sysfs for reading raw temp
I'm having a hard time trying to install on my Windows 10 the Grub bootloader. I downloaded the Ubuntu 18.04.4-desktop-amd64 ISO then ran the Ubuntu live session, then I ran this command sudo fdisk -l
SSD:
According to some internet articles I need to shrink my current SSD at least by 400 MB in order to format a boot partition as EFI FAT32 with a proper flag, and with that I will be able to install GRUB there. I have never used a Linux distro before.
Would someone here give me guidance me with proper commands in order to shrink my current drive which has 223 size, but only has a free space of 33 GIB? I only need a 400 MB boot partition.
Once I have installed Grub, finally I would be able to ran the grub configuration to finally fix the HPET of my motherboard firmware among other things.
With GRUB booting Windows, I can access to the configuration of the motherboard firmware allowed in Asrock, and with that force High Event Precision Timing to Disable Cause in a regular way my motherboard firmware is causing issues with HPET forced enable even if I disabled it, so with the GRUB there is a configuration to force HPET to disable, and force the Windows timer to 3.580 MHz.
I am using Ubuntu 14.04. I am a high school teacher, and I want a software to create a school timetable. Just to feed it with the class lessons and teacher, for the teacher section. To provide it with subjects being taught, to auto generate it.
Would be an alternative to Windows's aScTimeTables.
I am currently running Ubuntu 12.0.4 on a 64 bit machine. I have an AM335X development board. Along with the kit came the compressed kernel (linux 3,2), rootfs, u-boot, and ARM cross compiler (arm-2010q1).
I uncompressed everything to a sub folder (/home/brent/work).
I have added the following to my .bashrc file:
PATH=/home/brent/work/arm-2010q1/bin:$PATH
CROSS_COMPILE=arm-none-linux-gnueabi-
I have also installed the following:
sudo apt-get install ia32-libs
When I go to built u-boot I am doing the following (per instructions that came with the kit):
brent@brent~/work/u-boot$ sudo make distclean
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
brent@brent~/work/u-boot$ sudo make myd_am335x_lcd4.3_config
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
Configuring for myd_am335x_lcd4.3 - Board: myd_am335x, Options: DISPLAY_LCD43
brent@brent~/work/u-boot$ sudo make
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk
/bin/bash: line 3: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk.dep
/bin/bash: line 3: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-ld: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
arm-none-linux-gnueabi-gcc -DDO_DEPS_ONLY \
-g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -I/home/brent/CropVentures/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem -pipe -DCONFIG_ARM -D__ARM__ -march=armv5 -Wall -Wstrict-prototypes \
-o lib/asm-offsets.s lib/asm-offsets.c -c -S
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
make: *** [lib/asm-offsets.s] Error 127
I have verified the binary is located at /home/brent/work/arm-2010q1/bin
I am also not sure why I need to have sudo as part of the command? If I do not I get a permissions error.
Any help or information on what I am doing wrong would be greatly appreciated.