High power consumption (20-22W) on HP Victus 15 (Ryzen 7 7435HS / RTX 4050) - Ubuntu https://askubuntu.com/questions/1566093/high-power-consumption-20-22w-on-hp-victus-15-ryzen-7-7435hs-rtx-4050-ub

I am experiencing high battery drain on Ubuntu with my HP Victus 15. Despite several optimizations, powertop shows a discharge rate of around 20-22W at idle/light use, which is quite high for this hardware.

System Specs:

  • Laptop: HP Victus 15

  • CPU: AMD Ryzen 7 7435HS

  • GPU: NVIDIA GeForce RTX 4050 (6GB)

  • OS: Ubuntu

What I have done so far:

  1. tlp: Installed and active.

  2. Turbo Boost: Disabled to save energy.

  3. GPU: Switched to integrated graphics using sudo prime-select intel (to ensure the NVIDIA card is powered down).

  4. Monitoring: Using powertop to track consumption, but it consistently stays between 20-22W.

Are there any specific kernel parameters, drivers, or BIOS settings for the HP Victus/Ryzen mobile series that I should look into? Any help would be greatly appreciated.

How can i disable Spotify title bar https://askubuntu.com/questions/1566092/how-can-i-disable-spotify-title-bar

I use latest version of Ubuntu. Spotify title bar looks like Windows Vista and i dont want to see that.

Mic works on Windows but not in Ubuntu - ASUS Laptop https://askubuntu.com/questions/1566090/mic-works-on-windows-but-not-in-ubuntu-asus-laptop

I've been reading the forums and found quite a few people with a similar issue, but none of the solutions worked for me.
My internal microphone is not working on Ubuntu. It works fine on Windows (dual boot), so it's definitely a software/driver issue.
System info:
- Computer: ASUS VivoBook X515EA
- Ubuntu: 25.10 (Questing)
- Audio chip: Realtek ALC256 (Intel Tiger Lake-LP Smart Sound)
- Audio server: PipeWire 1.4.7
What I've tried:
- Setting options snd-hda-intel model=asus-zenbook in /etc/modprobe.d/
- Adjusting capture levels in alsamixer (F4 view, HDA Intel PCH card)
- Setting the default source with pactl set-default-source
- Reinstalling PipeWire and resetting WirePlumber config
- Running amixer -c 0 cset numid=6 2 to select Internal Mic 1 (node 0x1b)
What I found:
- arecord -D hw:0,0 with Internal Mic 1 selected (numid=6 set to 2) does show vumeter activity so ALSA can capture audio at the hardware level
- However, PipeWire does not seem to pass the audio through, parecord and pw-record both record silence
- The dmesg shows the driver picks up two internal mic nodes: Internal Mic=0x12 and Internal Mic=0x1b
- Capture Switch (numid=8) needs to be set on,on manually after every reboot

