From miwi at FreeBSD.org Sun Jun 1 16:53:49 2008 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Sun Jun 1 16:53:52 2008 Subject: ports/118539: x11-drivers/xf86-video-ati - Bitmap fonts corrupted in xorg under load (radeon driver) Message-ID: <200806011653.m51Grmbe075186@freefall.freebsd.org> Synopsis: x11-drivers/xf86-video-ati - Bitmap fonts corrupted in xorg under load (radeon driver) State-Changed-From-To: feedback->closed State-Changed-By: miwi State-Changed-When: Sun Jun 1 16:53:48 UTC 2008 State-Changed-Why: Submitter have no longer the hardware, so can we close this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=118539 From miwi at FreeBSD.org Sun Jun 1 16:59:12 2008 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Sun Jun 1 16:59:14 2008 Subject: ports/118778: X11 I810 x11-drivers/xf86-video-i810 1.7.4 fatal server error Message-ID: <200806011659.m51GxBqc075373@freefall.freebsd.org> Synopsis: X11 I810 x11-drivers/xf86-video-i810 1.7.4 fatal server error State-Changed-From-To: feedback->closed State-Changed-By: miwi State-Changed-When: Sun Jun 1 16:59:11 UTC 2008 State-Changed-Why: Submitter problem is solved with switch to xf86-video-intel. Thanks for your report. http://www.freebsd.org/cgi/query-pr.cgi?pr=118778 From miwi at FreeBSD.org Sun Jun 1 17:03:08 2008 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Sun Jun 1 17:03:10 2008 Subject: ports/116412: x11/xorg - Screen artifacts with radeon X driver Message-ID: <200806011703.m51H385r075654@freefall.freebsd.org> Synopsis: x11/xorg - Screen artifacts with radeon X driver State-Changed-From-To: feedback->closed State-Changed-By: miwi State-Changed-When: Sun Jun 1 17:03:07 UTC 2008 State-Changed-Why: Feedback timeout about 2 months. If this problem still exists, please feel free to follow-up this PR so that we can re-open it and find a solution for the problem. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=116412 From miwi at FreeBSD.org Sun Jun 1 17:04:54 2008 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Sun Jun 1 17:04:56 2008 Subject: ports/112895: [dri] xorg-7.2 dri with radeon 7500 Message-ID: <200806011704.m51H4sT0075754@freefall.freebsd.org> Synopsis: [dri] xorg-7.2 dri with radeon 7500 State-Changed-From-To: open->closed State-Changed-By: miwi State-Changed-When: Sun Jun 1 17:04:54 UTC 2008 State-Changed-Why: Feedback timeout about 1 year. If this problem still exists, please feel free to follow-up this PR so that we can re-open it and find a solution for the problem. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=112895 From rcgill at vistaclinical.com Sun Jun 1 19:02:17 2008 From: rcgill at vistaclinical.com (Rawld Gill) Date: Sun Jun 1 19:02:23 2008 Subject: can't get 2560x1600 (freebsd 7.0, nv, 8500gt, hp lp3065) Message-ID: I am unable to get X to display 2560x1600. The best I can get is 1280x800. I've constructed a xorg.conf file with the proper modelines (I think), but this doesn't help. Here's the configuration: Mainboard: Gigabyte GA-M51GM-S2G Processor: AMD Athlon 64 X2 3800+ @ 2000 MHz RAM: 4096 MB Video Card: MSI NX8500GT-TD512EH (http://www.msicomputer.com/product/p_spec.asp?model=NX8500GT-TD512EH&class= vga) Monitor: HP LP3065 (http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/382087-382087-64283-72270-444 767-3297215.html) OS: FreeBSD 7.0 amd64 (NOT i386) Note that I am using the nv driver because the NVIDIA Proprietary Driver doesn't support amd64. The OS had been freshly installed from the ISO images. I updated the nv driver from ports (xf86-video-nv). Both the driver distributed with the iso install and the updated driver exhibit the same behavior. This card and monitor clearly should work OK since I have the exact same configuration (MB + CPU + RAM + video card + monitor) on another box running win xp perfectly. I've attached the relevant files below (xorg.conf, the xorg log, and output from xrandr -q after x is up). Thanks so much for any help. Best, Rawld Here is the xorg.conf file (note that I tried a couple of modelines in the monitor section). Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/local/share/X11/rgb" 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 "GLcore" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "record" Load "xtrap" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "HP" ModelName "LP3065" DisplaySize 641 400 HorizSync 100.0 VertRefresh 60.0 #ModeLine "2560x1600" 268.0 2560 2608 2640 2720 1600 1603 1609 1646 Modeline "2560x1600" 268.00 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "SWcursor" # [] #Option "HWcursor" # [] #Option "NoAccel" # [] #Option "ShadowFB" # [] #Option "UseFBDev" # [] #Option "Rotate" # [] #Option "VideoKey" # #Option "FlatPanel" # [] #Option "FPDither" # [] #Option "CrtcNumber" # #Option "FPScale" # [] #Option "FPTweak" # #Option "DualHead" # [] Identifier "Card0" Driver "nv" VendorName "nVidia Corporation" BoardName "GeForce 8500 GT" BusID "PCI:2:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" Subsection "Display" Viewport 0 0 Modes "2560x1600" Depth 24 EndSubSection EndSection Here is the xorg log file: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-RELEASE amd64 Current Operating System: FreeBSD rcg.wanda.vista-info-tech.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 13 February 2008 01:44:21PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 1 10:53:51 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Automatically adding devices (==) Automatically enabling devices (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/ X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dp i/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (**) RgbPath set to "/usr/local/share/X11/rgb" (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 10de,02f5 card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:00:1: chip 10de,02fa card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:00:2: chip 10de,02fe card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:00:3: chip 10de,02f8 card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:00:4: chip 10de,02f9 card 1458,5000 rev a2 class 05,00,00 hdr 00 (II) PCI: 00:00:5: chip 10de,02ff card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:00:6: chip 10de,027f card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:00:7: chip 10de,027e card 1458,5000 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:04:0: chip 10de,02fb card 0000,0000 rev a1 class 06,04,00 hdr 01 (II) PCI: 00:09:0: chip 10de,0270 card 1458,5001 rev a2 class 05,00,00 hdr 00 (II) PCI: 00:0a:0: chip 10de,0260 card 1458,5001 rev a3 class 06,01,00 hdr 80 (II) PCI: 00:0a:1: chip 10de,0264 card 1458,0264 rev a3 class 0c,05,00 hdr 80 (II) PCI: 00:0a:2: chip 10de,0272 card 1458,0264 rev a3 class 05,00,00 hdr 80 (II) PCI: 00:0b:0: chip 10de,026d card 1458,5004 rev a3 class 0c,03,10 hdr 80 (II) PCI: 00:0b:1: chip 10de,026e card 1458,5004 rev a3 class 0c,03,20 hdr 80 (II) PCI: 00:0d:0: chip 10de,0265 card 1458,b000 rev a1 class 01,01,8a hdr 00 (II) PCI: 00:0e:0: chip 10de,0266 card 1458,b003 rev a1 class 01,04,85 hdr 00 (II) PCI: 00:0f:0: chip 10de,0267 card 1458,b002 rev a1 class 01,04,85 hdr 00 (II) PCI: 00:10:0: chip 10de,026f card 0000,0000 rev a2 class 06,04,01 hdr 81 (II) PCI: 00:10:1: chip 10de,026c card 1458,a002 rev a2 class 04,03,00 hdr 80 (II) PCI: 00:14:0: chip 10de,0269 card 1458,e000 rev a3 class 06,80,00 hdr 00 (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 01:0e:0: chip 104c,8024 card 1458,1000 rev 00 class 0c,00,10 hdr 00 (II) PCI: 02:00:0: chip 10de,0421 card 1462,0960 rev a1 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:4:0), (0,2,2), BCTRL: 0x000c (VGA_EN is set) (II) Bus 2 I/O range: [0] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B] [1] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B] [2] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B] [3] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xf2000000 - 0xf5ffffff (0x4000000) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:10:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:16:0), (0,1,1), BCTRL: 0x0204 (VGA_EN is cleared) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xf6000000 - 0xf60fffff (0x100000) MX[B] (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:24:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] (--) PCI:*(2:0:0) nVidia Corporation GeForce 8500 GT rev 161, Mem @ 0xf4000000/24, 0xe0000000/28, 0xf2000000/25, I/O @ 0xa000/7 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xf6000000 - 0xf7ffffff (0x2000000) MX[B]E [1] -1 0 0xf6004000 - 0xf6007fff (0x4000) MX[B]E [2] -1 0 0xf6107000 - 0xf6107fff (0x1000) MX[B]E [3] -1 0 0xf6100000 - 0xf61fffff (0x100000) MX[B]E [4] -1 0 0xf6108000 - 0xf610ffff (0x8000) MX[B]E [5] -1 0 0xf6104000 - 0xf6107fff (0x4000) MX[B]E [6] -1 0 0xf6106000 - 0xf6107fff (0x2000) MX[B]E [7] -1 0 0xf6105000 - 0xf6105fff (0x1000) MX[B]E [8] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B](B) [9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [10] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B) [11] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [12] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]E [13] -1 0 0x00000b60 - 0x00000b7f (0x20) IX[B]E [14] -1 0 0x00000960 - 0x0000097f (0x20) IX[B]E [15] -1 0 0x00000be0 - 0x00000bff (0x20) IX[B]E [16] -1 0 0x000009e0 - 0x000009ff (0x20) IX[B]E [17] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [18] -1 0 0x00000b70 - 0x00000b7f (0x10) IX[B]E [19] -1 0 0x00000970 - 0x0000097f (0x10) IX[B]E [20] -1 0 0x00000bf0 - 0x00000bff (0x10) IX[B]E [21] -1 0 0x000009f0 - 0x000009ff (0x10) IX[B]E [22] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]E [23] -1 0 0x00001c80 - 0x00001cff (0x80) IX[B]E [24] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [25] -1 0 0x0000a000 - 0x0000a07f (0x80) IX[B](B) (II) PCI Memory resource overlap reduced 0xf6000000 from 0xf7ffffff to 0xf6003fff (II) PCI Memory resource overlap reduced 0xf6100000 from 0xf61fffff to 0xf6103fff (II) PCI I/O resource overlap reduced 0x00000b60 from 0x00000b7f to 0x00000b6f (II) PCI I/O resource overlap reduced 0x00000960 from 0x0000097f to 0x0000096f (II) PCI I/O resource overlap reduced 0x00000be0 from 0x00000bff to 0x00000bef (II) PCI I/O resource overlap reduced 0x000009e0 from 0x000009ff to 0x000009ef (II) PCI Memory resource overlap reduced 0xf6104000 from 0xf6107fff to 0xf6104fff (II) PCI Memory resource overlap reduced 0xf6106000 from 0xf6107fff to 0xf6106fff (II) PCI I/O resource overlap reduced 0x00001c00 from 0x00001cff to 0x00001c7f (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xf6000000 - 0xf6003fff (0x4000) MX[B]E [1] -1 0 0xf6004000 - 0xf6007fff (0x4000) MX[B]E [2] -1 0 0xf6107000 - 0xf6107fff (0x1000) MX[B]E [3] -1 0 0xf6100000 - 0xf6103fff (0x4000) MX[B]E [4] -1 0 0xf6108000 - 0xf610ffff (0x8000) MX[B]E [5] -1 0 0xf6104000 - 0xf6104fff (0x1000) MX[B]E [6] -1 0 0xf6106000 - 0xf6106fff (0x1000) MX[B]E [7] -1 0 0xf6105000 - 0xf6105fff (0x1000) MX[B]E [8] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B](B) [9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [10] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B) [11] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [12] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]E [13] -1 0 0x00000b60 - 0x00000b6f (0x10) IX[B]E [14] -1 0 0x00000960 - 0x0000096f (0x10) IX[B]E [15] -1 0 0x00000be0 - 0x00000bef (0x10) IX[B]E [16] -1 0 0x000009e0 - 0x000009ef (0x10) IX[B]E [17] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [18] -1 0 0x00000b70 - 0x00000b7f (0x10) IX[B]E [19] -1 0 0x00000970 - 0x0000097f (0x10) IX[B]E [20] -1 0 0x00000bf0 - 0x00000bff (0x10) IX[B]E [21] -1 0 0x000009f0 - 0x000009ff (0x10) IX[B]E [22] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]E [23] -1 0 0x00001c80 - 0x00001cff (0x80) IX[B]E [24] -1 0 0x00001c00 - 0x00001c7f (0x80) IX[B]E [25] -1 0 0x0000a000 - 0x0000a07f (0x80) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) All system resource ranges: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf6000000 - 0xf6003fff (0x4000) MX[B]E [5] -1 0 0xf6004000 - 0xf6007fff (0x4000) MX[B]E [6] -1 0 0xf6107000 - 0xf6107fff (0x1000) MX[B]E [7] -1 0 0xf6100000 - 0xf6103fff (0x4000) MX[B]E [8] -1 0 0xf6108000 - 0xf610ffff (0x8000) MX[B]E [9] -1 0 0xf6104000 - 0xf6104fff (0x1000) MX[B]E [10] -1 0 0xf6106000 - 0xf6106fff (0x1000) MX[B]E [11] -1 0 0xf6105000 - 0xf6105fff (0x1000) MX[B]E [12] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B](B) [13] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [14] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B) [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [17] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [18] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]E [19] -1 0 0x00000b60 - 0x00000b6f (0x10) IX[B]E [20] -1 0 0x00000960 - 0x0000096f (0x10) IX[B]E [21] -1 0 0x00000be0 - 0x00000bef (0x10) IX[B]E [22] -1 0 0x000009e0 - 0x000009ef (0x10) IX[B]E [23] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [24] -1 0 0x00000b70 - 0x00000b7f (0x10) IX[B]E [25] -1 0 0x00000970 - 0x0000097f (0x10) IX[B]E [26] -1 0 0x00000bf0 - 0x00000bff (0x10) IX[B]E [27] -1 0 0x000009f0 - 0x000009ff (0x10) IX[B]E [28] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]E [29] -1 0 0x00001c80 - 0x00001cff (0x80) IX[B]E [30] -1 0 0x00001c00 - 0x00001c7f (0x80) IX[B]E [31] -1 0 0x0000a000 - 0x0000a07f (0x80) IX[B](B) (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "freetype" will be loaded. This was enabled by default and also specified in the config file. (II) "type1" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading extension XFree86-DRI (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (==) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension RECORD (II) LoadModule: "xtrap" (II) Loading /usr/local/lib/xorg/modules/extensions//libxtrap.so (II) Module xtrap: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DEC-XTRAP (II) LoadModule: "freetype" (II) Loading /usr/local/lib/xorg/modules/fonts//libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 1.4.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font FreeType (II) LoadModule: "type1" (II) Loading /usr/local/lib/xorg/modules/fonts//libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Type1 (II) LoadModule: "nv" (II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so (II) Module nv: vendor="X.Org Foundation" compiled for 1.4.0, module version = 2.1.8 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 2.0 (II) LoadModule: "mouse" (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.2.3 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.0 (II) LoadModule: "kbd" (II) Loading /usr/local/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.2.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.0 (II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2, Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64, Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400, GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go, GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra, Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420, GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go, GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL, GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL, GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X, GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X, GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL, Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI, GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL, Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X, GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL, Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra, GeForce FX 5800, Quadro FX 2000, Quadro FX 1000, GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT, GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700, GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200, GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250, GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M, Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI, GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra, GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra, GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700, GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE, GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700, Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800, GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT, GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000, GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT, GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400, Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT, GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600, GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL, GeForce Go 6600, GeForce Go 6600 GT, Quadro FX 550, Quadro FX 550, Quadro FX 540, GeForce 6200, GeForce 6500, GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM), GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400, GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 6800, GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT, GeForce 6200, GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX, GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800, GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7300 LE, GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300, GeForce Go 7400, GeForce Go 7400 GS, Quadro NVS 110M, Quadro NVS 120M, Quadro FX 350M, GeForce 7500 LE, Quadro FX 350, GeForce 7300 GS, GeForce 7600 GT, GeForce 7600 GS, GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT, GeForce Go 7700, GeForce Go 7600, GeForce Go 7600 GT, Quadro NVS 300M, GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560, GeForce 7900 GTX, GeForce 7900 GT, GeForce 7900 GS, GeForce Go 7900 GS, GeForce Go 7900 GTX, Quadro FX 2500M, Quadro FX 1500M, Quadro FX 5500, Quadro FX 3500, Quadro FX 1500, Quadro FX 4500 X2, GeForce 6150, GeForce 6150 LE, GeForce 6100, GeForce Go 6150, GeForce Go 6100, GeForce 8800 GTX, GeForce 8800 GTS, GeForce 8800 Ultra, Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS, GeForce 8600 GT, GeForce 8600 GT, GeForce 8400 GS, GeForce 8600M GT, GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M, Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS, GeForce 8400 GS, GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS, GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M, Quadro NVS 135M, Quadro FX 360M, Quadro NVS 290, GeForce 8800 GT, GeForce 8800 GS, GeForce 8800 GS, GeForce 8800 GT, Quadro FX 3700, GeForce 9600 GT, GeForce 8400 GS (II) Primary Device is: PCI 02:00:0 (--) Chipset GeForce 8500 GT found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf6000000 - 0xf6003fff (0x4000) MX[B]E [5] -1 0 0xf6004000 - 0xf6007fff (0x4000) MX[B]E [6] -1 0 0xf6107000 - 0xf6107fff (0x1000) MX[B]E [7] -1 0 0xf6100000 - 0xf6103fff (0x4000) MX[B]E [8] -1 0 0xf6108000 - 0xf610ffff (0x8000) MX[B]E [9] -1 0 0xf6104000 - 0xf6104fff (0x1000) MX[B]E [10] -1 0 0xf6106000 - 0xf6106fff (0x1000) MX[B]E [11] -1 0 0xf6105000 - 0xf6105fff (0x1000) MX[B]E [12] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B](B) [13] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [14] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B) [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [17] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [18] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]E [19] -1 0 0x00000b60 - 0x00000b6f (0x10) IX[B]E [20] -1 0 0x00000960 - 0x0000096f (0x10) IX[B]E [21] -1 0 0x00000be0 - 0x00000bef (0x10) IX[B]E [22] -1 0 0x000009e0 - 0x000009ef (0x10) IX[B]E [23] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [24] -1 0 0x00000b70 - 0x00000b7f (0x10) IX[B]E [25] -1 0 0x00000970 - 0x0000097f (0x10) IX[B]E [26] -1 0 0x00000bf0 - 0x00000bff (0x10) IX[B]E [27] -1 0 0x000009f0 - 0x000009ff (0x10) IX[B]E [28] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]E [29] -1 0 0x00001c80 - 0x00001cff (0x80) IX[B]E [30] -1 0 0x00001c00 - 0x00001c7f (0x80) IX[B]E [31] -1 0 0x0000a000 - 0x0000a07f (0x80) IX[B](B) (II) resource ranges after probing: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf6000000 - 0xf6003fff (0x4000) MX[B]E [5] -1 0 0xf6004000 - 0xf6007fff (0x4000) MX[B]E [6] -1 0 0xf6107000 - 0xf6107fff (0x1000) MX[B]E [7] -1 0 0xf6100000 - 0xf6103fff (0x4000) MX[B]E [8] -1 0 0xf6108000 - 0xf610ffff (0x8000) MX[B]E [9] -1 0 0xf6104000 - 0xf6104fff (0x1000) MX[B]E [10] -1 0 0xf6106000 - 0xf6106fff (0x1000) MX[B]E [11] -1 0 0xf6105000 - 0xf6105fff (0x1000) MX[B]E [12] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B](B) [13] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [14] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B) [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [20] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [21] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]E [22] -1 0 0x00000b60 - 0x00000b6f (0x10) IX[B]E [23] -1 0 0x00000960 - 0x0000096f (0x10) IX[B]E [24] -1 0 0x00000be0 - 0x00000bef (0x10) IX[B]E [25] -1 0 0x000009e0 - 0x000009ef (0x10) IX[B]E [26] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [27] -1 0 0x00000b70 - 0x00000b7f (0x10) IX[B]E [28] -1 0 0x00000970 - 0x0000097f (0x10) IX[B]E [29] -1 0 0x00000bf0 - 0x00000bff (0x10) IX[B]E [30] -1 0 0x000009f0 - 0x000009ff (0x10) IX[B]E [31] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]E [32] -1 0 0x00001c80 - 0x00001cff (0x80) IX[B]E [33] -1 0 0x00001c00 - 0x00001c7f (0x80) IX[B]E [34] -1 0 0x0000a000 - 0x0000a07f (0x80) IX[B](B) [35] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [36] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (II) NV(0): Initializing int10 (==) NV(0): Write-combining range (0xa0000,0x20000) was already clear (==) NV(0): Write-combining range (0xc0000,0x40000) was already clear (II) NV(0): Primary V_BIOS segment is: 0xc000 (==) NV(0): Write-combining range (0x0,0x1000) was already clear (--) NV(0): Console is VGA mode 0x3 (==) NV(0): Depth 24, (==) framebuffer bpp 32 (==) NV(0): RGB weight 888 (==) NV(0): Default visual is TrueColor (==) NV(0): Using hardware cursor (==) NV(0): Using gamma correction (1.0, 1.0, 1.0) (==) NV(0): Write-combining range (0xf4000000,0x1000000) was already clear (II) NV(0): MMIO registers mapped at 0x802c00000 (--) NV(0): Total video RAM: 512.0 MB (--) NV(0): BAR1 size: 256.0 MB (--) NV(0): Mapped memory: 256.0 MB (==) NV(0): Write-combining range (0xe0000000,0x10000000) was already clear (II) NV(0): Linear framebuffer mapped at 0x803c00000 (II) Loading sub module "i2c" (II) LoadModule: "i2c"(II) Module "i2c" already built-in (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module "ddc" already built-in (--) NV(0): Connector map: (--) NV(0): Bus 0 -> DAC1 (--) NV(0): Bus 0 -> SOR0 (--) NV(0): Bus 1 -> DAC2 (--) NV(0): Load detection: 340 (II) NV(0): I2C bus "I2C0" initialized. (II) NV(0): Output VGA1 using monitor section Monitor0 (II) NV(0): Output DVI0 has no monitor section (II) NV(0): I2C bus "I2C1" initialized. (II) NV(0): Output VGA2 has no monitor section (II) NV(0): Probing for EDID on I2C bus 0... (II) NV(0): I2C device "I2C0:ddc2" registered at address 0xA0. (--) NV(0): DDC detected a DFP: (II) NV(0): Manufacturer: HWP Model: 2690 Serial#: 16843009 (II) NV(0): Year: 2008 Week: 14 (II) NV(0): EDID Version: 1.3 (II) NV(0): Digital Display Input (II) NV(0): Max H-Image Size [cm]: horiz.: 64 vert.: 40 (II) NV(0): Gamma: 2.20 (II) NV(0): DPMS capabilities: Off; RGB/Color Display (II) NV(0): First detailed timing is preferred mode (II) NV(0): redX: 0.658 redY: 0.324 greenX: 0.204 greenY: 0.665 (II) NV(0): blueX: 0.146 blueY: 0.070 whiteX: 0.313 whiteY: 0.329 (II) NV(0): Manufacturer's mask: 0 (II) NV(0): Supported additional Video Mode: (II) NV(0): clock: 268.0 MHz Image Size: 641 x 400 mm (II) NV(0): h_active: 2560 h_sync: 2608 h_sync_end 2640 h_blank_end 2720 h_border: 0 (II) NV(0): v_active: 1600 v_sync: 1603 v_sync_end 1609 v_blanking: 1646 v_border: 0 (II) NV(0): Supported additional Video Mode: (II) NV(0): clock: 71.0 MHz Image Size: 641 x 400 mm (II) NV(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1440 h_border: 0 (II) NV(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 823 v_border: 0 (II) NV(0): Monitor name: HP LP3065 (II) NV(0): Serial No: CNN8140R2D (II) NV(0): EDID (in hex): (II) NV(0): 00ffffffffffff0022f0902601010101 (II) NV(0): 0e120103804028782a8585a85334aa25 (II) NV(0): 12505400000001010101010101010101 (II) NV(0): 010101010101b06800a0a0402e603020 (II) NV(0): 360081902100001abc1b00a050201730 (II) NV(0): 3020360081902100001a000000fc0048 (II) NV(0): 50204c50333036350a202020000000ff (II) NV(0): 00434e4e383134305232440a20200081 (--) NV(0): Trying load detection on VGA1 ... nothing. (II) NV(0): EDID vendor "HWP", prod id 9872 (II) NV(0): Probing for EDID on I2C bus 1... (II) NV(0): I2C device "I2C1:ddc2" registered at address 0xA0. (II) NV(0): I2C device "I2C1:ddc2" removed. (II) NV(0): ... none found (--) NV(0): Trying load detection on VGA2 ... nothing. (II) NV(0): Output VGA1 disconnected (II) NV(0): Output DVI0 connected (II) NV(0): Output VGA2 disconnected (II) NV(0): Output DVI0 using initial mode 1280x800 (--) NV(0): Virtual size is 1280x1280 (pitch 1280) (**) NV(0): Driver mode "1280x800": 71.0 MHz (scaled from 0.0 MHz), 49.3 kHz, 59.9 Hz (II) NV(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz) (**) NV(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz (II) NV(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (**) NV(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz (II) NV(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (**) NV(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz (II) NV(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (**) NV(0): Default mode "512x384": 32.5 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz (D) (II) NV(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz) (**) NV(0): Display dimensions: (641, 400) mm (**) NV(0): DPI set to (50, 81) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/local/lib/xorg/modules//libxaa.so (II) Module xaa: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.2.0 ABI class: X.Org Video Driver, version 2.0 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B] [1] 0 0 0xe0000000 - 0xefffffff (0x10000000) MX[B] [2] 0 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B] [3] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [7] -1 0 0xf6000000 - 0xf6003fff (0x4000) MX[B]E [8] -1 0 0xf6004000 - 0xf6007fff (0x4000) MX[B]E [9] -1 0 0xf6107000 - 0xf6107fff (0x1000) MX[B]E [10] -1 0 0xf6100000 - 0xf6103fff (0x4000) MX[B]E [11] -1 0 0xf6108000 - 0xf610ffff (0x8000) MX[B]E [12] -1 0 0xf6104000 - 0xf6104fff (0x1000) MX[B]E [13] -1 0 0xf6106000 - 0xf6106fff (0x1000) MX[B]E [14] -1 0 0xf6105000 - 0xf6105fff (0x1000) MX[B]E [15] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B](B) [16] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [17] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B) [18] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [19] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [20] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [21] 0 0 0x0000a000 - 0x0000a07f (0x80) IX[B] [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [23] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [24] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [25] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]E [26] -1 0 0x00000b60 - 0x00000b6f (0x10) IX[B]E [27] -1 0 0x00000960 - 0x0000096f (0x10) IX[B]E [28] -1 0 0x00000be0 - 0x00000bef (0x10) IX[B]E [29] -1 0 0x000009e0 - 0x000009ef (0x10) IX[B]E [30] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [31] -1 0 0x00000b70 - 0x00000b7f (0x10) IX[B]E [32] -1 0 0x00000970 - 0x0000097f (0x10) IX[B]E [33] -1 0 0x00000bf0 - 0x00000bff (0x10) IX[B]E [34] -1 0 0x000009f0 - 0x000009ff (0x10) IX[B]E [35] -1 0 0x0000f000 - 0x0000f0ff (0x100) IX[B]E [36] -1 0 0x00001c80 - 0x00001cff (0x80) IX[B]E [37] -1 0 0x00001c00 - 0x00001c7f (0x80) IX[B]E [38] -1 0 0x0000a000 - 0x0000a07f (0x80) IX[B](B) [39] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [40] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (--) NV(0): 153.75 MB available for offscreen pixmaps (II) NV(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Scanline Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 32 256x256 slots 16 512x512 slots (==) NV(0): Backing store disabled (==) NV(0): Silken mouse enabled (II) NV(0): RandR 1.2 enabled, ignore the following RandR disabled message. (--) RandR disabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension XAccessControlExtension (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/local/lib/xorg/modules/extensions//libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) GLX: Initialized MESA-PROXY GL provider for screen 0 (II) NV(0): Setting screen physical size to 641 x 400 (**) Option "Protocol" "auto" (**) Mouse0: Device: "/dev/sysmouse" (**) Mouse0: Protocol: "auto" (**) Option "CorePointer" (**) Mouse0: always reports core events (**) Option "Device" "/dev/sysmouse" (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5 6 7" (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7 (**) Mouse0: Buttons: 11 (**) Mouse0: Sensitivity: 1 (**) Option "CoreKeyboard" (**) Keyboard0: always reports core events (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse Finally, here is the output from xrandr -q after starting x: Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1280 VGA1 disconnected DVI0 connected 1280x800+0+0 641mm x 400mm 1280x800 59.9* 1024x768 60.0 800x600 60.3 640x480 59.9 512x384 120.0 VGA2 disconnected From jimmiejaz at gmail.com Mon Jun 2 00:56:55 2008 From: jimmiejaz at gmail.com (Jimmie James) Date: Mon Jun 2 00:57:24 2008 Subject: Error in I830WaitLpRing() Message-ID: <48433F18.4090003@gmail.com> Switching from i810 to intel and I still get the same error as reported in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=118778 Using the Option "NoAccel" with the intel driver seems to help, but at a loss of features (mplayer doesn't work in full screen, no DRI, etc) My original PR on this, Wed, 16 Apr 2008 http://www.freebsd.org/cgi/query-pr.cgi?pr=122830 http://pastebin.ca/986954 Console messages /Xorg.0.log http://pastebin.ca/983903 dmesg http://pastebin.ca/983910 xorg.conf http://pastebin.ca/983911 pciconf -vl Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ffc0001getbl_err: 0x0 ipeir: 0 iphdr: 7d000006 LP ring tail: 1afa0 head: 1ad64 len: 1f001 start 0 eir: 0 esr: 0 emr: ffff instdone: fa41 instpm: 0 memmode: 108 instps: 800f00c4 hwstam: fffe ier: 2 imr: 8 iir: 80 Ring at virtual 0x2884d000 head 0x1ad64 tail 0x1afa0 count 143 That error causes me to have to reboot to get X working again. This machine has been running over a year without problems, this is something new in the last week or two (I didn't update ports, too busy working, so I can't pinpoint the date the change happened, only that on Sat.12th Apr.or Sun the 13th I updated) -- Over the years I've come to regard you as people I've met. If you can't beat your computer at chess, try kickboxing. From bugmaster at FreeBSD.org Mon Jun 2 11:07:13 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 2 11:07:44 2008 Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org Message-ID: <200806021107.m52B7CZf093365@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/106370 x11 Screen corruption when using Direct Rendering on a PCI o ports/116359 x11 x11/xorg - screen blinks with PCI-E nvidia card and ve o ports/117195 x11 ix11/Xorg 7.3 dumps core at exit (sig 11) f ports/117508 x11 x11/xorg 7.2,7.3 i8i0 and intel crash system using Ble o ports/117766 x11 x11-servers/xorg-server (7.3) crashes under heavy load o ports/118950 x11 x11-drivers/xf86-video-nv - xorg xf86 nv (nvidia) driv o ports/119037 x11 x11: Can't type _ (Underscore) under X (gnome) f ports/119091 x11 x11-drivers/xf86-video-intel 2.1.1 panics system o ports/121360 x11 x11/xorg - Change default of ~/.xsession-errors to off o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/122924 x11 XCreateImage fails in most recent x11/XOrg 11 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s ports/73743 x11 XOrg/XFree xauth add/startx problem o ports/93667 x11 x11/xorg-libraries: undefined symbol in libOSMesa.* is o ports/113106 x11 x11/xorg - Xorg 7.2 + Mach64 + dri produces error mess f ports/114827 x11 Xorg server crashes when starting astro/google-earth o ports/115020 x11 New port: graphics/osmesa - Mesa's off-screen renderin s ports/115536 x11 [new port] x11/xorg-base port for a minimal X.Org inst o ports/116443 x11 x11-drivers/xf86-input-keyboard patch for USB jp106 ke f ports/116603 x11 x11/xorg server 7.3 hangs up f ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) f ports/118217 x11 xorg doesnt find usb mouse when initiated with devd, w o ports/118547 x11 [patch] x11/xdm fails with pam_krb5 o ports/118645 x11 Xorg need realtime priority for mouse work nice o ports/121230 x11 [patch] ports/x11/xkeyboard-config WITHOUT_NLS support o ports/123137 x11 x11/libX11: missing ru_RU.UTF-8 locale 14 problems total. From joerg at FreeBSD.org Mon Jun 2 21:26:49 2008 From: joerg at FreeBSD.org (joerg@FreeBSD.org) Date: Mon Jun 2 21:26:51 2008 Subject: ports/124220: [amd64] X.org server runs in infinite loop Message-ID: <200806022126.m52LQnJk051613@freefall.freebsd.org> Synopsis: [amd64] X.org server runs in infinite loop Responsible-Changed-From-To: freebsd-ports-bugs->x11 Responsible-Changed-By: joerg Responsible-Changed-When: Mon Jun 2 23:26:16 MEST 2008 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=124220 From flz at xbsd.org Tue Jun 3 13:51:59 2008 From: flz at xbsd.org (Florent Thoumie) Date: Tue Jun 3 13:52:02 2008 Subject: can't get 2560x1600 (freebsd 7.0, nv, 8500gt, hp lp3065) In-Reply-To: References: Message-ID: On Sun, Jun 1, 2008 at 7:46 PM, Rawld Gill wrote: > I am unable to get X to display 2560x1600. The best I can get is 1280x800. > I've constructed a xorg.conf file with the proper modelines (I think), but > this doesn't help. Try setting "Virtual 2560 1600" in the Display subsection. -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer From amarat at ksu.ru Tue Jun 3 16:21:11 2008 From: amarat at ksu.ru (Marat N.Afanasyev) Date: Tue Jun 3 16:21:18 2008 Subject: updating drm Message-ID: <48456950.8060507@ksu.ru> Hello! I wonder is there any plans to update drm in either CURRENT or STABLE from MESA tree? -- SY, Marat From cokane at FreeBSD.org Tue Jun 3 17:10:08 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Tue Jun 3 17:10:12 2008 Subject: updating drm In-Reply-To: <48456950.8060507@ksu.ru> References: <48456950.8060507@ksu.ru> Message-ID: <1212511997.15220.25.camel@localhost> On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > Hello! > > I wonder is there any plans to update drm in either CURRENT or STABLE > from MESA tree? > I believe so, but only after the stuff in the MESA tree is stable. From what I can tell, there is still work going into developing it more (integrating VBLANK and other changes). There will probably be a merge once the BSD part of the tree is stable again. I've also got at least one outstanding bug report open that needs either fixing in drm/bsd-core or in xf86-video-ati. -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080603/f2469b2f/attachment.pgp From rnoland at 2hip.net Tue Jun 3 17:30:19 2008 From: rnoland at 2hip.net (Robert Noland) Date: Tue Jun 3 17:30:23 2008 Subject: updating drm In-Reply-To: <48456950.8060507@ksu.ru> References: <48456950.8060507@ksu.ru> Message-ID: <1212512034.32992.13.camel@squirrel.corp.cox.com> On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > Hello! > > I wonder is there any plans to update drm in either CURRENT or STABLE > from MESA tree? I'm working on drm at the moment and it would be nice to get a new build into the kernel soon, but I don't have a commit bit, so we will have to get some help... robert. -- Robert Noland 2Hip Networks From cokane at FreeBSD.org Tue Jun 3 17:51:33 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Tue Jun 3 17:51:38 2008 Subject: updating drm In-Reply-To: <1212512034.32992.13.camel@squirrel.corp.cox.com> References: <48456950.8060507@ksu.ru> <1212512034.32992.13.camel@squirrel.corp.cox.com> Message-ID: <1212515390.15220.33.camel@localhost> On Tue, 2008-06-03 at 12:53 -0400, Robert Noland wrote: > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > > Hello! > > > > I wonder is there any plans to update drm in either CURRENT or STABLE > > from MESA tree? > > I'm working on drm at the moment and it would be nice to get a new build > into the kernel soon, but I don't have a commit bit, so we will have to > get some help... > > robert. > Robert, Can you take a look at: https://bugs.freedesktop.org/show_bug.cgi?id=16200 And give me any insight? -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080603/d3ffa512/attachment.pgp From rnoland at 2hip.net Tue Jun 3 19:19:44 2008 From: rnoland at 2hip.net (Robert Noland) Date: Tue Jun 3 19:19:49 2008 Subject: updating drm In-Reply-To: <1212515390.15220.33.camel@localhost> References: <48456950.8060507@ksu.ru> <1212512034.32992.13.camel@squirrel.corp.cox.com> <1212515390.15220.33.camel@localhost> Message-ID: <1212520774.32992.19.camel@squirrel.corp.cox.com> On Tue, 2008-06-03 at 13:49 -0400, Coleman Kane wrote: > On Tue, 2008-06-03 at 12:53 -0400, Robert Noland wrote: > > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > > > Hello! > > > > > > I wonder is there any plans to update drm in either CURRENT or STABLE > > > from MESA tree? > > > > I'm working on drm at the moment and it would be nice to get a new build > > into the kernel soon, but I don't have a commit bit, so we will have to > > get some help... > > > > robert. > > > > Robert, > > Can you take a look at: > https://bugs.freedesktop.org/show_bug.cgi?id=16200 > > And give me any insight? > I have talked with another user who is having the same issue i think. AFAIK, concensus is that it is a gart problem and airlied may be looking at it. I don't have any radeon hardware now, so it's difficult for me to know what is going on. I'm busy trying to get all the vblank changes in and working properly. robert. -- Robert Noland 2Hip Networks From freebsd at troback.com Wed Jun 4 11:28:23 2008 From: freebsd at troback.com (Anders Troback) Date: Wed Jun 4 11:28:27 2008 Subject: FreeBSD Port: x11/xdm Message-ID: <20080604131217.544516c0@server09.gelita.swe> Hi, I'm having problems to connect to a remote XDM session! I did edit the xdm-config and Xaccess and the local XDM session are working just fine! Some ideas? Thanks! -- Anders Trob?ck http://www.troback.com/ ============================================ Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" -------------------------------------------- From martin at email.aon.at Wed Jun 4 16:50:03 2008 From: martin at email.aon.at (Martin Birgmeier) Date: Wed Jun 4 16:50:06 2008 Subject: ports/119091: x11-drivers/xf86-video-intel 2.1.1 panics system Message-ID: <200806041650.m54Go3h7059286@freefall.freebsd.org> The following reply was made to PR ports/119091; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/119091: x11-drivers/xf86-video-intel 2.1.1 panics system Date: Wed, 4 Jun 2008 18:20:40 +0200 (CEST) Until a few days ago I was nearly convinced that the driver is working now... FreeBSD atpcdvvc.xyzzy 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu May 22 17:20:59 CEST 2008 root@atpcdvvc.xyzzy:/usr/VOL/OBJ/FreeBSD/RELENG_7_0_0_RELEASE/src/sys/XYZZY_SMP_NA i386 xf86-video-intel-2.2.1, built on April 5 ports mostly up to date However, at that date, I started doing heavy-duty file moving using the KDE file manager konqueror for the first time (I was mostly using the command line before that). Dragging icons from time to time leads to panics again - actually not panics, but simply instant reboots. Since then, I am back to the command line. Just from the looks I'd guess that the cause must be within bitblt routines, but I am not familiar with modern X software. Warning: this might be a new defect, as the system is now running on an S6410 laptop. If you want you may close this defect (I cannot reproduce it on the original HW any more), and I'll open a new one. So, summarizing the feedback: Something is still badly broken. From amarat at ksu.ru Wed Jun 4 21:01:42 2008 From: amarat at ksu.ru (Marat N.Afanasyev) Date: Wed Jun 4 21:01:45 2008 Subject: updating drm In-Reply-To: <1212511997.15220.25.camel@localhost> References: <48456950.8060507@ksu.ru> <1212511997.15220.25.camel@localhost> Message-ID: <484702B1.6080402@ksu.ru> Coleman Kane ?????: > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: >> Hello! >> >> I wonder is there any plans to update drm in either CURRENT or STABLE >> from MESA tree? >> > > I believe so, but only after the stuff in the MESA tree is stable. From > what I can tell, there is still work going into developing it more > (integrating VBLANK and other changes). There will probably be a merge > once the BSD part of the tree is stable again. > > I've also got at least one outstanding bug report open that needs either > fixing in drm/bsd-core or in xf86-video-ati. > I think that without importing drm onto, at least, CURRENT, there will be a few chances to receive bug-reports to be worked with ;) -- SY, Marat From flz at xbsd.org Thu Jun 5 11:21:45 2008 From: flz at xbsd.org (Florent Thoumie) Date: Thu Jun 5 11:21:52 2008 Subject: updating drm In-Reply-To: <1212512034.32992.13.camel@squirrel.corp.cox.com> References: <48456950.8060507@ksu.ru> <1212512034.32992.13.camel@squirrel.corp.cox.com> Message-ID: On Tue, Jun 3, 2008 at 5:53 PM, Robert Noland wrote: > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: >> Hello! >> >> I wonder is there any plans to update drm in either CURRENT or STABLE >> from MESA tree? > > I'm working on drm at the moment and it would be nice to get a new build > into the kernel soon, but I don't have a commit bit, so we will have to > get some help... Getting the code in the tree isn't exactly the hardest part :-) Poke Eric when your patch is ready, or myself if he doesn't answer. -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer From freebsd at troback.com Thu Jun 5 13:18:24 2008 From: freebsd at troback.com (Anders Troback) Date: Thu Jun 5 13:18:35 2008 Subject: FreeBSD Port: x11/xdm In-Reply-To: <20080604131217.544516c0@server09.gelita.swe> References: <20080604131217.544516c0@server09.gelita.swe> Message-ID: <20080605150038.4b11a348@server09.gelita.swe> On Wed, 4 Jun 2008 13:12:17 +0200 Anders Troback wrote: > Hi, > > I'm having problems to connect to a remote XDM session! > > I did edit the xdm-config and Xaccess and the local XDM session are > working just fine! > > Some ideas? > > Thanks! > It was the LISTEN in Xaccess! LISTEN * is not working anymore, I had to specify a host name or IP address! Is this right? Are not LISTEN * suppose to work? -- Anders Trob?ck http://www.troback.com/ ============================================ Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" -------------------------------------------- From freebsd at troback.com Thu Jun 5 13:18:24 2008 From: freebsd at troback.com (Anders Troback) Date: Thu Jun 5 13:18:35 2008 Subject: XDMCP working? In-Reply-To: <20071128132421.511450d3@itpc01.gelita.swe> References: <20071128132421.511450d3@itpc01.gelita.swe> Message-ID: <20080605150016.63348077@server09.gelita.swe> On Wed, 28 Nov 2007 13:24:21 +0000 Anders Trob?ck wrote: > Hi, > > are XDMCP working all right? I'm having problems to connect with: > > Xnest -query server25 :2 > > All I got are a grey window without a greeter! > > I'm running 7.0 but have the same on 6.2! > > I did place a ! on the last row in xdm-config and I did remove the # > from row 49 and 67 in Xaccess and I can logon on the local terminal. > > Thanks!!! > > > \\troback It was the LISTEN in Xaccess! LISTEN * are not working anymore, I had to specify a host name or IP address! -- Anders Trob?ck http://www.troback.com/ ============================================ Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" -------------------------------------------- From cokane at FreeBSD.org Thu Jun 5 18:19:49 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Thu Jun 5 18:19:53 2008 Subject: updating drm In-Reply-To: <484702B1.6080402@ksu.ru> References: <48456950.8060507@ksu.ru> <1212511997.15220.25.camel@localhost> <484702B1.6080402@ksu.ru> Message-ID: <1212688916.1904.19.camel@localhost> On Thu, 2008-06-05 at 01:01 +0400, Marat N.Afanasyev wrote: > Coleman Kane ?????: > > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > >> Hello! > >> > >> I wonder is there any plans to update drm in either CURRENT or STABLE > >> from MESA tree? > >> > > > > I believe so, but only after the stuff in the MESA tree is stable. From > > what I can tell, there is still work going into developing it more > > (integrating VBLANK and other changes). There will probably be a merge > > once the BSD part of the tree is stable again. > > > > I've also got at least one outstanding bug report open that needs either > > fixing in drm/bsd-core or in xf86-video-ati. > > > > I think that without importing drm onto, at least, CURRENT, there will > be a few chances to receive bug-reports to be worked with ;) > The bug report above is one that I've submitted, and we're currently working on resolving it. At least two combined changes happened at the same time to the BSD drm code (vblank-rework as well as r5xx/r6xx support). I've been trying to get the latter one working, but in the process I think I might have gotten bit by the former. The drm code has almost always been continually developed in the mesa/drm git tree at freedesktop.org, with snapshots being merged into the FreeBSD tree as new features and changes settle. I am confident that when more of these outstanding issues are resolved, the resulting code will get merged. A likely result of just merging everything now might be a sudden breakage of DRI for numerous R1xx, R2xx, R3xx, and R4xx users who already have good, working DRI support. It would be better if the deluge of PR's was limited to the users of R5xx and above cards, who right now don't have DRI support. I am also confident that this will happen real-soon-now. That said, anybody can see/get the current development trees by visiting: * http://gitweb.freedesktop.org/?p=mesa/drm.git;a=summary -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080605/2fdc1f63/attachment.pgp From rnoland at 2hip.net Thu Jun 5 18:25:24 2008 From: rnoland at 2hip.net (Robert Noland) Date: Thu Jun 5 18:25:31 2008 Subject: updating drm In-Reply-To: <1212688916.1904.19.camel@localhost> References: <48456950.8060507@ksu.ru> <1212511997.15220.25.camel@localhost> <484702B1.6080402@ksu.ru> <1212688916.1904.19.camel@localhost> Message-ID: <1212690315.57447.24.camel@squirrel.corp.cox.com> On Thu, 2008-06-05 at 14:01 -0400, Coleman Kane wrote: > On Thu, 2008-06-05 at 01:01 +0400, Marat N.Afanasyev wrote: > > Coleman Kane ?????: > > > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > > >> Hello! > > >> > > >> I wonder is there any plans to update drm in either CURRENT or STABLE > > >> from MESA tree? > > >> > > > > > > I believe so, but only after the stuff in the MESA tree is stable. From > > > what I can tell, there is still work going into developing it more > > > (integrating VBLANK and other changes). There will probably be a merge > > > once the BSD part of the tree is stable again. > > > > > > I've also got at least one outstanding bug report open that needs either > > > fixing in drm/bsd-core or in xf86-video-ati. > > > > > > > I think that without importing drm onto, at least, CURRENT, there will > > be a few chances to receive bug-reports to be worked with ;) > > > > The bug report above is one that I've submitted, and we're currently > working on resolving it. > > At least two combined changes happened at the same time to the BSD drm > code (vblank-rework as well as r5xx/r6xx support). I've been trying to > get the latter one working, but in the process I think I might have > gotten bit by the former. The drm code has almost always been > continually developed in the mesa/drm git tree at freedesktop.org, with > snapshots being merged into the FreeBSD tree as new features and changes > settle. > > I am confident that when more of these outstanding issues are resolved, > the resulting code will get merged. A likely result of just merging > everything now might be a sudden breakage of DRI for numerous R1xx, > R2xx, R3xx, and R4xx users who already have good, working DRI support. > It would be better if the deluge of PR's was limited to the users of > R5xx and above cards, who right now don't have DRI support. I am also > confident that this will happen real-soon-now. > > That said, anybody can see/get the current development trees by > visiting: > * http://gitweb.freedesktop.org/?p=mesa/drm.git;a=summary FWIW, the current HEAD has a couple of locking issues... I have fixes that have not been pushed to fdo yet, though they should be soon. robert. -- Robert Noland 2Hip Networks From rnoland at 2hip.net Sat Jun 7 13:28:01 2008 From: rnoland at 2hip.net (Robert Noland) Date: Sat Jun 7 13:28:28 2008 Subject: updating drm In-Reply-To: References: <48456950.8060507@ksu.ru> <1212512034.32992.13.camel@squirrel.corp.cox.com> Message-ID: <1212845253.32965.8.camel@wombat.2hip.net> On Thu, 2008-06-05 at 12:21 +0100, Florent Thoumie wrote: > On Tue, Jun 3, 2008 at 5:53 PM, Robert Noland wrote: > > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote: > >> Hello! > >> > >> I wonder is there any plans to update drm in either CURRENT or STABLE > >> from MESA tree? > > > > I'm working on drm at the moment and it would be nice to get a new build > > into the kernel soon, but I don't have a commit bit, so we will have to > > get some help... > > Getting the code in the tree isn't exactly the hardest part :-) > > Poke Eric when your patch is ready, or myself if he doesn't answer. Yeah, Eric is really busy right now... I could use a larger testing pool, right now it consists of only two users and my personal hardware inventory is quite limited these days. I've resolved the pcie r500 issue for at least one of them, the other is still questionable... robert. -- Robert Noland 2Hip Networks From rsmith at xs4all.nl Sun Jun 8 11:36:55 2008 From: rsmith at xs4all.nl (Roland Smith) Date: Sun Jun 8 11:36:59 2008 Subject: 7-STABLE and Intel G33 Message-ID: <20080608104234.GA73057@slackbox.xs4all.nl> My PC has built-in intel G33 graphics, which I'm trying to get to work in something better then vesa. Following the instructions in http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039638.html I have compiled and installed the driver and kernel modules from the git trees for drm and the xf86-video-intel driver from June 5th. I also patched agp_i810.c to remove the comments from the chipset identifiers and rebuilt the kernel. After loading the i915.ko kernel module from the git tree, and starting X with a config file using the intel driver, I still get; (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x006ff000 (pgoffset 1791) (WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 1 at offset 0x6ff000 failed (Invalid argument) Fatal server error: Couldn't bind memory for front buffer In dmesg output I see: agp0: trying to bind into stolen memory Looking at the Xorg.0.log, the xf86-video-intel driver and the drm and dri drivers seem to initialize OK. Grepping through the source, this error seems to originate in /usr/src/sys/pci/agp_i810.c; if ( sc->chiptype != CHIP_I810 ) { if ( (offset >> AGP_PAGE_SHIFT) < sc->stolen ) { device_printf(dev, "trying to bind into stolen memory"); return EINVAL; } [disclaimer: I'm not a software engineer by education or trade, just a mechanical engineer who likes to tinker with computers and software] I've been reading the agp code, the intel driver code and I've skimmed the intel docs. I find the code quite hard to understand, and the intel docs nigh-on unreadable. Would modifying the if-statement to not produce this error on the CHIP_G33 fix this problem? Or would it horribly blow up in my face? Any help to get this to work would be very much appreciated! Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080608/126bd4e3/attachment.pgp From rnoland at 2hip.net Sun Jun 8 15:31:09 2008 From: rnoland at 2hip.net (Robert Noland) Date: Sun Jun 8 15:31:13 2008 Subject: updating drm In-Reply-To: <1212690315.57447.24.camel@squirrel.corp.cox.com> References: <48456950.8060507@ksu.ru> <1212511997.15220.25.camel@localhost> <484702B1.6080402@ksu.ru> <1212688916.1904.19.camel@localhost> <1212690315.57447.24.camel@squirrel.corp.cox.com> Message-ID: <1212939056.1471.29.camel@wombat.2hip.net> On Thu, 2008-06-05 at 14:25 -0400, Robert Noland wrote: > On Thu, 2008-06-05 at 14:01 -0400, Coleman Kane wrote: ... > > That said, anybody can see/get the current development trees by > > visiting: > > * http://gitweb.freedesktop.org/?p=mesa/drm.git;a=summary > > FWIW, the current HEAD has a couple of locking issues... I have fixes > that have not been pushed to fdo yet, though they should be soon. FYI, I have pushed all of my changes except for intel suspend/resume support now. robert. > robert. > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080608/b0b878bb/attachment.pgp From rnoland at 2hip.net Sun Jun 8 15:31:40 2008 From: rnoland at 2hip.net (Robert Noland) Date: Sun Jun 8 15:31:44 2008 Subject: 7-STABLE and Intel G33 In-Reply-To: <20080608104234.GA73057@slackbox.xs4all.nl> References: <20080608104234.GA73057@slackbox.xs4all.nl> Message-ID: <1212937757.1471.23.camel@wombat.2hip.net> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080608/301227f4/attachment.pgp From rsmith at xs4all.nl Sun Jun 8 21:58:02 2008 From: rsmith at xs4all.nl (Roland Smith) Date: Sun Jun 8 21:58:10 2008 Subject: 7-STABLE and Intel G33 In-Reply-To: <1212937757.1471.23.camel@wombat.2hip.net> References: <20080608104234.GA73057@slackbox.xs4all.nl> <1212937757.1471.23.camel@wombat.2hip.net> Message-ID: <20080608215747.GA1500@slackbox.xs4all.nl> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080608/22f503fe/attachment.pgp From wahjava.ml at gmail.com Mon Jun 9 00:58:08 2008 From: wahjava.ml at gmail.com (=?utf-8?B?4KSG4KS24KWA4KS3IOCktuClgeCkleCljeCksg==?= Ashish Shukla) Date: Mon Jun 9 00:58:11 2008 Subject: 'intel' graphics slow on 945G Message-ID: <20080609003149.GB2291@chateau.d.lf> Hi, I'm running FreeBSD 7.0-RELEASE-p1 (amd64) on Intel D945GNTL mobo (GMA950 graphics). And, I've experienced the performance of graphics slow as compared to the performance in GNU/Linux. * The framerate reported by glxgears is less compared to GNU/Linux. abbe [~] chateau% glxgears 2236 frames in 5.0 seconds = 447.134 FPS 2242 frames in 5.0 seconds = 448.295 FPS 2263 frames in 5.0 seconds = 452.524 FPS 2276 frames in 5.0 seconds = 455.112 FPS * I'm not able to run compiz in FreeBSD, got following error: abbe [~] chateau% compiz --replace compiz (core) - Fatal: GLX_EXT_texture_from_pixmap is missing compiz (core) - Error: Failed to manage screen: 0 compiz (core) - Fatal: No manageable screens found on display :0.0 My hardware is Intel Pentium 4 630 (EM64T/HT) + 2 GiB DDR2 (533 MHz). Is this the currently expected performance, or there could be some issue at my end, hmm...? TIA -- Ashish Shukla ???? ????? http://wahjava.wordpress.com/ ?-- ?- ???? ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080609/9eed94c1/attachment.pgp From novembre at gmail.com Mon Jun 9 03:04:02 2008 From: novembre at gmail.com (Novembre) Date: Mon Jun 9 03:04:04 2008 Subject: 'intel' graphics slow on 945G Message-ID: <3b47caa90806082004u34415f90pc4fa27a75df6d65e@mail.gmail.com> Hi, There is a tutorial on how to run Compiz Fusion on FreeBSD here: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/compiz-fusion/index.html, but as far as I understood, it is mainly written with nVidia cards in mind. I have an Intel 965G card, and I had to make some changes to make Compiz Fusion work. First of all, I use the intel driver (not the older i810) and XAA (not the default EXA) as the acceleration method, since EXA results in poor performance especially in Firefox. In my xorg.conf, I have the following lines: Option "AIGLX" "true" in ServerLayout section, Option "AccelMethod" "XAA" Option "XAANoOffscreenPixmaps" "true" Option "AddARGBGLXVisuals" "true" Option "DRI" "true" in Device section, and at the end of the file, these: Section "DRI" Mode 0666 EndSection Section "Extensions" Option "Composite" "enable" EndSection Then, I before I start Compiz, I run the following commands: LIBGL_ALWAYS_INDIRECT=1; export LIBGL_ALWAYS_INDIRECT INTEL_BATCH=1; export INTEL_BATCH And I run Compiz with: $ compiz --replace --indirect-rendering --sm-disable ccp & $ emerald --replace & Then it runs fine (although I have my own share of problems when I close X). My glxgears benchmark is around 1150fps. Here is the Compiz Fusion wiki page for Intel hardware: http://wiki.compiz-fusion.org/Intel%20with%20AiGLX Good luck From bugmaster at FreeBSD.org Mon Jun 9 11:07:09 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 9 11:07:57 2008 Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org Message-ID: <200806091107.m59B78ov070939@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/106370 x11 Screen corruption when using Direct Rendering on a PCI o ports/116359 x11 x11/xorg - screen blinks with PCI-E nvidia card and ve o ports/117195 x11 ix11/Xorg 7.3 dumps core at exit (sig 11) f ports/117508 x11 x11/xorg 7.2,7.3 i8i0 and intel crash system using Ble o ports/117766 x11 x11-servers/xorg-server (7.3) crashes under heavy load o ports/118950 x11 x11-drivers/xf86-video-nv - xorg xf86 nv (nvidia) driv o ports/119037 x11 x11: Can't type _ (Underscore) under X (gnome) f ports/119091 x11 x11-drivers/xf86-video-intel 2.1.1 panics system o ports/121360 x11 x11/xorg - Change default of ~/.xsession-errors to off o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/122924 x11 XCreateImage fails in most recent x11/XOrg 11 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s ports/73743 x11 XOrg/XFree xauth add/startx problem o ports/93667 x11 x11/xorg-libraries: undefined symbol in libOSMesa.* is o ports/113106 x11 x11/xorg - Xorg 7.2 + Mach64 + dri produces error mess f ports/114827 x11 Xorg server crashes when starting astro/google-earth o ports/115020 x11 New port: graphics/osmesa - Mesa's off-screen renderin s ports/115536 x11 [new port] x11/xorg-base port for a minimal X.Org inst o ports/116443 x11 x11-drivers/xf86-input-keyboard patch for USB jp106 ke f ports/116603 x11 x11/xorg server 7.3 hangs up f ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) f ports/118217 x11 xorg doesnt find usb mouse when initiated with devd, w o ports/118547 x11 [patch] x11/xdm fails with pam_krb5 o ports/118645 x11 Xorg need realtime priority for mouse work nice o ports/121230 x11 [patch] ports/x11/xkeyboard-config WITHOUT_NLS support o ports/123137 x11 x11/libX11: missing ru_RU.UTF-8 locale 14 problems total. From bugmaster at FreeBSD.org Mon Jun 9 11:08:47 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 9 11:08:50 2008 Subject: Current problem reports assigned to x11@FreeBSD.org Message-ID: <200806091108.m59B8kIa072884@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/124220 x11 [amd64] x11-servers/xorg-server - X.org server runs in 1 problem total. Non-critical problems From wahjava.ml at gmail.com Mon Jun 9 13:55:38 2008 From: wahjava.ml at gmail.com (=?utf-8?B?4KSG4KS24KWA4KS3IOCktuClgeCkleCljeCksg==?= Ashish Shukla) Date: Mon Jun 9 13:55:41 2008 Subject: 'intel' graphics slow on 945G In-Reply-To: <3b47caa90806082004u34415f90pc4fa27a75df6d65e@mail.gmail.com> References: <3b47caa90806082004u34415f90pc4fa27a75df6d65e@mail.gmail.com> Message-ID: <20080609135518.GB27613@chateau.d.lf> ,--[ On Sun, Jun 08, 2008 at 10:04:00PM -0500, Novembre wrote: | Hi, | | There is a tutorial on how to run Compiz Fusion on FreeBSD here: | http://www.freebsd.org/doc/en_US.ISO8859-1/articles/compiz-fusion/index.html, | but as far as I understood, it is mainly written with nVidia cards in | mind. I have an Intel 965G card, and I had to make some changes to make | Compiz Fusion work. First of all, I use the intel driver (not the older | i810) and XAA (not the default EXA) as the acceleration method, since EXA | results in poor performance especially in Firefox. In my xorg.conf, I have | the following lines: I was also using intel driver, but with EXA enabled, now I've switched to XAA. | | Option "AIGLX" "true" | in ServerLayout section, | | Option "AccelMethod" "XAA" | Option "XAANoOffscreenPixmaps" "true" | Option "AddARGBGLXVisuals" "true" | Option "DRI" "true" | in Device section, | | and at the end of the file, these: | Section "DRI" | Mode 0666 | EndSection | Section "Extensions" | Option "Composite" "enable" | EndSection | | Then, I before I start Compiz, I run the following commands: | LIBGL_ALWAYS_INDIRECT=1; export LIBGL_ALWAYS_INDIRECT | INTEL_BATCH=1; export INTEL_BATCH | | And I run Compiz with: | $ compiz --replace --indirect-rendering --sm-disable ccp & | $ emerald --replace & I've got compiz working[1]. But no change in framerate of glxgears :( . References: [1] - http://www.flickr.com/photos/wahjava/2564309910/ Thank you very much. -- Ashish Shukla ???? ????? http://wahjava.wordpress.com/ ?-- ?- ???? ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080609/67cfd528/attachment.pgp From novembre at gmail.com Tue Jun 10 04:16:45 2008 From: novembre at gmail.com (Novembre) Date: Tue Jun 10 04:16:48 2008 Subject: 'intel' graphics slow on 945G In-Reply-To: <20080609135518.GB27613@chateau.d.lf> References: <3b47caa90806082004u34415f90pc4fa27a75df6d65e@mail.gmail.com> <20080609135518.GB27613@chateau.d.lf> Message-ID: <3b47caa90806092116m360061d0w44dcf62768b1edd2@mail.gmail.com> On Mon, Jun 9, 2008 at 8:55 AM, ???? ????? Ashish Shukla wrote: > ,--[ On Sun, Jun 08, 2008 at 10:04:00PM -0500, Novembre wrote: > | Hi, > | > | There is a tutorial on how to run Compiz Fusion on FreeBSD here: > | > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/compiz-fusion/index.html > , > | but as far as I understood, it is mainly written with nVidia cards in > | mind. I have an Intel 965G card, and I had to make some changes to make > | Compiz Fusion work. First of all, I use the intel driver (not the older > | i810) and XAA (not the default EXA) as the acceleration method, since EXA > | results in poor performance especially in Firefox. In my xorg.conf, I > have > | the following lines: > > I was also using intel driver, but with EXA enabled, now I've switched > to XAA. > > | > | Option "AIGLX" "true" > | in ServerLayout section, > | > | Option "AccelMethod" "XAA" > | Option "XAANoOffscreenPixmaps" "true" > | Option "AddARGBGLXVisuals" "true" > | Option "DRI" "true" > | in Device section, > | > | and at the end of the file, these: > | Section "DRI" > | Mode 0666 > | EndSection > | Section "Extensions" > | Option "Composite" "enable" > | EndSection > | > | Then, I before I start Compiz, I run the following commands: > | LIBGL_ALWAYS_INDIRECT=1; export LIBGL_ALWAYS_INDIRECT > | INTEL_BATCH=1; export INTEL_BATCH > | > | And I run Compiz with: > | $ compiz --replace --indirect-rendering --sm-disable ccp & > | $ emerald --replace & > > I've got compiz working[1]. But no change in framerate of glxgears :( . > > References: > [1] - http://www.flickr.com/photos/wahjava/2564309910/ > > Thank you very much. > -- > Ashish Shukla ???? ????? > http://wahjava.wordpress.com/ > ?-- ?- ???? ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- -- > I'm glad that you have Compiz Fusion running. Unfortunately, I can't help with the framerate; it's just above my level of expertise. Maybe someone more experienced could help. By the way, the Compiz Fusion forums ( http://forum.compiz-fusion.org/) are good as well, a lot of knowledgeable people there... Good luck From bugmaster at FreeBSD.org Mon Jun 16 11:07:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 16 11:08:36 2008 Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org Message-ID: <200806161107.m5GB7540036905@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/106370 x11 Screen corruption when using Direct Rendering on a PCI o ports/116359 x11 x11/xorg - screen blinks with PCI-E nvidia card and ve o ports/117195 x11 ix11/Xorg 7.3 dumps core at exit (sig 11) f ports/117508 x11 x11/xorg 7.2,7.3 i8i0 and intel crash system using Ble o ports/117766 x11 x11-servers/xorg-server (7.3) crashes under heavy load o ports/118950 x11 x11-drivers/xf86-video-nv - xorg xf86 nv (nvidia) driv o ports/119037 x11 x11: Can't type _ (Underscore) under X (gnome) f ports/119091 x11 x11-drivers/xf86-video-intel 2.1.1 panics system o ports/121360 x11 x11/xorg - Change default of ~/.xsession-errors to off o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/122924 x11 XCreateImage fails in most recent x11/XOrg 11 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s ports/73743 x11 XOrg/XFree xauth add/startx problem o ports/93667 x11 x11/xorg-libraries: undefined symbol in libOSMesa.* is o ports/113106 x11 x11/xorg - Xorg 7.2 + Mach64 + dri produces error mess f ports/114827 x11 Xorg server crashes when starting astro/google-earth o ports/115020 x11 New port: graphics/osmesa - Mesa's off-screen renderin s ports/115536 x11 [new port] x11/xorg-base port for a minimal X.Org inst o ports/116443 x11 x11-drivers/xf86-input-keyboard patch for USB jp106 ke f ports/116603 x11 x11/xorg server 7.3 hangs up f ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) f ports/118217 x11 xorg doesnt find usb mouse when initiated with devd, w o ports/118547 x11 [patch] x11/xdm fails with pam_krb5 o ports/118645 x11 Xorg need realtime priority for mouse work nice o ports/121230 x11 [patch] ports/x11/xkeyboard-config WITHOUT_NLS support o ports/123137 x11 x11/libX11: missing ru_RU.UTF-8 locale 14 problems total. From bugmaster at FreeBSD.org Mon Jun 16 11:08:45 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 16 11:09:21 2008 Subject: Current problem reports assigned to x11@FreeBSD.org Message-ID: <200806161108.m5GB8iZa038848@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/124220 x11 [amd64] x11-servers/xorg-server - X.org server runs in 1 problem total. Non-critical problems From callumgibson at optusnet.com.au Mon Jun 16 17:50:03 2008 From: callumgibson at optusnet.com.au (Callum Gibson) Date: Mon Jun 16 17:50:06 2008 Subject: ports/117907: x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) Message-ID: <200806161750.m5GHo32X003705@freefall.freebsd.org> The following reply was made to PR ports/117907; it has been noted by GNATS. From: Callum Gibson To: bug-followup@FreeBSD.org, josh@hewbert.com Cc: Subject: Re: ports/117907: x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) Date: Mon, 16 Jun 2008 17:53:37 +1000 flz wrote: >Can you try to do these: >- Simple rebuild the port, test. - Change XORG_VERSION to 7.0.0 in >Makefile, rebuild, test. - Add the following to /etc/libmap.conf, test. >[/usr/local/lib/xorg/modules/drivers/mga_drv.so] > libc.so.6 /compat/linux/lib/libc.so.6 There are a couple of reasons the above doesn't work. Firstly, you seem to need double '/' in the constraint. ie. [/usr/local/lib/xorg/modules/drivers//mga_drv.so] I determined this with ktrace. Having fixed that... Secondly, because Xorg is running setuid it will only allow trusted library paths (/lib, /usr/lib, /usr/local/lib). However, in order to get Xorg to use /compat/linux/lib/libc.so.6 you need to have it appear within the trusted library paths. I'm not sure, but I think this is compiled into the binary, but I was able to get around this by making a symlink thus: lrwxr-xr-x 1 root wheel 13 13 Jun 10:08 /usr/local/lib/compat/linux -> /compat/linux Having done this, though, I found that Xorg segfaulted upon initialisation of the mga_drv.so inside the linux libc in strrchr(). As a matter of interest I also compiled a native version of mga_drv.so using the source from matrox and using the linux mga_hal_drv.so with a slight tweak to the libmap.conf line as follows: [/usr/local/lib/xorg/modules/drivers//mga_hal_drv.so] libc.so.6 /compat/linux/lib/libc.so.6 but this segfaults in the same place, albeit upon loading the mag_hal_drv.so (as opposed to the mga_drv.so). I'm not sure why this is occurring - it doesn't seem to be code in the driver itself that is crashing but in the loading of the linux compat library. The stack trace is something like: strrchr() __init_misc() _init() dlsym ... I can get an exact one if anyone thinks it will help. In the meantime I'm looking at v1.9.100 of xf86-video-mga instead to see if it can be made to work (for a dual DVI G550). -- Callum Gibson @ home http://members.optusnet.com.au/callumgibson/ From jean-christophe_11 at orange.fr Mon Jun 16 18:37:31 2008 From: jean-christophe_11 at orange.fr (jean-christophe) Date: Mon Jun 16 18:37:36 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 Message-ID: <1213634501.6012.19.camel@Desktop.kusanagi.fr> hello, i would like know if a new version of radeonhd port is prevu. i read in the xorg wiki that the 3D support for my carte was bear with a latest version of radeonhd and there dependances. i am not enough any experiences in freebsd for modify him self the port. i am with freebsd-current and it isn't with the actualy version of radeonhd. i am waiting for install blender for working in my project. if not updating this port soon i must try to update him self but i am not your experience and i was need more time as you to get a fonctionnal port. thanks for your reply. best regard jean-christophe. From cokane at FreeBSD.org Mon Jun 16 18:56:17 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Mon Jun 16 18:56:24 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 In-Reply-To: <1213634501.6012.19.camel@Desktop.kusanagi.fr> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> Message-ID: <1213641854.2184.2.camel@localhost> On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: > hello, > > i would like know if a new version of radeonhd port is prevu. > > i read in the xorg wiki that the 3D support for my carte was bear with a > latest version of radeonhd and there dependances. > > i am not enough any experiences in freebsd for modify him self the port. > > i am with freebsd-current and it isn't with the actualy version of > radeonhd. > > i am waiting for install blender for working in my project. > > if not updating this port soon i must try to update him self but i am > not your experience and i was need more time as you to get a fonctionnal > port. > > thanks for your reply. > best regard > jean-christophe. Probably not until they release a new driver. However, I've just been following their git tree directly and that works pretty well for me. -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080616/66b71f4d/attachment.pgp From hartzell at alerce.com Mon Jun 16 19:29:50 2008 From: hartzell at alerce.com (George Hartzell) Date: Mon Jun 16 19:29:55 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 In-Reply-To: <1213641854.2184.2.camel@localhost> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> <1213641854.2184.2.camel@localhost> Message-ID: <18518.47720.619810.258288@almost.alerce.com> Coleman Kane writes: > On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: > > hello, > > > > i would like know if a new version of radeonhd port is prevu. > > [...] > > Probably not until they release a new driver. However, I've just been > following their git tree directly and that works pretty well for me. If you try to build from the git tree, you'll need to have devel/xorg-macros installed (wasn't obvious to me...). g. From r.c.ladan at gmail.com Mon Jun 16 19:52:32 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Jun 16 19:52:35 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 In-Reply-To: <1213641854.2184.2.camel@localhost> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> <1213641854.2184.2.camel@localhost> Message-ID: <4856BEB9.90303@gmail.com> Coleman Kane schreef: > On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: >> hello, >> >> i would like know if a new version of radeonhd port is prevu. >> >> i read in the xorg wiki that the 3D support for my carte was bear with a >> latest version of radeonhd and there dependances. >> >> i am not enough any experiences in freebsd for modify him self the port. >> >> i am with freebsd-current and it isn't with the actualy version of >> radeonhd. >> >> i am waiting for install blender for working in my project. >> >> if not updating this port soon i must try to update him self but i am >> not your experience and i was need more time as you to get a fonctionnal >> port. >> >> thanks for your reply. >> best regard >> jean-christophe. > > Probably not until they release a new driver. However, I've just been > following their git tree directly and that works pretty well for me. > ( omitting ports@ ) Works here too, except that I'm now getting a "drmRadeonCmdBuffer: -22" message when starting something which uses dri. I have these options in my 7.0R box: device vga options VESA device agp and I have drm and radeon loaded as module. Maybe some code is out of sync? Maybe that's also the cause of the black window syndrome? Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From cokane at FreeBSD.org Mon Jun 16 20:09:58 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Mon Jun 16 20:10:03 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 In-Reply-To: <4856BEB9.90303@gmail.com> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> <1213641854.2184.2.camel@localhost> <4856BEB9.90303@gmail.com> Message-ID: <1213646859.2184.11.camel@localhost> On Mon, 2008-06-16 at 21:27 +0200, Rene Ladan wrote: > Coleman Kane schreef: > > On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: > >> hello, > >> > >> i would like know if a new version of radeonhd port is prevu. > >> > >> i read in the xorg wiki that the 3D support for my carte was bear with a > >> latest version of radeonhd and there dependances. > >> > >> i am not enough any experiences in freebsd for modify him self the port. > >> > >> i am with freebsd-current and it isn't with the actualy version of > >> radeonhd. > >> > >> i am waiting for install blender for working in my project. > >> > >> if not updating this port soon i must try to update him self but i am > >> not your experience and i was need more time as you to get a fonctionnal > >> port. > >> > >> thanks for your reply. > >> best regard > >> jean-christophe. > > > > Probably not until they release a new driver. However, I've just been > > following their git tree directly and that works pretty well for me. > > > ( omitting ports@ ) > > Works here too, except that I'm now getting a "drmRadeonCmdBuffer: -22" > message when starting something which uses dri. I have these options in > my 7.0R box: > > device vga > options VESA > device agp > > and I have drm and radeon loaded as module. Maybe some code is out of sync? > Maybe that's also the cause of the black window syndrome? > > Regards, > Rene Oh, to be fair I've been using the "ati" driver instead of "radeonhd" for dri lately. I've been using "radeonhd" for 2D-only X sessions (since the ati driver sucks for 2D only). I cannot get radeonhd to actually do DRI properly for me (RS690), I just get a black window for glxgears, etc... -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080616/343c3daf/attachment.pgp From rgrover1 at gmail.com Mon Jun 16 20:52:14 2008 From: rgrover1 at gmail.com (Rohit Grover) Date: Mon Jun 16 20:52:18 2008 Subject: failing to start X on my Core 2 Duo macbook (No devices detected) Message-ID: <426bed110806161323q6b87766cs6ea3a23a5e61ece8@mail.gmail.com> Hello, I'm having trouble configuring Xorg on my Core 2 Duo Apple MacBook. I have followed instructions from a blog at http://goddess-gate.com/dc2/index.php/post/251 in installing Freebsd7.0 Release on it. I have rebuilt the kernel with the following added to the config: > device drm # Enable graphic acceleration (base support). > device i915drm # Enable graphic acceleration (i945GM support). > > The laptop has an Intel GMA965 X3100 chipset which shows up as Intel Mobile GMA965/GL960 using 'pciconf -lv' on pci channel 0:2:1. While running xorgconfig, I specified the use of "i810" (option 16) as the graphic controller--this was in accordance with the instructions from the blog above. The following is an excerpt from the blog which applies to my Xorg configuration: > Graphic card setup > > When you're asked if you want to parse graphic cards list, answer "y". > The graphic controller to use is "i810" (option 16). > Installed memory is "65536K" (option 9). > Identifier should be "GMA950" (I used GMA965). > Leave modes as is (answer "4"). > Default mode will be 24 bits (answer "5"). > Unfortunately, with this configuration, my X server doesn't start and gives the following error: > (EE) No devices detected. > Fatal server error: > no screens found > The FAQ from Xorg (http://www.x.org/wiki/FAQErrorMessages#head-93b1e0b56f76546d61364f789045e9c745b6cfd4) claims that: It is very likely that your xorg.conf file doesn't contain the > correct driver(s) for the chipset(s) in your system or that your > chipset isn't supported by any of the drivers. Could someone please help me with figuring out what drivers should I be using for my chipset? regards, From rsmith at xs4all.nl Mon Jun 16 21:23:52 2008 From: rsmith at xs4all.nl (Roland Smith) Date: Mon Jun 16 21:23:57 2008 Subject: failing to start X on my Core 2 Duo macbook (No devices detected) In-Reply-To: <426bed110806161323q6b87766cs6ea3a23a5e61ece8@mail.gmail.com> References: <426bed110806161323q6b87766cs6ea3a23a5e61ece8@mail.gmail.com> Message-ID: <20080616212349.GA20951@slackbox.xs4all.nl> On Tue, Jun 17, 2008 at 08:23:46AM +1200, Rohit Grover wrote: > Hello, > > I'm having trouble configuring Xorg on my Core 2 Duo Apple MacBook. > I have followed instructions from a blog at > http://goddess-gate.com/dc2/index.php/post/251 in installing Freebsd7.0 > Release on it. > I have rebuilt the kernel with the following added to the config: > > > device drm # Enable graphic acceleration (base support). > > device i915drm # Enable graphic acceleration (i945GM support). > > > > The laptop has an Intel GMA965 X3100 chipset which shows up as Intel Mobile > GMA965/GL960 using 'pciconf -lv' on pci channel 0:2:1. > While running xorgconfig, I specified the use of "i810" (option 16) as the > graphic controller--this was in accordance with the instructions from the > blog above. > Unfortunately, with this configuration, my X server doesn't start and gives > the following error: > > > (EE) No devices detected. > > Fatal server error: > > no screens found > Could someone please help me with figuring out what drivers should I be > using for my chipset? You probably need the xf86-video-intel driver. It has replaced the i810 driver. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080616/3d527467/attachment.pgp From adamk at voicenet.com Mon Jun 16 22:13:15 2008 From: adamk at voicenet.com (Adam K Kirchhoff) Date: Mon Jun 16 22:13:18 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 In-Reply-To: <1213641854.2184.2.camel@localhost> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> <1213641854.2184.2.camel@localhost> Message-ID: <20080616154617.1e5b8110.adamk@voicenet.com> On Mon, 16 Jun 2008 14:44:14 -0400 Coleman Kane wrote: > On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: > > hello, > > > > i would like know if a new version of radeonhd port is prevu. > > > > i read in the xorg wiki that the 3D support for my carte was bear > > with a latest version of radeonhd and there dependances. > > > > i am not enough any experiences in freebsd for modify him self the > > port. > > > > i am with freebsd-current and it isn't with the actualy version of > > radeonhd. > > > > i am waiting for install blender for working in my project. > > > > if not updating this port soon i must try to update him self but i > > am not your experience and i was need more time as you to get a > > fonctionnal port. > > > > thanks for your reply. > > best regard > > jean-christophe. > > Probably not until they release a new driver. However, I've just been > following their git tree directly and that works pretty well for me. Have you tried radeonhd vs. radeon? Last I heard, the radeonhd driver had issues with using 2D and 3D acceleration at the same time. I'm currently using the radeon driver with a PCIe x1800 and an AGP x1300 on two separate systems without any real issues thanks to Robert's great work. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From jeckermann at profitchannels.com.au Tue Jun 17 04:52:37 2008 From: jeckermann at profitchannels.com.au (Jeff Eckermann) Date: Tue Jun 17 04:52:42 2008 Subject: Failure in xorg-apps port install Message-ID: <148781.29245.qm@web34205.mail.mud.yahoo.com> Latter part of output following; package list following that. "config.log" attached. ===> Registering installation for xdpyinfo-1.0.2_1 ===> Returning to build of xorg-apps-7.3 ===> xorg-apps-7.3 depends on executable: xdriinfo - not found ===> Verifying reinstall for xdriinfo in /usr/ports/x11/xdriinfo ===> Vulnerability check disabled, database not found => xdriinfo-1.0.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/xorg/app. => Attempting to fetch from ftp://ftp.gwdg.de/pub/x11/x.org/pub/individual/app/. xdriinfo-1.0.2.tar.bz2 100% of 86 kB 36 kBps ===> Extracting for xdriinfo-1.0.2 => MD5 Checksum OK for xorg/app/xdriinfo-1.0.2.tar.bz2. => SHA256 Checksum OK for xorg/app/xdriinfo-1.0.2.tar.bz2. ===> Patching for xdriinfo-1.0.2 ===> xdriinfo-1.0.2 depends on file: /usr/local/libdata/pkgconfig/glproto.pc - found ===> xdriinfo-1.0.2 depends on file: /usr/local/libdata/pkgconfig/x11.pc - found ===> xdriinfo-1.0.2 depends on executable: pkg-config - found ===> xdriinfo-1.0.2 depends on shared library: GL.1 - found ===> Configuring for xdriinfo-1.0.2 configure: WARNING: you should use --build, --host, --target checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for i386-portbld-freebsd6.2-gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of cc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking return type of signal handlers... void checking for i386-portbld-freebsd6.2-pkg-config... no checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for XDRIINFO... yes checking for library containing glXGetProcAddressARB... no configure: error: cannot find GL library - make sure Mesa or other OpenGL package is installed See `config.log' for more details. ===> Script "configure" failed unexpectedly. Please report the problem to x11@FreeBSD.org [maintainer] and attach the "/usr/ports/x11/xdriinfo/work/xdriinfo-1.0.2/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/x11/xdriinfo. *** Error code 1 Stop in /usr/ports/x11/xdriinfo. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.78680.1 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=xorg-clients-6.9.0_3 UPGRADE_PORT_VER=6.9.0_3 make reinstall server# ls /var/db/pkg ImageMagick-6.4.1.1 hal-0.5.11_1 libiconv-1.11_1 pecl-APC-3.0.19 setxkbmap-1.0.4 apache-2.2.8 help2man-1.36.4_2 libltdl-1.5.24 pecl-filter-0.11.0 showfont-1.0.1_1 apache-ant-1.7.0_2 iceauth-1.0.2 libtool-1.5.26 pecl-hash-1.5 smproxy-1.0.2 appres-1.0.1 ico-1.0.2 libublio-20070103 pecl-json-1.2.1 tiff-3.8.2_1 autoconf-2.13.000227_6 imake-6.9.0 libvolume_id-0.81.0 perl-5.8.8_1 trapproto-3.4.3 autoconf-2.61_2 inputproto-1.4.2.1 libxkbfile-1.0.4 php5-5.2.6 twm-1.0.3_3 autoconf-wrapper-20071109 intltool-0.37.1 libxkbui-1.0.2_1 php5-ctype-5.2.6 unzip-5.52_5 automake-1.4.6_4 iso8879-1986_2 libxml2-2.6.32 php5-dom-5.2.6 videoproto-2.2.2 automake-wrapper-20071109 itext-2.1.0_1,1 libxslt-1.1.24 php5-gettext-5.2.6_1 viewres-1.0.1 bash-3.2.39_1 jakarta-commons-beanutils-1.7.0_2 linux_base-fc-4_13 php5-iconv-5.2.6 x11perf-1.4.1 bdftopcf-1.0.1 jakarta-commons-collections-3.2_2 listres-1.0.1 php5-mbstring-5.2.6 xalan-j-2.7.0_2 beforelight-1.0.2 jakarta-commons-digester-1.7_2 log4j-1.2.15_1 php5-mysql-5.2.6 xauth-1.0.2 bigreqsproto-1.0.2 jakarta-commons-logging-1.1_2 luit-1.0.2_2 php5-pcre-5.2.6 xbacklight-1.1 bitmap-1.0.3 jakarta-poi-2.5.1_2 m4-1.4.11,1 php5-pdo-5.2.6 xbiff-1.0.1 bitstream-vera-1.10_2 jasper-1.900.1_6 mediawiki-1.12.0_1 php5-pdo_sqlite-5.2.6 xbitmaps-1.0.1 bouncycastle-1.39_2 jasperreports-3.0.0_1 mkcomposecache-1.2_1 php5-posix-5.2.6 xcalc-1.0.2 bsdftpd-ssl-1.1.0_1 javavmwrapper-2.3.2 mkfontdir-1.0.3_1 php5-readline-5.2.6 xclipboard-1.0.1 compositeproto-0.4 jbigkit-1.6 mkfontscale-1.0.3 php5-session-5.2.6 xclock-1.0.3 consolekit-0.2.10_1 jcommon-1.0.12_1 mpeg2codec-1.2_3 php5-simplexml-5.2.6 xcmiscproto-1.1.2 cups-base-1.3.7_3 jfreechart-1.0.9_1 mysql-client-5.0.51a php5-spl-5.2.6 xcmsdb-1.0.1 cvsup-16.1h_2 jpeg-6b_4 mysql-connector-java-5.1.6_1 php5-sqlite-5.2.6 xconsole-1.0.3 damageproto-1.1.0_2 junit-4.4_1 mysql-server-5.0.51a php5-tokenizer-5.2.6 xcursorgen-1.0.2 db41-4.1.25_4 kbproto-1.0.3 oclock-1.0.1 php5-xml-5.2.6 xdbedizzy-1.0.2 dbus-1.2.1 lcms-1.17,1 openldap-client-2.3.42 php5-xmlreader-5.2.6 xditview-1.0.1 dbus-glib-0.74_1 libFS-1.0.0_1 p5-Archive-Tar-1.36 php5-xmlwriter-5.2.6 xdm-1.1.6_3 diablo-jdk-1.5.0.07.01_10 libICE-1.0.4_1,1 p5-CGI-Lite-2.02 php5-zlib-5.2.6 xdpyinfo-1.0.2_1 dmidecode-2.9 libSM-1.0.3_1,1 p5-CGI.pm-3.37_1,1 pixman-0.9.6 xerces-j-2.9.0_2 dmxproto-2.2.2 libX11-1.1.3_1,1 p5-Compress-Raw-Zlib-2.006 pkg-config-0.23_1 xextproto-7.0.2 docbook-4.1_3 libXScrnSaver-1.1.2 p5-Compress-Zlib-2.007 pkgdb.db xf86bigfontproto-1.1.2 docbook-xml-4.2_1 libXau-1.0.3_2 p5-DBI-1.60.4 png-1.2.28 xf86dgaproto-2.0.3 docbook-xsl-1.71.1_2 libXaw-1.0.4_1,1 p5-ExtUtils-CBuilder-0.19 policykit-0.8_2 xf86driproto-2.0.3 editres-1.0.3 libXcursor-1.1.9_1 p5-ExtUtils-ParseXS-2.18 popt-1.7_5 xf86miscproto-0.9.2 evieext-1.0.2 libXdmcp-1.0.2_1 p5-IO-Compress-Base-2.006 portupgrade-2.4.3_2,2 xf86vidmodeproto-2.2.2 expat-2.0.1 libXext-1.0.3,1 p5-IO-Compress-Zlib-2.006 postgresql-client-8.3.3 xfs-1.0.5_1,1 ezm3-1.2_1 libXfixes-4.0.3_1 p5-IO-String-1.08 postgresql-jdbc-8.3.603_1 xineramaproto-1.1.2 fixesproto-4.0 libXfont-1.3.1_3,1 p5-IO-Zlib-1.07 postgresql-plperl-8.3.1 xkeyboard-config-1.2_1 fontcacheproto-0.1.2 libXft-2.1.12 p5-IO-stringy-2.110 postgresql-server-8.3.3 xmlcatmgr-2.2 fontconfig-2.5.0,1 libXi-1.1.3,1 p5-MIME-Base64-3.07 printproto-1.0.3 xorg-clients-6.9.0_3 fontsproto-2.0.2 libXinerama-1.0.2,1 p5-Module-Build-0.28.08 python25-2.5.2_2 xorg-documents-6.9.0 fonttosfnt-1.0.3 libXmu-1.0.3,1 p5-OLE-Storage_Lite-0.14 randrproto-1.2.1 xorg-fonts-100dpi-6.9.0_1 freetype2-2.3.5 libXp-1.0.0,1 p5-Params-Util-0.30 recordproto-1.13.2 xorg-fonts-75dpi-6.9.0_1 fslsfonts-1.0.1 libXpm-3.5.7 p5-Parse-CSV-1.00 renderproto-0.9.3 xorg-fonts-cyrillic-6.9.0_1 fstobdf-1.0.2 libXprintUtil-1.0.1 p5-PathTools-3.25 resourceproto-1.0.2 xorg-fonts-encodings-6.9.0_1 fusefs-kmod-0.3.9.p1.20080208_1 libXrandr-1.2.2_1 p5-Scalar-List-Utils-1.19,1 rgb-1.0.1 xorg-fonts-miscbitmaps-6.9.0_1 fusefs-libs-2.7.2_1 libXrender-0.9.4_1 p5-Spiffy-0.30 rpm-3.0.6_14 xorg-fonts-truetype-6.9.0 fusefs-ntfs-1.2506 libXt-1.0.5_1 p5-Spreadsheet-ParseExcel-0.3200 rstart-1.0.2 xorg-fonts-type1-6.9.0 gamin-0.1.9_2 libXtst-1.0.3_1 p5-Storable-2.18 rsync-3.0.2_1 xorg-libraries-6.9.0 gettext-0.17_1 libXxf86dga-1.0.2 p5-Test-Base-0.54 ruby-1.8.6.111_2,1 xorg-nestserver-6.9.0_1 ghostscript-gpl-8.62_2 libXxf86misc-1.0.1 p5-Test-Harness-2.64 ruby18-bdb-0.6.2 xorg-server-1.4.2,1 gio-fam-backend-2.16.3_1 libXxf86vm-1.0.1 p5-Test-Simple-0.72 ruby18-deplate-0.8.1 xorg-vfbserver-6.9.0_2 glib-2.16.3_1 libdrm-2.3.0 p5-Text-CSV_XS-0.23 samba-3.0.28a_2,1 xproto-7.0.10_1 glproto-1.4.8 libexecinfo-1.1_1 p5-XML-Parser-2.36 screen-4.0.3_4 xterm-235 gmake-3.81_3 libfontenc-1.0.4 p5-YAML-0.65 scripts-1.0.1 xtrans-1.0.4 gnome_subr-1.0 libfpx-1.2.0.12_1 p5-gettext-1.05_2 scrnsaverproto-1.1.0 gnutls-2.2.5_1 libgcrypt-1.4.1_1 pciids-20080312 sdocbook-xml-1.1,1 gsfonts-8.11_4 libgpg-error-1.6_1 pcre-7.7 sessreg-1.0.3 Jeff Eckermann | Business Analyst Profitable Channels Management T 08 8231 9937 E jeckermann@profitchannels.com.auW http://www.profitchannels.com.auThis e-mail is from Profitable Channels Management. The contents are confidential and may be protected by legal professional privilege. -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log Type: application/octet-stream Size: 12037 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080617/b582cc9f/config.obj From jhein at timing.com Tue Jun 17 16:14:50 2008 From: jhein at timing.com (John E Hein) Date: Tue Jun 17 16:14:55 2008 Subject: Failure in xorg-apps port install In-Reply-To: <148781.29245.qm@web34205.mail.mud.yahoo.com> References: <148781.29245.qm@web34205.mail.mud.yahoo.com> Message-ID: <18519.56396.522753.171125@gromit.timing.com> Jeff Eckermann wrote at 21:25 -0700 on Jun 16, 2008: . . > ===> xdriinfo-1.0.2 depends on shared library: GL.1 - found > ===> Configuring for xdriinfo-1.0.2 . . > configure: error: cannot find GL library - make sure Mesa or other OpenGL package is installed > See `config.log' for more details. > ===> Script "configure" failed unexpectedly. > > server# ls /var/db/pkg [list in orig email omitted, but note there's no libGL listed] . . [from config.log ...] configure:3718: cc -o conftest -O2 -fno-strict-aliasing -pipe conftest.c -lGL -L/usr/local/lib -lX11 >&5 /usr/bin/ld: cannot find -lGL configure:3724: $? = 1 configure: failed program was: So the port can find _a_ libGL ('ldconfig -r | grep libGL'), but the configure script is looking specifically in /usr/local/lib. And there's no installed package that I saw in your list that might have libGL.*. Perhaps you updated from an old x install that was in /usr/X11R6 and there's still a libGL there and somehow you blew away the /var/db/pkg entry for that one? If so, remove (or move away) the old version in /usr/X11R6 and try to build again. From jonc at chen.org.nz Tue Jun 17 21:37:19 2008 From: jonc at chen.org.nz (Jonathan Chen) Date: Tue Jun 17 21:37:22 2008 Subject: xorg-server-1.4.2,1 and mouse buttons. Message-ID: <20080617212143.GA19438@osiris.chen.org.nz> Hi, I recently upgraded to xorg-server-1.4.2,1 and it looks like it's mangled my mouse button settings. I currently use a left-handed mouse orientation (set within GNOME), but this has been ignored since the xorg-server upgrade. Is anyone else seeing this? Cheers. -- Jonathan Chen ---------------------------------------------------------------------- "A person should be able to do a small bit of everything, specialisation is for insects" From lhecking at users.sourceforge.net Tue Jun 17 23:24:31 2008 From: lhecking at users.sourceforge.net (lhecking@users.sourceforge.net) Date: Tue Jun 17 23:24:35 2008 Subject: X pausing until mouse move - reprise Message-ID: <20080617230241.05E3A4E343@cork.irdesign.cypress.com> Apologies for boring everyone with an old thread, but after going over the March archive, I assumed this problem was fixed with patches to xorg and hal in ports. I updated ports yesterday, and the problem persists, even with moused disabled. Which I found out about 15min ago when I plugged in the USB mouse :-/ hal-0.5.11_1 hal-info-20080508_1hal-info-20080508_1 xorg-server-1.4.2,1 RELENG_7 ports-current Core2 Duo/NVidia/USB mouse/Gnome 2.22/hald/4BSD schduler From mezz7 at cox.net Wed Jun 18 05:44:14 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Wed Jun 18 05:44:17 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! Message-ID: Hello folks, First all, ahze did most of work. Thanks ahze! Yesterday, I am just merely pick up and help him. Right now, he is pretty busy with move to different state but he is still with this project when he can. It might be a bit long email as I am going to list each ports in subject and TODO tasks. Please add my email and gnome@ in CC, no matter what, that way my team and I can follow up better and quicker. Thanks! x11/pixman: Update to 0.10.0 ------------------------------------------------------- Firefox 3 needs it. Orignal, the shared library was bumped and ahze has added a new feature in our USE_GNOME=ltverhack by can control the number of shared library. To control the number of shared library, add the ltverhack:N. Right now pixman has USE_GNOME=ltverhack:9 to make it stays same at libpixman-1.so.9. If anyone want to use ltverhack:N in one of your port, you need to make sure the ABI doesn't change to use it. We will need more users to test to make sure it doesn't break any function in other ports that depend on pixman. I am running on it without change anything and it works great. ------------------------------------------------------- graphics/cairo: Update to 1.6.4 ------------------------------------------------------- Firefox 3 needs it. We have updated most cairo binding ports too. Let us know if we have missed some or cairo breaks your desktop/application. ------------------------------------------------------- graphics/poppler: Update to 0.8.3 ------------------------------------------------------- The shared library version has been changed. All ports that depend on poppler will have to be bump. We still need to bring more ports in MC ports-stable to test it. We don't have it all at the moment, but we will. The poppler-qt and poppler-qt4 still need to be work on. I don't have QT3/QT4 install right now, so it would be nice if one of you can help me. I will installing QT3/QT4 anyway, btw. KDE maintainers, please help to test on koffice-kde3 and kdegraphics3 when poppler-qt* are done as I don't know much about KDE. ------------------------------------------------------- www/firefox3: Update to 3.0 final ------------------------------------------------------- The bsd.gecko.mk has been moved from www/mozilla/ to Mk/. You no longer need to include bsd.gecko.mk/Makefile.common by manual. We still keep it in backward compatibility, so the rest ports won't be break. We haven't add some other ports to have Firefox 3 support yet, so if you want to add in your ports early then feel free to send me patch(es) and I shall add in MC ports-stable. ------------------------------------------------------- TODO tasks: ------------------------------------------------------- - Bring more ports that depend on poppler in ports-stable. - Need to update the document for bsd.gecko.mk (USE_GECKO). - Fix plist in firefox-devel, I hope to get it fix by tomorrow or so in this week. - Add firefox3 in some ports' USE_GECKO if these support, but it's safe to wait either. (no hurry) - Test and test. - Maybe more if there is any ------------------------------------------------------- How to use MC ports-stable and upgrade? ------------------------------------------------------- You can grab marcusmerge[1] and run 'marcusmerge -m ports-stable'. If you want to update your ports tree, you have to run cvsup, csup, portsnap or different method first then marcusmerge second at the everytime. If you want to unmerge your ports tree, you can run 'marcusmerge -U' and be sure to update your ports tree to bring ports back. Be sure to read in marcusmerge manpage[2] for more info. To upgrade your installed ports, you can just simple 'portmaster -a' or 'portupgrade -a'. While we don't have most ports that depend on poppler get bump yet, so be expect to get a bit problem in runtime at the moment. But it is easy to fix by rebuild/reinstall port. To downgrade, well you have to do it by manual. As for the MC ports (GNOME development) users, I have moved these ports from ports module to ports-stable module. You will need to run 'marcusmerge -U' first then update ports tree then MC ports-stable then at last MC ports. [1] http://www.marcuscom.com/downloads/marcusmerge [2] http://www.marcuscom.com/marcusmerge.8.html ------------------------------------------------------- With all of these changes, I want this to be tested in the pointyhat-exp first before merges into FreeBSD ports tree. The more help we get will get faster pointyhat-exp test and merge into FreeBSD ports tree. ;-) Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From tevans.uk at googlemail.com Wed Jun 18 12:07:49 2008 From: tevans.uk at googlemail.com (Tom Evans) Date: Wed Jun 18 12:07:54 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! In-Reply-To: References: Message-ID: <1213789329.10665.146.camel@localhost> On Wed, 2008-06-18 at 00:27 -0500, Jeremy Messenger wrote: > Hello folks, > > First all, ahze did most of work. Thanks ahze! Yesterday, I am just merely > pick up and help him. Right now, he is pretty busy with move to different > state but he is still with this project when he can. It might be a bit > long email as I am going to list each ports in subject and TODO tasks. > Please add my email and gnome@ in CC, no matter what, that way my team and > I can follow up better and quicker. Thanks! > > x11/pixman: Update to 0.10.0 > ------------------------------------------------------- > Firefox 3 needs it. Orignal, the shared library was bumped and ahze has > added a new feature in our USE_GNOME=ltverhack by can control the number > of shared library. To control the number of shared library, add the > ltverhack:N. Right now pixman has USE_GNOME=ltverhack:9 to make it stays > same at libpixman-1.so.9. If anyone want to use ltverhack:N in one of your > port, you need to make sure the ABI doesn't change to use it. We will need > more users to test to make sure it doesn't break any function in other > ports that depend on pixman. I am running on it without change anything > and it works great. > ------------------------------------------------------- > > graphics/cairo: Update to 1.6.4 > ------------------------------------------------------- > Firefox 3 needs it. We have updated most cairo binding ports too. Let us > know if we have missed some or cairo breaks your desktop/application. > ------------------------------------------------------- > > graphics/poppler: Update to 0.8.3 > ------------------------------------------------------- > The shared library version has been changed. All ports that depend on > poppler will have to be bump. We still need to bring more ports in MC > ports-stable to test it. We don't have it all at the moment, but we will. > The poppler-qt and poppler-qt4 still need to be work on. I don't have > QT3/QT4 install right now, so it would be nice if one of you can help me. > I will installing QT3/QT4 anyway, btw. KDE maintainers, please help to > test on koffice-kde3 and kdegraphics3 when poppler-qt* are done as I don't > know much about KDE. > ------------------------------------------------------- > > www/firefox3: Update to 3.0 final > ------------------------------------------------------- > The bsd.gecko.mk has been moved from www/mozilla/ to Mk/. You no longer > need to include bsd.gecko.mk/Makefile.common by manual. We still keep it > in backward compatibility, so the rest ports won't be break. We haven't > add some other ports to have Firefox 3 support yet, so if you want to add > in your ports early then feel free to send me patch(es) and I shall add in > MC ports-stable. > ------------------------------------------------------- > > TODO tasks: > ------------------------------------------------------- > - Bring more ports that depend on poppler in ports-stable. > - Need to update the document for bsd.gecko.mk (USE_GECKO). > - Fix plist in firefox-devel, I hope to get it fix by > tomorrow or so in this week. > - Add firefox3 in some ports' USE_GECKO if these support, > but it's safe to wait either. (no hurry) > - Test and test. > - Maybe more if there is any > ------------------------------------------------------- > > How to use MC ports-stable and upgrade? > ------------------------------------------------------- > You can grab marcusmerge[1] and run 'marcusmerge -m ports-stable'. If you > want to update your ports tree, you have to run cvsup, csup, portsnap or > different method first then marcusmerge second at the everytime. If you > want to unmerge your ports tree, you can run 'marcusmerge -U' and be sure > to update your ports tree to bring ports back. Be sure to read in > marcusmerge manpage[2] for more info. > > To upgrade your installed ports, you can just simple 'portmaster -a' or > 'portupgrade -a'. While we don't have most ports that depend on poppler > get bump yet, so be expect to get a bit problem in runtime at the moment. > But it is easy to fix by rebuild/reinstall port. To downgrade, well you > have to do it by manual. > > As for the MC ports (GNOME development) users, I have moved these ports > from ports module to ports-stable module. You will need to run > 'marcusmerge -U' first then update ports tree then MC ports-stable then at > last MC ports. > > [1] http://www.marcuscom.com/downloads/marcusmerge > [2] http://www.marcuscom.com/marcusmerge.8.html > ------------------------------------------------------- > > With all of these changes, I want this to be tested in the pointyhat-exp > first before merges into FreeBSD ports tree. The more help we get will get > faster pointyhat-exp test and merge into FreeBSD ports tree. ;-) > > Cheers, > Mezz Thanks Mezz One thing missing from this that I needed to get going is that the when the marcusmerge script checks out from cvs, you need to give the right cvs password - 'anoncvs'. I'll let you know how the actual ports go later. Cheers Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080618/2726f8c0/attachment.pgp From r.c.ladan at gmail.com Wed Jun 18 14:13:06 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Wed Jun 18 14:13:12 2008 Subject: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 In-Reply-To: <1213646859.2184.11.camel@localhost> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> <1213641854.2184.2.camel@localhost> <4856BEB9.90303@gmail.com> <1213646859.2184.11.camel@localhost> Message-ID: 2008/6/16 Coleman Kane : > On Mon, 2008-06-16 at 21:27 +0200, Rene Ladan wrote: >> Coleman Kane schreef: >> > On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: >> >> hello, >> >> >> >> i would like know if a new version of radeonhd port is prevu. >> >> >> >> i read in the xorg wiki that the 3D support for my carte was bear with a >> >> latest version of radeonhd and there dependances. >> >> >> >> i am not enough any experiences in freebsd for modify him self the port. >> >> >> >> i am with freebsd-current and it isn't with the actualy version of >> >> radeonhd. >> >> >> >> i am waiting for install blender for working in my project. >> >> >> >> if not updating this port soon i must try to update him self but i am >> >> not your experience and i was need more time as you to get a fonctionnal >> >> port. >> >> >> >> thanks for your reply. >> >> best regard >> >> jean-christophe. >> > >> > Probably not until they release a new driver. However, I've just been >> > following their git tree directly and that works pretty well for me. >> > >> ( omitting ports@ ) >> >> Works here too, except that I'm now getting a "drmRadeonCmdBuffer: -22" >> message when starting something which uses dri. I have these options in >> my 7.0R box: >> >> device vga >> options VESA >> device agp >> >> and I have drm and radeon loaded as module. Maybe some code is out of sync? >> Maybe that's also the cause of the black window syndrome? >> > Oh, to be fair I've been using the "ati" driver instead of "radeonhd" > for dri lately. I've been using "radeonhd" for 2D-only X sessions (since > the ati driver sucks for 2D only). I cannot get radeonhd to actually do > DRI properly for me (RS690), I just get a black window for glxgears, > etc... > I haven't tried the ati driver (yet), but if dri works with ati but not with radeonhd, then radeonhd is to blame (and not dri/mesa)? Also, I get this in dmesg: vgapci0: port 0xb000-0xb0ff mem 0xc0000000-0xcfffffff,0xfdff0000-0xfdffffff irq 16 at device 0.0 on pci1 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080528 ... vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ... info: [drm] Setting GART location based on new memory map info: [drm] GART aligned down from 0x00010000 to 0x00000000 info: [drm] Loading RS690 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] error: [drm:pid1212:r300_emit_carefully_checked_packet0] *ERROR* Register 208c failed check as flag=00 error: [drm:pid1212:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet0 failed ... info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] GART aligned down from 0x00010000 to 0x00000000 info: [drm] Loading RS690 Microcode <------ info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] Notice the line with the arrow, I actually have an M64-based card (X1450). Maybe the two error messages are causing the -22 error? The card id is 0x7186:0x1043:0x1231 (Asus A6JE) Xorg.0.log doesn't say anything noticeably wrong about dri. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From mezz7 at cox.net Wed Jun 18 16:01:16 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Wed Jun 18 16:01:40 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! In-Reply-To: References: Message-ID: On Wed, 18 Jun 2008 00:27:38 -0500, Jeremy Messenger wrote: > Hello folks, > > TODO tasks: > ------------------------------------------------------- > - Fix plist in firefox-devel, I hope to get it fix by > tomorrow or so in this week. s/firefox-devel/firefox3/g.. Anyway, it's fixed and committed. > ------------------------------------------------------- > > How to use MC ports-stable and upgrade? > ------------------------------------------------------- > You can grab marcusmerge[1] and run 'marcusmerge -m ports-stable'. If > you want to update your ports tree, you have to run cvsup, csup, > portsnap or different method first then marcusmerge second at the > everytime. If you want to unmerge your ports tree, you can run > 'marcusmerge -U' and be sure to update your ports tree to bring ports > back. Be sure to read in marcusmerge manpage[2] for more info. > > To upgrade your installed ports, you can just simple 'portmaster -a' or > 'portupgrade -a'. While we don't have most ports that depend on poppler > get bump yet, so be expect to get a bit problem in runtime at the > moment. But it is easy to fix by rebuild/reinstall port. To downgrade, > well you have to do it by manual. > > As for the MC ports (GNOME development) users, I have moved these ports > from ports module to ports-stable module. You will need to run > 'marcusmerge -U' first then update ports tree then MC ports-stable then > at last MC ports. Tom Evans has pointed that I have forgotten to point one more details. When you run marcusmerge and it will asking for CVS password. The CVS password is 'anoncvs' (w/out quote). You can see more details at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/ .. Thanks Tom! Cheers, Mezz > [1] http://www.marcuscom.com/downloads/marcusmerge > [2] http://www.marcuscom.com/marcusmerge.8.html > ------------------------------------------------------- > > With all of these changes, I want this to be tested in the pointyhat-exp > first before merges into FreeBSD ports tree. The more help we get will > get faster pointyhat-exp test and merge into FreeBSD ports tree. ;-) > > Cheers, > Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From chess at chessgriffin.com Wed Jun 18 18:43:37 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Wed Jun 18 18:43:39 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! In-Reply-To: References: Message-ID: <485953A6.2010304@chessgriffin.com> Jeremy Messenger wrote: > > With all of these changes, I want this to be tested in the pointyhat-exp > first before merges into FreeBSD ports tree. The more help we get will > get faster pointyhat-exp test and merge into FreeBSD ports tree. ;-) > > Cheers, > Mezz > Hi- I just created a new tinderbox build using 7-STABLE and the marcuscom ports-stable tree and started up a www/firefox3 build. Everything that got pulled in (approx 74 ports) built ok, but Firefox3 failed with what appears to be a dbus/gnome-config configure error. This is at the end of the log: > checking for pango >= 1.10.0 pangocairo >= 1.10.0 pangoft2 >= 1.10.0... yes > checking MOZ_PANGO_CFLAGS... -D_THREAD_SAFE -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/pixman-1 > checking MOZ_PANGO_LIBS... -pthread -L/usr/local/lib -lpangocairo-1.0 -lcairo -lpangoft2-1.0 -lpango-1.0 -lm -lfreetype -lz -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -liconv > checking for gnome-vfs-2.0 >= 2.0 gnome-vfs-module-2.0 >= 2.0... gnome-config: not found > gnome-config: not found > gnome-config: not found > gnome-config: not found > checking for gconf-2.0 >= 1.2.1... gnome-config: not found > gnome-config: not found > checking for libgnome-2.0 >= 2.0... gnome-config: not found > gnome-config: not found > checking for libgnomeui-2.0 >= 2.2.0... gnome-config: not found > gnome-config: not found > checking for dbus-glib-1 >= 0.60... gnome-config: not found > gnome-config: not found > Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' found > configure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. > ===> Script "configure" failed unexpectedly. > Please run the gnomelogalyzer, available from > "http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the > problem and suggest a solution. If - and only if - the gnomelogalyzer cannot > solve the problem, report the build failure to the FreeBSD GNOME team at > gnome@FreeBSD.org, and attach (a) > "/work/a/ports/www/firefox3/work/mozilla/config.log", (b) the output of the > failed make command, and (c) the gnomelogalyzer output. Also, it might be a > good idea to provide an overview of all packages installed on your system > (i.e. an `ls /var/db/pkg`). Put your attachment up on any website, > copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with > the attachment. Try to avoid sending any attachments to the mailing list > (gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists are > usually discarded by the mailing list software. > *** Error code 1 > > Stop in /a/ports/www/firefox3. > ================================================================ > build of /usr/ports/www/firefox3 ended at Wed Jun 18 18:23:50 UTC 2008 -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080618/9b4cd762/signature.pgp From cyberbotx at cyberbotx.com Wed Jun 18 20:55:49 2008 From: cyberbotx at cyberbotx.com (Naram Qashat) Date: Wed Jun 18 20:55:52 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! In-Reply-To: References: Message-ID: <48597287.2040907@cyberbotx.com> Jeremy Messenger wrote: > Hello folks, > > First all, ahze did most of work. Thanks ahze! Yesterday, I am just > merely pick up and help him. Right now, he is pretty busy with move to > different state but he is still with this project when he can. It might > be a bit long email as I am going to list each ports in subject and TODO > tasks. Please add my email and gnome@ in CC, no matter what, that way my > team and I can follow up better and quicker. Thanks! > > x11/pixman: Update to 0.10.0 > ------------------------------------------------------- > Firefox 3 needs it. Orignal, the shared library was bumped and ahze has > added a new feature in our USE_GNOME=ltverhack by can control the number > of shared library. To control the number of shared library, add the > ltverhack:N. Right now pixman has USE_GNOME=ltverhack:9 to make it stays > same at libpixman-1.so.9. If anyone want to use ltverhack:N in one of > your port, you need to make sure the ABI doesn't change to use it. We > will need more users to test to make sure it doesn't break any function > in other ports that depend on pixman. I am running on it without change > anything and it works great. > ------------------------------------------------------- > > graphics/cairo: Update to 1.6.4 > ------------------------------------------------------- > Firefox 3 needs it. We have updated most cairo binding ports too. Let us > know if we have missed some or cairo breaks your desktop/application. > ------------------------------------------------------- > > graphics/poppler: Update to 0.8.3 > ------------------------------------------------------- > The shared library version has been changed. All ports that depend on > poppler will have to be bump. We still need to bring more ports in MC > ports-stable to test it. We don't have it all at the moment, but we > will. The poppler-qt and poppler-qt4 still need to be work on. I don't > have QT3/QT4 install right now, so it would be nice if one of you can > help me. I will installing QT3/QT4 anyway, btw. KDE maintainers, please > help to test on koffice-kde3 and kdegraphics3 when poppler-qt* are done > as I don't know much about KDE. > ------------------------------------------------------- > > www/firefox3: Update to 3.0 final > ------------------------------------------------------- > The bsd.gecko.mk has been moved from www/mozilla/ to Mk/. You no longer > need to include bsd.gecko.mk/Makefile.common by manual. We still keep it > in backward compatibility, so the rest ports won't be break. We haven't > add some other ports to have Firefox 3 support yet, so if you want to > add in your ports early then feel free to send me patch(es) and I shall > add in MC ports-stable. > ------------------------------------------------------- Well, I tried to build Firefox 3 after updating all the other ports, it gets to this point and fails: c++ -o nsBlockFrame.o -c -I../../dist/include/system_wrappers -include ../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API -D_IMPL_NS_COM_OBSOLETE -D_IMPL_NS_GFX -D_IMPL_NS_WIDGET -DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES -DOSTYPE=\"FreeBSD7\" -DOSARCH=FreeBSD -D_IMPL_NS_LAYOUT -I. -I./../base -I./../forms -I./../tables -I./../xul/base/src -I./../../content/xul/content/src -I./../../content/base/src -I./../../content/html/content/src -I./../../dom/src/base -D_THREAD_SAFE -I/usr/local/include/cairo -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/pixman-1 -D_THREAD_SAFE -I/usr/local/include/cairo -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include/pixman-1 -I. -I. -I../../dist/include/xpcom -I../../dist/include/string -I../../dist/include/dom -I../../dist/include/content -I../../dist/include/thebes -I../../dist/include/gfx -I../../dist/include/widget -I../../dist/include/locale -I../../dist/include/view -I../../dist/include/necko -I../../dist/include/js -I../../dist/include/caps -I../../dist/include/pref -I../../dist/include/htmlparser -I../../dist/include/webshell -I../../dist/include/plugin -I../../dist/include/docshell -I../../dist/include/webbrwsr -I../../dist/include/oji -I../../dist/include/unicharutil -I../../dist/include/lwbrk -I../../dist/include/imglib2 -I../../dist/include/xpconnect -I../../dist/include/java -I../../dist/include/intl -I../../dist/include/thebes -I../../dist/include/cairo -I../../dist/include/accessibility -I../../dist/include -I../../dist/include/layout -I/usr/local/include/nspr -I/usr/local/include -I/usr/include -I../../dist/sdk/include -I/usr/local/include -fPIC -I/usr/local/include -I/usr/local/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-long-long -O -pipe -O2 -fno-strict-aliasing -O2 -fno-strict-aliasing -fshort-wchar -pipe -DNDEBUG -DTRIMMED -O2 -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/freetype2 -I/usr/local/include/pixman-1 -I/usr/local/include/gtk-unix-print-2.0 -I/usr/local/include -I/usr/local/include -DMOZILLA_CLIENT -include ../../mozilla-config.h nsBlockFrame.cpp In file included from ../../dist/include/content/nsContentUtils.h:46, from ./../../content/base/src/nsGenericElement.h:59, from ./../../content/base/src/nsStyledElement.h:50, from ./../../content/base/src/nsMappedAttributeElement.h:48, from ./../../content/html/content/src/nsGenericHTMLElement.h:41, from nsBlockFrame.cpp:69: ../../dist/include/js/jsnum.h:150: warning: 'js_TraceRuntimeNumberState' initialized and declared 'extern' ../../dist/include/js/jsnum.h:150: error: variable or field 'js_TraceRuntimeNumberState' declared void ../../dist/include/js/jsnum.h:150: error: 'JSTracer' was not declared in this scope ../../dist/include/js/jsnum.h:150: error: 'trc' was not declared in this scope nsBlockFrame.cpp: In member function 'PRBool nsBlockFrame::HandleOverflowPlaceholdersOnPulledLine(nsBlockReflowState&, nsLineBox*)': nsBlockFrame.cpp:4268: warning: unused variable 'taken' nsBlockFrame.cpp: In member function 'void nsBlockFrame::SetOverflowOutOfFlows(const nsFrameList&)': nsBlockFrame.cpp:4620: warning: unused variable 'result' nsBlockFrame.cpp: In member function 'virtual void nsBlockFrame::DeleteNextInFlowChild(nsPresContext*, nsIFrame*)': nsBlockFrame.cpp:5601: warning: unused variable 'prevInFlow' gmake[4]: *** [nsBlockFrame.o] Error 1 gmake[4]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/layout/generic' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/layout' gmake[2]: *** [libs_tier_gecko] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox3/work/mozilla' gmake[1]: *** [tier_gecko] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox3/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox3. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.39797.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=firefox-2.0.0.14_1,1 UPGRADE_PORT_VER=2.0.0.14_1,1 make BATCH=yes WITH_OPENSSL_PORT=yes WITH_OPENSSL=yes WITHOUT_GNOME=esound WITHOUT_CUPS=yes WITH_BDB_VER=46 WITH_MYSQL_VER=50 WITH_OPTIMIZED_CFLAGS=yes WITH_SMB=yes DISABLE_VULNERABILITIES=yes ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/firefox3 (firefox-2.0.0.14_1,1) (new compiler error) Thanks, Naram Qashat > TODO tasks: > ------------------------------------------------------- > - Bring more ports that depend on poppler in ports-stable. > - Need to update the document for bsd.gecko.mk (USE_GECKO). > - Fix plist in firefox-devel, I hope to get it fix by > tomorrow or so in this week. > - Add firefox3 in some ports' USE_GECKO if these support, > but it's safe to wait either. (no hurry) > - Test and test. > - Maybe more if there is any > ------------------------------------------------------- > > How to use MC ports-stable and upgrade? > ------------------------------------------------------- > You can grab marcusmerge[1] and run 'marcusmerge -m ports-stable'. If > you want to update your ports tree, you have to run cvsup, csup, > portsnap or different method first then marcusmerge second at the > everytime. If you want to unmerge your ports tree, you can run > 'marcusmerge -U' and be sure to update your ports tree to bring ports > back. Be sure to read in marcusmerge manpage[2] for more info. > > To upgrade your installed ports, you can just simple 'portmaster -a' or > 'portupgrade -a'. While we don't have most ports that depend on poppler > get bump yet, so be expect to get a bit problem in runtime at the > moment. But it is easy to fix by rebuild/reinstall port. To downgrade, > well you have to do it by manual. > > As for the MC ports (GNOME development) users, I have moved these ports > from ports module to ports-stable module. You will need to run > 'marcusmerge -U' first then update ports tree then MC ports-stable then > at last MC ports. > > [1] http://www.marcuscom.com/downloads/marcusmerge > [2] http://www.marcuscom.com/marcusmerge.8.html > ------------------------------------------------------- > > With all of these changes, I want this to be tested in the pointyhat-exp > first before merges into FreeBSD ports tree. The more help we get will > get faster pointyhat-exp test and merge into FreeBSD ports tree. ;-) > > Cheers, > Mezz From linimon at FreeBSD.org Wed Jun 18 22:24:12 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Jun 18 22:24:17 2008 Subject: FreeBSD ports that you maintain which are currently scheduled for deletion Message-ID: <20080618222411.AC07B1CCCD@mail.droso.net> Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: x11-servers/xorg-server-snap description: X.Org X server and related programs maintainer: x11@FreeBSD.org status: IGNORE deprecated because: Port hasn't been used since the switch to modular releases expiration date: 2008-06-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-servers&portname=xorg-server-snap If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD. From rgrover1 at gmail.com Wed Jun 18 23:15:54 2008 From: rgrover1 at gmail.com (Rohit Grover) Date: Wed Jun 18 23:15:58 2008 Subject: failing to start X on my Core 2 Duo macbook (No devices detected) In-Reply-To: <20080616212349.GA20951@slackbox.xs4all.nl> References: <426bed110806161323q6b87766cs6ea3a23a5e61ece8@mail.gmail.com> <20080616212349.GA20951@slackbox.xs4all.nl> Message-ID: <426bed110806181615g217409c9hb36868edea7aa093@mail.gmail.com> On Tue, Jun 17, 2008 at 9:23 AM, Roland Smith wrote: > On Tue, Jun 17, 2008 at 08:23:46AM +1200, Rohit Grover wrote: > > Hello, > > > > I'm having trouble configuring Xorg on my Core 2 Duo Apple MacBook. > > > Could someone please help me with figuring out what drivers should I be > > using for my chipset? > > You probably need the xf86-video-intel driver. It has replaced the i810 > driver. > Yes, thanks for that, the xf86-video-intel driver worked. I can now start X. Now I am having trouble getting X to recognize my laptop's trackpad. I have specified /dev/ums0 as my mouse, but X doesn't work with either the trackpad or an external USB mouse. I have tried /dev/ums1, /dev/ukbd1, and a few others based on the mouse-like devices whose drivers emit messages on the console at boot time, but still no luck. Could someone please help? thanks, From rgrover1 at gmail.com Thu Jun 19 01:29:32 2008 From: rgrover1 at gmail.com (Rohit Grover) Date: Thu Jun 19 01:29:34 2008 Subject: Unable to get the trackpad on my Macbook Core2 Duo to work Message-ID: <426bed110806181829l5f766fd6k754c18edb1b7f6eb@mail.gmail.com> Hello, I'm having trouble configuring Xorg on my Core 2 Duo Apple MacBook. I have followed instructions from a blog at http://goddess-gate.com/dc2/index.php/post/251 in installing Freebsd7.0 Release on it, and configuring X. I am using the xf86-video-intel driver instead of the original i810, and X starts alright. Unfortunately, the trackpad doesn't work. Neither does an external USB mouse. I have referred to the following instructions (excerpted from the blog above) in configuring X, but to no avail. > > Mouse setup > > You will have to use "Auto" mouse protocol. As the trackpad doesn't work > well (instable mouse pointer, absolute positionning between display and > trackpad surface), you have to use an USB mouse. > When you're asked if you want to emulate 3 buttons, answer "n". > When you're asked which device to use, you may have to answer "/dev/ums0". > Adapt to your real needs. > Could someone please help me out with the trackpad/mouse for my Macbook? thanks. regards, From avg at icyb.net.ua Thu Jun 19 11:36:31 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Jun 19 11:36:34 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 Message-ID: <485A3EE1.8070601@icyb.net.ua> Maybe this is related to some other port but I strongly believe that this happened after I upgraded to xorg-server-1.4.2,1. I have very customized xkb configuration where Caps Lock key is used as layout switch key and Pause/Break is used for original Caps Lock functions. I use this configuration for quite a while and everything used to be ok. After the upgrade the keys continue to work as expected. The only issue is that now both Caps Lock and Pause/Break affect state of Caps Lock LED. And this is quite annoying. I want to report this issue here first, maybe someone would have an advice for me what and where to check. However I guess that this is an upstream issue. Here's relevant snippets from my XKB config: partial modifier_keys xkb_symbols "multi_scrl_caps" { ... replace key { type="ONE_LEVEL", [ Caps_Lock ], actions= [ LockMods(modifiers=Lock) ] }; replace key { type="ONE_LEVEL", [ Caps_Lock ], actions= [ LockMods(modifiers=Lock) ] }; ... replace modifier_map Lock { Caps_Lock }; }; ... partial modifier_keys xkb_symbols "caps" { replace key { type = "CTRL+SHIFT", // Base, Ctrl, Shift symbols[Group1] = [ NoSymbol, NoSymbol, NoSymbol ], symbols[Group2] = [ NoSymbol, NoSymbol, NoSymbol ], symbols[Group3] = [ NoSymbol, NoSymbol, NoSymbol ], actions[Group1] = [ NoAction(), LockGroup(group=+1), LockGroup(group=+2) ], actions[Group2] = [ SetGroup(group=+2), LockGroup(group=+1), LockGroup(group=+2) ], actions[Group3] = [ SetGroup(group=+1), LockGroup(group=+1), LockGroup(group=+2) ] }; }; -- Andriy Gapon From onemda at gmail.com Thu Jun 19 14:06:29 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Jun 19 14:06:33 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <485A3EE1.8070601@icyb.net.ua> References: <485A3EE1.8070601@icyb.net.ua> Message-ID: <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> It is upstream issue/regression. I liked how it was before ... but Xorg devs have different opinion. From avg at icyb.net.ua Thu Jun 19 14:14:57 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Jun 19 14:15:03 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> References: <485A3EE1.8070601@icyb.net.ua> <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> Message-ID: <485A69DD.4000308@icyb.net.ua> on 19/06/2008 16:37 Paul B. Mahol said the following: > It is upstream issue/regression. I liked how it was before ... but > Xorg devs have different opinion. Could you please expand a little bit on this? particular commit or discussion or something? BTW, what's strange too is that if I use xkbvleds then it reflects Caps Lock LED changes caused by "new"/remapped Caps Lock button but it doesn't respond to the "old"/normal Caps Lock button. But physical LED responds to both. -- Andriy Gapon From onemda at gmail.com Thu Jun 19 16:08:11 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Jun 19 16:08:14 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <485A69DD.4000308@icyb.net.ua> References: <485A3EE1.8070601@icyb.net.ua> <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> <485A69DD.4000308@icyb.net.ua> Message-ID: <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com> On 6/19/08, Andriy Gapon wrote: > on 19/06/2008 16:37 Paul B. Mahol said the following: >> It is upstream issue/regression. I liked how it was before ... but >> Xorg devs have different opinion. > > Could you please expand a little bit on this? particular commit or > discussion or something? > xset led {1-32} doesnt work any more as it was before (only Scroll Lock LED can be turned on/off). I guess it was caused by new version of xf86-input drivers, I never found issue so imortant to fix it myself. > BTW, what's strange too is that if I use xkbvleds then it reflects Caps > Lock LED changes caused by "new"/remapped Caps Lock button but it > doesn't respond to the "old"/normal Caps Lock button. But physical LED > responds to both. > > -- > Andriy Gapon > From oberman at es.net Thu Jun 19 16:10:12 2008 From: oberman at es.net (Kevin Oberman) Date: Thu Jun 19 16:10:17 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: Your message of "Thu, 19 Jun 2008 15:37:18 +0200." <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> Message-ID: <20080619155823.5F37E4500E@ptavv.es.net> > Date: Thu, 19 Jun 2008 15:37:18 +0200 > From: "Paul B. Mahol" > Sender: owner-freebsd-x11@freebsd.org > > It is upstream issue/regression. I liked how it was before ... but > Xorg devs have different opinion. Hmm. They have the opinion that busted is good? This has been annoying for a while. I swap CapsLock with LeftCtrl. I have done this ever since Microsoft decided to "hide" it down below the shift key. It has always worked fine, but it "broke" with xorg 7.2 (or maybe 7.3). Now, to get ALT+CTRL to work, I need to press ALT first and then CTRL, which is not my natural tendancy. It's very annoying. I have confirmed with xev that all of the press/release events are proper, so it's something in the processing of the events that is foobar. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080619/1aec6348/attachment.pgp From onemda at gmail.com Thu Jun 19 16:16:36 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Jun 19 16:16:41 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <20080619155823.5F37E4500E@ptavv.es.net> References: <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> <20080619155823.5F37E4500E@ptavv.es.net> Message-ID: <3a142e750806190916q3763939yb23bd80c2e649f8f@mail.gmail.com> On 6/19/08, Kevin Oberman wrote: >> Date: Thu, 19 Jun 2008 15:37:18 +0200 >> From: "Paul B. Mahol" >> Sender: owner-freebsd-x11@freebsd.org >> >> It is upstream issue/regression. I liked how it was before ... but >> Xorg devs have different opinion. > > Hmm. They have the opinion that busted is good? I'm not sure that they really busted it for ever. (but I got such opinion) Better to ask them directly. > This has been annoying for a while. I swap CapsLock with LeftCtrl. I > have done this ever since Microsoft decided to "hide" it down below the > shift key. It has always worked fine, but it "broke" with xorg 7.2 > (or maybe 7.3). Now, to get ALT+CTRL to work, I need to press ALT first > and then CTRL, which is not my natural tendancy. It's very annoying. > > I have confirmed with xev that all of the press/release events are > proper, so it's something in the processing of the events that is > foobar. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > From avg at icyb.net.ua Thu Jun 19 17:39:49 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Jun 19 17:39:52 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <20080619155823.5F37E4500E@ptavv.es.net> References: <20080619155823.5F37E4500E@ptavv.es.net> Message-ID: <485A99E1.6080604@icyb.net.ua> on 19/06/2008 18:58 Kevin Oberman said the following: >> Date: Thu, 19 Jun 2008 15:37:18 +0200 >> From: "Paul B. Mahol" >> Sender: owner-freebsd-x11@freebsd.org >> >> It is upstream issue/regression. I liked how it was before ... but >> Xorg devs have different opinion. > > Hmm. They have the opinion that busted is good? > > This has been annoying for a while. I swap CapsLock with LeftCtrl. I > have done this ever since Microsoft decided to "hide" it down below the > shift key. It has always worked fine, but it "broke" with xorg 7.2 > (or maybe 7.3). Now, to get ALT+CTRL to work, I need to press ALT first > and then CTRL, which is not my natural tendancy. It's very annoying. > > I have confirmed with xev that all of the press/release events are > proper, so it's something in the processing of the events that is > foobar. I think that this is a result of how XKB works. After you swapped CAPS and LCTL the latter stopped being a modifier key, so when it is pressed "CTRL" modifier flag is not set and there is no magic about CTRL+ALT. On the other hand ALT is still a modifier key, so ALT+CTRL can still be magic. I think that you can still make CTRL+ALT work through some configuration hackery for ALT key. And pressing CAPS+ALT should work right now (because CAPS now sets the modifier flag). What can not be changed, and you are completely correct here, is that a key a press has an effect on XKB state as soon as it is pressed. Only previous key presses can affect current key press, but current key press can not wait for future key presses. So for XKB ALT+CTRL and CTRL+ALT are always different sequences, but "normally" they can be made to have the same effect. E.g. see /usr/local/share/X11/xkb/symbols/group: partial modifier_keys xkb_symbols "ctrl_alt_toggle" { virtual_modifiers Alt; key { type[Group1]="PC_CONTROL_LEVEL2", symbols[Group1]= [ NoSymbol, ISO_Prev_Group ], virtualMods= Alt }; key { type[Group1]="PC_CONTROL_LEVEL2", symbols[Group1]= [ NoSymbol, ISO_Next_Group ], virtualMods= Alt }; key { type[Group1]="PC_ALT_LEVEL2", symbols[Group1]= [ Control_L, ISO_Prev_Group ] }; key { type[Group1]="PC_ALT_LEVEL2", symbols[Group1]= [ Control_R, ISO_Next_Group ] }; }; First two "key" clauses define what happens when ALTs are pressed while CTRL modifier is in effect, two others define the opposite situation. In any case, this does not seem to be related to my original report. -- Andriy Gapon From avg at icyb.net.ua Thu Jun 19 18:05:31 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Jun 19 18:05:34 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com> References: <485A3EE1.8070601@icyb.net.ua> <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> <485A69DD.4000308@icyb.net.ua> <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com> Message-ID: <485A9437.6020305@icyb.net.ua> on 19/06/2008 19:08 Paul B. Mahol said the following: > On 6/19/08, Andriy Gapon wrote: >> on 19/06/2008 16:37 Paul B. Mahol said the following: >>> It is upstream issue/regression. I liked how it was before ... but >>> Xorg devs have different opinion. >> Could you please expand a little bit on this? particular commit or >> discussion or something? >> > > xset led {1-32} doesnt work any more as it was before (only Scroll > Lock LED can be turned on/off). > > I guess it was caused by new version of xf86-input drivers, I never > found issue so imortant to fix it myself. I don't think that this is related to my issue. In fact, I think that what you described is controlled by xkeyboard-config settings. In /usr/local/share/X11/xkb/compat/led* allowExplicit is set only for Scroll Lock, Num Lock and Caps Lock have !allowExplicit. That means that X applications can not directly change them, which is exactly what you describe. This is still configurable, but not in a convenient way though. >> BTW, what's strange too is that if I use xkbvleds then it reflects Caps >> Lock LED changes caused by "new"/remapped Caps Lock button but it >> doesn't respond to the "old"/normal Caps Lock button. But physical LED >> responds to both. >> >> -- >> Andriy Gapon >> -- Andriy Gapon From avg at icyb.net.ua Thu Jun 19 18:06:16 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Jun 19 18:06:18 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <485A3EE1.8070601@icyb.net.ua> References: <485A3EE1.8070601@icyb.net.ua> Message-ID: <485AA016.9050203@icyb.net.ua> on 19/06/2008 14:11 Andriy Gapon said the following: > Maybe this is related to some other port but I strongly believe that > this happened after I upgraded to xorg-server-1.4.2,1. > > I have very customized xkb configuration where Caps Lock key is used as > layout switch key and Pause/Break is used for original Caps Lock > functions. I use this configuration for quite a while and everything > used to be ok. > > After the upgrade the keys continue to work as expected. The only issue > is that now both Caps Lock and Pause/Break affect state of Caps Lock > LED. And this is quite annoying. > > I want to report this issue here first, maybe someone would have an > advice for me what and where to check. However I guess that this is an > upstream issue. And by the way, commit message for update of x11-servers/xorg-server to 1.4.2 is quite misleading. It says that it is just a security update. But in fact 1.4.1=>1.4.2 change is a security update and our port used to have version 1.4[.0], and there were some larger functionality changes between 1.4=>1.4.0.90=>1.4.1 which the port didn't get before. -- Andriy Gapon From avg at icyb.net.ua Thu Jun 19 18:06:58 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Jun 19 18:07:00 2008 Subject: capslock led after upgrade to xorg-server-1.4.2,1 In-Reply-To: <485AA016.9050203@icyb.net.ua> References: <485A3EE1.8070601@icyb.net.ua> <485AA016.9050203@icyb.net.ua> Message-ID: <485AA040.3000706@icyb.net.ua> on 19/06/2008 21:06 Andriy Gapon said the following: > on 19/06/2008 14:11 Andriy Gapon said the following: >> Maybe this is related to some other port but I strongly believe that >> this happened after I upgraded to xorg-server-1.4.2,1. >> >> I have very customized xkb configuration where Caps Lock key is used as >> layout switch key and Pause/Break is used for original Caps Lock >> functions. I use this configuration for quite a while and everything >> used to be ok. >> >> After the upgrade the keys continue to work as expected. The only issue >> is that now both Caps Lock and Pause/Break affect state of Caps Lock >> LED. And this is quite annoying. >> >> I want to report this issue here first, maybe someone would have an >> advice for me what and where to check. However I guess that this is an >> upstream issue. > > And by the way, commit message for update of x11-servers/xorg-server to > 1.4.2 is quite misleading. It says that it is just a security update. > But in fact 1.4.1=>1.4.2 change is a security update and our port used > to have version 1.4[.0], and there were some larger functionality > changes between 1.4=>1.4.0.90=>1.4.1 which the port didn't get before. For convenience: http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=shortlog;h=server-1.4-branch;pg=0 -- Andriy Gapon From mezz7 at cox.net Fri Jun 20 17:53:44 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Fri Jun 20 17:53:53 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! In-Reply-To: References: Message-ID: On Wed, 18 Jun 2008 00:27:38 -0500, Jeremy Messenger wrote: > Hello folks, > graphics/poppler: Update to 0.8.3 > ------------------------------------------------------- > The shared library version has been changed. All ports that depend on > poppler will have to be bump. We still need to bring more ports in MC > ports-stable to test it. We don't have it all at the moment, but we > will. The poppler-qt and poppler-qt4 still need to be work on. I don't > have QT3/QT4 install right now, so it would be nice if one of you can > help me. I will installing QT3/QT4 anyway, btw. KDE maintainers, please > help to test on koffice-kde3 and kdegraphics3 when poppler-qt* are done > as I don't know much about KDE. > ------------------------------------------------------- Just a FYI, I have finished with all poppler stuff. If I have missed anything, just let me know. It looks like there is no change and no bump in poppler-qt, so it's nothing hurt for ports that depend on poppler-qt (KDE maintainer, you don't have to worry about it anymore ;-)). As for the poppler-qt4, I have fixed the build and it does change shared library. Lucky, there is no ports that depend on poppler-qt4 as far I know. > TODO tasks: > ------------------------------------------------------- > - Need to update the document for bsd.gecko.mk (USE_GECKO). > - Add firefox3 in some ports' USE_GECKO if these support, > but it's safe to wait either. (no hurry) > - Test and test. > - Maybe more if there is any > ------------------------------------------------------- Updated the TODO. > Cheers, > Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From mail at ozzmosis.com Sat Jun 21 07:02:41 2008 From: mail at ozzmosis.com (andrew clarke) Date: Sat Jun 21 07:02:46 2008 Subject: Possibly missing run dependencies with TightVNC's vncserver Message-ID: <20080621063557.GA10655@ozzmosis.com> Hi, I've just built net/tightvnc from the Ports tree on a headless machine running FreeBSD 6.3. Prior to installing tightvnc, the machine had no xorg apps or xorg libraries installed. My initial problem was that when I run vncserver, I got errors in $HOME/.vnc/$HOST:1.log telling me that the programs listed in $HOME/.vnc/xstartup are missing (xrdb, xsetroot, xterm and twm). I've since installed all of those from Ports, but have encountered another hurdle: Couldn't open RGB_DB '/usr/local/lib/X11/rgb' ... xsetroot: unknown color "grey" twm: invalid color name "black" twm: invalid color name "white" I've since learned that the x11/rgb port installs /usr/local/lib/X11/rgb.txt, but not /usr/local/lib/X11/rgb, but I guess I'm on the right track. After doing a bit more Googling I'm beginning to think /etc/X11/xorg.conf is used to configure the xorg backend, which vncserver relies on, but I don't have an xorg.conf on that machine, presumably because some crucial parts of xorg are still missing - or I'm meant to configure xorg somehow before running vncserver. I get the feeling that I'm doing this all backwards, and that I'm supposed to install more of xorg before I install net/tightvnc. Ideally the tightvnc port should've done that prior, though. Anyway, maybe someone could give me some hints on what I should be doing in this particular situation. Thanks, Regards Andrew From ws at au.dyndns.ws Sat Jun 21 16:48:32 2008 From: ws at au.dyndns.ws (Wayne Sierke) Date: Sat Jun 21 16:48:35 2008 Subject: Possibly missing run dependencies with TightVNC's vncserver In-Reply-To: <20080621063557.GA10655@ozzmosis.com> References: <20080621063557.GA10655@ozzmosis.com> Message-ID: <1214065993.35607.50.camel@predator-ii.buffyverse> On Sat, 2008-06-21 at 16:35 +1000, andrew clarke wrote: > Hi, > > I've just built net/tightvnc from the Ports tree on a headless machine > running FreeBSD 6.3. Prior to installing tightvnc, the machine had no > xorg apps or xorg libraries installed. > > My initial problem was that when I run vncserver, I got errors in > $HOME/.vnc/$HOST:1.log telling me that the programs listed in > $HOME/.vnc/xstartup are missing (xrdb, xsetroot, xterm and twm). I've > since installed all of those from Ports, but have encountered another > hurdle: > > Couldn't open RGB_DB '/usr/local/lib/X11/rgb' > ... > xsetroot: unknown color "grey" > twm: invalid color name "black" > twm: invalid color name "white" > > I've since learned that the x11/rgb port installs > /usr/local/lib/X11/rgb.txt, but not /usr/local/lib/X11/rgb, but I > guess I'm on the right track. After doing a bit more Googling I'm > beginning to think /etc/X11/xorg.conf is used to configure the xorg > backend, which vncserver relies on, but I don't have an xorg.conf on > that machine, presumably because some crucial parts of xorg are still > missing - or I'm meant to configure xorg somehow before running > vncserver. > > I get the feeling that I'm doing this all backwards, and that I'm > supposed to install more of xorg before I install net/tightvnc. > Ideally the tightvnc port should've done that prior, though. > > Anyway, maybe someone could give me some hints on what I should be > doing in this particular situation. Hi Andrew, I have tightvnc running on a headless machine and see various errors, too: Couldn't open RGB_DB '/usr/local/lib/X11/rgb' xrdb: not found xsetroot: not found I ignore them, and tightvnc seems to run ok regardless, at least to the extent where I can connect satisfactorily from other machines. Here's what's installed (on a 6.3 system): # pkg_info -rx tightvnc Information for tightvnc-1.3.9_1: Depends on: Dependency: xineramaproto-1.1.2 Dependency: xf86vidmodeproto-2.2.2 Dependency: xf86miscproto-0.9.2 Dependency: xf86dgaproto-2.0.3 Dependency: xextproto-7.0.2 Dependency: videoproto-2.2.2 Dependency: scrnsaverproto-1.1.0 Dependency: renderproto-0.9.3 Dependency: recordproto-1.13.2 Dependency: randrproto-1.2.1 Dependency: printproto-1.0.3 Dependency: kbproto-1.0.3 Dependency: inputproto-1.4.2.1 Dependency: fixesproto-4.0 Dependency: damageproto-1.1.0_2 Dependency: compositeproto-0.4 Dependency: fontsproto-2.0.2 Dependency: fontcacheproto-0.1.2 Dependency: font-util-1.0.1 Dependency: encodings-1.0.2,1 Dependency: expat-2.0.0_1 Dependency: perl-5.8.8 Dependency: jpeg-6b_4 Dependency: pkg-config-0.22_1 Dependency: mkfontdir-1.0.3 Dependency: pixman-0.9.6 Dependency: xtrans-1.0.4 Dependency: xproto-7.0.10_1 Dependency: libfontenc-1.0.4 Dependency: libXau-1.0.3_2 Dependency: libXdmcp-1.0.2 Dependency: libX11-1.1.3,1 Dependency: libxkbfile-1.0.4 Dependency: liboldX-1.0.1 Dependency: libXrender-0.9.4 Dependency: libXfixes-4.0.3 Dependency: libXdamage-1.1.1 Dependency: libXcursor-1.1.9 Dependency: libXext-1.0.3,1 Dependency: libdmx-1.0.2 Dependency: libXxf86vm-1.0.1 Dependency: libXxf86misc-1.0.1 Dependency: libXxf86dga-1.0.2 Dependency: libXv-1.0.3,1 Dependency: libXvMC-1.0.4 Dependency: libXtst-1.0.3 Dependency: libXres-1.0.3_2 Dependency: libXrandr-1.2.2 Dependency: libXinerama-1.0.2,1 Dependency: libXi-1.1.3,1 Dependency: libXfontcache-1.0.4 Dependency: libXevie-1.0.2 Dependency: libXcomposite-0.4.0,1 Dependency: libXp-1.0.0,1 Dependency: libXScrnSaver-1.1.2 Dependency: libICE-1.0.4,1 Dependency: libSM-1.0.3,1 Dependency: libXt-1.0.5 Dependency: libxkbui-1.0.2 Dependency: libXprintUtil-1.0.1 Dependency: libXprintAppUtil-1.0.1 Dependency: libXmu-1.0.3,1 Dependency: xauth-1.0.2 Dependency: libXpm-3.5.7 Dependency: libXaw-1.0.4,1 Dependency: trapproto-3.4.3 Dependency: libXTrap-1.0.0 Dependency: libFS-1.0.0 Dependency: freetype2-2.3.5 Dependency: mkfontscale-1.0.3 Dependency: font-winitzki-cyrillic-1.0.0 Dependency: font-sun-misc-1.0.0 Dependency: font-sony-misc-1.0.0 Dependency: font-screen-cyrillic-1.0.1 Dependency: font-schumacher-misc-1.0.0 Dependency: font-mutt-misc-1.0.0 Dependency: font-misc-misc-1.0.0 Dependency: font-misc-cyrillic-1.0.0 Dependency: font-micro-misc-1.0.0 Dependency: font-jis-misc-1.0.0 Dependency: font-isas-misc-1.0.0 Dependency: font-dec-misc-1.0.0 Dependency: font-daewoo-misc-1.0.0 Dependency: font-cursor-misc-1.0.0 Dependency: font-cronyx-cyrillic-1.0.0 Dependency: xorg-fonts-cyrillic-7.3 Dependency: font-bitstream-75dpi-1.0.0 Dependency: font-bitstream-100dpi-1.0.0 Dependency: font-bh-lucidatypewriter-75dpi-1.0.0 Dependency: font-bh-lucidatypewriter-100dpi-1.0.0 Dependency: font-bh-75dpi-1.0.0 Dependency: font-bh-100dpi-1.0.0 Dependency: font-arabic-misc-1.0.0 Dependency: xorg-fonts-miscbitmaps-7.3 Dependency: font-alias-1.0.1 Dependency: font-adobe-utopia-75dpi-1.0.1 Dependency: font-adobe-utopia-100dpi-1.0.1 Dependency: font-adobe-75dpi-1.0.0 Dependency: xorg-fonts-75dpi-7.3 Dependency: font-adobe-100dpi-1.0.0_1 Dependency: xorg-fonts-100dpi-7.3 Dependency: libXfont-1.3.1_1,1 Dependency: fontconfig-2.4.2_2,1 Dependency: font-xfree86-type1-1.0.0 Dependency: font-misc-meltho-1.0.0_1 Dependency: font-misc-ethiopic-1.0.0 Dependency: font-ibm-type1-1.0.0 Dependency: font-bitstream-type1-1.0.0 Dependency: font-bh-type1-1.0.0 Dependency: font-bh-ttf-1.0.0 Dependency: font-adobe-utopia-type1-1.0.1 Dependency: xorg-fonts-type1-7.3 Dependency: bitstream-vera-1.10_4 Dependency: xorg-fonts-truetype-7.3 Dependency: xorg-fonts-7.3 Dependency: libXft-2.1.12 Dependency: xorg-libraries-7.3_1 hth, Wayne From linimon at FreeBSD.org Sun Jun 22 00:26:57 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jun 22 00:27:01 2008 Subject: ports/124861: Keyboard problems with xorg Message-ID: <200806220026.m5M0Qugu076120@freefall.freebsd.org> Synopsis: Keyboard problems with xorg Responsible-Changed-From-To: freebsd-bugs->freebsd-x11 Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 22 00:26:30 UTC 2008 Responsible-Changed-Why: Make a ports PR and assign. http://www.freebsd.org/cgi/query-pr.cgi?pr=124861 From mail at ozzmosis.com Mon Jun 23 09:58:55 2008 From: mail at ozzmosis.com (andrew clarke) Date: Mon Jun 23 09:58:59 2008 Subject: Possibly missing run dependencies with TightVNC's vncserver In-Reply-To: <1214065993.35607.50.camel@predator-ii.buffyverse> References: <20080621063557.GA10655@ozzmosis.com> <1214065993.35607.50.camel@predator-ii.buffyverse> Message-ID: <20080623095849.GA17951@ozzmosis.com> On Sun 2008-06-22 02:03:13 UTC+0930, Wayne Sierke (ws@au.dyndns.ws) wrote: > I have tightvnc running on a headless machine and see various errors, > too: > > Couldn't open RGB_DB '/usr/local/lib/X11/rgb' > xrdb: not found > xsetroot: not found > > I ignore them, and tightvnc seems to run ok regardless, at least to the > extent where I can connect satisfactorily from other machines. Yes, maybe I wasn't clear in my original message. vncserver runs fine, and I can connect to it without trouble, but xterm (and others) generated errors due to missing components. I've since created a minimal xorg.conf after installing the x11/rgb port and it seems all the errors have disappeared. And WindowMaker no longer segfaults after I kill twm and run wmaker. $ cat /etc/X11/xorg.conf Section "Files" RgbPath "/usr/local/share/X11/rgb" 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/" FontPath "/usr/local/lib/X11/fonts/URW/" EndSection Oddly though, if I delete xorg.conf, the errors don't return. Some sort of caching in place, perhaps. Regards Andrew From bugmaster at FreeBSD.org Mon Jun 23 11:07:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 23 11:07:45 2008 Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org Message-ID: <200806231107.m5NB744V065155@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/106370 x11 Screen corruption when using Direct Rendering on a PCI o ports/116359 x11 x11/xorg - screen blinks with PCI-E nvidia card and ve o ports/117195 x11 ix11/Xorg 7.3 dumps core at exit (sig 11) f ports/117508 x11 x11/xorg 7.2,7.3 i8i0 and intel crash system using Ble o ports/117766 x11 x11-servers/xorg-server (7.3) crashes under heavy load o ports/118950 x11 x11-drivers/xf86-video-nv - xorg xf86 nv (nvidia) driv o ports/119037 x11 x11: Can't type _ (Underscore) under X (gnome) f ports/119091 x11 x11-drivers/xf86-video-intel 2.1.1 panics system o ports/121360 x11 x11/xorg - Change default of ~/.xsession-errors to off o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/122924 x11 XCreateImage fails in most recent x11/XOrg o ports/124861 x11 Keyboard problems with xorg 12 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s ports/73743 x11 XOrg/XFree xauth add/startx problem o ports/93667 x11 x11/xorg-libraries: undefined symbol in libOSMesa.* is o ports/113106 x11 x11/xorg - Xorg 7.2 + Mach64 + dri produces error mess f ports/114827 x11 Xorg server crashes when starting astro/google-earth o ports/115020 x11 New port: graphics/osmesa - Mesa's off-screen renderin s ports/115536 x11 [new port] x11/xorg-base port for a minimal X.Org inst o ports/116443 x11 x11-drivers/xf86-input-keyboard patch for USB jp106 ke f ports/116603 x11 x11/xorg server 7.3 hangs up f ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) f ports/118217 x11 xorg doesnt find usb mouse when initiated with devd, w o ports/118547 x11 [patch] x11/xdm fails with pam_krb5 o ports/118645 x11 Xorg need realtime priority for mouse work nice o ports/121230 x11 [patch] ports/x11/xkeyboard-config WITHOUT_NLS support o ports/123137 x11 x11/libX11: missing ru_RU.UTF-8 locale 14 problems total. From bugmaster at FreeBSD.org Mon Jun 23 11:08:49 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 23 11:08:51 2008 Subject: Current problem reports assigned to x11@FreeBSD.org Message-ID: <200806231108.m5NB8mCa067052@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/124220 x11 [amd64] x11-servers/xorg-server - X.org server runs in 1 problem total. Non-critical problems From wblock at wonkity.com Mon Jun 23 17:28:53 2008 From: wblock at wonkity.com (Warren Block) Date: Mon Jun 23 17:28:57 2008 Subject: Slow switch from console to X with 7.x? Message-ID: Just switched a 6.3 system to 7-STABLE and then csupped and rebuilt all ports. No CPU optimizations in /etc/make.conf. The only serious difference seems to be switching from a text console to X (Alt-F9). Graphic mode screen shows immediately (but not completely, looks like the wrong bit depth) and then there's a lag of about five seconds, then the screen is is drawn correctly. That switch took a second or so on 6.3. No difference with or without VESA/SC_PIXEL_MODE in the kernel, and switching from X to a text console (Ctrl-Alt-F1) seems the same as before, about a second. A couple of searches didn't help, but it's hard to pick the right search terms for this. Is a slow switch from console to X expected behavior with 7.x or is there something that can be done? FreeBSD speedy.wonkity.com 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon Jun 23 09:20:32 MDT 2008 root@speedy.wonkity.com:/usr/obj/usr/src/sys/SPEEDY i386 FreeBSD 7.0-STABLE #0: Mon Jun 23 09:20:32 MDT 2008 root@speedy.wonkity.com:/usr/obj/usr/src/sys/SPEEDY Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 3000+ (2108.96-MHz 686-class CPU) ... vgapci0: mem 0xdc000000-0xddffffff,0xdfefc000-0xdfefffff,0xdf000000-0xdf7fffff irq 16 at device 0.0 on pci1 ... sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 xf86-video-mga-1.9.100 (I think I tried 1.4.7 during the port rebuild with the same behavior.) -Warren Block * Rapid City, South Dakota USA From jhein at timing.com Tue Jun 24 00:13:10 2008 From: jhein at timing.com (John E Hein) Date: Tue Jun 24 00:13:13 2008 Subject: Slow switch from console to X with 7.x? In-Reply-To: References: Message-ID: <18528.15377.743142.882852@gromit.timing.com> Warren Block wrote at 10:54 -0600 on Jun 23, 2008: > Just switched a 6.3 system to 7-STABLE and then csupped and rebuilt all > ports. No CPU optimizations in /etc/make.conf. > > The only serious difference seems to be switching from a text console to > X (Alt-F9). Graphic mode screen shows immediately (but not completely, > looks like the wrong bit depth) and then there's a lag of about five > seconds, then the screen is is drawn correctly. > > That switch took a second or so on 6.3. No difference with or without > VESA/SC_PIXEL_MODE in the kernel, and switching from X to a text console > (Ctrl-Alt-F1) seems the same as before, about a second. Slow switching with usb keyboards is a known problem, but I don't think that is a 7.x regression, and I don't recall if it matters if you go from text->graphics or vice versa. From ws at au.dyndns.ws Tue Jun 24 17:37:50 2008 From: ws at au.dyndns.ws (Wayne Sierke) Date: Tue Jun 24 17:37:53 2008 Subject: Possibly missing run dependencies with TightVNC's vncserver In-Reply-To: <20080623095849.GA17951@ozzmosis.com> References: <20080621063557.GA10655@ozzmosis.com> <1214065993.35607.50.camel@predator-ii.buffyverse> <20080623095849.GA17951@ozzmosis.com> Message-ID: <1214329064.35607.185.camel@predator-ii.buffyverse> On Mon, 2008-06-23 at 19:58 +1000, andrew clarke wrote: > On Sun 2008-06-22 02:03:13 UTC+0930, Wayne Sierke (ws@au.dyndns.ws) wrote: > > > I have tightvnc running on a headless machine and see various errors, > > too: > > > > Couldn't open RGB_DB '/usr/local/lib/X11/rgb' > > xrdb: not found > > xsetroot: not found > > > > I ignore them, and tightvnc seems to run ok regardless, at least to the > > extent where I can connect satisfactorily from other machines. > > Yes, maybe I wasn't clear in my original message. vncserver runs > fine, and I can connect to it without trouble, but xterm (and others) > generated errors due to missing components. I've since created a > minimal xorg.conf after installing the x11/rgb port and it seems all > the errors have disappeared. And WindowMaker no longer segfaults > after I kill twm and run wmaker. > > $ cat /etc/X11/xorg.conf > Section "Files" > RgbPath "/usr/local/share/X11/rgb" > 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/" > FontPath "/usr/local/lib/X11/fonts/URW/" > EndSection > > Oddly though, if I delete xorg.conf, the errors don't return. Some > sort of caching in place, perhaps. I've taken another look at the setup here. xterms work adequately in the vnc desktop for my needs, e.g. top and vi work as expected and the only failing I've seen is that mutt was unusable as the text was not visible. I've not pursued that issue since it's not a problem for my needs. Here's some of the configuration on the system I referred to: # crontab -l -u ws # 20080330 ws - vncserver bombs without /usr/local/bin (for xauth) in PATH PATH=/bin:/usr/bin:/usr/local/bin # 20080329 ws - /usr/X11R6 is now /usr/local @reboot /usr/local/bin/vncserver :1 -geometry 1024x768 -depth 16 # cat /home/ws/.vnc/xstartup #!/bin/sh xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & env DISPLAY=:1 wine c:/utorrent.exe & lwm & # ls /etc/X11/* ls: No match. # ls /home/ws/.X* /root/.X* /home/ws/.Xauthority /root/.Xauthority I don't recall the history of the xrdb and xsetroot lines in xstartup, but neither is currently installed nor required - hence the errors for those in my previous message. x11/rgb isn't installed and the only other port I can recall deliberately installing was x11-wm/lwm (actually a couple of other light-weight window managers, too, but I currently use lwm). The system was running 6.x until yesterday when it was upgraded to 7-STABLE with no discernible change in behaviour, albeit the ports are yet to be updated. ?Some additional information is needed to narrow this down. What exactly did you see the xterm (and others) complaining about? System and ports versions? Are you running vncserver as root or user? Wayne From p.schack at kapricorne.net Fri Jun 27 00:40:06 2008 From: p.schack at kapricorne.net (=?utf-8?B?UGhpbGlwcGUgU0NIw4RDSw==?=) Date: Fri Jun 27 00:40:08 2008 Subject: ports/124861: Keyboard problems with xorg Message-ID: <200806270040.m5R0e6EM004823@freefall.freebsd.org> The following reply was made to PR ports/124861; it has been noted by GNATS. From: "=?utf-8?B?UGhpbGlwcGUgU0NIw4RDSw==?=" To: Cc: Subject: Re: ports/124861: Keyboard problems with xorg Date: Fri, 27 Jun 2008 02:16:59 +0200 Hi, I have made some more tests. I have reinstalled the old FreeBSD 6.2 Hard disk in my computer and launche= d xorg (older version 6.8 or 6.9 ?). The problem is the same than with the FreeBSD 7.0 installation. This version was running on a MSI motherboard without any problem until the= motherboard died. The problem is about xorg and the new motherboard (Asus P5KPL-VM) ?. From radek at ceskedomeny.cz Fri Jun 27 08:39:24 2008 From: radek at ceskedomeny.cz (Bc. Radek Krejca) Date: Fri Jun 27 08:39:27 2008 Subject: Problem witch xorg on 7.0 Message-ID: <1982271535.20080627101239@starnet.cz> Hello, I reinstall my notebook from 6.0 to 7.0 FBSD and I have problem with X. Xorg is installed from ports and is starting. But I only see something like this: After command X: http://www.starnet.cz/free/xorg.jpg After command kdm: http://www.starnet.cz/free/kdm.jpg No chance for anything action, I only see this like some bitmap. Logs: dmesg: http://www.starnet.cz/free/dmesg.txt installed packages (from ports): http://www.starnet.cz/free/pkg.txt Xorg log: http://www.starnet.cz/free/Xorg.0.log.txt I have similar problem in 6.3, but there i got black screen without chance for any action (hard reset). When i put this lines (in 6.3) device drm device radeondrm then i got the same problem like in 7.0. Hardware is ok because my friend has the same notebook with 6.3 and when we change disks with his installation, then xorg working properly. But we cannot find diference between us. Radek -- Regards, Bc. Radek Krejca STARNET, s. r. o. radek@ceskedomeny.cz From mail at ozzmosis.com Fri Jun 27 15:54:16 2008 From: mail at ozzmosis.com (andrew clarke) Date: Fri Jun 27 15:54:21 2008 Subject: Possibly missing run dependencies with TightVNC's vncserver In-Reply-To: <1214329064.35607.185.camel@predator-ii.buffyverse> References: <20080621063557.GA10655@ozzmosis.com> <1214065993.35607.50.camel@predator-ii.buffyverse> <20080623095849.GA17951@ozzmosis.com> <1214329064.35607.185.camel@predator-ii.buffyverse> Message-ID: <20080627155412.GA40278@ozzmosis.com> On Wed 2008-06-25 03:07:44 UTC+0930, Wayne Sierke (ws@au.dyndns.ws) wrote: > > Yes, maybe I wasn't clear in my original message. vncserver runs > > fine, and I can connect to it without trouble, but xterm (and others) > > generated errors due to missing components. I've since created a > > minimal xorg.conf after installing the x11/rgb port and it seems all > > the errors have disappeared. And WindowMaker no longer segfaults > > after I kill twm and run wmaker. > > > > $ cat /etc/X11/xorg.conf > > Section "Files" > > RgbPath "/usr/local/share/X11/rgb" > > 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/" > > FontPath "/usr/local/lib/X11/fonts/URW/" > > EndSection > > > > Oddly though, if I delete xorg.conf, the errors don't return. Some > > sort of caching in place, perhaps. After deleting xorg.conf and running "pkg_delete rgb-1.0.1", I re-ran vncserver and the errors returned. WindowMaker started dumping core again: $ cat $HOME/.vnc/*.log Couldn't open RGB_DB '/usr/local/lib/X11/rgb' 28/06/08 01:22:51 Xvnc version TightVNC-1.3.9 28/06/08 01:22:51 Copyright (C) 2000-2007 TightVNC Group 28/06/08 01:22:51 Copyright (C) 1999 AT&T Laboratories Cambridge 28/06/08 01:22:51 All Rights Reserved. 28/06/08 01:22:51 See http://www.tightvnc.com/ for information on TightVNC 28/06/08 01:22:51 Desktop name 'X' (blizzard.dancer:1) 28/06/08 01:22:51 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t 28/06/08 01:22:51 Listening for VNC connections on TCP port 5901 28/06/08 01:22:51 Listening for HTTP connections on TCP port 5801 28/06/08 01:22:51 URL http://blizzard.dancer:5801 xsetroot: unknown color "grey" wmaker warning: could not parse color "black" wmaker warning: could not parse color "white" wmaker warning: "gray" is not a valid color name wmaker warning: Error in texture specification for key "WidgetColor" wmaker warning: using default "(solid, gray)" instead wmaker warning: "gray" is not a valid color name wmaker warning: Error in texture specification for key "WidgetColor" wmaker warning: could not parse color "white" wmaker warning: could not get color for key "HighlightColor" wmaker warning: using default "white" instead wmaker warning: could not parse color "white" wmaker warning: could not get color for key "HighlightColor" wmaker warning: could not parse color "black" wmaker warning: could not get color for key "HighlightTextColor" wmaker warning: using default "black" instead wmaker warning: could not parse color "black" wmaker warning: could not get color for key "HighlightTextColor" wmaker warning: could not parse color "black" wmaker warning: could not get color for key "ClipTitleColor" wmaker warning: using default "black" instead wmaker warning: could not parse color "black" wmaker warning: could not get color for key "ClipTitleColor" wmaker warning: could not parse color "white" wmaker warning: could not get color for key "FTitleColor" wmaker warning: using default "white" instead wmaker warning: could not parse color "white" wmaker warning: could not get color for key "FTitleColor" wmaker warning: could not parse color "white" wmaker warning: could not get color for key "PTitleColor" wmaker warning: using default "white" instead wmaker warning: could not parse color "white" wmaker warning: could not get color for key "PTitleColor" wmaker warning: could not parse color "black" wmaker warning: could not get color for key "UTitleColor" wmaker warning: using default "black" instead wmaker warning: could not parse color "black" wmaker warning: could not get color for key "UTitleColor" wmaker warning: "black" is not a valid color name wmaker warning: Error in texture specification for key "FTitleBack" wmaker warning: using default "(solid, black)" instead wmaker warning: "black" is not a valid color name wmaker warning: Error in texture specification for key "FTitleBack" wmaker warning: "gray40" is not a valid color name wmaker warning: Error in texture specification for key "PTitleBack" wmaker warning: using default "(solid, "#616161")" instead wmaker warning: could not parse color "white" wmaker warning: could not get color for key "MenuTitleColor" wmaker warning: using default "white" instead wmaker warning: could not parse color "white" wmaker warning: could not get color for key "MenuTitleColor" wmaker warning: could not parse color "black" wmaker warning: could not get color for key "MenuTextColor" wmaker warning: using default "black" instead wmaker warning: could not parse color "black" wmaker warning: could not get color for key "MenuTextColor" wmaker warning: could not parse color "gray50" wmaker warning: could not get color for key "MenuDisabledColor" wmaker warning: using default "#616161" instead wmaker warning: "black" is not a valid color name wmaker warning: Error in texture specification for key "MenuTitleBack" wmaker warning: using default "(solid, black)" instead wmaker warning: "black" is not a valid color name wmaker warning: Error in texture specification for key "MenuTitleBack" wmaker warning: could not parse color "white" wmaker warning: could not get color for key "IconTitleColor" wmaker warning: using default "white" instead wmaker warning: could not parse color "white" wmaker warning: could not get color for key "IconTitleColor" wmaker warning: could not parse color "black" wmaker warning: could not get color for key "IconTitleBack" wmaker warning: using default "black" instead wmaker warning: could not parse color "black" wmaker warning: could not get color for key "IconTitleBack" $ cat $HOME/.vnc/xstartup #!/bin/sh xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & wmaker & If I replace wmaker with twm: twm: invalid color name "black" twm: invalid color name "white" twm: invalid color name "slategrey" twm: invalid color name "gray85" twm: invalid color name "gray85" twm: invalid color name "gray85" twm: invalid color name "slategrey" twm: invalid color name "gray70" twm: invalid color name "gray85" twm: invalid color name "gray85" twm: invalid color name "gray85" And run Mutt from xterm: xterm: Cannot allocate color green xterm: Cannot allocate color cyan xterm: Cannot allocate color gray90 xterm: Cannot allocate color black xterm: Cannot allocate color white xterm: Cannot allocate color blue2 xterm: Cannot allocate color yellow xterm: Cannot allocate color red3 > I don't recall the history of the xrdb and xsetroot lines in xstartup, > but neither is currently installed nor required - hence the errors for > those in my previous message. > > x11/rgb isn't installed and the only other port I can recall > deliberately installing was x11-wm/lwm (actually a couple of other > light-weight window managers, too, but I currently use lwm). > > The system was running 6.x until yesterday when it was upgraded to > 7-STABLE with no discernible change in behaviour, albeit the ports are > yet to be updated. > > ???Some additional information is needed to narrow this down. What exactly > did you see the xterm (and others) complaining about? System and ports > versions? Are you running vncserver as root or user? FreeBSD 6.3, as non-root user. Ports tree is current. I think the issue is that the tightvnc port: 1. does not list x11/rgb as a dependency 2. does not point to the right place where the RGB database is located. See net/tightvnc/files/patch-Xvnc::programs::Xserver::dix::Imakefile : +DEFAULTRGBDATABASE = ${LOCALBASE}/lib/X11/rgb I think this should be: +DEFAULTRGBDATABASE = ${LOCALBASE}/lib/X11/rgb.txt OK, I'm baffled. After making that change then doing a rebuild/reinstall of net/tightvnc, then reinstalling x11/rgb, I still get this error: Couldn't open RGB_DB '/usr/local/lib/X11/rgb.txt' But it's there: -r--r--r-- 1 root wheel 17371 2008-06-21 16:16 /usr/local/lib/X11/rgb.txt And /etc/X11/xorg.conf seems to make no difference this time. As you can probably imagine, I don't understand what's going on at this point. Regards Andrew From jkim at FreeBSD.org Fri Jun 27 23:34:43 2008 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Fri Jun 27 23:34:45 2008 Subject: [HEADSUP] xf86-video-ati update and separation Message-ID: <200806271934.32448.jkim@FreeBSD.org> xf86-video-ati is updated to 6.9.0. From this release, mach64 and r128 are separated out into xf86-video-mach64 and xf86-video-r128 respectively. If you are using one of the video cards, please read 20080627 entry from ports/UPDATING. Thanks, Jung-uk Kim From delphij at freebsd.org Sat Jun 28 00:26:41 2008 From: delphij at freebsd.org (Xin LI) Date: Sat Jun 28 00:26:43 2008 Subject: [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 Message-ID: <200806280026.m5S0QfOg090856@freefall.freebsd.org> >Submitter-Id: current-users >Originator: Xin LI >Organization: The FreeBSD Project >Confidential: no >Synopsis: [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 >Severity: non-critical >Priority: low >Category: ports >Class: update >Release: FreeBSD 7.0-STABLE i386 >Environment: System: FreeBSD freefall.freebsd.org 7.0-STABLE FreeBSD 7.0-STABLE #34: Sat Apr 12 11:52:18 UTC 2008 simon@freefall.freebsd.org:/usr/src/sys/i386/compile/FREEFALL i386 >Description: >How-To-Repeat: >Fix: --- xf86-video-nv.diff begins here --- Index: Makefile =================================================================== RCS file: /home/ncvs/ports/x11-drivers/xf86-video-nv/Makefile,v retrieving revision 1.9 diff -u -p -r1.9 Makefile --- Makefile 6 Jun 2008 14:10:26 -0000 1.9 +++ Makefile 28 Jun 2008 00:14:41 -0000 @@ -6,8 +6,7 @@ # PORTNAME= xf86-video-nv -PORTVERSION= 2.1.8 -PORTREVISION= 1 +PORTVERSION= 2.1.9 CATEGORIES= x11-drivers MAINTAINER= x11@FreeBSD.org Index: distinfo =================================================================== RCS file: /home/ncvs/ports/x11-drivers/xf86-video-nv/distinfo,v retrieving revision 1.7 diff -u -p -r1.7 distinfo --- distinfo 31 Mar 2008 10:30:55 -0000 1.7 +++ distinfo 28 Jun 2008 00:14:51 -0000 @@ -1,3 +1,3 @@ -MD5 (xorg/driver/xf86-video-nv-2.1.8.tar.bz2) = c3e8c98287dc98677bebfbe1ba51ab77 -SHA256 (xorg/driver/xf86-video-nv-2.1.8.tar.bz2) = 825ffb97525517de9f0ff7155946c6e58c278dba11957573cc970dd3b094f94a -SIZE (xorg/driver/xf86-video-nv-2.1.8.tar.bz2) = 384527 +MD5 (xorg/driver/xf86-video-nv-2.1.9.tar.bz2) = c6b7e52fa18455c22eb040b8d2575ce5 +SHA256 (xorg/driver/xf86-video-nv-2.1.9.tar.bz2) = 20d92ff3ab4b9ecc150f4ed17a7012a48f56dbf3fb51b51dde769b28922976d9 +SIZE (xorg/driver/xf86-video-nv-2.1.9.tar.bz2) = 386003 --- xf86-video-nv.diff ends here --- From edwin at FreeBSD.org Sat Jun 28 00:30:15 2008 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sat Jun 28 00:30:17 2008 Subject: ports/125065: [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 Message-ID: <200806280030.m5S0UFBK092084@freefall.freebsd.org> Synopsis: [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-x11 Responsible-Changed-By: edwin Responsible-Changed-When: Sat Jun 28 00:30:14 UTC 2008 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=125065 From dfilter at FreeBSD.ORG Sat Jun 28 10:10:04 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Jun 28 10:10:06 2008 Subject: ports/125065: commit references a PR Message-ID: <200806281010.m5SAA3nC072664@freefall.freebsd.org> The following reply was made to PR ports/125065; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/125065: commit references a PR Date: Sat, 28 Jun 2008 10:02:37 +0000 (UTC) flz 2008-06-28 10:02:33 UTC FreeBSD ports repository Modified files: x11-drivers/xf86-video-nv Makefile distinfo Log: Update x11-drivers/xf86-video-nv to 2.1.9. PR: ports/125065 Submitted by: delphij Revision Changes Path 1.10 +1 -2 ports/x11-drivers/xf86-video-nv/Makefile 1.8 +3 -3 ports/x11-drivers/xf86-video-nv/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From bugmaster at FreeBSD.org Mon Jun 30 11:07:08 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 30 11:07:43 2008 Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org Message-ID: <200806301107.m5UB76vH095939@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/106370 x11 Screen corruption when using Direct Rendering on a PCI o ports/116359 x11 x11/xorg - screen blinks with PCI-E nvidia card and ve o ports/117195 x11 ix11/Xorg 7.3 dumps core at exit (sig 11) f ports/117508 x11 x11/xorg 7.2,7.3 i8i0 and intel crash system using Ble o ports/117766 x11 x11-servers/xorg-server (7.3) crashes under heavy load o ports/118950 x11 x11-drivers/xf86-video-nv - xorg xf86 nv (nvidia) driv o ports/119037 x11 x11: Can't type _ (Underscore) under X (gnome) f ports/119091 x11 x11-drivers/xf86-video-intel 2.1.1 panics system o ports/121360 x11 x11/xorg - Change default of ~/.xsession-errors to off o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/122924 x11 XCreateImage fails in most recent x11/XOrg o ports/124220 x11 [amd64] x11-servers/xorg-server - X.org server runs in o ports/124861 x11 Keyboard problems with xorg 13 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s ports/73743 x11 XOrg/XFree xauth add/startx problem o ports/93667 x11 x11/xorg-libraries: undefined symbol in libOSMesa.* is o ports/113106 x11 x11/xorg - Xorg 7.2 + Mach64 + dri produces error mess f ports/114827 x11 Xorg server crashes when starting astro/google-earth o ports/115020 x11 New port: graphics/osmesa - Mesa's off-screen renderin s ports/115536 x11 [new port] x11/xorg-base port for a minimal X.Org inst o ports/116443 x11 x11-drivers/xf86-input-keyboard patch for USB jp106 ke f ports/116603 x11 x11/xorg server 7.3 hangs up f ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) f ports/118217 x11 xorg doesnt find usb mouse when initiated with devd, w o ports/118547 x11 [patch] x11/xdm fails with pam_krb5 o ports/118645 x11 Xorg need realtime priority for mouse work nice o ports/121230 x11 [patch] ports/x11/xkeyboard-config WITHOUT_NLS support o ports/123137 x11 x11/libX11: missing ru_RU.UTF-8 locale o ports/125065 x11 [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 15 problems total. From radek at ceskedomeny.cz Mon Jun 30 12:31:24 2008 From: radek at ceskedomeny.cz (Bc. Radek Krejca) Date: Mon Jun 30 12:31:28 2008 Subject: Problem witch xorg on 7.0 In-Reply-To: <1982271535.20080627101239@starnet.cz> References: <1982271535.20080627101239@starnet.cz> Message-ID: <1246272067.20080630143114@starnet.cz> Hi, I have new symptoms for this problem and emergency help (not good but working). When I start 2 X servers, then firs has still problems but second is working. In KDE you can configure kdmrc for starting two X servers. Then you have on terminal 9 X server, which isnt working and on terminal 10 (ALT+F9) working kdm and KDE. I dont know why, but this is working. It was very big fortune discover this. Thanks to my colleague who has old kdmrc with one server for connection to remote X server. Radek -- Regards, Bc. Radek Krejca STARNET, s. r. o. radek@ceskedomeny.cz From cracauer at cons.org Mon Jun 30 15:44:00 2008 From: cracauer at cons.org (Martin Cracauer) Date: Mon Jun 30 15:44:04 2008 Subject: Synaptics driver not suspend/resume safe Message-ID: <20080630153108.GA86191@cons.org> The synapics driver doesn't seem to be suspend/resume safe. If you suspend directly from within X11 then using the touchpad hangs the machine after wakeup. If you F-2 away from X11 before suspend/resume the whole machine things don't crash, X11 works including keystrokes, but no touchpad events get through. Any solutions for this? Is it a known problem? Can we reset the driver via some special ioctl? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From delphij at FreeBSD.org Mon Jun 30 18:02:04 2008 From: delphij at FreeBSD.org (delphij@FreeBSD.org) Date: Mon Jun 30 18:02:06 2008 Subject: ports/125065: [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 Message-ID: <200806301802.m5UI241x044952@freefall.freebsd.org> Synopsis: [PATCH] Update x11-drivers/xf86-video-nv to 2.1.9 State-Changed-From-To: open->closed State-Changed-By: delphij State-Changed-When: Mon Jun 30 18:01:49 UTC 2008 State-Changed-Why: Patch committed by flz@ http://www.freebsd.org/cgi/query-pr.cgi?pr=125065 From mezz7 at cox.net Mon Jun 30 23:18:01 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Mon Jun 30 23:18:13 2008 Subject: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0! In-Reply-To: References: Message-ID: FYI: These have been committed in FreeBSD ports tree. You now can run 'marcusmerge -U' to unmerge ports-stable and remove it. I will removing everything in ports-stable tonight. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org