[Xpert]Disable virtual console switching
Is there a server flag in XF86Config or other option that will disable the Control-Alt-Fn virtual console switching for XFree86-3.3.6 under Linux 2.2.x Many thanks Mark ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert](no subject)
Hi there, I have recently bought a Toshiba Satellite 1800-S204 laptop that comes with a `trident cyberbladeXPAi1' card. I installed RedHat 7.0 that came with XFree86-4.0.1 and it did not recognize the card. I upgraded to XFree86-4.1.0 but no improvement. Since I noticed that support for this card was added to the soon to be released XFree86-4.2.0, I downloaded the latest CVS from December 4 and the compiling and installation seemed to be all right. However, by running `XFree86 -configure' I could only get one mode and it is not usable, since I get a small frame in which I seem to recognize the default 'net-style' X background with a ghost-like mouse pointer. Nevertheless the card is correctly identified as one can see from the log-file included below. Does anybody have any idea of what went wrong? Did I make some mistake somewhere or is there any setting that I could change in order to get a usable picture? Hopefully the included log-file may help those who know more about this to understand what is going on. By the way, one more thing, `startx' quit working after installation of the new CVS. After typing it I get the following error message: xauth: error while loading shared libraries: LibXmuu.so.1: cannot open shared object file: No such file or directory. I wonder what that means since the file LibXmuu.so.1 actually exists. Does anybody have any idea of how to fix this? Thanks a lot Gabriele Included XFree86.0.log This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.99.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: xx November 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.2.16-22 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Wed Dec 5 23:12:12 2001 (++) Using config file: XF86Config.new Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.1.99.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.1.99.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 10b9,1644 card , rev 01 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 10b9,5247 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 10b9,5237 card 1179,0004 rev 03 class 0c,03,10 hdr 00 (II) PCI: 00:04:0: chip 10b9,5229 card 1179,0004 rev c3 class 01,01,f0 hdr 00 (II) PCI: 00:06:0: chip 10b9,5451 card 1179,0001 rev 01 class 04,01,00 hdr 00 (II) PCI: 00:07:0: chip 10b9,1533 card 1179,0004 rev 00 class 06,01,00 hdr 00 (II) PCI: 00:08:0: chip 10b9,7101 card 1179,0001 rev 00 class 06,80,00 hdr 00 (II) PCI: 00:0a:0: chip 8086,1229 card 1179,0001 rev 0d class 02,00,00 hdr 00 (II) PCI: 00:11:0: chip 1179,0617 card , rev 32 class 06,07,00 hdr 82 (II) PCI: 00:11:1: chip 1179,0617 card , rev 32 class 06,07,00 hdr 82 (II) PCI: 01:00:0: chip 1023,8820 card 1179,0001 rev 82 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci:
Re: [Xpert]sis-630/lcd with newest xfree cvs
Andre Werthmann writes: With the old version of the driver the LCD wasn't initialized (it slowly has gone white). I have connected a Monitor to vga out and everything displayed ok there. OK. What happens if you run VESA framebuffer and start the Xserver with SiS driver on top? Please try a mode that has the same resolution and depth as the mode in X. I have not tried 8bpp yet, I'll do soon. OK. Could you please get the exact message (or the log file)? I have written a log file, but at my fault I deleted it while deleting the xc source. I'll compile it again and send you the logfile. OK, thanks! Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
Egbert Eich: Rune Petersen writes: sorry had a lot on my mind... Doesn't work means: all except the topmost cm. is flickering between showing about 1/4 of the actual image (also looks streched vertically) and showing black. I' have tried without Framebuffer and got the same result. Hm, doesn't sound too good. The problem about the sis driver is: We have no decend documentation for the SiS 630. Even if we did we'd have a hard time: the code that sets up the chip was provided by SiS. What they did was very simple: they translated their i86 machine language BIOS code to C. The code looks horrible! It retreives register values from tables in the BIOS and writes them to the chip. It is very likely that later versions of the BIOS do some things the BIOS that served as base for this code didn't do. What happened when you used the old driver - without my patches? Regards, Egbert. The old drivers made the screen all white, to get it to work I had to patch the drivers so they didn't setup the LCD, an then use the VESA framebuffer to setup the display. I have no experience in this but the VESA framebuffer (as far as I know) uses the BIOS to setup the LCD and that works for me, any chance the same can be done with these drivers? or have I gotten it all wrong? Rune Petersen ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]People working on Geode/CS5530 in XFree86 4.x?
National produce Linux drivers for the Geode/CS5530 for both XFree86 4 and 3.3.6, as well as native mode audio drivers (rather than SB emulation that you note on your web page). My understanding is that they are only available to companies NDA with National Semi. Interesting - I wondered where NS's drivers went (they used to be on a publicly-accessible web page; I should have downloaded them while I had a chance). So I guess I'm on my own then. I don't want to get the legal behemoth lumbering on establishing a relationship with NS, because we don't buy anything directly from them and we have no intention of tying ourselves to their hardware - at the moment it's cheap and does what we want, but we can and will switch to other SBC architectures as our needs vary. Thanks for the info. I guess I will try some simple hacks on the mediagx driver to at least get 4.x working, and I'll release a patch if I do get it working. -- Lewin A.R.W. Edwards Embedded Engineer, Digi-Frame Inc. Work: http://www.digi-frame.com/ Tel (914) 937-4090 9am-6:30pm M-F ET Personal: http://www.larwe.com/ http://www.zws.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Unsupported X Windows visual
Hello, sorry if bother you with a trivial question, i'm using XFree 4 on slackware 8.0, when trying to execute a remote session of IDL (on a unix machine) i get this error: % Unsupported X Windows visual (class: StaticGray, depth: 0). Substituting default (class: UndefinedVisual, Depth: 0) any simple solution? thanks a lot for your attention Andrea Miglio ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
Rene Rebe writes: For the newer sis chips / bios version we had to disable the mode-switching and let the VESA-framebuffer initialize the chip. - I spend many hours debugging in the stupid sis_bios.[h,c] ... , too. I have a short info page: http://www.tfh-berlin.de/~s712059/sis630/index.html I've looked at it - you only offer binary drivers. However I think I know what you do. Your patch is pretty similar to the VESAFbHack patch posted a while ago. I'm thinking of something different: sis_bios.c is converted BIOS code anyway. Since we have the int10 infrastructure we can use it to run the real BIOS and eliminate much of the code in sis_bios.c. I tryed to get docu from sis - even considering signing a NDA - but suddely the email thread with them stopped ... ? - They so not seem to be interessted in getting they chip to work properly under Linux ... :-( I would certainly love to have better docs for the graphics part of the 630 than there are in the 630 datasheet. Egbert. -- Egbert Eich XFree86 Core Team SuSE GmbH [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
On Thu, 6 Dec 2001 19:01:19 +0100 (MET) Egbert Eich [EMAIL PROTECTED] wrote: Rene Rebe writes: For the newer sis chips / bios version we had to disable the mode-switching and let the VESA-framebuffer initialize the chip. - I spend many hours debugging in the stupid sis_bios.[h,c] ... , too. I have a short info page: http://www.tfh-berlin.de/~s712059/sis630/index.html I've looked at it - you only offer binary drivers. However I think I know what you do. Your patch is pretty similar to the VESAFbHack patch posted a while ago. I'm thinking of something different: sis_bios.c is converted BIOS code anyway. Since we have the int10 infrastructure we can use it to run the real BIOS and eliminate much of the code in sis_bios.c. Yes. Exactly. I'm no binary only fan, too - but it was a one-minute hack and I deleted the source ... - it is so simply that I did not reworked it. The direct BIOS call came to my mind, too. - The current code is a bad joke. Fideling with all the defines and defines of defines are completely unfollowable ... - and sometimes they use the set_reg methods sometimes direct ins outs (even with hardcoded hex-values) ... a horror! I tryed to get docu from sis - even considering signing a NDA - but suddely the email thread with them stopped ... ? - They so not seem to be interessted in getting they chip to work properly under Linux ... :-( I would certainly love to have better docs for the graphics part of the 630 than there are in the 630 datasheet. Maybe I can try to write to the german reseller (Helped to get Avision's scanner specs ;-) - and if that doesn't help ask www.heise.de (or /.) to publish some sis slows down XFree driver development for a year, now ... It is interesting that the [EMAIL PROTECTED], [EMAIL PROTECTED] (the PR adresses I used some weeks ago) seems to be removed ... ?? [EMAIL PROTECTED] - is the one I had the discussion about getting docs under a NDA ... Egbert. -- Egbert Eich XFree86 Core Team SuSE GmbH [EMAIL PROTECTED] [EMAIL PROTECTED] k33p h4ck1n6 René -- René Rebe (Registered Linux user: #248718 http://counter.li.org) eMail:[EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.tfh-berlin.de/~s712059/index.html Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident cyberbladeXPAi1
Egbert, 4. One should consider this when looking for a new system (especially a laptop): It may be a good idea to look around and see which HW is already known to be supported. Humm, this is exactly what I've done (I'm quite used to Linux, running it exclusively since 1994). And, guess what, if you look at Trident web site (www.tridentmicro.com) and look for the CyberBladeXPAi1, it's supposed to be tested and certified on Windows 98, ME, 2000, XP *and* Linux (Look at the bottom of their page, this is what they say) Actually, this is why I've choosen that particular laptop ! Crazy, isn't it ? Take care, Olivier. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
On Thu, 6 Dec 2001 18:50:57 +0100 (MET) Egbert Eich [EMAIL PROTECTED] wrote: Rune Petersen writes: The old drivers made the screen all white, to get it to work I had to patch the drivers so they didn't setup the LCD, an then use the VESA framebuffer to setup the display. Guess how I debugged the sis_bios.c code. I enabled the VESA framebuffer, removed parts of the initialization in sis_bios.c until I found the code that broke it. ;-( - Same here. For me sis_bios.c: static Bool SetCRT2Group(UShort BaseAddr,ULong ROMAddr,UShort ModeNo, ScrnInfoPtr pScrn) Breaks the settings. If I leave it away or hardcode IF_DEF_LVDS and IF_DEF_CH7005 it did not destroyed the chip-setting. (I do not remember the exact combination of it - and it did not worked itself - the VESA-framebuffer had still to init the right mode - but the driver did not destroyed it) - I also tryed to analyse some reg-dumps - but never had time to finish it. This is a bit tricky. Most initialization functions in sis_bios.c depend on variables set by the previous functions called. One cannot just remove them at random but rather work his way up from the bottom. As I said already: this funtion contains x86 BIOS code converted to C. This is how this code looks like, too. [...] k33p h4ck1n6 René -- René Rebe (Registered Linux user: #248718 http://counter.li.org) eMail:[EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.tfh-berlin.de/~s712059/index.html Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
Ok, this is my (working) setup Laptop: Gericom Webgine, SIS630 (rev 49) Modeline: 1024x768 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync Depth: 16 bpp No framebuffer. 3D acceleration still doesn't work even after a full reinstall, I get SIS driver : out of video memory Fatal errors in sis_dri.so When I run a Mesa executable like gears. No chance incrementing the video memory. Hope this helps, alfredo On Dec 4 Rune wrote: Hi, It's great it works for you!! Any chance you are interested in helping me find out what works, and what doesn't? Can you give me your setup? Mine that doesn't work: Laptop:Uniwill 340S2 resolution:1024x768 framebuffer: VESA modeline: 65.1 1024 1032 1176 1344 768 771 777 806 +hsync +vsync Date: Tue, 4 Dec 2001 09:03:59 +0100 (CET) From: Braunstein Alfredo To: [EMAIL PROTECTED] Subject: [Xpert]SiS630 and LCD Hi there, It' is better, no more white screen, but its flickering black/white with 4 black vertical bands.. at least its an improvement, no more boring white. Rune Petersen and - Original Message - From: Egbert Eich [EMAIL PROTECTED] To: Rune Petersen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, December 02, 2001 1:05 PM Subject: Re: [Xpert]Egbert Eich did you fix alle the LCD problems in the SIS-630? Rune Petersen writes: straight forward question: Can I use the new drivers on my labtop? Well... I've got one report where the SiS 630 works better now. I however cannot promise anything. I have no detailed specs for the SiS 630 and therefore a lot of the things I did were pure guess work. However you may want to give it a try... Egbert. Hi, For me is working perfectly now. Even VESA blank is working, which wasn't before! The only thing is that 3D acceleration seems not to work anymore for me (it worked but with some glitches), but I think It may be due to an installation problem: I've only replaced sis_drv.o instead of a full reinstall. For now I'm ok without it! Thank you very much keep up the good work, alfredo A l f r e d o B r a u n s t e i n [EMAIL PROTECTED] Beam me up, Scotty! It ate my phaser! ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
Egbert Eich writes: Rene Rebe writes: For the newer sis chips / bios version we had to disable the mode-switching and let the VESA-framebuffer initialize the chip. - I spend many hours debugging in the stupid sis_bios.[h,c] ... , too. I have a short info page: http://www.tfh-berlin.de/~s712059/sis630/index.html I've looked at it - you only offer binary drivers. However I think I know what you do. Your patch is pretty similar to the VESAFbHack patch posted a while ago. I'm thinking of something different: sis_bios.c is converted BIOS code anyway. Since we have the int10 infrastructure we can use it to run the real BIOS and eliminate much of the code in sis_bios.c. Theres only one problem with int10 is that it does an segment fault when int10 initialises (at least for me). see attachment... I tryed to get docu from sis - even considering signing a NDA - but suddely the email thread with them stopped ... ? - They so not seem to be interessted in getting they chip to work properly under Linux ... :-( I would certainly love to have better docs for the graphics part of the 630 than there are in the 630 datasheet. Egbert. -- Egbert Eich XFree86 Core Team SuSE GmbH [EMAIL PROTECTED] [EMAIL PROTECTED] XFree86.0.log Description: Binary data
Re: [Xpert]Trident cyberbladeXPAi1
Egbert, and Olivier 4. One should consider this when looking for a new system (especially a laptop): It may be a good idea to look around and see which HW is already known to be supported. Humm, this is exactly what I've done (I'm quite used to Linux, running it exclusively since 1994). And, guess what, if you look at Trident web site (www.tridentmicro.com) and look for the CyberBladeXPAi1, it's supposed to be tested and certified on Wind ows 98, ME, 2000, XP *and* Linux (Look at the bottom of their page, this is wh at they say) Actually, this is why I've choosen that particular laptop ! Crazy, isn't it ? snip Me too, AND if you look at the Linux Laptop Website in the Toshiba section there is a report from the owner of a -254 IIRC and although he had problems They did not seem insurmountable with a current release of XFree86, and all the information I could find seemed to indicate the graphics path were the same between the -254 and the -274 which influenced me to acquire the -274, (Along with the reasonable price at which Fry's were offering the -274). So I got the thing and the truth is out. Go figure! So I guess my question is, How long until the release of XFree86 4.2? In the meantime I finally will have to dig in and learn cvs. :-) dlg PS: I do not know about the -204 but except for the little bump in the X Windows road I am pretty happy with the -274. I do hate booting up XP (gag,hack) just to see the display in all its beauty. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]BadValue mager opcode failed request :89 (Solved
On Wed, 5 Dec 2001, Ba la wrote: Hi All, Thanks for all, Bad Alloc problem was solved. one of the integer value is out of range that why the problem. According to the man page you are trying to store pixels in cells that don't exist. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
On Thu, 6 Dec 2001, Mark Swan wrote: Hi, Does anybody know of an implementation of X which can run a GNOME or KDE desktop in portrait mode, i.e. rotated 90 degrees under Linux? Specifically, I'm looking for it to work with an Intel 810e adapter chipset, but would be interested to hear of any rotation/transform X developments... Many drivers have Rotate options. Eg, from the nv driver man page: Option Rotate CW Option Rotate CCW Rotate the display clockwise or counterclockwise. This mode is unaccelerated. Default: no rotation. Last I checked, the i810 didn't support this, however. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Mouse problems
This is a well-known problem. Either the switch resets the protocol in a way the driver doesn't understand or it results in junk during the switch and the driver can't deal with that because it doesn't have any error checking code. This won't get fixed until somebody volunteers to look into it and fix it. For starters, somebody needs to investigate what exactly happens to the signal during switches. Mark. On Thu, 6 Dec 2001, John Magrini wrote: Hello, I have a microsoft intellimouse explorer and a belkin ps2 kvm, my X is setup to use psaux for mouse information. X is setup like this Section InputDevice Identifier Mouse0 Driver mouse Option Protocol ExplorerPS/2 Option Device /dev/mouse Option Buttons 7 Option ZAxisMapping 6 7 EndSection im using debian sid. and X free 4.1.0.1 MY PROBLEM I switch between windows2k and X windows, but whenever i switch back to X my mouse is all scrambled and making very odd movements, it seems to be out of sync. This can be fixed if i switch to a console and then switch back to X. this also does not happen if im in a console when i switch back to my linux box. so basically anytime i switch to X from a console everything is fine. but when i switch directly to X from my other computer my mouse is scrambled. (this does not happen switching into windows btw). IM wondering if there is a way to resync the mouse with a hotkey or something, perhaps alittle script thats executed with a hotkey. its very bothersome to have to switch back and forth to console to change computers. any help would be appreciated. Thanks alot John ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]The use of VideoTimerCallback in Xv?
On Thu, 6 Dec 2001, hzeng wrote: Hi, In many Xv driver, there are the founction VideoTimerCallback. At the end of PutImage and PutVideo, the function is used, but I don't know what is the use of the founction and how to use the function? It gives you an opportunity to free the video surfaces at some time later, rather than immediately. In case somebody starts and stops video you can delay freeing the initial surface for a few seconds. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Unsupported X Windows visual
On Thu, 6 Dec 2001 [EMAIL PROTECTED] wrote: Hello, sorry if bother you with a trivial question, i'm using XFree 4 on slackware 8.0, when trying to execute a remote session of IDL (on a unix machine) i get this error: % Unsupported X Windows visual (class: StaticGray, depth: 0). Substituting default (class: UndefinedVisual, Depth: 0) The message doesn't make any sense. There aren't any depth 0 visuals. I assume this means that IDL can't run in whatever depth you are running on your XFree86 machine. IDL probably only supports depth 8 (PseudoColor) and depth 24 (TrueColor), and maybe only the depth 8 visuals. If you are running in depth 16, that's likely the problem. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
In article [EMAIL PROTECTED] Mark wrote: Many drivers have Rotate options. Eg, from the nv driver man page: Option Rotate CW Option Rotate CCW Rotate the display clockwise or counterclockwise. This mode is unaccelerated. Default: no rotation. Coincidentally, I just tried this last night with my TNT2 and XFree86 4.1.0. It didn't work well at all. The hardware cursor seemed pretty badly confused and there were weird dead areas on the screen containing garbage and portions of the root weren't visible no matter how I panned around. Dragging windows caused all sorts of corruption and glitching. -Jeremy. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Help with CyberBladeXPAi1 (Trident) on a Toshiba 1800-814 laptop
Egbert If trident works it is better as it is accelerated. Vesa uses the BIOS and allows mode switching - but it is unacceled. It may still have quirks. fbdev is so simple it should always work - but unaccelerated. I think I may have found something interesting (thus I copy the list ;-) 1) Using Vesa driver works. 2) Passing vga=790 or vga=791 or even vga=792 at linux kernel and using Trident driver *works* but it's very slooow, a lot slower that Vesa driver, in 24bpp and 16bpp -I didn't try 8bpp- 3) Never use vga=xxx and Vesa XFree driver all together. It seems to be dangerous for the LCD display (use either normal textmode with XFree Vesa driver or fb text mode with XFree trident driver, but *not* fb text mode and Vesa driver !) What's puzzling me is why the trident driver with vga=xxx is so slow. I include my XF86Config file so you can check and see by yourself (note that I define all 3 devices, vesa, trident and fbdev and select the one I want by uncommenting the right line in the screen section) Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files FontPath unix/:7100 EndSection # Module loading section Section Module Load dbe # Double-buffering Load GLcore # OpenGL support Load dri # Direct rendering infrastructure Load glx # OpenGL X protocol interface Load extmod # Misc. required extensions # Load v4l # Video4Linux # Load pex5 # PHIGS for X 3D environment (obsolete) # Load record# X event recorder # Load xie # X Image Extension (obsolete) # You only need the following two modules if you do not use xfs. # Load freetype # TrueType font handler # Load type1 # Adobe Type 1 font handler EndSection Section InputDevice Identifier Keyboard0 Driver keyboard Option XkbLayout fr EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Device /dev/mouse Option Protocol PS/2 Option Emulate3Buttons on Option ZAxisMapping 4 5 EndSection Section Monitor Identifier My Monitor VendorName Unknown ModelName Unknown HorizSync 31.5 - 48.5 VertRefresh 50-70 Option dpms EndSection Section Device Identifier * Generic VESA compatible Driver vesa BoardName Unknown Option UseFBDev EndSection Section Device Identifier Linux Frame Buffer Driver fbdev BoardName Unknown EndSection Section Device Identifier Trident Driver trident BoardName Unknown Option NoAccel false Option ShadowFB false BusID PCI:1:0:0 Option CyberStretch false Option CyberShadow true Option ShadowFB true EndSection Section Screen Identifier Screen0 Device * Generic VESA compatible #Device Linux Frame Buffer #Device Trident Monitor My Monitor DefaultDepth 16 Subsection Display Depth 24 Modes 1024x768 800x600 640x480 EndSubSection Subsection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection Subsection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section DRI Mode 0666 EndSection ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
On Thu, 6 Dec 2001, Jeremy Sugerman wrote: In article [EMAIL PROTECTED] Mark wrote: Many drivers have Rotate options. Eg, from the nv driver man page: Option Rotate CW Option Rotate CCW Rotate the display clockwise or counterclockwise. This mode is unaccelerated. Default: no rotation. Coincidentally, I just tried this last night with my TNT2 and XFree86 4.1.0. It didn't work well at all. The hardware cursor seemed pretty badly confused and there were weird dead areas on the screen containing garbage and portions of the root weren't visible no matter how I panned around. Dragging windows caused all sorts of corruption and glitching. Ugh, I haven't tried this stuff in a long time. It looks like somebody broke all of this stuff. I doubt the problems are specific to the nv driver. I'll look into it. Sound like nobody has been using it though, since this is the first time I've heard a complaint about it not working. Mark. PS. There is no hardware cursor in that mode. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
Option Rotate CW Option Rotate CCW Ugh, I haven't tried this stuff in a long time. It looks like somebody broke all of this stuff. I doubt the problems are specific How come this is handled so strangely? My daily bread is a series of embedded systems with inbuilt gravity sensor that rotate the onscreen display dynamically (realtime) when the user rotates the housing. We don't use the chipset rotation features. We keep the chipset believing it is working with (say) a 640x480 display, and the application layer believes it is working with a 480x640 display. The GDI layer does the rotation and translation of coordinates, maintaining use of hardware acceleration features where available (including hardware cursor...). Sounds like the current X code uses a single piece of generic rotation code and bumps every chipset down to an unaccelerated mode using that rotation code. -- Lewin A.R.W. Edwards Embedded Engineer, Digi-Frame Inc. Work: http://www.digi-frame.com/ Tel (914) 937-4090 9am-6:30pm M-F ET Personal: http://www.larwe.com/ http://www.zws.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert] Anyone who knows WaitForSomething(): os/WaitFor.c
Anyone who knows WaitForSomething(): os/WaitFor.c
what is the context of the follow steps that causes a new connection to
happen when XFD_ANYSET(tmp_set) is TRUE? What condition causes a new
connection? I have a BadWindow and its caused by this new connection
*without* a new client!
367 #ifndef __CYGWIN__
368 i = Select (MaxClients, LastSelectMask, NULL, NULL, wt);
.
.
.
441 fd_set tmp_set;
442 #ifdef SMART_SCHEDULE
443 if (someReady)
444 XFD_ORSET(LastSelectMask, ClientsWithInput,
LastSelectMask);
445 #endif
446 if (AnyClientsWriteBlocked XFD_ANYSET (clientsWritable))
447 {
448 NewOutputPending = TRUE;
449 XFD_ORSET(OutputPending, clientsWritable,
OutputPending);
450 XFD_UNSET(ClientsWriteBlocked, clientsWritable);
451 if (! XFD_ANYSET(ClientsWriteBlocked))
452 AnyClientsWriteBlocked = FALSE;
453 }
454
455 XFD_ANDSET(devicesReadable, LastSelectMask,
EnabledDevices);
456 XFD_ANDSET(clientsReadable, LastSelectMask, AllClients);
457 XFD_ANDSET(tmp_set, LastSelectMask,
WellKnownConnections);
458 if (XFD_ANYSET(tmp_set))
459 QueueWorkProc(EstablishNewConnections, NULL,
460 (pointer)LastSelectMask);
^
here is where I get the new connection without a new client
Thanks in advance!
James Dugger
Senior Linux Engineer
[EMAIL PROTECTED]
EchoStar Technologies
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 and LCD
At 07:01 PM 6/12/01 +0100, Egbert Eich wrote: I've looked at it - you only offer binary drivers. However I think I know what you do. Your patch is pretty similar to the VESAFbHack patch posted a while ago. The VesaFBHack patch, which was my little effort at re-implementing the patch posted to this list by Kirill Konyagin (back in July 2001), may have been based on the same work as Rene, or Rene's work was based upon it. I simply put it into a form that allowed the user to easily enable/disable it. It also meant that if it was fixed, a config file change was not really necessary (something I was looking at, as I was investigating rolling these out into a production environment, and the less changes in the future, the better). I'm thinking of something different: sis_bios.c is converted BIOS code anyway. Since we have the int10 infrastructure we can use it to run the real BIOS and eliminate much of the code in sis_bios.c. You might find that a lot of the code in the XFree driver is now the same as that in the Linux Kernel FrameBuffer for the SiS630 chip, so some common development here could be a definite advantage. Something I have noticed as a difference between the VesaFB and SiSFB drivers in the Linux kernel, is that the VesaFB driver does it's init as absolutely early as it can, as the routines to change resolution have to be performed (afaik) in real mode, not in protected or virtual modes. I tryed to get docu from sis - even considering signing a NDA - but suddenly the email thread with them stopped ... ? - They so not seem to be interested in getting the chip to work properly under Linux ... :-( I would certainly love to have better docs for the graphics part of the 630 than there are in the 630 datasheet. I got very little response from SiS, to very similar or the same queries (re: docs, NDA, sample code, etc). The company I work for wants to use a machine made by Clevo (a Taiwanese company) as a Point of Sale terminal (it's a desktop with an LCD screen, and very small footprint), but with the current problems we have with the SiS630 chipset (if not resolved soon), we will simply have to turn down the product as another good idea, bad implementation. Pity really, as the cost was reasonable, and the options on the product were ideal for our market. AMC Enterprises P/L- Stuart Young First Floor- Network and Systems Admin 3 Chesterville Rd - [EMAIL PROTECTED] Cheltenham Vic 3192- Ph: (03) 9584-2700 http://www.amc.com.au/ - Fax: (03) 9584-2755 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
On Thu, 6 Dec 2001, Mark Vojkovich wrote: Many drivers have Rotate options. Eg, from the nv driver man page: Option Rotate CW Option Rotate CCW Rotate the display clockwise or counterclockwise. This mode is unaccelerated. Default: no rotation. Coincidentally, I just tried this last night with my TNT2 and XFree86 4.1.0. It didn't work well at all. The hardware cursor seemed pretty badly confused and there were weird dead areas on the screen containing garbage and portions of the root weren't visible no matter how I panned around. Dragging windows caused all sorts of corruption and glitching. Ugh, I haven't tried this stuff in a long time. It looks like somebody broke all of this stuff. I doubt the problems are specific to the nv driver. I'll look into it. Sound like nobody has been using it though, since this is the first time I've heard a complaint about it not working. It's fixed in CVS now. Must have broken a long time ago from the looks of it. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
Hi Mark, We don't use the chipset rotation features. We keep the chipset believing it is working with (say) a 640x480 display, and the application layer believes it is working with a 480x640 display. The GDI layer does the rotation and translation of coordinates, maintaining use of hardware acceleration features where available (including hardware cursor...). That's because rotating X-rendering correctly is an ominous task. X11 is a pixel-perfect specification. Just rotating the coordinates on lines and polygons won't render them correctly. None of this Can you explain this further? At the moment I have a system - running X actually - where I am emulating my older proprietary systems inside a frame buffer. Eventually I would have gotten around to looking at X's rotation possibilities anyway; I knew of it theoretically but have never tried to use it. Bear in mind that I know nothing about the internals of how things are represented in X. But the first part I don't understand is why rotating the coordinates of lines and polygons will not yield a correct result. A rectangle 100x25 pixels in size, 100 pixels right of the origin and 50 pixels below it, is described completely regardless of the geometry of the screen (assuming a Windows-convention origin, not an OS/2 PM-convention origin, of course :) My understanding of how it would work is that it would abstract the rotation at the same level I abstract it - i.e. the client app would be unaware of the rotation and would only be aware of the fact that the screen's pixel dimensions are a bit strange. As far as the client is concerned there is no rotation; the dimensions and sign-directions of the display surface exactly match that of the physical display output. The client renders at (say) 480x640; the user sees 480x640. The fact that there is a rotation operation is purely a hardware issue related to the order in which the display controller DMAs pixels out of RAM; it's just an issue of internal frame storage. Where am I going wrong in my understanding? And is this a question of rigorous standards compliance, or one of basic functional failure that will be obvious to the user? (Oh, and in case this is not clear: I'm not at all being argumentative or implying that any XFree code is bad, I'm just trying to see why it is impossible to implement an efficiency improvement). OT-PS: Pity you guys (NVidia) wouldn't sell us LCD controllers when we asked ;) but I'm very interested to try your PDA-chip with integral MIPS micro... ;) (or was that Neomagic? Darn N-names :) If there's a Linux port and an X server, I'm a happy monkey. -- Lewin A.R.W. Edwards Embedded Engineer, Digi-Frame Inc. Work: http://www.digi-frame.com/ Tel (914) 937-4090 9am-6:30pm M-F ET Personal: http://www.larwe.com/ http://www.zws.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Rotated display under Linux?
On Thu, 6 Dec 2001, Lewin A.R.W. Edwards wrote: Hi Mark, We don't use the chipset rotation features. We keep the chipset believing it is working with (say) a 640x480 display, and the application layer believes it is working with a 480x640 display. The GDI layer does the rotation and translation of coordinates, maintaining use of hardware acceleration features where available (including hardware cursor...). That's because rotating X-rendering correctly is an ominous task. X11 is a pixel-perfect specification. Just rotating the coordinates on lines and polygons won't render them correctly. None of this Can you explain this further? At the moment I have a system - running X actually - where I am emulating my older proprietary systems inside a frame buffer. Eventually I would have gotten around to looking at X's rotation possibilities anyway; I knew of it theoretically but have never tried to use it. Bear in mind that I know nothing about the internals of how things are represented in X. But the first part I don't understand is why rotating the coordinates of lines and polygons will not yield a correct result. A rectangle 100x25 pixels in size, 100 pixels right of the origin and 50 pixels below it, is described completely regardless of the geometry of the screen (assuming a Windows-convention origin, not an OS/2 PM-convention origin, of course :) The biasing rules for lines and polygon edges are octant-specific. You won't get the same results for the same reason that Bresenham's algorithm won't draw a line from point A to B on the same points as a line from B to A without some octant-specific fixups. My understanding of how it would work is that it would abstract the rotation at the same level I abstract it - i.e. the client app would be unaware of the rotation and would only be aware of the fact that the screen's pixel dimensions are a bit strange. As far as the client is concerned there is no rotation; the dimensions and sign-directions of the display surface exactly match that of the physical display output. The client renders at (say) 480x640; the user sees 480x640. The fact that there is a rotation operation is purely a hardware issue related to the order in which the display controller DMAs pixels out of RAM; it's just an issue of internal frame storage. That's the way it works now, except the copies from the shadow buffer to the real framebuffer are done with the CPU due to the general lack of user-space DMA capabilties on the operating systems we support. Where am I going wrong in my understanding? And is this a question of rigorous standards compliance, or one of basic functional failure that will be obvious to the user? (Oh, and in case this is not clear: I'm not at all being argumentative or implying that any XFree code is bad, I'm just trying to see why it is impossible to implement an efficiency improvement). Perhaps I misunderstand what you were asking about. You've described the way it currently works. I described why doing without a shadow buffer has not been done. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Capturing video from X
Hello I would like to record a demonstration of my program running in X 4.1.0, could someone tell me if this is possible? Is it possible to log X commands and then generate an MPEG or other video format from that data? or is it possible to capture video in real time? The other option I would resort to if this Digital capture method was not possible is to plug my monitor output into another PC analogue capture card. JG Hypermedia Research Centre Sanyo RD Headquarters, Tokyo http://www.sanyo.co.jp/R_and_D/3dm/ Tel: +81 (0)3 5803 3566 Fax: +81 (0)3 5803 3640 E-post: [EMAIL PROTECTED] Please use open standard file formats for attachments ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]BadValue mager opcode failed request :89 (Solved
ya, that is what happened, the integer value is some where arround 9 digits, it suppose to be 0-128, that is why the XStoreColors() has giving BadValue error. Thanks again, Bala. --- Mark Vojkovich [EMAIL PROTECTED] wrote: On Wed, 5 Dec 2001, Ba la wrote: Hi All, Thanks for all, Bad Alloc problem was solved. one of the integer value is out of range that why the problem. According to the man page you are trying to store pixels in cells that don't exist. Mark. __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]When is 4.1.1 (or what will it be?) is scheduled?
Hello! It seems a lot of time passed since the relesease of 4.1.0... almost half a year... So what is next release and when it is scheduled?? Thanks!! -- ðÏÓÅÔÉÔÅ íïóëï÷óëéê çïòïäóëïê óáêô http://mosk.ru ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident cyberbladeXPAi1
You are the second one within two days who has problems with this chipset. It is a brand new chipset and support for this has just been added. I am sure that noone of the developers has seen a CyberBladeXPAi1, yet. I don't know if anyone has documentation for this chip yet. The situation may be just as it is for the CyberBladeXPm8/16 chipsets: Trident doesn't allow us to release source code. People should understand: 1. In the eyes of chipset vendors Linux is *not* mainstream. Some (not all!) of them don't consider the extra revenue they can make by providing support to OpenSource projects like XFree86 worth the efford. (And they make revenue despite the fact that they don't support Linux as this case shows us!) 2. Toshiba doesn't consider Linux mainstream enough to bother to support it officially. There have been moves to do so in the past but I haven't heared of them for over two years now. Luckily some of the engineers at Toshiba don't think that way and have provided systems for testing in the past. 3. From 1 and 2 one can gather that hardware vendors don't throw at us any new system they put on the market and provide all documentation necessary to support the stuff begging us to add this support. It is vice versa: We still need to beg for documentation and may be a test system. 4. One should consider this when looking for a new system (especially a laptop): It may be a good idea to look around and see which HW is already known to be supported. Anybody buying the latest and greatest systems with chips that have just been released may have to expect unpleasant surprises. I had this surprise, too - many years ago. That's how I got onto this project. I will try and see if I can get a box like this from Toshiba. Egbert. gabriele castellini writes: Hi there, I have recently bought a Toshiba Satellite 1800-S204 laptop that comes with a `trident cyberbladeXPAi1' card. I installed RedHat 7.0 that came with XFree86-4.0.1 and it did not recognize the card. I upgraded to XFree86-4.1.0 but no improvement. Since I noticed that support for this card was added to the soon to be released XFree86-4.2.0, I downloaded the latest CVS from December 4 and the compiling and installation seemed to be all right. However, by running `XFree86 -configure' I could only get one mode and it is not usable, since I get a small frame in which I seem to recognize the default 'net-style' X background with a ghost-like mouse pointer. Nevertheless the card is correctly identified as one can see from the log-file included below. Does anybody have any idea of what went wrong? Did I make some mistake somewhere or is there any setting that I could change in order to get a usable picture? Hopefully the included log-file may help those who know more about this to understand what is going on. By the way, one more thing, `startx' quit working after installation of the new CVS. After typing it I get the following error message: xauth: error while loading shared libraries: LibXmuu.so.1: cannot open shared object file: No such file or directory. I wonder what that means since the file LibXmuu.so.1 actually exists. Does anybody have any idea of how to fix this? ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
