update asking if iperf3 should be run as a demon at startup? https://askubuntu.com/questions/1563117/update-asking-if-iperf3-should-be-run-as-a-demon-at-startup

I'm running standard 'Ubuntu 25.10 Desktop' fully updated.

I just received an update for 'iperf3' (something i never heard of) and it asked if I wanted to run it as a demon at startup. As a fool I just clicked the tickbox and carried on.

From what I now understand, 'iperf3' is for performance testing of network connections. Is it necessary to run as a demon for a basic user. ie: someone who just checks email and surfs the web?

If not, how do i disable it from being run at startup? Is it part of standard Ubuntu or did I somehow install it inadvertently in the past?

Update: I've gone and checked 4 other installs I have access to and 3/4 have iperf3 installed but not active [service --status-all] shows them existing but they have a '-' in front of them. So I'm guessing it is a standard issue service.

As for stopping it run as a demon at startup, I used 'synaptic package manager' to do a 'complete removal' and then reinstalled it.

It is a bit of a brute force method, adjusting a setting would have been better & I still would like to know how.

Thanks.

BAR Allocation Failed & IOMMU Conflicts: Dual GPU (RTX 5060 + 4060) on Ryzen 5800X/B550 - "No Space" Errors https://askubuntu.com/questions/1563112/bar-allocation-failed-iommu-conflicts-dual-gpu-rtx-5060-4060-on-ryzen-580

I am hitting a wall trying to configure a dual GPU setup on a B550/Ryzen platform running Ubuntu. I am facing a persistent Memory Mapped I/O (MMIO) resource allocation issue where the kernel cannot assign BAR addresses for the second GPU, leading to can't assign; no space errors.

Hardware Specs:

  • CPU: AMD Ryzen 7 5800X

  • Mobo: B550 Chipset [INSERT YOUR MOTHERBOARD MODEL HERE]

  • GPU 1: NVIDIA RTX 4060

  • GPU 2: NVIDIA RTX 5060 (New gen)

  • PSU: 850W

  • OS: Ubuntu (Kernel 6.x generic)

  • Driver: Manual install of NVIDIA-Linux-x86_64-580.126.09.run (Required for 5060 support)

The Problem: When booting with default BIOS settings, only one GPU is enumerated correctly. The second GPU fails with BAR allocation errors in dmesg. When I attempt to fix this by enabling "Above 4G Decoding" in BIOS, the system fails to mount the NVMe drive or panics during boot unless I use specific kernel parameters, and even then, I lose the proprietary driver binding.

Logs & Symptoms:

1. The BAR Error (dmesg output): Without 4G decoding, the kernel clearly sees the device but cannot map the memory:

Bash

[ 0.666193] pci 0000:07:00.0: BAR 1 [mem size 0x10000000 64bit pref]: can't assign; no space
[ 0.666195] pci 0000:07:00.0: BAR 1 [mem size 0x10000000 64bit pref]: failed to assign
[ 0.666196] pci 0000:07:00.0: VF BAR 2 [mem size 0x10000000 64bit pref]: can't assign; no space
NVRM: BAR1 is 0M @ 0x0 (PCI:0000:04:00.0)

2. The IOMMU/Disk Conflict: If I Enable Above 4G Decoding and Disable CSM (UEFI only), the boot process hangs with filesystem errors, losing access to the NVMe block devices:

Bash

/var/lib/snapd/snaps/firefox_2356.snap: Can't lookup blockdev
[FAILED] Failed to mount Mount unit for firefox.
[FAILED] Failed to mount Mount unit for snapd.

What I have tried so far:

  1. BIOS Settings:

    • Above 4G Decoding: Enabled

    • Re-Size BAR: Auto/Enabled

    • CSM: Disabled

  2. Kernel Parameters:

    • Tried pci=realloc: Did not resolve the no space error.

    • Tried iommu=soft: This allows the system to boot with "Above 4G Decoding" enabled (bypassing the blockdev error), BUT nvidia-smi fails to detect devices, or the system falls back to llvmpipe (software rendering) with a zoomed-in resolution.

  3. Display Manager:

    • Disabled Wayland in /etc/gdm3/custom.conf (WaylandEnable=false).
  4. Driver Installation:

    • Purged all apt nvidia packages.

    • Running the .run file for driver 580.126.09.

    • Installation completes successfully in Recovery Mode (Root Shell), but upon rebooting with iommu=soft, the driver doesn't seem to bind correctly to the cards.

The Question: How can I properly expose the BAR address space for both cards on a B550/Ryzen platform without breaking the NVMe/IOMMU controller? Is there a specific combination of GRUB parameters (e.g., pci=noalloc, iommu=pt, amd_iommu=on) that allows 4G decoding to coexist with a functional NVIDIA driver on this chipset?

Any insights on how to escape this loop would be appreciated.

Smartctl: how to output SSD temp number only? https://askubuntu.com/questions/1563111/smartctl-how-to-output-ssd-temp-number-only

Using Xubuntu 24.04 with Samsung 860 evo 1TB SSD on desktop PC. Here is the smartctl command I must use to find the SSD temperature (with output):

marsdenf@marsdenf-Desktop:~$ sudo smartctl -a /dev/sda | grep -i temp
190 Airflow_Temperature_Cel 0x0032   068   052   000    Old_age   Always       -       32

The temperature is the last number in the output ("32"). Is there a way to have the terminal output only the temperature number with nothing else before it? I want to use a command in genmon to show only the number. (Apparently hddtemp is not available for Xubuntu 24.04.) Thanks in advance.

How can I see data output from USB port in Ubuntu? https://askubuntu.com/questions/1563110/how-can-i-see-data-output-from-usb-port-in-ubuntu

Is it possible to log bits/bytes/characters, whatever format of data output through USB in Ubuntu?

I mean exact data which are transferred through USB port of a computer rather than connected device name, time and other metadata.

Restore point at Ubuntu, like in windows https://askubuntu.com/questions/1563094/restore-point-at-ubuntu-like-in-windows

Is it possible to make restore point at Ubuntu like in windows?

If is it, how to make restore point and how to restore it?

I am using Ubuntu server (no GUI).

Screen video/audio capture app for Ubuntu 24.04 https://askubuntu.com/questions/1563067/screen-video-audio-capture-app-for-ubuntu-24-04

I'm looking for a GUI screen video with audio capture app for Ubuntu 24.04. Search on Ask Ubuntu pulls up stuff 10-15 years old with things no longer in existence, the same with search engines.

Ubuntu Software only has recording junk. Most do not even open, have no GUI, or open and lock up like they're not working with Wayland.

That print screen thing only records video. no audio.

VLC says it can capture the desktop, but has no record button or way to select.

I can use my laptop's HDMI output to record screen to my DVD recorder, bring the burned DVD to the laptop, and use Handbrake to make mp4 recordings. It seems there should be something more user friendly.

I tried OBS Studio and got this:

enter image description here

Failed to fetch linux-firmware 503 Service Unavailable [IP: 91.189.92.24 80] https://askubuntu.com/questions/1563064/failed-to-fetch-linux-firmware-503-service-unavailable-ip-91-189-92-24-80

While running sudo apt upgrade on a server on Ubuntu 24.04.3, I cannot upgrade the linux-firmware package.

I have tried several times since yesterday morning.

The dialogue is as follows:

