no GUI after upgrade to buster

Help with issues regarding installation of Debian

no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 11:58

I can't boot into debian 10 after upgrade from stretch.
I have following OSs installed alongside debian xfce: Windows, Linux mint xfce, ubuntu xfce. After installing buster I can only access ubuntu, neither LM or debian boot into GUI. (for a moment though I could load LM but then it was gone as well).
On debian I have separate / and /home partitions (they were already there before upgrade). I followed properly (as it seems) the upgrade procedure, I did format / root partition, but left /home untouched, just assigned new /home to old /home, while new / root partition was placed on old, formatted / root. Now I can see that system is booting directly into / root partition instead of /home which ends up with GUI not loading, only cmd line is available. But I can access /home in graphical mode from ubuntu (as well as via cmd), so files are in place.

attached are blkid readings and fstabs from debian and ubuntu, and screenshot of gparted from ubuntu.

Now, there might be one thing I did not do properly during upgrade: I did not assign swap partition, so installer did it on its own accord and assigned all 3 swap partitions available during upgrade to debian. I don't know if that could have affected the process.

couldn't find an answer in extensive internet research so my last resort is to open a call here.
your help would be appreciated.
...............
for some reason I can't upload attachments so I copy the contents below:

1. blkid from debian
/dev/sda1: LABEL="SYSTEM" UUID="98C9-B5E4" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9d3228d5-f86e-491a-bdad-f7f6288bbba5"
/dev/sda2: LABEL="Recovery" UUID="7C12EB1512EAD366" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c3a08008-e49c-4a1b-8f61-26f1523ac02e"
/dev/sda4: LABEL="OS" UUID="B4DCEE5ADCEE1700" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="42714427-cb04-42c7-899f-2c355d26e8c1"
####/dev/sda5: UUID="9afcc736-0a3b-4d92-b8e9-5a70e796156e" TYPE="ext4" PARTLABEL="root" PARTUUID="dd52a06d-046c-42f6-8f5d-82a0634fdddf"
/dev/sda5: UUID=30a48c54-5cd5-4607-a70d-a1b7ac761ce0 #### current UUID
/dev/sda6: LABEL="Restore" UUID="A2D6F120D6F0F57F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="41ef1919-1090-42bb-a613-a0e9da1a7339"
/dev/sda7: LABEL="UBUNTU" UUID="94dd2258-eb2a-4be5-a1f0-73e6084f366e" TYPE="ext4" PARTLABEL="ubuntu" PARTUUID="80955e57-b777-4ccc-a537-208c31c5fcbd"
/dev/sda8: LABEL="home" UUID="9f475ba3-5518-4eb0-9cb3-abe6d8e4a720" TYPE="ext4" PARTLABEL="home" PARTUUID="61ecb978-03ec-40fd-b27e-0117de8fcee9"
/dev/sda9: UUID="fdd875d2-cdc6-41b1-874b-c349a5ae39e5" TYPE="swap" PARTUUID="d5fbd2cf-a99b-4229-90eb-44d592f876e5"
/dev/sda10: UUID="0210e113-4325-4e84-b20f-64e269137a72" TYPE="swap" PARTLABEL="swap_deb" PARTUUID="11ff2495-12a7-4997-a6c1-fefe7b274b27"
/dev/sda11: LABEL="LM" UUID="0b825ea5-e617-4af0-8c48-fef0b0ab02b2" TYPE="ext4" PARTLABEL="LM" PARTUUID="e7f2365d-345a-45ed-90d4-16e19499d302"
/dev/sda12: UUID="fda8a178-7545-41b0-a1cf-52a623b2b382" TYPE="swap" PARTLABEL="swap_LM" PARTUUID="ea36963b-0865-46dd-b41e-e4f5e349ccee"
/dev/sda13: LABEL="F" UUID="c4948f75-ef28-4d1c-bd88-e5d7adc88977" TYPE="ext4" PARTUUID="bbfacbc2-c821-44ea-af54-977d29069045"
/dev/sda14: LABEL="E" UUID="1764901f-4c45-4a1d-b6ab-0abb973509c6" TYPE="ext4" PARTUUID="77f46295-9768-42fb-ae08-2f37cf2701a1"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="fb9e09ae-9edc-4d67-b49f-52726972c09a"

------

