- Code: Select all
apt update
apt install firmware-amd-graphics
And report this
- Code: Select all
apt policy firmware-amd-graphics
grep ^d /etc/apt/sources.list
apt update
apt install firmware-amd-graphics
apt policy firmware-amd-graphics
grep ^d /etc/apt/sources.list
serandrzej wrote:Head_on_a_Stick wrote: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.
serandrzej wrote:why debian is booting into root partition instead of /home
Head_on_a_Stick wrote:Did you run the Debian buster installer and use it to install a new system?
adduser test
grep home /etc/fstab
blkid | grep home
mount | grep home
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...
- Code: Select all
apt update
apt install firmware-amd-graphics
And report this
- Code: Select all
apt policy firmware-amd-graphics
grep ^d /etc/apt/sources.list
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
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
ls /etc/apt/sources.list
cat /etc/apt/sources.list
L_V wrote:Just after boot, if you log in root session, and execute sddm: what happen ?
serandrzej wrote: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)
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.
ls /home
mount [or] cat /etc/mtab
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.
djk44883 wrote:"boot into" / "instead of"?? so you can get to a command line andis empty?
- Code: Select all
ls /home
djk44883 wrote:Executeto see what is mounted and where
- Code: Select all
mount [or] cat /etc/mtab
Users browsing this forum: No registered users and 9 guests