I am running Ubuntu 24.04, and I installed virtualbox following these instructions: https://www.virtualbox.org/wiki/Linux_Downloads.

Here is the error I receive when launching my Windows VM: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE). VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {...}

I have two 1TB hard drives. In BIOS mode both drives are listed, however when installing there's only one drive showing. When the installation completes and I log into the completed install, Disks shows only the one installation drive. Nowhere can I find the second drive.

Also in the sidebar there are two icons for HDDs. Hovering over the drives I see rpool. Clicking either of those two icons says failed to mount rpool.

Questions:

1. How do I get Ubuntu to recognize the second 1TB drive?
2. Once the second drive is recognized, is there a way to treat the two drives as one 2TB drive?

Error installing Broadcom BCM43142 802.11b/g/n driver, command error sudo apt-get install broadcom-sta-dkms

Errors were found while processing:
broadcom-sta-dkms 
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm trying to open the text editor with the command line. Everywhere I search tells me that gedit is the default text editor on ubuntu, but gedit doesn't work on the CLI

What is the default text editor application (the one called "Text Editor") and how do you start it from the Terminal?

Does someone have an Ubuntu desktop image for the Raspberry Pi 3? I do not have a Raspberry Pi 4 and want to run the Ubuntu desktop on a Raspberry Pi 3.

When I first installed Ubuntu a couple of months ago the Ethernet was working just fine, then suddenly it stopped connecting by giving me an error message (although the hardware still appears to be seen by the system). The WiFi works.

I also have installed Windows 11 in a dual boot, and there the Ethernet is working. I'm still a noob at linux, so I don't know what to do.

I've installed Ubuntu 25.10 yesterday and I keep having weird glitched all over the GNOME interface and other Ubuntu specific apps like the terminal, also it almost always crashes my terminal when I save a document with NANO. Sometimes the GNOME interface even freezes so I am unable to do anything with the desktop and my only solution is to reboot my laptop via the power button.

I should also clarify that I do NOT experience these glitches while playing videogames or watching videos on YouTube (Firefox), so I bet it's rather GNOME's problem. I've also attached a video for you to see closely how it looks like.

https://drive.google.com/file/d/1jx6auNoAIggOgtmjY48_D6DAKGUc5AMR/view?usp=sharing

Here are the specifications:

OS: Ubuntu 25.10 x86_64
Kernel: Linux 6.17.0-14-generic
CPU: Intel(R) Core(TM) i5-7300U (4) @ 3.50 GHz
GPU: Intel HD Graphics 620 @ 1.10 GHz [Integrated]
DE: GNOME 49.0
WM: Mutter (Wayland)

Driver specific information:

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
    Subsystem: Lenovo Device 225d
    Kernel driver in use: i915

I'm a newb who enabled fips and lost some connectivity. Wireless is disconnected and the ProtonVPN app won't even start.

This is what I did that day: sudo pro attach [key] sudo pro enable fips-updates

I ran disable fips-updates but nmcli device shows wifi still disconnected.

Ubuntu 24.04.4 LTS kernel: 6.8.0-101-fips

Looks like it gave me a new kernel?

Running lspci gives Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)

Running lshw -C network gives description: Wireless interface product: Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak]

Following Daniel T's suggestion, I tried: ~$ sudo pro disable fips-updates --purge FIPS Updates is not currently enabled - nothing to do. See: sudo pro status

Because I disabled it already.

So, upon trying to enable, I got this message: ~$ sudo pro enable fips-updates One moment, checking your subscription first This will install the FIPS packages including security updates. Warning: This action can take some time and cannot be undone. Are you sure? (y/N) y The "generic" variant of fips-updates is based on the "generic" Ubuntu kernel but this machine is running the "fips" kernel. The "fips" kernel may have significant hardware support differences from "generic" fips-updates. Warning: Installing generic fips-updates may result in lost hardware support and may prevent the system from booting. Do you accept the risk and wish to continue? (y/N)

Sure why not?

It worked despite the caveats (--purge is "experimental") and warnings like it might be left unbootable.

I've recently purchased USB fingerprint scanner and configured fprintd for lock screen and some other authorizations.

Here is my /etc/pam.d/kde file

auth    sufficient      pam_fprintd.so max-tries=10 timeout=10
auth    sufficient      pam_unix.so nullok try_first_pass

The issue is that when fprintd fails to recognize my finger, its messages flush password entry line out of the screen, like in the photo below.

Is there any way to customize the area, where messages from fprintd appear? For example, add scroll-bar?

I use KDE, desktop theme is Breeze.

Versions:

Kubuntu: 24.04.4LTS

package kubuntu-desktop: 1.451.2

package sddm-theme-breeze: 4:5.27.12-0ubuntu0.1

UPD. I understand that I can reduce max-tries. However, matching algorithm is still experimental, it gives too many false negatives. Each false reject appends a new message. Therefore I'd like to enlarge output area.

Reading files in /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/ I've found that this message is accessible in the field root.notification.

Unfortunately, I'm totally newbie in KDE theme development, therefore, I have no idea how to add style to this component.

I recently installed Ubuntu 24.04 in my (Asus Vivobook Go 15 E1504FA) Everything works fine, but the WiFi driver is not detected by the OS. My laptop does not even have an Ethernet port. The WiFi driver works fine in Windows and it has no hardware issues.

I've tried the following troubleshooting steps:

1. Firmware Update: I cloned the latest linux-firmware repository and copied the mediatek firmware files to /lib/firmware/mediatek/.

2. Driver Installation: I attempted to load the mt7921e driver with the following commands:

   sudo modprobe mt7921e
   sudo modprobe -r mt7921e and sudo modprobe mt7921e again
   

3. Check Network Status:

   lshw -C network shows the Wi-Fi card as "UNCLAIMED."
   iwconfig shows no wireless extensions.

