Ubuntu on RPi doesn't use eth0 by default https://askubuntu.com/questions/1563070/ubuntu-on-rpi-doesnt-use-eth0-by-default

I consider myself a beginner as far as the Linux world is concerned. Please bear with me. I searched the topic but it appears to be a different problem here.

I wanna play a bit with one of my RaspberryPi and setup a Nginx server to explore it's reverse proxy function. Hence, latency is a topic. The issue with this RPi (tried setting it up multiple times) is, that the eth0 interface isn't automatically activated. That's weird because the interface is directly connected to my router. I can activate the interface without any errors and receive an IP from the DHCP server immediately when I fire the command dhclient eth0.

For whatever reason, after every reboot or some time, the eth0 interface goes down and the RPi uses the wlan0 interface instead. I tried amending the config file to deactivate the wlan0 interface but that caused the device to not be reachable at all. Looks like only the manual dhclient call can start the eth0 interface.

What should I check or change to make sure there's no hardware issue and why does my RPi not preferably use the eth0 interface as it should? (It's freshly installed, no changes made to the default network configuration that I'm aware of)

Thanks so much for any help!

1 of 2 monitors not receiving signal after waking up from power management sleep https://askubuntu.com/questions/1563069/1-of-2-monitors-not-receiving-signal-after-waking-up-from-power-management-sleep

When my laptop wakes up from a power management suspend/sleep I have a monitor that doesn't start to receive a signal again. When I unplug it and plug it back in the monitor starts to get a signal again.

I have 2 external monitors,

  • One is attached through a ThinkPad dock/hub -> a kvm switch -> an HDMI connection to the monitor. Weirdly this one is the one that is working. It's a 24" Dell monitor
  • One directly connected to my HDMI port on my laptop. This one is a 49' 8k ultrawide screen Dell monitor.

My base system is:

  • ThinkPad Carbon
  • Ubuntu 22.02
  • i3 window manager
  • Running boxthrough X

Below is the debugging info that I have collected so far.

  • xrandr shows the monitor as still connected.
  • I don't see anything in the udev logs that looks like a cause.
  • I don't see any errors that look hardware related through. journalctl(journalctl | grep -C 100 -E 'PM: suspend (entry|exit)). There is a warning about the HDMI monitors about it being a weird aspect ratio. "consider adding a quark"
  • turning the monitor off and on doesn't fix it. Physically unplugging it and plugging it back in does.
  • sudo get-edid | parse-edid is of limited help. It fails with errors on monitors that work and the one with a problem.
  • The monitor works fine in gnome-3 and Wayland. It suspends and wakes up just fine.

I dont think its a driver issue or and issue reading the monitor information from the device itself since the monitor eventually comes back if its unplugged and plugged back in.

What are the next log files I should look in, or what is the next thing I should try?

Blue Screen on Boot after installing Kubuntu 25.10 (Plasma 6) on Asus Laptop (NVIDIA Graphics) https://askubuntu.com/questions/1563068/blue-screen-on-boot-after-installing-kubuntu-25-10-plasma-6-on-asus-laptop-nv

I recently installed the new Kubuntu 25.10 on my Asus X556UQK laptop (Intel + NVIDIA 940MX). The installation went smoothly, but after the first reboot, I was stuck on a dark blue/black screen and couldn't reach the login manager (SDDM).

If you are facing a similar issue where the system boots but the GUI doesn't start, here is how I fixed it:

1. Access the Terminal (TTY)

When stuck on the black screen, press Ctrl + Alt + F2 (or F3/F4). This allowed me to log in via the command line.

2. Update and Install NVIDIA Drivers

It turns out the default open-source drivers were struggling with the new Plasma 6 environment on my hardware. I ran these commands:

sudo apt update

sudo apt full-upgrade

sudo ubuntu-drivers install

The last command automatically detected and installed the NVIDIA 580 (or 550) proprietary drivers.

3. Disable Wayland (If needed)

Kubuntu 25.10 defaults to Wayland. Since NVIDIA and Wayland can sometimes conflict on older hybrid laptops, I forced the system to use X11 for the login manager:

* Open the SDDM config: sudo nano /etc/sddm.conf

* Add these lines:

[General]

DisplayServer=x11

* Save and exit (Ctrl+O, Enter, Ctrl+X).

4. Final Reboot

After a sudo reboot, the system finally loaded the Plasma 6 desktop perfectly!

Specs:

* OS: Kubuntu 25.10

* Kernel: 6.17.0-8-generic

* GPU: NVIDIA GeForce 940MX (NVIDIA 580 drivers)

* Laptop: Asus X556UQK

I hope this helps anyone else struggling with a fresh install!

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

looking for a GUI screen video w/audio capture app for Ubuntu 24.04lts - search on AskUbuntu pulls up stuff 10-15 years old with things no longer in existence... same with search engines.

Ubuntu Software only has recording junk - most do not even open, have no GUI, or open and locks up like not working with Wayland.

That print screen thing only records video - no audio.

VLC says can capture 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... seems there should be something more user friendly!?!

Boot issue on um 880 stuck in grub, and root is in lvm file.It says no recovery nomodset dis_ucode_ldr. I have recovery grub page looking for help https://askubuntu.com/questions/1563066/boot-issue-on-um-880-stuck-in-grub-and-root-is-in-lvm-file-it-says-no-recovery

I just got a bare bone pc(um880) that I installed linux on. I did not back it up,and it got corrupted! My root is stuck in lvm/vgmint-root, I think thd rest of files are on hd0,gpt2. The linux line says no recovery nomodeset dis_ucode_ldr. Thanks

How to use dual Nvidia Grace Hopper as a single memory block for computations https://askubuntu.com/questions/1563065/how-to-use-dual-nvidia-grace-hopper-as-a-single-memory-block-for-computations

I have access to a dual Grace Hopper GPU on a remote server. I was told that it should be possible to use the two GH200 on this dual chip as a single memory block for a computation. However, I'm having difficulty finding information as to how to do this, and all jobs I send seem to be directed to either one GPU or the other.

Can someone point me to the relevant information, or just tell me if I'm wrong?

