ports/132426: Unable to start X server after ports upgrade

Stephane Legrand stephleg at free.fr
Sun Mar 8 18:00:14 UTC 2009


>Number:         132426
>Category:       ports
>Synopsis:       Unable to start X server after ports upgrade
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 08 18:00:13 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Stephane Legrand
>Release:        -STABLE
>Organization:
>Environment:
i386 - FreeBSD -stable
>Description:
Hello,

After doing a global portupgrade, i'm now more able to start the X server. Here is some lines of the Xorg log file : 

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.1-STABLE i386 
Current Operating System: FreeBSD sequoia.mondomaineamoi.megalo 7.1-STABLE FreeBSD 7.1-STABLE #20: Sat Jan 10 15:24:24 CET 2009     stephane at sequoia.mondomaineamoi.megalo:/usr/obj/usr/src/sys/SEQUOIA i386
Build Date: 08 March 2009  05:41:09PM
..
(II) Loading /usr/local/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
	compiled for 1.5.3, module version = 0.1.0
	ABI class: X.Org Video Driver, version 4.1
(==) intel(0): Depth 24, (==) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945G
(--) intel(0): Chipset: "945G"
(EE) intel(0): No valid FB address in PCI config space
(II) UnloadModule: "intel"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/local/lib/xorg/modules//libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found



Note that the X server worked perfectly well before the portupgrade with the same config file.

>How-To-Repeat:
Try to start the X server. Unfortunately, it's hard for me to narrow which port can be guilty as the portupgrade has upgraded several ports in the same session.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list