Re: [XFree86] problems report
On Mon, Apr 18, 2005 at 01:00:43PM +0200, Youkun Gao wrote: >VIDEO DRIVER: > >Neomagic nm2200 > >OPERATING SYSTEM: > >Red Hat Linux release 9 (shrike) >kernel 2.4.20-8 on an i686 > >VIDEO CARD: > > >MODEL: > >Compaq presario 1925 (laptop integrate video card) > >GRAPHICS CHIPSET: > >MagicMedia 256AV > >VIDEO MEMORY: > >2MB DRAM > >BUS TYPE: > >PCI > >REPORT: >i can not enter the graphic surface only the text, and the it shows >Error: open /dev/fb0 : no such device >could not init font path element /usr/X11R6/lib/X11/fonts/speedo, removing >from list! >could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing >from list! Assuming that you are using automatic configuration, none of these are fatal errors. Can you send the complete /var/log/XFree86.0.log file? David ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] server crash
On Thu, Apr 07, 2005 at 11:42:39AM -0400, Sean Hamilton wrote: >Fatal server error: >Cannot run in framebuffer mode. Please specify busIDsfor all >framebuffer devices It looks like autoconfig's fbdev fallback needs some refinement. Either create a static configuration based on what is shown in the log file, modified to use either the fbdev or vesa drivers, or run with the command line option '-screen "Builtin Default vesa Screen 0"' to explicitly specify use of the vesa portion of the automatically generated configuration. David ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Vmware 5.0.0 build-13124 autoconfigure did not work using XFree86 Version 4.5.0
On Thu, Apr 14, 2005 at 04:14:10AM -0700, David Nicholson wrote: >I am having problem trying to use XFree86 Version 4.5.0. This is >installed on Solaris 9 u7 x86 hosted > >on a Vmware 5.0.0 build-13124. Attached Xfree86.0.log and DxDiag.txt > >(--) PCI: (0:15:0) VMware Inc [VMware SVGA II] PCI Display Adapter rev 0, Mem >@ 0xf000/27, 0xec00/23, I/O @ 0x14e0/4 >(II) AutoConfig: Primary device is not PCI. I've run XFree86 4.5.0 on Solaris 8, hosted on vmware 3 running on Linux, and it worked correctly. From your XFree86 log, it looks like something isn't quite as expected with how the vmware video hardware appears on the PCI bus. >(II) PCI: 00:0f:0: chip 15ad,0405 card 15ad,0405 rev 00 class 03,00,00 hdr 00 >(--) PCI: (0:15:0) VMware Inc [VMware SVGA II] PCI Display Adapter rev 0, Mem >@ 0xf000/27, 0xec00/23, I/O @ 0x14e0/4 >(II) AutoConfig: Primary device is not PCI. For comparison, I get (Solaris 8, vmware 3): (II) PCI: 00:0f:0: chip 15ad,0405 card , rev 00 class 03,00,00 hdr 00 (--) PCI:*(0:15:0) VMware Inc [VMware SVGA II] PCI Display Adapter rev 0, Mem @ 0xfc00/24, 0xfb00/24, I/O @ 0x10a0/4 (II) AutoConfig: Primary PCI is 0:15:0 Can you run 'scanpci -v' as root on the Solaris 9 install immediately after it boots up? That may show why XFree86 is not identifying a primary device. The error preventing the fallback vga driver from working may well be related: Fatal server error: A driver tried to allocate the Block Memresource at 0xa:0xa which conflicted with another resource. Send the output of the server to [EMAIL PROTECTED] Please specify your computer hardware as closely as possible. David ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] mailing list updates
The XFree86 mailing lists have been modified on an experimental basis to require subscription for posting. Perhaps this will be enough to eliminate the < 0.1% of spam that our existing filtering does not already catch. The existing filtering (spam assassin plus a home-grown filter) will remain in place. If this does not prove effective, or if the list admin burden increases signficantly (i.e., posters do not subscribe), then the behaviour may be reverted. David ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] (no subject)
I need for your help, my computer spesification athlon xp 2500+ abit nf7 ati radeon 7500. linux mandrake 9.2 when i start my computer I am not font kde desktop, I enter command $startx and I have found icewm desktop not kde what my i do ? thank a lot Akses Internet TELKOMNet-Instan beri Diskon s.d. 50 % khusus untuk wilayah Jawa Timur. Informasi selengkapnya di www.telkomnetinstan.com atau hub 0800-1-INSTAN (467826) XFree86.0.log Description: Binary data
Re: [XFree86] mouse stopped working
>In the middle of a session the mouse became unresponsive, CPU went to >100%, and eventually the cursor disappeared completely. Try finding more about the failure seeing wich process is tearing up the CPU (using 'top' is good). I think many kinds of failures may stop the mouse as a side effect... ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Fwd: Dials and Buttons (SGI)
hi, everybody, I have got "Dials and Buttons" by SGI and I want to install it under linux. Are they supported? Do you know whether I have to declare it in section "InputDevice" in file "/etc/X11/Xorg.conf"? Which driver do I need? Do I need options? Can I test the Dials and Buttons? Many thanks. Ruediger ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] mouse movement
I'm not sure this is the proper list, but perhaps someone can offer assistance. I'm writing a program that I want to be able to move the mouse pointer on screen (preferably independent of window manager). I couldn't find a way to do this from within X, so I created a named pipe and set X to read from it as a second mouse with the same protocol as my physical mouse (IMPS/2). I cat'd /dev/input/mouse0 to a file while performing some simple mouse actions (cliking the buttons then moving in a square) and wrote a program to write that 3 bytes at a time to /dev/input/mouse0 to see if it would reproduce the movements, instead the pointer flailed about wildly and went semi-unresponsive (the pointer would still move, but mouse and keyboard input would only go to the window with focus, which couldn't be changed--it's as if the mouse input was still waiting for a missing byte or something). Probably writing the bytes so quickly caused acceleration in the mouse driver to kick in, which would explain the jumpy movements, but it doesn't explain the semi-unresponsiveness. I've also tried doing things like echo -e '\000\020\000' > /dev/input/mypipe which succeeds in moving the pointer either up or to the left, but I can't do mouse clicks or move down or to the right, even if I echo, say, the 3 bytes that were produced in /dev/input/mouse0 when I right clicked. Does anyone have a suggestion as to a better way to proceed? Are there functions either in X or gnome/kde that would be better suited to this? Thanks, -- Eric Zilli Hasselmo Lab - Computational Neurophysiology Center for Memory and Brain Boston University 2 Cummington St. Boston MA, 02215 www.digfarenough.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