Do you want to continue? [Y/n] Y
Ign:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.22
Ign:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.22
Ign:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.22
Err:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.22
  503  Service Unavailable [IP: 91.189.92.24 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_20240318.git3b128b60-0ubuntu2.22_amd64.deb  503  Service Unavailable [IP: 91.189.92.24 80]

I have seen similar messages from 5th September 2025. Is there really an issue with the repository now, or is this something on my side. I was able to install the other updates yesterday without any issue.

I never experienced this issue in 12 years working with Ubuntu.

Update 21 Jan 2026:
I tried again this morning and I still received the same result, however I then changed http into https in my ubuntu.sources file. I then run apt update followed by apt upgrade and the linux-firmware was installed right away.

I still don't understand why this worked as originally all the other updates were installed with the URL as http.

Does anyone else have trouble with logitech universal receiver devices? https://askubuntu.com/questions/1563063/does-anyone-else-have-trouble-with-logitech-universal-receiver-devices

Running Ubuntu 24.04.3 LTS, using a Logitech M325S mouse and a K750 keyboard. Most of the time they work fine, but they go through periods where they are very slow, or jerky, or miss signals altogether. I am running Solaar (1.1.11+dfsg+2) to manage Logitech devices, is there something else I can do that with? Anyone else having any trouble; if not, are they running something besides Solaar?

Output of fwupdmgr command:

HP HP EliteBook 665 16 inch G11 Notebook PC
│
├─HP 5MP Camera:
│     Device ID:          377eb704f59a32dc0c615859a9e7bb66246a732d
│     Current version:    0.7
│     Vendor:             Chicony (USB:0x04F2)
│     Serial Number:      0001
│     GUID:               ac588922-ba28-5efc-bd16-5a8fbe669e09 ← USB\VID_04F2&PID_B7E9
│     Device Flags:       • Updatable
│                         • Can tag for emulation
│   
├─Ryzen 7 Pro 7735U with Radeon Graphics:
│ │   Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │   Vendor:             AMD
│ │   GUIDs:              52f8f9af-1ca9-5352-bef4-ceb232c888a5 ← CPUID\PRO_0&FAM_19&MOD_44
│ │                       e94372a3-3ffb-5d1c-a579-c415b7313e52 ← CPUID\PRO_0&FAM_19&MOD_44&STP_1
│ │   Device Flags:       • Internal device
│ │ 
│ ├─Secure Processor:
│ │     Device ID:        c54ab0237d7a8db8c717b68e0be78e4374a2a079
│ │     Current version:  00.28.00.73
│ │     Bootloader Version: 00.28.00.73
│ │     Vendor:           AMD (PCI:0x1022)
│ │     GUID:             9844da3e-1df2-52fe-9413-d4378af6221e ← PCI\VEN_1022&DEV_1649
│ │     Device Flags:     • Internal device
│ │                       • Can tag for emulation
│ │   
│ └─System Management Unit (SMU):
│       Device ID:        db0330716216c629bb2c07256e5d018f499eb6ce
│       Summary:          Microcontroller used within CPU/APU program 4
│       Current version:  69.67.0
│       Vendor:           AMD
│       GUID:             79307ae6-a2ea-52e1-bf56-6abbaf3547ad ← /sys/devices/platform/AMDI0007:00
│       Device Flags:     • Internal device
│                         • Can tag for emulation
│     
├─SBAT:
│     Device ID:          6469856584e2f5873b2f148302e46c9313c7d054
│     Summary:            Generation number based revocation mechanism
│     Current version:    1.7.4
│     Vendor:             OS:ubuntu-core
│     GUID:               009def40-8820-52da-8435-8353cfe3d72c ← UEFI\OS_ubuntu-core&VAR_SbatLevelRT
│     Device Flags:       • Updatable
│                         • Needs a reboot after installation
│                         • Signed Payload
│   
├─SK hynix PC801 HFS001TEJ9X101N:
│     Device ID:          04e17fcf7d3de91da49a163ffe4907855c3648be
│     Summary:            NVM Express solid state drive
│     Current version:    HPS1    
│     Vendor:             PCI:0x1C5C
│     Serial Number:      AME5N006013505J3T
│     GUIDs:              bcfb6135-158b-5c97-a08c-a76de6c90dc4 ← NVME\VEN_1C5C&DEV_1959
│                         021c33a7-8b6a-5ec2-a388-4c472df55c3f ← NVME\VEN_1C5C&DEV_1959&SUBSYS_1C5C1959
│                         b0e8345f-66fe-5a95-b9e5-7c5d15902d17 ← SK hynix PC801 HFS001TEJ9X101N
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│                         • Signed Payload
│                         • Can tag for emulation
│   
├─System Firmware:
│ │   Device ID:          5ac99b4cc4602bcdcdebe24d7b22da95d44a7711
│ │   Summary:            UEFI System Resource Table device (updated via NVRAM)
│ │   Current version:    17104896
│ │   Minimum Version:    1
│ │   Vendor:             HP (DMI:HP)
│ │   Update State:       Success
│ │   GUID:               27b49886-41a0-4955-38a3-92f903b1b283
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • System requires external power source
│ │                       • Needs a reboot after installation
│ │                       • Cryptographic hash verification is available
│ │                       • Device is usable for the duration of the update
│ │   Device Requests:    • Message
│ │ 
│ ├─HP UEFI Secure Boot PK:
│ │     Device ID:        6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│ │     Summary:          UEFI Platform Key
│ │     Current version:  2017
│ │     Vendor:           HP Inc.
│ │     GUIDs:            a8179545-9ab4-5347-a45f-e35b1a12ed11 ← UEFI\VENDOR_HP-Inc.&NAME_HP-UEFI-Secure-Boot-PK
│ │                       3906d7cb-dd6d-5a75-ae08-5ec6fca77c46 ← UEFI\CRT_9BF772D66DF309A55F193437F0B99A6AB1BA6711
│ │     Device Flags:     • Internal device
│ │   
│ ├─UEFI Key Exchange Key:
│ │ │   Device ID:        2a4c23bfb79b5dabe474cb7b1b3e604645d6f9c6
│ │ │   Device Flags:     • Internal device
│ │ │ 
│ │ ├─HP UEFI Secure Boot KEK:
│ │ │     Device ID:      84cabb1dce2a14c89c23fd80885530c7a877ca39
│ │ │     Current version: 2017
│ │ │     Vendor:         HP Inc. (UEFI:HP Inc.)
│ │ │     GUIDs:          5cff761c-d054-5fd0-a5a7-1091b6eebe69 ← UEFI\VENDOR_HP-Inc.&NAME_HP-UEFI-Secure-Boot-KEK
│ │ │                     cc14b9a4-557c-59dd-b154-e040b1d67517 ← UEFI\CRT_3421767E92415862B897D24D9B408A81A8AF375F
│ │ │     Device Flags:   • Internal device
│ │ │                     • Updatable
│ │ │                     • Needs a reboot after installation
│ │ │                     • Device is usable for the duration of the update
│ │ │                     • Signed Payload
│ │ │                     • Can tag for emulation
│ │ │   
│ │ └─KEK CA:
│ │       Device ID:      b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7
│ │       Current version: 2023
│ │       Vendor:         Microsoft (UEFI:Microsoft)
│ │       GUIDs:          814e950f-1449-566a-a190-42c9d3a3a2df ← UEFI\VENDOR_Microsoft&NAME_Microsoft-KEK-CA
│ │                       cd94ec34-7163-5f27-8549-1bd4b7872ae8 ← UEFI\CRT_DEC64D7746D983DB3774829A00BF829D9F19E9CF
│ │       Device Flags:   • Internal device
│ │                       • Updatable
│ │                       • Needs a reboot after installation
│ │                       • Device is usable for the duration of the update
│ │                       • Signed Payload
│ │                       • Can tag for emulation
│ │     
│ ├─UEFI Signature Database:
│ │ │   Device ID:        0352a8acc949c7df21fec16e566ba9a74e797a97
│ │ │   Device Flags:     • Internal device
│ │ │ 
│ │ ├─HP UEFI Secure Boot DB:
│ │ │     Device ID:      c8fe97acb1ac2ff598a3a255dd2b760ed1f870c9
│ │ │     Current version: 2024
│ │ │     Vendor:         HP Inc. (UEFI:HP Inc.)
│ │ │     GUIDs:          c57348fa-61fc-54a1-a8ba-148bdbe4bde5 ← UEFI\VENDOR_HP-Inc.&NAME_HP-UEFI-Secure-Boot-DB
│ │ │                     c9538d57-d8ec-53f2-9710-597dea0d4cbd ← UEFI\CRT_121B33FA80A23170F18C7CA279D835D3D0E38D4D
│ │ │     Device Flags:   • Internal device
│ │ │                     • Updatable
│ │ │                     • Needs a reboot after installation
│ │ │                     • Signed Payload
│ │ │                     • Can tag for emulation
│ │ │   
│ │ ├─UEFI CA:
│ │ │     Device ID:      5bc922b7bd1adb5b6f99592611404036bd9f42d0
│ │ │     Current version: 2023
│ │ │     Vendor:         Microsoft (UEFI:Microsoft)
│ │ │     GUIDs:          26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
│ │ │                     308281c7-d0c5-52e0-8c1a-810540de03df ← UEFI\CRT_7CD7437C555F89E7C2B50E21937E420C4E583E80
│ │ │     Device Flags:   • Internal device
│ │ │                     • Updatable
│ │ │                     • Needs a reboot after installation
│ │ │                     • Signed Payload
│ │ │                     • Can tag for emulation
│ │ │   
│ │ └─Windows UEFI CA:
│ │       Device ID:      d31da5f926c6d962ed810b284fab5a2ef623007b
│ │       Current version: 2023
│ │       Vendor:         Microsoft (UEFI:Microsoft)
│ │       GUIDs:          914015a8-9d92-5462-9a9b-f2b361e4faae ← UEFI\VENDOR_Microsoft&NAME_Windows-UEFI-CA
│ │                       89a825bf-78b5-5f1c-905b-e982b2f02584 ← UEFI\CRT_A794240D25F0CCB2EC8142DC2F7411890717DEAD
│ │       Device Flags:   • Internal device
│ │                       • Updatable
│ │                       • Needs a reboot after installation
│ │                       • Signed Payload
│ │                       • Can tag for emulation
│ │     
│ └─UEFI dbx:
│       Device ID:        362301da643102b9f38477387e2193e57abaa590
│       Summary:          UEFI revocation database
│       Current version:  20250902
│       Minimum Version:  20250902
│       Vendor:           Microsoft (UEFI:Microsoft)
│       Install Duration: 1 second
│       GUIDs:            7689caf4-c147-5c67-bff9-5dbe59a441bd ← UEFI\CRT_C8B4C6D9755968B6DEB48D4768DD5E9020D3FF4ADC9A62521F54252DD4241678&ARCH_X64
│                         d07ff664-b0e1-5f4e-a723-d7fbcbfcb94f ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_X64
│                         f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
│       Device Flags:     • Internal device
│                         • Updatable
│                         • Supported on remote server
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│                         • Only version upgrades are allowed
│                         • Signed Payload
│                         • Can tag for emulation
│     
├─TPM:
│     Device ID:          1d8d50a4dbc65618f5c399c2ae827b632b3ccc11
│     Current version:    7.2.3.1
│     Vendor:             Nuvoton (TPM:NTC)
│     GUIDs:              fac1c8f3-73c8-5cd6-8330-07a3690b5140 ← TPM\VEN_NTC&DEV_0000
│                         bf68887b-e3d9-5572-9a02-0d34979502c7 ← TPM\VEN_NTC&MOD_NPCT75x"!"8rls
│                         e9ccc1dc-960a-5e09-afe9-e59a904b776d ← TPM\VEN_NTC&DEV_0000&VER_2.0
│                         bc8b2f06-5f89-5b3a-bc74-976e0329f53b ← TPM\VEN_NTC&MOD_NPCT75x"!"8rls&VER_2.0
│     Device Flags:       • Internal device
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device can recover flash failures
│                         • Signed Payload
│                         • Can tag for emulation
│   
├─UEFI Device Firmware:
│     Device ID:          904f9e062b08a03a7337f7f6cbff53b799344c3e
│     Summary:            UEFI System Resource Table device (updated via NVRAM)
│     Current version:    335609856
│     Minimum Version:    1
│     Vendor:             DMI:HP
│     Update State:       Success
│     GUID:               b58cfc31-3a86-6286-a620-f2a1c6c03ac2
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│     Device Requests:    • Message
│   
├─UEFI Device Firmware:
│     Device ID:          b970edafffcf075cf953e5efebbf2595bf98f1db
│     Summary:            UEFI System Resource Table device (updated via NVRAM)
│     Current version:    335609856
│     Minimum Version:    1
│     Vendor:             DMI:HP
│     Update State:       Success
│     GUID:               ca1146a5-1403-4385-9661-619f4e9eefbb
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│     Device Requests:    • Message
│   
└─UEFI Device Firmware:
      Device ID:          e97608be1da5b9d742670ca8c3c4f515bc10646a
      Summary:            UEFI System Resource Table device (updated via NVRAM)
      Current version:    935603970
      Minimum Version:    1
      Vendor:             DMI:HP
      Update State:       Success
      GUID:               aaa08f4f-bc42-40c2-adf8-aa5a3e62e8e5
      Device Flags:       • Internal device
                          • Updatable
                          • System requires external power source
                          • Needs a reboot after installation
                          • Device is usable for the duration of the update
      Device Requests:    • Message
Changing home directory from one small SD card to another big SD card fails https://askubuntu.com/questions/1562790/changing-home-directory-from-one-small-sd-card-to-another-big-sd-card-fails

I'm using Ubuntu 22.04 on a ThinkPad.
The current /home is separately on a
small SD card (256GB, ext4) and I need to use a bigger SD card (1TB, ext4) instead.

I tried to follow the "change home directory procedure" as described here
https://wiki.ubuntuusers.de/Home_umziehen/
and first synchronized data from the original SD card to the new SD card using rsync. small SD mounted as usual as /home
big SD mounted automatically under /media/\<username\>/\<drive\>
Copied result is verified and OK.

1. Unexpected behavior
I am able to mount temporarily the big SD to /home and to see its content on the desktop (Gnome),
but I am unable to unmount the small SD. (It says it is active.)

2. Unexpected behavior
I entered the UUID of the big SD into /etc/fstab
and left the entry for the small SD marked as comment
then I shutdown the PC, removed the small SD and restarted
Ubuntu went into an "emergency mode"
independent if the big SD remains via adapter to USB or is in the card reader. I don't know what I can do with the "emergency mode"?

I started with a live Ubuntu session and
mounted the respective partition
redo the changes in /etc/fstab so
I got back the original situation with the small SD as /home, but how to get the big SD with the same data as the small SD running as new /home?

Ubuntu 24.04 serving Time Machine disconnects, won't resume until reboot https://askubuntu.com/questions/1562232/ubuntu-24-04-serving-time-machine-disconnects-wont-resume-until-reboot

I've been serving Apple Time Machine backups from a Ubuntu 24.04 server for some time, first via netatalk/afp and now via SAMBA, which run reliably when the server is first booted. After the server has been running for a few days/weeks, though, I'll see the Apple clients report that the network disk has disconnected and subsequent backups fail until I reboot the server at which point, again, it'll run successfully for a while and then hit another disconnect failure. Has anyone else here seen a similar pattern and, if so, have you found a means to prevent it from recurring?

ThinkCentre M91p: 1962 "No operating system" after Ubuntu Server install https://askubuntu.com/questions/1545435/thinkcentre-m91p-1962-no-operating-system-after-ubuntu-server-install

I have an old ThinkCentre M91p that was my son's computer, running Windows 10 with a 120Gb SATA SSD. I was going to repurpose the computer as a Minecraft server for my family, and decided to install Ubuntu Server (24.04.1) on it.

Server install goes fine, finds the SSD and partitions it without any problems. In short, the installation goes flawlessly.

But once I reboot it after: 1962 No Operating System. The same exact hardware was working with Windows just 10 minutes earlier.

I've tried Legacy/UEFI/Auto boot modes, and Auto/AHCI SATA mode. All combinations results in the same error.

If I boot Ubuntu, fdisk sees the SATA SSD just fine, and I can partition it.

It just isn't booting Ubuntu Server from the SATA SSD. No matter what I try.

There's a looot of other threads that are similar — but with one distinct difference: I'm running a server without GUI. So none of the "Install and run boot-repair" solutions will work for me, since I can't run GUI apps.

Cant find the fingerprint option on ubuntu 24.04 https://askubuntu.com/questions/1519906/cant-find-the-fingerprint-option-on-ubuntu-24-04

It detects when I use lsusb but can't run fprintd-enroll

fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
sudo systemctl start fprintd && sudo systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: active (running) since Mon 2024-07-08 15:22:30 IST; 3s ago
       Docs: man:fprintd(1)
   Main PID: 90113 (fprintd)
      Tasks: 6 (limit: 9114)
     Memory: 1.6M (peak: 2.5M)
        CPU: 72ms
     CGroup: /system.slice/fprintd.service
             └─90113 /usr/libexec/fprintd

Jul 08 15:22:30 bhanu-vardhan-reddy-Vostro-3500 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jul 08 15:22:30 bhanu-vardhan-reddy-Vostro-3500 fprintd[90113]: Creating TOD wrapper for goodix-tod (Goodix Fingerprint Sensor 53xc) driver
Jul 08 15:22:30 bhanu-vardhan-reddy-Vostro-3500 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Some applications temporarily unresponsive after fresh boot of Ubuntu 24.04 https://askubuntu.com/questions/1519189/some-applications-temporarily-unresponsive-after-fresh-boot-of-ubuntu-24-04

Since I upgraded my system to Ubuntu 24.04 (from 23.10), I’ve been experiencing some peculiar performance issues:

In the first hour or so after booting, some applications tend to freeze suddenly upon some actions. Ubuntu then shows a dialog like “‘Application XY’ is not responding” with the option to “Force quit” or “Wait”. Usually the action completes after roughly half a minute.

For example:

  • Firefox (Snap version)
    • especially on right-click and actions in the context menu (even expanding another menu level; in these cases, an unresponsiveness dialog is shown for the main window as well as each open context menu level)
    • sometimes even input like scrolling using the mouse wheel or text input in a form field
  • Gnome Terminal
    • especially opening a new tab or switching between tabs
    • sometimes even text input

Other applications seem to be completely unaffected, I did never observe this problem for any Flatpak applications for example.

All this happens despite very low system load (CPU, memory, IO). Interestingly, after an hour or so, everything works fluently again.

My suspicion is that there is some problem with a GTK component, but I have no idea how to examine this. Any suggestions?

Wifi on Ubuntu 22.04 Macbook pro 2018 Intel chip https://askubuntu.com/questions/1500235/wifi-on-ubuntu-22-04-macbook-pro-2018-intel-chip

There is an amazing thread on this here - Installing Broadcom Wireless Drivers

Which sadly does not mention the 4464 adaptors. My machine (a 2018 Macbook Pro with an intel chip has the following)

Network controller [0280]: Broadcom Inc. and subsidiaries BCM4364 802.11ac Wireless Network Adapter [14e4:4464] (rev 03)
    Subsystem: Apple Inc. BCM4364 802.11ac Wireless Network Adapter [106b:07bf]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin A routed to IRQ 255
    Region 0: Memory at 81400000 (64-bit, non-prefetchable) [disabled] [size=32K]
    Region 2: Memory at 81000000 (64-bit, non-prefetchable) [disabled] [size=4M]
    Capabilities: <access denied>
    Kernel modules: brcmfmac

The adaptor is not listed in the various responses, and I have tried all the options to no avail - still no wifi!

Output of sudo dmesg | grep brcm gives :

[    2.306318] usbcore: registered new interface driver brcmfmac
[    2.306471] brcmfmac 0000:03:00.0: enabling device (0000 -> 0002)
[    2.416065] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b2-pcie for chip BCM4364/3
[    2.417728] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN-u-7.5-X0.bin failed with error -2
[    2.418243] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN-u-7.5.bin failed with error -2
[    2.418276] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN-u.bin failed with error -2
[    2.418307] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN.bin failed with error -2
[    2.418337] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-X0.bin failed with error -2
[    2.418367] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai.bin failed with error -2
[    2.418398] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.bin failed with error -2
[    2.418401] brcmfmac 0000:03:00.0: brcmf_pcie_setup: Dongle setup failed
[    2.418418] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[    3.070049] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'

Does anyone have an idea how to make this work with the 14e4:4464 version?

Thank you so much!

How can I record from YouTube videos or Streaming videos in Ubuntu 22.04 LTS https://askubuntu.com/questions/1489095/how-can-i-record-from-youtube-videos-or-streaming-videos-in-ubuntu-22-04-lts

How can I record from YouTube videos or Streaming videos in Ubuntu 22.04 LTS? I wish to record the "Ring of Fire" solar eclipse event, and also others from online - whether streaming live or just a video.

With Wayland, how can I mirror two displays and extend a third? https://askubuntu.com/questions/1468499/with-wayland-how-can-i-mirror-two-displays-and-extend-a-third

I want to mirror two displays (laptop and left display) and extend a third (right display).

If that is unclear, I found a substantially equivalent question at How to "overlay"/clone displays in GNOME Wayland that includes some handy images showing two displays are mirrored and one is extended.

Sadly, the only answer was to try something manual. Under Xorg, it is easy to do this with xrandr so I am disappointed that I don't find a simple solution in Wayland / Ubuntu 22.04.

I found a "manual" and quite ugly solution, but I hope there is a better way. I will eventually post the manual solution in detail if there are no better options. In brief, I saved ~/.config/monitors.xml multiple times while changing config, inferred which configuration was active and how to mirror two displays, edited a single <logicalmonitor> to contain the two <monitor> instances that are mirrored, and rebooted.

Kernel Panic- not syncing: VFS: Unable to mount root fs on unknown block (0,0) https://askubuntu.com/questions/1424828/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-0-0

My laptop went into hibernation during a distro upgrade. I ran into this error during boot:

Kernel Panic- not syncing: VFS: Unable to mount root fs on unknown block (0,0)

Here are the boot message details:

[    0.711099] sched_clock: Marking stable (708847122, 744205)->(719361868, -9770541)
[    0.712023] registered taskstats version 1
[    0.712778] Loading compiled-in X.509 certificates
[    0.714203] Loaded X.509 cert 'Build time autogenerated kernel key: 3e9c0893400760cb433d1bad37690f1fbf53b04b'
[    0.715499] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969'
[    0.716838] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19'
[    0.717589] blacklist: Loading compiled-in revocation X.509 certificates
[    0.718374] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
[    0.719187] zswap: loaded using pool lzo/zbud
[    0.720175] Key type .fscrypt registered
[    0.720980] Key type fscrypt registered
[    0.722002] Key type big_key registered
[    0.722887] Key type trusted registered
[    0.723752] Key type encrypted registered
[    0.724515] AppArmor: AppArmor sha1 policy hashing enabled
[    0.725930] integrity: Loading X.509 certificate: UEFI:db
[    0.726696] integrity: Loaded X.509 cert 'Lenovo Ltd.: ThinkPad Product CA 2012: 838b1f54c1550463f45f98708640f1106925949'
[    0.727468] integrity: Loading X.509 certificate: UEFI:db
[    0.728290] integrity: Loaded X.509 cert 'Lenovo(Beijing) Ltd.: TPCDL-DB: f6c9e489d7ebacde9b329d40d06cc0f87cfe6fff'
[    0.729062] integrity: Loading X.509 certificate: UEFI:db
[    0.729863] integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8ffffc6b027ec3449e9c8f'
[    0.730669] integrity: Loading X.509 certificate: UEFI:db
[    0.731471] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    0.732341] integrity: Loading X.509 certificate: UEFI:db
[    0.733178] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    0.734833] Revoking X.509 certificate: UEFI:dbx
[    0.735733] blacklist: Revoked X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
[    0.736635] Revoking X.509 certificate: UEFI:dbx
[    0.737484] blacklist: Revoked X.509 cert 'Debian Secure Boot Signer: 08a7468def'
[    0.739357] ima: Allocated hash algorithm: sha1
[    0.887046] usb 1-3: new high-speed USB device number 2 using xhci_hcd
[    0.895855] ima: No architecture policies found
[    0.896778] evm: Initialising EVM extended attributes:
[    0.897635] evm: security.selinux
[    0.898501] evm: security.SMACK64
[    0.899360] evm: security.SMACK64EXEC
[    0.900255] evm: security.SMACK64TRANSMUTE
[    0.901105] evm: security.SMACK64MMAP
[    0.901951] evm: security.apparmor
[    0.902769] evm: security.ima
[    0.903638] evm: security.capability
[    0.904459] evm: HMAC attrs: 0x1
[    0.906281] PM: Magic number: 2:564:498
[    0.907274] rtc_cmos 00:02: setting system clock to 2022-08-20T20:27:50 UTC (1661027270)
[    0.908390] md: Waiting for all devices to be available before autodetect
[    0.909188] md: If you don't use raid, use raid=noautodetect
[    0.910246] md: Autodetecting RAID arrays.
[    0.911047] md: autorun ...
[    0.911911] md: ... autorun DONE.
[    0.912799] VFS: Cannot open root device "mapper/ubuntu--vg-root" or unknown-block(0,0): error -6
[    0.913654] Please append a correct "root=" boot option; here are the available partitions:
[    0.914523] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.915413] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-99-generic #112-Ubuntu
[    0.916344] Hardware name: LENOVO 20F600A1GE/20F600A1GE, BIOS R02ET71W (1.44 ) 05/08/2019
[    0.917248] Call Trace:
[    0.918143]  dump_stack+0x6d/0x8b
[    0.919037]  panic+0x101/0x2e3
[    0.919962]  mount_block_root+0x23f/0x2e8
[    0.920818]  mount_root+0x38/0x3a
[    0.921699]  prepare_namespace+0x13f/0x194
[    0.922576]  kernel_init_freeable+0x23f/0x263
[    0.923450]  ? rest_init+0xb0/0xb0
[    0.924353]  kernel_init+0xe/0x110
[    0.925199]  ret_from_fork+0x35/0x40
[    0.926116] Kernel Offset: 0xb000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    0.927059] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