4. System Logs: I couldn't find any helpful output from dmesg | grep mt7921e.

Despite these efforts, the Wi-Fi driver doesn't seem to load, and the network interface remains unclaimed. Could anyone guide me on how to get my Wi-Fi working on Ubuntu? I'm using kernel version 6.8.0-51-generic.

Please help me to fix this and get my wifi drivers working on Ubuntu.

How can I stop Ubuntu from asking for my account's password I wake my computer up from a black screen? The ubuntu-lock-on-suspend setting doesn't do it.

ISSUE: Network Settings do not show wifi but ubuntu lists correct hw.

Im running the following with a MSI Z790 ace max motherboard.

Operating System: Ubuntu 24.04.1 LTS                
          Kernel: Linux 6.8.0-49-generic
    Architecture: x86-64
 Hardware Vendor: Micro-Star International Co., Ltd.
  Hardware Model: MS-7D86
Firmware Version: A.43
   Firmware Date: Wed 2024-06-19
    Firmware Age: 5month 1w 6d

The exact network manager I'm using is:

*-network
       description: Network controller
       product: WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800]
       vendor: Qualcomm Technologies, Inc
       physical id: 0
       bus info: pci@0000:07:00.0
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=ath12k_pci latency=0
       resources: irq:239 memory:81200000-813fffff

When I inspect dmesg for ath12k I get the following:

[    5.703227] ath12k_pci 0000:07:00.0: BAR 0 [mem 0x81200000-0x813fffff 64bit]: assigned
[    5.703244] ath12k_pci 0000:07:00.0: enabling device (0000 -> 0002)
[    5.703393] ath12k_pci 0000:07:00.0: MSI vectors: 16
[    5.703397] ath12k_pci 0000:07:00.0: Hardware name: wcn7850 hw2.0
[    6.266352] ath12k_pci 0000:07:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
[    6.266364] ath12k_pci 0000:07:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
[    6.266398] ath12k_pci 0000:07:00.0: qmi failed to load regdb bin:
[    6.266399] ath12k_pci 0000:07:00.0: qmi failed to load regdb file:-2

I found this:

https://lore.kernel.org/all/87ttmlrc8l.fsf@kernel.org/T/

Which states that

regdb.bin is for developer testing, end users shouldn't use that file.

Can you try ath.git master branch:

https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/

We have some patches in the pipeline which didn't sadly make it to v6.8.

However link doesnt work, I tried downloading latest ath12k-firmware but it also did not work. (following: https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath12k/installation.html)

If I update to a newer kernel version, my GPU drivers stop working.

Any ideas on how to solve this?

2024 kubuntu is in use. There are two problems on my notebook (it is Honor MagicBook X16 plus, similar to Huawei notebooks):

• sometimes brightness is arbitrary self-changing by unknown reason to max or min
• sometimes some UI events (generated by unknown source) prevent selecting of text (say in terminal or browser with mouse cursor)

I have tried to find the events source and it seems the first above problem reason is kglobalaccel5 catches events as if brightness changing buttons (Fn + F1 or F2) were pressed. I have got this conclusion on digging in dbus-monitor output.

It is possible to disable brightness-related shortcuts in Settings (then it is possible to set brightness via scrolling on battery tray icon). But the second problem still remains.

In fact arbitrary self-regulated brightness takes place regardless DE (ubuntu-desktop, cinnamon and something else were tried with the same magic). Attempts to find (and disable) something similar to ALS failed.

So the question is: how to determine these events source?

I'm trying to set up a pxeboot installer for 24.04 Server LTS. The machine finds our PXE and TFTP just fine, and loads the kernel and initrd. But when it gets to the install, it fails to recognize that it's received a DHCP address. I can tail the logs on our DHCP server and see it getting an address. On the console of the machine, I can see it naming that same IP address but then saying "no such device" and then "no devices to configure" despite starting each round with the IP it was assigned.

I've tried changing the pxeboot settings to use a static IP and still get errors along the lines of "no device." It tries a number of times at increasingly longer intervals and eventually fails out.

It seems to be that the BIOS can find a NIC for the initial boot but the kernel loaded via TFTP can't. Except I can still see each attempt in the logs on the DHCP server.

The machine is a VM running under the xen hypervisor. That doesn't seem like it should be an issue. It does work fine with Ubuntu 22.04 LTS. In xen the default "NIC" is a Realtek or you can also choose to emulate an Intel e1000. I've tried both with no change. Update: I've also tried this on bare metal (Dell R740) with slightly different errors (the Dell is running UEFI and the VM uses legacy BIOS) but still no love.

Once it drops to the busybox/initramfs prompt, the network interface is unconfigured. I can enable it and it gets DHCP settings just fine including IP, GW, broadcast, DNS, TFTP server. DNS doesn't work, though: /etc/resolv.conf is empty. I can add a nameserver to it manually and then networking is fine. Here's the whole situation:

Begin: Waiting up to 180 secs for any network device to become available ... done.
Setting ip link enX0 up
ipconfig: 10.6.165.234: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
Sleeping 30 seconds before retrying getting a DHCP lease
ipconfig: 10.6.165.234: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
Sleeping 60 seconds before retrying getting a DHCP lease
ipconfig: 10.6.165.234: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
Sleeping 90 seconds before retrying getting a DHCP lease
ipconfig: 10.6.165.234: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
Sleeping 120 seconds before retrying getting a DHCP lease

BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) no search or nameservers found in /run/net-.conf /run/net-*.conf /run/net6-*.conf
Begin: Running /scripts/casper-premount ... done.
done.
Begin: Trying netboot from : ... Begin: Trying to download and mount [http://depot.pc.scharp.org/ISO/ubuntu-24.04-live-server-amd](https://www.google.com/search?q=http://depot.pc.scharp.org/ISO/ubuntu-24.04-live-server-amd)
64.iso ... wget: bad address 'depot.pc.scharp.org'
done.
Unable to find a live file system on the network

(initramfs) ipconfig
ipconfig: no devices to configure
(initramfs) ipconfig enX0
IP-Config: enX0 hardware address d2:8d:f2:9e:37:64 mtu 1500 DHCP RARP
IP-Config: enX0 complete (dhcp from 10.6.164.134):
address: 10.6.165.238     broadcast: 10.6.165.255     netmask: 255.255.254.0
gateway: 10.6.164.1       dns0     : 10.6.164.135     dns1   : 140.107.117.11
domain : pc.scharp.org
nisdomain: scharp.org
rootserver: 10.6.164.192 rootpath:
filename  :
(initramfs) cat /etc/resolv.conf
(initramfs) echo "nameserver 10.6.164.135" > /etc/resolv.conf
(initramfs) wget [http://depot.pc.scharp.org/foo.html](https://www.google.com/search?q=http://depot.pc.scharp.org/foo.html)
Connecting to depot.pc.scharp.org (10.6.164.192:80)
saving to 'foo.html'
foo.html             100% |********************************************************************************|     4  0:00:00 ETA
'foo.html' saved
(initramfs) cat foo.html
foo
(initramfs)

Has anything changed about calling the install from pxelinux.cfg.default?

Here's what I'm calling:

LABEL Ubuntu24.04 LTS Auto Install
  MENU LABEL Ubuntu 24.04 LTS Unattended Base Build (SCHARP)
  KERNEL ubuntu24.04/vmlinuz
  APPEND autoinstall initrd=ubuntu24.04/initrd root=/dev/ram0 ramdisk_size=16384 hostname=ubuntu-24 ip=dhcp url=http://depot.pc.scharp.org/ISO/ubuntu-24.04-live-server-amd64.iso ds=nocloud-et;s=http://depot.pc.scharp.org/auto_os/u24/

Update 4/29: It occurred to me I was using a very old version of the pxelinux.0 file. Installed pxelinux to my tfptd server and copied in current versions of pxelinux.0 and the dependent files. No change.

Also tried booting the install using static addressing, specifying the network device and settings in the "APPEND" line. I still get "no such device" in the error output despite seeing the same device name earlier.

I got the following message when trying to install Ubuntu in WSL.

Installing, this may take a few minutes...  
The parameter is incorrect.  
Please create a default UNIX user account.    
The username does not need to match your Windows username.  
Enter new UNIX username: ▂ 

What should I do now?

Dell Latitude 6530 comes with Nvidia Quatro 5200M 23.10 does not offer v390. According to Nvidia, I can install 535, or the latest driver. When I try any 400 ...535 driver, it tells me that this hardware is supported by 390.

Ubuntu 23.10 has no nvidia-driver-390 package.

When I power off Ubuntu 20.04 any type of way it just stays on this screen that says my computer logo and the Ubuntu logo at the bottom. I'm new to Linux. I just want to go to bed with my PC completely shut down.

I'm trying to reinstall something on my new kernel of Ubuntu 16.04 system, and I accidentally tried the command: sudo update initramfs -u Since then my computer could not boot correctly anymore. Every time it will enter BusyBox like this:

BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash)
enter 'help' for a list of built-in commands.

(initramfs)

More importantly, I could not type in anything under this circumstance.

Right now I am able to use my computer via another kernel, but does anyone have some good ideas to fix my issue?

Here is the output of ls -al /boot

total 158540  
drwxr-xr-x  4 root root     4096 Apr  7 12:28 .  
drwxr-xr-x 24 root root     4096 Apr  7 07:01 ..  
-rw-r--r--  1 root root   217286 Apr  5  2019 config-4.15.0-48-generic  
-rw-r--r--  1 root root   217465 Feb 28 12:24 config-4.15.0-91-generic  
-rw-r--r--  1 root root   217465 Apr  1 01:44 config-4.15.0-96-generic   
drwx------  3 root root     4096 Dec 31  1969 efi  
drwxr-xr-x  5 root root     4096 Apr  7 12:30 grub  
-rw-r--r--  1 root root 55577646 Aug 28  2019 initrd.img-4.15.0-48-generic  
-rw-r--r--  1 root root 56163066 Mar 18 06:25 initrd.img-4.15.0-91-generic  
-rw-r--r--  1 root root 12625827 Apr  7 12:28 initrd.img-4.15.0-96-generic   
-rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin  
-rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf  
-rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin  
-rw-------  1 root root  4051368 Apr  5  2019 System.map-4.15.0-48-generic  
-rw-------  1 root root  4067536 Feb 28 12:24 System.map-4.15.0-91-generic  
-rw-------  1 root root  4068326 Apr  1 01:44 System.map-4.15.0-96-generic  
-rw-------  1 root root  8141400 Apr  8  2019 vmlinuz-4.15.0-48-generic  
-rw-------  1 root root  8193432 Mar  1 05:28 vmlinuz-4.15.0-91-generic  
-rw-------  1 root root  8191544 Apr  6 12:08 vmlinuz-4.15.0-96-generic

I tried sudo update-initramfs -c -k 4.15.0-96-generic,
but it did not help.

(py35) yunzhi@DESKTOP-Ubuntu:~$ sudo update-initramfs -c -k 4.15.0-96-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-96-generic
(py35) yunzhi@DESKTOP-Ubuntu:~$ ls -al /boot/initrd*
-rw-r--r-- 1 root root 55577646 Aug 28  2019 /boot/initrd.img-4.15.0-48-generic
-rw-r--r-- 1 root root 56163066 Mar 18 06:25 /boot/initrd.img-4.15.0-91-generic
-rw-r--r-- 1 root root 12626314 Apr  7 16:17 /boot/initrd.img-4.15.0-96-generic

The updated output of ls -al /boot:

total 158540    

drwxr-xr-x  4 root root     4096 Apr  7 16:25 .  
drwxr-xr-x 24 root root     4096 Apr  7 07:01 ..  
-rw-r--r--  1 root root   217286 Apr  5  2019 config-4.15.0-48-generic  
-rw-r--r--  1 root root   217465 Feb 28 12:24 config-4.15.0-91-generic  
-rw-r--r--  1 root root   217465 Apr  1 01:44 config-4.15.0-96-generic  
drwx------  3 root root     4096 Dec 31  1969 efi  
drwxr-xr-x  5 root root     4096 Apr  7 12:30 grub  
-rw-r--r--  1 root root 55577646 Aug 28  2019 initrd.img-4.15.0-48-generic  
-rw-r--r--  1 root root 56163066 Mar 18 06:25 initrd.img-4.15.0-91-generic  
-rw-r--r--  1 root root 12625839 Apr  7 16:25 initrd.img-4.15.0-96-generic  
-rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin  
-rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf  
-rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin  
-rw-------  1 root root  4051368 Apr  5  2019 System.map-4.15.0-48-generic  
-rw-------  1 root root  4067536 Feb 28 12:24 System.map-4.15.0-91-generic  
-rw-------  1 root root  4068326 Apr  1 01:44 System.map-4.15.0-96-generic  
-rw-------  1 root root  8141400 Apr  8  2019 vmlinuz-4.15.0-48-generic  
-rw-------  1 root root  8193432 Mar  1 05:28 vmlinuz-4.15.0-91-generic  
-rw-------  1 root root  8191544 Apr  6 12:08 vmlinuz-4.15.0-96-generic  

I'm not too familiar with VPNs and I'm having a hard time connecting to a VPN service with OpenConnect.

The VPN service I've purchased uses Cisco AnyConnect, which I can't get for Linux, but the OpenConnect application is supposed to do the same thing. I've installed OpenConnect and the GUI for it.

On other OS'es like Android, the VPN service simply has me link the Cisco AnyConnect client to an XML file which AnyConnect then uses to connect to the servers. No other configuration in the client software is needed besides providing this XML file, which makes me think that this XML file contains all the information necessary to connect to all these VPN servers - no configuring checkboxes, no downloading of certificates, etc.

Once I provide the XML file, AnyConnect generates the list of VPN servers, I choose one, and fill in my username and password in the ensuing popup boxes and that's it.

<AnyConnectProfile xmlns="http://schemas.xmlsoap.org/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/encoding/ AnyConnectProfile.xsd">
<ClientInitialization>
<UseStartBeforeLogon UserControllable="false">false</UseStartBeforeLogon>
<StrictCertificateTrust>false</StrictCertificateTrust>
<RestrictPreferenceCaching>false</RestrictPreferenceCaching>
<RestrictTunnelProtocols>IPSec</RestrictTunnelProtocols>
<BypassDownloader>true</BypassDownloader>
<WindowsVPNEstablishment>AllowRemoteUsers</WindowsVPNEstablishment>
<CertEnrollmentPin>pinAllowed</CertEnrollmentPin>
<CertificateMatch>
<KeyUsage>
<MatchKey>Digital_Signature</MatchKey>
</KeyUsage>
<ExtendedKeyUsage>
<ExtendedMatchKey>ClientAuth</ExtendedMatchKey>
</ExtendedKeyUsage>
</CertificateMatch>
<BackupServerList>
<HostAddress>localhost</HostAddress>
</BackupServerList>
</ClientInitialization>
<ServerList>
<HostEntry>
<HostName>server 1</HostName>
<HostAddress>japan.examplevpn.com</HostAddress>
</HostEntry>
<HostEntry>
<HostName>server 2</HostName>
<HostAddress>amsterdam.examplevpn.com</HostAddress>
</HostEntry>  
</ServerList>
</AnyConnectProfile>

OpenConnect on Linux doesn't seem to have any provision to import an XML file.

What do I need to do to configure each connection in OpenConnect, based on what's in the XML file?

I am running Ubuntu 19.10 on my laptop, I recently installed miniconda3. No problems this far, but after creating an environment with python 2.7 I get the following message everytime I open a terminal:

Command 'python' not found, but can be installed with:
sudo apt install python3         # version 3.7.5-1, or
sudo apt install python          # version 2.7.17-1
sudo apt install python-minimal  # version 2.7.17-1

So I followed the advise and installed python, then this error occured:

Traceback (most recent call last):
  File "<stdin>", line 3, in <module>
ImportError: No module named conda

My guess is that bash is trying to access the conda python 2.7? Here is what I get by running which python without conda active:

which python

/usr/bin/python

which python3

/usr/bin/python3

whereis python

python: /usr/bin/python2.7 /usr/bin/python3.7 /usr/bin/python3.7m /usr/bin/python /usr/lib/python3.8 /usr/lib/python2.7 /usr/lib/python3.7 /etc/python2.7 /etc/python3.7 /etc/python /usr/local/lib/python2.7 /usr/local/lib/python3.7 /usr/include/python3.7m /usr/share/python /usr/share/man/man1/python.1.gz

with conda activated here are the corresponding results:

which python

/home/rustax/miniconda3/bin/python

which python3

/home/rustax/miniconda3/bin/python3

whereis python

python: /usr/bin/python2.7 /usr/bin/python3.7 /usr/bin/python3.7m /usr/bin/python /usr/lib/python3.8 /usr/lib/python2.7 /usr/lib/python3.7 /etc/python2.7 /etc/python3.7 /etc/python /usr/local/lib/python2.7 /usr/local/lib/python3.7 /usr/include/python3.7m /usr/share/python /home/rustax/miniconda3/bin/python3.7-config /home/rustax/miniconda3/bin/python3.7m /home/rustax/miniconda3/bin/python3.7 /home/rustax/miniconda3/bin/python3.7m-config /home/rustax/miniconda3/bin/python /usr/share/man/man1/python.1.gz

This is what conda adds to the .bashrc file:

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/home/rustax/miniconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/home/rustax/miniconda3/etc/profile.d/conda.sh" ]; then
        . "/home/rustax/miniconda3/etc/profile.d/conda.sh"
    else
        export PATH="/home/rustax/miniconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<

Thank you in advance for any help you can provide

BusyBox error message:

Gave up waiting for root device.  Common problems:

- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=1ddd1a18-5a44-4da5-be79-b0b48002f91e does not exist.  Dropping to a shell!

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

(initramfs)

grub> prompt:

                  GNU GRUB  version 2.02~beta2-36ubuntu3.20

   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. ESC at any time exits.

grub> sudo nano /etc/de
Possible files are:

 depmod.d/ debconf.conf debian_version default/ deluser.conf
grub> sudo nano /etc/default/grub
error: can't find command `sudo'. grub> nano /etc/default/grub error: can't find command `nano'.
grub> /etc
error: can't find command `/etc'.
grub> ls -l
Device hd0: No known filesystem detected - Sector size 512B - Total size
104857600KiB
        Partition hd0,msdos5: No known filesystem detected -           Partition start
at 103858176KiB - Total size 998400KiB
        Partition hd0,msdos1: Filesystem type ext* - Last modification time
2019-03-30 18:49:53 Saturday, UUID 1ddd1a18-5a44-4da5-be79-b0b48002f91e -
Partition start at 1024KiB - Total size 103856128KiB

grub> _

UUID description (results of ls -l):

Fetched 1,129 kB in 1s (1,087 kB/s)
Selecting previously unselected package libgtkmm-2.4-1v5:amd64.
(Reading database ... 236667 files and directories currently installed.)
Preparing to unpack .../libgtkmm-2.4-1v5_1%3a2.24.4-2_amd64.deb ...
Unpacking libgtkmm-2.4-1v5:amd64 (1:2.24.4-2) ...
Selecting previously unselected package libparted-fs-resize0:amd64.
Preparing to unpack .../libparted-fs-resize0_3.2-15ubuntu0.1_amd64.deb ...
Unpacking libparted-fs-resize0:amd64 (3.2-15ubuntu0.1) ...
Selecting previously unselected package gparted.
Preparing to unpack .../gparted_0.25.0-1_amd64.deb ...
Unpacking gparted (0.25.0-1) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.2) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20180209-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libgtkmm-2.4-1v5:amd64 (1:2.24.4-2) ...
Setting up libparted-fs-resize0:amd64 (3.2-15ubuntu0.1) ...
Setting up gparted (0.25.0-1) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
vishnu@vishnu:~$ gparted
Root privileges are required for running gparted.
vishnu@vishnu:~$ sudo gparted
======================
libparted : 3.2
======================
vishnu@vishnu:~$ make oldconfit
make: *** No rule to make target 'oldconfit'.  Stop.
vishnu@vishnu:~$ make oldconfig
make: *** No rule to make target 'oldconfig'.  Stop.
vishnu@vishnu:~$ sudo make oldconfig
make: *** No rule to make target 'oldconfig'.  Stop.
vishnu@vishnu:~$ cd /dev/disk
vishnu@vishnu:/dev/disk$ cd by-uuid/
vishnu@vishnu:/dev/disk/by-uuid$ ls -l
total 0
lrwxrwxrwx 1 root root 10 Apr  1 13:45 1ddd1a18-5a44-4da5-be79-b0b48002f91e -> ../../sda1
lrwxrwxrwx 1 root root  9 Apr  1 13:45 2018-12-18-11-51-35-12 -> ../../sr0
lrwxrwxrwx 1 root root 10 Apr  1 13:45 a656eab4-48b7-45bd-b3fa-eb47bad66deb -> ../../sda5
vishnu@vishnu:/dev/disk/by-uuid$ █