2. blkid from ubuntu
/dev/sda1: LABEL="SYSTEM" UUID="98C9-B5E4" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9d3228d5-f86e-491a-bdad-f7f6288bbba5"
/dev/sda2: LABEL="Recovery" UUID="7C12EB1512EAD366" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c3a08008-e49c-4a1b-8f61-26f1523ac02e"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="fb9e09ae-9edc-4d67-b49f-52726972c09a"
/dev/sda4: LABEL="OS" UUID="B4DCEE5ADCEE1700" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="42714427-cb04-42c7-899f-2c355d26e8c1"
####/dev/sda5: UUID="9afcc736-0a3b-4d92-b8e9-5a70e796156e" TYPE="ext4" PARTLABEL="root" PARTUUID="dd52a06d-046c-42f6-8f5d-82a0634fdddf"
/dev/sda5: UUID=30a48c54-5cd5-4607-a70d-a1b7ac761ce0 #### current UUID
/dev/sda6: LABEL="Restore" UUID="A2D6F120D6F0F57F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="41ef1919-1090-42bb-a613-a0e9da1a7339"
/dev/sda7: LABEL="UBUNTU" UUID="94dd2258-eb2a-4be5-a1f0-73e6084f366e" TYPE="ext4" PARTLABEL="ubuntu" PARTUUID="80955e57-b777-4ccc-a537-208c31c5fcbd"
/dev/sda8: LABEL="home" UUID="9f475ba3-5518-4eb0-9cb3-abe6d8e4a720" TYPE="ext4" PARTLABEL="home" PARTUUID="61ecb978-03ec-40fd-b27e-0117de8fcee9"
/dev/sda9: UUID="fdd875d2-cdc6-41b1-874b-c349a5ae39e5" TYPE="swap" PARTUUID="d5fbd2cf-a99b-4229-90eb-44d592f876e5"
/dev/sda10: UUID="0210e113-4325-4e84-b20f-64e269137a72" TYPE="swap" PARTLABEL="swap_deb" PARTUUID="11ff2495-12a7-4997-a6c1-fefe7b274b27"
/dev/sda11: LABEL="LM" UUID="0b825ea5-e617-4af0-8c48-fef0b0ab02b2" TYPE="ext4" PARTLABEL="LM" PARTUUID="e7f2365d-345a-45ed-90d4-16e19499d302"
/dev/sda12: UUID="fda8a178-7545-41b0-a1cf-52a623b2b382" TYPE="swap" PARTLABEL="swap_LM" PARTUUID="ea36963b-0865-46dd-b41e-e4f5e349ccee"
/dev/sda13: LABEL="F" UUID="c4948f75-ef28-4d1c-bd88-e5d7adc88977" TYPE="ext4" PARTUUID="bbfacbc2-c821-44ea-af54-977d29069045"
/dev/sda14: LABEL="E" UUID="1764901f-4c45-4a1d-b6ab-0abb973509c6" TYPE="ext4" PARTUUID="77f46295-9768-42fb-ae08-2f37cf2701a1"

-------
3. fstab from debian:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=9afcc736-0a3b-4d92-b8e9-5a70e796156e / ext4 errors=remount-ro 0 1 ### /dev/sda5: UUID=30a48c54-5cd5-4607-a70d-a1b7ac761ce0 #### current UUID
# /boot/efi was on /dev/sda1 during installation
UUID=98C9-B5E4 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda8 during installation
UUID=9f475ba3-5518-4eb0-9cb3-abe6d8e4a720 /home ext4 defaults 0 2
# swap was on /dev/sda10 during installation
UUID=0210e113-4325-4e84-b20f-64e269137a72 none swap sw 0 0
# swap was on /dev/sda12 during installation
UUID=fda8a178-7545-41b0-a1cf-52a623b2b382 none swap sw 0 0
# swap was on /dev/sda9 during installation
UUID=fdd875d2-cdc6-41b1-874b-c349a5ae39e5 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

---------
(4. I removed fstab as seen from ubuntu - seems irrelevant)
5. unfortunately I can't upload a copy of gparted view from ubuntu
Last edited by serandrzej on 2019-08-11 17:38, edited 2 times in total.
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby L_V » 2019-07-25 14:32

Not sure report from ubuntu is relevant.
You use 3 swap partitions for Debian.
Did you try to disable all of them to investigate iff any difference ? (comment the swap lines in fstab).
Did you install the correct firmware for your graphic ?
L_V
 
Posts: 1125
Joined: 2007-03-19 09:04

Re: no GUI after upgrade to buster

Postby Head_on_a_Stick » 2019-07-25 15:55

serandrzej wrote:I followed properly (as it seems) the upgrade procedure, I did format / root partition, but left /home untouched, just assigned new /home to old /home, while new / root partition was placed on old, formatted / root.

I don't understand, did you update your old system or install a new one?
Don't break DebianHow to report bugs

SharpBang GNU/Linux — a pre-configured Openbox/Tint2 desktop running on Debian stable
User avatar
Head_on_a_Stick
 
Posts: 10605
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: no GUI after upgrade to buster

Postby Dai_trying » 2019-07-25 17:54

Do you have intel graphics?
Dai_trying
 
Posts: 791
Joined: 2016-01-07 12:25

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 20:34

thank you all for addressing my topic this quickly, here are the answers:

L_V wrote:Not sure report from ubuntu is relevant.
You use 3 swap partitions for Debian.
Did you try to disable all of them to investigate iff any difference ? (comment the swap lines in fstab).
Did you install the correct firmware for your graphic ?


- 3 partitions because I just didn't specify swap partition for debian during upgrade, I thought it would not be a problem if I didn't assign swap
- I think graphic firmware is not the problem, I have been running debian on this asus netbook (x102b or sth like that) since jessie.

- still no GUI, nothing changed after I commented fstab like this:
# swap was on /dev/sda10 during installation
#UUID=0210e113-4325-4e84-b20f-64e269137a72 none swap sw 0 0
# swap was on /dev/sda12 during installation
#UUID=fda8a178-7545-41b0-a1cf-52a623b2b382 none swap sw 0 0
# swap was on /dev/sda9 during installation
#UUID=fdd875d2-cdc6-41b1-874b-c349a5ae39e5 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

maybe I should reinstall buster once again this time assigning one, specific swap during upgrade?
Last edited by serandrzej on 2019-07-25 21:15, edited 1 time in total.
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 20:38

Head_on_a_Stick wrote:
serandrzej wrote:I followed properly (as it seems) the upgrade procedure, I did format / root partition, but left /home untouched, just assigned new /home to old /home, while new / root partition was placed on old, formatted / root.

I don't understand, did you update your old system or install a new one?


thanks for response
I have upgraded from stretch to buster. stretch (and jessie before) worked fine (apart from minor glitches I got used to live with - I put them down to the simplicity of my netbook asus x102b or sth like this)
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 20:39

Dai_trying wrote:Do you have intel graphics?

thanks for your response
I didn't consider graphics as the source of problems as I ran on this netbook jessie and stretch prior to buster

as it turns out I don't have intell, having run "lspci -k | grep -A3 VGA" I gather I have AMD, radeon..
Last edited by serandrzej on 2019-07-25 21:28, edited 1 time in total.
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby L_V » 2019-07-25 20:49

Trying to disable the swaps is to be sure nothing strange is found at boot in these shared swaps (some recovery status for example).
For the graphics, you may be don't remember what you installed earlier.

Code: Select all
dpkg -l firmware* |grep ii
L_V
 
Posts: 1125
Joined: 2007-03-19 09:04

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 21:07

L_V wrote:Trying to disable the swaps is to be sure nothing strange is found at boot in these shared swaps (some recovery status for example).
For the graphics, you may be don't remember what you installed earlier.

Code: Select all
dpkg -l firmware* |grep ii


thank you, for advice.
I've just run the command, it returned this:
"ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel"
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby L_V » 2019-07-25 21:10

I don't know if you need this one: firmware-linux-nonfree , may be....

Code: Select all
lspci -k | grep -A3 VGA
L_V
 
Posts: 1125
Joined: 2007-03-19 09:04

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 21:24

L_V wrote:
Code: Select all
lspci -k | grep -A3 VGA

returns this:
"VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180]
Subsystem: ASUSTek Computer Inc. Kabini [Radeon HD 8180]
Kernel modules: radeon, amdgpu
Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio"

oh, I see I don't have intell..
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby L_V » 2019-07-25 21:27

Then install firmware-amd-graphics to see.
L_V
 
Posts: 1125
Joined: 2007-03-19 09:04

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 21:31

L_V wrote:Then install firmware-amd-graphics to see.


firmware-amd-graphics has no installation candidate but is referred by another package. should I add a new repository to sourceslist? which one?
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Re: no GUI after upgrade to buster

Postby L_V » 2019-07-25 21:39

firmware-amd-graphics is "non-free"
https://packages.debian.org/buster/firm ... d-graphics
You need to add non-free in your /etc/apt/sources.list / example:
deb http://ftp.de.debian.org/debian buster main non-free
L_V
 
Posts: 1125
Joined: 2007-03-19 09:04

Re: no GUI after upgrade to buster

Postby serandrzej » 2019-07-25 22:05

L_V wrote:firmware-amd-graphics is "non-free"


I did add this to sources.list:
deb http://ftp.de.debian.org/debian buster main non-free[/quote]
still, after 'apt install firmware-amd-graphics' the return is the same: .."E: Package firmware-amd-graphics is not available, but is referred (..) This may mean that the package is missing, has been obsolete, or is only available from another source"

but then, what is still intriguing me, is why linux mint GUI doesn't get up either, while ubuntu GUI does,
and why debian is booting into root partition instead of /home.

---------------
finally I got to install firmware-amd-graphics but still no change
Last edited by serandrzej on 2019-08-10 17:43, edited 4 times in total.
serandrzej
 
Posts: 31
Joined: 2015-03-10 10:00

Next

Return to Installation

Who is online

Users browsing this forum: wlnx and 7 guests

fashionable