To fix it I followed the steps from this topic.

Here are all the steps I followed:

ubuntu@ubuntu:~$ sudo mount /dev/mapper/ubuntu--vg-root /mnt
ubuntu@ubuntu:~$ sudo mount --bind /dev /mnt/dev
ubuntu@ubuntu:~$ sudo mount --bind /dev/pts /mnt/dev/pts/
ubuntu@ubuntu:~$ sudo mount --bind /proc/ /mnt/proc/
ubuntu@ubuntu:~$ sudo mount --bind /sys/ /mnt/sys/
ubuntu@ubuntu:~$ sudo mount --bind /run /mnt/run
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# uname -a
Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:/# cal /boot/
config-5.4.0-26-generic      System.map-5.4.0-26-generic
initrd.img-5.4.0-26-generic  
root@ubuntu:/# update-initramfs -u -k 5.4.0-26-generic
update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic
root@ubuntu:/# update-grub2
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
/usr/sbin/grub-mkconfig: 275: cannot create /boot/grub/grub.cfg.new: Directory nonexistent

The last command had an issue.

Here is additional information:

root@ubuntu:/# grub-install -v
grub-install: Info: executing modprobe efivars 2>/dev/null.
grub-install: Info: Looking for /sys/firmware/efi ...
grub-install: Info: ... found.  
x86_64-efi will be installed for your platform.  
grub-install: Info: cannot open "/boot/grub/device.map":   
No such file or directory.   
grub-install: Error: EFI directory cannot be found.