GParted:

Results of blkid:

vishnu@vishnu:~$ blkid
/dev/sr0: UUID="2018-12-18-11-51-35-12" LABEL="VBox_GAs_6.0.0" TYPE="iso9660"
/dev/sda1: UUID="1ddd1a18-5a44-4da5-be79-b0b48002f91e" TYPE="ext4" PARTUUID="a97
5a70b-01"
/dev/sda5: UUID="a656eab4-48b7-45bd-b3fa-eb47bad66deb" TYPE="swap" PARTUUID="a97
5a70b-05"
vishnu@vishnu:~$ _

I have tried all the methods I could find on the internet. Unfortunately, nothing fixed my problem. All these are happening inside VirtualBox. It started happening after an audio update in Ubuntu. I can post the blkid and the UUID that creates the error if requested. Anyway I dug the resume inside the conf file and it looks to be different.

I am not able to do sudo or edit the files inside initramfs or GRUB.

The blkid and uuid looks different. Do you have any idea how to edit them?

Note: I am unable to copy paste the error message.

I have no background with linux but I wanted to give it a try.
So I downloaded Ubuntu 18.04.1 LTS and flashed it to my newly formated 16GB USB drive and got this message.
I tried different USB drives (all of the same kind, all 16GB and all have a micro-USB on the other side to connect it to eg Android phones), the Ubuntu 18.10 version and Linux Mint 19.1 Tessa (Cinnamon). I reinstalled balena Etcher (the program I flashed the USB drives with) but it still did not work.

