Re: [Xpert] V_BIOS woes
Adam Goode wrote: One last thing I noticed: Sometimes XFree86 prints this: (II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x and sometimes this: (II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03b0, hwp-PIOOffset is 0x (For the Radeon, hwp-IOBase is sometimes 0x03d0 and sometimes 0x03b0.) The SiS is always 0x03d0. Does this mean anything? At first I thought the Radeon was at was 0x03b0 when it failed, but it turned out that it can be 0x03b0 even when it works (and 0x03d0 when it fails). 0x3b0 is the IOBase for monochrome mode, 0x3d0 for color mode. The fact that the ati driver chooses the monochrome base might have something to do with reading an incorrect MISC register (which is responsible for choosing either color or mono). Perhaps I am mislead myself, but shouldn't this setup require RAC (which is not being used according to the log)? Is the amount of video RAM detected by the SiS driver (4096K) correct? Is there any particular reason for why you're using a mixture of modules compiled for 4.2.1 and 4.2.99? Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert] Re: sis620 X (was Re: [Xpert]*****SPAM*****)
The 620 is - as regards the VGA part - compatible to the 530. As far as I know, the 530 (thus the 620) were supported by 4.1 already. 4.3 will bring many enhancements, among others Xv for these old chips. Thomas Andy Isaacson wrote: On Mon, Dec 30, 2002 at 08:28:05AM -0500, [EMAIL PROTECTED] wrote: SPAM: NO_REAL_NAME (-0.3 points) From: does not include a real name You should configure your software to have a real name in the mail headers, and include a useful subject on further mailing list posts. This would help you avoid being labelled as spam. (You also need to get a better ISP, but I can understand that is sometimes difficult.) hello i am trying to run redhat 5.2 on a computer with a SiS620 chipset anyone have a patch for my xfconfig file??? I would recommend getting a more recent Linux rather than attempting to use an ancient version of RedHat. RH5.2 shipped with XFree86 3.3.2.3, which has absolutely no support for the SiS620 (the support appeared sometime before 3.3.6). At best, you'd have to download RPMs for a more recent XFree86; at worst, you'd be recompiling XFree86. Even RedHat 6.x should be able to support the SiS 620. -andy ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]X locks up the complete system
Michel Dänzer wrote: I can't give a definite answer but only an educated guess: with the HW cursor, Silken mouse may also be used, meaning that the cursor position is updated asynchronously, which may trigger a race condition in the driver. If this hypothesis is correct, the HW cursor shouldn't lock up if you start the server with the -nosilk option. What sort of race condition are you thinking of? The HWCursor code in the driver does no wait's or anything, it just sets a few registers in the MMIO area. The HWCursor code in the sis driver is the same since 4.1 and I have never heard of a _complete_machine_freeze_ (or any other problem) when using it. Unless there were any changes in the silken mouse stuff in 4.2(.1), I hardly believe that this is hwcursor related. Thomas PS: I am developing and maintaining the sis driver since about a year ago. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]X locks up the complete system
Michel Dänzer wrote: I suspect that may exactly be the problem. It may interfere with other MMIO register access, overflowing the chip's FIFO or similar. What process is calling the mouse routines? Is it possible that 2D processing (ie setting up a 2D action) is interrupted by mouse activity? (2D and 3D are the only other things that use the MMIO registers) Even though, I find this unlikely. The SiS chips have a separate queue for 2D/3D which has some sort of extension in video RAM. This queue is never used beyond 1/4 of its size. Speaking of this: Mukhben, try setting the video RAM to 64MB and try then. Perhaps something is writing beyond the usable video memory and thereby overwriting the turbo queue area. This might without doubt cause a complete machine freeze. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Changing ctrl-alt-bckspc to ctrl-alt-delete
[EMAIL PROTECTED] wrote: Making a generic method by which you could send an arbitrary string (defined in a keymap) to a driver does seem like a flexible method for handling this sort thing though, so maybe I'll look into it when I finish some current projects. That's in about what I thought of, so I'd really appreciate! Thomas -- Thomas Winischhofer Vienna/Austria mailto:thomas;winischhofer.net *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Changing ctrl-alt-bckspc to ctrl-alt-delete
Joe, while you are at it: Would it be possible to implement some sort of generic/custom key combination (of your choice) to be used by video drivers, such as a replacement of the Fn-combination found on many laptops? I am facing the following problem: On SiS based machines, the Fn-combination for switching between LCD, TV and VGA in many cases does not work. If it works, it messes up the registers without letting the video driver know. I would like to implement the switch-LCD-TV-VGA function into the video driver (in fact, the function is already there, but unused) but so far I haven't found a way to intercept keyboard events from within a video driver. Just my $.2 Thomas [EMAIL PROTECTED] wrote: David Dawes writes: On Thu, Oct 17, 2002 at 02:29:19PM -0700, Mark Vojkovich wrote: [...] It'd be nice to make this configurable, and I'm sure that a patch to do that would be welcome. There may be other ways to do this via configuring the XKB extension. But I know next to nothing about XKB. It's currently intercepting key events before they get passed up out of the DDX. I'm not sure how feasible it would be to intercept them after they've been converted into X keysyms, but that might offer a more configurable solution. XKB definately has support for defining action keys (e.g. to switch VTs or to kill the server) and the mappings are, of course, configurable. I thought I had submitted a patch long ago to enable this functionality in XFree86, but I guess I never sent it in. I'll see if I can find it in my archives. I didn't find it, so I rewrote it. This is better way of implementing than I did it before anyway. The attached patch: 1) Creates a new function to process action events that can be called both by the current code (in xf86Events.c) that intercepts special key sequences and by XKEYBOARD's action handlers. 2) Implements handling the processing of the Terminate action 3) Updates the xkb symbol maps to have a default mapping for the Ctrl-Alt-Backspace sequence to the Terminate action I'll send a patch implementing other special keys in XKB as soon as I write it. -- Thomas Winischhofer Vienna/Austria mailto:thomas;winischhofer.net *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Sis315 Card config?
www.winischhofer.net/linuxsis630.shtml Thomas John P. Herlocher wrote: I'm having diffuculty getting my Xfree86 configured to support an SiS315 Graphics card. I had it successfully running with horrible resolution once using the generic VGA card but It wasn't very useable. Any input on drivers or specific configurations appreciated. John -- Didja Know... It is estimated that illiteracy costs U.S. businesses $225 billion a year in lost productivity? (Source: Useless Facts) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert -- Thomas Winischhofer Vienna/Austria mailto:thomas;winischhofer.nethttp://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Intercepting keyboard events from within video driver?
The goal is: A quick hack in order to do a simple task which I am asked for almost every day: The hardware I am developing for has two CRT controllers (actually it's the sis driver for XFree86). One of these CRT controllers is able to control LCD panels and TV encoders, but only one of these two at the same time. The choice between LCD and TV (if both are detected at server start-up) is currently done with an Option in XF86Config-4, but this makes it impossible to change the setting during run-time (which is what users really ask for). (The special key on laptops which should provide this does not work under Linux - don't ask why; even if it did it is not satisfactory as I have no control over what the BIOS does to my registers. However, involving the BIOS is definitely not desired.) So, I thought of another qd solution: In the good, old CTRL-ALT-KP_Plus/Minus-manner why not intercept eg. CTRL-ALT-KP_Multiply and cycle through all possible output devices (LCD, TV and - theoretically - secondary VGA, that is)? Can this be done from within a video driver? I looked though the input related code but could not find a solution. Anybody? Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Intercepting keyboard events from within video driver?
Thanks Mark, Alex, Xavier, Branden. Mark Vojkovich wrote: On Mon, 30 Sep 2002, Thomas Winischhofer wrote: The hardware I am developing for has two CRT controllers (actually it's [...] registers. However, involving the BIOS is definitely not desired.) Those key presses often never get passed the BIOS. They won't even get to the X-server. That's the way they work on the recent laptops that I've had experience with. No software outside of the BIOS knows about it. I know. That's the problem. This key combination causes a *complete* machine lock-up here and on many others. And the idea also was to keep the BIOS from messing around with the registers (eg. while Xv is active, etc). I have seen (literally *seen*, felt like 10 years ago in my assembler era) many SiS BIOSes causing the strangest effects (mouse cursor jumps around wildly in the first left 32 pixels of the screen, xv is totally skrewed up, etc). And the final - and most important - reason is that the BIOS drives the video bridge in slave mode (don't bother...) and this would end up in a catastophe in dual head mode. So, I thought of another qd solution: In the good, old CTRL-ALT-KP_Plus/Minus-manner why not intercept eg. CTRL-ALT-KP_Multiply and cycle through all possible output devices (LCD, TV and - theoretically - secondary VGA, that is)? Can this be done from within a video driver? I looked though the input related code but could not find a solution. I suspect that it's not possible for the video driver to intercept key presses. To hear that from Mark makes it sound quite final.. :( But then, sorry, if I'm annoying: Remember, what I want is not necessarily a secure or standard compliant solution; the target user group is a few people who know what they're doing. What about installing a wakuphandler (or wrapping the old one), wrapping some xkb resource or something like that? Alex Deucher wrote: you could create a little cli app like s3switch for savage based cards that will switch the output between tv and crt2. then map the keyboard shortcut to run that cli app using your window manager, etc. This would result in writing a server extension. Otherwise an application outside the server won't be able to communicate with the driver, if I'm not mistaken... (And the driver not only NEEDS to know about the change, it is also the driver which is to PERFORM it; setting up LCD or TV on SiS chipsets is ca 500k source code since the driver supports 8 chipsets with each 4 possible video bridges and so far ca. 60 different panel types) - if anybody knows better, feel free to object! Branden Robinson wrote: Apart from what Mark said, that particular key combination is already reserved, though it's not trapped by the server by default. You can be forgiven for not knowing this, though, as it's not documented everywhere it should be. ;-) As so many other things as well... :) I saw no code anywhere indicating this. Well then, I don't insist on this very combination anyway. In case I somehow manage to do what I originally intended: What would be a suitable and not-yet reserved combination? Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]mouse pointer bug: SiS 5598, XFree86 4.2.0
Caciano Machado wrote: The 'X' cursor is OK but when the arrow pointer appear it draw two lines in the screen. This bug appear in all windowmanagers (KDE, GNOME, wmaker...) I tested it with the resolutions 640x480 and 1024x768, XFree86 4.2.0, Slackware 8.1, and my video card is the onboard SiS 5598. Try using the option SWCursor Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SIS630 Chip Set
David Hunt wrote: Hi there I have an SIS630 chipset on a notebook, that seems to work ok under X, but if you swap back to a virtual console the screen turns to junk. Is this a configuration issue or a driver bug in X4.2.0 Protocol Version 11 revision 0 vendor release 6600. FreeBSD package 4.2.0_1,1. Please try my updated driver at www.winischhofer.net/linuxsis630.shtml Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with driver for SIS 315
PUJOmania! wrote: Hi, I have got a SIS video card, AG315P-64 and I don't know how I can configure it with XFree86. I have RedHat 7.2 with XFree86-4.0.1-1 and the sis driver don't support the card. And the manufacturer don't support the driver. Only I can start X with a resolution of 640x480 with 16 colors! Could anybody help me? www.winischhofer.net/linuxsis630.shtml Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]sis6326 8mb xv
[EMAIL PROTECTED] wrote: Can someone implement the xv support on the sis driver for 6326? Yes, I just found a datasheet for this device. Since the 6326's video part works similar to the 630's, it won't take long. Be patient. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: sis6326 8mb xv
[EMAIL PROTECTED] wrote: If nobody does the xv support for sis6326 I would want to do that and i want know if it's hard? OK, the first version with Xv for the 6326 is available for download on my website (URL in signature). I developed this today completely blindly (without hardware for testing), so I can't say if it works at all. I have so far not touched that 4MB-limit. So people testing this will have to set the video RAM to 8192 in XF86Config-4. The Xv part does double buffering, so it needs quite much RAM. When reporting, please 1) describe in detail what you seen on the screen, AND 2) send me your X log and the log of the application you use (eg. Xine or aviplay). Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: sis6326 8mb xv
Whoops New version online in a few minutes. Please don't send logs to the list but to me privately. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]sis6326 8mb xv
[EMAIL PROTECTED] wrote: i have a sis6326 AGP 8Mb and xv doesn't work and X limit videoram to 4096. I want to use 8Mb of memory and xv to work. can you give me some advice? I don't really know about the RAM issue (although I always wondered about that limitation in the code - Egbert?), but Xv is not supported on this device. The only SiS chips that support (native) Xv is the 630/730 and the 310 series (315, 650, 740, 550). If you want I can remove the RAM limitation from the code and send you the binary for testing. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]sis6326 8mb xv
Alan Hourihane wrote: On Sun, May 12, 2002 at 12:44:26 +0200, [EMAIL PROTECTED] wrote: so what should i do to have xv to work? xv can work with 4Mb of memory? I meant that the 6326 can support it, it doesn't appear to be implemented in the driver though. Right. Xv is only supported on the 630/730 in the current 4.2 driver, and on the 310 series (315, 650, 740) in my development version. I was not aware of that feature in previous devices. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]sis6326 8mb xv
[EMAIL PROTECTED] wrote: Now i'm using videoRAM 8192Kb and works well disabling the accelleration engine!!! I'm using DRI too! DRI on the 6326? With what driver? The DRM kernel driver only supports 300, 630, 540... Can someone implement the xv support on the sis driver for 6326? If you can provide me with a complete data sheet, no problem... Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]sis driver problem
totos wrote: I think that my driver works not perfect. Can you help me? Yes. Go to my website and download a newer version of the driver. Apart from that: Section Modes Identifier Modes[0] Modeline 1024x768 66.29 1024 1040 1216 1400 768 768 777 802 Modeline 1024x768 79.68 1024 1040 1216 1400 768 768 777 802 Modeline 800x600 40.56 800 816 928 1072 600 600 609 626 Modeline 800x600 46.80 800 816 928 1072 600 600 609 626 Modeline 640x480 25.96 640 656 720 864 480 480 489 501 Modeline 640x480 29.95 640 656 720 864 480 480 489 501 EndSection Remove this section, it's not needed. Section Device BoardName5591/5592 AGP BusID0:2:0 Driver sis Identifier Device[1] Screen 0 VendorName SiS EndSection Remove this section; the 5591 is the AGP bridge, not the VGA device. Section DRI Group video Mode 0660 EndSection This should read 0666. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SIS 315/550/650/640/740 - testers wanted
Hi, I am desperatly looking for people who are willing to help me testing (and eventually developing) the kernel framebuffer and X driver for these chipsets. If you're interested, please drop me a note. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SIS630: problems with GL and XV.
Ulrich Schwenk wrote: Second, the ogle dvd-player does not function properly due to problems with xv. Another video application however claims to be using xv for some scaling issues and runs all right. What can be wrong with it? How can I test xv? Unfortunetely, the SiS driver included with 4.2 has a bug in the Xv part (the deadline came one day too early...). Please use a newer version available at http://www.webit.com/tw/linuxsis630.shtml (Download either the binary for 4.2 - which has been compiled with CVS version as of 22/02/02 by a nice helper but has not been tested by me - or download the source and compile it yourself) Thomas -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SiS VGA drivers - once again
Hello, since I do only get very few testing results recently, I would all people reading this and using machines with SiS VGA devices (especially laptops) kindly ask to test the current versions of the X driver as well as the kernel framebuffer driver available at http://www.webit.com/tw/linuxsis630.shtml and to report the results (including logs). I got only one machine for testing, so I need your help! Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]S3 ProSavageDDR
Fai wrote: Hello! I am new to this mailing list! Hi Fai! [...] the other is SiS6325, which XFree86 4.x is no supported but reported as valid screen, very strange! Are you sure you mean 6325 and not 6326? The SiS632_6_ is supported by the SiS driver in 4.2. However, I could not test this. (So I leave this question to you, Egbert!) The 632_5_ is the new SiS 650 Anthony told me about (is this a P4 system?) SiS told me that this chipset is not on the market yet (about 2 months ago). Support for this chipset is, however, under development by me and SiS. Currently, the driver accepts the chipsets as valid but might not work correctly. Could you send me the log and tell me more details about what happens on the screen? (Privately, please) Thanks, Thomas -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]3D acceleration with SiS ?
José Romildo Malaquias wrote: I have read your Linux SiS page, grabbed some drivers, and tested them with the SiS 305 card. I have followed the instructions in your page: 1. Compiled and installed a linux 2.4.18 kernel with the sisfb driver sisfb_src_100202.tar.gz. I have tried some configurations: a) VESA framebuffer driver enabled and disabled Never enable the VESA framebuffer when using the sis framebuffer. These two have the same purpose. b) compiled the vesafb driver into the kernel (instead of as a module) What is it with you people that you all stick to this VESA thing?! :) As said: Disable the VESA framebuffer (don't even compile into the kernel nor as a module). c) added the kernel parameters video=sisfb:mode:none,mem:12288 or video=sisfb:1024x768x16:none,mem:12288 The second statement is wrong: if you don't want to use a graphical console, use video=sisfb:mode:none,mem:12288 2. Installed the SiS X driver sis_drv.o_260202.tar.gz. 3. Set up the X config file with a depth of 16 or 24 and specified the option MaxXFBMem to 12288 in the Device section. 4. Tried to run the tuxracer program. The screen became black (or almost) with a dark pointer in it. Some clicks were heard on the speakers, and the system froze. Attached is the output of the xdpyinfo program. Any clues? Well, not yet. Please send me (not the list) the X log, your XF86Config-4 and the output of glxinfo. The relevant part of syslog would be interesting, too (the lines starting with sisfb: and a few of the following) It is known that some older distributions of X 4.1 (such as early Redhat's) had problems with DRI. I use Debian's 4.1.0.1 and it works here. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: 3D acceleration with SiS ?
Mike A. Harris wrote: If it is the same patch I am refering to, it was sent to me forwarded to me with a comment that someone at Caldera wrote it. I forwarded the patch back to XFree86 I believe, with that info. You may want to check the XFree changelog, confirm wether or not the patch was yours, and correct the credit if necessary. I'm sure if it is incorrect, that it was an honest mistake by whomever sent it along the chain. I don't want to make a big deal about this, but I meant the latest patch for the DRM kernel module. It had a permission problem and I sent a patch to LKML as well as Alan and now it's included even in the stock kernel (credited Alan Cox)... if you meant something different, I appologize. (My changes to the SiS X driver aren't ever credited either because I don't commit myself. Egbert Eich is doing this on my behalf.) Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]3D acceleration with SiS ?
José Romildo Malaquias wrote: Not all SiS chipsets are supported by the current driver. DRI is only available for the 300/540/630/730. 2D accelleration is also supported on the 530 and some older 55xx chipsets. 640/740/315/650 are currently subject to development. I don't know about the 305, I'd need to know the PCI ID to tell you more. (Install the card, boot Linux, type lspci -vvv in the console and send me the output.) By now I have got one SiS 205 card. I mean, a SiS 305 card. According to the PCI ID it's a SiS 300. This chip is said to be supported by the current drivers (but I have never heard of anyone using this card type). You might want to use the most current versions of the drivers available at http://www.webit.com/tw/linuxsis630.shtml I'd appreciate if you could report your experiences with that card. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS 530 DRI Out Of Memory Errors
T.P. Reitzel wrote: I've been trying to narrow down the source of fatal out of memory errors in the sis_dri.so library for about 3 weeks to no avail. I noticed that someone else on the users mailing list at DRI Sourceforge is having exactly the same problems with the SiS 730S chip. I'm currently using XFree86 4.1, but I also tried 4.2 with no luck. I've also gone to using the latest Alan Cox patches for the 2.4.18 kernel with no luck, either. Instead of going into a lot more detail, see the attached XFree86.0.log for my system. DRI appears to load successfully, but generates this error when an openGL application such as glxgears is invoked. 1. DRI requires the sis kernel framebuffer driver (sisfb) for memory management. 2. sisfb does not support the 530. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS 530 DRI Out Of Memory Errors
T.P. Reitzel wrote: 1. DRI requires the sis kernel framebuffer driver (sisfb) for memory management. 2. sisfb does not support the 530. Thomas As far as your involvement is concerned, will the SiSfb driver probably support the SiS 530 chipset by 1 Sept. 2002? Certainly not. The 530 is AFAIK about 4 years old technology and there's no support from SiS. I won't spend any time on that (especially as I don't have a machine for testing). I'm asking so I can make a decision whether to wait or replace this PCCHIPS motherboard now. If the video could be disabled, I'd just buy another PCI video card. I'd do that anyway. Even if DRI one day works on the 530, I would not exspect any special performance. That chip's simply too old. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Various SiS driver items
Hi, could you please send our patches to me? Thanks. About the line Unofficial driver by...: I need to do this for testing, to see what version the people are using when sending me their logs. We had a time issue when committing the code to Xfree86 before the deadline for 4.2, Egbert Eich (who commits on my behalf) seems to have missed this. Egbert had to make some minor changes to the accel code for (global) memory management reasons introduced by my MaxXFbMem option. As soon as I have received your patches, I will take care of this. As for the unused options: (**) SIS(0): Option SWcursor (**) SIS(0): Using SW cursor (==) SIS(0): PCI retry enabled (==) SIS(0): Fast VRAM enabled (==) SIS(0): TurboQueue disabled ... Then later on: (==) SIS(0): Silken mouse enabled (II) SIS(0): direct rendering disabled (WW) SIS(0): Option swsursor is not used You see the difference...? sw_S_ursor... (--) SIS(0): Video BIOS version ËVer 1 detected This is fixed in my development version, which will be committed soon. The driver does no more use the BIOS. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re:[Xpert]3D acceleration with SiS ?
Hello. I am in a need of a new graphics card to use in my Linux system. I am looking for a not too expensive card. I have been offered a SiS 305 card by a reasonable price. But I am not sure whether XFree86 already supports 2D _and_ 3D acceleration with it. Can anyone with a SiS card give me his(her) opinion on the subject? Not all SiS chipsets are supported by the current driver. DRI is only available for the 300/540/630/730. 2D accelleration is also supported on the 530 and some older 55xx chipsets. 640/740/315/650 are currently subject to development. I don't know about the 305, I'd need to know the PCI ID to tell you more. (Install the card, boot Linux, type lspci -vvv in the console and send me the output.) Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SiS630 - new framebuffer driver
Hello everyone, I don't know if you keep up the with current development, so excuse me if I bug you with information you already have. The situation is like this: Two days ago, I received a new version if the sisfb from SiS themselves. This new version of sisfb, of course, refused to work on my machine, and looking through the code, I saw that it contained the exact same bugs as the old version. However, the root problem the old driver had, namely that the LVDS tables were all empty (which made it impossible that the driver ever worked on a LVDS machine), is gone; there are lots of tables for about 30 different LCD panel types/brands/models. What I did was do the same patches to the code that I had made to the old linux kernel driver, and after a short while I could make the new driver run on my machine. WITHOUT READING THE BIOS. (8bit modes still don't work, though). Why I am writing this to you: The new sisfb also contains support for the upcoming SiS650 chipset. Since the X driver only supports 630 and compatibles (540,300; aside from the old 530 series) I intend to include the mode switching functions of sisfb into the X driver in order to support newer chipsets as well. I WILL ONLY DO THIS IF sisfb's FUNCTIONS REALLY WORK ON ALL MACHINES! Therefore, I really need to know if the new sisfb works on your machines. Please, please, please try the new sisfb with all 16 and 32 bit modes your LCD display supports and report a) if the old driver worked on your machine, AND b) if the new driver works. People with 1280x960 panels should also try this mode with 16 and 32 bit depth! Please include the relevant part of the syslog and the output of lspci -vvv with your reports. My progress with the X driver depends on your results! Thanks in advance, Thomas PS: The new driver is available at http://www.webit.com/tw/linuxsis630.shtml PPS: Installation remark: The archive contains a file names sisfb.h which must be copied over the old one in [kernel-tree]/include/linux PPPS: Please let me remind you that sisfb does NOT support 24 bit modes. Use 32 instead. (The value refers to the framebuffer depth, not the COLORdepth.) -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SiS630 - new framebuffer driver
Hello everyone, I don't know if you keep up the with current development, so excuse me if I bug you with information you already have. The situation is like this: Two days ago, I received a new version if the sisfb from SiS themselves. This new version of sisfb, of course, refused to work on my machine, and looking through the code, I saw that it contained the exact same bugs as the old version. However, the root problem the old driver had, namely that the LVDS tables were all empty (which made it impossible that the driver ever worked on a LVDS machine), is gone; there are lots of tables for about 30 different LCD panel types/brands/models. What I did was do the same patches to the code that I had made to the old linux kernel driver, and after a short while I could make the new driver run on my machine. WITHOUT READING THE BIOS. (8bit modes still don't work, though). Why I am writing this to you: The new sisfb also contains support for the upcoming SiS650 chipset. Since the X driver only supports 630 and compatibles (540,300; aside from the old 530 series) I intend to include the mode switching functions of sisfb into the X driver in order to support newer chipsets as well. I WILL ONLY DO THIS IF sisfb's FUNCTIONS REALLY WORK ON ALL MACHINES! Therefore, I really need to know if the new sisfb works on your machines. Please, please, please try the new sisfb with all 16 and 32 bit modes your LCD display supports and report a) if the old driver worked on your machine, AND b) if the new driver works. People with 1280x960 panels should also try this mode with 16 and 32 bit depth! Please include the relevant part of the syslog and the output of lspci -vvv with your reports. My progress with the X driver depends on your results! Thanks in advance, Thomas PS: The new driver is available at http://www.webit.com/tw/linuxsis630.shtml PPS: Installation remark: The archive contains a file names sisfb.h which must be copied over the old one in [kernel-tree]/include/linux PPPS: Please let me remind you that sisfb does NOT support 24 bit modes. Use 32 instead. (The value refers to the framebuffer depth, not the COLORdepth.) -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 X-Mas
SiS 630 Update 26/12/01: -) Video memory corruption temporarily solved (new option for XF86Config-4) -) DRI works with some applications (Qu*ke3 doesn't work yet) -) TurboQueue doesn't hang X if sisfb used at the same time. For download links and more information, please see my website. Please test the drivers and report eventual problems. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 X-Mas
Erm...hi, it's me - again. Just finished another update. Mode restoration now (on my machine) works, so you may use the sisfb and the new X driver at the same time. There were changes in _both_ drivers, so you need to install them both. Please read the information on http://www.webit.com/tw/linux.shtml for problems still unsolved. Thomas Thomas Winischhofer wrote: I just made another update. Those of you who already downloaded the files please do that again. The new version has been tested on Gericom Webboy and Webshox (LVDS bridges) and worked on both. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 X-Mas
Already have made an update. As it turned out, there are new laptops on the market which either don't have a video bridge at all or at least not one we know of (yet). I therefore included an option (see XF86Config-4) for forcing the usage of VESA on such machines. Please not that the driver will automatically choose to use VESA if it detects a SiS630 _in_combination_ with an LVDS bridge. This behavior can be overruled by setting NoVESA. On the other hand (on machines with SiS630 and no or unknown bridges), you may set the option UseVesa to force the driver to use VESA (even though it would'nt do that otherwise). The options have no effect on chipsets other than SiS630. Thomas PS: I included the update in the files already, so please use the links I posted earlier this day (5 in the morning, to be exact). Thomas Winischhofer wrote: Hi everybody, I have just finished coding the new sis X driver. This one should finally do it on _ALL_ machines. It uses the BIOS' VESA interface to change the mode. I have tested it on three (Gericom) machines, so I really believe it works. Please _don't_ use any framebuffer driver when using this driver as it cannot restore graphics modes (yet). Binary (compiled for 4.1): http://members.aon.at/~twinisch/new_sis_drv.o.tar.gz (On Debian, sis_drv.o should be placed at /usr/X11R6/lib/modules/drivers/) Source (compiles well on CVS 4.1.99 and probably on 4.2): http://members.aon.at/~twinisch/new_sis_drv_src.tar.gz XF86Config-4: http://members.aon.at/~twinisch/new_xf86config-4.tar.gz Please read the XF86Config-4 file as it contains important information on how to use the driver in 24 bit depth mode. This time I have tested _all_ modes and they all worked on my machines. In case you want to use the old code (for some reason), set the option NoVesa (this is commented in XF86Config-4). The driver uses the old code if it detects a chipset other than SiS630 and a video bridge other than LVDS. Feedback welcome! I am tired now. The whole thing started with I want a driver for my notebook and got a real project (Egbert, you were right). My girlfried is really annoyed already. I hope everybody is satisfied now :) @Egbert: Der Code basiert größtenteils auf CVS von etwa vor 2 Wochen. Ich habe - anläßlich der Entwicklung von sisfb - auch einige Fehler in sis_bios.c behoben, die den Treiber (bei NoVesa oder auf bridge-losen Gfx-Karten) vermutlich besser funktionieren lassen. Schau Dir das mal an und inkludiere vielleicht Deine Patches (wenn es überhaupt welche gegeben hat; was Du mir am 17. Dezember geschrieben hast ist inkludiert [war wegen der TurboQueue, aber leider erfolglos, hat aber auch keinen negativen Effekt]. Mein Verdacht ist übrigens, daß es daran liegt, daß die Register für die Turboqueue in SiS300InitMode [in sis_vga.c; wird in ModeInit über *ModeInit aufgerufen], neu gesetzt werden; ich habe das aber nicht getestet. Der Stand ist nach wie vor, daß X bei eingeschaltener TurboQueue hängt, wenn man zwischen VT und X wechselt.) Sorry daß ich keine Patches gemacht habe, aber das ist mir - ehrlich gesagt - zu mühsam, da ich den Original-Code nicht mehr habe. Ich überlasse es selbstverständlich Dir, den Code zu committen.. :) (was mich, nebenbei gesagt, sehr freuen würde) @Rune: You should compile from source. I saw from your logs that you are using 4.1.99 and that sis_drv crashed when accessing the vbe extension. I believe this has to do with changes within vbe (changes in structures there) so I don't think you should use the binary. This means everyone of you using 4.1.99 by the way. Merry christmas! Thomas PS: Please don't forget to fill out the form I posted under SiS630 - newest info on the XPert list and please use the _new_ X driver for testing. Thank you. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 X-Mas
I just made another update. Those of you who already downloaded the files please do that again. The new version has been tested on Gericom Webboy and Webshox (LVDS bridges) and worked on both. Thomas Thomas Winischhofer wrote: Already have made an update. As it turned out, there are new laptops on the market which either don't have a video bridge at all or at least not one we know of (yet). I therefore included an option (see XF86Config-4) for forcing the usage of VESA on such machines. Please not that the driver will automatically choose to use VESA if it detects a SiS630 _in_combination_ with an LVDS bridge. This behavior can be overruled by setting NoVESA. On the other hand (on machines with SiS630 and no or unknown bridges), you may set the option UseVesa to force the driver to use VESA (even though it would'nt do that otherwise). The options have no effect on chipsets other than SiS630. Thomas PS: I included the update in the files already, so please use the links I posted earlier this day (5 in the morning, to be exact). Thomas Winischhofer wrote: Hi everybody, I have just finished coding the new sis X driver. This one should finally do it on _ALL_ machines. It uses the BIOS' VESA interface to change the mode. I have tested it on three (Gericom) machines, so I really believe it works. Please _don't_ use any framebuffer driver when using this driver as it cannot restore graphics modes (yet). Binary (compiled for 4.1): http://members.aon.at/~twinisch/new_sis_drv.o.tar.gz (On Debian, sis_drv.o should be placed at /usr/X11R6/lib/modules/drivers/) Source (compiles well on CVS 4.1.99 and probably on 4.2): http://members.aon.at/~twinisch/new_sis_drv_src.tar.gz XF86Config-4: http://members.aon.at/~twinisch/new_xf86config-4.tar.gz Please read the XF86Config-4 file as it contains important information on how to use the driver in 24 bit depth mode. This time I have tested _all_ modes and they all worked on my machines. In case you want to use the old code (for some reason), set the option NoVesa (this is commented in XF86Config-4). The driver uses the old code if it detects a chipset other than SiS630 and a video bridge other than LVDS. Feedback welcome! I am tired now. The whole thing started with I want a driver for my notebook and got a real project (Egbert, you were right). My girlfried is really annoyed already. I hope everybody is satisfied now :) @Egbert: Der Code basiert größtenteils auf CVS von etwa vor 2 Wochen. Ich habe - anläßlich der Entwicklung von sisfb - auch einige Fehler in sis_bios.c behoben, die den Treiber (bei NoVesa oder auf bridge-losen Gfx-Karten) vermutlich besser funktionieren lassen. Schau Dir das mal an und inkludiere vielleicht Deine Patches (wenn es überhaupt welche gegeben hat; was Du mir am 17. Dezember geschrieben hast ist inkludiert [war wegen der TurboQueue, aber leider erfolglos, hat aber auch keinen negativen Effekt]. Mein Verdacht ist übrigens, daß es daran liegt, daß die Register für die Turboqueue in SiS300InitMode [in sis_vga.c; wird in ModeInit über *ModeInit aufgerufen], neu gesetzt werden; ich habe das aber nicht getestet. Der Stand ist nach wie vor, daß X bei eingeschaltener TurboQueue hängt, wenn man zwischen VT und X wechselt.) Sorry daß ich keine Patches gemacht habe, aber das ist mir - ehrlich gesagt - zu mühsam, da ich den Original-Code nicht mehr habe. Ich überlasse es selbstverständlich Dir, den Code zu committen.. :) (was mich, nebenbei gesagt, sehr freuen würde) @Rune: You should compile from source. I saw from your logs that you are using 4.1.99 and that sis_drv crashed when accessing the vbe extension. I believe this has to do with changes within vbe (changes in structures there) so I don't think you should use the binary. This means everyone of you using 4.1.99 by the way. Merry christmas! Thomas PS: Please don't forget to fill out the form I posted under SiS630 - newest info on the XPert list and please use the _new_ X driver for testing. Thank you. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SiS630 X-Mas
Hi everybody, I have just finished coding the new sis X driver. This one should finally do it on _ALL_ machines. It uses the BIOS' VESA interface to change the mode. I have tested it on three (Gericom) machines, so I really believe it works. Please _don't_ use any framebuffer driver when using this driver as it cannot restore graphics modes (yet). Binary (compiled for 4.1): http://members.aon.at/~twinisch/new_sis_drv.o.tar.gz (On Debian, sis_drv.o should be placed at /usr/X11R6/lib/modules/drivers/) Source (compiles well on CVS 4.1.99 and probably on 4.2): http://members.aon.at/~twinisch/new_sis_drv_src.tar.gz XF86Config-4: http://members.aon.at/~twinisch/new_xf86config-4.tar.gz Please read the XF86Config-4 file as it contains important information on how to use the driver in 24 bit depth mode. This time I have tested _all_ modes and they all worked on my machines. In case you want to use the old code (for some reason), set the option NoVesa (this is commented in XF86Config-4). The driver uses the old code if it detects a chipset other than SiS630 and a video bridge other than LVDS. Feedback welcome! I am tired now. The whole thing started with I want a driver for my notebook and got a real project (Egbert, you were right). My girlfried is really annoyed already. I hope everybody is satisfied now :) @Egbert: Der Code basiert größtenteils auf CVS von etwa vor 2 Wochen. Ich habe - anläßlich der Entwicklung von sisfb - auch einige Fehler in sis_bios.c behoben, die den Treiber (bei NoVesa oder auf bridge-losen Gfx-Karten) vermutlich besser funktionieren lassen. Schau Dir das mal an und inkludiere vielleicht Deine Patches (wenn es überhaupt welche gegeben hat; was Du mir am 17. Dezember geschrieben hast ist inkludiert [war wegen der TurboQueue, aber leider erfolglos, hat aber auch keinen negativen Effekt]. Mein Verdacht ist übrigens, daß es daran liegt, daß die Register für die Turboqueue in SiS300InitMode [in sis_vga.c; wird in ModeInit über *ModeInit aufgerufen], neu gesetzt werden; ich habe das aber nicht getestet. Der Stand ist nach wie vor, daß X bei eingeschaltener TurboQueue hängt, wenn man zwischen VT und X wechselt.) Sorry daß ich keine Patches gemacht habe, aber das ist mir - ehrlich gesagt - zu mühsam, da ich den Original-Code nicht mehr habe. Ich überlasse es selbstverständlich Dir, den Code zu committen.. :) (was mich, nebenbei gesagt, sehr freuen würde) @Rune: You should compile from source. I saw from your logs that you are using 4.1.99 and that sis_drv crashed when accessing the vbe extension. I believe this has to do with changes within vbe (changes in structures there) so I don't think you should use the binary. This means everyone of you using 4.1.99 by the way. Merry christmas! Thomas PS: Please don't forget to fill out the form I posted under SiS630 - newest info on the XPert list and please use the _new_ X driver for testing. Thank you. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
Now that it's Monday and you all read list mail again: I fixed the sisfb driver for use with LVDS video (LCD) bridges including the CHROMTEL 7005 TV converter. A lot of laptops using the SiS630 do not use the SiS301 but this one instead. The driver has only one problem: It doesn't know about timings, refresh rates and other data specific for various LCD panels and TV connectors. Instead, the current code contains empty tables for this. I inserted data read out from the BIOS to make it run on my machine. This is, of course, no solution. (I have only one machine with one 1024x768 LCD panel, so I can't ever find out all combinations for other, larger or smaller panels.) I will release a (quite huge) patch on the kernel list within the next few days where I will also change the driver to use the BIOS data (like the X driver does). Otherwise it will never work with bidges other than the SiS301. By the way: I had to implement about 200 changes into the code because somebody tried to implement support for SiS301B and 302 bridges, and broke LVDS instead. This code that this somebody wrote could by no means ever have worked on _any_ machine with a bridge other than SiS301 because of major programming glitches (using pointers and arrays doesn't seem to be that simple :) ). Have patience, Thomas PS: In the meantime I kindly ask you to test the driver published yesterday (available on my homepage, link below, follow link Linux on Gericom... and scroll down). Please check the log for what video bridge the driver detects and report your results. I am waiting impatiently. On my machine (SiS630 rev 31, LVDS+CHROMTEL bridge) the driver works perfectly, as long as I keep the TurboQueue disabled. I used it the last two days (day = 18 hours) and stress-tested it. Absolutely no problems here. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
Addendum: Egbert seems to be right with his assumption that X is spinning in a waiting loop within the 2D engine when switching back to X from another VT. How do I know this? Simply set the option NoAccel in XF86Config-4 - and it will work! I think we will have to reset the accelleration engine either when switching away from the server or when switching back. I am currently trying to find a awy to do this (yet unsuccessfully...) Thomas -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
Is everybody on vacation? :) I wrote: Addendum: Egbert seems to be right with his assumption that X is spinning in a waiting loop within the 2D engine when switching back to X from another VT. How do I know this? Simply set the option NoAccel in XF86Config-4 - and it will work! Even better and easier: Set Option TurboQueue to false (and leave NoAccel out) - this gives you acceleration and does not freeze X on switching VTs. In case the driver does not work, try removing all ModeLine statements from your XF86Config-4 file. I have been running the driver the entire day, with a lot of switching VTs and APM events, it never crashed or distorted the display. Thomas PS: I am currently debugging the sisfb driver - this piece of sh*t is pure chaos. In init.c are three (!) different (!) procedures to detect the video bridge - two of which work, one is completely out of date. The driver oopses and melts the screen on my machine because it detects a SiS302B video bridge (which is obviously wrong, since my machine has a LVDS bridge, which is correctly detected by the X driver) and tries to initialize the CRT1 (!) group - which I believe is meant for 310 and 315 chipsets only. Because of this, the driver (correctly) skips initializing the pointers to its 310-refreshtables - but later (because of his erratious assumption of a SiS302B bridge) tries to access them anyway. On the other hand, there are lots of wonderful LVDS tables in the files, but the driver simply ignores them after all - there is not a single reference to these tables! I can't imagine a single machine with a SiS630 (and possibly a LCD panel) where this driver does not crash! (Rene?) I believe, sisfb is the result of a lot of people fixing it for their very own machines only, breaking stuff for others. Who am I talking to by the way? I think I need some sleep. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
(Sorry for creating a monologue here...) Well, after porting Egbert's changes into the 4.1 driver, this situation is as follows: 1) Screen gets initialized correctly - as far as I can see. I have not yet recompiled the kernel to try without vesafb, but I can switch modes in X (CTRL-ALT-+/-). 640x480 flickers a little bit (looks like a CRT when the refresh rate is too low), but it works basically. 2) Switching between VTs and X causes the machine to somewhat freeze randomly when switching back to X, i.e. mouse and keyboard dead, network ok. The system seems alive and I can see the X screen, but I can only power down the box by pressing the power switch. 3) APM causes trouble, too. Suspend works, but during resume the machine freezes (for real this time)... resume process is never completed (PCMCIA does not come up again) and even the network is dead. Hm. The simularities seem to be point out a problem when re-initializing the screen (switching back from VT to X - resume). Furthermore, the problems are exactly the same for CVS version. Maybe I was too fast with my conclusions Thomas -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
Some further details on my testing: I have now compiled the current CVS driver for 4.1 (required just changing one line in sis_driver.c to get rid of xf86ReadDomainMemory() (if i recall correctly) and replacing it with (old) xf86ReadBIOS(). I don't know whether or not this is proper - but the driver does not complain about any unresolved symbols and comes up fine. I still see the following issues: 1) Disabling the VESA framebuffer for console mode did not change anything. The driver still makes the computer freeze every second or third time after switching to VTs and back (actually, the problem is switching back to X). I see green vertical lines of about 30 (?) pixels in height on top of the - otherwise correctly displayed - screen; mouse and keyboard dead, machine otherwise alive. (It seems what I see there is the text screen displayed in gfx mode.) I know when lockup it going to happen because the X screen shows up slightly quicker after pressing ALT-F7 than when it works. 2) APM: This works - sometimes. Resuming locks up the box about every second or third time. This seems to lock the machine hard, ie no network available any more. 3) I included Stuart Young's VesaFBHack patch and this makes the driver run correctly. I switched to VTs and suspended/resumed for about twenty times each now, flawlessly. I have not taken a closer look at the driver's current code yet, but I somewhat doubt that it's just are hardware problem. Even if the display doesn't get initialized correctly - and this is exactly what Stuart's patch skips - , this shouldn't cause a lock-up, am I right? Well, I'll keep testing. Thomas PS: Rene, the driver I mailed to you is the one I am talking about here, ie for 4.1 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: SiS630 - the neverending story
Thanks for replying, Egbert! On Thursday 13 December 2001 16:06, you wrote: Thomas Winischhofer writes: Well, after porting Egbert's changes into the 4.1 driver, this situation is as follows: 1) Screen gets initialized correctly - as far as I can see. I have not yet recompiled the kernel to try without vesafb, but I can switch modes in X (CTRL-ALT-+/-). 640x480 flickers a little bit (looks like a CRT when the refresh rate is too low), but it works basically. 2) Switching between VTs and X causes the machine to somewhat freeze randomly when switching back to X, i.e. mouse and keyboard dead, network ok. The system seems alive and I can see the X screen, but I can only power down the box by pressing the power switch. Do you have the impression that X is frozen or could it also be gpm which is still running and blocks the input devices? I don't have gpm running, so I suppose that's not the reason. Can you kill X from remote? I am sure i could do this (am at work and have no proper network here). The harddisk seems to keep writing log entries, so I really believe that the System is alive. I will test pinging the box (at least that's what the network here is good enough for). Could you please run strace on the Xserver to see where it is spinning? Well, erm... I am not really a hacker but I'll try. Does this require any special environment, any debug modes and such? Recompiling? 3) APM causes trouble, too. Suspend works, but during resume the machine freezes (for real this time)... resume process is never completed (PCMCIA does not come up again) and even the network is dead. Hm. The simularities seem to be point out a problem when re-initializing the screen (switching back from VT to X - resume). Furthermore, the problems are exactly the same for CVS version. Maybe I was too fast with my conclusions Could you please try the server flag option noPM? OK, I will and write again. Thomas ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 LCD - again (success)
Egbert Eich wrote: Well, I'm happy that I made at least some people happy! :) For the folks who have noticed that I used the domain branch: Thanks for notifying me. However, it does not make any difference. I now used the sis driver of MAIN branch for testing. The only patch I did was Stuart Young's VesaFBHack. Please note: Otherwise this is a pure 4.1 system! (Debian's 4.1.0-9, XFree86 not suid). I am not using VESA fb for console mode. Newest results: 1) Console switching This does not lock up the entire machine, just X. I can log in remotely and reboot the box (which seems to be quite busy, telnet(ssh) reacts very slowly) It happens only when switching back to X, it never happened when switching to a VT. It is more likely to happen after one has typed something on the console (I used vi for testing), although this is not entirely verified. Unfortunately, the problem is not systematically reproducible, although it happens averagly every third or fourth time when switching back to X from a VT. (This is where strace comes in, isn't it?) 2) APM Cannot test this at the moment, because I have general trouble with APM. Even with Stuart's patched driver the box does not resume when logged in as a user (???) (although APM worked before) so I have to fix that first. I assume I destoyed one or another file with my permanent reboots. (Anyone got an idea?) Thomas -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SiS630 LCD - again (success)
Just finished compiling CVS version from today (12/12) and ... SiS driver actually WORKS on my laptop (Gericom). No more melting screen! I could not perform intensive testing yet, but at the moment I am running X using the CVS driver without any distortion. Even the rectangle-bug I reported yesterday has disappeared. Thanks Egbert! I am running a Woody box with 4.1.0 installed. Had slight trouble setting CVS-X up aside my working installation. KDM does not come up (Client rejected, something with XDM-AUTHOTIZATION and Xlib: Protocol not supported shows up and kdm quits), so I simply run startx from console for testing at the moment. However, X locks up (freezes) the machine about every third time I am running startx; the screen remains black and I have to power the box down. The times it comes up, it works well. I am not sure about the reason for this but I suppose it's not the sis driver that causes trouble here. The log does not contain anyhing useful. Anyway: Thanks! Thomas Now that we seem to have an idea how to initialize the LCD - time to fix the kernel's sisfb ...! -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] http://www.webit.com/tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
I wrote: Egbert, could you shortly describe what exactly you changed in the xfree drive a) for fixing that rectangle bug, Never mind, already found your len-- b) for making in work on LCD panels? I guess this is all in sis_bios, I just copied the CVS files over the 4.1 ones and started the creation of the world. We'll see.. Thomas -- Thomas Winischhofer Vienna/Austria Check it out: mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw ICQ# 63288080 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