I did all steps again with mounting boot partition.

The only change I had was here:

update-initramfs -u -k 5.4.0-26-generic
ln: Die harte Verknüpfung '/boot/initrd.img-5.4.0-26-generic.dpkg-bak' => '/boot/initrd.img-5.4.0-26-generic' konnte nicht angelegt werden: Vorgang nicht zulässig
update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic

Does anyone have any idea?

Here is some additional information:

lsblk -f
sda                                                                           
├─sda1
│    vfat   FAT32       18E8-5B11                               465,6M     9% /boot
├─sda2
│    ext2   1.0         6c5d8821-3ae5-4dc7-9b50-4b1eedbd6ec5                  
└─sda3
     LVM2_m LVM2        durg23-i4ZY-vzY0-2BQU-IoGz-j4cU-JCVgvQ                
  ├─ubuntu--vg-root
  │  ext4   1.0         346cd866-61d7-4339-bd6f-043897a89b2a        7G    93% /
  └─ubuntu--vg-swap_1
     swap   1           387b8baf-13e0-4be6-8c60-659f9aa7a4b4                  
sdb  iso966 Jolie Ubuntu 20.04 LTS amd64
│                       2020-04-23-07-51-42-00                                
├─sdb1
│    iso966 Jolie Ubuntu 20.04 LTS amd64
│                       2020-04-23-07-51-42-00                                
├─sdb2
│    vfat   FAT12       1AC3-20ED                                             
└─sdb3
     ext4   1.0   writable
                        8fe94b8c-a489-4927-bd44-473c51d40ea0                  
