I have an old 3rd gen Asus k55vj laptop with Core i5 3rd gen, Intel 4000 S graphics with 8 GB RAM and a GeForce GT 635M dedicated GPU. I want to install Ubuntu 25.10 as Windows is unable to detect my dGPU and the laptop fans are spinning at maximum speed even though there are no processes or CPU stress. During the installation of Ubuntu I got stuck at the welcome wallpaper, not even getting the option of choosing the language.

I again restarted in safe mode and successfully installed Ubuntu in safe mode, but after the installation it asked me to remove the drive and press Enter, but failed to start the newly installed Ubuntu 25.10. How to resolve this? I know the dGPU of mine is a failed card because it is old. Please help me to get rid of the fan noise and save my laptop.

Attention! Some of your past questions have not been well-received. You're in danger of being blocked from asking any more..

For help formulating a clear, useful question, see: How do I ask a good question?

Also, edit your previous questions to improve formatting and clarity.

Very RUDE! Go ahead and block me. Why would I ask for your help?

I thought something felt off in my Hardware Info when I was writing this, but I couldn't pin down what until I looked at an older question with my info on it. Somehow and I don't know how, but I'd assume it's not helping (if it isn't the main cause for overheating all the sudden), my graphics have gone from listing "AMD Radeon RX 7900 XT" and "AMD Ryzen 7 7800X3D" to only listing "Software Rendering". If anyone knows what could cause this and how to fix it, I would be grateful.

Nothing has changed much since I got my computer up and running for the semester. The only thing I can think of is that I let it run an update a day or so ago, but all of the sudden my computer is running so hot doing things like browsing the web and checking my Discord notifications that I can't use it for more than 30 minutes at a time without one of the sensors hitting an ALARM (HIGH) report when running sensors in the terminal.

Basic specs are below and the current temperature at the moment. Usually it would go to +70° C, but I've taken off one of the PC's side panels just to vent the heat. It's a small form factor computer, so I do expect it to get pretty hot, but never before for just regular day-to-day use. Help is much appreciated, as I'd like to not worry about it overheating and causing permanent damage while I'm in college.

spd5118-i2c-2-51  
Adapter: SMBus PIIX4 adapter port 0 at 0b00 
temp1:         +56.8 degrees C (low = +0.0 degrees C, high = +55.0 degrees C) ALARM (HIGH) 
                               (crit low = +0.0 degrees C, crit = +85 degrees C)

I'm also unsure if it'd help, but here's a look at the System Monitor at the moment.

The CPU seems that it isn't be overloaded (I've had an issue with that before, but it appeared to be a power issue possibly, as moving and using a different plug made that problem disappear), with the most CPU usage being the Gnome Shell, so I'm unsure what's going on that's causing it to overheat.

I have tried to format it, but all the buttons are gray and using the cmd prompt isn't working either. I followed someone else's guide and it did nothing.

I have a dashboard from Home Assistant and would like it to be shown as the desktop wallpaper/background using some web web browser (Firefox, Chromium) in kiosk mode.

How would I tell my Ubuntu 24.04/Wayland/Gnome to automatically start that browser upon user login and run it as desktop wallpaper?

I checked gnome dynamic wallpaper resources and found:

• https://itsfoss.gitlab.io/post/add-dynamic-wallpapers-to-your-gnome-desktop/ only allows to display images
• https://extensions.gnome.org/extension/1040/random-wallpaper/ only allows to display images
• https://github.com/jeffshee/gnome-ext-hanabi only allows to display a video
• https://linuxconfig.org/how-to-create-gnome-dynamic-wallpapers only allows to display images

I remember years before Gnome came up it was possible to start application such that they would run in the root or desktop window - such as xearth, xroach and xsnow used to do.

Unlike Can only boot Ubuntu 20.04.1 LTS when holding shift, I have Ubuntu 24.04.3 running on a HDD with the CPU being an AMD Ryzen 5 7600X.

Going into GRUB and then into Recovery Mode, seems to be the only way to boot all the way to desktop consistently.

Latest Recovery had black sections before I moved the selected options over them. Maybe it works is also related to how the resolution becomes 1024 x 768.

And even when I get GRUB, rarely, using the "Ubuntu" option boots fine. Holding down Shift during the boot logo might actually do something useful, or might just be me making a false cause fallacy.

Unlike the linked question's answer, my sudo nano /etc/default/grub reads:

> GRUB_DEFAULT=0  
GRUB_TIMEOUT_STYLE=hidden  
GRUB_TIMEOUT=0  
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`  
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"  
GRUB_CMDLINE_LINUX=""

Is it because I have quad boot options on my GRUB? Ubuntu, Advanced, Memory Tests, then Windows 10, XP, and another XP spread out over 3 HDDs. They're all on Legacy, but I'm always just trying to boot into Ubuntu.

I bet it's more due to graphics related stuff that flickers my screen as the boot logo screen adjusts to fit my monitor. My card and monitor are really old, (NVIDIA GT 220 connecting to a Hanns.G HG-216D), but it does that no matter if I go to GRUB, although the screen doesn't tear if I actually get to see the GRUB menu.

It seems even just getting to GRUB isn't a total fix. Did a sudo shutdown -r now from a successful boot to get to GRUB, left it on GRUB for a while while typing most of this out, picked Ubuntu, and the screen didn't tear, but there's still a black screen after the boot logo.

A mention of VGA GPU in the boot logs of the "failed" boot clued me in to take a guess, and it seems like it works after unplugging the VGA.

Or at least it worked once, and then not again-ish. Still probably a graphics issue, but gnome / Ubuntu just can't seem to settle on always using HDMI, even when it's the only display output plugged in? At least Recovery Mode still works.

The log line in question being:

gnome-shell: Boot VGA GPU /dev/dri/card1 selected as primary

Appears in all "failed" boots.

But my monitor doesn't report "no HDMI video signal", emphasis mine, it just gives a black screen.

Basic timeline:

• I chose the "upgrade" option from the gui pop-up letting me know there was a newer version available.

• That ran for a bit, then gave me a message that it failed (I don't remember any details of the message, I mentally categorized it as "deal with that later")

• I noticed something was wrong with my internet, and the setting was missing from the quick menu

• I rebooted to see if that would resolve it

• It wouldn't boot into a gui, only into the terminal

• I started exploring in the terminal, and quickly found that I in fact don't have internet connectivity (eg, any install attempt of any package results in "failed to fetch")

• I booted from a 24.04 usb, which worked fine

• I was able to mount the old partition, explore files, etc; it's all still there

• I used the option, from the usb stick, to install 24.04 side-by-side

• That install went fine, and I now have two (relevant) partitions, one with 22.04 and one with 24.04. 24.04 works as expected but has none of my installed software, files, etc, and 22.04 boots into the terminal and has no internet connectivity

I would like to actually repair and upgrade the 22.04 installation and go back to using that partition as primary, but I'm not sure how to go about doing so. Fixing the internet on that partition seems like my first priority.

Output of ip link show when booted on the 22.04 partition:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:93:90:2d:0e:56 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether b0:dc:ef:02:43:10 brd ff:ff:ff:ff:ff:ff

Output of ip link show when booted on the 24.04 partition:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:93:90:2d:0e:56 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether b0:dc:ef:02:43:10 brd ff:ff:ff:ff:ff:ff

I'm way out of practice on network config via cli and haven't had much luck googling to try to figure out how to get the internet up and running, but I imagine that if I can get online, so that I can manually upgrade/install packages using apt, I probably could manage to get the system repaired from there.

Edit to add additional outputs:

sudo lshw -C network:

  *-network DISABLED
       description: Wireless interface
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       logical name: wlp0s20f3
       version: 01
       serial: b0:dc:ef:02:43:10
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=6.16.3-76061603-generic firmware=89.4d42c933.0 so-a0-gf-a0-89.uc latency=0 link=no multicast=yes wireless=IEEE 802.11
       resources: irq:17 memory:be390000-be393fff
  *-network DISABLED
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: enp12s0
       version: 15
       serial: d4:93:90:2d:0e:56
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=r8169 driverversion=6.16.3-76061603-generic latency=0 link=no multicast=yes
       resources: irq:17 ioport:d000(size=256) memory:be504000-be504fff memory:be500000-be503fff

sudo lspci -vnn | awk -vRS= '/\[02[08]0\]/':

00:14.3 Network controller [0280]: Intel Corporation Device [8086:51f1] (rev 01)
    Subsystem: Intel Corporation Device [8086:0094]
    Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 7
    Memory at be390000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
    Capabilities: [100] Latency Tolerance Reporting
    Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi
0c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
    Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1558:7755]
    Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 14
    I/O ports at d000 [size=256]
    Memory at be504000 (64-bit, non-prefetchable) [size=4K]
    Memory at be500000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 01
    Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
    Capabilities: [170] Latency Tolerance Reporting
    Capabilities: [178] L1 PM Substates
    Kernel driver in use: r8169
    Kernel modules: r8169

ip link show after sudo ip link set wlp0s20f3 up (verified with ping that this did not bring internet back):

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:93:90:2d:0e:56 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether b0:dc:ef:02:43:10 brd ff:ff:ff:ff:ff:ff

Update as of 1/17/2026: I finally had time to poke at this some more today. Here's the additional info I was able to gather:

• Connecting via ethernet appears unhelpful; while in chroot, I can ping 8.8.8.8 just fine with or without ethernet, but DNS is not resolving (shame on me for pinging a url instead of an IP previously)
• However, ethernet does not get internet connectivity when booted directly into the old partition. enp12s0 shows as down with ip link show, and while sudo ip link set enp12s0 up does change its status to up, pinging 8.8.8.8 still does not work ("network is unreachable").
• Using chroot from the working installation does not let me interact with services (I attempted this to try to get dns resolution back online); it wants (and fails) to interact with the main system services (which makes sense, I'm not truly running on the old partition when using chroot).
• Unfortunately, since I can't get internet connected while truly booted into the old partition, and apt-offline is not already installed, I think it's at a dead end, and I'm going to need to just move what I need over to the new partition and delete/displace the old one to reclaim the space. I'm not going to get rid of the old partition just yet, so I'm all ears if anyone has other ideas that might get past this hurdle, but otherwise, I'm considering this closed.

I get a notification on login saying "Language support is incomplete, additional packages are required", but I don't get an option to install it.

What is missing? I've searched the internet. but the posts offer nothing that has worked.

I’m trying to dual boot Ubuntu and Windows 11 on an HP Spectre x360 16 from 2024, however when I turn on my computer it boots directly into Windows. When I check my boot menu, I only have the option to boot into Windows unless I manually tell it to boot into the Grub EFI file. When I check the BIOS settings, it doesn’t see the Ubuntu partition, just the Windows one. I have Secure Boot turned off. What should I do?

Now, the latest version of Node is 20.11.0. However, every time I tried to install Node, it installed the 12.22.9 version.

This commands is not working, every time it installed the same version 12.22.9

curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -

sudo apt install nodejs

Error description

I have an existing Conda environment with Python 3.8.16, and I have tried to install Spyder with: conda install spyder as well as with conda install -c conda-forge spyder, (not simultaneously) which installs Spyder 5.4.3.

Running spyder however outputs:

Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Aborted (core dumped)

Running it from Anaconda navigator gives:

Exit code: 134

N.B. Running Spyder from Anaconda navigator in base environment works fine! It also works fine in the problematic environment but on my laptop with Ubuntu 20.04.6, with the same Spyder version but conda 23.9.0.

I have found several related issues:

Rstudio fails to open with error "...could not find or load the Qt platform plugin "xcb""

Cannot open qcreator qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""

Could not find or load the Qt platform plugin "xcb": TexMaker

OpenCOR, "could not find or load the Qt platform plugin "xcb""

Could not find or load the Qt platform plugin "xcb"

“Failed to load platform plugin ”xcb“ ” while launching qt5 app on linux without qt installed

https://github.com/NVlabs/instant-ngp/discussions/300

https://discuss.pixls.us/t/solved-could-not-load-the-qt-platform-plugin-xcb-in-even-though-it-was-found/17677/7

None of which have solved my issue. Most of them have users finding the solution to be installing a large variety of libxcb*packages.

I have tried:

sudo apt install libxcb1
sudo apt install libx11-xcb1
sudo apt install xcb
sudo apt install libxcb-*

I have also tried:

export QT_QPA_PLATFORM=minimal

as well as xcb, dxcb and vnc and setting it to "".

Setting:

export QT_DEBUG_PLUGINS=1

also gives no new additional information. Also, on my laptop, echoing any of these variables gives nothing, yet it works there.

At first glance, the issue seems to be that the path where it looks for xcb is "", but I don't know what variable to change. After some searching, I tried:

export QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins

since echoing that variable gave nothing. However, echoing that in base also gives nothing, yet it works there.

This just resulted in the error:

Could not load the Qt platform plugin "xcb" in "/usr/lib/x86_64-linux-gnu/qt5/plugins" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

Aborted (core dumped)

Update 1: Now, however, setting export QT_DEBUG_PLUGINS=1 shows a whole lot, where the last perhaps relevant lines are:

Got keys from plugin meta data ("xcb")
QFactoryLoader::QFactoryLoader() checking directory path "/home/lord/anaconda3/envs/tir-top/bin/platforms" ...
Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: (/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: undefined symbol: _ZNK15QXcbIntegration28createPlatformVulkanInstanceEP15QVulkanInstance, version Qt_5_PRIVATE_API)
QLibraryPrivate::loadPlugin failed on "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so" : "Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: (/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: undefined symbol: _ZNK15QXcbIntegration28createPlatformVulkanInstanceEP15QVulkanInstance, version Qt_5_PRIVATE_API)"
Could not load the Qt platform plugin "xcb" in "/usr/lib/x86_64-linux-gnu/qt5/plugins" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

Aborted (core dumped)

But I don't even know whether this is the correct path to set, and again, it seems these variables aren't even needed on my laptop.

Update 2: Creating a new environment and installing spyder there with

conda create -n spyd-test python=3.8.16
conda activate spyd-test
conda install spyder

works!

But for some reason, in my already existing environment with the same python version, it does not.

Other sys specs:

Ubuntu 22.04.3
spyder 5.4.3
spyder-kernels 2.4.4
conda 23.9.0
qt5dxcb-plugin (5.0.46+git20220314-1)

$ conda list | grep qt
pyqt                      5.15.9           py38hffdaa6c_5    conda-forge
pyqt5-sip                 12.12.2          py38h17151c0_5    conda-forge
pyqtwebengine             5.15.6                   pypi_0    pypi
pyqtwebengine-qt5         5.15.2                   pypi_0    pypi
qt-main                   5.15.8              h01ceb2d_12    conda-forge
qt-webengine              5.15.8               h27f4a20_2    conda-forge
qtawesome                 1.2.2            py38h06a4308_0  
qtconsole                 5.4.4                    pypi_0    pypi
qtpy                      2.4.0                    pypi_0    pypi
sphinxcontrib-qthelp      1.0.3              pyhd3eb1b0_0

conda list | grep spyder
pyls-spyder               0.4.0              pyhd3eb1b0_0  
spyder                    5.4.3            py38h06a4308_1  
spyder-kernels            2.4.4            py38h06a4308_0

Any help would be highly appreciated!

Since the upgrade to 22.04, my CPU/GPU temperatures are not available. When attempting to configure the Plasma desktop widget, only disk drives appear. It would be nice to monitor the temperature again.

Specs:

   CPU: AMD Ryzen 3 2200G with Radeon Vega graphics
   RAM: 30737 MB (10697 MB used)
   OS: Ubuntu 22.04.2 LTS
   Display resolution: 1920x1080 pixels
   X11 vendor: The X.Org Foundation
   OpenGL renderer: AMD Radeon Vega 8 graphics (raven, LLVM 15.0.7, DRM 3.47, 5.19.0-43-generic)

I have a QNAP NAS with NFS shares on my LAN and am trying to mount them on my mostly vanilla Ubuntu 22.04 install.

Running showmount on the client shows the NFS shares:

~$ showmount -e nas.localdomain
Export list for nas.localdomain:
/Videos   *
/Public   *
/Games    *
/Download *

The mount command completes successfully...

~$ sudo mount -t nfs nas.localdomain:/ /mnt/nas

... however trying to do anything in the mounted directory hangs (e.g. ls). Nautilus shows the top-level shared directories, but also hangs on trying to access them.

Oddly enough I have 2 other laptops, one running Ubuntu 21.04 and another one running Manjaro, and they both can mount the NAS shares with the exact same command without any problem, so the issue is most likely not with the NFS server but rather the client.

Any idea on how to solve this?

Currently I use the following line in /etc/default/grub:

GRUB_CMDLINE_LINUX_DEFAULT="rd.modules-load=vfio-pci amd_iommu=on iommu=pt kvm.ignore_msrs=1 vfio-pci.ids=10de:1e84,10de:10f8"

The purpose of the above line is to reserve the primary GPU for later use by a VM using vfio.

The setup I have is:

• Asus PRIME B450-PLUS
• AMD Ryzen 7 3700X 8-Core Processor
• Primary: TU104 [GeForce RTX 2070 SUPER] via DP
• Secondary: GK208B [GeForce GT 710] via HDMI
• Lenovo ThinkVision 2560x1440 display with HDMI and DP in (for switching between host and VMs by pressing the monitor buttons).

There is no setting on the mobo as to which GPU is primary and I do not have integrated graphics on the CPU.

What happens now Grub loads and starts showing the messages on the primary GPU and gets to this line:

[ 0.843241] vfio-pci 0000:07:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem

That screen freezes. I then have to type in the LUKS password blindly, wait a bit, then switch the monitor to HDMI for the secondary GPU. At this point I see the Ubuntu log in screen.

What I'd like to happen:

I would like:

1. The GRUB bootloader to use the secondary GPU as soon as it realizes there is one.
2. The messages from GRUB to appear on the secondary GPU so that I get the LUKS prompt and I can type in my password non-blindly.

This would also help with any future boot problems as I'll see what's happening. This would also hopefully remove the video from the primary GPU as currently it just shows the last thing it saw - when the computer goes to sleep, the monitor auto-switches back to the lines from GRUB.

WIRELESS USB DONGLE - BLUETOOTH USB DONGLE - MINI 5.0 - VERSION 5.48 - 0a12:0001

So lately I bought a Bluetooth USB dongle - model no: MLT-5.0-MiNi

I'm using Ubuntu 20.04.1 LTS.

1. After I connected the adapter into USB port, I checked the port typing in terminal lsusb and I got the following:

Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

2. hciconfig -a gave the following:

hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0
        Features: 0xff 0xff 0x87 0xfa 0xdb 0xbf 0x7b 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT

3. hcitool dev:

Devices:

So it seemed that my PC didn't have the driver installed.

4. bluetoothctl --version:

bluetoothctl: 5.53

5. rfkill:

ID TYPE      DEVICE      SOFT      HARD
0  bluetooth hci0   unblocked unblocked

6. And finally btmon:

Bluetooth monitor ver 5.53
Failed to bind channel: Operation not permitted

I found this YouTube video to solve the problem.

1. First of all, I had to install the app "Ubuntu Mainline Kernel Installer" to update until the lastest kernel version, so I typed:

sudo add-apt-repository ppa:cappelikan/ppa
sudo apt-get update
sudo apt-get install mainline

2. Then, before updating to the last kernel version, I had to check what the running kernel version is:

User@PC:~$ uname -r

5.4.0-48-generic

User@PC:~$ uname -sr

Linux 5.4.0-48-generic

3. Later I went to the website of KERNEL and checked what the last Kernel version that's stable is, for example: 5.8.13

After all, I opened the app Ubuntu Mainline Kernel Installer and clicked the last kernel version that is stable, for example: 5.8.13. Finally clicked the button Install.

4. After the installation and reboot, I checked again:

User@PC:~$ uname -r

5.8.13-050813-generic

User@PC:~$ uname -sr

Linux 5.8.13-050813-generic

I saw that it was successful, and the bluetooth USB DONGLE 5.0 is working.

BUT THERE IS ONE PROBLEM TO CONNECT AFTER PAIRING: After pairing Ubuntu with my speaker 5.0, it cannot connect, then after pairing Ubuntu with my smartphone LG, I couldn't send any pictures to smartphone from Ubuntu nor vice versa.

1. I typed systemctl status bluetooth and entered.

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2020-10-03 19:02:12 -05; 10min ago
       Docs: man:bluetoothd(8)
   Main PID: 2173 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4649)
     Memory: 2.2M
     CGroup: /system.slice/bluetooth.service
             └─2173 /usr/lib/bluetooth/bluetoothd

oct 03 19:02:11 PC systemd[1]: Starting Bluetooth service...
oct 03 19:02:12 PC bluetoothd[2173]: Bluetooth daemon 5.53
oct 03 19:02:12 PC systemd[1]: Started Bluetooth service.
oct 03 19:02:12 PC bluetoothd[2173]: Starting SDP server
oct 03 19:02:12 PC bluetoothd[2173]: Bluetooth management interface 1.17 initialized
oct 03 19:02:13 PC bluetoothd[2173]: Failed to set mode: Blocked through rfkill (0x12)
oct 03 19:02:14 PC bluetoothd[2173]: Endpoint registered: sender=:1.75 path=/MediaEndpoint/A2DPSink/sbc
oct 03 19:02:14 PC bluetoothd[2173]: Endpoint registered: sender=:1.75 path=/MediaEndpoint/A2DPSource/sbc
oct 03 19:02:14 PC bluetoothd[2173]: Failed to set mode: Blocked through rfkill (0x12)

I see that there is a problem:

bluetoothd[2173]: Failed to set mode: Blocked through rfkill (0x12)

2. rfkill list:

1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

3. hciconfig -a:

hci0:   Type: Primary  Bus: USB
    BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
    UP RUNNING PSCAN ISCAN 
    RX bytes:1174 acl:0 sco:0 events:65 errors:0
    TX bytes:1046 acl:0 sco:0 commands:65 errors:0
    Features: 0xff 0xff 0x87 0xfa 0xdb 0xbf 0x7b 0x83
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
    Link policy: RSWITCH HOLD SNIFF PARK 
    Link mode: SLAVE ACCEPT 
    Name: 'Daniel-MS-7529'
    Class: 0x1c0104
    Service Classes: Rendering, Capturing, Object Transfer
    Device Class: Computer, Desktop workstation
    HCI Version: 5.0 (0x9)  Revision: 0x810
    LMP Version: 5.0 (0x9)  Subversion: 0x2312
    Manufacturer: Cambridge Silicon Radio (10)

I see that everything is OK.

4. btmon:

Bluetooth monitor ver 5.53
Failed to bind channel: Operation not permitted

5. sudo dmesg | grep -i bluetooth:

[  132.146271] Bluetooth: Core ver 2.22
[  132.146302] Bluetooth: HCI device and connection manager initialized
[  132.146308] Bluetooth: HCI socket layer initialized
[  132.146310] Bluetooth: L2CAP socket layer initialized
[  132.146314] Bluetooth: SCO socket layer initialized
[  132.515401] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds...
[  133.859424] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  133.859426] Bluetooth: BNEP filters: protocol multicast
[  133.859431] Bluetooth: BNEP socket layer initialized
[  135.263551] Bluetooth: RFCOMM TTY layer initialized
[  135.263561] Bluetooth: RFCOMM socket layer initialized
[  135.263570] Bluetooth: RFCOMM ver 1.11
[ 1017.955624] Bluetooth: hci0: inquiry failed: status 0x0c
[ 1023.331631] Bluetooth: hci0: inquiry failed: status 0x0c
[ 3305.392256] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds...

There is one more problem:

Bluetooth: hci0: inquiry failed: status 0x0c

6. Another time, I typed on the terminal hcidump -X and entered and then I went to the setting of Bluetooth to try to pair and connect the speaker and I got the following results on the terminal:

HCI sniffer - Bluetooth packet analyzer ver 5.53
device: hci0 snap_len: 1500 filter: 0xffffffffffffffff

[several lines related to HCI Event]

> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2744 class 0x240404 rssi -25
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 24:FC:E5:6E:53:5B mode 1 clkoffset 0x18bd class 0x08043c rssi -71
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 24:FC:E5:6E:53:5B mode 1 clkoffset 0x18bd class 0x08043c rssi -98
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Random Address (0x08|0x0005) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Parameters (0x08|0x000b) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 128 reason 0x16
    Reason: Connection Terminated by Local Host
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -25
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Random Address (0x08|0x0005) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Parameters (0x08|0x000b) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -27
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -27
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -24
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -24
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -23
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -24
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -23
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -22
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data

Soundcore Flare+ is the speaker's model. I see there is one another problem:

Unknown type 0xff with 9 bytes data

The Bluetooth USB 5.0 works fine on Windows 10 but on Ubuntu 20.04, it doesn't work. So Ubuntu needs drivers for Bluetooth 5.0.

On 5.8.14 Kernel, Ubuntu really displays devices to pair and connect, but the pairing and connecting don't work.

So, could anyone help me to solve this problem of pairing and connecting with devices from Ubuntu?

I found the problem solved for Linux in this website but I don't know how to compile and patch on Ubuntu 20.04, it can work only for Kernel's version 5.8.

My system is Ubuntu MATE 20.04. I have a problem with:

[    2.037058] ata2: softreset failed (device not ready)
[    2.037080] ata1: softreset failed (device not ready)
[    2.225055] ata3: softreset failed (device not ready)

I use 3 hard drives including one SSD.

My computer components (quite old):

• AMD Phenom X4 9750

• Gigabyte GA-MA770-UD3 motherboard

• RAM 7GB

• SSD Micron 1100

• 2 Hard drives

• Nvidia GeForce 9800GT Zalman

I have 2 Ubuntu machines (1 laptop, 1 desktop). I want to log in to the desktop from the laptop when I am either or the same network or not.

The desktop, as suggested in a few places, seems to have all the correct "sharing" options turned on.

Additionally, I have Remmina (1.4.7) installed.

I know the IP of my desktop (fwiw, I used: showmyipaddress.eu.

On my laptop I also have file sharing, screen sharing and remote login turned on (this is probably overkill).

I also have Remmina installed (currently 1.4.7).

Now I can connect to the desktop using the "local" name:

But when I try to use the same method, but change the local name to the external IP address, I get "unable to connect to the VNC server".

What do I need to do to make this work?

I have my office quite a distance away from my wifi AP, with my desktop connected with a single ethernet cable, and the game console docked in the same room.

Right now, in order to give it internet, I'm having to use a USB wifi adaptor to create a wifi hotspot that only the console connects to, I have been looking into giving it a wired connection but the idea of having to buy an ethernet switch just to add another device and then a USB to ethernet adapter seems like quite an expense and not worth the trouble cable-managing.

Would it be possible to use a USB A-A cable so my desktop acts as an ethernet to usb adapter itself?

Edit: Forgot to mention I'm running ubuntu desktop 20.04

I want to access my Xubuntu desktop machine remotely, and see the same desktop as is shown on the remote machine's monitor. By default using both VNC and xrdp, one gets a new desktop session, and I don't want that.

The possibilities seem to be:

• vino
• x11vnc
• xrdp

The only half-way secure solution I seem to be able to get is to use

UNIXPW_DISABLE_SSL=1 x11vnc -unixpw -localhost

and create my own systemd service file for that, and then connect to that over an SSH tunnel.

vino

I use a Danish keyboard, and vino doesn't seem to support that because of this bug. Not being able to use æøå or any special characters such as <>|;. rules out vino for me. Also, vino is poorly supported on XFCE, because vino-preferences has been removed.

x11vnc

x11vnc mostly works, but, but there doesn't seem to be any way to store a password securely. Using a VNC password file is possible, but is limited to 8 characters and and trivially decryptable, so is only security-by-obscurity at best. x11vnc using -nopw (and -local so it isn't available over the network requiring use over an SSH tunnel) works, but then any process (running as any user) on the desktop machine can access my logged-in desktop and that is not good.

x11vnc has options for secure connections: -ssl and -stunnel. For -ssl, Remmina showed: "TLS handshake failed: A TLS fatal alert has been received.." and xtightvncviewer showed: "Server did not offer supported security type" while if the server used -stunnel both viewers just sat there and didn't complain but also didn't start up a VNC window.

x11vnc has a -unixpw that "will use the su(1) program to verify the user's password". But that requires either -ssl or -stunnel and -localhost, but neither -ssl nor -stunnel worked for me when connecting with Remmina or xtightvncviewer. But setting the UNIXPW_DISABLE_SSL=1 environment variable "disables requiring either -ssl or -stunnel" according to the man page.

And UNIXPW_DISABLE_SSL=1 x11vnc -unixpw -localhost and then running it over an SSH tunnel seems to be almost nirvana. But with -unixpw I can't store the credentials in Remmina (that stores the password in gnome-keyring). But have to enter them every time. And frankly it looks horrible / bad user experience in my personal opinion.

xrdp

xrdp seems to either start an independent desktop session, or can connect to a running desktop over - drumroll - vino or x11vnc and so I get all the problems outlined above, in addition to whatever issues xrdp introduces.

Is there really no better secure way of accessing my desktop? For real?

What I ended up doing

Edit: In the end, I went for the hopelessly insecure -rfbauth /home/user/.vnc/passwd (and another password!) instead of -unixpw. Combined with -localhost and using an SSH tunnel because the user experience of -unixpw was just too bad. l. And needed to add some more options, so the final systemd config was:

[Unit]
Description=x11vnc VNC Server for X11
Requires=lightdm.service
After=lightdm.service

[Service]
Type=simple
ExecStart=/usr/bin/x11vnc -auth /var/run/lightdm/root/:0 -display WAIT:0 -forever -shared -rfbauth /home/user/.vnc/passwd -rfbport 5900 -localhost
ExecStop=/usr/bin/killall x11vnc
Restart=on-failure
RestartSec=2
SuccessExitStatus=3

[Install]
WantedBy=graphical.target

When I turn on my laptop, everything seems to boot normally and I enter my decryption key to decrypt my hard drive. Then I'm taken to my login page, but when I try to type in my password, none of my keys work and I can't move my mouse. Why is this happening?

Earlier I had a problem where I would get a black screen of death whenever I turned on my laptop and I resolved this by going into recovery mode and reinstalling Nvidia drivers. Now I have the problem mentioned above and whenever I go into the root terminal in recovery mode, I find that I'm not able to install any packages. I can't even do a simple sudo apt-get update.

What is happening?

I was using Windows 10. Then I installed Ubuntu 18.04 LTS as multiboot. Grub2 replaced Windows bootloader. I wanted Windows bootloader, so I installed EasyBCD 2.3 on my Windows 10. I created a new Linux entry on it. When I booted I had two entries, but instead of booting to Ubuntu it booted to "grub4dos".

I used the Boot-Repair tool via live USB. It reinstalled grub2, but now I have two bootloaders. grub2 loads first. Then, when I select Windows 10 from it, Windows bootloader loaded up. I have to select Windows from it to boot into Windows 10. As I use Windows 10, regularly. I have to go through two bootloaders to get to my Windows 10.

I like to have either grub2 or Windows bootloader which boots both OSs with single click.

I use a laptop with a single HDD.

I had tried different options on EasyBCD but every time I end up using my Boot-Repair live USB to reinstall grub2.

I had Ubuntu 17.10 installed alongside Windows 10 and everything was working normally. I deleted the Ubuntu partition, then the Windows partition and finally formatted the hard disk. Now when I open the laptop it shows an "Ubuntu boot failed" message and then "Windows Boot Manager boot failed" and it shows this black screen.

Intel UNDI, PXE-2.1 (build 083)  
Copyright (C) 1997-2000 Intel Corporation

This Product is covered by one or more of the following patents:  
US6,570,884, US6,115,776 and US6,327,625

Realtek PCIe GBE Family Controller Series v2.57 (08/27/13)  
PXE-E61: Media test failure, check cable  

PXE-M0F: Exiting PXE ROM.  
No bootable device -- insert boot disk and press any key.

How to solve this problem? I want to install Ubuntu again without any problems.

I'm having some strange issues with a fresh VNC server install. I recently built a new Plex server, and it's running gnome Ubuntu 16.04. So far, I've gotten the openSSH server up and running with Google 2FA authentication. Now I'm working on getting vnc working so that I can ultimately run this headless, and remote into it with vnc through SSH when need be.

I started out running just:

sudo apt-get install vnc4server

then, ran vncserver to configure it and set the password, so far, so good.

I then went to my client PC (Windows 10), and attempted to connect without SSH, just to make sure it's working. That's the first issue, upon connecting, I'm getting just a grey screen, which I think is due to the desktop environment not coming up correctly with the connection is made, which I think I can fix by modifying the ~/.vnc/xstartup file.

So back on the server, I ran:

sudo gedit ~/.vnc/xstartup

Now I'm receiving an error, anytime I try to open a gui application as sudo, that error is:

[sudo] password for username:
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

(gedit:12145): Gtk-WARNING **: cannot open display: :0

Now I'm lost. I'm 100% sure this is related to VNC, but even shutting down the VNC server doesn't fix it.

Anyone got any ideas? I'm just spinning my wheels and getting frustrated at this point.

After some searching, I didn't find exactly what my problem is, or at least I should not relate it to any past questions I found.

Old setup

HDD with 2 partitions, grub booting Ubuntu on one and Windows 7 on the other. Everything went just fine.

New setup

One/two months ago I bought an SSD and I'm now writing this from its Windows 10. It has only this partition.

HDD got its Windows 7 partition formatted, but not the Ubuntu's. Problem is: when I try to boot (hotkey at the boot menu) from the HDD, it doesn't work anymore.

My understanding of the problem

I didn't wipe out the entire HDD contents, only the Windows 7 partition, so I thought even if Windows wouldn't boot anymore (obviously), Ubuntu would. I don't think I got the knowledge to fix this up because I don't know if I can fix it as it is now or if I must wipe out the Ubuntu partition and start over, or if I have to wipe grub from that drive (and I don't even know how to do this), lots of questions are popping up!

What I want to learn

The desired result is: Windows 10 booting from the SSD as it is now. Ubuntu booting from HDD partition #2 (if I recall the order number). HDD partition #1 serving as storage for Windows 10.

I don't care if boot process is either:

• From the HDD, like "PC turns on, HDD starts grub, I choose, grub does his things" or
• From boot hotkey, like "PC turns on, I press the boot device hotkey, choose drive, OS boots"

I just need it working as soon as possible.

I managed to boot using the grub prompt, but I got to tty. Then as I found no problem there, I tried to reboot. When the Ubuntu logo (the loading screen) showed up was my last moment of happiness: it stopped there. Maybe something went wrong with the video drivers, my video card or the monitor?

fdisk -l output:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes  
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors  
Units = sectors of 1 * 512 = 512 bytes  
Sector size (logical/physical): 512 bytes / 4096 bytes  
I/O size (minimum/optimal): 4096 bytes / 4096 bytes  
Disk identifier: 0xf4ca1ca3  

   Device Boot      Start         End      Blocks   Id  System  
/dev/sda1   *        2048      206847      102400    7  HPFS/NTFS/exFAT  
/dev/sda2          206848  1495039999   747416576    7  HPFS/NTFS/exFAT  
/dev/sda3      1495042046  1953523711   229240833    5  Extended  
Partition 3 does not start on physical sector boundary.  
/dev/sda5      1945526272  1953523711     3998720   82  Linux swap / Solaris  
/dev/sda6      1495042048  1945526271   225242112   83  Linux  

Partition table entries are not in disk order

Disk /dev/sdb: 120.0 GB, 120034123776 bytes  
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors  
Units = sectors of 1 * 512 = 512 bytes  
Sector size (logical/physical): 512 bytes / 512 bytes  
I/O size (minimum/optimal): 512 bytes / 512 bytes  
Disk identifier: 0x6597ec03  

   Device Boot      Start         End      Blocks   Id  System  
/dev/sdb1   *        2048     1026047      512000    7  HPFS/NTFS/exFAT  
/dev/sdb2         1026048   234438655   116706304    7  HPFS/NTFS/exFAT  

Disk /dev/sdc: 8004 MB, 8004304896 bytes  
255 heads, 63 sectors/track, 973 cylinders, total 15633408 sectors  
Units = sectors of 1 * 512 = 512 bytes  
Sector size (logical/physical): 512 bytes / 512 bytes  
I/O size (minimum/optimal): 512 bytes / 512 bytes  
Disk identifier: 0x027e5a9a

   Device Boot      Start         End      Blocks   Id  System  
/dev/sdc1   *        2048    15633407     7815680    c  W95 FAT32 (LBA)

I'm installing ubuntu 14.04 on a machine which currently runs windows 8.

I selected the option to completely erase the hard drive and do a clean install of ubuntu. I also selected the options to download updates and install 3rd party software. Ubuntu ran fine off the usb, but now im trying to install it, it copies around 80% of the files, but then seems to freeze. I can still click through the features, and the task bar buttons seems responsive, but the cursor is stuck on the spinning mode and the loading bar hasn't moved for at least 15 mins.

Is it safe to reboot to try again? Any help would be much appreciated

I have setup disk encryption with LUKS and configured it to auto-mount when the system boots up. So now as it is supposed to, it prompts me for a passphrase when the system boots up. If I enter the correct passphrase it continues to the system.

However, in some cases, I might want to log in without the passphrase. Is there a way to do that?

I tried to install Ubuntu to my Toshiba Satellite from a created disk. After setting partitions, installation took an extreme amount of time and then shut down. I now cannot boot any operating system. A black screen with a cursor in the left upper corner is the only thing that comes up. I can reach the BIOS screen only by pressing the F2 key at startup.

I have tried a restore with original restore disks, but nothing is recognized. I have tried to boot Ubuntu from a disk, but nothing is recognized, so nothing boots from my CD drive. What else can I do? Is there a way to wipe the computer clean and simply fresh install Ubuntu? No other function key works during startup except for F2 to access the BIOS.

I would like to use CUDA on my Ubuntu machine with the graphics card NVIDIA Geforce 9600 GT. Installing CUDA is no problem but in order to run any CUDA code I need to install the proprietary NVIDIA driver as well.

I did so by choosing an appropriate one (for example, 331) from the list popping up in the "Additional drivers" menu. The installation works just fine but whenever I reboot the system all I see is a black screen with a blinking cursor.

After purging all NVIDIA related stuff (sudo apt-get remove --purge nvidia*), I'm able to use the system again after rebooting.

I read somewhere that this problem might be related to the fact that I have to use DVI instead of VGA as there are no other output ports on the card. However, switching from one DVI output port to another doesn't help either.

Any help is greatly appreciated.

The last command may show too few lines of user login info, truncated by when the “wtmp begins”.

If I want to get as much as possible last info (e.g., to see if my system was accessed from any unknown/suspicious IP using my username), how can I output the older “last” info?

If I use last -2000, intending to see 2000 lines of output, but the command may only return just a few lines, anything that happened before the “wtmp begins” would be truncated.)

Just wondering somehow if it is possible to output as many lines of login info as possible.

This is my first time using/installing Ubuntu. I booted from a USB and it was running, however when I started to "install" it for the second time (getting rid of Windows completely) halfway through this second install the laptop froze. I shut it down and to my horror it will not start. It just has a black screen with a blinking cursor bar in the top right hand corner.

I assume that it didn't fully install Ubuntu and it wiped Windows and it won't load Ubuntu because I need Windows to do that.

Do you have any ideas about how to fix this?