arecord -l output:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC256 Analog [ALC256 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

It seems like ALSA captures audio correctly when configured manually, but PipeWire/WirePlumber doesn't route it properly to applications. Any ideas on what could be causing this or how to fix it?
Thanks in advance!

Deb-package for thunderbird for Ubuntu 26.04 [duplicate] https://askubuntu.com/questions/1566088/deb-package-for-thunderbird-for-ubuntu-26-04

is there a DEB-Package for Thunderbird and Ubuntu 26.04? Thanks Karl

How to fix screenshot in mobile view crashing libadwaita flatpak apps? https://askubuntu.com/questions/1566084/how-to-fix-screenshot-in-mobile-view-crashing-libadwaita-flatpak-apps

I installed a libadwaita app from flathub. I opened mobile view with ctrl + shift + m .

It looks like this (this is an example screenshot from the mobile view blog post, the actual app was different, but this issue is most likely generic):

image

Here I tried to take a screenshot by clicking on the screenshot button above, but the app crashed.

I tried running the app from terminal, and it says Vulkan is not supported in Haswell yet. How to fix this? I just need to take a screenshot. Surely I don't need accelerated graphics for something like taking a screenshot in mobile mode?

I am using Ubuntu 24.04 in an iMac made in 2013, which has Intel Haswell processor.

TPlink PCI 881ND wireless lan card is not getting detected in 26.04LTS https://askubuntu.com/questions/1566082/tplink-pci-881nd-wireless-lan-card-is-not-getting-detected-in-26-04lts

TPlink PCI 881ND wireless lan card is not getting detected in 26.04LTS,however it was getting detected in 24.04LTS

Apps opening in cage on wayland too zoomed out https://askubuntu.com/questions/1566080/apps-opening-in-cage-on-wayland-too-zoomed-out

I'm using cage (the single app opener on the cli that runs individual apps without a desktop environment,) to run apps on wayland in an effort to remove all distraction. Can't have 50 different windows open and all that temptation if you only have one app to work with!

I start the apps like this:

cage thunderbird.

It works! but the windows (the window X, minimize and maximize buttons, and all the content inside the window) of the apps I run all look zoomed out and shrunken. Even if I zoom in to the content, the buttons on the top of the window "menu bar" part and the minimize maximize and exit buttons, all remain shrunken.

I want the window edges, window buttons, and everything in the window to not look miniature. How do I expand it all? All of it.

Ubuntu Desktop 24.04 is not possible to resume appropriately after of the "systemctl suspend" command execution https://askubuntu.com/questions/1566077/ubuntu-desktop-24-04-is-not-possible-to-resume-appropriately-after-of-the-syste

For a ASUS laptop (2016) with 16GB Ram was installed Ubuntu Desktop 24.04.4 LTS. It works very fast.

For other machines in the LAN with Ubuntu when the systemctl suspend command is executed as expected the OS goes suspended until is pressed any key and the login screen appears again.

But only in this Asus: the command works, but is impossible "resume" ... the screen remains in black showing some messages (it's not possible to read it easily due to the font size). Please indicate where I can see that data in the logs to share here for more details. Therefore it's mandatory to hold down the poweroff button until the laptop shuts down and then to restart it again.

Note: Just in case it is a fresh install and there's an Nvidia graphics card (After to did do a research I read it would be a possible issue) without any driver installed because it's not required to make explicit use of the graphics card itself (for video games, graphic design, etc.).

Inconsistent access of local WIndows drive https://askubuntu.com/questions/1566076/inconsistent-access-of-local-windows-drive

On a dual boot PC with Windows and Ubuntu 24.04 as a user share, I'm seeing inconsistent access to a mounted Windows drive.

When listing the drive contents using the natively supported Windows access, all files appear:

share@PC1:/media/share/Big_Media$ ls -al
total 857
drwxrwxrwx 1 share users 65536 Nov 14 10:50 .
drwxr-x---+ 3 root root 4096 Apr 23 22:44 ..
drwxrwxr-x 1 share share 8192 May 21 2020 '$RECYCLE.BIN'
drwxrwxr-x 1 share share 0 Dec 10 2021 '2021 XP Build'
...

When listing the same drive mounted manually using ntfs-3g, even after configuring the user and group to be the same, there are no files!?

share@PC1:/mnt/htpc_bigmedia$ ls -al   
total 8   
drwxr-xr-x 2 share users 4096 Apr 23 19:10 .   
drwxr-xr-x 4 root  root  4096 Apr 23 19:10 ..   
share@PC1:/mnt/htpc_bigmedia$

Why in the second case is file access blocked? What am I missing?

Diagnostics ...

Unmounting the native connection and then trying "sudo mount -t ntfs-3g /dev/sdb1 /mnt/htpc_bigmedia" produced this response: $MFTMirr does not match $MFT (record 3). Failed to mount '/dev/sdb1': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details.

Will chase this down and advise ...

Boot-Repair problem https://askubuntu.com/questions/1566075/boot-repair-problem

Ubuntu 22.04 won't boot. Get a "Line endings are different ... set to pager=1" or something to that effect. Anyway I finally got Boot-Repair to fire up, but there was no "it was repaired" message.

Below is a link to what came up. Secure Boot is disabled. I did this using a USB drive. I have 5 partitions on the broken machine. I guess they're the sdb ones as the gpt3 says "unknown file". gpt 4 and 5 are Windows I believe.

It has both Ubuntu and Windows 10 installed on it. It's a Thinkpad if that matters. I searched and found a guy saying you can ignore the first 2 lines about the "MBR" and that some "EFI" partition didn't have a "Boot" thingy for it and to use "gparted" to add one.

I think that might be sdb2 here, but it shows a "boot" in the link. In the broken machine it shows gpt2 with and this is exact "efi /System Volume Information/" no boot or root.

Anyway, I'm pretty much new to all this. This originally was set up a few years ago by someone that's unable to work on it anymore, so I've just been doing searches and watching videos to try and figure it out.

https://paste.ubuntu.com/p/R73Zw2XkFx/

Is there a search function here?

Is there a way to get the possible answers to pop up again? I'd like to study them some more.

Ubuntu 24.04 only boots into emergency mode https://askubuntu.com/questions/1566074/ubuntu-24-04-only-boots-into-emergency-mode

I'm new to Linux (as in I only changed from Windows 10 last week) and just turned the PC off two days ago. When I restarted it the next day I got this black screen. I can enter recovery mode, but it doesn't boot any further than that.

[  OK  ] Finished plymouth-quit-wait.servic.old until boot process finishes up.
[  OK  ] Finished plymouth-quit.service - Terminate Plymouth Boot Screen.
[FAILED] Failed to start dbus.service - D-Bus System Message Bus.
[FAILED] Failed to start dbus.service - D-Bus System Message Bus.
[FAILED] Failed to start power-profiles-daemon.service - Power Profiles daemon.
[FAILED] Failed to start bluetooth.service - Bluetooth service.
[FAILED] Failed to start dbus.service - D-Bus System Message Bus.
[FAILED] Failed to start gnome-remote-desktop.service - GNOME Remote Desktop.
[FAILED] Failed to start systemd-oomd.servi.erspace Out-Of-Memory (OOM) Killer.
[FAILED] Failed to start systemd-oomd.servi.erspace Out-Of-Memory (OOM) Killer.
[FAILED] Failed to start dbus.service - D-Bus System Message Bus.
[FAILED] Failed to start gnome-remote-desktop.service - GNOME Remote Desktop.
[FAILED] Failed to start bluetooth.service - Bluetooth service.
[FAILED] Failed to start power-profiles-daemon.service - Power Profiles daemon.
[FAILED] Failed to start me.proton.vpn.spli.neling.service - Proton VPN Daemon.
[FAILED] Failed to listen on dbus.socket - D-Bus System Message Bus Socket.
[DEPEND] Dependency failed for me.proton.vp.neling.service - Proton VPN Daemon.
[DEPEND] Dependency failed for power-profil.on.service - Power Profiles daemon.
[DEPEND] Dependency failed for bluetooth.service - Bluetooth service.
[DEPEND] Dependency failed for gnome-remote.top.service - GNOME Remote Desktop.
[FAILED] Failed to listen on dbus.socket - D-Bus System Message Bus Socket.
[DEPEND] Dependency failed for gdm.service - GNOME Display Manager.
_

sudo apt update and sudo apt upgrade always return an inability to upgrade five packages but I can't manually upgrade them either.

A friend suggested sudo apt-get remove for each of the failed dependencies and then reinstalling it with sudo apt-get install, however each time I get told the system can't even find the packages to uninstall.

Please confirm this finding: Crash in LTSR2604 desktop adding printer with firewall enabled https://askubuntu.com/questions/1566072/please-confirm-this-finding-crash-in-ltsr2604-desktop-adding-printer-with-firew

My setup: Install in virtualbox virtual machine. Enable firewall. Try to add a printer. Now either a hang or a crash occurs.

Ubuntu 22.04 to 24.04 upgrade issues Curl and others https://askubuntu.com/questions/1566070/ubuntu-22-04-to-24-04-upgrade-issues-curl-and-others

I upgraded with do-release-upgrade from 22.4 to 24.4 and encountered no breaking-issues during the upgrade.

After the upgrade I had issues with many services, some resolved by getting systemd-resolver working. But i still have some lingering issues, if anyone has any tips it would be greatly appriciated!

Curl

curl: error while loading shared libraries: liblber-2.5.so.0:

I've tried to both purge and reinstall curl but it still requires liblber which is supposed to be replaced(?) by libldap.so.2. Is there some files/linkes that need to be purged to force curl to use libldap.so.2?

root@box:/proc/sys/fs/binfmt_misc# which curl
/usr/local/bin/curl
root@seedbox:/proc/sys/fs/binfmt_misc# ldd $(which curl)
        linux-vdso.so.1 (0x00007fff58ff9000)
        libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x000072ddb9946000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000072ddb9600000)
        liblber-2.5.so.0 => not found
        libldap-2.5.so.0 => not found
        libcares.so.2 => /usr/local/lib/libcares.so.2 (0x000072ddb992a000)
        libssl.so.3 => /lib/x86_64-linux-gnu/libssl.so.3 (0x000072ddb987e000)
        libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x000072ddb9000000)
        libnghttp2.so.14 => /lib/x86_64-linux-gnu/libnghttp2.so.14 (0x000072ddb9853000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x000072ddb9837000)
        libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x000072ddb9829000)
        libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x000072ddb9546000)
        libpsl.so.5 => /lib/x86_64-linux-gnu/libpsl.so.5 (0x000072ddb9813000)
        libssh2.so.1 => /lib/x86_64-linux-gnu/libssh2.so.1 (0x000072ddb8fb8000)
        /lib64/ld-linux-x86-64.so.2 (0x000072ddb9a4c000)
        libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x000072ddb9523000)
        libunistring.so.5 => /lib/x86_64-linux-gnu/libunistring.so.5 (0x000072ddb8e0b000)
        libidn2.so.0 => /lib/x86_64-linux-gnu/libidn2.so.0 (0x000072ddb8de9000)

Should be correct sources

root@box:/proc/sys/fs/binfmt_misc# cat /etc/apt/sources.list.d/ubuntu.sources
Types: deb
URIs: http://archive.ubuntu.com/ubuntu
Suites: noble noble-updates
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Types: deb
URIs: http://security.ubuntu.com/ubuntu
Suites: noble-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

If related these services wont start right now binfmt-support, Apparmor, snapd, zfs-mount & zfs-zed

Ubuntu Desktop does not respect VPN DNS servers https://askubuntu.com/questions/1566068/ubuntu-desktop-does-not-respect-vpn-dns-servers

On Ubuntu Desktop, in Settings > Network > VPN, I've configured my wireguard VPN tunnel, including desired IPv4 and IPv6 DNS servers.

The tunnel works, but the operating system continues to use the DNS server provided by the DHCP server of the main network interface, not the one configured in wg0. I can observe this in wireguard.

Because of this bug, I am unable to reach interally hosted services using their DNS names.

How do I force Ubuntu to respect VPN mandated DNS server? If I manually query my desired DNS server that lives on the other side of the VPN, it responds correctly so it's not a connectivity issue. It's a typical DNS leak.

I can replicate this behaviour on Ubuntu Desktop 25.10 and 26.04.