root@ubuntu:/# [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
UEFI
root@ubuntu:/# dpkg -l | grep '^ii  grub'
ii  grub-common                                2.06-2ubuntu7                                           amd64        GRand Unified Bootloader (common files)
ii  grub-efi                                   2.06-2ubuntu7                                           amd64        GRand Unified Bootloader, version 2 (dummy package)
ii  grub-efi-amd64                             2.06-2ubuntu7                                           amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii  grub-efi-amd64-bin                         2.06-2ubuntu7                                           amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii  grub-efi-amd64-signed                      1.180+2.06-2ubuntu7                                     amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
ii  grub2-common 
No device Found error with Cheese in Ubuntu 20.04.3 LTS https://askubuntu.com/questions/1361802/no-device-found-error-with-cheese-in-ubuntu-20-04-3-lts

I have been struggling to start my webcam as i need to clear an interview with a video conferencing. I updated the OS from 18.04 to 20.04 but still I get the message No device found when I try to open cheese. Below is the output of the command lsusb

nik@nik:/$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Below are some commands executed

   nik@nik:/$ sudo modprobe uvcvideo
   nik@nik:/$ 

   niket@nik:/$ sudo modprobe vfe_v4l2
   modprobe: FATAL: Module vfe_v4l2 not found in directory 
    /lib/modules/5.4.0-81-generic
   niket@nik:/$ sudo modprobe gc2035
    modprobe: FATAL: Module gc2035 not found in directory / 
     lib/modules/5.4.0-81-generic