I run my scripts in python. Can someone point me in the right direction? The output of the nvidia-smi command is:Output of nvidia-smi for dual GH

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 apt upgrade on a server on Ubuntu 24.04.3 LTS, I cannot upgrade the package linux-firmware.

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. Never experienced this issue in 12 years working with Ubuntu. Any suggestions would be appreciated.
Thanks 
jamesp
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?

Automated (cloud-init) install of 22.04 Server on machine with 4GB RAM https://askubuntu.com/questions/1563062/automated-cloud-init-install-of-22-04-server-on-machine-with-4gb-ram

I have a PXE server set up, network booting from the Ubuntu 22.04.1 live server ISO. I am attempting to automate the Subiquity installation process using cloud-init.

The kernel command line parameters I'm using are:

/jammy/22.04.1/vmlinuz ip=dhcp url=http://myserver/isos/ubuntu-22.04.1-live-server-amd64.iso ds=nocloud-net;s=http://myserver/config/
  • The ISO is about 1.5GB.

  • The files user-data and meta-data both exist in myserver/config/.

  • The machine has 4GB RAM.

I can successfully go through the install process manually if I don't use cloud-init. However, when attempting to use it, the cloud-init process keeps getting killed after running out of memory during the startup sequence, then the installer hangs on "waiting for cloud-init...".

  • I hand-wavily tried limiting the ramdisk size to the size of the ISO via a ramdisk_size=1500000 kernel parameter but it had no effect on the end result.

  • I also tried using the cloud-config-url parameter (instead of ds) to point directly to the user-data URL but that just seemed to be ignored and the manual install process ran.

  • I tried looking for a smaller ISO image but discovered that the minimized ISO images haven't been available for Ubuntu since 20.04.

  • I tried following these instructions (as closely as possible) to modify the ISO itself and add user-data directly into it. The ISO modification process worked but cloud-init still ran out of memory on boot.

I'm not sure why cloud-init needs so much memory. Is there some way to make cloud-init work on a machine with 4GB RAM? Alternatively, is there some way to have it use the ISO without downloading the entire thing to RAM first (which I'm assuming would leave enough memory for cloud-init to run)?

Please let me know if I've used any terms incorrectly or am missing any info, this is my first time trying to set up an automated network Ubuntu install; I am used to the Debian installer.

Ubuntu Server: mirroring display WITHOUT installing desktop https://askubuntu.com/questions/1563048/ubuntu-server-mirroring-display-without-installing-desktop

I am trying to install Ubuntu Server (24.04 or 26.04 snapshot2) on a server-ish motherboard (Gigabyte MC62-G40) that has an onboard BMC with a VGA port. Unfortunately, there seems to be a problem with the hardware so that, although I can see the output through the BMC using the H5 remote viewer, nothing is actually shown to the monitor. It remains in hibernate mode.

I have installed a second graphics card (Radeon HD6450) but, for some reason, the BIOS cannot be encouraged to use it over the onboard one. So when Ubuntu Server launches I can still only see the output via the H5 viewer. Again, nothing is shown on the external monitor.

I can install Desktop and then set the displays to Mirror. This has the desired effect and I can see the output on the monitor. However, this only occurs after I have logged in - which is tricky with a blank screen!

I'd like to avoid installing Desktop if I can so is there another way to make the displays mirror?

I've reloaded 24.04 and updated everything. It still behaves the same. I've tried toggling the 'Server Monitor OFF Feature Status' and that doesn't help. For a block diagram of the Gigabyte MC62-G40 board and the connections to the BMC, see below image:

Gigabyte MC62-G40 block diagram

Backspace and Enter buttons aren't working when I resume from sleep on ThinkPad T14s https://askubuntu.com/questions/1562973/backspace-and-enter-buttons-arent-working-when-i-resume-from-sleep-on-thinkpad

In the last week, after some update, either firmware or Ubuntu update, the backspace and Enter buttons don't work after I open the lip of the laptop. I can't figure out the incantation that will make those buttons work so that I can login.

Sometimes Fn+F7 makes it work, sometimes just waiting 2 minutes, sometimes it's Ctrl+F7, etc. I've tried a few and mostly can repeat the sequence. The buttons work perfectly after logging in or after a reboot, so something in the suspend or resume is locking up these keys. Do you have any idea on how to diagnose this so I can reply with better detail, or ideas on how to fix it?

UPDATE 1 day later:

I tried not pressing random keys and just waiting: works. the wait time was 5mins. Also got a clanker to help with diagnosis. It told me that keyboard loads fine but power management was the issue. here is some of the output.

ThinkPad T14s Keyboard Issue Diagnosis

Problem Summary

  • Hardware: ThinkPad T14s Gen 2i
  • Issue: Enter and Backspace keys stop working after reboot/suspend
  • Timeline: Started ~1 week ago after system update
  • Current Status: Intermittent failure, keys work sometimes

System Information

  • OS: Ubuntu 24.04.3 LTS (noble)
  • Current Kernel: 6.14.0-37-generic (problematic)
  • Available Rollback: 6.14.0-36-generic
  • Hardware: Lenovo ThinkPad T14s Gen 2i
  • Firmware: N35ET63W (1.63) - Wed 2025-07-09

Diagnostic Results

Hardware Detection ✅

AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
  • Keyboard properly detected via i8042 controller
  • No hardware initialization errors
  • All input devices working normally

Kernel Logs ✅

# Clean dmesg output - no keyboard errors
[    0.767098] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
  • No driver errors or timeouts
  • Proper initialization at boot
  • Rules out kernel driver regression

Power Management ⚠️

# Problematic power management settings
/sys/devices/platform/i8042/serio0/power/control: auto
/sys/devices/platform/i8042/serio0/power/runtime_status: unsupported

Root Cause: Power Management Issue

This is a power management regression in kernel 6.14.0-37:

  1. Keyboard initializes correctly at boot
  2. Fails after suspend/resume due to PM conflicts
  3. Recovery happens when power management stabilizes
  4. Conflicting "auto" control with "unsupported" runtime status

