Friday, I updated to latest 6-stable and did portupgrade --all successfully, however, I did not restart the system and X until this morning. The system boots to login properly, but will not startx to KDE. It locks up completely, cannot even ssh in from outside. Seeing the note in /usr/ports/UPDATING about Display Postscript, I cvsupped again and rebuilt world, ran portupgrade again, and cleaned x11/kde3 and did make && make install on it. No tasty enchiladas yet. I just tried running startx without startkde in .xinitrc, but still no luck. The X log file (/var/log/Xorg.0.log) never gets written. I am about to make clean for all X.org libraries and reinstall. What else should I be doing? -- Don Wilde Org 01737 505-844-1126 Man does not live by words alone, despite the fact that sometimes he has to eat them. - Adlai E. Stevenson Jr.
On 30 Jan 2006, at 18:28, Wilde, Donald wrote:> Friday, I updated to latest 6-stable and did portupgrade --all > successfully, however, I did not restart the system and X until this > morning. The system boots to login properly, but will not startx to > KDE. > It locks up completely, cannot even ssh in from outside. Seeing the > note > in /usr/ports/UPDATING about Display Postscript, I cvsupped again and > rebuilt world, ran portupgrade again, and cleaned x11/kde3 and did > make > && make install on it. No tasty enchiladas yet. I just tried running > startx without startkde in .xinitrc, but still no luck. The X log file > (/var/log/Xorg.0.log) never gets written. I am about to make clean for > all X.org libraries and reinstall. > > What else should I be doing?I used portmanager and just let it rebuild everything that links to X. Everything's working perfectly for me. Andy.
Hello, On Mon, 30 Jan 2006, Wilde, Donald wrote:> Friday, I updated to latest 6-stable and did portupgrade --all > successfully, however, I did not restart the system and X until this > morning. The system boots to login properly, but will not startx to KDE. > It locks up completely, cannot even ssh in from outside. Seeing the note > in /usr/ports/UPDATING about Display Postscript, I cvsupped again and > rebuilt world, ran portupgrade again, and cleaned x11/kde3 and did make > && make install on it. No tasty enchiladas yet. I just tried running > startx without startkde in .xinitrc, but still no luck. The X log file > (/var/log/Xorg.0.log) never gets written. I am about to make clean for > all X.org libraries and reinstall. > > What else should I be doing?For me on my IBM T43, updating to Xorg-6.9 broke X as well. After some time spent hunting around for answers, I found a thread that suggested that Xorg-6.9 broke DRI (certainly for the graphics card on the T43). Disabling DRI in xorg.conf then enabled me to use startx successfully thereafter., Might be worth a shot for you too. Regards, Stacey> > -- > Don Wilde Org 01737 505-844-1126 > Man does not live by words alone, despite the fact that sometimes he has > to eat them. - Adlai E. Stevenson Jr. > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Yes, Stacey, that worked for me, too. For the record, neither portupgrade or portmanager did the trick. What worked was editing /etc/X11/xorg.conf to comment out the line in Section "Module" that says 'Load "dri"', like so: Section "Module" ... # Load "dri" ... EndSection Thank you for your assistance, Stacey! :D -- Don Wilde Org 01737 505-844-1126 If you don't find it in the index, look very carefully through the entire catalogue. - Sears, Roebuck, and Co. Consumer's Guide, 1897 -----Original Message----- From: Stacey Roberts [mailto:stacey@vickiandstacey.com] Sent: Monday, January 30, 2006 11:50 AM To: Wilde, Donald Cc: freebsd-stable@freebsd.org Subject: Re: X.org 6.9 Hello, On Mon, 30 Jan 2006, Wilde, Donald wrote:> Friday, I updated to latest 6-stable and did portupgrade --all > successfully, however, I did not restart the system and X until this > morning. The system boots to login properly, but will not startx toKDE.> It locks up completely, cannot even ssh in from outside. Seeing the > note in /usr/ports/UPDATING about Display Postscript, I cvsupped again> and rebuilt world, ran portupgrade again, and cleaned x11/kde3 and did> make && make install on it. No tasty enchiladas yet. I just tried > running startx without startkde in .xinitrc, but still no luck. The X > log file > (/var/log/Xorg.0.log) never gets written. I am about to make clean for> all X.org libraries and reinstall. > > What else should I be doing?For me on my IBM T43, updating to Xorg-6.9 broke X as well. After some time spent hunting around for answers, I found a thread that suggested that Xorg-6.9 broke DRI (certainly for the graphics card on the T43). Disabling DRI in xorg.conf then enabled me to use startx successfully thereafter., Might be worth a shot for you too. Regards, Stacey> > -- > Don Wilde Org 01737 505-844-1126 > Man does not live by words alone, despite the fact that sometimes he > has to eat them. - Adlai E. Stevenson Jr. > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to"freebsd-stable-unsubscribe@freebsd.org">
On Mon, 30 Jan 2006 11:28:03 -0700 "Wilde, Donald" <dwilde@sandia.gov> wrote:> Friday, I updated to latest 6-stable and did portupgrade --all > successfully, however, I did not restart the system and X until this > morning. The system boots to login properly, but will not startx to > KDE. It locks up completely, cannot even ssh in from outside. > What else should I be doing?I portupgraded -rRa (all) ports and all was well. Except the fact that KDE (my wife's account uses it) did not start up. Fvwm (my own manager) did though. What I did was a *one time start* of kde from my root account. This one did start! I logged off again as root, started X as my wife an now kde started up OK. Don't know why, but hey, it works ;-) -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.0 ++ The Power to Serve
I am finding out more. There are a number of pointers that suggest that DRI (Direct Rendering) in 6.9 includes the 3D by default, but it is broken on the Radeon X300 cards, especially the PCIe variant (see r300.sourceforge.net). That site also says that the development is now in the X.org tree, however, It Ain't There Yet. At the bottom of this message is the diff between enabling (<) and disabling (>) Load "dri" in xorg.conf. The DRI and DRM segments appear to load and test correctly, producing this logfile, but the lockup is so complete the machine will not even listen to its On/Off button, which normally initiates 'shutdown -h now', so restart includes pulling the plug and running fsck -p in single-user mode. :-(. Before the portupgrade/portmanager run it wouldn't even get to write the logfile, so that set of procedures was of some use. 14c14 < (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 30 12:49:28 2006 ---> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 30 12:16:52 2006225,236d224 < (II) LoadModule: "dri" < (II) Loading /usr/X11R6/lib/modules/extensions/libdri.so < (II) Module dri: vendor="X.Org Foundation" < compiled for 6.9.0, module version = 1.0.0 < ABI class: X.Org Server Extension, version 0.2 < (II) Loading sub module "drm" < (II) LoadModule: "drm" < (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.so < (II) Module drm: vendor="X.Org Foundation" < compiled for 6.9.0, module version = 1.0.0 < ABI class: X.Org Server Extension, version 0.2 < (II) Loading extension XFree86-DRI 751,779d738 < drmOpenDevice: node name is /dev/dri/card0 < drmOpenDevice: open result is 6, (OK) < drmOpenDevice: node name is /dev/dri/card0 < drmOpenDevice: open result is 6, (OK) < drmOpenByBusid: Searching for BusID pci:0000:01:00.0 < drmOpenDevice: node name is /dev/dri/card0 < drmOpenDevice: open result is 6, (OK) < drmOpenByBusid: drmOpenMinor returns 6 < drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 < (II) RADEON(0): [drm] DRM interface version 1.2 < (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0" < (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc7208000 < (II) RADEON(0): [drm] mapped SAREA 0xc7208000 to 0x28791000 < (II) RADEON(0): [drm] framebuffer handle = 0xd0000000 < (II) RADEON(0): [drm] added 1 reserved context for kernel < (II) RADEON(0): [pci] 8192 kB allocated with handle 0x00000000 < (II) RADEON(0): [pci] ring handle = 0xc72b3000 < (II) RADEON(0): [pci] Ring mapped at 0x30881000 < (II) RADEON(0): [pci] Ring contents 0x00000000 < (II) RADEON(0): [pci] ring read ptr handle = 0xc73b4000 < (II) RADEON(0): [pci] Ring read ptr mapped at 0x28793000 < (II) RADEON(0): [pci] Ring read ptr contents 0x00000000 < (II) RADEON(0): [pci] vertex/indirect buffers handle = 0xc73b5000 < (II) RADEON(0): [pci] Vertex/indirect buffers mapped at 0x30982000 < (II) RADEON(0): [pci] Vertex/indirect buffers contents 0x00000000 < (II) RADEON(0): [pci] GART texture map handle = 0xc75b5000 < (II) RADEON(0): [pci] GART Texture map mapped at 0x30b82000 < (II) RADEON(0): [drm] register handle = 0xdfde0000 < (II) RADEON(0): [dri] Visual configs initialized 781,785d739 < (II) RADEON(0): CP in BM mode < (II) RADEON(0): Using 8 MB GART aperture < (II) RADEON(0): Using 1 MB for the ring buffer < (II) RADEON(0): Using 2 MB for vertex/indirect buffers < (II) RADEON(0): Using 5 MB for GART textures 789,792d742 < (II) RADEON(0): Will use back buffer at offset 0x10ac000 < (II) RADEON(0): Will use depth buffer at offset 0x1456000 < (II) RADEON(0): Will use 32 kb for PCI GART table at offset 0x7ff8000 < (II) RADEON(0): Will use 106496 kb for textures at offset 0x1800000 820,827c770 < (II) RADEON(0): X context handle = 0x1 < (II) RADEON(0): [drm] installed DRM signal handler < (II) RADEON(0): [DRI] installation complete < (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers < (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers < (II) RADEON(0): [drm] dma control initialized, using IRQ 16 < (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 < (II) RADEON(0): Direct rendering enabled ---> (WW) RADEON(0): Direct rendering disabled868a812,822> SetClientVersion: 0 9 > SetGrabKeysState - disabled > SetGrabKeysState - enabled > SetClientVersion: 0 9 > SetGrabKeysState - disabled > SetGrabKeysState - enabled > SetClientVersion: 0 9 > SetGrabKeysState - disabled > SetGrabKeysState - enabled > (==) RADEON(0): Write-combining range (0xa0000,0x10000) was alreadyclear> FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2,should be 1; fixing. -- Don Wilde Org 01737 505-844-1126 If you don't find it in the index, look very carefully through the entire catalogue. - Sears, Roebuck, and Co. Consumer's Guide, 1897
Hi, Kamikaze -
Mine only has the following, twice for two heads. MonitorLayout was
already commented out.
Section "Device"
Option "BusType" "PCIE" #
[<str>]4
Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RADEON X300"
BusID "PCI:1:0:0"
EndSection
I followed all your other suggestions, and they speeded up the
non-accelerated startup quite a bit, but it still crashes _hard_ with
DRI enabled.
--
Don Wilde Org 01737 505-844-1126
If you don't find it in the index, look very carefully through the
entire catalogue. - Sears, Roebuck, and Co. Consumer's Guide, 1897
-----Original Message-----
From: owner-freebsd-stable@freebsd.org
[mailto:owner-freebsd-stable@freebsd.org] On Behalf Of [LoN]Kamikaze
Sent: Monday, January 30, 2006 12:52 PM
To: freebsd-stable@freebsd.org
Subject: Re: X.org 6.9
My X also didn't start after the update. I got it fixed though.
The trouble seems to be related to improved monitor detection that
conflicts with manual settings.
To get my X work again I removed all entries in the section Monitor
except for Identifier:
Section "Monitor"
Identifier "LCD"
EndSection
I also removed the MonitorLayout from my Device section, this was
actually causing the problem I think, even though the entry was correct
it seemed to cause problems with the auto detection of xorg. It now
looks like this:
Section "Device"
Identifier "ATI Radeon 7500 Mobile"
Driver "radeon"
Option "BusType" "AGP"
Option "AGPMode" "4"
Option "AGPFastWrite" "true"
Option "GartSize" "64"
Option "EnablePageFlip" "true"
Option "DDCMode" "true"
EndSection
I also cleaned up my Screen section, because X is now well capable of
detecting the supported resolutions without me interfering:
Section "Screen"
Identifier "Screen 1"
Device "ATI Radeon 7500 Mobile"
Monitor "LCD"
DefaultDepth 24
EndSection
BTW, DRI is not broken for me and after the update glxgears performs
with 37% more fps. I also noticed a performance boost in Quake 3 Arena.
Stacey Roberts wrote:> Hello,
>
> On Mon, 30 Jan 2006, Wilde, Donald wrote:
>
>> Friday, I updated to latest 6-stable and did portupgrade --all
>> successfully, however, I did not restart the system and X until this
>> morning. The system boots to login properly, but will not startx to
KDE.>> It locks up completely, cannot even ssh in from outside. Seeing the
>> note in /usr/ports/UPDATING about Display Postscript, I cvsupped
>> again and rebuilt world, ran portupgrade again, and cleaned x11/kde3
>> and did make && make install on it. No tasty enchiladas yet. I
just
>> tried running startx without startkde in .xinitrc, but still no luck.
>> The X log file
>> (/var/log/Xorg.0.log) never gets written. I am about to make clean
>> for all X.org libraries and reinstall.
>>
>> What else should I be doing?
>
> For me on my IBM T43, updating to Xorg-6.9 broke X as well. After some
> time spent hunting around for answers, I found a thread that suggested
that Xorg-6.9 broke DRI (certainly for the graphics card on the
T43).>
> Disabling DRI in xorg.conf then enabled me to use startx successfully
> thereafter., Might be worth a shot for you too.
>
> Regards,
>
> Stacey
>
>> --
>> Don Wilde Org 01737 505-844-1126
>> Man does not live by words alone, despite the fact that sometimes he
>> has to eat them. - Adlai E. Stevenson Jr.
>>
>>
>>
>>
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org">>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org">
>
On the contrary, your suggestions are very helpful, Kamikaze. It still crashed when I erased everything, but I'll try successively adding bits and pieces. It never did have that 'Mode 0666' line, so I'll see if there's a combo that does work. I've never had to really tinker with the X conf file, so this is a "learning experience". :D -- Don Wilde Org 01737 505-844-1126 Why do people in ship mutinies always ask for "better treatment?" I'd ask for a pinball machine, because with all that rocking back and forth you'd probably be able to get a lot of free games. - Jack Handy -----Original Message----- From: [LoN]Kamikaze [mailto:LoN_Kamikaze@gmx.de] Sent: Monday, January 30, 2006 4:42 PM To: Wilde, Donald Subject: Re: X.org 6.9 I'm sorry that my mail doesn't seem to help anyone.
Reading X.org's bugzilla, it appears that my X 6.9 lockup is fairly Radeon X300-specific and (fortunately!) in active development. Therefore, I'll keep my bits off FreeBSD-STABLE for now. Thanks, all, for the suggestions! :D -- Don Wilde Org 01737 505-844-1126 Why do people in ship mutinies always ask for "better treatment?" I'd ask for a pinball machine, because with all that rocking back and forth you'd probably be able to get a lot of free games. - Jack Handy