Can someone clarify me if webcam drivers are not there or how do I need to resolve this problem. I have looked into lot of online docs and applied them but still cannot resolve this issue.

Ubuntu is slow - apt-get update is slow, the boot time is slow, etc https://askubuntu.com/questions/1330757/ubuntu-is-slow-apt-get-update-is-slow-the-boot-time-is-slow-etc

Since Thursday, my Ubuntu 16.04.7 server has been extremely sluggish, even when the load is below 1.0.

sudo apt-get update and sudo apt-get upgrade are both extremely slow. The boot time also takes ages.

I have PHP running on the server and scripts are also taking much longer to execute, even though there are barely any requests coming in.

Output of the top results from systemd-analyze blame:

2min 11.015s apt-daily.service
1min 56.993s cloud-init-local.service
1min 12.026s console-setup.service
1min 8.095s apt-daily-upgrade.service
1min 6.282s dev-vda1.device
1min 649ms cloud-init.service
50.921s apparmor.service
50.255s cloud-config.service
44.707s cloud-final.service
32.721s mysql.service
27.685s systemd-tmpfiles-setup.service
20.327s systemd-update-utmp.service
17.572s snapd.service
11.468s boot-efi.mount
11.051s resolvconf.service
10.486s nginx.service
10.369s networking.service
10.203s certbot.service

Output of critical-chain:

Screenshot

Has anyone got an idea what could be causing this?

Access denied when using mysqli with php https://askubuntu.com/questions/1258511/access-denied-when-using-mysqli-with-php

I want to connect to my database on my Linux machine with PHP (PHP 7.2.24-0ubuntu0.18.04.6 (cli)) using mysqli(). But whenever I try to access it, I get this error:

Warning: mysqli_connect(): (HY000/1698): Access denied for user 'root'@'localhost' in /var/www/html/connect_DB.php on line 9

Connected Success!

I have MySQL installed (mysql Ver 14.14 Distrib 5.7.30, for Linux (x86_64) using EditLine wrapper), and I use the Apache2 server. I do not have XAMPP installed.

My code:

error_reporting(E_ALL); ini_set('display_errors', '1');
$mysql_host = 'localhost'; //server
$mysql_user = "root";
$mysql_pass = "root";

$conn = mysqli_connect($mysql_host, $mysql_user, $mysql_pass, "tests"); 

echo "Connected Success!<br>";

The table ("tests") belongs to the root user... I don't know if this may have anything to do with it, but to open mysql, I do this:

sudo mysql -u root -p

I did check on Warning: mysqli_connect(): (HY000/1045): Access denied for user 'username'@'localhost' (using password: YES) and it did not quite help...

Error booting Linux from grub https://askubuntu.com/questions/1118998/error-booting-linux-from-grub

I have the same problem as this post. I have followed its accepted answer in this way.

I ran:

set pager=1   
ls  

This is the result of ls.

                           GNU GRUB  version 2.02~beta2-36ubuntu3

   Minimal BASH-like line editing is supported. For the first word, TAB
   lists possible command completions. Anywhere else TAB lists possible
   device or file completions.


grub> set pager=1
grub> ls


(hd0) (hd0,apple2) (hd0,apple1) (hd0,msdos2) (hd1) (hd1,gpt10) (hd1,gpt9)
(hd1,gpt8) (hd1,gpt7) (hd1,gpt6) (hd1,gpt5) (hd1,gpt4) (hd1,gpt3) (hd1,gpt2)
(hd1,gpt1) (cd0) error: failure reading sector 0x21c68 from `cd0'.
error: failure reading sector 0x21c40 from `cd0'.
error: failure reading sector 0x0 from `cd0'.

grub> _

I found my Linux root file system: (hd1,gpt7), and ran the mentioned commands in the answer, but I don't know what to put instead of /dev/sda1. In other words I don't know how what is the location of my root system.

I ran commands with /dev/sda1 and get this result:

grub> ls
(hd0) (hd0,apple2) (hd0,apple1) (hd0,msdos2) (hd1) (hd1,gpt10) (hd1,gpt9)
(hd1,gpt8) (hd1,gpt7) (hd1,gpt6) (hd1,gpt5) (hd1,gpt4) (hd1,gpt3) (hd1,gpt2)
(hd1,gpt1) (cd0) error: failure reading sector 0x21c68 from `cd0'.
error: failure reading sector 0x21c40 from `cd0'.
error: failure reading sector 0x0 from `cd0'.

grub> set root=(hd1,gpt7)
grub> linux /boot/vmlinuz-4.4.0-21-generic root=/dev/sda1
grub> initrd /boot/initrd.img-4.4.0-21-generic
grub> boot_

Result after pressing Enter:

[    2.168297] vga_switcheroo: enabled
[    2.168517] [TTM] Zone  kernel: Available graphics memory: 4030758 KiB
[    2.168518] [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
[    2.168518] [TTM] Initializing pool allocator
[    2.168531] [TTM] Initializing DMA pool allocator
[    2.168539] nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB
[    2.168539] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    2.168541] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[    2.168542] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    2.168543] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[    2.267891] nouveau 0000:01:00.0: DRM: MM: using copy for buffer copies
[    2.267894] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[    2.477903] scsi 5:0:0:0: Direct-Access     UFD 2.0  Silicon-Power8G  1100 PQ: 0 ANSI: 4
[    2.478295] sd 5:0:0:0: Attached scsi generic sg2 type 0
[    2.478526] sd 5:0:0:0: [sdb] 15730688 512-byte logical blocks: (8.05 GB/7.50 GiB)
[    2.479298] sd 5:0:0:0: [sdb] Write Protect is off
[    2.480093] sd 5:0:0:0: [sdb] No Caching mode page found
[    2.480093] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[    2.483308]  sdb: sdb1 sdb2
[    2.485895] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[    2.560538] clocksource: Switched to clocksource tsc
[    2.660408] Console: switching to colour frame buffer device 240x67
[    2.664802] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[    4.299824] random: nonblocking pool is initialized
Begin: Will now check root file system ... fsck from util-linux 2.27.1
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
run-init: opening console: No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
No init found. Try passing init= bootarg.
[    4.419231] hidraw: raw HID events driver (C) Jiri Kosina
[    4.421048] usbcore: registered new interface driver usbhid
[    4.421659] usbhid: USB HID core driver

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) [    7.808252] ACPI Warning: \_SB_.PCIO.PEGO.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[    7.809419] ACPI: \_SB_.PCIO.PEGO.PEGP: failed to evaluate _DSM
[    7.810191] ACPI Warning: \_SB_.PCIO.PEGO.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[    7.810964] nouveau 0000:01:00.0: DRM: evicting buffers...
[    7.811583] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[    7.812223] nouveau 0000:01:00.0: DRM: suspending client object trees...
[    7.814162] nouveau 0000:01:00.0: DRM: suspending kernel object tree...

