New motherboard - X does not start

C

callado

I have replaced my motherboard with an ASUS P5QPL-AM and I have only the integrated G41 express chipset X4500 video.
The previous one with GMA 3000 worked fine with X.
In FreeBSD 8.0 X crashes immediately to CLI, with the error message in Xorg.0.log that agpgart is not available. I included 'load_agp="YES"' in /boot/loader.conf, although my previous intel chip worked without this. But X still crashes with the same error message and I don't see /dev/agp*.
I have no xorg.conf, I have enabled hal and dbus in /etc/rc.conf.
I have also PCBSD 7.1.1 (based on FreeBSD 7.2) and X crashes the same way.
Under linux X works without problem.
 
Ok, there was 'agp_load="YES"' in /boot/loader.conf, I mistyped it.
I use GENERIC.
Anyway, if I enter 'kldload agp', I get 'kldload: can't load agp: File exists'
Now both PCBSD and FreeBSD work only with 'vesa' driver.
 
% Xorg -configure could help you guess your new driver.
When swapping motherboards/graphic cards chances are that the previous /etc/X11/xorg.conf will NOT work out of the box for the new hardware.
 
achix said:
% Xorg -configure could help you guess your new driver.
When swapping motherboards/graphic cards chances are that the previous /etc/X11/xorg.conf will NOT work out of the box for the new hardware.
Click to expand...
I had no xorg.conf at all, it is no longer required if hal is running. I also tried 'Xorg -configure' and copying '/root/xorg.conf.new' to '/etc/X11/xorg.conf', but it did not help. I need the same driver ('intel') as before. Now I use the xorg.conf to start X with 'vesa'.
 
callado said:
I had no xorg.conf at all, it is no longer required if hal is running. I also tried 'Xorg -configure' and copying '/root/xorg.conf.new' to '/etc/X11/xorg.conf', but it did not help. I need the same driver ('intel') as before. Now I use the xorg.conf to start X with 'vesa'.
Click to expand...

oops, i didn't know that, i just tried it today for the first time.
Thanx for pointing this out.
However, i still i read a lot of graphics "hardcore" stuff, referring to xorg.conf.
 
Your Xorg log file shows that it's running as DISPLAY :1... Is there another X server already running on that machine as :0?

Adam
 
adamk said:
Your Xorg log file shows that it's running as DISPLAY :1... Is there another X server already running on that machine as :0?

Adam
Click to expand...
No. In which line do you see that?
 
Code: 
(==) Log file: "/var/log/Xorg.1.log",

The log files are numbered based on their DISPLAY. So something is causing X to start as DISPLAY :1, which is very odd. It maybe completely unrelated to this crash, but that's certainly something to look into. What's the output of 'ps ax'? Does /var/log/Xorg.0.log exist?

Adam
 
adamk said:
Code: 
(==) Log file: "/var/log/Xorg.1.log",
Adam
Click to expand...
I think that it only means that it is a backup of a previous X log. Xorg.0.log is the latest, the previous one is moved to Xorg.0.log.old, the ones before that are moved to Xorg.1.log, Xorg.1.log.old, Xorg.2.log, Xorg.2.log.old, etc. In order to launch X, I needed the 'vesa' driver, so I provided an earlier log.
 
That is not correct. The number in the log file specifies the the display. Xorg.0.log is the most recent log for display :0. Xorg.0.log.old is the next most recent. It does not keep older versions around.

EDIT: You can confirm this by looking at the -logfile option in the Xorg man page.

Adam
 
It is not required to load agp.ko module in /boot/loader.conf if you use GENERIC.

It may be quite useful to show here your /etc/X11/xorg.conf as it is at yours.
Eventually somebody who has same chip may post his/her working xorg.conf and then you just make "diff" :)
 
what happens if you
# kldload /boot/kernel/i915.ko
by hand?
is your xf86-video-intel package up to date?

