CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 05/02/09 09:06:55 Log message: Fix Juliusz Chroboczek's email address. Modified files: xc/programs/Xserver/hw/xfree86/doc/sgml/: dps.sgml fonts.sgml xc/programs/fonttosfnt/: fonttosfnt.man xc/programs/luit/: luit.man xc/programs/mkfontscale/: mkfontscale.man Revision ChangesPath 1.4 +2 -2 xc/programs/Xserver/hw/xfree86/doc/sgml/dps.sgml 1.26 +2 -2 xc/programs/Xserver/hw/xfree86/doc/sgml/fonts.sgml 1.4 +2 -2 xc/programs/fonttosfnt/fonttosfnt.man 1.9 +2 -2 xc/programs/luit/luit.man 1.6 +2 -2 xc/programs/mkfontscale/mkfontscale.man ___ Cvs-commit mailing list Cvs-commit@XFree86.Org http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 05/02/09 09:08:10 Log message: update formatted docs Modified files: xc/programs/Xserver/hw/xfree86/doc/: README.dps README.fonts Revision ChangesPath 1.8 +2 -2 xc/programs/Xserver/hw/xfree86/doc/README.dps 1.31 +2 -2 xc/programs/Xserver/hw/xfree86/doc/README.fonts ___ Cvs-commit mailing list Cvs-commit@XFree86.Org http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 05/02/09 11:41:33 Log message: update version, and add Solaris-sparc Modified files: xc/programs/Xserver/hw/xfree86/etc/: Xinstall.sh Revision ChangesPath 1.85 +18 -2 xc/programs/Xserver/hw/xfree86/etc/Xinstall.sh ___ Cvs-commit mailing list Cvs-commit@XFree86.Org http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 05/02/09 17:37:52 Log message: cleanup Modified files: xc/programs/Xserver/hw/xfree86/os-support/bsd/: bsd_mouse.c Revision ChangesPath 1.37 +3 -1 xc/programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c ___ Cvs-commit mailing list Cvs-commit@XFree86.Org http://XFree86.Org/mailman/listinfo/cvs-commit
Re: DRM kernel source broken/incomplete
On Tue, Feb 08, 2005 at 08:14:59PM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 11:52:27PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 06:40:07PM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 11:24:43PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 06:17:50PM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 05:12:29PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 11:59:15AM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 04:40:42PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 11:32:56AM -0500, David Dawes wrote: It looks like the DRM kernel source in xc/extras/drm is broken and incomplete, especially for BSD platforms. The Linux version only appears to build for a narrow range of kernels, and this either needs to be fixed, or the minimum kernel requirements enforced in the Makefile. Perhaps we'll have to roll back to an older version that does build? I suspect pulling in a newer snapshot would be better, although it's a little more complicated now because the drm has split out support for linux 2.4 and 2.6 kernels is separate subdirectories. Does the build automatically figure out which to use based on the kernel version, and what range of kernels has it been verified on? No. Any imports/updates need to address our requirements in this regard. If we import the current DRM trunk code, there are three linux directories. 1. linux for 2.4 kernels (monolithic) 2. linux-2.6 for 2.6 kernels (monolithic) 3. linux-core for 2.6 kernels with modular drm.ko and driver.ko and two for bsd 1. bsdmonolithic 2. bsd-core modular as above The -core are the new ones going forward and which I believe has been merged in linux 2.6.11. So, for now the linux-2.6, linux and bsd directories are the ones to stick with for stability. But things are changing. There'll be necessary build tweaks to select which directories are needed. At this point in our release cycle, the priorities are: 1st: It builds/runs and is reasonably stable on a good range of platforms. 2nd: It supports as many DRI features as possible consistent with the first priority. I don't think that even changing from the existing single Linux directory to two different kernel-specific directories is appropriate at this point in our release cycle. The time for such a change was before the feature freeze. If what we have now is too broken to be fixed without major structural changes, then it will need to be rolled back. The fear is, if you roll back the DRM, then the drivers may need to be rolled back as well to support lesser features. Some have said here today that the drivers can adapt to older DRM versions. That's how it should be, but I don't know if it is true or not. I've seen some things in my initial testing that may cast some doubt on it, but there were too many other variables to be certain without followup. It would clearly be preferable to have a recent version that works. Is there a known recent stable/working version? From my point of view the fear is, updating to the latest version, adapting to its structural changes, and finding that the result is no better. But isn't it better to move forward than backwards ? If the result is no better, then we need to fix the problems found. Going back to an older version, and just because it builds, doesn't guarantee it's going to work any better either. I've got more faith in the current DRM CVS as people are actively working on it, rather than using an older snapshot that people could be unwilling to go back and fix if a problem was found. Alan. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.5.0 RC1 (4.4.99.901)
David, People have been telling me that the [EMAIL PROTECTED] address is bouncing. Could you please either fix the alias, or change the fonts.sgml document to use [EMAIL PROTECTED] ? (Or both.) Thanks, Juliusz ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: DRM kernel source broken/incomplete
On Wed, Feb 09, 2005 at 10:05:38AM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 08:14:59PM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 11:52:27PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 06:40:07PM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 11:24:43PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 06:17:50PM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 05:12:29PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 11:59:15AM -0500, David Dawes wrote: On Tue, Feb 08, 2005 at 04:40:42PM +, Alan Hourihane wrote: On Tue, Feb 08, 2005 at 11:32:56AM -0500, David Dawes wrote: It looks like the DRM kernel source in xc/extras/drm is broken and incomplete, especially for BSD platforms. The Linux version only appears to build for a narrow range of kernels, and this either needs to be fixed, or the minimum kernel requirements enforced in the Makefile. Perhaps we'll have to roll back to an older version that does build? I suspect pulling in a newer snapshot would be better, although it's a little more complicated now because the drm has split out support for linux 2.4 and 2.6 kernels is separate subdirectories. Does the build automatically figure out which to use based on the kernel version, and what range of kernels has it been verified on? No. Any imports/updates need to address our requirements in this regard. If we import the current DRM trunk code, there are three linux directories. 1. linux for 2.4 kernels (monolithic) 2. linux-2.6 for 2.6 kernels (monolithic) 3. linux-corefor 2.6 kernels with modular drm.ko and driver.ko and two for bsd 1. bsd monolithic 2. bsd-core modular as above The -core are the new ones going forward and which I believe has been merged in linux 2.6.11. So, for now the linux-2.6, linux and bsd directories are the ones to stick with for stability. But things are changing. There'll be necessary build tweaks to select which directories are needed. At this point in our release cycle, the priorities are: 1st: It builds/runs and is reasonably stable on a good range of platforms. 2nd: It supports as many DRI features as possible consistent with the first priority. I don't think that even changing from the existing single Linux directory to two different kernel-specific directories is appropriate at this point in our release cycle. The time for such a change was before the feature freeze. If what we have now is too broken to be fixed without major structural changes, then it will need to be rolled back. The fear is, if you roll back the DRM, then the drivers may need to be rolled back as well to support lesser features. Some have said here today that the drivers can adapt to older DRM versions. That's how it should be, but I don't know if it is true or not. I've seen some things in my initial testing that may cast some doubt on it, but there were too many other variables to be certain without followup. It would clearly be preferable to have a recent version that works. Is there a known recent stable/working version? From my point of view the fear is, updating to the latest version, adapting to its structural changes, and finding that the result is no better. But isn't it better to move forward than backwards ? If the result is no better, then we need to fix the problems found. Going back to an older version, and just because it builds, doesn't guarantee it's going to work any better either. I've got more faith in the current DRM CVS as people are actively working on it, rather than using an older snapshot that people could be unwilling to go back and fix if a problem was found. I'd like to see a version that is proven to build, work, and fit in with our requirements before making any final decision on this. The snapshot we currently have imported is clearly not a good one. Otherwise, going back to the version of the kernel modules that we shipped with 4.4.0 won't be too difficult, especially if the user-mode side has the level of backward compatibility that people have claimed. David ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Message Received
Thank you for contacting Archivus for employment opportunities. Due to the enormous volume of requests that we get every day, we cannot respond to all inquiries about employment. Your message has been forwarded to the appropriate personnel for processing. If your geographic location and qualifications make you a good candidate for an opportunity that we have, you will be contacted within three business days. If your qualifications make you a candidate for potential future opportunities, we will keep your contact information on file. Again, thank you for contacting Archivus, and good luck in your job search. - Archivus Management team ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
[XFree86] Please, urgent - I want to recover.
Hi,. I am Dhilepan, from India,. I was intended to get Xmanager ( in Windows ) like a environment for Linux to interact with CDE, some were I found your site link and studied your introduction. There you mentioned xfree86 is for X windows systems. As of I don't have much experience in Linux environment, I have downloaded your xfree86_glib22 for Linux and installed it, but now I am unable to get my previous Linux Desktop. I am getting a login screen, but after login the system takes me to your application ( a xterm, xsm ..). I want to get my old desktop and system functionality, I don't want to work with Xserver, How I could recover the system to old state.I am in trouble. As soon as you see this mail, please respond me,. Thanks in advance,. eagerly waiting for your response, -dhilepan ,. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with Radeon 7000 (Cannot read V_BIOS)
This problem was debated here : http://www.mail-archive.com/xfree86%40xfree86.org/msg00930.html I have it too. I can start X on radeon once, but after that it fails with (EE) RADEON(0): Cannot read V_BIOS I have set the system BIOS to init the other (SiS 6326) gfx card. Any news on this front ? I have i386 (Debian/sarge) Regards, David Balazic ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Xfree configuration problem
Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree configuration problem
1. Can you do /sbin/lspci and post it. 2. Can you do uname -a or uname -r and post it. The 865GV chipset was released after RH 2.1 AS, maybe for some reason it is having difficult in recognizing the video controller. But I doubt it. Anyway, there is a work around that Mark posted a while back. Try Mark's suggestion . A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI 00:02:0 Mauricio Rojas wrote: Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] rebooting failure-
type this command who -r you should see run-level 5 If you don't see it, that means you are not running at run level 5. RH automatically starts xfs at run level 5 You can change your inittab to default to run level 5 id:5:initdefault: Or you can start it manual at your current run level --- /etc/init.d/xfs start Your problem is you don't have font server running. saji kurian wrote: from saji TAS,Bangalore today after a due to power failure the system is went off.after that i try to rebbot it ,it get into booting but i can't go to the GUI mod,after the booting. it show some error while i try to got GUI from text terminal using [EMAIL PROTECTED] root]#startx i using the cluster system having two nodes the report of the problem is attached with this mail. as in the file /var/log/XFree86.0.log i expect a solution through the mail saji bangalore 09/02/05 __ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 --- Name: XFree86.0.log XFree86.0.log Type: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 Description: XFree86.0.log ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Xfree configuration problem
Hello, 1.- here it is the first output 00:00.0 Host bridge: Intel Corporation: Unknown device 2570 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation: Unknown device 2572 (rev 02) 00:1d.0 USB Controller: Intel Corporation: Unknown device 24d2 (rev 02) 00:1d.1 USB Controller: Intel Corporation: Unknown device 24d4 (rev 02) 00:1d.2 USB Controller: Intel Corporation: Unknown device 24d7 (rev 02) 00:1d.3 USB Controller: Intel Corporation: Unknown device 24de (rev 02) 00:1d.7 USB Controller: Intel Corporation: Unknown device 24dd (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82820 820 (Camino 2) Chipset PCI (rev c2) 00:1f.0 ISA bridge: Intel Corporation: Unknown device 24d0 (rev 02) 00:1f.1 IDE interface: Intel Corporation: Unknown device 24db (rev 02) 00:1f.3 SMBus: Intel Corporation: Unknown device 24d3 (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation: Unknown device 24d5 (rev 02) 01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) 2.- the second one Linux demo234.isc.cl 2.4.9-e.3 #1 Fri May 3 17:02:43 EDT 2002 i686 unknown Chao, Mauricio Rojas P. Gerente Producto y Servicio ISC S.A. (http://www.isc.cl) fono: 56 2 2362306 fax: 56 2 2362088 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Bukie Mabayoje Enviado el: Miércoles, 09 de Febrero de 2005 18:00 Para: xfree86@xfree86.org Asunto: Re: [XFree86] Xfree configuration problem 1. Can you do /sbin/lspci and post it. 2. Can you do uname -a or uname -r and post it. The 865GV chipset was released after RH 2.1 AS, maybe for some reason it is having difficult in recognizing the video controller. But I doubt it. Anyway, there is a work around that Mark posted a while back. Try Mark's suggestion . A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI 00:02:0 Mauricio Rojas wrote: Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] HELLO
Heyyy, it's me Kimberly... my fianc=E9 is on business trip=20 you can come and chat with me, i have an online profile...if you want, we= can have a date and get to know each other much closer http://godateinnotime.com/d/b/8.php ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree configuration problem
I have the same chipset you have. And the lspci information is the same as yours. So this is not an hw issue. my X was able to identify the video on Kernel 2.2.20 and 2.4.18. Also, I am running a older version of XFree 4.1.0.1 so it is not XFree issue either. I don't know if demo234.isc.cl 2.4.9-e.3 = Red Hat 2.1 2.4.9-e.3. Anyway did you try Mark's workaround? Mauricio Rojas wrote: Hello, 1.- here it is the first output 00:00.0 Host bridge: Intel Corporation: Unknown device 2570 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation: Unknown device 2572 (rev 02) 00:1d.0 USB Controller: Intel Corporation: Unknown device 24d2 (rev 02) 00:1d.1 USB Controller: Intel Corporation: Unknown device 24d4 (rev 02) 00:1d.2 USB Controller: Intel Corporation: Unknown device 24d7 (rev 02) 00:1d.3 USB Controller: Intel Corporation: Unknown device 24de (rev 02) 00:1d.7 USB Controller: Intel Corporation: Unknown device 24dd (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82820 820 (Camino 2) Chipset PCI (rev c2) 00:1f.0 ISA bridge: Intel Corporation: Unknown device 24d0 (rev 02) 00:1f.1 IDE interface: Intel Corporation: Unknown device 24db (rev 02) 00:1f.3 SMBus: Intel Corporation: Unknown device 24d3 (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation: Unknown device 24d5 (rev 02) 01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) 2.- the second one Linux demo234.isc.cl 2.4.9-e.3 #1 Fri May 3 17:02:43 EDT 2002 i686 unknown Chao, Mauricio Rojas P. Gerente Producto y Servicio ISC S.A. (http://www.isc.cl) fono: 56 2 2362306 fax: 56 2 2362088 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Bukie Mabayoje Enviado el: Miércoles, 09 de Febrero de 2005 18:00 Para: xfree86@xfree86.org Asunto: Re: [XFree86] Xfree configuration problem 1. Can you do /sbin/lspci and post it. 2. Can you do uname -a or uname -r and post it. The 865GV chipset was released after RH 2.1 AS, maybe for some reason it is having difficult in recognizing the video controller. But I doubt it. Anyway, there is a work around that Mark posted a while back. Try Mark's suggestion . A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI 00:02:0 Mauricio Rojas wrote: Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Xfree configuration problem
Yes, I tried it, but it didnt work Could you send your Xfree config file? Regards, Mauricio Rojas P. Gerente Producto y Servicio ISC S.A. (http://www.isc.cl) fono: 56 2 2362306 fax: 56 2 2362088 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Bukie Mabayoje Enviado el: Miércoles, 09 de Febrero de 2005 20:05 Para: xfree86@xfree86.org Asunto: Re: [XFree86] Xfree configuration problem I have the same chipset you have. And the lspci information is the same as yours. So this is not an hw issue. my X was able to identify the video on Kernel 2.2.20 and 2.4.18. Also, I am running a older version of XFree 4.1.0.1 so it is not XFree issue either. I don't know if demo234.isc.cl 2.4.9-e.3 = Red Hat 2.1 2.4.9-e.3. Anyway did you try Mark's workaround? Mauricio Rojas wrote: Hello, 1.- here it is the first output 00:00.0 Host bridge: Intel Corporation: Unknown device 2570 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation: Unknown device 2572 (rev 02) 00:1d.0 USB Controller: Intel Corporation: Unknown device 24d2 (rev 02) 00:1d.1 USB Controller: Intel Corporation: Unknown device 24d4 (rev 02) 00:1d.2 USB Controller: Intel Corporation: Unknown device 24d7 (rev 02) 00:1d.3 USB Controller: Intel Corporation: Unknown device 24de (rev 02) 00:1d.7 USB Controller: Intel Corporation: Unknown device 24dd (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82820 820 (Camino 2) Chipset PCI (rev c2) 00:1f.0 ISA bridge: Intel Corporation: Unknown device 24d0 (rev 02) 00:1f.1 IDE interface: Intel Corporation: Unknown device 24db (rev 02) 00:1f.3 SMBus: Intel Corporation: Unknown device 24d3 (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation: Unknown device 24d5 (rev 02) 01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) 2.- the second one Linux demo234.isc.cl 2.4.9-e.3 #1 Fri May 3 17:02:43 EDT 2002 i686 unknown Chao, Mauricio Rojas P. Gerente Producto y Servicio ISC S.A. (http://www.isc.cl) fono: 56 2 2362306 fax: 56 2 2362088 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Bukie Mabayoje Enviado el: Miércoles, 09 de Febrero de 2005 18:00 Para: xfree86@xfree86.org Asunto: Re: [XFree86] Xfree configuration problem 1. Can you do /sbin/lspci and post it. 2. Can you do uname -a or uname -r and post it. The 865GV chipset was released after RH 2.1 AS, maybe for some reason it is having difficult in recognizing the video controller. But I doubt it. Anyway, there is a work around that Mark posted a while back. Try Mark's suggestion . A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI 00:02:0 Mauricio Rojas wrote: Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree configuration problem
Check my comments in blue... You can find them by searching for BUKIE # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section "Module" # This loads the DBE extension module. Load "dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Load "type1" Load "freetype" # This loads the GLX module # Load "glx" EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # BUKIE1: You may run into problems here. If you don't have all the fonts. # Note: I don't run xfs that is why you didn't see FontPath "unix/:7100" # It is required for Red hat # The module search path. The default path is shown here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ** # Server flags section. # ** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # Option "NoTrapSignals" # Uncomment this to disable the Crtl>Alt>BS> server abort sequence # This allows clients to receive this key event. # Option "DontZap" # Uncomment this to disable the Crtl>Alt>KP_+>/KP_-> mode switching # sequences. This allows clients to receive these key events. # Option "Dont Zoom" # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # Option "DisableVidModeExtension" # Uncomment this to enable the use of a non-local xvidtune client. # Option "AllowNonLocalXvidtune" # Uncomment this to disable dynamically modifying the input
