Since the 26.04 kubuntu upgrade, when I try to log in with ssh using a password, I get a graphical window box asking for the password. I cannot emphasize enough how much I do not want this.

So I disabled the use kdewallet in the system settings, but that wasn't enough. I saw I also had to remove ksshaskpass, which I did, only to receive ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory, so I installed ssh-askpassand now there is a lame looking box asking for a password. Neither of those boxes work, and worse of all they break the use ofsshpass` which I need in some scripts. Yes, I know "use keys", but I can't on some systems, it's not allowed, don't ask me why.

So, how do I get ssh to ask for the password in text, as is traditional ?

I have been using Ubuntu and Windows without issues on a dual-boot setup. The Windows drive mounts automatically on startup in Ubuntu.

However, I want to re-enable BitLocker to encrypt the Windows drive. After reenabling it, Ubuntu will not start. I get the following message:

You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup. Press Enter for system maintenance (or press Control-D to continue):

If I type "systemctl reboot," nothing happens. If I type "exit", the same message appears again.

I have disabled Bitlocker again, but still, I would prefer to have the Windows drive encrypted (it is a laptop I sometimes travel with).

Thanks!

enter image description hereHI team ubuntu.

I have installed 26.04 with cinnamon desktop 6.14 to get custom as desklets, applets etc... but they don't work. the sever does not run and give nothing to see !?

thank you all for your lights.

I have installed 26.04 with cinnamon desktop 6.14 to get custom desklets, applets etc... but they don't work. The server does not run and gives no error messages!

I recently upgraded Ubuntu on a multi-boot system. I'm trying a few different linux distro's to try and decide witch is maybe better for what. Anyway the issue was that Ubuntu upgrade just ignored my current config and destroyed grub. The problem was that I am not that experienced so I waisted over 4 hours of my day restoring some semblance of the grub2 that I had to get things up and running again. While this was a learning opportunity!! I was wondering if I did something wrong when I did the upgrade or is there a way to avoid this problem next time? This is important to me because I have no intention of going back to Microsoft again for anything. Thanks in advance.

I am not very computer literate. I installed Ubuntu on an old Surface Go tablet I had and it was working fine except that the website can (command???) didn't work.

In trying to resolve this I followed the kernel installation advice here. Now all I get is a black screen with a commend line. I've tried to reboot from a USB, but nothing happens and I just restart to the black screen every time.

I'd be happy just to start again with a reinstall, but don't know how to do that.

I was a user of RealVNC, because it allows to connect to my computers across any network after signing in with RealVNC account.

However, RealVNC does not support Wayland, and KDE will drop support for X11 in 2027. While Kubuntu 26.04 is going to be supported for five more years, I want to prepare for the full Wayland transition.

There are ways to connect to Wayland via TigerVNC, and it is also possible to connect to PCs in a different network (via tailscale), as explained in this answer. However, this method has some bugs, e.g. the ctrl button does not always work, which is a pain, because I need to run code in my workstation, and it is hard to copy/paste/undo without the control button.

I have read that there are other available options such as RDP, RustDesk and more, but I don't know if they properly support Wayland. I have also read conflicting comments about what actually works, apart from VNC.

What are the other options (apart from TigerVNC) for KDE Wayland, and how to set them up? Does it also support remotely logging in (this feature is supported in RealVNC, but does not work for the related answer regarding TigerVNC, which is running from a logged in account)?

It would be nice if the method also supports other Wayland setups (e.g. GNOME), but that is not strictly necessary.

I installed the latest "Ubuntu touch" on my "Google Pixel 3a" yesterday. But, when I rebooted it, I found a message that "The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device." So, what should I do to solve this serious problem? Please someone help me.

I am experiencing an issue where my Wi-Fi is completely disabled after installing/updating to Ubuntu 26.04 on my Acer Aspire E5-475G laptop.Here are my hardware details:Laptop: Acer Aspire E5-475GWi-Fi Chipset: Qualcomm Atheros QCA9377 Wireless Network Adapter (rev 31)The Problem:The Wi-Fi option is grayed out or shows as "disabled" in the system settings. Clicking the toggle to turn it on does nothing. Bluetooth (which is on the same combo chip) works fine.

