Re: How Xserver build the makefil for dirver?
On Thu, Aug 03, 2006 at 10:27:43PM +0800, vichy.kuo wrote: Dear All: I need to build the via driver within XFree86_4_3 but I found via didn't support the driver until 4.4. I directly copy the via folder to the driver directory in 4.3, but the makefile cannot been build after typing make World. Is there any configure file I need to modify? Thanks all of you beforehand. Vichy Why don't you just use the driver at unichrome.sf.net. I still need to get it in line with 4.6, but that's on the TODO for the next release. Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: i945G 1280x768 sync polarity bug
On Tue, Jun 13, 2006 at 11:44:05AM +0100, Barry Scott wrote: Good question. We note that the EDID data wants these sync polarities. Does the monitor use the pulse widths or the polarity to tell one mode from another? We think that the polarity is used, but we are far from certain. Talking CVT here? as sync polarity there is used to flag H:V proportion. What problem are you trying to solve? If any of your monitors does have a problem requiring tight control over sync polarity, please provide a log with the EDID block dumped. Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: How do I convert 4.5.0 driver to 4.6.0?
On Tue, May 23, 2006 at 06:06:27PM +0100, Barry Scott wrote: You might want to approach the Unichrome author, Luc Verhaegen, for permission to use his code in Xfree86. Why would i need to give permission, or from a license point of view; how could i withhold permission? I'm not VIA, i don't drop copyrights unwarrantedly or insert bogus licenses surreptitiously; it's all nicely MITed, with proper disclaimers (with VIA permission) too. Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: How do I convert 4.5.0 driver to 4.6.0?
On Tue, May 23, 2006 at 06:06:27PM +0100, Barry Scott wrote: The via driver code that XFree86 ships in 4.5.0 and 4.6.0 does not work for XVIDEO on the CLE266 chip. The Xserver uses 100% CPU time and you have to reboot to get your machine back after Xine starts to play a movie. The via code from the Unichrome sourceforge project is very stable. I'm porting the unichrome driver to 4.6.0. This code is usually used with Xorg. You might want to approach the Unichrome author, Luc Verhaegen, for permission to use his code in Xfree86. There is a another version of the via code called the OpenChrome project. But their code is unstable (and the default in Xorg...). Oh and the code from via themselves is next to useless and very poorly written. Barry Barry, How much time have you already spent trying to get my code to build and run against xfree86 4.6.0? How much would it have cost you if you allowed me to bill you for the time i'd be spending on it? And when would you have had a working X and driver? Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Changes to via_drv.o solving problems of hardwired devices.
On Mon, May 09, 2005 at 02:51:59PM +0200, damian gruszka wrote: Hello, to support hardwired TV and LVDS devices, which doesn't apear on I2O bus I suggest following changes. The Option ConnectedDevice set the correesponding field in VIABIOSInfo.Since my routine and the the switch for ActiveDevice are quite similar, I also risked to replace this code by new visually shorter code. via.patch - contains combined changes done to .c and .h files. via_driver.c.patch, via_bios.h.patch and via_bios.c.patch - patches in separate files. Pls. comment this changes. Best Regards Damian You're grabbing a value from the CrtC registers [0x3d4/5] but your comments state SR32. SR tends to imply Sequencer register [0x3c4/5]. Please at least adjust one or the other. How global is this? I wouldn't be one bit surprised if this was all very kontron specific. I've been bashed by igel over something their bios did differently than the via bios (memory sizing), so this wouldn't exactly be a first. Also, from a quick review of the docs i scraped together, it seems that CR3E is the BIOS initialised active device listing. At least it seems to be that on the epia M. Then there's SR12, which (somewhat) outlines which is connected where... Luc Verhaegen. http://unichrome.sf.net/ ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Unichrome Pro
On Wed, May 04, 2005 at 03:30:51PM -0700, [EMAIL PROTECTED] wrote: I am returning to FreeBsd after an absense of years nd find myself trying to remember how to ride this bike with all its new bells whistles. I have an Abit AV-20 M/B that has an integrated Unichrome Pro Graphics with 2D/3D video controller. I am trying to install XFree onto FreeBSD 5.3 and am having trouble getting X11R6.4.5. to work. It seems I need a driver and noticed that in a discussion on the topic: FreeBSD 5.3 NVIDIA-1.0.7174 GLX extension problem Twas said by Randy Dawson: I wondered if there is a similar driver for the Unichrome. Also some more detailed instructions for the sequence of commands needed to successfully add new drivers and carry out the sysinstall would be much appreciated. Thanks David Abit VA-20 uses a VIA KM400, which makes it a plain unichrome. http://www.abit-usa.com/products/mb/products.php?categories=1model=226 The via driver should suffice. Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Fatal Error --? Video driver?
On Wed, May 04, 2005 at 02:50:00PM -0700, [EMAIL PROTECTED] wrote: For some reason this did not get posted http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/via/ The files in there have xf-4_5 tags... And what's there should be capable of running an X natively on a standard KM400 board. Thanks Luc -- but forgive me - my board is a VA-20 -- do you happen to know: (a) which one of the files I need AND (b) what do I have to do to get X11R6 to use it? Thanks again David Put Driver via in your Device Section. Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Fatal Error --? Video driver?
On Tue, May 03, 2005 at 05:18:28PM -0700, Tim Roberts wrote: [EMAIL PROTECTED] wrote: devel@XFree86.Org Hi I am trying to get XFree running on this configuration butno success so far. It looks likevsomething to do with the on board video The motherboard is ABIT VA-20 (www.abit.com) Integrated on board Unichrome Pro Graphics with 2D/3D/video controller 64 Meg of DDR ram allocated for video Total ram 1G The VIA Unichrome chip does not have a driver built-in to XFree86. VIA distributes one, but I don't know whether it plays with XFree86 4.5.0. Google for xfree86 unichrome for lots of hints. You should be able to run the vesafb driver. You won't get acceleration, but it should work. -- Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/via/ The files in there have xf-4_5 tags... And what's there should be capable of running an X natively on a standard KM400 board. Luc Verhaegen. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Problems with video card
On Tue, Dec 14, 2004 at 04:04:28PM +0100, [EMAIL PROTECTED] wrote: My card is a on-board of ASUS A7V8X-MX SE motherboard, the Integrated VIA Unichrome Graphics You could try setting a vesa video card just to see if everything works Please post you configuraton file too Or via. Luc Verhaegen. unichrome.sf.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Configuring VIA driver for TV out with overscan
On Fri, Aug 06, 2004 at 07:30:12PM -0700, Vladimir Testiler wrote: Hi, I have XFree86 version 4.4.0 and VIA CLE266. It is VIA EPIA M 10K mini-ITX motherboard. I am using S-video connector to connect it to Sony 32 TV. I am trying to get video to fill full screen, but it has small black borders on the sides. I am using VIA drivers and this is mine device section of XF86Config: Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor # [bool] #Option Dac6Bit # [bool] #Option Dac8Bit # [bool] #Option ForcePCIMode # [bool] #Option CPPIOMode # [bool] #Option CPusecTimeout # i #Option AGPMode # i #Option AGPSize # i #Option RingSize # i #Option BufferSize # i #Option EnableDepthMoves # [bool] #Option CrtScreen # [bool] #Option PanelSize # [str] #Option UseFBDev # [bool] Option TVVScan overscan Identifier Card0 Driver _DRIVER_ BusID PCI:_ADDRESS_ EndSection Option TVVScan overscan doesn't work. Could you help with it? Thanks According to PreInit code, it seems to accept over and under. This was inherited from VIA, and is hardly as urgent as most of the other problems we inherited from VIA. Luc Verhaegen. unichrome.sf.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4 - VIA driver - Option PanelSize
On Thu, Jul 29, 2004 at 08:58:04PM +0200, Owen.G wrote: 'Summary of new features in 4.4.0. A new driver for several VIA integrated graphics chipsets has been added.' The VIA driver documentation at www.xfree86.org says the VIA driver's display resolutions are: Option PanelSize string Specify the size (width x height) of the LCD panel attached to the system. Sizes 640x480, 800x600, 1024x768, 1280x1024, and 1400x1050 are supported. My LCD monitor (Samsung SyncMaster 172w) has the following attributes: Horizontal Frequency (Hz): 30-81 Vertical Frequency (Hz): 56-75 Maximum Resolution: 1280*768 silly question Even if I specify the horizontal and vertical refresh rates in xf86cfg myself, I'm not going to get 1280x768 on my display am I? /silly question Advice gratefully accepted. Owen This sounds like a standard LCD monitor, which you, since i still haven't seen actual unichrome hardware with DVI, probably have connected off a standard D-SUB/HD-15 VGA connector. In this case, the PanelSize option is (or should be) pretty much ignored. Given the current state of the via driver (this is inherited from via) it is quite impossible to freely set your own modes (i'm spending quite a bit of my time on this though). Fortunately, the modetables which via seems to prefer include 1280x768. Luc Verhaegen. unichrome.sf.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Vertical refresh with VESA driver
On Tue, Jun 15, 2004 at 09:59:45AM -0300, Paulo Mauricio Paes Barretto wrote: Hi, I have Mandrake 9.2 installed. Since my onboard VIA video isn't recognized, it is using VESA driver. I would like to know how can I get vertical refresh frequencies higher than 60Hz. My XF86Config-4 and XFree86.0.log files are attached. I've tryied some modifications in XF86Config-4, like adding specific ModeLines and changing options in Display Subsection, without success. The one attached is the original from installation. I've found in the log file lines suggesting that higher frequencies are possible, like: (II) VESA(0): Supported VESA Video Modes: (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): [EMAIL PROTECTED] But I can't understand the lines: (II) VESA(0): Attempting to use 85Hz refresh for mode 800x600 (114) (II) VESA(0): Attempting to use 85Hz refresh for mode 640x480 (111) ...attempting... and why not succeeding? Thank you for any possible help. Paulo What via video is this? The CLE266 and KM/N400 have usable support since xfree86-4.4.0 and you can easily compile the driver for 4.3.x. Luc Verhaegen ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Vertical refresh with VESA driver
On Tue, Jun 15, 2004 at 12:19:31PM -0300, Paulo Mauricio Paes Barretto wrote: The VIA chipset is KM400. I have, in a previous installation of Mandrake, successfully upgraded XFree86 to version 4.4.0 following the instructions in Install.txt and using Xinstall.sh. After upgrading, I changed the driver to via in Device Section. XFree started and worked, but I also coudn't get higher vertical refresh frequencies. In fact, I could get 1024x768 @ 75Hz, but my screen is not so big, and I want to use 800x600. These lines are from the VESA log file: (II) VESA(0): monitor1: Using hsync range of 31.00-65.00 kHz (II) VESA(0): monitor1: Using vrefresh range of 50.00-120.00 Hz and these values are correct for my monitor. Using the Via driver, I remember the range was much narrower in the corresponding lines. It seemed to me that was preventing the use of 800x600 at higher frequencies. There were also 4 messages of unresolved symbols in the log file. Well, then I gave up struggling with Via driver. I reinstalled Mandrake and tried to get what I need from Vesa driver. Is it possible to get 800x600 @ 75 or 85Hz from Vesa driver? If not, will you help me putting Via driver to work after upgrading again to 4.4.0? I'm about to give up using Linux because of a flickering screen. Thank you Paulo This section (from your vesa log) would be exactly the same using the via driver: (II) VESA(0): VESA VBE DDC supported (II) VESA(0): VESA VBE DDC Level 2 (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec. (II) VESA(0): VESA VBE DDC read successfully (II) VESA(0): Manufacturer: SNY Model: 0 Serial#: 1501602 (II) VESA(0): Year: 1996 Week: 28 (II) VESA(0): EDID Version: 1.0 (II) VESA(0): Analog Display Input, Input Voltage Level: 0.714/0.286 V (II) VESA(0): Sync: Separate Composite SyncOnGreen (II) VESA(0): Max H-Image Size [cm]: horiz.: 29 vert.: 21 (II) VESA(0): Gamma: 2.86 (II) VESA(0): DPMS capabilities: Suspend Off; RGB/Color Display (II) VESA(0): redX: 0.625 redY: 0.340 greenX: 0.280 greenY: 0.595 (II) VESA(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298 (II) VESA(0): Supported VESA Video Modes: (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): [EMAIL PROTECTED] (II) VESA(0): Manufacturer's mask: 0 (II) VESA(0): Supported Future Video Modes: (II) VESA(0): #0: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) VESA(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 With most CRTs you would also get frequencies and bandwidth reported. X, since 4.4.0, tries to use DDC directly, but it handles the lack of frequency information akwardly. Modes are selected on the basis of these frequency ranges, either specified in the config or from DDC. When this information is not available from DDC, X tries to calculate this from the modes specified, resulting in frequencies which are close but not 100% equal to those specified in, in this case, the monitors manual. This explains the difference in values you might see. It seems that vesa is using [EMAIL PROTECTED] I'm about to give up using Linux because of a flickering screen. Firstly, to me, this translates as: I don't care about this software one bit. Secondly, it is pretty close to blackmail. If this were irc, i would've stated fine. and put you on ignore. Oh, by installing programs directly, you are going in against your package management system, which jeopardizes the long term survivability of your installation. You should be able to find (src-)rpms of 4.4.0. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Pb with VIA S3G KM400/Xvideo on Acer Laptop
On 2004.03.10 18:49, Sébastien SOILEN wrote: Hello, I'm currently running an acer laptop with this stuff: Linux slackware 9.1 Kernel 2.6.3 Xfree 4.4.0 (packages from the xfree website) The graphic chip is a VIA S3G KM400 and the server use the right driver correctly as I can observe it. I encounter these issues: - No Xvideo adaptor present (checked with xvinfo), even if it seems to be allright in the config and log files - Once the server is running, I'm unable to use the consoles by using Ctrl+Alt+Fx: I have only black screen. When I shutdown the server, the same thing happen -- black screen... However, the consoles are functionnal, since it's always possible to log and run commands blindly... You'll find my log file below. There is no XV for km400 due to Via's excellent policy towards providing information freely. People are experimenting with it. About the VT issue, is there anything special about your kernel you wish to talk about? (fb for instance) If not, does this still happen when you switch to the vesa driver? Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Pb with VIA S3G KM400/Xvideo on Acer Laptop
On 2004.03.10 21:05, Sébastien SOILEN wrote: There is no more problems with terminals when I use the vesa driver. Here are the relative informations from .config file about graphic drivers on my kernel: # # Graphics support # CONFIG_FB=y # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y I read on this page http://www.xfree86.org/4.4.0/via.4.html that Xv extensions are supported for the VIA chips. Did I misunderstand what it means? There is a known issue with VT restoration, visible when using NetBSD or when X is competing with FB. The information on that page is not entirely correct. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Support for Matrox P650 / P750
On 2004.02.29 20:41, Lionel Lecoq wrote: Hi, I just had a look at the release notes for 4.4 I still find no indication of support for those cards... I like Matrox because I mainly do pictures processing. I feel that the quality of the display is better with Matrox (I have a 550) than with other cards (which compensate by being better for games than the Matrox)... Any idea when drivers for these two will become available? Cheers Lionel Matrox has a closed source driver. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xfree vesa only 800x600
On 2004.02.25 07:22, Ron Johnson wrote: Could you post a note to the list when that occurs? -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA http://cvs.sourceforge.net/viewcvs.py/unichrome/ Luc I. B. Verhaegen Melle, BE EU ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xfree vesa only 800x600
On 2004.02.24 15:33, [EMAIL PROTECTED] wrote: Hi ya all, I have a problem, with my X. ( no ;-) ) I run Debian sid, kernel 2.6.2, xserver-xfree8 4.3.0-2,gcc 3.3.2-3, so I upgraded my system and at start ( the next day ), my X goes only in 800x600 instead 1024x748, I use vesa driver because my laptop has Prosavage 8 on VIA KN400 chipset, and drivers does not function well. That's it, the /var/log/XFree86.0.log errors seems only to be: - Open APM failed (/dev/apm_bios) (No such file or directory) - VESA(0): VESA VBE DDC read failed - VESA(0): VBESetVBEMode failed...Tried again without customized values - VESA(0): Failed to set up write-combining range (0xf000,0x400) - (II) VESA(0): Total Memory: 1024 64KB banks (65536kB) (II) VESA(0): monitor1: Using hsync range of 31.50-48.50 kHz (II) VESA(0): monitor1: Using vrefresh range of 70.00-130.00 Hz (II) VESA(0): Not using mode 1024x768 (no mode of this name) (--) VESA(0): Virtual size is 800x600 (pitch 800) (**) VESA(0): Built-in mode 800x600 (**) VESA(0): Built-in mode 640x480 (++) VESA(0): DPI set to (100, 100) (II) VESA(0): Attempting to use 72Hz refresh for mode 800x600 (114) (II) VESA(0): Attempting to use 85Hz refresh for mode 640x480 (111) (**) VESA(0): Using Shadow Framebuffer but I didn't touched in anyway neither X nor anything concerned. I just killed X and poweroff'ed. What's going on? Help me please I can't stand 800x600 no more, since my video card is not supported ( :-(( why me! ) -- If a train station is where a train stops. Then what stops at a workstation? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 There is no longer a need to run vesa for the kn400 (the lcd issue was found by Johannes Specht last week). There is a working driver in current cvs, which i am using on an (older) debian-branches 4.3. There will be a few short howtos for getting via in a complete debian xfree86 (which is what i have been using for a while) or as a seperate package (need to decently look into debscripts, creating control and such manually is going to be a tad hairy :)) on unichrome.sf.net soon. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xfree 4.3.99 + via driver: Output only on external display
On 2004.02.10 23:15, Johannes Schlueter wrote: Hi, I'm running XFree86 on my Gentoo Linux (kernel 2.6) laptop. The laptop has an VIA KM400 chipset. lspci -v tells: ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xfree 4.3.99 + via driver: Output only on external display
On 2004.02.10 23:15, Johannes Schlueter wrote: Hi, I'm running XFree86 on my Gentoo Linux (kernel 2.6) laptop. The laptop has an VIA KM400 chipset. lspci -v tells: Right, that was daft, anyway: http://bugs.xfree86.org/show_bug.cgi?id=813 Please use the vesa driver. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Modeline for 1280x720 (=720p)
On 2004.02.05 06:06, Martti Kuparinen wrote: I tried that but it didn't work. I even tried with different combinations of UseBIOS, NoDDCValue and NoAccel without any luck. I've attached the logfile if that helps anything. Does this mean that the via driver and/or CLE266 is really that crappy and it's impossible to get 1280x720? Martti The via driver has its modes pretty much hardcoded. The closest thing in the open source driver is 1280x768. Isnt 1280x720 a hdtv resolution? Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] via driver limits
On 2004.02.03 11:07, Serge Basterot wrote: Hi, Finally XFree86 (4.3.99.902) started with NetBSD on KM400. But there are some problems. First, I can't write anything in every programs (xterm, vi etc.). I don't know if this is related to my system (possible error from myself) or if this is caused by the (experimental) driver. Second, I can't set screen size up to 800x600. I hope the driver will support 1024x768 soon. Could you tell me if I made mistakes, or if the driver have effectively thses limits ? Many thanks, PS: sorry for my bad english -- Serj The via driver is a perfect example of what one shouldnt call open source driver, it is available as source, anyone can see it (at least the version dragged into xfree86, you have to ask via nicely and wait for a month for any changes they themselves attempted), and it somewhat works in some manner (already vastly improved through nothing more than guesswork by several people, one of which is Alan Cox) It is buggy, unmaintainable code which vaguely ressembles what should be an xfree86 driver released without documentation (or an offer for) by via because they quite likely couldnt get it anywhere themselves. There is a problem with restoring the registers when switching to textmode (reported by Martti Kuparinen in january, confirmed by Matthieu Herb that this sort of problem would only be seen on openbsd, which is why i mention this here, there are a lot of problems with this driver and several people are trying to fix them). I'm postponing an actual bugreport as this will not get fixed before 4.4 is released. I have noticed a text rendering problem myself, i'm not sure who reported it but someone did back in november, as soon as it can be reproduced it will be reported properly too. Characters or whole strings are not rendered just resulting in small patches of blank spaces where letters should be. If this is what you mean with I can't write anything in every programs and if this is reproducable, then this can be looked into now. If this is not what you meant, please give more details. About the via_driver and modes, it is a complete mess. And that's not counting in the fact that it only allows a few hardcoded resolutions and refresh rates. Please attach a normal log where you attempt to use 1024x768(from within your screen section) in your response. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] via driver limits
On 2004.02.03 19:30, Serge Basterot wrote: In fact it's a problem with my keyboard and not with the driver (a Logitech Internet Keyboard). Bugger. I put my XF86Config et the log here : http://serge.basterot.free.fr/fichiers/ (II) via(0): Monitor0: Using default hsync range of 31.46-54.57 kHz (II) via(0): Monitor0: Using default vrefresh range of 70.07-100.00 Hz Notice how the vertical range starts at 70.07Hz. This is because the DDC information retrieved from your monitor does not include actual hsync/vrefresh information, but it does include a list of usable modes and the hsync/vrefresh ranges are guessed from these modes. This whole DDC functionality is quite new (this was not present in 4.3.0) and guessing ranges from modes is even newer and not completely functional yet. You have provided ranges from your monitors documentation but this is overridden by the information retrieved through DDC. Please specify Option NoDDC in your Device section to resolve this. The via driver knows NoDDCValue but this will be dropped and should thus be ignored. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with an integrated graphic card!
On 2004.02.02 11:32, Luca Martella wrote: Hello everybody! I don't know what to do... I've a CHYANG FUN motherboard (CFI-S86 is the name of the model) with an integrated S3 ProSavage8 video controller... I tried to start 'X -configure' and this is what it sayd : XFree86 has found a valid card configuration Unfortunately the appropriate data has not been added to xf86PciInfo. h In the attachment you will find the log and the output of 'scanpci - v' Thanks in advance and thanks for your good work! Luca Martella [EMAIL PROTECTED] 2004-02-02 The pci id for this chip has been added to the via driver in cvs on Wed Oct 2 20:39:55 2002 UTC and thus made it into xfree86-4.3.0 Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] CLE266 problems
On 2004.01.25 08:09, Martti Kuparinen wrote: http://users.piuha.net/martti/tmp/IMGP2694.JPG I can type anything but only the first line is okay. The above picture was taken after quitting X and pressing Ctrl+L. I don't know what went wrong but I could start the vesa driver. I even ran xf86cfg and selected vesa but X didn't start. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Try selecting 800x600 and 640x480 in your Screen section. Have you tried another operating system with this hardware? (linux for instance) You wouldnt need to install much, just enough to compile a cvs Xfree86. There is a high probability that this is caused by the via_driver but we should find out what exact combination makes this happen. Luc Verhaegen ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] CLE266 problems
On 2004.01.25 11:39, Martti Kuparinen wrote: On Sun, 25 Jan 2004, Luc Verhaegen wrote: Try selecting 800x600 and 640x480 in your Screen section. Have you No luck (with 640x480). You attached a config friday, can you set Driver in Section Device to vesa and add 640x480 to your screen section (no need to bother with xf86cfg) and attach the full log? I tried Slackware (with 2.4.22) and cvs xfree86 from 2004-01-22. Everything is okay in Linux (I've attached the log file), no sign of any corruption. Great, that leaves us netbsd + xfree86 with or without the via_driver, depending on what vesa will get us. Trouble is, i am utterly clueless about the BSDs. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] CLE266 problems
On 2004.01.25 12:50, Matthieu Herrb wrote: One thing to note about this (and other similar reports that XFree86 leaves the text console garbled on exit on NetBSD and OpenBSD) is that the Linux console driver does its own VGA registers save/restore when switching VTs, while the wscons driver used by NetBSD and OpenBSD doesn't save/restore anything. I don't know if the proper fix is to duplicate the code from the Linux console driver in the X server for the systems that need it, or to add this feature to the wscons driver. Matthieu Hrm, Martti, have you followed http://www.xfree86.org/4.3.0/NetBSD7.html#16 Your log has (--) Using wscons driver in pcvt compatibility mode (version 3.32) Matthieu, does this mean that X/wscons is lacking in this area, or that problems storing/restoring console within a driver will only be revealed when using netbsd? Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] CLE266 problems
On 2004.01.23 16:06, Martti Kuparinen wrote: Does this happen every time you switch to a console (without actually quitting X)? Yes. I can switch back to X. I can even quit X and from the corrupted console start X again. up ok when you switch back? Please define latest XFree86 sources ROOT h118:~/xc cvs update -dPA ROOT h118:~/xc ROOT h118:~/xc TZ=UTC date Fri Jan 23 10:09:33 UTC 2004 I then applied these changes: ROOT h118:~/xc/programs/Xserver/hw/xfree86/drivers/via cvs diff Index: via_driver.c === RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/via/via_driver. c,v retrieving revision 1.23 diff -r1.23 via_driver.c 1923c1923 CARD8 tmp --- CARD8 tmp; Index: via_driver.h === RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/via/via_driver. h,v retrieving revision 1.10 diff -r1.10 via_driver.h 29a30 #define DEBUG_PRINT Martti --- Can you tell me more about the corruption you are seeing in textmode? Is the first line the line at the very top of the screen or is it the current line? What is garbage? Random values printed as characters? What happens if you type? Also, can you try the vesa driver and verify that this is a problem only with the via driver? Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] CLE266 problems
On 2004.01.12 11:16, Martti Kuparinen wrote: Hi! My previous posts didn't make it to the list so I'll try one more time... I'm trying to configure X on my Mini-ITX server (the latest NetBSD/ i386 development version) with integrated CLE266. I've fetched the latest XFree86 sources with cvs and compiled everything. I then ran xf86cfg. After this the screen goes to power save (=no signal) and there's no way to get back to the console (C+A+Backspace doesn't work). I logged into the server with ssh and the xf86cfg process was still running. I killed it but the screen remains without signal. The only way to get normal text console was to reboot the whole system. Any ideas what's wrong? http://users.piuha.net/martti/tmp/XF86Config http://users.piuha.net/martti/tmp/XFree86.8.log Martti ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 I know that the via driver returns FALSE in VIAPreInit before it actually probes the ddc. This is one of my TODOs, i will look into it shortly. I am sorry, but i can not provide further information at current, i will get back to you. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] In response to - as requested - Epox mainboard Via KM400 Unichrome
unknown) STATUS0x0210 COMMAND 0x0001 CLASS 0x04 0x01 0x00 REVISION 0x50 BASE0 0xdc01 addr 0xdc00 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x03 INT_LINE 0x05 BYTE_00xcc01 BYTE_1 0x00 BYTE_2 0x80746fc BYTE_3 0x pci bus 0x cardnum 0x12 function 0x00: vendor 0x1106 device 0x3065 VIA Device unknown CardVendor 0x1695 card 0x3005 (Card unknown) STATUS0x0210 COMMAND 0x0007 CLASS 0x02 0x00 0x00 REVISION 0x74 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08 BASE0 0xe001 addr 0xe000 I/O BASE1 0xea001000 addr 0xea001000 MEM MAX_LAT 0x08 MIN_GNT 0x03 INT_PIN 0x01 INT_LINE 0x0b BYTE_00xfe020001 BYTE_1 0x00 BYTE_2 0x8074a74 BYTE_3 0x pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1106 device 0x7205 VIA Device unknown CardVendor 0x1106 card 0x7205 (VIA, Card unknown) STATUS0x0230 COMMAND 0x0007 CLASS 0x03 0x00 0x00 REVISION 0x01 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 BASE0 0xe408 addr 0xe400 MEM PREFETCHABLE BASE1 0xe800 addr 0xe800 MEM MAX_LAT 0x00 MIN_GNT 0x02 INT_PIN 0x01 INT_LINE 0x0b Gena __ Using the freedom of Debian GNU Linux ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 This is what is known to the via driver itself: via_regs.h:#define PCI_CHIP_CLE31220x3122 via_regs.h:#define PCI_CHIP_CLE30220x3022 via_regs.h:#define PCI_CHIP_VT3205 0x3205 via_regs.h:#define PCI_CHIP_VT7205 0x7205 via_regs.h:#define PCI_CHIP_VT3204 0x3204 via_regs.h:#define PCI_CHIP_VT7204 0x7204 Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xwindows VIA driver problem
On 2004.01.05 19:22, Warren wrote: Hi, Using the X VIA driver (KT266) version 4.3.99.16, every version of doom out there (lsdldoom, llxdoom, prboom) locks up the system shortly after initializing the sound. Using the vesa driver works fine with everything else being the same. I notice that there is a more recen version available, unfortunately my development system is packed at the moment. If you happen to know that a more recent version will fix this problem, please (Please! Please!) email me and let me know so that I can get the latest. Regards, Warren Melnick CTO CAC Media ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 There are quite a number of known issues with the via driver, i am not certain what causes your problems, but it might be a DRI/DRM issue. Alan Cox has reported that he has his DRI working, and that he has submitted his changes. You will find people submitting their binaries on http://forums.viaarena.com/categories.cfm?catid=28forumid=1 But, even though i think that the users of that forum are in good faith, this is not affiliated to xfree86.org and therefor binaries should be treated with the necessary caution. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xwindows VIA driver problem
On 2004.01.06 15:42, Ben Phillips wrote: Luc Verhaegen sez: You will find people submitting their binaries on http://forums.viaarena.com/categories.cfm?catid=28forumid=1 But, even though i think that the users of that forum are in good faith, this is not affiliated to xfree86.org and therefor binaries should be treated with the necessary caution. Just out of curiosity, what would the necessary caution be in the case of a linux binary? Besides just not using it? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 There is only not using it. I'm just trying to say that when it leaps out, empties the fridge and the drinkscabinet and starts singing questionable songs at the top of its voice at 4 in the morning, i nor xfree86 should be held accountable. I know that the license states no warranty and this and that... but extra caution is needed with binaries posted on a forum. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Building xfree on Debian
On 2004.01.02 16:18, kamesh wrote: Hi, I'm trying to build xfree 4.0.3 from sources, adding the following line on the site.def file: define LinuxDistribution LinuxDebian Compilation process starts, but it soon stops signaling Makefile.proto:1240: *** missing 'endef', unterminated 'define'. Stop. I tried to build without modifing site.def, and the proceess go without troubles. What shoud I do to personilize xfree for my disribution? Thank you. Fabrizio. -- Il Buddha, il Divino, dimora nel circuito di un computer o nell'ingranaggio del cambio di una moto, con lo stesso agio che in cima a una montagna o nei petali di un fiore. Robert M. Pirsig ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 check out http://necrotic.deadbeast.net/xsf/XFree86/ This is the main repository of the X strike force. step by step: mkdir xfree86-4.3.0, descend into this grab xfree86_4.3.0.orig.tar.gz, gunzip, bzip2, rename to xfree86-4.3.0. tar.bz2 grab the latest branches-4.3.0-sid-debian... tarball, untar run dpkg-buildpackage -rfakeroot wait. Luc Verhaegen. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: VIA Driver problems
On 2003.12.20 15:49, Jan Thorsson wrote: Hi folks, I've just compiled 4.3.99.902 on my PC runing NetBSD-current. As with previous versions of XFree86 I found that the VIA driver still crashes due to a problem with the VIAFindModeUseBIOSTable() function in via_bios.c. This function uses a field that is not initialized: /* Default settings have not been loaded, they must be obtained from the BIOS */ pBIOSInfo-pUTUSERSETTING-DefaultSetting = FALSE; When I try to start X the value of pBIOSInfo-pUTUSERSETTING is NULL. This causes a segmentation fault. I can't find any initialization at all of this field in the code, so I tried to allocate memory to the field: *** via_driver.c.orgSat Dec 20 14:43:24 2003 --- via_driver.cSat Dec 20 14:16:49 2003 *** *** 449,454 --- 449,456 xnfcalloc(sizeof(VIABIOSInfoRec), 1); ((VIARec *)(pScrn-driverPrivate))-pBIOSInfo-pModeTable = xnfcalloc(sizeof(VIAModeTableRec), 1); + ((VIARec *)(pScrn-driverPrivate))-pBIOSInfo-pUTUSERSETTING = + xnfcalloc(sizeof(UTUSERSETTING), 1); /* initial value in VIARec */ ((VIARec *)(pScrn-driverPrivate))-SavedReg.mode = 0xFF; With this, the Xserver starts and it seems to work. OK, I still have some problems when exiting X. I don't know if this is the right way to solve this problem, but it is easy to understand that the server crashes without some form of initialization of this field. - Jan Was reported before (see following bugreport content). Now Opened as http://bugs.xfree86.org/show_bug.cgi?id=1006 Luc Verhaegen. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