I'm trying to bring back an old PC to life. After looking around I concluded that Lubuntu is a great option. It's modern yet fast, using very little resources.

This computer is in a room where it would be very inconvenient to throw a cable to connect to internet, so I have a USB Wifi receiver dongle. It's the ZyXEL G-220 v3 and I have the original driver disc for it, the thing is, it's for Windows.

I am new to Linux and don't really even know where to start. I did find where my devices are located (System Profiler and Benchmark) but still don't know how to make it work.

If anybody could point me in the right direction I would really appreciate it.

Here's the lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 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 002 Device 003: ID 0586:3419 ZyXEL Communications Corp. G-220 v3 802.11bg Wireless Adapter [ZyDAS ZD1211B]
Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I want to make disk image in case if something goes wrong. I found few topics and method about zeroing free space, but people also said that method is not safe for SSD. Then I found other method - Create A Disk Image Without Enough Free Space, but it is a bit old and I don't know if it works on 14.04 with SSD.
Can I do that by following that guide? If no, please tell me some other method, thanks.

On the virtual machine when I update grub (sudo update-grub) and restart I get the BusyBox initramfs shell on boot.

I have a checkpoint on the machine so I can easily go back to just before I ran the command and reboot to regain access to the fully booted machine.

Ordinarily I wouldn't really care because I could just not update grub. However, I want to increase the resolution on the machine and this requires running that command and rebooting. Which as stated, kills the installation.