(initramfs) _

I don't know what to do now. I couldn't comment about the information that was posted under the answer, because I don't have the enough reputation.

How do I remove or reset all xrdp settings for user https://askubuntu.com/questions/1068452/how-do-i-remove-or-reset-all-xrdp-settings-for-user

I am running xrdp on my Ubuntu 18.04 computer. I got 3 users. Two is working well. They can connect from Windows 10 rdp without any problem. But the last one does fail with a "Connection problem, giving up" message. And it is that user I use myself.

I have spend a lot of time researching and looking at log-files without any luck. I did remove and install xrdp again - no change.

I might have done something to corrupt the settings for this user. It did work for some time. If I only could somehow reset the user.

The user is not logged on locally. I use gnome desktop. From inxi for one of the functioning users i got this info:

Desktop: Gnome 3.28.2 Distro: Ubuntu 18.04.1 LTS Display Server: X.Org 1.19.6

EDIT

I compared an OK user with the malfunctioning user by looking at /var/log/xrdp.log. For the OK user, the log continues after:

 [DEBUG] xrdp_wm_log_msg: started connecting

while the other just gets a bunch of:

 [DEBUG] Closed socket 17 (AF_UNIX)

and after a while these lines appears:

 xrdp_wm_log_msg: connection problem, giving up
 xrdp_wm_log_msg: some problem

There are some differences in .xorgxrdp.10.log

Bad one:

  [ 22202.422] (II) Loading /usr/lib/x86_64-linux-gnu/nvidia/xorg/libglx.so
  [ 22202.425] (II) Module glx: vendor="NVIDIA Corporation"
  [ 22202.425]    compiled for 4.0.2, module version = 1.0.0
  [ 22202.425]    Module class: X.Org Server Extension
  [ 22202.425] (II) NVIDIA GLX Module  390.48  Wed Mar 21 23:42:56 PDT 2018
    ...
  [ 22202.428] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

Good one

[ 24242.838] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 24242.839] (II) Module glx: vendor="X.Org Foundation"
[ 24242.839]    compiled for 1.19.6, module version = 1.0.0
[ 24242.839]    ABI class: X.Org Server Extension, version 10.0
...
[ 24242.843] (II) AIGLX: Screen 0 is not DRI2 capable
[ 24242.843] (EE) AIGLX: reverting to software rendering
[ 24242.869] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[ 24242.870] (II) IGLX: Loaded and initialized swrast
[ 24242.870] (II) GLX: Initialized DRISWRAST GL provider for screen 0

Edit xrdp.ini added

cat /etc/xrdp/xrdp.ini
[Globals]
; xrdp.ini file version number
ini_version=1

; fork a new process for each incoming connection
fork=true
; tcp port to listen
port=3389
; 'port' above should be connected to with vsock instead of tcp
use_vsock=false
; regulate if the listening socket use socket option tcp_nodelay
; no buffering will be performed in the TCP stack
tcp_nodelay=true
; regulate if the listening socket use socket option keepalive
; if the network connection disappear without close messages the connection will be closed
tcp_keepalive=true
#tcp_send_buffer_bytes=32768
#tcp_recv_buffer_bytes=32768

; security layer can be 'tls', 'rdp' or 'negotiate'
; for client compatible layer
security_layer=negotiate
; minimum security level allowed for client
; can be 'none', 'low', 'medium', 'high', 'fips'
crypt_level=high
; X.509 certificate and private key
; openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365
certificate=
key_file=
; set SSL protocols
; can be comma separated list of 'SSLv3', 'TLSv1', 'TLSv1.1', 'TLSv1.2'
ssl_protocols=TLSv1, TLSv1.1, TLSv1.2
; set TLS cipher suites
#tls_ciphers=HIGH

; Section name to use for automatic login if the client sends username
; and password. If empty, the domain name sent by the client is used.
; If empty and no domain name is given, the first suitable section in
; this file will be used.
autorun=

allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
#hidelogwindow=true
max_bpp=32
new_cursors=true
; fastpath - can be 'input', 'output', 'both', 'none'
use_fastpath=both
; when true, userid/password *must* be passed on cmd line
#require_credentials=true
; You can set the PAM error text in a gateway setup (MAX 256 chars)
#pamerrortxt=change your password according to policy at http://url

;
; colors used by windows in RGB format
;
blue=009cb5
grey=dedede
#black=000000
#dark_grey=808080
#blue=08246b
#dark_blue=08246b
#white=ffffff
#red=ff0000
#green=00ff00
#background=626c72

;
; configure login screen
;

; Login Screen Window Title
#ls_title=My Login Title

; top level window background color in RGB format
ls_top_window_bg_color=009cb5

; width and height of login screen
ls_width=350
ls_height=430

; login screen background color in RGB format
ls_bg_color=dedede

; optional background image filename (bmp format).
#ls_background_image=

; logo
; full path to bmp-file or file in shared folder
ls_logo_filename=
ls_logo_x_pos=55
ls_logo_y_pos=50

; for positioning labels such as username, password etc
ls_label_x_pos=30
ls_label_width=60

; for positioning text and combo boxes next to above labels
ls_input_x_pos=110
ls_input_width=210

; y pos for first label and combo box
ls_input_y_pos=220

; OK button
ls_btn_ok_x_pos=142
ls_btn_ok_y_pos=370
ls_btn_ok_width=85
ls_btn_ok_height=30

; Cancel button
ls_btn_cancel_x_pos=237
ls_btn_cancel_y_pos=370
ls_btn_cancel_width=85
ls_btn_cancel_height=30

[Logging]
LogFile=xrdp.log
LogLevel=DEBUG
EnableSyslog=true
SyslogLevel=DEBUG
; LogLevel and SysLogLevel could by any of: core, error, warning, info or debug

[Channels]
; Channel names not listed here will be blocked by XRDP.
; You can block any channel by setting its value to false.
; IMPORTANT! All channels are not supported in all use
; cases even if you set all values to true.
; You can override these settings on each session type
; These settings are only used if allow_channels=true
rdpdr=true
rdpsnd=true
drdynvc=true
cliprdr=true
rail=true
xrdpvr=true
tcutils=true

; for debugging xrdp, in section xrdp1, change port=-1 to this:
#port=/tmp/.xrdp/xrdp_display_10

; for debugging xrdp, add following line to section xrdp1
#chansrvport=/tmp/.xrdp/xrdp_chansrv_socket_7210


;
; Session types
;