also, as zeiz said, its a good idea to put aside hal and dbus for a while, try to use xorg.conf till you have your first xterm appearing, and then you go back to hal, step by step.
 
achix said:
is your xf86-video-intel package up to date?
Click to expand...
Yes, I have xf86-video-intel-2.7.1

My xorg.conf (X works with this one with 'vesa'):
Code: 
Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/local/lib/xorg/modules"
	FontPath     "/usr/local/lib/X11/fonts/misc/"
	FontPath     "/usr/local/lib/X11/fonts/TTF/"
	FontPath     "/usr/local/lib/X11/fonts/OTF"
	FontPath     "/usr/local/lib/X11/fonts/Type1/"
	FontPath     "/usr/local/lib/X11/fonts/100dpi/"
	FontPath     "/usr/local/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
	Load  "dbe"
	Load  "ddc"
	Load  "dri"
	Load  "dri2"
	Load  "extmod"
	Load  "glx"
	Load  "record"
	Load  "xtrap"
	Load  "freetype"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/sysmouse"
	Option	    "Buttons" "6"
	Option	    "ZAxisMapping" "4 5"
	Option      "Emulate3Buttons"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	Vendorname	"LGE"
	Modelname	"LG FLATRON W2042S"
	Horizsync	30.0-80.0	
	Vertrefresh	59.9-60.0
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# [<bool>]
        #Option     "SWcursor"           	# [<bool>]
        #Option     "ColorKey"           	# <i>
        #Option     "CacheLines"         	# <i>
        #Option     "Dac6Bit"            	# [<bool>]
        #Option     "DRI"                	# [<bool>]
        #Option     "NoDDC"              	# [<bool>]
        #Option     "ShowCache"          	# [<bool>]
        #Option     "XvMCSurfaces"       	# <i>
        #Option     "PageFlip"           	# [<bool>]
	Identifier  "Card0"
	Driver      "vesa"
#	VendorName  "Intel Corporation"
#	BoardName   "4 Series Chipset Integrated Graphics Controller"
#	BusID       "PCI:0:2:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth	24
	SubSection "Display"
		Depth	24
		Modes "1280x1024"
	EndSubSection
EndSection
 
your Xorg.0.log posted in the PR, complains about not being abled to load i915 kernel module:
Code: 
[drm] failed to load kernel module "i915"
did you try the kldload above?
 
Specification for your monitor is (some important):
Screen Resolution 1680x1050
Horizontal Frequency Bandwidth (H-Sync Rate) 30-83 Hz
Vertical Frequency Bandwidth (V-Sync Rate) 56-75 MHz
So sections "Monitor" and "Screen" (Subsection "Display") should rather look like this:

Code: 
Section "Monitor"
	Identifier   "Monitor0"
	VendorName	"LGE"
	ModelName	"LG FLATRON W2042S"
	HorizSync	30.0-83.0	
	VertRefresh	56.0-75.0
        Option            "DPMS"
EndSection

Code: 
Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth	24
     SubSection "Display"
                Viewport 0 0
		Depth	24
		Modes "1680x1050_60"
     EndSubSection
EndSection

This already can help, try first with "vesa" then change to intel, lets see if we need more workaround :)

PS. Forgot to highlight: probably it was just a typo but anyway capital letters must be in place:
Code: 
Vendor[B]N[/B]ame	
Model[B]N[/B]ame	
Horiz[B]S[/B]ync	
Vert[B]R[/B]efresh
 
callado said:
It loads. But if I start X after that with 'intel', it still crashes.
Click to expand...

We usually say "crash" to denote a kernel panic/crash.
Anyway, after loading i915.ko, is your Xorg log still the same?
What does it complain about now?
 
I'm wondering if it's possible that the FreeBSD agpgart driver doesn't support your particular chipset. It would be odd, but not impossible. What's the full output of 'pciconf -vl'?
 
You must log in or register to reply here.
Back
Top