Continuous Reboot, unable to reach gnome login screen

rraj

Member

Reaction score: 4
Messages: 77

Hi

Last saturday after pkg upgrade, upon reboot I encountered white screen error "Oh no! Something has gone wrong". So i decided to do single user login and upgraded FreeBSD from 11.3 to 11.4 successfully!

Now I face a different issue - multi user login does not reach gnome login screen, instead it reboots continuously.

I tried to reinstall gdm from single user login. Able to run startx (eterm/xterm) now. Upon installation completion i received a warning from gdm that do not schedule gdm to run at boot time in '/etc/ttys'. I have gdm_enable=YES in rc.conf! Not sure if gdm setting in /etc/ttys is there.

Where to look for error? What can i do now?

Thanks
Ravi
 

Elazar

Well-Known Member

Reaction score: 143
Messages: 363

Where to look for error?
Generally speaking, in log files. A wild guess from me would be /var/log/gdm, or /var/log/Xorg.0.log, or in dmesg.

Can you reach the multi user console?
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

Generally speaking, in log files. A wild guess from me would be /var/log/gdm, or /var/log/Xorg.0.log, or in dmesg.

Can you reach the multi user console?
Attaching logs greeter.log, Xorg.0.log. dmesg l grep error output is: module_register_init: MOD_LOAD (vesa, 0xffffffff80ff20a0, 0) error 19, this particular error existed from before.

Cannot reach multi user login!

when i try to run gdm on single user i get an error message: Couldn't connect to system bus: Could not connect: Connection refused
 

Attachments

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,332
Messages: 33,894

Now I face a different issue - multi user login does not reach gnome login screen, instead it reboots continuously.
Based on your other issues I suspect you are using graphics/drm-kmod? Remove the automatic boot to X/GDM and check if loading that kernel module is the cause of the reboot. Make sure the module is built for the exact version of FreeBSD you currently have (mismatched kernel modules can and will cause reboots).
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

Based on your other issues I suspect you are using graphics/drm-kmod? Remove the automatic boot to X/GDM and check if loading that kernel module is the cause of the reboot. Make sure the module is built for the exact version of FreeBSD you currently have (mismatched kernel modules can and will cause reboots).
Hi

pkg install of DRM-Kmod stops reboots. But I receive same screen as originally, attaching photo of that screen.

Where to look for error?
 

Attachments

NapoleonWils0n

Well-Known Member

Reaction score: 128
Messages: 272

Hi Mate

Do you have any gnome extensions installed

I had a similar issue with Gnome not starting and the problem was the Gnome workspace extension

Gnome extensions are stored in this location

Bash:
~/.local/share/gnome-shell/extensions
Have a look and see if you have any extensions installed in that directory and try moving them to the Desktop
and then see if you can log in
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

Hi Mate

Do you have any gnome extensions installed

I had a similar issue with Gnome not starting and the problem was the Gnome workspace extension

Gnome extensions are stored in this location

Bash:
~/.local/share/gnome-shell/extensions
Have a look and see if you have any extensions installed in that directory and try moving them to the Desktop
and then see if you can log in
Hi

There is no 'extensions' sub-directory under 'gnome-shell'!

I suspect there is some other issue, but don't know where to look for error?
 

bigemot

New Member


Messages: 1

Hi,
I have had the same issue with white screen at boot.
have a look in
Bash:
/usr/local/share/gnome-shell/extensions
I've had one manually installed extension
Bash:
dash-to-panel@jderose9.github.com
I have removed this directory and gnome is working well now.
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

Hi,
I have had the same issue with white screen at boot.
have a look in
Bash:
/usr/local/share/gnome-shell/extensions
I've had one manually installed extension
Bash:
dash-to-panel@jderose9.github.com
I have removed this directory and gnome is working well now.
Hi

As i mentioned in this thread before that there is no extensions sub-directory under gnome-shell!

See: https://termbin.com/b0k6.

Is it possible that this directory be hidden? If yes, how to access it? Please give the commands.
 

Phishfry

Son of Beastie

Reaction score: 2,011
Messages: 4,990

To fix this you need to disable the Display Manager and boot to FreeBSD command prompt. Just like SirDice said.
Remove the automatic boot to X/GDM and check if loading that kernel module is the cause of the reboot. Make sure the module is built for the exact version of FreeBSD you currently have (mismatched kernel modules can and will cause reboots).
Only then will you be able to debug this correctly.
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

To fix this you need to disable the Display Manager and boot to FreeBSD command prompt. Just like SirDice said.


Only then will you be able to debug this correctly.
Hi

Now there are no more reboots.

Still do you want me to remove gdm_enable=YES & gnome_enable=YES from rc.conf?
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

My philosophy is to get Xorg working from the command prompt first then invoke a Display Manager if you must.
Disabled gdm & gnome in rc.conf!

Running startx goes in white screen says: system can't recover, please log out and try again. Tried reinstalling xorg, but of no avail.

See no errors in Xorg.0.log: https://termbin.com/vjqv.
 

Attachments

Abraham79

Member

Reaction score: 6
Messages: 62

Disabled gdm & gnome in rc.conf!

Running startx goes in white screen says: system can't recover, please log out and try again. Tried reinstalling xorg, but of no avail.

See no errors in Xorg.0.log: https://termbin.com/vjqv.
You may try: tail -f /var/log/messages in one virtual console and launch startx in another pseudo console (CTRL+ALT+F1/F2 etc). Then, looking at messages output may give some hints on what is happening.
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

You may try: tail -f /var/log/messages in one virtual console and launch startx in another pseudo console (CTRL+ALT+F1/F2 etc). Then, looking at messages output may give some hints on what is happening.
Hi

Ran tail -f /var/log/messages in one console. Unable to launch another console using CTRL+ALT+F1/F2 etc.

attached startx output
 

Attachments

Sevendogsbsd

Aspiring Daemon

Reaction score: 531
Messages: 982

Why are you launching Gnome, or even X for that matter, as root? Have you tried this as a normal user? Also, are your video drivers loaded for whatever video card you have? Gnome requires 3D acceleration to run.
 
OP
R

rraj

Member

Reaction score: 4
Messages: 77

Why are you launching Gnome, or even X for that matter, as root? Have you tried this as a normal user? Also, are your video drivers loaded for whatever video card you have? Gnome requires 3D acceleration to run.
Hi
Startx output has changed, attaching photo. It’s same for normal user. Regarding video drivers, same as originally must be loaded.
 

Attachments

Top