Konsole scrollbar color (again) https://askubuntu.com/questions/1566060/konsole-scrollbar-color-again

I just installed Kubuntu 26.04 and, upon switching Konsole color scheme to "black on light yellow" I found out that the scrollbar becomes a garish bright yellow. This rings a bell, I think it happened already around 20.04, but it was fixed and certainly doesn't look like that in 24.04

Good (24.04):

sample with grey scrollbar

Bad (26.04):

sample with yellow scrollbar

Any ideas how to fix it?

After Update from 24.04 to 26.04: how can I configure my terminal to open in the same directory as other open terminals https://askubuntu.com/questions/1566040/after-update-from-24-04-to-26-04-how-can-i-configure-my-terminal-to-open-in-the

After the latest operating system update I realized that my productivity went down as I was unable to configure my shell to open a new tab console in the same directory as the already opened tab.

How to reproduce:

  • Open a terminal (Ctrl Alt T)
  • cd Downloads
  • Open a new terminal (Ctrl Shift T)
  • New tab opens in ~ but in 24.04 the console opened in ~/Downloads

Any idea how I can get the old behaviour after my update?

The graphical UI has a setting "Preserve Working Directory" with available options: Always - Never - Safe, that does not change the behaviour of the terminal. New tabs open always open in the home directory.

My prompt command variable was used in 24.04 and remains unchanged:

 $ echo $PROMPT_COMMAND setLastCommandState;
echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/$HOME/~}\007";setGitPrompt

Thanks

Solution: switching back to gnome-terminal restored the functionality I worked with in 24.04. Thanks for the help nevertheless! Let's see if ptyxis will add this productivity feature in the future. Nevertheless I love the new Ctrl . to open a terminal from a nautilus window in 26.04.

26.04 LTS upgrade https://askubuntu.com/questions/1566029/26-04-lts-upgrade

I'm from India, currently running Ubuntu 24.04.4 LTS. I am excited to upgrade to the newly released 26.04 LTS. However, even today's morning (Apr 25), my software updater couldn't find a newer version to upgrade to. Articles like (https://linuxconfig.org/upgrade-ubuntu-24-04-to-26-04) and (https://linuxize.com/post/how-to-upgrade-to-ubuntu-26-04/) suggest a manual upgrade via the terminal, first upgrading to a non-LTS version (25.10). I am not willing to wait till 26.04.1 LTS release.

How do I upgrade? Please help!

My PC does not power off on shutdown https://askubuntu.com/questions/1566023/my-pc-does-not-power-off-on-shutdown

I have an Ubuntu desktop that does not power all the way down. And i try to edit GRUB and modify GRUB_CMDLINE_LINUX_DEFAULT to be like this

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off"

Then I updated Grub using sudo update-grub, but the problem still persists and the machine is not shutting down.

PC build:

  • Motherboard: Asus TUF GAMING B460M-PLUS (WiFi)

  • CPU: Intel Core i5-10400F CPU @ 2.90GHz

  • GPU: RTX5050

Results of neofetch:

  • OS: Ubuntu 24.04.4 LTS x86_64

  • Kernel: 6.17.0-22-generic

  • Uptime: 18 minutes

  • Packages: 2284 (dpkg), 24 (snap)

  • Shell: bash 5.2.21

  • Resolution: 1920x1080

  • DE: GNOME 46.0

  • WM: Mutter

  • WM Theme: Adwaita

  • Theme: Orchis-Dark [GTK2/3]

  • Icons: Tela-dark [GTK2/3]

  • Terminal: gnome-terminal

  • CPU: Intel i5-10400F (12) @ 4.300GHz

  • GPU: NVIDIA 01:00.0 NVIDIA Corporation Device 2d83

  • Memory: 4135MiB / 32008MiB

Ubuntu 26.04 Desktop Sharing / Remote Login https://askubuntu.com/questions/1565994/ubuntu-26-04-desktop-sharing-remote-login

I wanted to connect to my Hyper-V Ubuntu 26.04 VM.

Fist, I connected from Win 11 by Hyper-V Manager Connection, but that doesn't allow me to copy & paste text between the Windows 11 host and the Ubuntu guest.

So, I enabled Settings -> System -> Remote Desktop -> Desktop Sharing in the guest OS (Ubuntu 26.04).

That worked; however, when the session locked after some time, the remote connection disconnected automatically. I found online I should enable Remote Control. I did so, but I am unable to connect to the VM from RDPMan (The server denied the connection).

Btw, grdctl returns a disabled status, despite the Settings -> System -> Remote Desktop -> Remote Login - Remote Login beign set to enabled

$ sudo grdctl status
[13:35:13:312] [22327:00005737] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate
RDP server certificate is invalid.
Failed to lookup legacy VNC password schema: Failed to execute child process ?dbus-launch? (No such file or directory)
RDP:
    Status: disabled
    Port: 3389
    Authentication methods: credentials
    TLS certificate: 
    TLS fingerprint: (null)
    TLS key: 
    Kerberos keytab: 
    View-only: yes
    Negotiate port: yes
Failed to read credentials: Failed to execute child process “dbus-launch” (No such file or directory).

It's a clean Ubuntu 26.04 installation.

What am I doing wrong?

data recovery software [closed] https://askubuntu.com/questions/1565874/data-recovery-software

Can anyone recommend some good disk data recovery software for Linux? I have a 4 Tb disk that was my primary Ubuntu 22.04 drive about 3/4 full that has a damaged GRUB and wouldn't boot. I spent about 2 weeks trying every repair command line strategy Google could come up with without any success. As a last resort I re-installed Grub from the installation USB. Now it boots but doesn't access any of the 257,410 items that 'properties' describes as unavailable. I presume that means I have overwritten some or all of my root directory. I have a new installation of Ubuntu 24.04 on a different computer with a larger drive so I have a safe place to put any recovered files. My question is how do I get access to those files. All the recovery software that Google comes up with seems to be for Mac and Windows and runs on Mac or Windows. I have 5 different flavors of Linux but no Mac or Windows. Any suggestions would be welcome.

User68187 asked what flavors of Linux. Ubuntu22.04 and 24.04, Mint 22, and LMDE7; all in desktop PC's. LinuxCNC (Debian 14) and BeagleBone black (Debian 12.13),in two dedicated non-PC machine controllers.

@Will: Business and bank records from the 1980s to March of this year (copied forward from DOS and OS/2 originals). Mozilla/Firefox bookmarks from 2006 forward. Lectures, tutorials, music and other interesting stuff.

@will (again)The 22.04 drive was supposed to be my backup but something; my error, expert hack-age or a hardware problem scrambled GRUB when I tried to boot it on on a different desktop. Things went downhill from there. Safe backup is expensive at 3.2Tb and I am on a retired budget.

How to use IBM Aspera Connect with a snap-installed browsers such as Firefox on Ubuntu? https://askubuntu.com/questions/1565697/how-to-use-ibm-aspera-connect-with-a-snap-installed-browsers-such-as-firefox-on

It seems that Aspera Connect does not work with snap-installed browsers tested as of Ubuntu 24.04.

This is notably the case for Ubuntu's default browser, Firefox. And it is also chromium's easiest install method by far.

On the other hand, I managed to use it fine from the exact same version of Firefox downloaded from https://www.firefox.com/en-US/thanks/ and ran as standalone.

Beyond the workaround of just using a non-snap installed browser, is there anything I can do to make it work on snap browsers so I don't have to have many browsers running around?

The break is documented on release notes up to release 4.0.0: https://www.ibm.com/docs/en/aspera-connect/4.0?topic=notes-release-aspera-connect-400