The OS is Ubuntu 15.04, 64-bit.

This is the output when I run the command. I don't know if there's anything weird going on there?

Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is se
t is no longer supported.
Found linux image: /boot/vmlinuz-3.19.0-15-generic
Found initrd image: /boot/initrd.img-3.19.0-15-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done

This is what happens when I reboot and this is all, there's no other information, unlike most of the screenshots of initramfs I've seen online.

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

(initramfs)

How do I fix this? Bear in mind that I have access to the fully booted desktop pre initramfs error and pre grub update.

I thought I should add that I have Ubuntu installed on a virtual hard drive. I am then accessing and making changes through a differencing disk.

I've managed to work around the initramfs error and get my full screen resolution.

I added the video=hyperv_fb:1920x1080 line to the etc/default/grub file as the resolution tutorial told me to and ran the update-grub command.

I then saved the /boot/grub/grub.cfg file and reverted back to the old checkpoint. I then compared the 'old' cfg file which was now back in place with the edited one. I found all the places that my video line should be and re-added them back in.

I then rebooted and hooray it worked. I still cannot run sudo update-grub, but I have managed to get my full screen resolution by doing this :)

I just installed the Lubuntu Desktop on top of my Ubuntu 14.04 install.

I can login in to any desktop environment from the start-up fine, but once I'm in Lubuntu my Menu -> Logout button does nothing. Also on the bottom right, my shutdown, Ethernet, keyboard, and volume settings are grayed out and I am unable to select them. The only way to shutdown or reboot is from the command line.

Do I need to fix my install?

Im running a computer with Ubuntu 14.04.1, no screen attached. I have installed Teamviewer 10.0.36897. Im trying to get it to produce fullscreen when connecting to it through Teamviewer, allthough it only shows 1024x768.

http://s13.postimg.org/ksbsgfq8m/res.jpg

Before connecting to my "Ubuntu-computer" I have - under properties - added 1920x1200, like image below shows, allthough this doesn't help.

http://s22.postimg.org/tsgxpkqpd/upls.png

In Ubuntu under "Screens" the dropdown option to change resolution is grayed out, and Im not able to change there either.

How do I increase the resolution?

I am using Ubuntu 14.04.1 LTS

Does anyone know how to fix this dkms.conf error?

dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
Error! Bad conf file.
File: 
does not represent a valid dkms.conf file.
Setting up linux-headers-generic (3.13.0.35.42) ...
Processing triggers for libc-bin (2.19-0ubuntu6.3) ...

$ dkms status

bbswitch, 0.7, 3.13.0-34-generic, x86_64: installed
bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed
nvidia-331-updates, 331.38, 3.13.0-34-generic, x86_64: installeddkms.conf: Error! No       'BUILT_MODULE_NAME' directive specified for record #0.
Error! Bad conf file.
File: 
does not represent a valid dkms.conf file.

nvidia-331-updates, 331.38, 3.13.0-35-generic, x86_64: installed

$ ls -R /var/lib/dkms


/var/lib/dkms:
bbswitch  dkms_dbversion  nvidia-331-updates  xpad

/var/lib/dkms/bbswitch:
0.7  kernel-3.13.0-34-generic-x86_64  kernel-3.13.0-35-generic-x86_64

/var/lib/dkms/bbswitch/0.7:
3.13.0-34-generic  3.13.0-35-generic  build  source

/var/lib/dkms/bbswitch/0.7/3.13.0-34-generic:
x86_64

/var/lib/dkms/bbswitch/0.7/3.13.0-34-generic/x86_64:
log  module

/var/lib/dkms/bbswitch/0.7/3.13.0-34-generic/x86_64/log:
make.log

/var/lib/dkms/bbswitch/0.7/3.13.0-34-generic/x86_64/module:
bbswitch.ko

/var/lib/dkms/bbswitch/0.7/3.13.0-35-generic:
x86_64

/var/lib/dkms/bbswitch/0.7/3.13.0-35-generic/x86_64:
log  module

/var/lib/dkms/bbswitch/0.7/3.13.0-35-generic/x86_64/log:
make.log

/var/lib/dkms/bbswitch/0.7/3.13.0-35-generic/x86_64/module:
bbswitch.ko

/var/lib/dkms/bbswitch/0.7/build:
bbswitch.c  dkms.conf  Makefile

/var/lib/dkms/nvidia-331-updates:
331.38  kernel-3.13.0-34-generic-x86_64  kernel-3.13.0-35-generic-x86_64

/var/lib/dkms/nvidia-331-updates/331.38:
3.13.0-34-generic  3.13.0-35-generic  build  source

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-34-generic:
x86_64

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-34-generic/x86_64:
log  module

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-34-generic/x86_64/log:
make.log

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-34-generic/x86_64/module:
nvidia_331_updates.ko

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-35-generic:
x86_64

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-35-generic/x86_64:
log  module

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-35-generic/x86_64/log:
make.log