What I have tried:Checked BIOS settings to ensure wireless is enabled.Tried toggling the physical Fn + Wi-Fi key combination.How can I get this Qualcomm QCA9377 chipset working properly on Ubuntu 26.04? Is there a specific firmware package (firmware-ath9k or ath10k) or a kernel module parameter needed for this version?Thank you in advance for your help!

I am using Python's SSH module to upload files from a Windows computer (IP: 192.168.5.3) to the device rk3588 (IP: 192.168.5.2). The rk3588 is running Ubuntu 22.04 with kernel version 5.10. Currently, I have 30 Windows PCs, and for some reason, 3 of them occasionally experience slow SSH transmission speeds. Normally, the transmission can be completed in about 6 minutes, but when there is an exception, it can take up to an hour to complete. When I capture packets on the rk3588 side, I find a large number of retransmissions.

I've done this many times on different systems, but this has me puzzled:

OS: Ubuntu 26

Had an external drive that I was mounting using the fstab.

/dev/sda1 /data ext4 defaults 0 0

I removed the drive and of course it rebooted and went into recovery mode. So I edited the /etc/fstab and removed the external drive mount. Now when it reboots, it still hangs up on trying to mount that drive.

Does Ubuntu 26 store the information that is/was in the fstab in another spot? Like a database or other file? I noticed the fstab in Ubuntu 26 is very minimal, so I'm guessing there is some sort of other place that needs to be updated??

ckb-next has stopped working correctly either I get RGB working or the G* keys but I can nolonger get both working together

anyone know whats wrong and how to fix

I am using Ubuntu 26.04 Resolute Raccoon and ckb-next 0.6.2 package version 0.6.2+dfsg-0.3 universe/electronics

this used to work for the longest time

My Laptop has a 3000 2000 px Display and I am Using Xubuntu. I have no Problems with scaling on most programms (im on 2x Scale) but for some reason qBittorrent doesnt scale and is very tiny with very tiny fonts and icons. I tried to force scale it with the Terminal, but nothing is working. Any Idea how I can make it usable?

I have Linux and Windows dual-booted on my laptop. Specs are as follows:

System:Acer Aspire 1 A114-31 (from 2018).
FW: InsydeH2O (UEFI Class 3+ -- Secure Boot off, TPM on)
CPU: Celeron N3350 (1.1GHz, 2C/2T, Apollo Lake)
RAM: 4GB SK Hynix DDR3 (soldered)
GPU: Intel HD Graphics 500
Storage: 32GB eMMC (non-upgradable) + I use a 2TB Seagate Backup Portable USB 3.0 drive
Network: RTL8x11 series Gig Ethernet + Atheros QCA9377 WiFi

Installed Ubuntu MATE 24.04 on the external drive, but using the eMMC for swap and the ESP. I then installed Win8.1 on the eMMC (cos it doesn't support installation to USB drives). In the BIOS, Windows Boot Manager shows up, but not GRUB. When I open the boot menu (F12), GRUB is there, but it is listed as an "Unknown Device" on the eMMC.

There are two boot blocks, /dev/mmcblk1boot0 and /dev/mmcblk1boot1. Neither are big enough to install Grub to, as they're each only a few megs in size.

I don't know how to fix this problem. Maybe I need to edit the EFI variables? Any help would be appreciated.

- Kami =)

(P.S. GRUB will autoboot, but only if I manually put bootmgr at the bottom of the boot order (below the PXE boot options). So I can still use the laptop.)

new to Linux, and while I think I'm fairly tech-savvy I'm not sure where to begin with this. Happens whenever I try to run sudo apt upgrade.

Running Ubuntu 26.04 LTS, Kernel Linux 7.0.0-22-generic

Output from terminal below:

sudo apt upgrade
[sudo: authenticate] Password:         
The following packages were automatically installed and are no longer required:
  jellyfin-ffmpeg7  jellyfin-server  jellyfin-web
Use 'sudo apt autoremove' to remove them.