ASCN-1971 - Linux browsers installed using Snap cannot launch Connect.

Later releases don't document it anymore, but I doubt it got fixed, it's likely just an oversight.

While writing this I also noticed that Aspera for desktop, downloadable from: https://ibmaspera.com/help/downloads/desktop does work on snap Firefox for the diagnostics page: https://ibmaspera.com/help/diagnostics Furthermore, https://www.ibm.com/products/aspera/downloads says that Aspera Desktop is replacing Aspera Connect:

IBM Aspera for desktop is replacing IBM Aspera Connect

But unfortunately Aspera Desktop seems to require that the server be new enough, and didn't work on the actual server I'm interested in.

Tested on Firefox 149.0, IBM Aspera Connect browser extension 4.1.1.1, IBM Aspera Client 4.2.19.956, Ubuntu 24.04.

ASPERA on Ubuntu 22.04 LTS - Connectivity issues https://askubuntu.com/questions/1563857/aspera-on-ubuntu-22-04-lts-connectivity-issues

Having issues connecting with ASPERA to NCBI SRA; connection is "timing out". Tried the test connection page that IBM set-up and got the following error. Any suggestions? (Using FF).

Secure Connection Failed

An error occurred during a connection to ibmaspera.com. PR_CONNECT_RESET_ERROR

Error code: PR_CONNECT_RESET_ERROR

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.
Kubuntu 25.10 - Intel MIPI Camera (ipu7) not working on Thinkpad X1 2-in-1 Gen 10 Aura https://askubuntu.com/questions/1559262/kubuntu-25-10-intel-mipi-camera-ipu7-not-working-on-thinkpad-x1-2-in-1-gen-1

Thinkpad does have good long-time support for Linux especially Ubuntu series until it hits the MIPI Intel cameras. Ever since the X1 2-in-1 Gen 10 came out I have been trying to get it work but to no avail. Looks like it has started using ipu7 models and further research shows that it is in fact a set of modules including the regular camera, the IR camera, and the camera's flashlight LED as separate modules. they must be all working and activatable in the meantime for the camera to actual work, otherwise it doesn't show any image or refresh at all. See attached link.

The three devices that must be in working order in the meantime:

The three devices that must be in working order in the meantime

The way I actually found this is in fact from Windows by accident. Last night I found that the camera stopped working even in Windows 11 - with the "Integrated IR Camera" and "Intel (R) Camera Flash LED" with exclamation warning marks. Further research showed that both of them had error code 10 - Device Power Status Failure. After trying different solutions for a couple of hours, I finally figured that the drivers have to be uninstalled when deleting the devices (by checking that extra box), then a reboot will have the correct ones reinstalled. Then everything came back online. Thus it made me think that the modules have to be working in the same way in Linux as well to power up the actual camera.

The system I currently have for Linux is Kubuntu 25.10. Needless to say that it doesn't work at the time as well as iio-sensor-proxy 3.7, however when I did install 24.04 LTS in the past and tried all the online solutions for the past ipu6 models, it seems to recognize the device and gave me a gray screen - which now I have realized that it kind of "worked" by trying to only power up the camera, but not the IR camera or the flash LED. Despite the recent support by Linux 6.17 kernel, this is not sufficient. I wonder if anyone can have a better idea to implement this and make it rain.

How do i make a live ubuntu USB https://askubuntu.com/questions/1533778/how-do-i-make-a-live-ubuntu-usb

I am looking for a simple solution that does not require installing this operating system to my internal drives. I know that there is a feature inside of the installer that allows you to try ubuntu. However, this is not what I wish for as I want the USB stick to behave as a normal built in drive so that I can have persistent storage. that can be used as an alternative to windows 11 as it does not fully support my system due to the silly TPM 2.0 requirement that my PC has not got. As a result it refuses to go past version 22H2. I wish to keep that and only that on my primary drive so that I can still have that as it is untouched. I just want the Ubuntu version of the WindowsToGo scheme that is currently around. Please help me as soon a possible. Thank you for the help if you choose to help me, so thank you. :)

Kernel panic with latest installed kernel on Ubuntu 20.04.5 https://askubuntu.com/questions/1427148/kernel-panic-with-latest-installed-kernel-on-ubuntu-20-04-5

My laptop goes directly into kernel panic at first startup every time I try to start it. Long pressing the power button to shut it down and starting it up again, takes me to the grub menu where I have to select the second latest installed kernel, as the latest one seems broken.

OS Version: Ubuntu 20.04.5 LTS (Focal Fossa)
Kernel Version (Broken): linux-generic 5.15.0-46
Kernel Version (Working): linux-generic 5.15.0-41

I tried following this "tutorial" but with no success. The file "initrd.img-5.15.0-46" didn't exist in my boot directory and the command sudo apt install --reinstall linux-generic failed with the following output and I didn't proceed further:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for linux-generic:amd64

When trying to update my system or execute sudo apt install linux-generic the update/command fails as well with this output.

Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-generic is already the newest version (5.4.0.125.126).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up linux-image-5.4.0-125-generic (5.4.0-125.141) ...
I: /boot/initrd.img.old is now a symlink to initrd.img-5.13.0-52-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.15.0-41-generic
Setting up initramfs-tools (0.136ubuntu6.7) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-5.15.0-46-generic (5.15.0-46.49~20.04.1) ...
Setting up linux-firmware (1.187.33) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-41-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.15.0-41-generic with 1.
dpkg: error processing package linux-firmware (--configure):
 installed linux-firmware package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-generic-hwe-20.04:
 linux-image-generic-hwe-20.04 depends on linux-firmware; however:
  Package linux-firmware is not configured yet.
 
dpkg: error processing package linux-image-generic-hwe-20.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-firmware; however:
  Package linux-firmware is not configured yet.
 
dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 5.4.0.125.126); however:
  Package linux-image-generic is not configured yet.
 
dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuratioNo apport report written because the error message indicates it's a follow-up error from a previous failure.
                                                                                                                                                          No apport report written because the error message indicates it's a follow-up error from a previous failure.
                     No apport report written because MaxReports has already been reached
                                                                                         No apport report written because MaxReports has already been reached
                                                                                                                                                             n of linux-generic-hwe-20.04:
 linux-generic-hwe-20.04 depends on linux-image-generic-hwe-20.04 (= 5.15.0.46.49~20.04.16); however:
  Package linux-image-generic-hwe-20.04 is not configured yet.
 
