Code: Select all
apt update
apt install firmware-amd-graphics
Code: Select all
apt policy firmware-amd-graphics
grep ^d /etc/apt/sources.list
Code: Select all
apt update
apt install firmware-amd-graphics
Code: Select all
apt policy firmware-amd-graphics
grep ^d /etc/apt/sources.list
That doesn't answer my question at allserandrzej wrote:thanks for responseHead_on_a_Stick wrote:I don't understand, did you update your old system or install a new one?
I have upgraded from stretch to buster.
What does this mean? Do you mean that you can't see /home in Debian? Use the findmnt command to view your mountpoints.serandrzej wrote:why debian is booting into root partition instead of /home
(sorry for late answer, did not realized 2nd page) At first I upgraded via apt update dist upgrade etc. then when I couldn't make system work I installed it several times from CD.Head_on_a_Stick wrote: Did you run the Debian buster installer and use it to install a new system?
Code: Select all
adduser test
Code: Select all
grep home /etc/fstab
blkid | grep home
mount | grep home
I can see /home partition, even in graphic mode but only from ubuntu.Head_on_a_Stick wrote:Do you mean that you can't see /home in Debian? Use the findmnt command to view your mountpoints.
L_V wrote:did you update befeore installing...And report thisCode: Select all
apt update apt install firmware-amd-graphics
Code: Select all
apt policy firmware-amd-graphics grep ^d /etc/apt/sources.list
I added a test user and logged on as the new user (in text mode)L_V wrote:Can you try to add a test user, and log in test session.
Then, problem.serandrzej wrote:grep ^d /etc/apt/sources.list - just hangs and nothing happens
Code: Select all
ls /etc/apt/sources.list
cat /etc/apt/sources.list
probably I will eventually resort to that, although would prefer not to, but actually trying to solve the issue in a proper way is quite gripping and educating and maybe will contribute to some corrections. so for now let's to try and try to possibly get rid of errors:)Deb-fan wrote:fresh install, including /home.
can config files on /home partition mess up with booting?Deb-fan wrote:The config files left behind in an unformatted /home could potentially cause conflicts/problems.
L_V wrote:Then, problem.Code: Select all
ls /etc/apt/sources.list cat /etc/apt/sources.list
Code: Select all
ls /etc/apt/sources.list
Code: Select all
cat /etc/apt/sources.list
sddm - command not found so I replaced it with lightdm and then upcame something like this:L_V wrote:Just after boot, if you log in root session, and execute sddm: what happen ?
If you did an upgrade and not a new installation... why "I did format"???serandrzej wrote:thanks for responseHead_on_a_Stick wrote:I don't understand, did you update your old system or install a new one?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 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)
"boot into" / "instead of"?? so you can get to a command line andNow 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.
Code: Select all
ls /home
Code: Select all
mount [or] cat /etc/mtab
at first I did regular upgrade (I followed the whole procedure update, dist upgrade, change source.list update.. etc - I probably followed every step and in the right order, on my other laptop it worked but there are only 2 systems and no separate /, /home)djk44883 wrote:If you did an upgrade and not a new installation... why "I did format"???
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.
I expected the system to boot into /home partition via GUI, and not /. and yes, command line is the only interface now and ls /home returns some files, moreover, all the files in from stretch /home partition are in place, and I can access them, and from ubuntu also in graphical mode.djk44883 wrote:"boot into" / "instead of"?? so you can get to a command line andis empty?Code: Select all
ls /home
cat /etc/mtab returns this:djk44883 wrote:Executeto see what is mounted and whereCode: Select all
mount [or] cat /etc/mtab
oh my! You might have considered asking for assistance... before you, uhm, well here you are now.serandrzej wrote:at first I did regular upgrade (I followed the whole procedure update, dist upgrade, change source.list update.. etc - I probably followed every step and in the right order, on my other laptop it worked but there are only 2 systems and no separate /, /home)djk44883 wrote:If you did an upgrade and not a new installation... why "I did format"???
but it failed, no GUI, so I installed buster from CD on top of lame buster which was already there. this ofcourse did not produce expected result, then I installed from CD several times, to no avail, no GUI.
Code: Select all
tmpfs /run/user/0 tmpfs rw,nosuid,nodev,relatime,size=346460k,mode=700 0 0
yes, but I did consulted the net, and thought that I followed properly all prescribed procedure.djk44883 wrote:oh my! You might have considered asking for assistance... before you, uhm, well here you are now.
just tried starx. and what struck me is that it says "operating system Linux 4.9.0-8.."djk44883 wrote:/etc/mtab does show /home is mounted. When your system does boot "into /" Do you have any messages? Have you tried startx ?
I can do anything only on root password, my account not on sudoers list.djk44883 wrote:No busybox? Not in maintenance mode? Not using root password?
boot menu is always debian's. except when I ran update-grub from ubuntu. after another reistall of buster it's again debian's.djk44883 wrote:One more thing, if you re-installed, then the boot menu comes from the debian installation now? or has it always?
Maybe your installation isn't so messed up as your booting wrong. That UUID doesn't match any that you posed in your first blkid... so yea, that seems messed up.just tried starx. and what struck me is that it says "operating system Linux 4.9.0-8.."
while uname -a returns 4.19.0-5
also "KERNEL command line: BOOT_IMAGE_=(..) root=UUID=30a48c54-5cd5-4607-a70d-a1b7ac761ce0 ro quiet"
something feels wrong with the UUID.
then it reports also several errors:
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server erro
correction, UUID=30a48c54-5cd5-4607-a70d-a1b7ac761ce0 is now assigned to dev/sda5 - root.djk44883 wrote: root=UUID=30a48c54-5cd5-4607-a70d-a1b7ac761ce0 ro quiet"
That UUID doesn't match any that you posed in your first blkid... so yea, that seems messed up.
I can't upload dmesg file, and pasting the result wouldn't make sense. what I'm getting on booting and also found in dmesg is that (30 or so same lines) :djk44883 wrote:
/etc/mtab does show /home is mounted. When your system does boot "into /" Do you have any messages? Have you tried startx ?