/var/lib/dkms/nvidia-331-updates/331.38/3.13.0-35-generic/x86_64/module:
nvidia_331_updates.ko

/var/lib/dkms/nvidia-331-updates/331.38/build:
conftest.sh          g_nvreadme.h   nv-chrdev.c  nv-frontend.c  nv.h                      nv-memdbg.h   nv-p2p.c     nv-reg.h            nv-vm.c         os-registry.c  rmretval.h
conftest.sh.orig     Makefile       nv.c.orig    nv-frontend.h  nv-i2c.c                  nv-mempool.c  nv-p2p.h     nvtypes.h           nv-vtophys.c    os-smp.c       xapi-sdk.h
cpuopsys.h           Makefile.orig  nv-cray.c    nv_gpu_ops.h   nvidia-modules-common.mk  nv-misc.h     nv-pat.c     nv-usermap.c        os-interface.c  os-usermap.c
dkms.conf            nv-acpi.c      nv-drm.c     nvgputypes.h   nv-kernel.o               nv-mlock.c    nv-procfs.c  nv_uvm_interface.c  os-interface.h  patches
gcc-version-check.c  nv.c           nverror.h    nv-gvi.c       nv-linux.h                nv-mmap.c     nv-proto.h   nv_uvm_interface.h  os-pci.c        rmil.h

/var/lib/dkms/nvidia-331-updates/331.38/build/patches:
allow_sublevel_greater_than_5.patch  buildfix_kernel_3.11.patch  buildfix_kernel_3.6.patch                 register-VT-switch-requirements.patch
buildfix_kernel_3.0.patch            buildfix_kernel_3.13.patch  buildfix_kernel_3.8.patch                 replace-VM_RESERVED-with-VM_DONTEXPAND-and-VM_DONTDU.patch
buildfix_kernel_3.10.patch           buildfix_kernel_3.14.patch  make-use-of-the-new-uapi-framework.patch

/var/lib/dkms/xpad:
0.1  kernel-3.13.0-34-generic-x86_64

/var/lib/dkms/xpad/0.1:
3.13.0-34-generic  build  source

/var/lib/dkms/xpad/0.1/3.13.0-34-generic:
x86_64

/var/lib/dkms/xpad/0.1/3.13.0-34-generic/x86_64:
log  module

/var/lib/dkms/xpad/0.1/3.13.0-34-generic/x86_64/log:
make.log

/var/lib/dkms/xpad/0.1/3.13.0-34-generic/x86_64/module:
xpad.ko

/var/lib/dkms/xpad/0.1/build:
dkms.conf  Makefile  xpad.c

Which is the preferred way to install the latest stable version of Mesa on Ubuntu? I believe that would be a PPA, but not the bleeding-edge one like xorg-edgers.

I would like to see a PPA that contains the latest stable release. Right now 10.3 has reached Release Candidate stage and development branched to 10.4, so the latest stable version is 10.2. Soon 10.3 will become the latest stable version and I'd like a PPA that would follow that. For comparison, xorg-edgers contains 10.3.0~git20140821 and oibaf has 10.4~git1408211930.

I've had this issue on and off for about two years now. I noticed it on a new (custom built) machine running 10.04 when that first came out, but then it went away until a few months ago. I've gone through a number of hard drive changes but I can't say specifically what if anything I changed hardware-wise to make it stop or start happening. I had assumed upgrading to a modern Ubuntu version would fix the issue, so I installed 12.04 beta on a spare partition last night, but it's still happening.

Here's the issue. After grub loads and I select a kernel to boot, the screen goes blank save for a blinking cursor. It sits in this state for many long minutes before it finally gives up and gives me an initramfs shell with the message gave up waiting for root device (and lists the /dev/disk/by-uuid/... path it was waiting for) but no other specific diagnostic information.

Now, here's the tricky part. For one, the problem is intermittent - sometimes it progresses from the blinking cursor to the Ubuntu splash boot screen in a few seconds, and once it gets that far it always continues booting fine. The really bizarre thing is that I can "force" it to "find" the root device by repeatedly pressing the space bar and hitting the machine's power button. If I tap those enough, eventually I will notice the hard drive light coming on, at which point it will always continue the boot process after a few seconds. Interestingly, if I wait slightly too long before pressing the power button (30s?), as soon as I press it I get the gave up waiting message and the initramfs shell.

I've tried setting up /etc/fstab (and the grub menu.lst or whatever it's called nowadays) to use device names (e.g. /dev/sda1) instead of UUIDs, but I get the same effect just with the device name, not UUID, in the error message.

I should also mention that when I boot to Windows 7, there is no issue. It boots slowly all the time just by virtue of being Windows, but it never hangs indefinitely. This would seem to indicate it's a problem in Ubuntu, not the hardware.

It's pretty annoying to have to babysit the computer every time it boots. Any ideas? I'm at a loss. Not even sure how to diagnose the issue.

Here's some dmesg output from 10.04. The 15 second gap is where it was doing nothing. I pressed the power button and space bar a few times, and the stuff at 16 seconds happened. Not sure what any of it means.

[    1.320250] scsi18 : ahci
[    1.320294] scsi19 : ahci
[    1.320320] ata19: SATA max UDMA/133 abar m8192@0xfd4fe000 port 0xfd4fe100 ir
q 18
[    1.320323] ata20: SATA max UDMA/133 abar m8192@0xfd4fe000 port 0xfd4fe180 ir
q 18
[    1.403886] usb 2-4: new high speed USB device using ehci_hcd and address 4
[    1.562558] usb 2-4: configuration #1 chosen from 1 choice
[   16.477824] ata16: SATA link down (SStatus 0 SControl 300)
[   16.477843] ata19: SATA link down (SStatus 0 SControl 300)
[   16.477857] ata3: SATA link down (SStatus 0 SControl 300)
[   16.477895] ata15: SATA link down (SStatus 0 SControl 300)
[   16.477906] ata20: SATA link down (SStatus 0 SControl 300)
[   16.477977] ata17: SATA link down (SStatus 0 SControl 300)
[   16.478003] ata12: SATA link down (SStatus 0 SControl 300)
[   16.478046] ata13: SATA link down (SStatus 0 SControl 300)
[   16.478063] ata14: SATA link down (SStatus 0 SControl 300)
[   16.478108] ata11: SATA link down (SStatus 0 SControl 300)
[   16.478123] ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   16.478127] ata6: SATA link down (SStatus 0 SControl 300)
[   16.478157] ata5: SATA link down (SStatus 0 SControl 300)
[   16.478193] ata18.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66