dpkg: error processing package linux-generic-hwe-20.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for linux-image-5.4.0-125-generic (5.4.0-125.141) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.0-125-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-125-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-125-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-125-generic (--configure):
 installed linux-image-5.4.0-125-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports has already been reached
                                                                    Processing triggers for initramfs-tools (0.136ubuntu6.7) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-41-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.15.0-41-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports has already been reached
                                                                    Processing triggers for linux-image-5.15.0-46-generic (5.15.0-46.49~20.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.15.0-46-generic
 
Kernel preparation unnecessary for this kernel.  Skipping...
 
Building module:
cleaning build area...
make -j12 KERNELRELEASE=5.15.0-46-generic all INCLUDEDIR=/lib/modules/5.15.0-46-generic/build/include KVERSION=5.15.0-46-generic DKMS_BUILD=1...(bad exit status: 2)
ERROR (dkms apport): binary package for evdi: 1.9.1 not found
Error! Bad return status for module build on kernel: 5.15.0-46-generic (x86_64)
Consult /var/lib/dkms/evdi/1.9.1/build/make.log for more information.
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-46-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.15.0-46-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-46-generic (--configure):
 installed linux-image-5.15.0-46-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports has already been reached
                                                                    Errors were encountered while processing:
 linux-firmware
 linux-image-generic-hwe-20.04
 linux-image-generic
 linux-generic
 linux-generic-hwe-20.04
 linux-image-5.4.0-125-generic
 initramfs-tools
 linux-image-5.15.0-46-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have some Linux knowledge, but I never did anything regarding kernels/boot apart from dual-boot setups, so I'm a complete noob regarding kernel problems and fixing them. Does anyone of you have some tips or a solution for my issue?

Edit: As also written in an answer to this comment, the issue seems to be this line in the output in particular:

installed linux-firmware package post-installation script subprocess returned error exit status 1

Which then causes the following processes to fail as well. How can I fix this?

Fix: I think I found a solution on this page. I removed the files of all packages which post install scripts fail. After executing sudo apt update and sudo apt upgrade a last time, the errors disappeared.

Is Ubuntu 22.04 Desktop (Full) Possible in 25G or Lower Hard Disk Space? https://askubuntu.com/questions/1404286/is-ubuntu-22-04-desktop-full-possible-in-25g-or-lower-hard-disk-space

Is it Possible to install Ubuntu 22.04 (Full) in a 25GB Partition or less space?

I tried the Ubuntu Minimal install option in the Installer, but seems like it does not install drivers or work, even though I checked the box in the Installer to install drivers.
So is it possible to install Ubuntu 22.04 (Full) in 25GB Partition or less space?

udisksctl power off wrong disk https://askubuntu.com/questions/1356502/udisksctl-power-off-wrong-disk

I try to safely eject my external disk with the following 2 commands:

udisksctl unmount -b /dev/sdc1
udisksctl power-off -b /dev/sdc

The partition is correctly unmounted, but the second command gives the following error:

Error powering off drive: The drive in use: Device /dev/sdb1 is mounted (udisks-error-quark, 14)

Yes, I have another partition on another drive mounted /dev/sdb. But I want to power-off /dev/sdc. How is this supposed to happen? How can I remove safely sdc?

Ubuntu 20.04

(base) home@home:~$ lsblk --topology --exclude 7
NAME                      ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED       RQ-SIZE  RA WSAME
sda                               0   4096      0    4096     512    1 mq-deadline      64 128    0B
├─sda1                            0   4096      0    4096     512    1 mq-deadline      64 128    0B
├─sda2                            0   4096      0    4096     512    1 mq-deadline      64 128    0B
└─sda3                            0   4096      0    4096     512    1 mq-deadline      64 128    0B
  └─ubuntu--vg-ubuntu--lv         0   4096      0    4096     512    1                 128 128    0B
sdb                               0   4096      0    4096     512    1 mq-deadline       2 128    0B
└─sdb1                            0   4096      0    4096     512    1 mq-deadline       2 128    0B
sdc                               0   4096      0    4096     512    1 mq-deadline       2 128    0B
├─sdc1                         3072   4096      0    4096     512    1 mq-deadline       2 128    0B
└─sdc2                            0   4096      0    4096     512    1 mq-deadline       2 128    0B
sr0                               0    512      0     512     512    1 mq-deadline      64 128    0B

Thanks

No such file or directory - bash https://askubuntu.com/questions/1144290/no-such-file-or-directory-bash

I am running out of ideas (and sources of ideas) on this one. I am getting a file-path from Audacious, and trying to get album art from the directory referenced. The info provided is correct, and works in terminal.

Things I have tried:

  1. Redirected variable to a file, and looked with hexedit for odd characters.

  2. Checked script for odd characters the same way.

  3. Executed the script with /bin/bash directly.

  4. Made a new script with only the non-functional code.

  5. Because the path returned is relative [~/Music/Eagles/Desperado] have tried it as [/home/freebird/Music/Eagles/Desperado].

  6. Because [Music] is a soft link to another drive have tried it as [/mnt/data/Music/Eagles/Desperado]

  7. Have been using the Eagles because I didn't want to deal with [~/Music/Alice Cooper/School's Out] until I had the simpler case working!

  8. IT does not have any CR's or other extraneous characters from editing on Windows or elsewhere - haven't used Windows for anything but Freecell and Spider Solitaire since 2007.

  9. Nothing so far can resolve the resulting path into usability from inside the script, ALL work from the terminal (including cd).

Here is the actual error message from a recent try:

freebird@nest:~$ ~/check.sh
/home/freebird/check.sh: line 8: cd: ~/Music/Eagles/Desperado: No such file or directory

Any further suspects for me?

Here is the check script for testing:

#!/bin/bash
file_path=`audtool --current-song-tuple-data file-path`
echo > test2 ${file_path}
#${file-path}="/mnt/data/""${file_path:2}"
echo > testpath ${file_path}
cd "${file_path}"
#cd -P "${file-path}"
pwd
exit 1
if [[ ! -e "folder.jpg" ]];   # if no art work found
    then
    cp ~/Work/headphone.png /tmp/cover.png # put in placeholder
    echo "Placeholder"
 else
    convert "${file_path}""/folder.jpg" -resize 120x120 /tmp/cover.png # ready for showing
    echo "found cover"
 fi

It contains various 'test' additions still, the equivalent of scattered printf() to see what's going on :)

new version of testing script:

#!/bin/bash
file_path=`audtool --current-song-tuple-data file-path`
file_path=$(eval echo $file_path)
echo > test2 ${file_path}
${file-path}="$HOME"${file_path:1}
echo > testpath ${file_path}
cd ${file-path}
#cd -P "${file-path}"
pwd
exit 1
if [[ ! -e "folder.jpg" ]];   # if no art work found
    then
    cp ~/Work/headphone.png /tmp/cover.png # put in placeholder
    echo "Placeholder"
 else
    convert "${file_path}""/folder.jpg" -resize 120x120 /tmp/cover.png # ready for showing
    echo "found cover"
 fi

New error messages:

freebird@nest:~$ ~/check.sh
/home/freebird/check.sh: line 5: path=/home/freebirdhome/freebird/Music/Eagles/Desperado: No such file or directory
/home/freebird/check.sh: line 7: cd: path: No such file or directory
/home/freebird
freebird@nest:~$ 
Ubuntu 14.04 VM kernel panics once every ~5-9 days on Hyper-V https://askubuntu.com/questions/680565/ubuntu-14-04-vm-kernel-panics-once-every-5-9-days-on-hyper-v

I have an x64 Ubuntu 14.04.3 LTS virtual machine running the hardware monitoring and status software Nagios. The VM seems to be kernel panicking once every 5-9 days. I am unable to pin down the cause.

I am currently the only person that uses Nagios on this machine. When it kernel panics, it's not being used by anybody (and to my knowledge, not doing much else besides receiving monitoring updates from other computers). Additionally, the VM is only available on the local network, and I've regularly kept everything up-to-date using sudo apt-get update && sudo apt-get upgrade.

The following boot messages show the VM kernel panics. Every kernel panic seems to be a slight variation of one of these two boot messages:

[419646.634751] PGD 0
[419646.637067] Oops: 0000 [#1] SMP
[419646.637067] Modules linked in: crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev hid_generic aesni_intel aes_x86_64 lrw gf128mul glue
_helper ablk_helper cryptd hid_hyperv serio_raw hyperv_keyboard hid i2c_piix4 mac_hid hyperv_fb lp parport hv_netvsc hv_storvsc hv_utils psmouse
 floppy hv_vmbus pata_acpi
[419646.637067] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-32-generic #57-Ubuntu
[419646.637067] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006  05/23/2012
[419646.637067] task: ffffffff81c15480 ti: ffffffff81c00000 task.ti: ffffffff81c00000
[419646.637067] RIP: 0010:[<ffffffff81492c9e>]  [<ffffffff81492c9e>] dev_get_drvdata+0xe/0x30
[419646.637067] RSP: 0018:ffff88003de03d70  EFLAGS: 00010002
[419646.637067] RAX: ffff880035a4eb00 RBX: ffff880036d49dc0 RCX: 0000000000000000
[419646.637067] RDX: 000000000000002a RSI: 0000000000000002 RDI: 0000000000000020
[419646.637067] RBP: ffff88003de03d70 R08: 0000000000000001 R09: ffff88003d400000
[419646.637067] R10: 0000000000000009 R11: 000000000000ba9b R12: ffff880036960d30
[419646.637067] R13: ffff880035a4f800 R14: 0000000000000001 R15: ffff880036960c00
[419646.637067] FS:  00007ff3a4dff700(0000) GS:ffff88003de00000(0000) knlGS:0000000000000000
[419646.637067] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[419646.637067] CR2: 0000000000000028 CR3: 0000000039204000 CR4: 00000000000406f0
[419646.637067] Stack:
[419646.637067]  ffff88003de03e98 ffffffffa0017917 ffff88003de14440 ffff88003de14440
[419646.637067]  ffff88003a95e5fc 0000000000000000 ffff88003de03e44 ffffffff81098015
[419646.637067]  ffff88003a95dfc0 0000000000000000 ffffffff81098059 ffff880036c07000
[419646.637067] Call Trace:
[419646.637067]  <IRQ> 
[419646.637067]  [<ffffffffa0017917>] storvsc_on_channel_callback+0x1b7/0x83c [hv_storvsc]
[419646.637067]  [<ffffffff81098015>] ? check_preempt_curr+0x75/0x90
[419646.637067]  [<ffffffff81098059>] ? ttwu_do_wakeup+0x19/0xc0
[419646.637067]  [<ffffffff8109a6da>] ? try_to_wake_up+0x1fa/0x2c0
[419646.637067]  [<ffffffffa00098c9>] vmbus_on_event+0x109/0x1b0 [hv_vmbus]
[419646.637067]  [<ffffffff8106c6f6>] tasklet_action+0xf6/0x100
[419646.637067]  [<ffffffff8106cafc>] __do_softirq+0xec/0x2c0
[419646.637067]  [<ffffffff8106d045>] irq_exit+0x105/0x110
[419646.637067]  [<ffffffff8103f1a7>] hyperv_vector_handler+0x47/0x60
[419646.637067]  [<ffffffff8172e2ad>] hyperv_callback_vector+0x6d/0x80
[419646.637067]  <EOI> 
[419646.637067]  [<ffffffff8101b773>] ? native_sched_clock+0x13/0x80
[419646.637067]  [<ffffffff8104f596>] ? native_safe_halt+0x6/0x10
[419646.637067]  [<ffffffff8101c60f>] default_idle+0x1f/0xc0
[419646.637067]  [<ffffffff8101ced6>] arch_cpu_idle+0x26/0x30
[419646.637067]  [<ffffffff810bec65>] cpu_startup_entry+0xc5/0x290
[419646.637067]  [<ffffffff8170a187>] rest_init+0x77/0x80
[419646.637067]  [<ffffffff81d35f70>] start_kernel+0x438/0x443
[419646.637067]  [<ffffffff81d35941>] ? repair_env_string+0x5c/0x5c
[419646.637067]  [<ffffffff81d35120>] ? early_idt_handlers+0x120/0x120
[419646.637067]  [<ffffffff81d355ee>] x86_64_start_reservations+0x2a/0x2c
[419646.637067]  [<ffffffff81d35733>] x86_64_start_kernel+0x143/0x152
[419646.637067] Code: 48 c7 c6 98 45 ad 81 48 c7 c7 18 70 d0 81 48 8b 10 31 c0 e8 c5 48 ef ff eb 80 0f 1f 00 66 66 66 66 66 90 55 48 85 ff 48 89 e5
 74 12 <48> 8b 47 08 48 85 c0 74 09 48 8b b0 98 00 00 00 5d c3 31 c0 5d
[419646.637067] RIP  [<ffffffff81492c9e>] dev_get_drvdata+0xe/0x30
[419646.637067]  RSP <ffff88003de03d70>
[419646.637067]  CR2: 0000000000000028
[419646.637067] ---[ end trace bbe168871ddbd6db ]---
[419646.637067] Kernel panic - not syncing: Fatal exception in interrupt
[374230.946314] PGD 3c9b5067 PUD 3699a067 PMD 0
[374230.946570] Oops: 0000 [#1] SMP
[374230.946917] Modules linked in: crct10dif_pclmul hid_generic joydev crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue
_helper ablk_helper cryptd i2c_piix4 hid_hyperv hid hyperv_fb hyperv_keyboard serio_raw mac_hid lp parport hv_netvsc hv_utils hv_storvsc psmouse
 floppy hv_vmbus pata_acpi
[374230.947096] CPU: 0 PID: 38548 Comm: check_snmp_prin Not tainted 3.13.0-32-generic #57-Ubuntu
[374230.947096] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006  05/23/2012
[374230.947096] task: ffff88003b2317f0 ti: ffff88003b530000 task.ti: ffff88003b530000
[374230.947096] RIP: 0010:[<ffffffffa002f8f6>]  [<ffffffffa002f8f6>] storvsc_on_channel_callback+0x196/0x83c [hv_storvsc]
[374230.947096] RSP: 0000:ffff88003de03d80  EFLAGS: 00010046
[374230.947096] RAX: 0000000000000000 RBX: ffff88003aad4540 RCX: 0000000000000000
[374230.947096] RDX: 000000000000002a RSI: 0000000000000002 RDI: ffff880036965c20
[374230.947096] RBP: ffff88003de03e98 R08: 0000000000000001 R09: ffff88003d400000
[374230.947096] R10: 0000000000000009 R11: 0000000000000000 R12: ffff880036962930
[374230.947096] R13: ffff88003b29f700 R14: 0000000000000001 R15: ffff880036962800
[374230.947096] FS:  00007fb4502ae740(0000) GS:ffff88003de00000(0000) knlGS:0000000000000000
[374230.947096] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[374230.947096] CR2: 0000000000000098 CR3: 000000003ab03000 CR4: 00000000000406f0
[374230.947096] Stack:
[374230.947096]  ffff88003d39b048 ffff88003d399858 ffff88003d39afe0 ffff88003de14440
[374230.947096]  ffff88003de03e44 ffff88003de03df0 ffffffff810a3eec 000000003de03de0
[374230.947096]  000000000000223f ffff880036961400 ffff880036965c20 ffff88003de14440
[374230.947096] Call Trace:
[374230.947096]  <IRQ> 
[374230.947096]  [<ffffffff810a3eec>] ? check_preempt_wakeup+0x17c/0x280
[374230.947096]  [<ffffffff81098025>] ? check_preempt_curr+0x85/0x90
[374230.947096]  [<ffffffffa00098c9>] vmbus_on_event+0x109/0x1b0 [hv_vmbus]
[374230.947096]  [<ffffffff8106c6f6>] tasklet_action+0xf6/0x100
[374230.947096]  [<ffffffff8106cafc>] __do_softirq+0xec/0x2c0
[374230.947096]  [<ffffffff8106d045>] irq_exit+0x105/0x110
[374230.947096]  [<ffffffff8103f1a7>] hyperv_vector_handler+0x47/0x60
[374230.947096]  [<ffffffff8172e2ad>] hyperv_callback_vector+0x6d/0x80
[374230.947096]  <EOI> 
[374230.947096]  [<ffffffff8136d055>] ? copy_page_rep+0x5/0x10
[374230.947096]  [<ffffffff811767e1>] ? do_wp_page+0x121/0x7c0
[374230.947096]  [<ffffffff81178f0c>] handle_mm_fault+0x65c/0xf00
[374230.947096]  [<ffffffff810a3031>] ? update_cfs_shares+0xb1/0x100
[374230.947096]  [<ffffffff8109ec18>] ? __enqueue_entity+0x78/0x80
[374230.947096]  [<ffffffff81727be4>] __do_page_fault+0x184/0x560
[374230.947096]  [<ffffffff8101b7e9>] ? sched_clock+0x9/0x10
[374230.947096]  [<ffffffff8109d1ad>] ? sched_clock_local+0x1d/0x80
[374230.947096]  [<ffffffff8111155c>] ? acct_account_cputime+0x1c/0x20
[374230.947096]  [<ffffffff8109d7db>] ? account_user_time+0x8b/0xa0
[374230.947096]  [<ffffffff8109ddf4>] ? vtime_account_user+0x54/0x60
[374230.947096]  [<ffffffff81727fda>] do_page_fault+0x1a/0x70
[374230.947096]  [<ffffffff81724448>] page_fault+0x28/0x30
[374230.947096] Code: ff ff 31 c0 48 c7 c6 40 01 03 a0 e8 85 ff 45 e1 80 7d 9f 02 0f 84 9b 02 00 00 8b 45 a8 4c 8b 6b 10 89 83 78 01 00 00 49 8b
 45 00 <48> 8b 88 98 00 00 00 48 8b 00 48 8b b8 e8 06 00 00 48 89 8d 20
[374230.947096] RIP  [<ffffffffa002f8f6>] storvsc_on_channel_callback+0x196/0x83c [hv_storvsc]
[374230.947096]  RSP <ffff88003de03d80>
[374230.947096]  CR2: 0000000000000098
[374230.947096] ---[ end trace e150a651434d4608 ]---
[374230.947096] Kernel panic - not syncing: Fatal exception in interrupt

The VM runs on Hyper-V on a computer with Windows Server 2012 Standard installed. However, the server runs 6 other VMs without incident (including Ubuntu 12.04 and CentOS 6 VMs).

Is it possible that Hyper-V integration services or drivers are at fault? I keep seeing hv_storvsc and references to Hyper-V in the kernel panics and am wondering if the Hyper-V drivers in 14.04 are subpar or have known issues.

The VM has been in operation for about 1.5 years, but these problems have only started surfacing a few months ago, if I recall correctly.

dditional information about the virtual machine:

  • 1 virtual processor assigned
  • 1024MB RAM
  • Hard drive on IDE Controller 0
  • Virtual hard disk resides on the server's C:\ drive
  • All integration services are enabled for the VM, including: operating system shutdown, time synchronization, data exchange, heartbeat, backup (volume snapshot)
  • Replication is enabled to a server in the same rack with identical hardware

Additional information about the host server that runs Hyper-V:

  • Powershell script runs every night that runs Windows Backup on all VMs to a local external hard drive
  • Motherboard: http://www.newegg.com/Product/Product.aspx?Item=N82E16813128577
  • CPU: AMD A8-5600K quad-core 3.6GHz CPU
  • RAM: 32GB (4x 8GB) CORSAIR Vengeance DDR3 1866
  • All RAM has been tested thoroughly with memtest86+
  • System has been stress tested with Prime95
  • System has been in operation for about 2.5 years
  • 2x 1TB HDs set up in RAID1 using the motherboard's onboard RAID controller
  • Raid software has not given any indication of problems with the array

Any help would be appreciated. I've been Googling around for days and haven't come up with any reasonable theories.

Have grub2 boot 32 and 64 bit Ubuntu https://askubuntu.com/questions/97641/have-grub2-boot-32-and-64-bit-ubuntu

I just installed a system like this:

ubuntu@ubuntu:~$ ls -l /dev/disk/by-label/
total 0
lrwxrwxrwx 1 root root 10 2012-01-22 18:49 Boot -> ../../sda1
lrwxrwxrwx 1 root root 10 2012-01-22 18:49 ubuntu32 -> ../../sda2
lrwxrwxrwx 1 root root 10 2012-01-22 18:28 ubuntu64 -> ../../sda3
lrwxrwxrwx 1 root root 10 2012-01-22 18:49 Home -> ../../sda5

ubuntu@ubuntu:~$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2012-01-22 20:55 3582d70f-f4a5-484c-b14c-45cd740346b9 -> ../../sda1
lrwxrwxrwx 1 root root 10 2012-01-22 20:55 741182a8-3f15-4dfd-994d-654c8a57a9e4 -> ../../sda2
lrwxrwxrwx 1 root root 10 2012-01-22 20:55 1c415472-a770-4d76-be9f-27b8c1408e2a -> ../../sda3
lrwxrwxrwx 1 root root 10 2012-01-22 20:55 3515d523-72a2-4e04-b7da-cb6a1fd572ef -> ../../sda5
lrwxrwxrwx 1 root root 10 2012-01-22 20:55 f1f1cd7e-30cb-44e7-9ef6-986a589e0045 -> ../../sda6

I need 32 and 64 bit separate so I can test driver performance on each, the Home directory is shared and each version of ubuntu is mounted as /ubuntuXX under the other version. /boot also points to /dev/sda1 on both.

When I run sudo update-grub from ubuntu32 it runs fine but I get an error booting ubuntu64. init fails and I'm assuming it is because of the wrong bit type. Shouldn't grub's OS probe be bit-aware? How can I get these two to boot properly.

I ran grub-customizer from a live disk, chose /dev/sda3 as root, selected all partitions in the second step, and then removed all entires except for OS-Prober and memtest. What resulted is the attached grub.cfg. It now lists /dev/sda2 as the only OS option. The grub.cfg has the root UUID set to /boot for every entry.

grub.cfg: http://pastebin.com/Dkdxian4

me@GAMMA:~$ cat /boot/grub/grub.cfg 
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
 
### BEGIN /etc/grub.d/10_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi
 
function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
 
function recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
 
function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}
 
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 1c415472-a770-4d76-be9f-27b8c1408e2a
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  insmod part_msdos
  insmod ext2
  set root='(hd0,msdos1)'
  search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
  set locale_dir=($root)/grub/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/10_header ###
 
### BEGIN /etc/grub.d/11_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
  clear
fi
### END /etc/grub.d/11_debian_theme ###
 
### BEGIN /etc/grub.d/12_os-prober ###
menuentry "Ubuntu 11.10 (11.10) (on /dev/sda2)" --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
    linux /vmlinuz-3.0.0-12-generic root=/dev/sda2
    initrd /initrd.img-3.0.0-12-generic
}
menuentry "Ubuntu 11.10 (11.10) (on /dev/sda2)" --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
    linux /vmlinuz-3.0.0-15-generic root=/dev/sda2
    initrd /initrd.img-3.0.0-15-generic
}
### END /etc/grub.d/12_os-prober ###
 