Solutions

Solution 1: Kernel Rollback (Recommended)

# Boot to GRUB menu (hold Shift during boot)
# Select: Ubuntu, with Linux 6.14.0-36-generic

# Or set default via command line:
sudo grub-set-default "1>Ubuntu, with Linux 6.14.0-36-generic"
sudo update-grub
sudo reboot

Solution 2: Power Management Fix

# Temporary fix (until next reboot)
echo 'on' | sudo tee /sys/devices/platform/i8042/serio0/power/control

# Permanent fix - add to startup
echo 'echo on > /sys/devices/platform/i8042/serio0/power/control' | sudo tee /etc/rc.local
sudo chmod +x /etc/rc.local

Solution 3: Emergency Keyboard Reset

# Create fix script for when keys fail
cat > ~/fix-keyboard.sh << 'EOF'
#!/bin/bash
echo "Resetting keyboard..."
sudo rmmod atkbd 2>/dev/null
sudo modprobe atkbd
echo "Keyboard reset complete"
EOF

chmod +x ~/fix-keyboard.sh

Available Kernels

ii  linux-image-6.14.0-36-generic   6.14.0-36.36~24.04.1   (working)
ii  linux-image-6.14.0-37-generic   6.14.0-37.37~24.04.1   (problematic)

GRUB Boot Access

  • Hold Shift key during boot to access GRUB menu
  • Select "Advanced options for Ubuntu"
  • Choose "Ubuntu, with Linux 6.14.0-36-generic"

Input Device Details

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds

Next Steps

  1. Test kernel rollback - Use 6.14.0-36 for several days
  2. Monitor: Check if issue resolved with older kernel
  3. Report: Submit bug report if rollback confirms the regression
  4. Watch: Monitor for kernel updates that fix the issue

Commands Used for Diagnosis

# System info
uname -r
hostnamectl
lsb_release -a

# Hardware detection
cat /proc/bus/input/devices
lsmod | grep -E "atkbd|i8042|input|thinkpad"

# Logs and errors
sudo dmesg | grep -i "keyboard|input|atkbd|error"
sudo journalctl -k | grep -i keyboard

# Available kernels
dpkg --list | grep linux-image
ls /boot/vmlinuz-* | sort -V

# Power management
cat /sys/devices/platform/i8042/serio0/power/control
cat /sys/devices/platform/i8042/serio0/power/runtime_status

Status: Ready for kernel rollback test

update 2: its desktop ubuntu. @guiverc i rolled back to the 36 kernel . did not solve the problem i reinstalled a 24.04.03 LTS. did not solve the problem. well, not totally, its sometimes works and sometimes does not. which is terrible for testing and feedback. i am sure they worked in BIOS menus. But im in the bios for a few minutes only. so i have not had a non-working bios experience.

for now, im using some keyboard remapper. del=backspace and rightctrl=enter.

i am hesitating ordering a replacement keyboard because official manual says i need the whole plastic cover and stuff with the membrane keyboard. but if its software related problem, then replacement hardware wont solve it.

i wonder if this was a firmware update that was done prior to the problem and the firmware was badly coded/tested. its hard to know because firmware description is cryptic and ubuntu doesnt have date displayed on update date. i dont want to be rolling back firmware if i can avoid it.

Command to change Gnome-terminal Font on Ubuntu 24.04 LTS? https://askubuntu.com/questions/1562955/command-to-change-gnome-terminal-font-on-ubuntu-24-04-lts

Setup

Fresh install of ubuntu 24.04 LTS & I have installed a new font under .local/share/fonts.

What I'm trying to do:

I want to change the font that the default gnome-terminal uses but through a command as I can't use the GUI for my purpose as I'm writing a script for this.

I have tried to use the gsettings list-keys org.gnome.Terminal.Legacy.Settings which gives the following output:

always-check-default-terminal
confirm-close
context-info
default-show-menubar
headerbar
menu-accelerator-enabled
mnemonics-enabled
new-tab-position
new-terminal-mode
schema-version
shell-integration-enabled
shortcuts-enabled
tab-policy
tab-position
theme-variant
unified-menu

But I don't see the key that would change the font among the keys.

I have seen a previous post which suggests to use gconftool-2 but I believe this is deprecated and no longer works in ubuntu 24.04.

Is there a new CLI utility I can use to achieve this changing of the font for GNOME-terminal on ubuntu 24.04 LTS, cause I haven't been able to find it other than gsettings? Any help is appreciated thank you.

EDIT: I believe this question is different than this post referenced in the comment by @graham, because it talks about command line changing of font using the 'gsettings' command on a much newer version of Ubuntu.

Unable to access ssh server, (no route to host error) https://askubuntu.com/questions/1562674/unable-to-access-ssh-server-no-route-to-host-error

Unable to access ssh server, (no route to host error)

Using HP laptops, both installed with Lubuntu 24.04 LTS and on the same WiFi LAN

Client:

   PCManFM-Qt File Manager
   Go -> Connect to Server
   Type = SSH
   Host = Server IP address
   Port = 22 (default)
   Path = leave clear
   Log in as = Server user name

Server:

   sudo service ssh status
   enabled active and running

   sudo ufw allow OpenSSH

  • Uninstalled & reinstalled server.
  • Updated ufw rules (port number 54321) on both server and client.
  • Started from scratch using ("Connect two computers with SSH in a home LAN").
  • ssh-copy-id worked this time. (Number of key(s) added: 1)

Set passwordAuthentication no, disabled root login, set port number to 54321 in /etc/ssh/sshd_config

sudo systemctl restart ssh
  • Disabled the password based authentication, but File manager is still asking me for a password to log-in?

The last thing I tied is this:

ssh -i ~/.ssh/id_ed25519 name@192.168.1.153 -p 54321

All working now using ssh keys with PasswordAuthentication no set. No longer asking for a password to login.

Help with Ubuntu boot https://askubuntu.com/questions/1530997/help-with-ubuntu-boot

These messages were copied from a session in Recovery mode:

