Re: SiliconMotion - unable to restore VGA screen on exit
[EMAIL PROTECTED] writes: What is the status of the problem of being unable to restore the VGA screen using the SiliconMotion drivers? Bugzilla 124 702 have reported the problem. Some comments indicate there is a working patch, while some comments (and my experience) indicate that the problem still exits, even using the latest 4.3.99.x XFree86. It's not clear if anyone is actively working on the problem. I would add that in my case, using a Panasonic CF-28 ToughBook (laptop), the problem exists using Solaris 8 and 4.3.99.x XFree86, but does NOT exist using RedHat Linux with 4.2 XFree86 on the same machine. Also, as I reported in Bugzilla 702, using Solaris 8 and 4.0.2 XFree86 Porting Kit, I did not have the problem either. I would have fixed this problem long ago if I could reproduce it on Linux. I have dug out my Lynx3D evaluation board just recently to see if I can reproduce this problem however I don't see it. It is fairly hard to fix a problem that I don't see. If you could describe the problem a little closer one may get an idea: - Dose the monitor sync at all when you go back to text mode? - Is this a video mode restoration problem? (Do you get the same frequencies on the text console as you had before you started X?) - Are you using a 'real' text mode (or is this something like a framebuffer mode under Linux)? - Is it a font loading problem (under linux you can load a new font by doing setfont ... to test this)? - Is it a pallette problem (ie that you get black on black)? Under linux the VGAlib had some tools to save/restore the VGA palette. I would appreciate feedback on any planned efforts on this problem. If any XFree86 Developer in the LA area needs to look at my machine, I may be able to accommodate them to get this problem solved. I don't know if there is any XFree86 Developer in the LA area. In fact there may by fewer XFree86 Developer around the world than you expect. It seems to be a popular misconception that this project has hundreds of active developers. Egbert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: SiliconMotion - unable to restore VGA screen on exit
On Fri, 10 Oct 2003 [EMAIL PROTECTED] wrote: What is the status of the problem of being unable to restore the VGA screen using the SiliconMotion drivers? The status of the problem is whatever the bug report states. If it doesn't state what you'd like to hear, then that is because nobody has anything to comment as of yet about the report(s), and nobody is likely investigating the problem. Bugzilla 124 702 have reported the problem. Some comments indicate there is a working patch, while some comments (and my experience) indicate that the problem still exits, even using the latest 4.3.99.x XFree86. It's not clear if anyone is actively working on the problem. The bug is reported against XFree86 4.3.0 on ia32. I doubt there are many people who: 1) Even have silicon motion hardware 2) Have the hardware you are having problems with 3) Are running NetBSD 4) Can reproduce your problem 5) Have had the time and interest in investigating the issue. I would add that in my case, using a Panasonic CF-28 ToughBook (laptop), the problem exists using Solaris 8 and 4.3.99.x XFree86, but does NOT exist using RedHat Linux with 4.2 XFree86 on the same machine. Also, as I reported in Bugzilla 702, using Solaris 8 and 4.0.2 XFree86 Porting Kit, I did not have the problem either. If 4.2.x works for you, why don't you just continue using 4.2.x? Or alternatively, extract a binary 4.2.x driver module from the older release and rename the 4.3.0 driver and plop the old one that worked in its place. I would appreciate feedback on any planned efforts on this problem. If any XFree86 Developer in the LA area needs to look at my machine, I may be able to accommodate them to get this problem solved. Everyone working on XFree86 does so as a volunteer. When people report bugs, if there is a volunteer who works in that area of code, be it a library, the X server, or a driver module, etc. and they have the time and inclination, and the problem interests them to fix, they generally respond to reports and fix them. If you display all bug reports, you'll notice the majority of them are fixed and closed. Since this issue is open still, that possibly means nobody is interested in hacking on an ancient video driver for ancient video hardware, so the bug stays open until someone comes along and volunteers to fix it, and submits a patch. That could well be an existing XFree86 developer, or someone such as yourself. More likely than not however, whoever fixes it (if it ever does get fixed) will be someone who actually has the hardware themselves. There really aren't enough volunteer developers out there to endlessly maintain every single video driver and keep it working on every piece of video hardware, and respond to problem reports instantly and fix all issues and fix them quickly. If you're unable to fix the problem yourself and submit a patch onto that bug report, you might find my previous suggestion of using the 4.2.1 video driver in 4.3.0 to be a useable workaround for now. Hope this helps. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: SiliconMotion - unable to restore VGA screen on exit
On Sat, 11 Oct 2003, Egbert Eich wrote: I would appreciate feedback on any planned efforts on this problem. If any XFree86 Developer in the LA area needs to look at my machine, I may be able to accommodate them to get this problem solved. I don't know if there is any XFree86 Developer in the LA area. In fact there may by fewer XFree86 Developer around the world than you expect. It seems to be a popular misconception that this project has hundreds of active developers. Another popular misconception that people have is that the developers that are actually working on the code have endless hours to volunteer, and each have a warehouse containing one of every piece of video hardware ever made including one of every laptop, as well as complete technical specification of all of that hardware, and that fixing bugs even in _ancient_ hardware is a high priority for them. ;o) It's kindof funny... Once in a while I get a rude response on a bug report from someone along the lines of Um.. Is *ANYONE* looking at this??? Is there any MOVEMENT on this?? *WHAT* do I need to do to get this problem fixed IMMEDIATELY?? Of course I rarely respond, but the answer I'm thinking in my mind - the true answer, is You need to go backwards in time, and remove your last comment from the bug report so that when time moves forward again, I have never seen it. Then you need to send me $1. ;o) -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
dual head different resolutions
Hi all! I'm not the XFree developer, but there Is important feature lacking. Thi is support for different resolution in dual head mode with functionality like big desktop mode in Windows XP. I use fglrx ati 3.2.5 driver. I have flatpanel 1280x1024 and TVset 800x600 connected to the Radeon 9000 PRO. In KDE and Gnome I lost half of the bottom bar and Start Menu. The windows maximizes to both of sceen, not to only one (e.g. TV screen). When I turn on the Xinerama extension if XF86config-4 the driver does not work. I've read that ati drivers have merged fb functionality, but I don't know how to turn it on and if it works with two different resolutions in KDE and Gnome. I've been searching for thread about this feature in devel mailing list, but I found some threads, more or less close to that. My idea/suggestion is to implement that feature to the XFree. The 4.4 feature freeze is coming soon, so maybe it is possible in the next release. Darek Borkowski ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: dual head different resolutions
I've never used ati's fireglx drivers so I can't comment on how they work. Plus since they are closed source binary only drivers, opensource developers cannot add any new features. if you want a xinerama like feature, ask ati directly. I maintain the mergedfb functionality in the xfree86 opensource radeon driver. Mergedfb creates a single large framebuffer with two viewports (the heads) looking into it. the xfree86 driver does not support tv-out yet on radeon hardware. However with mergedfb, you can use the vga and dvi ports to create a dualhead desktop. the driver also implements pseudo-xinerama which allows xinarama-aware apps to act as expected in a dualhead setup. For more information please see my radeon man page or Thomas Winischhofer's sis page: http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/final/radeon.4.html http://www.winischhofer.net/linuxsisvga.shtml I committed Mergedfb support to DRI cvs and it is available in the DRI snapshots: http://dri.sourceforge.net/snapshots/ Alex --- Darek Borkowski [EMAIL PROTECTED] wrote: Hi all! I'm not the XFree developer, but there Is important feature lacking. Thi is support for different resolution in dual head mode with functionality like big desktop mode in Windows XP. I use fglrx ati 3.2.5 driver. I have flatpanel 1280x1024 and TVset 800x600 connected to the Radeon 9000 PRO. In KDE and Gnome I lost half of the bottom bar and Start Menu. The windows maximizes to both of sceen, not to only one (e.g. TV screen). When I turn on the Xinerama extension if XF86config-4 the driver does not work. I've read that ati drivers have merged fb functionality, but I don't know how to turn it on and if it works with two different resolutions in KDE and Gnome. I've been searching for thread about this feature in devel mailing list, but I found some threads, more or less close to that. My idea/suggestion is to implement that feature to the XFree. The 4.4 feature freeze is coming soon, so maybe it is possible in the next release. Darek Borkowski __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Dri-devel] Deadlock with radeon DRI
On Fri, 10 Oct 2003, Keith Whitwell wrote: Date: Fri, 10 Oct 2003 21:55:57 +0100 From: Keith Whitwell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: DRI Devel [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii; format=flowed Subject: Re: [Dri-devel] Deadlock with radeon DRI John Dennis wrote: The locking problem is solved, my original analysis was incorrect. The problem was that DRM_CAS was not correctly implemented on IA64. Thus this was an IA64 issue only, this is consistent with others who showed up in a google search describing the problem, all were on IA64. I have filed an XFree86 bug report on this. I could not find a DRI specific bug reporting mechanism other than the dri-devel list. This list is good. Can you put together a patch to correct the behaviour? http://bugs.xfree86.org/show_bug.cgi?id=778 has John's patch that fixes this. Thanks Keith, TTYL -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
