Strange thing at Kernel 2170_FC5smp bootup

Hitboxx · 05-04-2006, 02:57 AM

Hi guys,

Recently i updated my kernel to 2.6.16-1.2170_FC5smp and its nvidia drivers. During bootup, after it checks for the 'udev' etc entries, it shows some msg like background readahead and goes into 'naked X mode'(like the screen goes blank and a 'X' for the mouse pointer is displayed at the center). I've to hit Ctrl+Alt+Backspace to quit that screen and the booting resumes normally and im on the desktop.

Is it coz i added a few resolution entries in xorg.conf ??
Here is it

Code:

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
	ModulePath   "/usr/lib/xorg/modules/extensions/nvidia"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "unix/:7100"
EndSection

Section "Module"
	Load  "dbe"
	Load  "extmod"
	Load  "fbdevhw"
	Load  "record"
	Load  "freetype"
	Load  "type1"
	Load  "glx"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#	Option	"Xleds"		"1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#	Option	"XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#	Option	"XkbModel"	"pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#	Option	"XkbModel"	"microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#	Option	"XkbLayout"	"de"
# or:
#	Option	"XkbLayout"	"de"
#	Option	"XkbVariant"	"nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#	Option	"XkbOptions"	"ctrl:swapcaps"
# Or if you just want both to be control, use:
#	Option	"XkbOptions"	"ctrl:nocaps"
#
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "yes"
EndSection

Section "Monitor"

 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Samsung SyncMaster 997DF/927DF/997MB/927MB/927DFI/927MBI"
	DisplaySize  350	260
 ### Comment all HorizSync and VertSync values to use DDC:
	HorizSync    30.0 - 96.0
	VertRefresh  50.0 - 160.0
	Option	    "dpms"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "nvidia"
	VendorName  "Videocard vendor"
	BoardName   "nVidia Corporation NV36 [GeForce FX 5700LE]"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "1024x768" "800x600"
	EndSubSection
EndSection

Section "DRI"
	Group        0
	Mode         0666
EndSection

I added "1024x768" into 16 depth and "1024x768" "800x600" into 24 depth sections.

Code:

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "1024x768" "800x600"
	EndSubSection
EndSection

I don't think this is the problem. Can it be a hardware problem? My specs are in my signature.

Anybody had such issues??

Thanks

Togni · 05-04-2006, 03:22 AM

The same thing is happening to me, on my desktop and on my laptop, two totally different machines and i never modified xorg.conf .
Strange.....looks like a bug or something new.

dubya · 05-04-2006, 09:22 AM

For the record I have the same problem. My xorg.conf is modified to make use of dual monitors. If I change the default runlevel from 5 to 3, then simply use startx once I've logged in, everything works fine. I did leave the computer on overnight when it appeared to be locked with a blank screen and the x cursor and by morning I did have the login screen; not sure how long that took though ( < 8 hours). Also, I'm not running the smp kernel, just the normal, default one.

I wouldn't be surprised if there was a new kernel available in the next day or two.

roskoo · 05-04-2006, 10:54 AM

same issue, so I needed to downgrade from the last kernel

dubya · 05-04-2006, 11:04 AM

Always a good idea to boot into the new kernel and test it out before removing the old.

Hitboxx · 05-05-2006, 12:07 AM

Guys,

Just a thought crossed my mind. Until now we were thinking it might be some kinda bug or error or something similar. What if for some testing/development purpose, it has been deliberately put in there. Let me explain, we normally hit Ctrl+Alt+Bkspc to exit that 'naked X' screen, in other words KILL IT. But upon normal 'killing' of any program in linux gives out error/debugging messages. But rather here, you get a very satisfactory 'Background Readahead [OK]' message right after exiting the screen. Not sure but i feel these 2 are connected. Maybe this is some sort of initialization process albeit in initial stages of development (requiring us 2 'kill it' lol).

Like i said -- Just a thought

dubya · 05-05-2006, 08:52 AM

If I understand you correctly, then that could be very probable; new features are introduced all the time that don't get as smoothly as developers would have liked them to.

Master of Reality · 05-05-2006, 05:15 PM

I would think turning off the splashscreen would also fix this? (not that I know how to do that)

spooon · 05-06-2006, 12:03 AM

2107 was very broken. Remove it if you have it installed. It was already removed from Fedora updates a few days ago. Now 2111 is out that should fix the problems.

Togni · 05-06-2006, 01:43 AM

I have installed kernel 2111 but it's even worse, it simply hangs and if i try to use 2107 i get a login screen and i have to manually do a "startx".

noxious · 05-06-2006, 03:49 PM

2111 works great. 2107 wouldn't boot. Good work!

Hitboxx · 05-07-2006, 11:36 PM

Quote:

Originally Posted by noxious

2111 works great. 2107 wouldn't boot. Good work!

AMEN!! (i aint a christian though

)

All the problems of 2107 has vanished, 2111 rocks!!