Re: X.org 6.9 - Greek Keyboard Layout - FreeBSD 6.0
Giorgos Kapetanakis wrote: > On Tue, January 31, 2006 12:01 am, Laganakos Vassilis wrote: > >> Hello, >> >> I use two layouts on X, English and Greek. I use the following lines in >> xorg.conf to switch between those two: >> >> Option "XkbRules" "xorg" >> Option "XkbModel" "acpi" >> Option "XkbLayout" "us,el" >> Option "XkbOptions" grp:alt_shift_toggle,grp_led:scroll,altwin:menu" >> >> This worked just fine until I port-upgraded to X.org 6.9 last week. >> It was compiled and installed correctly. Whe I tried to start X I >> noticed that I couldn't switch to the Greek layout, and I could not >> switch to to console with the Alt-Ctrl-F? key combination. When I exited >> the >> X mode, I saw the following message: >> >> The XKEYBOARD keymap compiler (xkbcomp) reports: >> > Error:Can't find file "pc/el" for symbols include >> > Exiting >> > Abandoning symbols file "basic" >> > Abandoning symbols file "default" >> Errors from xkbcomp are not fatal to the X server >> >> >> So I was forced to comment out the last two of those lines in xorg.conf >> and use only English. Greek are can be displayed in any program or Web >> page, >> but I cannot type in greek. >> >> Thanx, >> >> Vassilis >> >> > > It's not FreeBSD's issue, it's X.org's. The greek sybols file is no longer > "el", but "gr". > Just type: > > # cd /usr/X11R6/lib/X11/xkb/symbols/pc > # ln -s gr el > > and everything should work fine ;) > > I had the same problem and "ln -s gr el" solved it. However, I looked at pc/gr and it seems it includes the pc/el file (which is now linked to pc/gr). There must be some configuration problem somewhere. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: X.org 6.9
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 WildeOrg 01737505-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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9 - Greek Keyboard Layout - FreeBSD 6.0
On Tue, January 31, 2006 12:01 am, Laganakos Vassilis wrote: > Hello, > > I use two layouts on X, English and Greek. I use the following lines in > xorg.conf to switch between those two: > > Option "XkbRules" "xorg" > Option "XkbModel" "acpi" > Option "XkbLayout" "us,el" > Option "XkbOptions" grp:alt_shift_toggle,grp_led:scroll,altwin:menu" > > This worked just fine until I port-upgraded to X.org 6.9 last week. > It was compiled and installed correctly. Whe I tried to start X I > noticed that I couldn't switch to the Greek layout, and I could not > switch to to console with the Alt-Ctrl-F? key combination. When I exited > the > X mode, I saw the following message: > > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Error:Can't find file "pc/el" for symbols include > > Exiting > > Abandoning symbols file "basic" > > Abandoning symbols file "default" > Errors from xkbcomp are not fatal to the X server > > > So I was forced to comment out the last two of those lines in xorg.conf > and use only English. Greek are can be displayed in any program or Web > page, > but I cannot type in greek. > > Thanx, > > Vassilis > > -- > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > It's not FreeBSD's issue, it's X.org's. The greek sybols file is no longer "el", but "gr". Just type: # cd /usr/X11R6/lib/X11/xkb/symbols/pc # ln -s gr el and everything should work fine ;) -- Giorgos Kapetanakis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: X.org 6.9
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 WildeOrg 01737505-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:[EMAIL PROTECTED] 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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9
On Tue, Jan 31, 2006 at 09:01:09AM +1100, Mark Andrews wrote: > > Well you can atleast get dri to compile. It doesn't compile on > FreeBSD 4.11 wants -std=c99 and . No pr sent in yet. > > None of the xservers compiled. Header files in the wrong order > and it wanted va_copy(). Moving to gcc33 and a few patches > addressed the issue. Pr sent > > I know one can't test build all the ports on FreeBSD 4.11 before > committing but one would think that X11 was critical enough to > too many people not to test build it on FreeBSD 4.11 before > committing the changes to ports. The default X server on FreeBSD 4.11 is XFree86 4.5, so that's what gets tested. Of course, x.org 6.9 *was* tested on modern versions of FreeBSD prior to the commit :-) Kris pgpfdtSrFzNQn.pgp Description: PGP signature
Re: X.org 6.9
Well you can atleast get dri to compile. It doesn't compile on FreeBSD 4.11 wants -std=c99 and . No pr sent in yet. None of the xservers compiled. Header files in the wrong order and it wanted va_copy(). Moving to gcc33 and a few patches addressed the issue. Pr sent I know one can't test build all the ports on FreeBSD 4.11 before committing but one would think that X11 was critical enough to too many people not to test build it on FreeBSD 4.11 before committing the changes to ports. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
X.org 6.9 - Greek Keyboard Layout - FreeBSD 6.0
Hello, I use two layouts on X, English and Greek. I use the following lines in xorg.conf to switch between those two: Option "XkbRules" "xorg" Option "XkbModel" "acpi" Option "XkbLayout" "us,el" Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll,altwin:menu" This worked just fine until I port-upgraded to X.org 6.9 last week. It was compiled and installed correctly. Whe I tried to start X I noticed that I couldn't switch to the Greek layout, and I could not switch to to console with the Alt-Ctrl-F? key combination. When I exited the X mode, I saw the following message: The XKEYBOARD keymap compiler (xkbcomp) reports: > Error:Can't find file "pc/el" for symbols include > Exiting > Abandoning symbols file "basic" > Abandoning symbols file "default" Errors from xkbcomp are not fatal to the X server So I was forced to comment out the last two of those lines in xorg.conf and use only English. Greek are can be displayed in any program or Web page, but I cannot type in greek. When I searched out the web for any clues, I found the following: http://archives.neohapsis.com/archives/linux/mandrake/2006-q1/0018.html http://rpmfind.net/linux/RPM/mandriva/devel/cooker/ppc/media/main/xorg-x11-100dpi-fonts-6.9.0-8mdk.ppc.html which state that there was an issue with Greek keyboard, but it should be corrected with the 6.9.0 final. Any ideas why's that happening in FreeBSD 6.0 Stable or how could I repair it? Thanx, Vassilis -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: X.org 6.9
Hi, Kamikaze - Mine only has the following, twice for two heads. MonitorLayout was already commented out. Section "Device" Option "BusType" "PCIE" # []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 WildeOrg 01737505-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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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 WildeOrg 01737505-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 "[EMAIL PROTECTED]" >> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: X.org 6.9
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 2006 225,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::01:00.0 < drmOpenDevice: node name is /dev/dri/card0 < drmOpenDevice: open result is 6, (OK) < drmOpenByBusid: drmOpenMinor returns 6 < drmOpenByBusid: drmGetBusid reports pci::01:00.0 < (II) RADEON(0): [drm] DRM interface version 1.2 < (II) RADEON(0): [drm] created "radeon" driver at busid "pci::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 = 0xd000 < (II) RADEON(0): [drm] added 1 reserved context for kernel < (II) RADEON(0): [pci] 8192 kB allocated with handle 0x < (II) RADEON(0): [pci] ring handle = 0xc72b3000 < (II) RADEON(0): [pci] Ring mapped at 0x30881000 < (II) RADEON(0): [pci] Ring contents 0x < (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 0x < (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 0x < (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 = 0xdfde < (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 0x180 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 disabled 868a812,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 (0xa,0x1) was already clear > FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. -- Don WildeOrg 01737505-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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9
On Mon, 30 Jan 2006 11:28:03 -0700 "Wilde, Donald" <[EMAIL PROTECTED]> 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 WildeOrg 01737505-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 "[EMAIL PROTECTED]" >> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > signature.asc Description: OpenPGP digital signature
RE: X.org 6.9
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 WildeOrg 01737505-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:[EMAIL PROTECTED] 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 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 WildeOrg 01737505-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 "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 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 WildeOrg 01737505-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 "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9
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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
X.org 6.9
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 WildeOrg 01737505-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 "[EMAIL PROTECTED]"
Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
I did get X.org running on 6-STABLE. As you have mentioned, starting X via "X -probeonly" with an Asus SLI motherboard and an NVidia 7800 GTX video card fails multiply; the internal configuration tries and fails to load module "fbdev", meanwhile, the probe of the card dials the contrast of the syscons consoles down to near-zero levels. However, running "Xorg -configure" succeeds where the other fails. All modules are loaded, an x.conf file is written and the contrast is not blown. On my system, the monitor is able to support the highest resolution specified in the configuration file, though the text is unreadably small. Therefore, modulo tuning of the acceptable modes, X is now working on this configuration. Thanks for all your help! Mike O'Brien ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
> Date: Thu, 26 Jan 2006 13:35:55 -0800 > From: Mike O'Brien <[EMAIL PROTECTED]> > > Kevin Oberman wrote: > > >>From: [EMAIL PROTECTED] (Mike O'Brien) > >>Date: Thu, 26 Jan 2006 07:44:43 -0800 > >>Sender: [EMAIL PROTECTED] > >>If I run X -probeonly, > >>I get a message that "module fbdev cannot be found". > >> > >I installed nvidia-driver and nvidia-xconfig. It worked > >immediately. nvidia-xconfig modifies the existing xorg.conf (or > >XF85Config) to work with the nvidia driver. > > > > > Do I need to worry about "module 'fbdev' not found"? > That doesn't sound good and makes me wonder if X.org > might be misconfigured out of the box. fbdev is not used. You should not have it listed in the "Modules" section. Several other modules are gone as their functionality has been rolled into the base system. I suspect fbdev is such a obsolete. If in doubt, use Xorg -configure and let nvidia-xconfig put in the nVidia specific config into the output. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
Kevin Oberman wrote: From: [EMAIL PROTECTED] (Mike O'Brien) Date: Thu, 26 Jan 2006 07:44:43 -0800 Sender: [EMAIL PROTECTED] If I run X -probeonly, I get a message that "module fbdev cannot be found". I installed nvidia-driver and nvidia-xconfig. It worked immediately. nvidia-xconfig modifies the existing xorg.conf (or XF85Config) to work with the nvidia driver. Do I need to worry about "module 'fbdev' not found"? That doesn't sound good and makes me wonder if X.org might be misconfigured out of the box. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
> From: [EMAIL PROTECTED] (Mike O'Brien) > Date: Thu, 26 Jan 2006 07:44:43 -0800 > Sender: [EMAIL PROTECTED] > > I sent this to "freebsd-x11" and didn't hear a peep back, > so I'm widening the net. > > I'm running FreeBSD 6-STABLE, cvsupped as of last night. I upgraded > the ports collection to X.org 6.9 at the same time. Under the X > that ships with 6-RELEASE, in the ISO image, and under X.org 6.9, > the symptoms are the same. > > The hardware is an Athlon 4400+ CPU on an Asus motherboard and an > NVIDIA 7800 GTX video card. > > I'm not running the NVidia FreeBSD driver (yet), preferring to see > the VESA work first before stirring the pot. If I run X -probeonly, > I get a message that "module fbdev cannot be found". This message > is, however, almost unreadable because the probing of the video > card causes the console contrast to drop almost to zero. The room > has to be almost pitch-black before the remaining dim text can be > read. I have to reboot the machine to make the console brightness > and contrast normal again. I have the same chipset and CPU on an MSI mobo and had exactly the same problem. Right down to the very low contrast video. I think VESA is broken with this chipset. I installed nvidia-driver and nvidia-xconfig. It worked immediately. nvidia-xconfig modifies the existing xorg.conf (or XF85Config) to work with the nvidia driver. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
Mike O'Brien wrote: I sent this to "freebsd-x11" and didn't hear a peep back, so I'm widening the net. I'm running FreeBSD 6-STABLE, cvsupped as of last night. I upgraded the ports collection to X.org 6.9 at the same time. Under the X that ships with 6-RELEASE, in the ISO image, and under X.org 6.9, the symptoms are the same. The hardware is an Athlon 4400+ CPU on an Asus motherboard and an NVIDIA 7800 GTX video card. I'm not running the NVidia FreeBSD driver (yet), preferring to see the VESA work first before stirring the pot. If I run X -probeonly, I get a message that "module fbdev cannot be found". This message is, however, almost unreadable because the probing of the video card causes the console contrast to drop almost to zero. The room has to be almost pitch-black before the remaining dim text can be read. I have to reboot the machine to make the console brightness and contrast normal again. Any takers on either of these problems? Mike O'Brien It might be worth trying the nvidia drivers even if VESA isn't working. My personal experience with the very recent FreeBSD nvidia drivers is that they are awesome. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
I sent this to "freebsd-x11" and didn't hear a peep back, so I'm widening the net. I'm running FreeBSD 6-STABLE, cvsupped as of last night. I upgraded the ports collection to X.org 6.9 at the same time. Under the X that ships with 6-RELEASE, in the ISO image, and under X.org 6.9, the symptoms are the same. The hardware is an Athlon 4400+ CPU on an Asus motherboard and an NVIDIA 7800 GTX video card. I'm not running the NVidia FreeBSD driver (yet), preferring to see the VESA work first before stirring the pot. If I run X -probeonly, I get a message that "module fbdev cannot be found". This message is, however, almost unreadable because the probing of the video card causes the console contrast to drop almost to zero. The room has to be almost pitch-black before the remaining dim text can be read. I have to reboot the machine to make the console brightness and contrast normal again. Any takers on either of these problems? Mike O'Brien --- End of Forwarded Message ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
