Just checking we covered all base's first....Sounds like it going/gone bad.
Type: Posts; User: 1fallen; Keyword(s):
Just checking we covered all base's first....Sounds like it going/gone bad.
make sure you haven't enabled Microsoft proprietary features in Windows like dynamic disks or whatever as they may prevent the drive form being used for other OSes.
Was it seen during the install?
If the OP is talking about 24.04LTS then this might need a look: https://ubuntuforums.org/showthread.php?t=2496736
56 ^^^^What B-om said :P
Just to add to dragonfly41's suggestion on rEFInd, it's worthwhile to install it.
Grub is always the boot-loader and rEFInd is a boot-manager.
No not really, but do you recall using any of the two I list below?
vlock: (it is in the repos of most distros),
Virtual Console locking program
vlock either locks the current...
Ok I get what is happening here, I was incomplete on my instruction's
To terminate the tty2 session you have to go to a tty3 session first.
(Ctrl Alt F3)
Now we can try again to get rid of that...
Something is a foul, Please Note the difference with mine and yours.
Mine from Morning Boot, my sessions are as follows:
└─> tty
/dev/pts/0
┌───────────────────>
│~
└─> ps -H -t /dev/tty2 ...
paste back the return for:
gnome-session --debug
was you prompted for a password? If yes use Key Combo (Ctrl Alt F2) now and then another combo of (Alt F7)
last
me tty7 :0 Thu May 16 12:27 still logged in
reboot...
Ok try now the second command.
To stop that tty2 try this:
First show us this:
ps -H -t /dev/tty2
Lets look at that reply first before going to my below suggestion.
systemctl stop getty@tty2.service
Yes it dose, see my screenshot with a Note.
And my file reads like:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 550.78
Section...
Might I give a good suggestion here; write that file .conf to "/etc/X11/xorg.conf.d/" as this example name "20-nvidia-xorg.conf"
Less chance of it getting overwrote.
You may want to add yourself to a current bug: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2028377
Yep I did some digging last nite as well came up with what you found.
I must say I'm surprised the ASUS MB even connects to it, hence all the kernel panics.
That board is a bit old I wonder how...