### BEGIN /etc/grub.d/13_memtest86+ ###
menuentry "Memory test (memtest86+)" {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
    linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
    linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/13_memtest86+ ###

fstab (both): http://pastebin.com/3sUabYRY

ubuntu@ubuntu:~$ cat /ubuntu32/etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda2 during installation
UUID=741182a8-3f15-4dfd-994d-654c8a57a9e4 /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=3582d70f-f4a5-484c-b14c-45cd740346b9 /boot           ext2    defaults        0       2
# /home was on /dev/sda5 during installation
UUID=3515d523-72a2-4e04-b7da-cb6a1fd572ef /home           ext4    defaults        0       2
# /ubuntu64 was on /dev/sda3 during installation
UUID=1c415472-a770-4d76-be9f-27b8c1408e2a /ubuntu64       ext4    defaults        0       2
# swap was on /dev/sda6 during installation
UUID=f1f1cd7e-30cb-44e7-9ef6-986a589e0045 none            swap    sw              0       0
 
ubuntu@ubuntu:~$ cat /ubuntu64/etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda3 during installation
UUID=1c415472-a770-4d76-be9f-27b8c1408e2a /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=3582d70f-f4a5-484c-b14c-45cd740346b9 /boot           ext2    defaults        0       2
# /home was on /dev/sda5 during installation
UUID=3515d523-72a2-4e04-b7da-cb6a1fd572ef /home           ext4    defaults        0       2
# /ubuntu32 was on /dev/sda2 during installation
UUID=741182a8-3f15-4dfd-994d-654c8a57a9e4 /ubuntu32       ext4    defaults        0       2
# swap was on /dev/sda6 during installation
UUID=f1f1cd7e-30cb-44e7-9ef6-986a589e0045 none            swap    sw              0       0``none

I know grub2 is all auto-generated and menus and jazz, but how do I just nuke all that and manually add entires (I'm not keeping this install long so there's no worry about kernel updates)

I took a shot at blindly replicating the /dev/sda2 entry but adjusting it for /dev/sda3 however it didn't go well. I did however, manage to get the same error as my first attempt (it's the line right before the kernel panic, run-init)