; Some session types such as Xorg, X11rdp and Xvnc start a display server.
; Startup command-line parameters for the display server are configured
; in sesman.ini. See and configure also sesman.ini.
[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
code=20

[X11rdp]
name=X11rdp
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
xserverbpp=24
code=10

[X11rdp2]
name=Custom
lib=libvnc.so
username=askallan
password=ask
ip=127.0.0.1
port=ask5901

[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask
ip=127.0.0.1
port=-1
#xserverbpp=24
#delay_ms=2000

[console]
name=console
lib=libvnc.so
ip=127.0.0.1
port=5900
username=na
password=ask
#delay_ms=2000

[vnc-any]
name=vnc-any
lib=libvnc.so
ip=ask
port=ask5900
username=na
password=ask
#pamusername=asksame
#pampassword=asksame
#pamsessionmng=127.0.0.1
#delay_ms=2000

[sesman-any]
name=sesman-any
lib=libvnc.so
ip=ask
port=-1
username=ask
password=ask
#delay_ms=2000

[neutrinordp-any]
name=neutrinordp-any
lib=libxrdpneutrinordp.so
ip=ask
port=ask3389
username=ask
password=ask

; You can override the common channel settings for each session type
#channel.rdpdr=true
#channel.rdpsnd=true
#channel.drdynvc=true
#channel.cliprdr=true
#channel.rail=true
#channel.xrdpvr=true
What is ubuntu-mate-vg and how to remove the traces of the Ubuntu Mate desktop? https://askubuntu.com/questions/1017177/what-is-ubuntu-mate-vg-and-how-to-remove-the-traces-of-the-ubuntu-mate-desktop

I am currently using Kubuntu 17.10, but previously I was running the Ubuntu MATE desktop.

After installing the Kubuntu Desktop, I deleted all the traces of Ubuntu MATE using the following commands:

sudo apt-get remove --auto-remove mate-desktop
sudo apt-get purge --auto-remove mate-desktop
sudo apt-get remove mate-*
sudo apt-get autoremove

However, when I opened my KDE partition manager, I saw the following:

First Screenshot

  • ATA TOSHIBA DT01ACA1 - 931.51 GiB (/dev/sda) - This is where my Kubuntu is installed.

  • ATA Hitachi HDS72101 - 931.51 GiB (/dev/sdb) - An empty hard drive.

  • ubuntu-mate-vg - 931.27 GiB (/dev/ubuntu-mate-vg) - I have no idea what this is but it seems it is including the ext4 and Linux swap partitions which logically should belong to the ATA Toshiba DT01ACA1 (/dev/sda).

Note: I have never manually partitioned my hard drive in any way. I always use the default settings and options.

Second Screenshot

My questions:

  1. What is the "ubuntu-mate-vg" entry that occupies the /dev/sda5 in the same device of my Kubuntu installation (First screenshot)?

  2. What is that "ubuntu-mate-vg" entry that is taking a whole section in my list of devices (Second screenshot)? and is it possible to delete it?

Boot Clonezilla from USB on Ubuntu https://askubuntu.com/questions/997372/boot-clonezilla-from-usb-on-ubuntu

I have Ubuntu on my machine and I used UNetbootin to download and setup Clonezilla on an external flash drive. Now I wonder how I can run Clonezilla when I boot up? I'm running on Ubuntu 17.10. When I press Esc after rebooting it shows me the options to choose Ubuntu or Ubuntu Recovery.

I tried the boot shortcut Ctrl+S, then the below screenshot appeared. I wonder what shortcut or how I can open Clonezilla on my Ubuntu machine to be able to take an image of my disk.

enter image description here

Removed Linux kernels are still showing up in GRUB https://askubuntu.com/questions/994759/removed-linux-kernels-are-still-showing-up-in-grub

I have removed several deprecated 3.16 kernels, however one is still showing up in GRUB and Ubuntu is booting using that kernel. When I run dpkg -l | grep linux-image-3.16.0-51-generic the image is not listed. When I run sudo update-grub it finds the kernel in /boot and adds it to the list of kernels to run.

Can I just delete this file? How do I remove this kernel, so that Ubuntu runs under 3.13?

Results of ls /boot:

:~$ sudo ls /boot | grep vmlinuz
vmlinuz-3.13.0-139-generic
vmlinuz-3.13.0-67-generic
vmlinuz-3.16.0-51-generic

Results of sudo dpkg -l | grep linux-image-3.16.0-51-generic:

dpkg -l

Safely move (and extend) Ubuntu partition https://askubuntu.com/questions/642931/safely-move-and-extend-ubuntu-partition

I know this question has probably been asked before, but I am having trouble finding an answer specific to my problem and I really don't want to ruin my machine and have to reinstall both operating systems.

Basically:

  1. Windows 7 was installed.

  2. I installed Ubuntu with only 30GB of space.

  3. I am running out of space on Ubuntu so I want to extend the partition.

  4. I shrank the Windows partition using GParted on a live USB drive.

Now I have an unallocated partition that I would like to use to extend Ubuntu. The unallocated partition comes before the Ubuntu partition.

Is it safe to do so?

Note: I know I must use GParted through a live USB and all my data is already backed up.

Install rt3572 driver for Asus Usb-N53 Adapter https://askubuntu.com/questions/419984/install-rt3572-driver-for-asus-usb-n53-adapter

I recently bought the asus USB-N53 wireless adapter, and want to install the latest driver for it. It comes with instructions of how to install the driver from the files provided, but I can't use makefile, so can't install the driver correctly. These are the instructions from the readme file included:

=======================================================================

Build Instructions:

  1. tar -jxvf 2011_1003_RT3572_Linux_STA_v2.5.0.0.DPO.tar.bz2 go to ./2011_1003_RT3572_Linux_STA_v2.5.0.0.DPO directory.

  2. switch to super user. ** for Fedora

    $ su
    

    ** for Ubuntu

    $ sudo su
    
  3. in Makefile

    set the "MODE = STA" in Makefile and chose the TARGET to Linux by set "TARGET = LINUX"
    

    define the linux kernel source include file path LINUX_SRC modify to meet your need.

  4. in os/linux/config.mk define the GCC and LD of the target machine define the compiler flags CFLAGS modify to meet your need.

    ** Build for being controlled by NetworkManager or wpa_supplicant wext functions Please set HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y. => #> cd wpa_supplicant-x.x => #> ./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d

    ** Build for being controlled by WpaSupplicant with Ralink Driver Please set HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n. => #> cd wpa_supplicant-0.5.7 => #> ./wpa_supplicant -Dralink -ira0 -c wpa_supplicant.conf -d

  5. compile driver source code $ make

=======================================================================

Install Instructions:

  1. load driver

       $ make install   
    
  2. plug in USB dongle.

=======================================================================

Can somebody help me to use makefile to install the driver?

EDIT: When I ran uname -R, the terminal outputted 3.2.0-58-generic-pae. When I ran lsusb, the terminal outputted:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0ac8:3450 Z-Star Microelectronics Corp. 
Bus 001 Device 004: ID 0b05:179d ASUSTek Computer, Inc. 
Bus 003 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Bus 002 Device 002: ID 05fc:0231 Harman Multimedia 
Chromebook boot pendrive https://askubuntu.com/questions/317028/chromebook-boot-pendrive

i want to create bootable ubuntu-live pendrive on chromebook. I have Crouton (13.04, KDE), but the usb-creator-kde package is not included. I tried to install Unetbootin, grub, syslinux , but none of them succeeded. Does anyone have the solutions? thanks

What does “ping: sendmsg: No buffer space available” mean? https://askubuntu.com/questions/210451/what-does-ping-sendmsg-no-buffer-space-available-mean

I had an intermittent issue (which resolves itself spontaneously, after using a different connection for a while) that caused Internet requests to fail, with one particular wireless network. After about 5 requests after associating with an AP, ping would report the error

ping: sendmsg: No buffer space available

just as in Wifi connected but no data transfer: "ping: sendmsg: No buffer space available".

In case it's relevant, I'm seeing with a Centrino Ultimate-N 6300 [8086:4238] wireless interface on a Thinkpad X201. Bug #836250 is possibly related.

While I can work around this issue, I was wondering: What does this error message mean? In particular, what buffer is it talking about?

Reading AVCHD/M2TS files https://askubuntu.com/questions/31828/reading-avchd-m2ts-files

I have a Sony Camcorder which records AVCHD discs that contains M2TS. How can these files be read under Ubuntu?

A fresh installation of 10.10 will open the files but the playback is very choppy. The same thing goes when trying to add with OpenShot.

I found the following post which suggests to repackage with ffmpeg to an MKV file, which in my situation did not help: http://ubuntuforums.org/showthread.php?t=1627194