GDM3 issues after update/reboot

Archived topics about LMDE 1 and LMDE 2
Locked
arvind

GDM3 issues after update/reboot

Post by arvind »

Hi people,

I've been using Linux Mint for quite a while and recently tried LMDE. Last week I had updated the system using the Mint update manager. Everything seemed to be fine until I rebooted today (I only reboot once in a while). When starting up, the kernel didn't recognize the ext3 drivers anymore so I switched my partitions and fstab to use ext4. The other problem is GDM3 won't start. All I get is an enless loop/flickering of the console screen but no GDM3 pops up. I have to press the power button to restart the computer.
I restarted in recovery mode and moved /etc/init.d/gdm3 to /etc/init.d/gdm3_ and rebooted the computer normally. I get my login prompt and I can log in normall. All my partitions have been mounted properly etc but when i do a "/etc/init.d/gmd3 start" I get the same flickering loop over again.

I checked the /var/log/gdm3 folder but nothing interesting is there. I'm not sure what to check next, would be cool if someone can give me some hints as to what to look for for troubleshooting gdm3 startup issues. Thanks a lot!

-Arv

EDIT:

I just found this in my Xorg.0.log file after doing a manual startx from the command line:

Code: Select all

(II) Module fbdev: vendor="X.Org Foundation"
	compiled for 1.7.6.901, module version = 0.4.2
	ABI class: X.Org Video Driver, version 6.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
	Sandybridge, Sandybridge
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 00@00:02:0
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 0.0.2
	ABI class: X.Org Video Driver, version 6.0
(EE) open /dev/fb0: No such file or directory
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
Seems I don't have a framebuffer (/dev/fb0) ?
I never messed with X much before so I'm stumped here...
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
blueyed

Re: GDM3 issues after update/reboot

Post by blueyed »

Could you solve this?

I've just run into this myself when trying the Debian Edition on a Samsung Series 9 notebook (900X3A).
(I could not pick any updates because neither WLAN nor the mini-LAN could be made to work.)
User avatar
Roken
Level 5
Level 5
Posts: 738
Joined: Fri Nov 19, 2010 4:55 pm
Location: Newport, S Wales

Re: GDM3 issues after update/reboot

Post by Roken »

Do you have an /etc/X11/xorg.conf file? If so, rename it to /etc/X11/xorg.conf.bak and reboot. Hopefully that will get you back to a desktop.
Kernel Linux Tex 5.12.14-zen1-1-zen, XFCE
Arch
Dual GTX1070 8Gb
AMD Ryzen 1800X
32Gb RAM
theophrastus

Re: GDM3 issues after update/reboot

Post by theophrastus »

I fought the gdm3 flashing screen dragon (linux Mint Xfce) for two days. at last i won. here are my insights/mumblings.

I apparently had downloaded and activated the nvidia proprietary drivers (i have a geforce gt 440); i now believe that this was prime mistake.

after fighting all manner of "apt-get install --reinstall..." "dpkg-reconfigure [gdm3|xserver-xorg]" i noticed "lsmod | grep nvidia" had a fat module sitting there. so i did a:

Code: Select all

   dpkg -r $(dpkg -l | perl -ane 'if(/nvidia/){print "$F[1] "}')
followed by a:

Code: Select all

   rmmod nvidia
and following a cold reboot. (why don't warm reboots apparently reload the latest kernels anymore?) all was well ...for me.

good luck out there.
and thank you thank you linux Mint folks! you've been a great happy harbor away from the Ubuntu unity madness.
Locked

Return to “LMDE Archive”