(null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom: ... done.
[    3.402989] request_module: runaway loop modprobe binfmt-464c
run-init: /sbin/init: Exec format error
[    3.406303] Kernel panic - not syncing: Attempted to kill init!
[    3.406394] Pid: 1, comm: run-init Not tainted 3.0.0-15-generic #25-Ubuntu
[    3.408290] [<c151a922>] ? printk+0x2d/0x2f
[    3.408338] [<c151a800>] panic+0x5c/0x151
[    3.408388] [<c104b564>] forget_original_parent+0x1e4/0x1f0
[    3.408440] [<c10d3a48>] ? perf_cgroup_attach_task+0x20/0x20
[    3.408489] [<c104b583>] exit_notify+0x13/0x140
[    3.408536] [<c104bd8d>] do_exit+0x1ad/0x3a8
[    3.408585] [<c1313850>] ? tty_write+0x228/0x228
[    3.408632] [<c104c098>] sys_exit+0x18/0x28
[    3.408680] [<c152e424>] syscall_call+0x7/0xb

I'm beginning to think it has to do with the kernel images that are in the /boot directory.

OK, now I'm certain that it is due to the fact that one partition is 32-bit and one is 64-bit.

updated part of grub.cfg: http://pastebin.com/DvfBhrBF

### BEGIN /etc/grub.d/12_os-prober ###
menuentry "Ubuntu 11.10 (11.10) (on /dev/sda2)" --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
    linux /vmlinuz-3.0.0-15-generic root=/dev/sda2
    initrd /initrd.img-3.0.0-15-generic
}
 
menuentry "Ubuntu 11.10 (11.10) (on /dev/sda3)" --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set=root 3582d70f-f4a5-484c-b14c-45cd740346b9
    linux /vmlinuz-3.0.0-15-generic root=/dev/sda3
    initrd /initrd.img-3.0.0-15-generic
}
### END /etc/grub.d/12_os-prober ###

Figure 1: excerpt from /boot/grub/grub.cfg:

linux /vmlinuz-3.0.0-12-generic root=/dev/sda2
initrd /initrd.img-3.0.0-12-generic

Figure 2: Listings of /ubuntu64/vm* and /ubuntu32/vm*

me@GAMMA:~$ ls -l /vm*
lrwxrwxrwx 1 root root 29 2012-01-23 20:41 /vmlinuz -> boot/vmlinuz-3.0.0-15-generic
lrwxrwxrwx 1 root root 29 2012-01-22 13:05 /vmlinuz.old -> boot/vmlinuz-3.0.0-12-generic
me@GAMMA:~$ ls -l /ubuntu32/vm*
lrwxrwxrwx 1 root root 29 2012-01-22 12:41 /ubuntu32/vmlinuz -> boot/vmlinuz-3.0.0-15-generic
lrwxrwxrwx 1 root root 29 2012-01-22 12:22 /ubuntu32/vmlinuz.old -> boot/vmlinuz-3.0.0-12-generic

Figure 3: Magic File Type of /boot/vmlinuz-3.0.0-12-generic

/boot/vmlinuz-3.0.0-12-generic: Linux kernel x86 boot executable bzImage, version 3.0.0-12-generic (buildd@creste, RO-rootFS, root_dev 0x801, swap_dev 0x4, Normal VGA
/boot/vmlinuz-3.0.0-15-generic: Linux kernel x86 boot executable bzImage, version 3.0.0-15-generic (buildd@creste, RO-rootFS, root_dev 0x801, swap_dev 0x4, Normal VGA

Now here's the real kicker:

me@GAMMA:~$ sudo find / -name "vmlinuz*"
/boot/vmlinuz-3.0.0-12-generic
/boot/vmlinuz-3.0.0-15-generic
/vmlinuz.old
/vmlinuz
/ubuntu32/vmlinuz.old
/ubuntu32/vmlinuz

That's the only kernel on my system! How is that even possible? I'm running 64-bit right now (/dev/sda3 is / and uname reports 64-bit)!

I checked the package contents on packages.ubuntu.com and the am64 version of linux-image-3.0.0.15-generic lists /boot/vmlinuz-3.0.0-15-generic as a file, so I ran the following:

me@GAMMA:~$ sudo openssl dgst -md5 /boot/vmlinuz-3.0.0-15-generic > ~/3.0.0.15x86
me@GAMMA:~$ sudo apt-get install --reinstall linux-image-3.0.0-15-generic
(Output Omitted)
me@GAMMA:~$ sudo openssl dgst -md5 /boot/vmlinuz-3.0.0-15-generic
MD5(/boot/vmlinuz-3.0.0-15-generic)= f56839a4642eb97e06e5efb0bc74f4dc
me@GAMMA:~$ cat ~/3.0.0.15x86 
MD5(/boot/vmlinuz-3.0.0-15-generic)= f56839a4642eb97e06e5efb0bc74f4dc
me@GAMMA:~$ sudo openssl dgst -md5 /boot/vmlinuz-3.0.0-15-generic > ~/3.0.0.15x86

So the Linux kernel acts very much like the Mach Kernel in OS X in that it is a 32-bit executable that switch to 64-bit mode when needed. The question then is why am I getting an error about "Exec format error"?

This Post however seems to indicate that the runaway loop modprobe from the Kernel Panic indicates that this is indeed a 32/64 bit issue. Grub must have some way of telling the kernel the bitlength, maybe it is in an associated file in /boot, looking into that tomorrow.

quick update:

The 32-bit and 64-bit kernels hash differently, but file reports them both to be x86.

< MD5(/boot/vmlinuz-3.0.0-15-generic)= f56839a4642eb97e06e5efb0bc74f4dc
 ---
> MD5(/boot/vmlinuz-3.0.0-15-generic)= cee6cd7db9016ee8531be92504ac802b

So I need to determine how to install the kernel to somewhere other than /boot so that the two kernels don't clobber each other...