After that, it took its sweet time, and I had to keep hitting space bar to coax it along. Here's some more dmesg output from a little later in the boot process:

[   17.982291] input: BTC USB Multimedia Keyboard as /devices/pci0000:00/0000:00
:13.0/usb5/5-2/5-2:1.0/input/input4
[   17.982335] generic-usb 0003:046E:5506.0002: input,hidraw1: USB HID v1.10 Key
board [BTC USB Multimedia Keyboard] on usb-0000:00:13.0-2/input0
[   18.005211] input: BTC USB Multimedia Keyboard as /devices/pci0000:00/0000:00
:13.0/usb5/5-2/5-2:1.1/input/input5
[   18.005274] generic-usb 0003:046E:5506.0003: input,hiddev96,hidraw2: USB HID 
v1.10 Device [BTC USB Multimedia Keyboard] on usb-0000:00:13.0-2/input1
[   22.484906] EXT4-fs (sda6): INFO: recovery required on readonly filesystem
[   22.484910] EXT4-fs (sda6): write access will be enabled during recovery
[   22.548542] EXT4-fs (sda6): recovery complete
[   22.549074] EXT4-fs (sda6): mounted filesystem with ordered data mode
[   32.516772] Adding 20482832k swap on /dev/sda5.  Priority:-1 extents:1 across:20482832k 
[   32.742540] udev: starting version 151
[   33.002004] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[   33.008135] parport_pc 00:09: reported by Plug and Play ACPI
[   33.008186] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[   33.012076] lp: driver loaded but no devices found
[   33.037271] ppdev: user-space parallel port driver
[   33.090256] lp0: using parport0 (interrupt-driven).

Are there any clues in there?

Some screenshots of dmesg output from the initramfs busybox shell when it fails:

normal:

[     1.330141] ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum
[     1.330145] ahci 0000:06:00.0: setting latency timer to 64
[     1.330245] scsi18 : ahci
[     1.330296] scsi19 : ahci
[     1.330323] ata19: SATA max UDMA/133 abar m8192@0xfd4fe000 port 0xfd4fe18
[     1.330326] ata20: SATA max UDMA/133 abar m8192@0xfd4fe000 port 0xfd4fe18
[ 301.305830] Clocksource tsc unstable (delta = 299971863297 ns)
[ 301.306301] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[22] MMIO=[fd6
d6ff7ff] Max Packet=[2048] IR/IT contexts=[4/8]
[ 301.306738] Switching to clocksource hpet
[ 301.361292] usb 2-4: new high speed USB device using ehci_hcd and addres
[ 301.423909] ata7: SATA link down (SStatus 0 SControl 300)
[ 301.423954] ata8: SATA link down (SStatus 0 SControl 300)
[ 301.423978] ata5: SATA link down (SStatus 0 SControl 300)
[ 342.065743] usb 2-4: configuration #1 chosen from 1 choice
[ 342.111380] CE: hpet increasing min_delta_ns to 40226 nsec
[ 345.677117] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 345.677146] ata17: SATA link down (SStatus 0 SControl 300)
[ 345.677163] ata15: SATA link down (SStatus 0 SControl 300)
[ 345.677165] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 345.677207] ata13: SATA link down (SStatus 0 SControl 300)
[ 345.677211] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 345.677225] ata12: SATA link down (SStatus 0 SControl 300)

without quiet splash on the linux line:

- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
[ 301.549359] usb 2-4: configuration #1 chosen from 1 choice
ALERT! /dev/disk/by-uuid/67bd9b15-38ea-4a8f-8e9f-f12b27c7f5b5 does
dropping to a shell!

BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) [ 301.641400] ata20: SATA link down (SStatus 0 SControl
[ 301.641486] ata19: SATA link down (SStatus 0 SControl 300)
[ 301.641567] ata16: SATA link down (SStatus 0 SControl 300)
[ 301.642642] ata13: SATA link down (SStatus 0 SControl 300)
[ 301.642733] ata17: SATA link down (SStatus 0 SControl 300)
[ 301.642753] ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 300
[ 301.642798] ata12: SATA link down (SStatus 0 SControl 300)
[ 301.642844] ata11: SATA link down (SStatus 0 SControl 300)
[ 301.642859] ata14: SATA link down (SStatus 0 SControl 300)
[ 301.642899] ata15: SATA link down (SStatus 0 SControl 300)
[ 301.643188] ata18.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66
[ 301.643687] ata18.00: configured for UDMA/66  
_

I tried fossfreedom's suggestion of trying a number boot options. So far, it looks like irqpoll is actually working! I've booted four times successfully with it so far.

(As a side note, I can't get irqpoll to stick -- I edited /etc/default/grub to add it to GRUB_CMDLINE_LINUX_DEFAULT and ran update-grub, but still nothin'. What am I missing?) (My grub was hosed somehow when installing the other ubuntus. I fixed it and am seeing irqpoll always now.)

Given that, what is the problem here? It sounds like irqpoll is a hack to get BIOSes that somehow don't adhere to some IRQ standard to work with Linux. How do I figure out what component is the issue, and is there another solution to get Linux to play nice with it that doesn't involve what sounds like so much overhead?