Quantcast
Channel: Ubuntu Forums - Installation & Upgrades
Viewing all 26379 articles
Browse latest View live
↧

Ubuntu 18.04 installation issue

March 31, 2020, 2:14 pm
$
0
0
Hello,
while trying to install Ubuntu 18.04 from a live USB (the system was previously Windows and I opted to erase Windows) I encountered the issue described in this post. As instructed in that post, I inserted the line "pci=noaer" into the GRUB and managed to finally install Ubuntu. The issue is that it only allowed me install it in OEM installation mode. I would really like to have a traditional install route, and understand what exactly was initially causing me this install issue. Is there anything I can do now that I have installed Ubuntu on my system (albeit in OEM mode) to reverse engineer what was causing the issues in the first place, that would then allow me to fix the installation issues and install Ubuntu normally ? I have no issue doing a fresh install (I haven't used the new Ubuntu install yet).
↧
Search

[ubuntu] Raspberry Pi 4 4GB, can't get ubuntu-desktop to work

April 1, 2020, 9:25 am
$
0
0
I have a Raspberry Pi 4 4GB that I'm trying to install Ubuntu 19.10.1 on to, but no matter how many times I wipe the SD card, re-download the Ubuntu image, etc. it fails to start the desktop. Here is what I'm doing:
I download the 64bit (also tried 32bit) 19.10.1 image for the Pi 4 from https://ubuntu.com/download/raspberry-pi
I follow the directions from https://ubuntu.com/tutorials/create-...ows#1-overview
I un-zip the image from its .xz container using 7zip, then use Win32DiskImager to flash the image to my 128GB SD card (I've also tried Rufus and Belina Etcher, also tried an 8GB SD card)
I put the SD card in my Pi 4 and boot with ethernet connected, I wait ~5 minutes to let everything boot and calm down, log in with ubuntu ubuntu, change my password, sudo apt update, sudo apt upgrade, reboot, sudo apt install --no-install-recommends ubuntu-desktop. (I also tried without the --no-install-recommends, and tried with lubuntu-desktop)
Everything downloads and installs fine, there are no popups or anything and after about half an hour it is finished.
At this point I type startx and it fails, if I reboot I'm greeted with a blank screen with a blinking cursor, I can type but nothing happens. I've attached pictures of the screen for the failed startx, and the xorg log file.
What do I need to do to fix this?
IMG_20200401_111444.jpgIMG_20200401_111627.jpgIMG_20200401_111653.jpg
Attached Images
↧
↧

[other] Upgrade to kernel 5.x problem

April 1, 2020, 10:29 am
$
0
0
Hi guys, first time I've seen this, I'm trying to upgrade my kernel to a more recent version in my Ubuntu Bionic:

Kernel: 4.15.0-20-generic
Command: sudo parted -l
Response:
Modelo: ATA SSEA4M8240GDS (scsi)
Disco /dev/sda: 240GB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: msdos
Indicadores de disco:

Numero Inicio Fin Tamaño Tipo Sistema de archivos Banderas
1 1049kB 210GB 210GB primary ntfs
2 210GB 239GB 29,2GB primary ext4
3 239GB 240GB 1099MB extended
5 239GB 240GB 1099MB logical linux-swap(v1)

Error: /dev/mmcblk0boot0: etiqueta de disco no reconocida
Modelo: Tarjeta de almacenamiento SD/MMC genérica (sd/mmc)
Disco /dev/mmcblk0boot0: 4194kB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: unknown
Indicadores de disco:

Error: /dev/mmcblk0boot1: etiqueta de disco no reconocida
Modelo: Tarjeta de almacenamiento SD/MMC genérica (sd/mmc)
Disco /dev/mmcblk0boot1: 4194kB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: unknown
Indicadores de disco:

Modelo: MMC Biwin (sd/mmc)
Disco /dev/mmcblk0: 30,9GB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: gpt
Indicadores de disco:

Numero Inicio Fin Tamaño Sistema de archivos Nombre Banderas
1 1049kB 106MB 105MB fat32 EFI system partition arranque, esp
2 106MB 123MB 16,8MB Microsoft reserved partition msftres
3 123MB 30,1GB 30,0GB ntfs Basic data partition msftdata
4 30,1GB 30,9GB 839MB ntfs Basic data partition oculta, diag

Command: blkid
Response:
/dev/mmcblk0p1: LABEL="SYSTEM" UUID="D05A-9ED8" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="44cbc224-6734-44e1-bfeb-cae75dd46865"
/dev/mmcblk0p3: LABEL="Windows" UUID="4A20687C206870BD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="12653868-4e52-4710-a8a5-d371c868b3d6"
/dev/mmcblk0p4: LABEL="Recovery" UUID="64966A1B9669EE4C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a4ba2a45-e210-4323-895e-400ca5c0ed4a"
/dev/sda1: UUID="10D0FDC8D0FDB456" TYPE="ntfs" PARTUUID="1373d5a9-01"
/dev/sda2: UUID="1379020b-b071-42d7-aca7-1a78701bb326" TYPE="ext4" PARTUUID="1373d5a9-02"
/dev/sda5: UUID="e49618cf-97d3-4cde-8997-00a3e0d5af0f" TYPE="swap" PARTUUID="1373d5a9-05"
/dev/mmcblk0: PTUUID="4d32ded6-1ef7-4cae-acfa-6bfa1c7d1c5b" PTTYPE="gpt"
/dev/mmcblk0p2: PARTLABEL="Microsoft reserved partition" PARTUUID="4fa942bb-dc40-48ad-8785-9c6795678e59"

Upgrade to kernel 5.x without any problem and update-grub runs without any problem, says: "done":

(Leyendo la base de datos ... 254403 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../linux-modules-5.3.0-45-generic_5.3.0-45.37~18.04.1_amd64.deb ...
Desempaquetando linux-modules-5.3.0-45-generic (5.3.0-45.37~18.04.1) ...
Seleccionando el paquete linux-image-5.3.0-45-generic previamente no seleccionado.
Preparando para desempaquetar .../linux-image-5.3.0-45-generic_5.3.0-45.37~18.04.1_amd64.deb ...
Desempaquetando linux-image-5.3.0-45-generic (5.3.0-45.37~18.04.1) ...
Configurando linux-modules-5.3.0-45-generic (5.3.0-45.37~18.04.1) ...
Configurando linux-image-5.3.0-45-generic (5.3.0-45.37~18.04.1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.18.0-25-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-4.18.0-25-generic
I: /vmlinuz is now a symlink to boot/vmlinuz-5.3.0-45-generic
I: /initrd.img is now a symlink to boot/initrd.img-5.3.0-45-generic
Procesando disparadores para linux-image-5.3.0-45-generic (5.3.0-45.37~18.04.1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.3.0-45-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generando un fichero de configuración de grub...
Encontrado fondo de pantalla: /etc/grub.d/backgrounds/bodhi.png
Aviso: Ya no se soporta fijar GRUB_TIMEOUT a un valor no nulo cuando GRUB_HIDDEN_TIMEOUT está fijado.
Found background image: /etc/grub.d/backgrounds/bodhi.png
Encontrada imagen de linux: /boot/vmlinuz-5.3.0-45-generic
Encontrada imagen de memoria inicial: /boot/initrd.img-5.3.0-45-generic
Encontrada imagen de linux: /boot/vmlinuz-4.18.0-25-generic
Encontrada imagen de memoria inicial: /boot/initrd.img-4.18.0-25-generic
Encontrada imagen de linux: /boot/vmlinuz-4.15.0-20-generic
Encontrada imagen de memoria inicial: /boot/initrd.img-4.15.0-20-generic
Encontrado Windows Boot Manager en /dev/mmcblk0p1@/EFI/Microsoft/Boot/bootmgfw.efi
Añadiendo menú de entrada de inicio para la configuración del firmware EFI
hecho

Situation: Booting into the new kernel gives error: "Timed out waiting for device dev-disk-by\x2duuid-D05A\x2d9ed0.device", the UEFI partition is in the missing device!, but more strange is:

fgonzalez@mbook:~$ sudo parted -l
Modelo: ATA SSEA4M8240GDS (scsi)
Disco /dev/sda: 240GB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: msdos
Indicadores de disco:

Numero Inicio Fin Tamaño Tipo Sistema de archivos Banderas
1 1049kB 210GB 210GB primary ntfs
2 210GB 239GB 29,2GB primary ext4
3 239GB 240GB 1099MB extended
5 239GB 240GB 1099MB logical linux-swap(v1)

fgonzalez@mbook:~$

Ok... I said: hummmm strange! where is "/dev/mmcblk0"? UEFI is in there so the question is: what's going on??? any clues, thoughs, suggestions, advice are very very welcome because I don't have any clue!

Regards!

Francisco
↧

Target Packages (Packages) is configured multiple times

April 1, 2020, 10:40 am
$
0
0
Hello,

After purging NVIDIA I proceeded with update and here is outcome:

Code:
pavel@ALABAMA:~$ sudo apt-get update
Hit:1 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Hit:2 http://fr.archive.ubuntu.com/ubuntu bionic InRelease                                                                     
Hit:3 http://fr.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                             
Hit:4 http://fr.archive.ubuntu.com/ubuntu bionic-backports InRelease                                     
Ign:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease
Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease       
Hit:7 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  Release
Reading package lists... Done                     
W: Target Packages (Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list.d/cuda.list:1
W: Target Translations (en_US) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list.d/cuda.list:1
W: Target Translations (en) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list.d/cuda.list:1
W: Target Packages (Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list.d/cuda.list:1
W: Target Translations (en_US) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list.d/cuda.list:1
W: Target Translations (en) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list.d/cuda.list:1
Any suggestions ?
Thanks.
↧

How to uninstall a kernel?

April 1, 2020, 12:46 pm
$
0
0
After updating today nvidia 390xx driver don't work. I have to boot to old kernel. How to uninstall this new kernel? Linux mb2 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
↧
↧

Gnome doesn't come up on 19-10

April 1, 2020, 2:57 pm
$
0
0
I go nowhere with a previous thread https://ubuntuforums.org/showthread.php?t=2436558 so I am trying again.

I purchased a slightly-used Dell Optiplex 9020 and installed Ubuntu 19-10 on it. It ran for a while but then after installing regular updates the startup didn't complete because Gnome never initialized. I do not know why Gnome wouldn't come up because I do not understand any of the messages in the log. Then for a while the system suddenly started working again until again a regular update caused a repetition of the Gnome startup failure. I tried rebooting multiple times. For a couple of days I got fed up and instead ran the system by booting from my Ubuntu 19-10 install USB. But while that provided some service I could not, for example, access my e-mail because Thunderbird on the USB refused to load the profile, complaining that it was for a newer version of Thunderbird even after I applied all outstanding updates to the USB.

So I tried to boot the system into recovery mode. I have the system set for BIOS boot so I held down the shift key. No change: the system booted up as before, with no pause to display the GRUB menu, and Gnome did not come up. So I tried holding down the ESC key. I still didn't get the GRUB menu but this time the system came up! WTF?

I would really like to understand what is going on so I can fix it once and for all. If Gnome doesn't come up what do I look for in the log to see WHY it didn't complete?
↧

[ubuntu] Upgrade Early, Still Get Updates?

April 1, 2020, 5:51 pm
$
0
0
If I were to upgrade early to 20.04 from 19.10, will I still get regular updates for it following the official release?
When the official version is released, will the Beta turn into the official version?

Btw, @ what time tomorrow is the 20.04 Beta supposed to be released?
↧

[ubuntu] Convert Desktop 19.10 to Server 19.10 because server installation fails

April 2, 2020, 3:47 am
$
0
0
Hi,

I had some issues with installing the Ubuntu 19.10 Server installation (did not find the NIC drivers/firmware), so I had to install Ubuntu 19.10 Desktop instead.
Is there a way to convert my current Ubuntu Desktop to a Ubuntu Server?

ps. the source of my problem is of course that I could not install Server 19.10 due to driver, and it has me wondering why the server install disk doesn't ship the same drivers/firmware. And if there is a way to add them to the install disk for next time.

Drivers:
Intel Wi-Fi 6 AX201
Intel Ethernet Connection I219-V


Thanks!
↧
Search

Repair boot configuation

April 2, 2020, 9:10 am
$
0
0
Hi,

I bought a SSD card for my laptop where I installed Lubuntu 19.10 using a bootable USB. The installation process went fine (just followed the instructions on internet) but unforthunatly I couldn‘t see Lubuntu as an option on my BIOS menu. When trying to solve this proble I booted again to the USB and installed Gparted....That‘s were things got worse, when trying to solve the issue, I deleted the boot partition that was on my Primary Disk need to boot Windows 10..As a result I can‘t boot now neither my Windows or the installed Lubuntu on the SSD because I can‘t see both of them on the BIOS menu.

I have read many posts and tried diffrent solutions but I still didn‘t manage to solve the problem. I‘m completely new to Ubuntu/Linux and thus having more issues understanding what to do. I have tried Boot-Repair but when launching the test I get an error saying that I need to creat a GPT boot partition first. I also tried under advanced options to repair the GRUB did not solve the problem (may be wrong options ?).
The Windows partiton with all my data seems to be fine.
I would be very grateful if you could help.
Ideally I would like to get windows running again with my current data and have lubuntu running on the SSD card.

P.S: wasn‘t sure which system information to include into my post.
↧
↧

[ubuntu] Region Setting Issue

April 2, 2020, 3:24 pm
$
0
0
Every time I install Ubuntu 19.10 as a clean install I select US as both the keyboard layout and country however despite this the installer always sets everything to Canada as the region which in and of itself does not prevent installation but when trying to change this after the fact it never fully changes meaning sites that pull up different pages based on your region default to Canada so prices are always CAD and not USD.

It does not seem to matter what i set the region to in the installer if its English and US as the language it defaults to Canada. Also, the updates server for Apt is set to Canada as well which is easy enough to change but it defaults to this.

My question is this if I load up the Live ISO and change the region on the live instance and then install it will this make a difference? Does the installer pull from default configurations or does it use the modified ones (if you changed any settings) from the live instance?

I did not seem to have this issue with 18.04 (that i remember anyway) and its easy enough to get around i just change my region on those sites manually but it would be nice if my update server and region info did not auto default to Canada.
↧

Needed packages being marked for autoremoval??

April 3, 2020, 12:10 am
$
0
0
I haven't tried a lot of Linux, just Fedora, and I never met this kind of stuff before. Is this normal? Is this a bug?

Packages, needed packages are being marked for autoremoval. Example:





amd64-microcode gnome-system-monitor intel-microcode iucode-tool libburn4 libisofs6 libjte1 libmetacity1 metacity-common mousepad ristretto thermald tp-smapi-dkms xfburn

gnome-system-monitor --- I have gnome, and I might need gnome system monitor.
mousepad --- I'm using it along side with gedit.
xfburn --- it's part of XFCE.

What's going on here??
↧

[ubuntu_studio] Unable to install GRUB in /dev/sda

April 3, 2020, 3:59 am
$
0
0
I was trying to install Ubuntu Studio 19.10 alongside Windows 10 on my 'hp notebook 15' . In the end the error in the image shows up.

Now I can't even start my windows.

Please help!!!
Attached Images
↧

[lubuntu] Can't install GRUB on lubuntu 18.04.4 32 bit EeePC

April 3, 2020, 4:56 am
$
0
0
So I have this EeePC and i used Lubuntu on it for some time, but then i had to format the drives as i started experimenting with different things on it.
Long story short, I started installing Lubuntu again. On the live cd i opened Disk and formatted the two ssd that it has, with erase option enabled, and proceeded with the installation (on /dev/sdb, 16GB, as /dev/sda is only 4GB)

Everything went fine until the very end when it said it can't install grub on /dev/sda. i tried to change it to /dev/sdb, /dev/sdb1 or /dev/sda1 but every time it failed.
I'm not sure what is the problem, i searched different sites, tried to install it manually with boot-repair app from the live usb, but nothing helped.

The only thing different now is that i tried installing 18.04.4 desktop version, while the last time i had 18.04 alternative version, but i don't see why this should be an issue.
I see in some places people say to disable secure boot from bios, but i'm not even sure if this EeePC have that option to begin with. there is an option to set password in the bios, but it's disable. not sure if that is it.

as a side note i tried installing batocera on the /dev/sda and it went fine and is booting. then tried installing lubuntu again on /dev/sdb with batocera still on, and with batocera removed by format (with erase) but nothing changed
↧
↧

[ubuntu] Not getting option "Normal installation" when installing ubuntu 18 on Windows 10

April 3, 2020, 5:29 am
$
0
0
Hi All,
I am trying to install dual-boot Ubuntu 18 from Windows 10 but I am getting error "need atleast 8 GB". This means that my hard disk is not being detected. Please help.
FYI, I have already disabled fast boot.

BIOS details:
SATA mode: Intel RST Premium with Intel Optane System accelaration
Intel RST 17.0.0.3720 RAID driver
Non-RAID physical disk: PCIe 1.0 IntelSSD ...

Physical DIsk info:
Model: IntelSSD512GB
Status: Non-RAID
Controller type: NVMe
Controller interface: PCIe

Let me know if any other details are required to help me out.

Thanks in advance..
↧

Blank screen when coming from Ubuntu

April 3, 2020, 9:55 am
$
0
0
Hi, I wasn't quite sure where to post this, but this is my issue:

I freshly installed Windows 10 and Ubuntu 19.10 shortly after for dual booting. My computer is a Lenovo ThinkPad L390 Yoga connected via USB Type C to a dock with keyboard, mouse, monitors, network etc.
If I shutdown the computer when running Ubuntu and try to start it again, the screen stays blank, it doesn't even show the BIOS logo, only the fan speeds up. If I unplug the Type C cable then, the screen suddenly turns on, asks me to open BIOS setup and continues to boot normally into GRUB. However, if shutdown the computer when running Windows, it also boots normally if connected to the dock.
↧
Search

[ubuntu] Installed 20.04, unable to load grub

April 3, 2020, 11:09 am
$
0
0
just replaced 16.04 with 20.04 beta and grub unable to load (it was fine with 16.04 where I dual boot with Windows). Now I am forced into 20.04 every time. I have run boot repair and still no grub menu (.txt below). Any ideas?

https://paste.ubuntu.com/p/xsdyCQZMPW/


↧

Upgrade from hard drive to SSD

April 3, 2020, 11:38 am
$
0
0
I bought a faster old computer that has win 10 currently installed. I want to upgrade the internal drive to an SSD and add Ubuntu to it.
There is only one internal drive bay - so I am unable to add the second drive and clone from one to the other easily. Is there another way to clone to an SSD through USB perhaps?
↧
↧

Help cleaning up disk drive/installations

April 3, 2020, 12:40 pm
$
0
0
Over the years I routinely upgrade/update my Ubuntu/Windows installation. Lately I have noticed an accumulation of kernals and related that I would like to remove (see below). I only want to keep Ubuntu and win10. What is a safe way to clean the rest of this up?


Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.0-45-generic
Found initrd image: /boot/initrd.img-5.3.0-45-generic
Found linux image: /boot/vmlinuz-5.3.0-42-generic
Found initrd image: /boot/initrd.img-5.3.0-42-generic
Found linux image: /boot/vmlinuz-5.3.0-40-generic
Found initrd image: /boot/initrd.img-5.3.0-40-generic
Found linux image: /boot/vmlinuz-4.15.0-91-generic
Found initrd image: /boot/initrd.img-4.15.0-91-generic
Found Windows Recovery Environment on /dev/sda1
Found Windows 10 on /dev/sda2
Found Windows 7 on /dev/sda3
Found Ubuntu 14.04.1 LTS - KODIbuntu (14.04) on /dev/sda6
Found linux image: /boot/vmlinuz-5.3.0-45-generic
Found initrd image: /boot/initrd.img-5.3.0-45-generic
Found linux image: /boot/vmlinuz-5.3.0-42-generic
Found initrd image: /boot/initrd.img-5.3.0-42-generic
Found linux image: /boot/vmlinuz-5.3.0-40-generic
Found initrd image: /boot/initrd.img-5.3.0-40-generic
Found linux image: /boot/vmlinuz-4.15.0-91-generic
Found initrd image: /boot/initrd.img-4.15.0-91-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Recovery Environment on /dev/sda1
Found Windows 10 on /dev/sda2
Found Windows 7 on /dev/sda3
Found Ubuntu 14.04.1 LTS - KODIbuntu (14.04) on /dev/sda6
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Recovery Environment on /dev/sda1
Found Windows 10 on /dev/sda2
Found Windows 7 on /dev/sda3
Found Ubuntu 14.04.1 LTS - KODIbuntu (14.04) on /dev/sda6
↧

Split Screen after boot - user's log in

April 3, 2020, 2:00 pm
$
0
0
Hi people,


When I arrived at the login screen, I noticed that my screen was separated in half (login screen and black). The weird thing is that I can still enter my password. After I hit 'enter', the screen works fine.
How to fix this?
Attached Images
↧

[ubuntu] questions on adding partition for 20.04 root

April 3, 2020, 3:23 pm
$
0
0
Getting ready to install 20.04 & need to be sure I plot everything correctly.

Here is the partition info of my SSD:

Code:
Number  Start  End    Size    File system    Name              Flags
 5      1049kB  2097kB  1049kB                                    bios_grub
 1      2097kB  211MB  209MB  ext4
 2      211MB  43.2GB  42.9GB  linux-swap(v1)  Linux filesystem
 3      43.2GB  96.8GB  53.7GB  ext4            root
 4      96.8GB  2000GB  1904GB  ext4            home
The idea is to shrink the home partition by 50GB (/dev/sda4) and put 20.04 root there. Ideally, I'd rather use gparted to put the new 20.04 root *before* /home -- note I will be sharing /home between both 16.04 and 20.04 -- but does it matter? What's the best way to proceed?

I just booted to the thumbdrive of 16.04 to make a dry run: I noticed that when I "shrank" /home and then tried to "create" the new partition at the end of the drive, the only option was to make it a primary partition -- just curious why I was apparently unable to make it a logical partition.

Also, if I do resize /home a new partition, will the UUID of the current (16.04) root change? Guess if it does, I can simply go into the 16.04 fstab and change root to the new UUID, though I'd just as soon not bother.

And... can I tell 20.04 to use the same swap partition as 16.04 is now?

Any caveats?
↧
Viewing all 26379 articles
Browse latest View live
Search