Get another security update through Ubuntu Pro with 'esm-apps' enabled:
  libopenexr-3-1-30
Learn more about Ubuntu Pro at https://ubuntu.com/pro
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
  7 not fully installed or removed.
  Space needed: 0 B / 390 GB available

Continue? [Y/n] y
Setting up linux-headers-7.0.0-22-generic (7.0.0-22.22)…
/etc/kernel/header_postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Autoinstall of module amdgpu/6.16.13-2278356.24.04 for kernel 7.0.0-22-generic (x86_64)
Building module(s)...........(bad exit status: 2)
Failed command:
'make' KERNELVER=7.0.0-22-generic
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fatal() directly instead.
  apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/amdgpu-dkms.0.crash'

Error! Bad return status for module build on kernel: 7.0.0-22-generic (x86_64)
Consult /var/lib/dkms/amdgpu/6.16.13-2278356.24.04/build/make.log for more information.

Autoinstall on 7.0.0-22-generic succeeded for module(s) hid-xpadneo xone.
Autoinstall on 7.0.0-22-generic failed for module(s) amdgpu(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 1
dpkg: error processing package linux-headers-7.0.0-22-generic (--configure):
 old linux-headers-7.0.0-22-generic package postinst maintainer script subprocess failed with exit status 1
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-7.0.0-22-generic; however:
  Package linux-headers-7.0.0-22-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-26.04:
 linux-headers-generic-hwe-26.04 depends on linux-headers-7.0.0-22-generic; however:
  Package linux-headers-7.0.0-22-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-26.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-26.04:
 linux-generic-hwe-26.04 depends on linux-headers-generic-hwe-26.04 (= 7.0.0-22.22); however:
  Package linux-headers-generic-hwe-26.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-26.04 (--configure):
 dependency problems - leaving unconfigured
Setting up linux-image-7.0.0-22-generic (7.0.0-22.22)…
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          No apport report written because the error message indicate
s its a followup error from a previous failure.
                                               No apport report written because MaxReports is reached already
                                                                                                             dpkg: dependency problems prevent configuration of linux
-generic:
 linux-generic depends on linux-headers-generic (= 7.0.0-22.22); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
 linux-generic-hwe-24.04 depends on linux-generic-hwe-26.04; however:
  Package linux-generic-hwe-26.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              No apport report written because MaxReports is reached already
                                                                                                                            Processing triggers for linux-image-7.0.0
-22-generic (7.0.0-22.22)…
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Autoinstall of module amdgpu/6.16.13-2278356.24.04 for kernel 7.0.0-22-generic (x86_64)
Building module(s)...........(bad exit status: 2)
Failed command:
'make' KERNELVER=7.0.0-22-generic
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fatal() directly instead.
  apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/amdgpu-dkms.0.crash'

Error! Bad return status for module build on kernel: 7.0.0-22-generic (x86_64)
Consult /var/lib/dkms/amdgpu/6.16.13-2278356.24.04/build/make.log for more information.

Autoinstall on 7.0.0-22-generic succeeded for module(s) hid-xpadneo xone.
Autoinstall on 7.0.0-22-generic failed for module(s) amdgpu(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-7.0.0-22-generic (--configure):
 old linux-image-7.0.0-22-generic package postinst maintainer script subprocess failed with exit status 1
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 linux-headers-7.0.0-22-generic
 linux-headers-generic
 linux-headers-generic-hwe-26.04
 linux-generic-hwe-26.04
 linux-generic
 linux-generic-hwe-24.04
 linux-image-7.0.0-22-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)

I installed Ubuntu 26.04 recently on a new device and enabled full disk encryption.

When I enter the password, sometimes the system does not recognise it and prompts me to enter it again. When I do that, it gets stuck on the loading screen and never boots. Pressing ESC showed me some error messages about the crypt library.

How can I solve this problem? I am forced to do a force restart at least once a day because of that. The keyboard layout is shown to be de So I don't think it is related to a layout mismatch.

#Edit1 Logs below executing journalctl:

If I run reboot command the system logs in without peoblems. So i happens roughly 50% when booting from an off state. It does not happen at all on reboot.

My system always restart after I do a poweroff.

I have a Nvidia rtx gpu, msi mag motherboard with the latest bios

I tried with two kernels: 6.12.0-061200, 7.0.0-14, 7.0.0-22

What I tried

• BIOS set to "Power Off" on AC loss
• ErP Ready enabled
• Wake-on-LAN disabled
• nvidia-powerd disabled
• GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force reboot=acpi apm=power_off nomodeset"

[UPDATE]: I found some threads on Framework's Community boards, and apparently this is a known issue with the AMD motherboard, and a workaround is to use a USB-A to USB-C cable instead of a USB-C to USB-C. I tried it, and was able to pair the phone successfully and tether it to share the network! Would prefer not to involve USB-A, but it seems to be a functioning workaround.

Original post:

I have a Framework 13 laptop (AMD cpu) with Ubuntu 26.04 freshly installed and updated. I plug in my iPhone 16 Pro (iOS 26.5) via USB-C cable, and Ubuntu shows an "Untrusted Device" dialog, and the phone shows a "Trust This Computer?" dialog.

Before I can click "Trust" on the iPhone, the dialog is dismissed. After 3-4 seconds, Ubuntu overlays another "Untrusted Device" dialog, and the iPhone again flashes the "Trust This Computer?" dialog.

It keeps repeating this endlessly, and never gives me enough time to click "Trust" on the iPhone and type in the pairing code.

The USB-C cable is a known working cable from Apple, which works fine to pair/tether the phone to a MacBook. I believe I've also paired this phone and laptop on a previous install of ubuntu, but I hadn't used this laptop in a year, and did a fresh 26.04 install recently, and I'm traveling, and surprised that I can't seem to pair the two to share my phone's internet.

The workaround is to use a wireless tethering method (bluetooth or wifi), but I can't plug my phone in to charge off the laptop without it making both the phone and laptop pop up a dialog every 3-4 seconds.

I spent a couple hours this morning with Claude to see if it could help me track down the issue, and I asked it to summarize what we tried, and here's the relevant bits from that summary:

Root-cause isolation. Verbose usbmuxd logging showed a consistent per-cycle pattern: the device enumerates cleanly, usbmuxd connects, the configuration is switched (0 → 4), preflight begins, reaches "Waiting for user to trust this computer," and then ~0.6–0.8 seconds later the device drops (Device RX aborted due to error or disconnect / Removed device) and re-enumerates. The disconnect timing is fixed and regular, and occurs with nothing on the host actively tearing down the connection — usbmuxd is idle in the trust-wait state when the drop happens. This points to the USB connection being torn down below userspace, at the USB host-controller/xHCI or device level, rather than a pairing-software failure.

What we ruled out (no effect on the drop). Different USB-C ports; the Apple cable (works on macOS); stale host trust state (cleared /var/lib/lockdown, and did Reset Location & Privacy on the phone); the udev rule 39-usbmuxd.rules (masked it entirely — no change); GNOME gvfs/gvfsd-afc contention (masked the volume monitors — the gvfs storm stopped but the ~0.8s drop persisted unchanged); daemon lifecycle (ran a single persistent usbmuxd --foreground so no socket/udev respawn could interfere); and the ipheth kernel module (unloaded it with modprobe -r ipheth — the device still dropped at the same ~0.8s mark with the driver entirely absent).

I have a Lenovo ThinkPad X9-15 Gen 1 with Ubuntu 26.04 (Resolute Raccoon, kernel 7.0.0-22-generic) and the built-in camera is not working in any application (Firefox, GNOME Camera, etc.). I tried to replicate solutions, given for ubuntu 24, but with no avail.

Some troubleshooting

Ubuntu version: 26.04

Ubuntu sees the camera:

$ v4l2-ctl --list-devices
Intel MIPI Camera (platform:v4l2loopback-000):
    /dev/video0

What I've already tried:

• Installed oem-sutton-dana-meta, libcamhal0, linux-modules-ipu7-generic, v4l2loopback-dkms

• v4l2-ctl --list-devices shows the camera via v4l2loopback

• ipu7x.so is present in /usr/lib/libcamhal/plugins/

• pw-cli list-objects shows the camera in PipeWire

v4l2-relayd -d fails with:

CamHAL[ERR] load_camera_hal_library, failed to open PCI device
gst_parse_launch_full: assertion 'pipeline_description != NULL' failed

libcamhal-ipu7x cannot be installed due to broken dependencies:

Depends: libjsoncpp25 but it is not installable (Ubuntu 26.04 has libjsoncpp26)
Depends: libia-cca-ipu7x0
Depends: libia-log-ipu7x0
Depends: libcamhal-ipu7x-common

In Ubuntu versions previous to 26.04 the default mount point for automatically mounted removable media (by GNOME?), like USB drives, external HDDs, SD cards, etc., was something like /media/<username>/<disk_id>/. Now, after upgrade to Ubuntu 26.04, it seems that the location /run/media/<username>/<disk_id>/ is used instead.

The top-level /media/ directory still exists and it is still populated with user directories from past mounts.

Update: There is a short explanation for the "why" this change has happened at the Release Notes for Ubuntu 26.04 and in some answers given below.

My question is: What will happen to the /media/ directory? Is the /media/ directory still created in fresh Ubuntu 26.04 installs? I had upgraded my system to 26.04 from 25.10 and I don't know whether it is still an essential directory or can be safely deleted.

I have a intel wifi adapter that is built into my motherboard and i was able to get wifi back up and running temporarily by just reloading my wifi module but now its not working again after I turned it off and on again the next day and I've tried redownlouding things and reloading wifi module again but nothing is working.the only why I've gotten wifi to my computer is through a wired connection through my phone. it does see the wifi adapter but for some reason i cant get wifi.

I used to use VNC in x11 but it does not work with Wayland.

How can I connect to my Kubuntu 26.04 (Wayland) computer from another computer in another network so that I can access its GUI, just like in VNC?

Being able to access Wayland with VNC is important because KDE's support for X.Org is going away in 1 year.

RealVNC provides a method to sign in and access your computer from anywhere. But it does not support Wayland. It would be able to use the same feature in Wayland across different networks.

I use KDE Connect between my phone and laptop on my University WiFi. Very often, the IP address changes and the connection stops working. I have to manually find the IP of the computer with the command ip address and put it in my phone and connect manually. The same thing happens when I connect to a different network.

Is there any way to automate the connection process? AFAIK know Apple's computers have some robust connection procedure with iOS devices.

I want to be able to do this for multiple computers with the same phone.

I'm setting up a test server on 24.04, moving it from W11 actually.

Got Apache all installed, works fine, http://localhost gives the expected output. Now need to move the web root from /var/www/html to a directory webroot on a different drive mounted as /media/nick/DATA. So:

Edited /etc/apache2/sites-available/000-default.conf to change the DocumentRoot line to /media/nick/DATA/webroot, added the following to /etc/apache2/apache2.conf

<Directory /media/nick/DATA/webroot/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
</Directory>

copied the index.html from the original document root into /media/nick/DATA/webroot, and restarted the server

sudo service apache2 restart

But, all I get is error 403, access forbidden.

Seems I have missed something?

Im trying to install the IPTV program Hypnotix on Ubuntu 23.04. But i have not succeeded. I have googled around a bit and im starting to think the problem is that Ubuntu 23.04 is very new and for some reason doesnt support Hypnotix yet? Does anyone know what the problem might be? Best regards Ubuntu newcomer Emil

I have a file with an xz extension, ubuntu-19.10-preinstalled-server-arm64+raspi3.img.xz. How do you get the .img out of it?

My goal is to flash the file on an SD card. I want to use www.etcher.io I finally got it to work, but etcher will only handle .iso and .img files.

I'm encountering a connection issue to my university WiFi network that I cannot solve: when attempting to connect, I get the following message with dmesg -T :

[ven. oct. 11 12:32:04 2019] wlan0: deauthenticating from X by local choice (Reason: 3=DEAUTH_LEAVING)

This problem has already been pointed out in the forum, but none of the solutions I tried worked:

• Disabling the powersave for WiFi (in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf set wifi.powersave = 2 ).
• Changing from NetworkManager to WICD.

• Adding the following lines to /etc/sysctl.conf:

  net.ipv6.conf.all.disable_ipv6 = 1
  net.ipv6.conf.default.disable_ipv6 = 1
  net.ipv6.conf.lo.disable_ipv6 = 1
  

None of these worked.

I have an openvpn client and it's configuration is stored in a .ovpn file. All my network traffic is going through the VPN tunnel when I connect to it.

I want to add an exception for some of the IPs to not go through the VPN tunnel. I have tried adding route www.google.com 255.255.255.255 192.168.43.1 at the end of the ovpn file to test it. (192.168.43.1 is router IP address)

But, this is making the configuration file invalid. I am just beginning to learn openvpn and I am confused about where to add this line exactly.

My laptop recognises external display devices if I connect them before booting the system, but many times it doesn't if I connect while the system is running. In this case, rebooting naturally solves the problem.

Is there a way to force Ubuntu to detect external displays? Opening up the display menu and pressing "Detect displays" does nothing.

I have Win8 on my desktop, where a 120G SSD is used to run windows and some select applications, while I have a 2TB HDD to provide basic file storage and where possible, install applications instead of on the SSD.

I want to install Ubuntu on a new partition of the HDD (I allocated 300GB, with 5GB swap file).

I've used a USB to install the OS, which seemed to have done the job. However, after prompting for a restart, I can no longer boot to ubuntu.

During instillation I was confused about where to install the "boot loader instillation". I ended up selecting "/dev/stb" because I figured I would be able to boot with BIOS by selecting the HDD drive as a priority over the SSD.

The bootloader is a large part of where I think I went wrong.

My partition system looked something like this:

/dev/sta  ...               //SSD ~120 GB
/dev/sta1 NTFS (350 MB)     //Win8System
/dev/sta2 NTFS (118 GB)     //Win8C-Drive

/dev/stb ...                //HDD ~2TB
/dev/stb1 NTFS (1563 GB)    //FileStorage
/dev/stb5 Free Space (300 GB)    //Space I want to use for Linux

(NOTE: Created two partitions from the 300GB, ~5GB and 295GB. stb5,stb6.)

It'd be great if I could get an explanation of what drive you'd select for the boot loader and why, and what selections won't work with regards to the Boot Loader Instillation. I think I understand what Grub is, but I have no idea on how to use it, or play around with it.

I seem to be able to get back into OS from my usb, however I believe it's just showing me a preview/trial of Ubuntu (ie, can't access any of the system NTFS drives). Note, if I try to install from the USB again, it will recognize that a version of Ubuntu 13.10 exists on the system.

Apologies in advance, have used windows all my life, don't really know to much about Linux at all. Did have a brief skim over some similar questions, didn't find anything too useful. - Where to install bootloader when installing Ubuntu as secondary OS? - ubuntu 12.10 dual boot with windows 8 on two hdds - Dual-boot Windows 7 and Ubuntu on two SSDs with UEFI

EDIT: Found Solution

Turns out, after I attempted to re-installing once more, that what was required was to create the root partition (~295GB) as a primary partition instead of the default selected Logical. It wouldn't recognize a logically formatted root partition.

All working now, I'm typing this from Ubuntu as we speak. (Yipeee!)

EDIT: Clarification

I still left the boot loader instillation specified to '/stb', and now I can use the BIOS to boot from the SSD or the HDD interchangeably. Very handy.

I still require an explanation as to why:

• Using a Logical partition would not be recognised the system's BIOS (I have an ASUS H-87 Pro Mobo).
• What would be different if I changed my boot loader instillation instead to '/sta'? Would I no longer directly boot into Windows, and instead use the Grub interface every time?
• Is there a preferred place to install the boot loader instillation? Clarifying that specifying volumes such as '/sta1' or '/stb5' would not allow you to load the OS?