Press Enter for maintenance
(or press Control-D to continue):
(base) root@jordans-msi-laptop:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1.6G  2.1M  1.6G   1% /run
/dev/nvme0n1p2  937G   87G  803G  10% /
tmpfs           7.7G     0  7.7G   0% /dev/shm
tmpfs           5.0M   12K  5.0M   1% /run/lock
efivarfs        192K  118K   70K  63% /sys/firmware/efi/efivars
/dev/nvme0n1p1  1.1G  6.2M  1.1G   1% /boot/efi
(base) root@jordans-msi-laptop:~#
[FAILED] Failed to start systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer.
See 'systemctl status systemd-oomd.service' for details.
[  OK  ] Finished plymouth-quit-wait.service - Hold until boot process finishes up.
[  OK  ] Finished plymouth-quit.service - Terminate Plymouth Boot Screen.
[FAILED] Failed to start gnome-remote-desktop.service - GNOME Remote Desktop.
[FAILED] Failed to start bluetooth.service - Bluetooth service.
[FAILED] Failed to start dbus.service - D-Bus System Message Bus.
[FAILED] Failed to start bolt.service - Thunderbolt system service.
[FAILED] Failed to start power-profiles-daemon.service - Power Profiles daemon.
[FAILED] Failed to start systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer.
[FAILED] Failed to start gnome-remote-desktop.service - GNOME Remote Desktop.
[FAILED] Failed to start bluetooth.service - Bluetooth service.
[  5.322412] ACPI BIOS Error (bug): Could not resolve symbol [_TZ.ETMD], AE_NOT_FOUND (20230628/psargs-330)
[  5.322472] ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
[FAILED] Failed to start systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer.
[FAILED] Failed to start bolt.service - Thunderbolt system service.
[FAILED] Failed to start thermald.service - Thermal Daemon Service.
[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 listen on dbus.socket - D-Bus System Message Bus Socket.
[DEPEND] Dependency failed for gnome-remote-desktop.service - GNOME Remote Desktop.
[FAILED] Failed to listen on dbus.socket - D-Bus System Message Bus Socket.
[DEPEND] Dependency failed for bluetooth.service - Bluetooth service.
[FAILED] Failed to listen on dbus.socket - D-Bus System Message Bus Socket.
[DEPEND] Dependency failed for thermald.service - Thermal Daemon Service.
[DEPEND] Dependency failed for bolt.service - Thunderbolt system service.
[DEPEND] Dependency failed for power-profiles-daemon.service - Power Profiles daemon.
[FAILED] Failed to listen on dbus.socket - D-Bus System Message Bus Socket.
[DEPEND] Dependency failed for gdm.service - GNOME Display Manager.
[FAILED] Failed to start snap.cups.cups-browsed.service - Service for snap application cups.cups-browsed.
[FAILED] Failed to start snap.cups.cupsd.service - Service for snap application cups.cupsd.
[FAILED] Failed to start rsyslog.service - System Logging Service.

I recently installed Ubuntu, and was seeing if I could dual boot Windows from Ubuntu. I think I messed around with one of the partitions (it let me unmount it, so I didn't think anything was wrong), then after a few minutes stuff started freezing up. I shut down my laptop, turned it back on and was met with a long boot, followed by this black screen. I'm not sure what to do from here. I'm completely out of my depth. I use a MSI Raider laptop.

Failed to mount "917 MB Volume" https://askubuntu.com/questions/1529980/failed-to-mount-917-mb-volume

I'm a new user, following the [official guide][1] to install Ubuntu 24.04.1 LTS, and whenever I try to actually install it on my new PC, it keeps giving me an error message saying:

Error mounting /dev/loop2 at /media/ubuntu/disk: /dev/loop2 already mounted or mount point busy

Does anyone know how to fix this?

If it helps, I'll note that I built my PC (for the first time)

EDIT 1: For those asking:

  • I downloaded the Ubuntu 24.04.1 LTS image
  • Flashed it onto a USB drive using balenaEtcher
  • Plugged it into my new PC before booting it
  • Followed the instructions of the installation wizard exactly
  • Chose interactive installation, extended selection, both recommended software options
  • Finally chose to erase the disk and install.

Additionally, the PC I built was only connected to the internet via ethernet cable

EDIT 2: My PC boots in UEFI mode, has 64 GB RAM, and a 2TB SSD

Also, I'm so new to Linux that I don't know how to run something like:

sudo fdisk -l (ele)

EDIT 3:

I forgot to mention this in my original question because of everything else going on, but sometime when I get to the disk setup stage, it only gives me the option of manual installation, and when I attempt to follow a tutorial to do so, it crashes, and only then gives me more options

EDIT 5:

This turned out to be a hardware issue, due to me not connecting my SSD to the power supply (it was only connected to the motherboard).

Apologies for not specifying this for 1 year, I legitimately forgot about this post once the problem was solved

Server is not coming up with Ubuntu 22.04 live server image [duplicate] https://askubuntu.com/questions/1464708/server-is-not-coming-up-with-ubuntu-22-04-live-server-image

I am trying to build a new Ubuntu 22.04.1 live server image.

[  OK  ] Finished Message of the Day.
[**    ] (1 of 3) A start job is running for Ubuntu Advantage Timer for running repeated jobs (2min 34s / no limit)
[ 1146.702132] blk_update_request: critical medium error, dev sr0, sector 2415116 op 0x0:(READ) flags 0x84700 phys_seg 24 prio 0
[**    ] (3 of 3) A start job is running for Wait until snapd is fully seeded (26min 36s / no limit)
[  OK  ] Stopped Getty on tty2.

The hardware is a Dell PowerEdge R540

In the installation screen I chose "try or Install" option but the server is not coming up with continuous jobs running for more than 30 minutes.

  • A start job is running Wait until snapd is fully seeded.
  • A start job is running casper-md5check Live ISO checksum.
Squid Proxy and Certificate problem https://askubuntu.com/questions/1460195/squid-proxy-and-certificate-problem

Recently i installed squid proxy on Ubuntu 18.04 and it was working fine for the http requests , but i faced a problem with some applications that require https connection , so i downloaded the source and compiled it with the following configuration options :

squid -v 
Squid Cache: Version 4.17
Service Name: squid

This binary uses OpenSSL 1.1.1  11 Sep 2018. For legal restrictions on distribution see https://www.openssl.org/source/license.html

configure options:  '--enable-ssl-crtd' '--with-openssl'

What i want is just to use squid to pass http/https traffic through it from a remote system due to some geo restrictions and regardless of the application used , But when i used the certificate for http/https ports , no traffic is passed at all ! only http port works if i don't use any cert with it .

I followed the instructions mentioned here to generate the cert (alternate method) ,created and Initialized the SSL database and also imported the cert in the browser and system wide ,but still no luck:

Installing and configuring Squid Proxy for SSL (Bumping or Peek-n-splice)

squid.conf:

acl all src all
http_access allow all
dns_v4_first on
#
# Recommended minimum configuration:
#

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 0.0.0.1-0.255.255.255  # RFC 1122 "this" network (LAN)
acl localnet src 10.0.0.0/8     # RFC 1918 local private network (LAN)
acl localnet src 100.64.0.0/10      # RFC 6598 shared address space (CGN)
acl localnet src 169.254.0.0/16     # RFC 3927 link-local (directly plugged) machines
acl localnet src 172.16.0.0/12      # RFC 1918 local private network (LAN)
acl localnet src 192.168.0.0/16     # RFC 1918 local private network (LAN)


acl SSL_ports port 443
acl Safe_ports port 80      # http
acl Safe_ports port 21      # ftp
acl Safe_ports port 443     # https
acl Safe_ports port 70      # gopher
acl Safe_ports port 210     # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280     # http-mgmt
acl Safe_ports port 488     # gss-http
acl Safe_ports port 591     # filemaker
acl Safe_ports port 777     # multiling http
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#
# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
#http_access deny all

# Squid normally listens to port 3128
http_port 3128 ssl-bump cert=/usr/local/squid/etc/certs/squid-ca-cert-key.pem generate-host-certificates=on dynamic_cert_mem_cache_size=4MB
https_port 3129 intercept ssl-bump cert=/usr/local/squid/etc/certs/squid-ca-cert-key.pem generate-host-certificates=on dynamic_cert_mem_cache_size=4MB

acl step1 at_step SslBump1                       
ssl_bump peek step1                       
ssl_bump bump all
sslcrtd_program /usr/local/squid/libexec/security_file_certgen -s /usr/local/squid/var/cache/squid/ssl_db -M 4MB
sslcrtd_children 5
ssl_bump server-first all
sslproxy_cert_error allow all
# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /usr/local/squid/var/cache/squid 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /usr/local/squid/var/cache/squid

#
# Add any of your own refresh_pattern entries above these.
#
refresh_pattern ^ftp:       1440    20% 10080
refresh_pattern ^gopher:    1440    0%  1440
refresh_pattern -i (/cgi-bin/|\?) 0 0%  0
refresh_pattern .       0   20% 4320

cache.log:

2023/03/20 16:38:28| Created PID file (/usr/local/squid/var/run/squid.pid)
2023/03/20 16:38:28 kid1| Set Current Directory to /usr/local/squid/var/cache/squid
2023/03/20 16:38:28 kid1| Starting Squid Cache version 4.17 for x86_64-pc-linux-gnu...
2023/03/20 16:38:28 kid1| Service Name: squid
2023/03/20 16:38:28 kid1| Process ID 85942
2023/03/20 16:38:28 kid1| Process Roles: worker
2023/03/20 16:38:28 kid1| With 655350 file descriptors available
2023/03/20 16:38:28 kid1| Initializing IP Cache...
2023/03/20 16:38:28 kid1| DNS Socket created at [::], FD 9
2023/03/20 16:38:28 kid1| DNS Socket created at 0.0.0.0, FD 13
2023/03/20 16:38:28 kid1| Adding nameserver 127.0.0.53 from /etc/resolv.conf
2023/03/20 16:38:28 kid1| Adding nameserver 8.8.8.8 from /etc/resolv.conf
2023/03/20 16:38:28 kid1| Adding nameserver 8.8.4.4 from /etc/resolv.conf
2023/03/20 16:38:28 kid1| helperOpenServers: Starting 5/5 'security_file_certgen' processes
2023/03/20 16:38:28 kid1| Logfile: opening log daemon:/usr/local/squid/var/logs/access.log
2023/03/20 16:38:28 kid1| Logfile Daemon: opening log /usr/local/squid/var/logs/access.log
2023/03/20 16:38:28 kid1| Store logging disabled
2023/03/20 16:38:28 kid1| Swap maxSize 0 + 262144 KB, estimated 20164 objects
2023/03/20 16:38:28 kid1| Target number of buckets: 1008
2023/03/20 16:38:28 kid1| Using 8192 Store buckets
2023/03/20 16:38:28 kid1| Max Mem  size: 262144 KB
2023/03/20 16:38:28 kid1| Max Swap size: 0 KB
2023/03/20 16:38:28 kid1| Using Least Load store dir selection
2023/03/20 16:38:28 kid1| Set Current Directory to /usr/local/squid/var/cache/squid
2023/03/20 16:38:28 kid1| Finished loading MIME types and icons.
2023/03/20 16:38:28 kid1| HTCP Disabled.
2023/03/20 16:38:28 kid1| Squid plugin modules loaded: 0
2023/03/20 16:38:28 kid1| Adaptation support is off.
2023/03/20 16:38:28 kid1| Accepting SSL bumped HTTP Socket connections at local=[::]:3128 remote=[::] FD 26 flags=9
2023/03/20 16:38:28 kid1| Accepting NAT intercepted SSL bumped HTTPS Socket connections at local=[::]:3129 remote=[::] FD 27 flags=41
2023/03/20 16:38:29 kid1| storeLateRelease: released 0 objects

access.log:

1679355519.102      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.554      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.555      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.556      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.556      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.557      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.558      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.559      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.559      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.560      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
1679355622.561      0 192.168.0.106 NONE_ABORTED/200 0 CONNECT 192.168.0.106:3129 - HIER_NONE/- -
ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.106  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::2xx:xxxx:fexx:xxxx  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 347695  bytes 334612753 (334.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 281191  bytes 166987314 (166.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So what am I doing wrong here ? and as i mentioned before , all i want is just to pass all the traffic without any restrictions through squid (like a public proxy) so if there is a fix or any alternative method for this please let me know .

Regards

How can I setup a dual boot of Ubuntu 22.04 and Windows 7? https://askubuntu.com/questions/1458822/how-can-i-setup-a-dual-boot-of-ubuntu-22-04-and-windows-7

Sorry if this question has already been answered, but there is a lot of information online and I am not sure what to do.

What I want, is a system where I can boot into Ubuntu or Windows from my computer startup. I think this is done by using GRUB but I'm not sure.

Here is everything that I have:

I have 3 disks:

  • /dev/sda which is a 250GB HDD formatted to ext4 and is just for my files and stuff

    (gparted screenshot)

  • /dev/sdb which is a 240GB SATA SSD that contains Linux and /home

    (gparted screenshot)

  • /dev/sdc which is a 160GB HDD formatted ntfs that contains Windows

    (gparted screenshot)

When I boot up my computer, it boots into GRUB and asks me what I want to boot up.

To get this to work originally, I had to change some stuff in /etc/default/grub. Here is what it looks like (top half only):

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

I changed GRUB_TIMEOUT_STYLE from hidden to menu, and I changed GRUB_TIMEOUT from 0 to 10.

The GRUB menu though only shows Ubuntu, Advanced Options for Ubuntu, and 2 memory tests.

After that I installed Boot-Repair using:

$ sudo add-apt-repository ppa:yannubuntu/boot-repair
$ sudo apt-get update
$ sudo apt-get install -y boot-repair

and I ran it using $ boot-repair, clicked Recommended Repair, and it output:

GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again.
Alternatively, you can retry after activating the [Separate /boot/efi partition:] option.

According to other answers, I think I need to create an unformatted partition and give it the flag bios_grub, but I'm not sure.

Extra info:

  • $ neofetch returns:

    neofetch

  • $ sudo os-prober returns: /dev/sdc1:Windows 7:Windows:chain.
Ubuntu 18.04 cannot boot problems https://askubuntu.com/questions/1434399/ubuntu-18-04-cannot-boot-problems

I am using Ubuntu 18.04 and it works well, but when I turned on my computer this morning the following problem occurred.

Starting WPA supplicant...
[  OK  ] Started Run anacron jobs.
[  OK  ] Reached target Login Prompts.
Starting Detect the available GPUs and deal with any system changes...
[  OK  ] Started Set the CPU Frequency Scaling governor.
Starting Modem Manager...
Starting LSB: Speech Dispatcher...
Starting Network Manager...
Starting LSB: automatic crash report generation...
Starting Bluetooth service...
Starting Accounts Service...
Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
Starting LSB: Record successful boot for GRUB...
Starting Snap Daemon...
Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started CUPS Scheduler.
Starting Login Service...
Starting Thermal Daemon Service...
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started irqbalance daemon.
Starting Save/Restore Sound Card State...
Starting Disk Manager...
Starting Clean php session files...
[  OK  ] Started ACPI event daemon.
[  OK  ] Started System Logging Service.
[  OK  ] Started Raise network interfaces.
[  OK  ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started LSB: Speech Dispatcher.
[  OK  ] Started Login Service.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Make remote CUPS printers available locally.
[  OK  ] Started Bluetooth service.
[  OK  ] Reached target Bluetooth.
[  OK  ] Started Detect the available GPUs and deal with any system changes.
[  OK  ] Started LSB: Record successful boot for GRUB.
Starting Authorization Manager...
Starting Hostname Service...
[  OK  ] Started WPA supplicant.
[  OK  ] Started Hostname Service.
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Started Authorization Manager.
[  OK  ] Started Accounts Service.
[  OK  ] Started Modem Manager.
[  OK  ] Started Disk Manager.
How to reduce Ubuntu 20.04 boot time? https://askubuntu.com/questions/1413218/how-to-reduce-ubuntu-20-04-boot-time

I am new to Ubuntu 20.04. Please check my /etc/fstab and let me know if any changes are needed. When I login to my laptop, it takes 1 minute to show the Ubuntu logo and after that it takes 2 more minutes to complete the boot. I'm also not sure how my swap is 16 GB and how I can change it back to 8 GB.

# /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>
# / was on /dev/sda6 during installation
UUID=45fa4db9-9416-40fe-b268-02332f32681d /               ext4    errors=remou>
# swap was on /dev/sda7 during installation
UUID=d30e1bf1-c706-4f73-86a7-e8dce5bea2a2 none            swap    sw          >
/dev/disk/by-uuid/01D7628B35A0B620 /mnt/01D7628B35A0B620 auto nosuid,nodev,nof>
/swapfile swap swap defaults 0 0
How to run Timeshift from command line https://askubuntu.com/questions/1393507/how-to-run-timeshift-from-command-line

I'm struggling a bit with running Timeshift from command line. My disk structure look like this:

sda                         8:0    0   1.8T  0 disk
├─sda1                      8:1    0   512M  0 part /boot/efi
├─sda2                      8:2    0     1G  0 part /run/timeshift/backup
└─sda3                      8:3    0   1.8T  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   100G  0 lvm  /
sdb                         8:16   0 232.9G  0 disk
└─sdb1                      8:17   0 232.9G  0 part /run/timeshift/backup

So, I would like to create a backup on the sdb1 disk, using:

sudo timeshift --create --comments "Test" --tags D --snapshot-device /dev/sdb1

gives me the following:

Mounted '/dev/sdb1' at '/run/timeshift/backup'
------------------------------------------------------------------------------
Creating new snapshot...(RSYNC)
Saving to device: /dev/sdb1, mounted at path: /run/timeshift/backup
Linking from snapshot: 2022-02-17_19-34-54
Synching files with rsync...
Created control file: /run/timeshift/backup/timeshift/snapshots/2022-02-17_20-51-55/info.json
RSYNC Snapshot saved successfully (111s)
Tagged snapshot '2022-02-17_20-51-55': ondemand
------------------------------------------------------------------------------

However, when listing using timeshift --list, I get the following:

Mounted '/dev/sda2' at '/run/timeshift/backup'
Device : /dev/sda2
UUID   : acd80a0d-761d-441a-8e8a-b5cca5bf7ee9
Path   : /run/timeshift/backup
Mode   : RSYNC
Status : Not enough disk space (< 12.9 GB)
Select another device or free up some space

No snapshots found

Any suggestions on what I am doing wrong?

Tom

Problems with booting the system https://askubuntu.com/questions/1163516/problems-with-booting-the-system

I have yesterday updated packages and today the system cannot boot properly. After seeing the Kubuntu logo there is a black screen with boot messages which show repeatedly.

[  OK  ] Started Wait Until Snapd is fully seeded.
[  OK  ] Created slice User Slice of igor.
         Starting User Manager for UID 1000...
[  OK  ] Started Session 1 of user igor.
[  OK  ] Started User Manager for UID 1000.
[  OK  ] Started Music Player Daemon.
                                     [**    ] (1 of 2) A start job is running for […]

[  OK  ] Created slice User Slice of gdm.
         Starting User Manager for UID 121...
[  OK  ] Started Session c1 of user gdm.
[  OK  ] Started User Manager for UID 121.
         Starting Daemon for power management...
[  OK  ] Started Daemon for power management.
         Stopping User Manager for UID 121...
[  OK  ] Started Session c2 of user gdm.
         Starting User Manager for UID 121...
[  OK  ] Started User Manager for UID 121.
         Stopping User Manager for UID 1000...
[  OK  ] Stopped User Manager for UID 1000.
[  OK  ] Removed slice User Slice of igor.

         Stopping User Manager for UID 121...
[  OK  ] Stopped User Manager for UID 121.
[  OK  ] Removed slice User Slice of gdm.
[  OK  ] Created slice User Slice of gdm.
         Starting User Manager for UID 121...
[  OK  ] Started Session c3 of user gdm.
[  OK  ] Started User Manager for UID 121.
Error: "A connection to the bus can't be made" while trying to install Ubuntu 18.04 https://askubuntu.com/questions/1153334/error-a-connection-to-the-bus-cant-be-made-while-trying-to-install-ubuntu-18

I removed Ubuntu 14.04 and I want to install Ubuntu 18.04.

There may be some important files missing because I format some volumes.

This time I choose Ubuntu 18.04, and I put the installing image on USB flash disk, everything goes well before I click install.

I click install

I find that I can't install it, and there is an error.

failed to connect the bus

How can I handle it?

Gnome Panels and Task-Bar and Starter are gone / missing / disappeared https://askubuntu.com/questions/1127493/gnome-panels-and-task-bar-and-starter-are-gone-missing-disappeared

What happened?

Everything was working correctly, but then i did the following: Today, i started Ubuntu not with my current kernel like normally, but with an older Kernel, because i wanted to try something out.

After is started Ubuntu with the older kernel, i noted that all my gnome settings are gone/missing/disappeared.

For example:

  • My Background-image gone
  • Mouse-speed settings gone
  • Nautilus settings gone
  • Bottom-Task-Bar gone
  • Panels (like Top/Bottom-Panels) gone

--> My Desktop looks pretty empty, only the icons for folders/files are visible.

At this point, i was not frightened about that, because I thought, that the reason for all these "missing settings" was, that i am on an "older" kernel right now. So, i thought, my settings will be there again as normal, after changing back from the older to my current kernel.

BUT: After changing back to my current Kernel, all settings like Background-Image, Panels, ... are still missing :-(

I have a feeling, that the process, that runs gnome, does not have the correct access-rights anymore to read all my config-files (for Background, mouse-speed, Nautilus-settings, ....).

When logging in with Guest-Account, all Panels and Menu-Bars are there as normally adn are working correct. -> That means, all installed gnome packages are still working correctly, no need for any update or installation of things. It seems, its just a "settings-problem".

Can anyone help??

THANKS!!!!!


I am using:

  • gnome-session-fallback (Metacity)
  • indicator-applet-complete
  • 4.4.0-143-generic (current kernel)
  • Distributor ID: Ubuntu
  • Description: Ubuntu 14.04.6 LTS
  • Release: 14.04
  • Codename: trusty
x11vnc constantly closing in 18.04 LTS https://askubuntu.com/questions/1041597/x11vnc-constantly-closing-in-18-04-lts

I've been using this remote desktop solution several years ago, but seems to be a problem with the latest Ubuntu. It closes constantly when remote connecting. Hoy can I find where the problem is? Should I search for a .log or something?

I tried with several x11vnc -options and all hangs. And tried the 'apt install lightdm' solutions posted here but didn't work

Unable to mount internal hard-drive https://askubuntu.com/questions/988698/unable-to-mount-internal-hard-drive

My computer has an SSD and an internal hard drive. I tried to set things up so that the hard drive would mount automatically at startup. Unfortunately something must have gone wrong because I can't mount it at all. I tried to put things back the way they were with the backup copy of fstab that I made before starting, but that didn't help.

When I try to access my hard drive using Files, I get this message:

Unable to access “47862f8f-0d45-4f1e-94f1-bb9ce2b88d23”

mount: /etc/fstab: parse error: ignore entry at line 10.
mount: /dev/sdb2 is already mounted or /mnt/47862f8f-0d45-4f1e-94f1-bb9ce2b88d23 busy
       /dev/sdb2 is already mounted on /
       /dev/sdb2 is already mounted on /mnt/47862f8f-0d45-4f1e-94f1-bb9ce2b88d23

Here are the contents of fstab.

/dev/sda1

UUID=3b0c4420-5c63-4878-be41-357c7c47dd7e /dev/disk/by-uuid/c126cc7a-ab90-46d2-aafb-c26f94a5bcb4 >/home/allan/Documents/ExtraDrive ext4 user,nosuid,nodev,nofail,x-gvfs-show 0 0

/dev/sdb2

UUID=47862f8f-0d45-4f1e-94f1-bb9ce2b88d23 none swap sw 0 0 /dev/disk/by-uuid/47862f8f-0d45-4f1e-94f1-bb9ce2b88d23 /mnt/47862f8f->0d45-4f1e-94f1-bb9ce2b88d23 ext4 user,nosuid,nodev,nofail,x-gvfs-show 0 1

/dev/sdb3

UUID=3b0c4420-5c63-4878-be41-357c7c47dd7e /dev/disk/by-uuid/3b0c4420-5c63-4878-be41-357c7c47dd7e >/home/allan/Documents/ExtraDrive ext4 user,nosuid,nodev,nofail,x-gvfs->show 0 0

Connect to Cabinet //cabinet.usask.ca/work$ /mnt/cabinet cifs username=ajm195,noauto,user 0 0

This is the output of lsblk -f:

NAME   FSTYPE LABEL  UUID                                 MOUNTPOINT
sdb                                                       
├─sdb2 ext4   Ubuntu 47862f8f-0d45-4f1e-94f1-bb9ce2b88d23 /mnt/47862f8f-0d45-4f1
├─sdb3 swap          3b0c4420-5c63-4878-be41-357c7c47dd7e [SWAP]
└─sdb1                                                    
sr0                                                       
sda                                                       
└─sda1                  

Here is the output of df -k:

Filesystem     1K-blocks     Used Available Use% Mounted on
udev             1961612        0   1961612   0% /dev
tmpfs             396648    16552    380096   5% /run
/dev/sdb2      111117096 96395236   9054328  92% /
tmpfs            1983240    33852   1949388   2% /dev/shm
tmpfs               5120        4      5116   1% /run/lock
tmpfs            1983240        0   1983240   0% /sys/fs/cgroup
cgmfs                100        0       100   0% /run/cgmanager/fs
tmpfs             396648       80    396568   1% /run/user/1000

I'm running version 16.04.

Installing Ubuntu 16.04 alongside Windows 10, legacy BIOS non-UEFI https://askubuntu.com/questions/833042/installing-ubuntu-16-04-alongside-windows-10-legacy-bios-non-uefi

I'm trying to dual boot Ubuntu with Windows 10 (Legacy BIOS), but whenever I try and install, I get this:

dual boot

Is there a solution from here? Can I just press the option not to force UEFI, and carry on with installation?

I followed this guide exactly, but the "Force UEFI installation?" occurs at the "Preparing to install Ubuntu" stage.

Xubuntu 15.04 Gummiboot kernel panic https://askubuntu.com/questions/623717/xubuntu-15-04-gummiboot-kernel-panic

I installed my new Xubuntu 15.04 in EFI mode. I installed gummiboot via sudo apt-get install gummiboot and activating sudo gummiboot install.

On my HP Notebook I have to enter the efi file as custom boot as described here: EFI\Boot\bootx64.efi

(Without switching to gummiboot, namely booting with EFI\ubuntu\grubx64.efi, works)

Unfortunately I get a kernel panic when trying to boot.

4.020118] ACPI PCC probe failed.
4.071610] tpm_tis 00:05: A TPM error (7) occurred attempting to read a pcr value
4.072759] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
4.072789] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-16-generic #16-Ubuntu
4.072816] Hardware name: Hewlett-Packard HP EliteBook 820 G2/225A, BIOS M71 Ver. 01.05 03/26/2015
4.072847] ffffea0010f0a8c0 ffff88043d2bbdc8 ffffffff817c2235 00000000000025b0
4.072880] ffffffff81a81d28 ffff88043d2bbe48 ffffffff817bf78d ffff88043d2bbde8
4.072912] ffffffff00000010 ffff88043d2bbe58 ffff88043d2bbdf8 000000000000ffff
4.072944] Call Trace:
4.072959] [<ffffffff817c2235>] dump_stack+0x45/0x57
4.072979] [<ffffffff817bf78d>] panic+0xc1/0x1f5
4.072999] [<ffffffff81d4d4a7>] mount_block_root+0x209/0x2a5
4.073021] [<ffffffff81d4d6d9>] mount_root+0x54/0x58
4.073040] [<ffffffff81d4d84a>] prepare_namespace+0x16d/0x1a6
4.073062] [<ffffffff81d4d1bf>] kernel_init_freeable+0x1e4/0x1f9
4.073086] [<ffffffff817b6b10>] ? rest_init+0x80/0x80
4.073106] [<ffffffff817b6b1e>] kernel_init+0xe/0xf0
4.073126] [<ffffffff817c9298>] ret_from_fork+0x58/0x90
4.073146] [<ffffffff817b6b10>] ? rest_init+0x80/0x80
4.073185] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffff
4.073219] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
_
Both Windows 8.1 and Ubuntu are not booting after installing Ubuntu 14.04 https://askubuntu.com/questions/502970/both-windows-8-1-and-ubuntu-are-not-booting-after-installing-ubuntu-14-04

I had installed Windows 8.1 in my Dell Inspiron 5521 in Legacy Mode. I then tried installing Ubuntu 14.04. The installation was successful, but after rebooting I was unable to boot into any OS. While booting Windows, "A disk read error ....." appears. I can't boot into Ubuntu either. This is my Boot-Repair paste. http://paste.ubuntu.com/7864978/ I hope I'll get this issue resolved.

Here's my GParted screenshot.

enter image description here

How do I find out which version and derivative of Ubuntu is right for my hardware in terms of minimal system requirements? https://askubuntu.com/questions/206407/how-do-i-find-out-which-version-and-derivative-of-ubuntu-is-right-for-my-hardwar

For a given hardware configuration, how do I find out if Ubuntu will run on it? What considerations should I take into account when choosing an Ubuntu version and flavour such as:

  • Xubuntu with a lighter desktop than the usual Gnome and Unity
  • Lubuntu with the even lighter LXDE desktop

Obviously Ubuntu does not run on some processor architectures. So how do I go about choosing the right version and derivate. How can I find out the minmal system requirements?