Please unsubscribe me from the mailing list ...
Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Please unsubscribe me from the mailing list ...
Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Please unsubscribe me from the mailing list ...
fyiDo you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Fri, 24 Jan 2003, Wayne Whitney wrote: On Fri, 24 Jan 2003, Marc Aurele La France wrote: Hummm. Can you re-post that log again? The output from `scanpci -v` would also help. OK, I've included three things below: the original log, the output of 'scanpci -v', and the patch to getValidBIOSBase() that allows my secondary PCI Radeon 7000 to be initialized. In case it is important, the 'scanpci -v' output was generated after booting and running X on my primary AGP Radeon VE, without using the secondary PCI Radeon 7000. OK, thanks. Please try the attached. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. Whitney.diff.gz Description: Binary data
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Mon, 27 Jan 2003, Marc Aurele La France wrote: OK, thanks. Please try the attached. That patch works great! Thank you very much. In case it is of interest, I have appended below the int10 hunk of a diff of the log files with your patch--XFree86.0.log is on the primary AGP RADEON VE and XFree86.1.log is on the secondary PCI RADEON 7000. I thought I would mention the two other problems I still have with my setup, in case they are of interest to you. 1) If I attempt to run multihead using both cards with the latest CVS version (fix 789), I get the following error: (II) Reloading /usr/X11R6-CVS/lib/modules/drivers/radeon_drv.o Symbol xf86SetDDCproperties from module /usr/X11R6-CVS/lib/modules/drivers/radeon_drv.o is unresolved! This is an improvement from a few days ago, when there were many Symbol unresolved messages. 2) There is a text mode corruption problem with the PCI Radeon 7000. It occurs as soon as XFree86 is run on this card after it has been initialized. So if the PCI card is initialized by the BIOS, it occurs the first time I run XFree86; if the AGP card is initialized by the BIOS, it occurs the second time I run XFree86 on the PCI card. The text mode is corrupted to a bunch of flashing half block characters, and this occurs before the display enters graphics mode. In case it is useful, I have included below the full diff between the log file when I first run XFree86 on the PCI Radeon 7000 and the second time I run XFree86 on it, when the corruption occurs. This is with the system BIOS set to initialize the AGP card. Thanks again for your help! Cheers, Wayne --- /var/log/XFree86.0.log 2003-01-27 10:10:43.0 -0800 +++ /var/log/XFree86.1.log 2003-01-27 10:11:04.0 -0800 @@ -360,13 +358,10 @@ compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): initializing int10 -(II) RADEON(0): Primary V_BIOS segment is: 0xc000 -(WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d00 -(WW) RADEON(0): Restoring CONFIG_MEMSIZE (0200), setting to 0200 -(WW) RADEON(0): Restoring MPP_TB_CONFIG31:24 (04), setting to 01 +(II) Truncating PCI BIOS Length to 49152 (--) RADEON(0): Chipset: ATI Radeon VE QY (AGP) (ChipID = 0x5159) -(--) RADEON(0): Linear framebuffer at 0xd800 -(--) RADEON(0): MMIO registers at 0xe900 +(--) RADEON(0): Linear framebuffer at 0xe000 +(--) RADEON(0): MMIO registers at 0xeb02 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 3 --- /var/log/XFree86.1.log.old 2003-01-27 10:11:04.0 -0800 +++ /var/log/XFree86.1.log 2003-01-27 10:11:59.0 -0800 @@ -16,7 +16,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: /var/log/XFree86.1.log, Time: Mon Jan 27 10:10:59 2003 +(==) Log file: /var/log/XFree86.1.log, Time: Mon Jan 27 10:11:56 2003 (==) Using config file: /etc/X11/XF86Config (++) ServerLayout Layout1 (**) |--Screen Screen1 (0) @@ -344,7 +344,7 @@ (II) Module vgahw: vendor=The XFree86 Project compiled for 4.2.99.4, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 -(II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03b0, hwp-PIOOffset is 0x +(II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) RADEON(0): PCI bus 0 card 8 func 0 (**) RADEON(0): Depth 16, (--) framebuffer bpp 16 (II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps) @@ -358,11 +358,15 @@ compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): initializing int10 -(II) Truncating PCI BIOS Length to 49152 +(EE) RADEON(0): Cannot read V_BIOS +(WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d00 +(WW) RADEON(0): Restoring CONFIG_MEMSIZE (0200), setting to 0200 (--) RADEON(0): Chipset: ATI Radeon VE QY (AGP) (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xe000 (--) RADEON(0): MMIO registers at 0xeb02 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) +(WW) RADEON(0): Video BIOS not detected in PCI space! +(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space! (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 3 (II) Loading sub module ddc @@ -378,7 +382,7 @@ compiled for 4.2.99.4, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C bus DDC initialized. -(II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=15000 +(II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12500 max=35000; xclk=18300 (==) RADEON(0): Using gamma
Re: Cyberpro 20x0 driver?
At at previous job I was responsible for XFree86 Cyberpro drivers. Tvia (www.tvia.com) had supplied us with source code for their XFree86 4.x Cyberpro driver that worked reasonably well. I did have to make a few fixes and we did add some enhancements. The point of this is that Tvia does develop and maintain XFree86 drivers for their Cyberpro series. Why these are not available at least as binary downloads from their web site eludes me. Tvia does try to earn extra income from selling their SDK's. As of a year ago when I working on this the SDK's did not include the XFree86 driver sources, we had to obtain that separately. I suspect the reason Tvia has not open sourced their driver is a function of their wanting to derive income from the sale of their SDK's. My personal opion of their SDK's and their doc was it was not worth the price they were asking. However, having said that, I did find it essential to have the SDK's in order to work on the driver because the SDK's provided example code to perform certain functions which at the time were not part of the driver. I think Tvia suffers the same type of myopia that many small vendors suffer from. They would generate more income via increased hardware sales by opening up their source pool then the amount of income they generate by selling their marginal SDK's to a handful of partners. Maybe it would be worthwhile for someone to press them on this issue. John ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Bison/Yacc problems ...
After opening the 4.2.0 tar balls and applying the 4.2.0-4.2.1 patch, I find I'm getting a compiling error when bison tries to process the file ./lib/Xft/xftgram.y. The CVS/RCS ID for the file is: $XFree86: xc/lib/Xft/xftgram.y,v 1.5 2001/05/16 10:32:54 keithp Exp $ And the error I get is this: bison -y -d xftgram.y xftgram.y:168.8: parse error, unexpected :, expecting ; or | xftgram.y:169.3-6: $$ of `matrix' has no declared type make[3]: *** [xftgram.c] Error 1 I checked the other *.y files in the distro, and there are other instances of what appears to be misplaced/missing semicolons in the grammar rules sections. From the ./xc directory, I looked for all (six or seven) *.y files and tried each with BISON version 1.75. I modified them all by hand (unwittingly adding semicolons where they made syntactical sense to me to put them), and the compilation now seems to be progressing smoothly as I write this. The whole exercise took only a few minutes. As I'm new to X-Windows, particularly to XFree86 and its source code, could someone verify this? Thanks, - Jamie ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Bison/Yacc problems ...
On Mon, Jan 27, 2003 at 03:17:27PM -0500, Jamie Risk wrote: After opening the 4.2.0 tar balls and applying the 4.2.0-4.2.1 patch, I find I'm getting a compiling error when bison tries to process the file ./lib/Xft/xftgram.y. The CVS/RCS ID for the file is: $XFree86: xc/lib/Xft/xftgram.y,v 1.5 2001/05/16 10:32:54 keithp Exp $ And the error I get is this: bison -y -d xftgram.y xftgram.y:168.8: parse error, unexpected :, expecting ; or | xftgram.y:169.3-6: $$ of `matrix' has no declared type make[3]: *** [xftgram.c] Error 1 I checked the other *.y files in the distro, and there are other instances of what appears to be misplaced/missing semicolons in the grammar rules sections. From the ./xc directory, I looked for all (six or seven) *.y files and tried each with BISON version 1.75. I modified them all by hand (unwittingly adding semicolons where they made syntactical sense to me to put them), and the compilation now seems to be progressing smoothly as I write this. The whole exercise took only a few minutes. As I'm new to X-Windows, particularly to XFree86 and its source code, could someone verify this? well, sure - bison 1.75 is known to do that sort of thing. (it's possible to write yacc-compatible scripts for bison, but it's getting harder). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4 Test report : Ctr-Alt-BkSpc status?
David Dawes wrote: On Sun, Jan 26, 2003 at 03:06:36AM -0500, Kevin Brosius wrote: Does the server work correctly other than the key sequence not working? If it is stuck somewhere, it might explain both why SIGTERM and SIGHUP didn't do anything and why the terminate key sequence didn't work. Yes, the server seems to work fine, other than ignoring Ctl-Alt-BkSpc. Other Alt sequences work, like Ctl-Alt-+. Those other sequences are handled in the same way as Ctl-Alt-BkSpc, so it does point to the mapping for that one getting overriden after the X server starts. Could you send the 'xmodmap -pk' output? Are you running any xmodmap script as part of your startx/xdm rc files that might be re-mapping the BackSpace key? The patch doesn't seem to make a difference. I've attached xmodmap -pk. The only difference I see between yours and mine is that mine has the following for the backspace key: 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) while yours is: 22 0xff08 (BackSpace) xmodmap scripts, that may be it. It looks like SuSE uses a .xinitrc which may call 'xmodmap /usr/X11R6/lib/X11/Xmodmap' if it exists and XSESSION_IS_UP is set. Although it comments that XSESSION_IS_UP is set by xdm, which I am not running. If it where set, it would use an old Xmodmap, as I've changed ProjectRoot on this machine and that default path is an older version, 4.1.0. Other than that, I don't see anything calling xmodmap. And I don't think it's calling that one, since it's xdm related. A way to double-check this is to run something like: startx /path/to/your/twm or just: 'XFree86' and see if the server terminate sequence works then. Yes, this case works. So, something in my setup (an xmodmap call I haven't located yet?) is incompatible with the recent changes? When started this way, running xmodmap -pk against the server does show: 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Mon, 27 Jan 2003, Marc Aurele La France wrote: On Mon, 27 Jan 2003, Wayne Whitney wrote: 2) There is a text mode corruption problem with the PCI Radeon 7000. It occurs as soon as XFree86 is run on this card after it has been initialized. So if the PCI card is initialized by the BIOS, it occurs the first time I run XFree86; if the AGP card is initialized by the BIOS, it occurs the second time I run XFree86 on the PCI card. The text mode is corrupted to a bunch of flashing half block characters, and this occurs before the display enters graphics mode. This appears related to issues being discussed on a different thread. I'll wait to see what happens there, before doing anything about it. Indeed, I hadn't noticed that thread on the xfree86 list (on radeon 7200 support). The patch discussed there, which I include below, gets rid of the text mode corruption I'm seeing. I'm all for it. I also attached the current diff between the log files when I run XFree86 the first and second times on my PCI Radeon 7000. I assume the differences are harmless. Thanks again for all your help! Cheers, Wayne --- radeon_driver.c.~1.81.~ 2003-01-26 18:54:43.0 -0800 +++ radeon_driver.c 2003-01-27 15:56:42.0 -0800 @@ -405,7 +405,7 @@ extern int gRADEONEntityIndex; -#if 0 /* !defined(__alpha__) */ +#if !defined(__alpha__) # define RADEONPreInt10Save(s, p) # define RADEONPostInt10Check(s, p) #else /* __alpha__ */ --- /var/log/XFree86.2.log.old 2003-01-27 15:59:13.0 -0800 +++ /var/log/XFree86.2.log 2003-01-27 15:59:29.0 -0800 @@ -16,7 +16,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: /var/log/XFree86.2.log, Time: Mon Jan 27 15:59:08 2003 +(==) Log file: /var/log/XFree86.2.log, Time: Mon Jan 27 15:59:25 2003 (==) Using config file: /etc/X11/XF86Config (++) ServerLayout Layout1 (**) |--Screen Screen1 (0) @@ -344,7 +344,7 @@ (II) Module vgahw: vendor=The XFree86 Project compiled for 4.2.99.4, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 -(II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03b0, hwp-PIOOffset is 0x +(II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) RADEON(0): PCI bus 0 card 8 func 0 (**) RADEON(0): Depth 16, (--) framebuffer bpp 16 (II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps) @@ -358,11 +358,13 @@ compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): initializing int10 -(II) Truncating PCI BIOS Length to 49152 +(EE) RADEON(0): Cannot read V_BIOS (--) RADEON(0): Chipset: ATI Radeon VE QY (AGP) (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xe000 (--) RADEON(0): MMIO registers at 0xeb02 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) +(WW) RADEON(0): Video BIOS not detected in PCI space! +(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space! (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 3 (II) Loading sub module ddc @@ -378,7 +380,7 @@ compiled for 4.2.99.4, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C bus DDC initialized. -(II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=15000 +(II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12500 max=35000; xclk=18300 (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEON(0): Validating modes on Primary head (DDCType: 2) - (II) RADEON(0): I2C device DDC:ddc2 registered at address 0xA0. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: register for video memory
There is a standard VESA VGA call. http://freespace.virgin.net/hugo.elias/graphics/x_svga_i.htm There is a different way to do this in XFree. Look at the Adjust() function in the drivers. http://www.xfree86.org/3.3.6/VGADriver6.html#16 Roger On Fri, 2003-01-24 at 11:40, [EMAIL PROTECTED] wrote: Hi, I am looking for the registers that can specify the video memory's offset where the image is shown on the screen. Does this register exist? If it does, can someone tell me any hint or keyword so that I can search it in related data sheets? My graphic card is ATI Radeon 7500. Thanks in advance, jing ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel -- roger [EMAIL PROTECTED] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [I18n] Unknow Font Foundry??
A I tried to install Lao OT fonts and got the following error message. A (none):/usr/share/fonts/defaults/TrueType# ttmkfdir fonts.scale A unknown font foundry code JG A unknown font foundry code LSW The fonts use font foundry codes that were not registered with Microsoft. Both ttmkfdir and mkfontscale will generate XLFD foundry names that are merely ``misc''; the fonts will still work. Could you please use ttfdump and tell me what the ``Copyright'' string in those fonts says? You'll find ttfdump somewhere on ftp.freetype.org. Juliusz ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
[XFree86] startx not running
hi my computer has intel D845GLLY motherboard with built in graphics card. log file is attached Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com XFree86.0.log Description: XFree86.0.log
[XFree86] Antialiasing and dual monitor with ATI Radeon 9000
Hi, my first question is about the antialiasing feature of the ATI Radeon 9000 (called smoothvision): How can I use/activate this feature under Linux? Secondly, I would like to use the dual monitor feature of this graphics card. Activating it using the ATI Control panel doesn't have any effect. In fact, when I start the X server I only have output on one monitor, otherwise I get output on two monitors. I use the new Linux drivers provided on the ATI webpage. Could someone, please, help me? Rainer Blum - Rainer Blum Entwickler idmk - Institut für digitale Medien und Kommunikation GmbH Germany Internet: http://www.idmk.de ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500Mobility)
I guess this doesn't happen with DRI disabled? Looks like pure luck to me that RADEONWaitForVerticalSync() ever returns when the DRM handles vertical blank interrupts. I'll look into fixing that if noone beats me to it. True, the problem doesn't occur unless DRI is enabled. 2. I was using KDM and after exiting X my machine would lock up as it tried to restart the login screen. I think that even without KDM I couldn't restart X after I started it once. I'm not positive about this though. Can you verify that? Would be interesting to know. Nope, I can't verify it. I guess my system just got into a bad state somehow. I'm using 4.2.99.4 right now and have successfully restarted X many times. I haven't tried using KDM again though. I'm almost ready to switch to this release for everyday use, but I still have to see how it handles a suspend/resume cycle. I saw that Charl's dri_resume patch isn't in yet, which is a shame. I guess no DRI for me for the near future. I suppose that's already true if I want to use dual-head though. For some reason anti-aliasing has ceased too. Oh well, a problem for another day. -- -- Nathaniel Gray -- Caltech Computer Science -- -- Mojave Project -- http://mojave.cs.caltech.edu -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] W32 and ET6000
hi I've just installe mandrake 8.0, and get a fatal error while booting. I've attached the XFree86.0.log. I've installed the various components: XFree86-server-common libfont.so.1 libintl.so.2 XFree86-W32-3.3.6-25.1mdk.i586 Now I'm not sure where to go from here. Any help would be appreciated! christine floppy Description: Binary data
Re: [XFree86] W32 and ET6000
Christine [EMAIL PROTECTED] writes: I've just installe mandrake 8.0, and get a fatal error while booting. I've attached the XFree86.0.log. Hmm. I really cannot se just how some of the values from the log file could arise with a working card, among other things it detects 0MB available memory on the card, and also the DACSpeed value (Max pixel clock) is completely wrong. There have been quite a few improvements to the driver for the et6k since version 4.0.3, you might want to try a newer version of XFree86 as well. XFree86-W32-3.3.6-25.1mdk.i586 This server/driver is not for the et6k, only for some et4k-based cards. Don't use it here. (It isn't used currently either. :) It might help if you sent the contents of /etc/X11/XF86Config-4 to see if there is something wrong specified there. Part of the problem is that I don't think there are any developers left with a working et6k card to test things on. So the driver are slowly getting less and less updates. Common problem with sufficiently old hardware, sadly. -Harald -- Harald Nordgård-Hansen, Linpro AShttp://www.linpro.no/~hnh/ PB. 375, N-1601 Fredrikstad, NorwayPhone/Fax: +47 6935 2424/25 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] startx not running
hi my computer has intel D845GLLY motherboard with built in graphics card. log file is attached Try to edit SCREEN and MONITOR sections in your conf-file ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] X won't start with Radeon IGP 320M
Regarding: X won't start with Radeon IGP 320M Email: [EMAIL PROTECTED] XFree86 Version: XFree86 Version 4.2.1 / X Window System OS: FreeBSD 5.0-RELEASE Area: xf86cfg Server: not server related Video Card: pci bus 0x cardnum 0x00 function 0x00: vendor 0x1002 device 0xcab0 ATI Device unknown STATUS0x2230 COMMAND 0x0006 CLASS 0x06 0x00 0x00 REVISION 0x13 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00 BASE0 0xf408 addr 0xf400 MEM PREFETCHABLE BASE1 0xf088 addr 0xf080 MEM PREFETCHABLE BASE2 0xa011 addr 0xa010 I/O pci bus 0x cardnum 0x01 function 0x00: vendor 0x1002 device 0x700f ATI Device unknown STATUS0x0220 COMMAND 0x0007 CLASS 0x06 0x04 0x00 REVISION 0x01 HEADER0x01 LATENCY 0x63 PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01 SECLT 0x44 IOBASE0xb100 IOLIM 0xbfff SECSTATUS 0x0220 NOPREFETCH_MEMBASE 0xf050 MEMLIM 0xf05f PREFETCH_MEMBASE 0xf800 MEMLIM 0xfbff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x02 function 0x00: vendor 0x10b9 device 0x5237 ALI Device unknown CardVendor 0x10b9 card 0x5237 (ALI, Card unknown) STATUS0x0290 COMMAND 0x0017 CLASS 0x0c 0x03 0x10 REVISION 0x03 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00 BASE0 0xf040 addr 0xf040 MEM MAX_LAT 0x50 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b BYTE_00x1f BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x03 function 0x00: vendor 0x10b9 device 0x5457 ALI Device unknown CardVendor 0x1734 card 0x100a (Card unknown) STATUS0x0290 COMMAND 0x0003 CLASS 0x07 0x03 0x00 REVISION 0x00 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00 BASE0 0xf0401000 addr 0xf0401000 MEM BASE1 0x8401 addr 0x8400 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b BYTE_00xc0220001 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x04 function 0x00: vendor 0x10b9 device 0x5229 ALI M5229 TXpro CardVendor 0x10b9 card 0x5229 (ALI, Card unknown) STATUS0x0290 COMMAND 0x0005 CLASS 0x01 0x01 0xfa REVISION 0xc4 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00 BASE4 0xa001 addr 0xa000 I/O MAX_LAT 0x04 MIN_GNT 0x02 INT_PIN 0x01 INT_LINE 0x00 BYTE_00x4a00 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x06 function 0x00: vendor 0x10b9 device 0x7101 ALI Device unknown CardVendor 0x10b9 card 0x7101 (ALI, Card unknown) STATUS0x0200 COMMAND 0x CLASS 0x06 0x80 0x00 REVISION 0x00 BYTE_00x84000 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x00: vendor 0x10b9 device 0x1533 ALI M1533 Aladdin IV CardVendor 0x10b9 card 0x1533 (ALI, Card unknown) STATUS0x0210 COMMAND 0x000f CLASS 0x06 0x01 0x00 REVISION 0x00 BYTE_00xea0bd301 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x08 function 0x00: vendor 0x10b9 device 0x5451 ALI Device unknown CardVendor 0x1734 card 0x100a (Card unknown) STATUS0xc290 COMMAND 0x0003 CLASS 0x04 0x01 0x00 REVISION 0x02 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00 BASE0 0x8801 addr 0x8800 I/O BASE1 0xf0402000 addr 0xf0402000 MEM MAX_LAT 0x18 MIN_GNT 0x02 INT_PIN 0x01 INT_LINE 0x0b pci bus 0x cardnum 0x09 function 0x00: vendor 0x10ec device 0x8139 Realtek RTL8139 10/100 Ethernet CardVendor 0x1734 card 0x100a (Card unknown) STATUS0x0290 COMMAND 0x0007 CLASS 0x02 0x00 0x00 REVISION 0x10 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00 BASE0 0x8c01 addr 0x8c00 I/O BASE1 0xf0406800 addr 0xf0406800 MEM MAX_LAT 0x40 MIN_GNT 0x20 INT_PIN 0x01 INT_LINE 0x0b pci bus 0x cardnum 0x0a function 0x00: vendor 0x1106 device 0x3044 VIA Device unknown CardVendor 0x1106 card 0x3044 (VIA, Card unknown) STATUS0x0210 COMMAND 0x0013 CLASS 0x0c 0x00 0x10 REVISION 0x46 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x10 BASE0 0xf0406000 addr 0xf0406000 MEM BASE1 0x8081 addr 0x8080 I/O MAX_LAT 0x20 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x05 pci bus 0x cardnum 0x0b function 0x00: vendor 0x1524 device 0x1420 Device unknown STATUS0x0210 COMMAND 0x0007 CLASS 0x06 0x07 0x00 REVISION 0x01 BIST 0x00 HEADER 0x82 LATENCY 0x40 CACHE 0x10 BASE0 0x8800 addr 0x8800 MEM BASE1 0x02a0 addr 0x02a0 MEM BASE2 0x20020200 addr 0x20020200 MEM BASE3 0xf000 addr 0xf000 MEM BASE5 0xf000 addr 0xf000 MEM MAX_LAT 0x04 MIN_GNT 0x40 INT_PIN 0x01 INT_LINE 0x0b BYTE_00x100a1734 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x0b function 0x01: vendor 0x1524
[XFree86] xfree, pci-domains and i.e. SPARC
Hi. In ROCK Linux we use the David S. Miller pci-domain patch (which only converts a few drivers ...) for SPARC, like Debian does .. Is there interest to merge s.th. like this into the normal XFree tree? Or is a cleaner solution preferred? I would be willing to modify the code in whatever way acceptable for the XFree team - or even implement a cleaner solution if there is a reason to do so. Sincerely - René -- René Rebe - Europe/Germany/Berlin e-mail: [EMAIL PROTECTED], [EMAIL PROTECTED] web: www.rocklinux.org, drocklinux.dyndns.org/rene/ Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] bug: euro symbol doesn't work in xfree86 4.2.99
euro symbol ( defined with EuroSign ) doesn't work anymore in xfree86 4.2.99, I get the old key instead. This was reported by several people using redhat beta 8.1 here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82642 how to replicate: setxkbmap fr press right alt + e, euro key should be displayed, but 'e' is instead. This works fine in xfree 4.2.1 Thanks! -- Soluţii informatice bazate pe Linux / Linux-based IT solutions www.galuna.ro ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] bug: euro symbol doesn't work in xfree86 4.2.99
Am Mon, 2003-01-27 um 13.52 schrieb Marius Andreiana: euro symbol ( defined with EuroSign ) doesn't work anymore in xfree86 4.2.99, I get the old key instead. Working fine here... But Xvideo is still not working with my Radeon 8500 (hint hint ;)). -- Christophe Saout [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xfree, pci-domains and i.e. SPARC
On Mon, 27 Jan 2003, Rene Rebe wrote: In ROCK Linux we use the David S. Miller pci-domain patch (which only converts a few drivers ...) for SPARC, like Debian does .. Is there interest to merge s.th. like this into the normal XFree tree? Or is a cleaner solution preferred? I would be willing to modify the code in whatever way acceptable for the XFree team - or even implement a cleaner solution if there is a reason to do so. That's already been done. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Touch Screen support
Hi I was hired to make a informatic solution with touch screen computers. The question I have is what's the state of X11's touch screen support, I really want to make the application with Linux. Another more general question I have is that I have to connect PDAs to a desktop computer, I want the PDAs to run Linux too. Does anyone knows how I could achieve this? Thanks for any information you might give me. Pablo. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] help
Hello, You are more likely to get help if you also include a description of what's wrong. And what distro and version of Linux and Xfree you are using just for clarity's sake. Maybe what kind of hardware too. :) (For example, your video card could be considered germane.) Everything was looking good (to me at least) until here. Maybe you clock settings. Or your sync settings. Perhaps these are being read automatically and that's not working properly. (==) NV(0): Using gamma correction (1.0, 1.0, 1.0) (II) NV(0): Monitor0: Using hsync range of 30.00-86.00 kHz (II) NV(0): Monitor0: Using vrefresh range of 50.00-160.00 Hz (II) NV(0): Clock range: 12.00 to 350.00 MHz (WW) (1400x1050,Monitor0) mode clock 151MHz exceeds DDC maximum 150MHz (WW) (1400x1050,Monitor0) mode clock 162MHz exceeds DDC maximum 150MHz (II) NV(0): Not using mode 1400x1050 (hsync out of range) (II) NV(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan) (II) NV(0): Not using default mode 512x384 (bad mode clock/interlace/doublescan) (II) NV(0): Not using default mode 1280x1024 (hsync out of range) (II) NV(0): Not using default mode 640x512 (hsync out of range) (WW) (1600x1200,Monitor0) mode clock 162MHz exceeds DDC maximum 150MHz (WW) (1600x1200,Monitor0) mode clock 175.5MHz exceeds DDC maximum 150MHz (II) NV(0): Not using default mode 1600x1200 (hsync out of range) (II) NV(0): Not using default mode 800x600 (hsync out of range) (II) NV(0): Not using default mode 1600x1200 (hsync out of range) (II) NV(0): Not using default mode 800x600 (hsync out of range) (II) NV(0): Not using default mode 1600x1200 (hsync out of range) (II) NV(0): Not using default mode 800x600 (hsync out of range) (WW) (1792x1344,Monitor0) mode clock 204.8MHz exceeds DDC maximum 150MHz (II) NV(0): Not using default mode 1792x1344 (hsync out of range) (II) NV(0): Not using default mode 896x672 (hsync out of range) (WW) (1856x1392,Monitor0) mode clock 218.3MHz exceeds DDC maximum 150MHz (II) NV(0): Not using default mode 1856x1392 (hsync out of range) (II) NV(0): Not using default mode 928x696 (hsync out of range) (II) NV(0): Not using default mode 1920x1440 (hsync out of range) (II) NV(0): Not using default mode 960x720 (hsync out of range) (II) NV(0): Not using default mode 1920x1440 (hsync out of range) (II) NV(0): Not using default mode 960x720 (hsync out of range) (II) NV(0): Not using default mode 700x525 (hsync out of range) (II) NV(0): Not using default mode 1920x1200 (hsync out of range) (II) NV(0): Not using default mode 960x600 (hsync out of range) [...] Could not init font path element unix/:7100, removing from list! Fatal server error: could not open default font 'fixed' I've seen this in quite a few of these messages in Red Hat XFree logs (might even be specific to Nvidia drivers), there -may- be a FAQ about it on the XFree86 website. (http://www.xfree86.org/support.html) Unfortunately I don't know what the error message signifies, but it's a good place to start looking. (could not open default font 'fixed', maybe add a comma and Red Hat 8.0 or whatever your version is.) You can use Google to search the site, just go to the Advanced Search Options and set the Domain Option (in the first block of options towards the bottom) to only search http://www.xfree86.org/. Also, if you're not already subscribed to the Xfree mailing list you may want to as that is where most of the help actually takes place. (http://www.xfree86.org/mailman/listinfo) Good luck, .cyn. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] RH 7.3 Help!!
Hello, I am attempting to run X on my RH 7.3 installation with no luck. What is strange is that the same hardware ran X under 7.2 flawlessly! Also, I used the graphical install and went through the X setup with no errors. I have tried everything I know even copying the old XF86Config from the 7.2 installation with no success. I am running an old system (PII 166) with an S3 video card. Any assistance would be greatly appreciated. Sincerely, Wade Schofield XFree86.0.log: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 20 20:34:36 2003 (==) Using config file: /etc/X11/XF86Config Parse warning on line 102 of section Keyboard in file /etc/X11/XF86Config Ignoring obsolete keyword LeftAlt. Parse error on line 102 of section Keyboard in file /etc/X11/XF86Config Meta is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] xf86 4.2.0 problem
I am using a linux-from-scratch system, I downloaded all the sources for xf86 4.2.0 and installed them correctly with symlinks and with correct entries in ld.conf etc. I configured the x system using xf86config, ( i have a nvidia riva tnt2 card and microsoft usb optical mouse ) but when i give the command startx, i get the following errors ( i have also attached the log file ): (WW) NV (0) : Failed to setup write combining range ( 0xe400, 0x200) When i give the command xf86cfg : only a blank black screen appears. when i give the command XFree86 : A hatched grey screen appears with a ( crossed ) mouse cursor that does not move I am sure there is no mistake with my hardware. I think there must be incompatiablity problems with my nvidia riva tnt2 card and xf86. I am also confused with the different results that i get from these different commands Can anyone please help me ?? My xfree86 Log contents :: XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19-16mdk i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 27 12:09:48 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device RIVA TNT2 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc101 (**) XKB: model: pc101 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card 1019,0a48 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,244e card , rev 12 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 12 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 1019,0a48 rev 12 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2442 card 1019,0a48 rev 12 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 1019,0a48 rev 12 class 0c,05,00 hdr 00 (II) PCI: 00:1f:4: chip 8086,2444 card 1019,0a48 rev 12 class 0c,03,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2445 card 1019,0a48 rev 12 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 10de,002d card 1043,0201 rev 15 class 03,00,00 hdr 00 (II) PCI: 02:01:0: chip 10ec,8139 card 11f6,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II)
Re: [XFree86] RH 7.3 Help!!
Pre RH8, I ALWAYS installed without Xsetup, then used Xconfigurator, custom, 800x600 60Hz to start with, and work up from there. I NEVER had trouble, even with the several TFT's I set up. Shane WADE SCHOFIELD wrote: Hello, I am attempting to run X on my RH 7.3 installation with no luck. What is strange is that the same hardware ran X under 7.2 flawlessly! Also, I used the graphical install and went through the X setup with no errors. I have tried everything I know even copying the old XF86Config from the 7.2 installation with no success. I am running an old system (PII 166) with an S3 video card. Any assistance would be greatly appreciated. Sincerely, Wade Schofield XFree86.0.log: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 20 20:34:36 2003 (==) Using config file: /etc/X11/XF86Config Parse warning on line 102 of section Keyboard in file /etc/X11/XF86Config Ignoring obsolete keyword LeftAlt. Parse error on line 102 of section Keyboard in file /etc/X11/XF86Config Meta is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Bus error after installing XFree86 4.2.99.3
I have installed 4.2.99.3 from binaries using Xinstall.sh on Redhat 7.3. When I XFree86 or XFree86 -configure from bash, I get a Bus error. Any suggestions?... I'll happily provide further details of my system if nec. Tks, Matthew Weymar ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] help!!!
Bruce, We seem to be getting more and more errors with no information in them. How are we supposed to help you if you don't give us any information? For a start, what OS is this? What cpu? What distribution? What do the logs say? What are the permissions on /dev/io? What version of X do you have? We aren't physic. If this is a bsd machine, then you have your security settings too high. If not, then perhaps your permissions are wrong. I can't tell with the little information you have given us. Sincerely, JohnFlux On Mon, Jan 27, 2003 at 05:56:47PM +0200, Bruce wrote: I can't run my X.What can I do? I'm install the X,and when I run xf86cfg, i'm get a message: Fatal server error: xfEnableIO: Failed to open /dev/io for extended I/O Please HELP ME!!! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Antialiasing and dual monitor with ATI Radeon 9000
Rainer Blum wrote: Hi, my first question is about the antialiasing feature of the ATI Radeon 9000 (called smoothvision): How can I use/activate this feature under Linux? AFIAK, not with the open-source drivers. I don't believe that ATI has ever released documentation for this feature. I'm fairly sure that ATI's close-source, binary-only driver support this feature. I haven't ever installed those drivers, so I don't know. You'll have to ask them how to make it work. :) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree86 on RH 8.0, DELL inspiron 2650
On Sunday, 26 Jan 2003, Affan Ahmed wrote: its actually a Geforce2 Go. I cant seem to get any of the Nvidia drivers to work and bring it upto 1024*768. Please help,Rem i installed RH 8.0 so i cant use the Xconfigurator...ug. As I understand it, on Red Hat 8.0, the `redhat-config-xfree86' utility replaces `XConfigurator'. Can you get the NVIDIA binary drivers to work at all? According to the latest `NVIDIA Accelerated Linux Driver Set README Installation Guide', the GeForce2 Go *should* be supported... You can get XFree86 to start, can't you? Can you send us the XFree86 log? (usually found in /var/log/XFree86.0.log) Jimmy. Thanx Affan --- James Boyden [EMAIL PROTECTED] wrote: On Saturday, 25 Jan 2003, Affan Ahmed wrote: hello, I have tried to get the Xfree86 to correctly detect my TFT screen and configure it to the optimum resolution. But that doesnt happen with RH 8.0 where i cant run XConfigurator. I have run the redhat-config-xfree86 but the problem is that it cannot recognize my monitor (btw what should i go for my TFT screen) and neither does it detect my Nvidia GeForce Go 100 card. I can't find any hint of an NVIDIA card called GeForce Go. Are you sure that's what it's called? Jimmy. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Fw: Kaking on yacc file ... (./lib/Xft/xftgram.y)
In fact, if I invoke the following line in the root directory of the build (./xc/), I see that every instance of a rule immediately preceding a 'number' rule in a yacc/bison file does *not* end with a semicolon and gives me an error. Again, could someone take a look at this? (or redirect me to those who might be interested?) - Jamie - Original Message - After opening the 4.2.0 tar balls and applying the 4.2.0-4.2.1 patch, I find I'm getting a compling error when bison tries to process the file ./lib/Xft/xftgram.y. The CVS/RCS ID for the file is: $XFree86: xc/lib/Xft/xftgram.y,v 1.5 2001/05/16 10:32:54 keithp Exp $ The error I get is this: bison -y -d xftgram.y xftgram.y:168.8: parse error, unexpected :, expecting ; or | xftgram.y:169.3-6: $$ of `matrix' has no declared type make[3]: *** [xftgram.c] Error 1 And it appears that the file really is missing a semicolon at the end of the matrix rule (~line 167). I've added one to my copy, and am trying it as I type. Could someone verify this? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Fw: Kaking on yacc file ... (./lib/Xft/xftgram.y)
The "following line" missing from the text below is: egrep "^number" -B 2 -n `find ./xc/ -name "*.y" -type f` Jamie Risk [EMAIL PROTECTED] wrote: In fact, if I invoke the following line in the root directory of the build(./xc/), I see that every instance of a rule immediately preceding a'number' rule in a yacc/bison file does *not* end with a semicolon and givesme an error.Again, could someone take a look at this? (or redirect me to those who mightbe interested?)- Jamie- Original Message - After opening the 4.2.0 tar balls and applying the 4.2.0-4.2.1 patch, Ifind I'm getting a compling error when bison tries to process the file "./lib/Xft/xftgram.y". The CVS/RCS ID for the file is: $XFree86: xc/lib/Xft/xftgram.y,v 1.5 2001/05/16 10:32:54 keithp Exp $ The error I get is this: bison -y -d xftgram.y xftgram.y:168.8: parse error, unexpected ":", expecting ";" or "|" xftgram.y:169.3-6: $$ of `matrix' has no declared type make[3]: *** [xftgram.c] Error 1 And it appears that the file really is missing a semicolon at the end ofthe "matrix" rule (~line 167). I've added one to my copy, and am trying it asI type. Could someone verify this?___XFree86 mailing list[EMAIL PROTECTED]http://XFree86.Org/mailman/listinfo/xfree86Post your free ad now! Yahoo! Canada Personals
RE: [XFree86] Problem with Red Hat Linux
Title: RE: [XFree86] Problem with Red Hat Linux (II) PCI: 00:02:0: chip 8086,2562 card 1028,0126 rev 01 class 03,00,00 hdr 00 you are having an intel 846 G which is only well supported by latest XF86 beta. -Alex. PS: sorry for late reply, the yourvote.com server with pci database was offline for a while. -Original Message- From: Art Rathke [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 14:27 To: [EMAIL PROTECTED] Subject: [XFree86] Problem with Red Hat Linux I have just installed Red Hat Linux on a Dell GX260 desktop computer with the standard video adapter which is integrated on the motherboard. I have attached a log file with the errors that have occurred. Thanks, Art Rathke [EMAIL PROTECTED] 586-977-1034
[XFree86] No config file?
Hi Common problem, I can't start my Xs Let's start from the beggining: # cd /usr/ports/x11/XFree86-4 # make install clean #cd /usr/ports/x11/kde3 # make install clean Once I have done it I type # XFree86 -configure #XFree86 -xf86config /root/XFree86configure.new Test is done, and the grey screen with moving coursor appears. So, I am going to edit my config vi /root/XF86Config I added some lines: In section MONITOR HorizSync 30-64 VertRefresh 50-100 and SECTION SCREEN DefaultDepth 24 SubSection Display Depth 24 Modes 1024x765 Besides I typed in a prompt: echo exec startkde ~/.xinitrc Then I rebooted and typed startx And server crashed, below there is my log: XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.7-STABLE i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 27 13:15:08 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] WHAT's UP Thx for eventually help - Wstaw swoje zdjcie do nowego Kontaktu! http://kontakt.wp.pl ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] No config file?
Ar an 27ú lá de mí 1, scríobh Marek Denis : (EE) Unable to locate/open config file [...] WHAT's UP Thx for eventually help As root; cp /root/XF86Config /etc/X11 and try again. -- I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet. -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] No config file?
On Monday, 27 Jan 2003, Marek Denis wrote: snip Once I have done it I type # XFree86 -configure #XFree86 -xf86config /root/XFree86configure.new Test is done, and the grey screen with moving coursor appears. So, I am going to edit my config vi /root/XF86Config I added some lines: snip Besides I typed in a prompt: echo exec startkde ~/.xinitrc Then I rebooted and typed startx And server crashed, below there is my log: snip (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 27 13:15:08 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found snip WHAT's UP Your XF86Config is still in /root/XFree86configure.new or /root/XF86Config, or whatever you ended up calling it. According to the manual page XF86Config-4(5x) on my system: ||XFree86 uses a configuration file called XF86Config for ||its initial setup. This configuration file is searched ||for in the following places when the server is started as ||a normal user: || ||/etc/X11/cmdline ||/usr/X11R6/etc/X11/cmdline ||/etc/X11/$XF86CONFIG ||/usr/X11R6/etc/X11/$XF86CONFIG ||/etc/X11/XF86Config-4 ||/etc/X11/XF86Config ||/etc/XF86Config ||/usr/X11R6/etc/X11/XF86Config.hostname ||/usr/X11R6/etc/X11/XF86Config-4 ||/usr/X11R6/etc/X11/XF86Config ||/usr/X11R6/lib/X11/XF86Config.hostname ||/usr/X11R6/lib/X11/XF86Config-4 ||/usr/X11R6/lib/X11/XF86Config || ||where cmdline is a relative path (with no .. compo ||nents) specified with the -xf86config command line option, ||$XF86CONFIG is the relative path (with no .. components) ||specified by that environment variable, and hostname is ||the machine's hostname as reported by gethostname(3). || ||When the X server is started by the root user, the con ||fig file search locations are as follows: || ||cmdline ||/etc/X11/cmdline ||/usr/X11R6/etc/X11/cmdline ||$XF86CONFIG ||/etc/X11/$XF86CONFIG ||/usr/X11R6/etc/X11/$XF86CONFIG ||$HOME/XF86Config ||/etc/X11/XF86Config-4 ||/etc/X11/XF86Config ||/etc/XF86Config ||/usr/X11R6/etc/X11/XF86Config.hostname ||/usr/X11R6/etc/X11/XF86Config-4 ||/usr/X11R6/etc/X11/XF86Config ||/usr/X11R6/lib/X11/XF86Config.hostname ||/usr/X11R6/lib/X11/XF86Config-4 ||/usr/X11R6/lib/X11/XF86Config Copy or move your XF86Config to the appropriate location. Jimmy ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
On Mon, Jan 27, 2003 at 12:39:49AM -0800, hy0 wrote: I did try with DRI disabled. In that case, X still starts up with a blank screen and a locked keyboard, but at least I can ssh in to the laptop and kill X and/or shutdown the machine. The text display is never recovered. I have attached the log of X running with DRI disabled. Can you further narrow it down by disabling XAA and hardware cursor (Option NoAccel, Option SWcursor)? With NoAccel and SWcursor I still get the blank screen and locked keyboard. Strangely, I also get a bunch of Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! messages. With NoAccel only (i.e. NO SWcursor) I don't have these messages, but I do get the same symptoms: blank screen and locked keyboard. I've attached both log files. This is quite a big breakage on my configuration. As I said before, 4.2.99.3 works perfectly with EXACTLY the same parameters. What else can I try? Thanks for your help, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.4 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 20 January 2003 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.7-10custom i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 27 20:37:46 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout DefaultLayout (**) |--Screen Default Screen (0) (**) | |--Monitor Clevo 15in 1400x1050 (**) | |--Device ATI Radeon 7500 Mobility (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Synaptics (GPM) (**) |--Input Device USB Mouse (**) FontPath set to /usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,/usr/lib/X11/fonts/TrueType,/usr/lib/X11/fonts/TTF (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.99.4, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card 1558,5600 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,2482 card 1558,5600 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2484 card 1558,5600 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 42 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 1558,5600 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,2483 card 1558,5600 rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 1558,5600 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:1f:6: chip 8086,2486 card 1558,5600 rev 02 class 07,03,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4c57 card 1558,5600 rev 00 class 03,00,00 hdr 00 (II) PCI: 02:04:0: chip 104c,8023 card 1558,5600 rev 00 class 0c,00,10 hdr 00 (II) PCI: 02:06:0: chip 10ec,8139 card 1558,5600 rev 10 class 02,00,00 hdr 00 (II) PCI: 02:07:0: chip 104c,ac50 card
[XFree86] Bug reporting suggestion
Hi, Many people are reporting problems and bugs without giving enough information. Personally I try to take the view the user is always right, and so this is what I propose.. :) *) I (or someone else) writes a quick program (or extension to bug or reportbug or any other bug reporting program) that the user runs. *) Running this program is suggested when the server crashes. *) The program notes down all the relevant details. X server, distro, cpu, graphics card, copy of log, copy of config and credit card number. *) The program emails this to a server. It shows it first to the user, with an option to save it to file instead/as well as so that those without internet connection can put it on a floppy disk and email it from elsewhere. *) The problem is compared against a crude knowledge base system (fancy name for a database). *) Solutions are returned to the user automatically. *) The user is encouraged to reply, successful or not. *) If successful, then the database notes it. *) If not, the whole lot gets sent to a mailing list (possibly this one). *) When it is solved, the knowledge based system is updated. I've been meaning to do something like this, but more generic. However the X mailing list tends to get a lot more repetive requests than most, and also has emails with the least amount of information, so seems the most needy IMHO. Thoughts? If I hear no comments then I'll get depressed and kill myself. :) JohnFlux -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] help!!!
I did not realize that we had a few virtual people on this list!! ;^) Lionel --- John Tapsell [EMAIL PROTECTED] wrote: snip We aren't physic. snip __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 v4.2.99+ / Radeon 9000 configuration issues
Further development... After disconnection of the S-Video cable from my TV followed by a reboot I could start XFree86 with output to my monitor. As soon as I connect the S-Video cable again and reboot I can't start XFree86. Is XFree86 incompatible with TV-out on Radeon 9000? Fredrik Hi, I have recently bought a Sapphire Radeon 9000 128 MB Atlantis video card which is based on the rv250 chip. In XP this card works wonderfully with ATI's Catalyst drivers. Under RedHat 8.0 on a PIII/900 I haven't got it to work at all except with the VESA driver, which naturally doesn't perform good enough. I've tried with both XFree86 v4.2.99.3 och v4.2.99.4 without any luck. After a fresh X -configure run, X -xf86config /root/XF86config.new exits with the following message: (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) RADEON(0): No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. The output of lspci -v and the XFree86 log file is attached. Does anyone know if it is possible to get the card working under XFree v4.2.99+ and if so how? Regards, Fredrik ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Is this working?
Hello, I am attempting to run X on my RH 7.3 installation with no luck. What is strange is that the same hardware ran X under 7.2 flawlessly! Also, I used the graphical install and went through the X setup with no errors. I have tried everything I know even copying the old XF86Config from the 7.2 installation with no success. I am running an old system (PII 166) with an S3 video card. Any assistance would be greatly appreciated. Sincerely, Wade Schofield XFree86.0.log: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Mon Jan 20 20:34:36 2003 (==) Using config file: /etc/X11/XF86Config Parse warning on line 102 of section Keyboard in file /etc/X11/XF86Config Ignoring obsolete keyword LeftAlt. Parse error on line 102 of section Keyboard in file /etc/X11/XF86Config Meta is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 -Original Message- From: Simon Westerby [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 1:32 PM To: [EMAIL PROTECTED] Subject: Re: [XFree86] Is this working? You need 4.2.99.4 as the INtel 845 chipset is not supported in 4.2.1 WADE SCHOFIELD wrote: I've sent in a couple of help requests and haven't received a reply or seen my message so up in list. Would someone please reply to this so I know it's working! Thanks, ws -Original Message- From: vishnu devineni [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 2:25 AM To: [EMAIL PROTECTED] Subject: [XFree86] startx not running hi my computer has intel D845GLLY motherboard with built in graphics card. log file is attached Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] SuperProbe
I installed X11R6 as part ofa FreeBSD installation, however I can't find the program SuperProbe anywhere in it. I don't know anything about this video card, and I can't do the rest of the configuration without it. Any idea where I can get SuperProbe on it's own?
Re: [XFree86] SuperProbe
On Mon, 27 Jan 2003, Casey Rockwell wrote: I installed X11R6 as part of a FreeBSD installation, however I can't find the program SuperProbe anywhere in it. I don't know anything about this video card, and I can't do the rest of the configuration without it. Any idea where I can get SuperProbe on it's own? SuperProbe no longer exists. Your best bet is to `XFree86 -configure` to see if the adapter is supported. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Bug reporting suggestion
Okay I'll have it done by the weekend. If it is of decent quality, could it be included in the distribution, with a bit of text suggesting to run it appended to the X crash output? Otherwise it is kinda pointless :) We'll have a play anyway. I have an example tommorrow morning, and it's getting late, so I won't be able to do it till friday. Kick me if I haven't submitted something by the monday morning :) ooh, as an after thought... I suppose this had better be done in C or C++? I can code in just about any language, but best not increase the dependancies of X, right? JohnFlux On Mon, Jan 27, 2003 at 04:32:35PM -0500, Matthew Weymar wrote: As a guilty party, I say, Brilliant idea! Lest the suggestion fall by the wayside, why not start with the more modest goal of automatically gathering all the relevant details for submission to this list? This would seem to be easy enough, and quite a valuable time and frustration saver. (C.f. the JDEE-Help-Submit Problem Report under Requesting Help http://jdee.sunsite.dk/rootpage.html#RequestingHelp) The db interaction would seem to be harder, and to require resources that may or may not be immediately available. Matthew PS - It's important that the database accept AmEx as well as Visa MC. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
On Mon, Jan 27, 2003 at 09:30:09PM +0100, Michel Dänzer wrote: On Mon, 2003-01-27 at 20:48, Charl P. Botha wrote: With NoAccel only (i.e. NO SWcursor) I don't have these messages, but I do get the same symptoms: blank screen and locked keyboard. BTW, how do you verify that the keyboard is 'locked'? None of the caps-lock, scroll-lock or num-lock keys work, judging by their accompanying leds. -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Caps/Scroll/Num Lock
I realize this is an idiot question but: How does one default NumLock to on? Is this a job for X, the WM, or the desktop? I always thought this was done with xset but that does not seem to do anything. Thanks, -Don ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Is this working?
It might be one of the Unsupported Chipsets in 4.2.0 / .1, have you tried the older 3.3.6 Server ? S3 3.3.6: Support (accelerated) for the S3 911, 924, 801, 805, 928, 864, 868, 964, 968, Trio32, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the XF86_S3 server and the XF86_SVGA server with the s3_svga driver. Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+ is provided by the XF86_S3V server. Support (accelerated) for the ViRGE chipsets, as well as the Trio3D and Trio3D/2X, is provided by the XF86_SVGA server with the s3v driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, and Savage2000, is provided by the XF86_SVGA server with the s3_savage driver on some OSes (Linux, *BSD). 4.2.1: Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32, Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the "s3" driver (however, only models using the IBM RGB 524, Texas Instruments 3025, or an internal TrioDAC RAMDAC chip are supported). Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the "s3virge" driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, Savage2000, and SuperSavage, is provided by the "savage" driver. Support for the other S3 chipsets has not yet been ported. Summary: All hardware supported in 3.3.6 is also supported in 4.2.1 except for the 911, 924, 801, 805, 928, 864, and 868, and versions of the 964 and 968 that do not use the RAMDAC chips listed above. The SuperSavage chipset is supported only in 4.2.1. WADE SCHOFIELD wrote: Hello, I am attempting to run X on my RH 7.3 installation with no luck. What is strange is that the same hardware ran X under 7.2 flawlessly! Also, I used the graphical install and went through the X setup with no errors. I have tried everything I know even copying the old XF86Config from the 7.2 installation with no success. I am running an old system (PII 166) with an S3 video card. Any assistance would be greatly appreciated. Sincerely, Wade Schofield XFree86.0.log: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Jan 20 20:34:36 2003 (==) Using config file: "/etc/X11/XF86Config" Parse warning on line 102 of section Keyboard in file /etc/X11/XF86Config Ignoring obsolete keyword "LeftAlt". Parse error on line 102 of section Keyboard in file /etc/X11/XF86Config "Meta" is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to [EMAIL PROTECTED]. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 -Original Message- From: Simon Westerby [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 1:32 PM To: [EMAIL PROTECTED] Subject: Re: [XFree86] Is this working? You need 4.2.99.4 as the INtel 845 chipset is not supported in 4.2.1 WADE SCHOFIELD wrote: I've sent in a couple of help requests and haven't received a reply or seen my message so up in list. Would someone please reply to this so I know it's working! Thanks, ws -Original Message- From: vishnu devineni [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 2:25 AM To: [EMAIL PROTECTED] Subject: [XFree86] startx not running hi my computer has intel D845GLLY motherboard with built in graphics card. log file is attached Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing
Re: [XFree86] Caps/Scroll/Num Lock
You wouldn't believe how often this comes up. http://hints.linuxfromscratch.org/hints/numlock.txt DEVELOPERS - PLEASE FIX THIS! (Having shouted, they probably already have.. and boy will I be embarrased) JohnFlux On Mon, Jan 27, 2003 at 04:52:16PM -0500, Don wrote: I realize this is an idiot question but: How does one default NumLock to on? Is this a job for X, the WM, or the desktop? I always thought this was done with xset but that does not seem to do anything. Thanks, -Don ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 -- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] CVS tree: Xserver deref null pointer in Mesa cleanup of dropped client connectio
XFree86 Bug/Test Report Form Please fill in as many of the fields a possible, and return this form to [EMAIL PROTECTED] Replace the comments in [] with your own text. VERSION: CVS tree on 1/21/2003 XF86_VERSION 4.2.99.4 VIDEO DRIVER: radeon mobile 9600 OPERATING SYSTEM: Linux VIDEO CARD: MODEL: Radeon Mobility 9000 GRAPHICS CHIPSET: ATI Radeon R250 RAMDAC: CLOCKCHIP: VIDEO MEMORY: BUS TYPE: PCI REPORT: I have an OpenGL program that crashes after opening the GL context (I believe) - but then dies. The Xserver tries to cleanup after this mishap and free memory. In the Mesa server code, xc/extras/Mesa/src/tnl, a context structure element freed_immesiate is used to cache the last freed memory - for possible reuse. Clearly a performance gain. The problem: If no memory has been freed - because none has been allocated yet, _tnl_DestroyContext (t_context.c:146) invokes _tnl_free_immediate with a second argument the pointer to the freed_immediate memory. This will be 0 if no memory has been freed - or if t_imm_alloc.c has given the memory to someone else already. _tnl_free_immediate (t_imm_alloc.c:129) places the second argument into a variable IM. Almost immediately at line 130 - IM is derefenced with ASSERT(IM-ref_count == 0); Oops Two possible fixes: a) _tnl_free_immediate should test for IM being 0, or _tnl_DestroyContext should not call _tnl_free_immediate if freed_immediate is 0. I chose the later Seems that the DRI development CVS tree suffers from the same. Ezra --- xc/extras/Mesa/src/tnl/t_context.c.ezra 2003-01-27 17:22:23.0 -0500 +++ xc/extras/Mesa/src/tnl/t_context.c 2003-01-27 17:11:58.0 -0500 @@ -144,7 +144,8 @@ _tnl_array_destroy( ctx ); _tnl_imm_destroy( ctx ); _tnl_destroy_pipeline( ctx ); - _tnl_free_immediate( ctx, tnl-freed_immediate ); + if (tnl-freed_immediate) + _tnl_free_immediate( ctx, tnl-freed_immediate ); FREE(tnl); ctx-swtnl_context = 0; $XFree86: xc/programs/Xserver/hw/xfree86/doc/BugReport.cpp,v 1.1 2001/01/15 23:00:01 dawes Exp $ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] How to get snow-free 2048x1536x24 display?
Hi, I am the fortunate owner of a Mitsubishi Diamond Pro 2070sb monitor. Unfortunately, when I ask xfree86 run the monitor at resolutions above 1600x1200x24 I get digital snow all over the screen during graphic updates. What do I have to do to get rid of the snow? ATI Radeon 7500 64Mb, Xfree86 4.2.99.5 Thanks George ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Bus error after installing XFree86 4.2.99.3
Matthew Weymar wrote: I have installed 4.2.99.3 from binaries using Xinstall.sh on Redhat 7.3. When I XFree86 or XFree86 -configure from bash, I get a Bus error. Any suggestions?... I'll happily provide further details of my system if nec. Tks, Matthew Weymar Does the following help at all?... XFree86 Bug/Test Report Form Please fill in as many of the fields a possible, and return this form to [EMAIL PROTECTED] Replace the comments in [] with your own text. VERSION: 4.2.99.3 VIDEO DRIVER: Combination of NVIDIA_kernel-1.0-3123.rh73smp_2.4.18_10.athlon.rpm and NVIDIA_GLX-1.0-3123.i386.rpm to produce 'nvidia' OPERATING SYSTEM: Linux RH 7.3 VIDEO CARD: NVIDIA GeForce4 Ti 4600 MODEL: GRAPHICS CHIPSET: GeForce4 Ti 4600 RAMDAC: Integrated RAMDAC CLOCKCHIP: VIDEO MEMORY: 128MB BUS TYPE: AGP 4X REPORT: Per above: When I XFree86 or XFree86 -configure from bash, I get a Bus error. Tks again, Matthew ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Touch Screen support
Matthew Allum wrote: on Mon, Jan 27, 2003 at 03:32:54PM +0100, Pablo Fern?ndez wrote: Another more general question I have is that I have to connect PDAs to a desktop computer, I want the PDAs to run Linux too. Does anyone knows how I could achieve this? Sharp Zaurus or COmpaq Ipaq ? Have you seen http://handhelds.org ? -- Matthew ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] urgent assistant
DEAR SIR/MADAM, Compliment of the day, I am JAMES KYARI, The son of late General Kubwa Kyari of the Democratic Republic of Congo. My father was a General in the Congolese Army. In his position (My father) with the office of the presidentcy during the regime of Laurent Kabila, he was assigned on a secret mission to source and acquire arms internationally in order to strengthen the Government forces against the rebels, which already had the support of Rwandan and Uganda Army. Meanwhile, he was still negotiating for the purchase of the arms, he received on the 16th January 2001 news of the assassination of Laurent Kabila which force him to call off the assignment and deposited the sum of US$12.5M, Packed in a diplomatic case in a private security company in the Hague, the Netherlands, though he registered the content as precious stones while the real content is (US12.5M) meant for the purchase of arms for the Congolese Army. My father went home for the funeral of the late president, but on his arrival he was arrested, detained and tortured, unfortunately my father suffer cardiac arrest and died on the 17th of March 2001. However, on one of our numerous visits, my mother and I paid him while in prison, my father was able to reveal this secret to me and advice that i should proceed to the Netherlands to claim the money, he handed me all the relevant documents that will enable me claim the box from the security company.Already, I have made my first visit to the security company and the availability of this box have been confirmed. On our arrival in the Netherlands few months ago, we sought for political asylum; which was granted. My mother and I are making frantic effort on the best way to handle this money. We sought advice from an attorney who advised that we must seek for a trustworthy foreign business partner whom this money could be transferred into his/her (companys) account. This we view as the best option because our refugee status dose not permit us to operate a bank account, hence we seek your assistance and hope you could be trusted. I got your contact from the commercial section of the congolese embassy in Belgium. Meanwhile, I sincerely ask for your assistance to get this money through your account, Your share for assisting us will be 25% of the total sum, 5% will be use for upsetting all the expenses incurred in the course of concluding this venture and the remaining 70% that will be for me and my family. Also you stand to gain from any investment you might introduce us into after the conclusion of the transfer. Please keep this confidential until we finalize and get this money into your account for security reasons. This is my e-mail address you can reach me:([EMAIL PROTECTED]) Thanks and GOD bless MR, JAMES KYARI. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Caps/Scroll/Num Lock
http://hints.linuxfromscratch.org/hints/numlock.txt Ok I have to apologize. I hit this page via a simple google search, read the first section, and thought it was a linux page. Thsi time I read the whole thing and lo and behold, there was my answer. Thanks for the link. -Don ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] One question about the XFree86 software.....
To whomever read this, Hi! I have one question. Well, two questions now. 1) When will the next version of XFree86 be released? I noticed it is already one year and there's no newer version yet. 2) Is there any progress on the video chipset, SIS 650 that will be included in the later release if it won't be in the next release?? Thanks, Scott F. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: Have you dropped radeon 7200 support?
On Sat, 25 Jan 2003, hy0 wrote: Thanks for the explanations, now I can see what this is about. However I still have some concerns about this code. Indeed, Radeon chips do have 0x1c0 (misnamed MPP_TB_CONFIG) as SEPROM_CNTL register. Modifying/restoring its SCK_PRESCALE field is unlikely to be the cause of this screen corruption problem. In the current code path, even for a properly POSTed card, MEM_CNTL is set to zero and then restored back. This step may cause some side effect to the memory controller. Properly initializing MEM_CNTL/MEM_SIZE should take several steps (I may miss something): 1. wait for memory control idle (MC_STATUS). 2. configure each channel (MEM_CNTL). 3. reset memory (MEM_SDRAM_MOD_REG). 4. check if each channel works correctly. Simply setting MEM_CNTL to zero and then restoring it back may put memory controller in some bad state. To me, this only means more registers need to be saved, and later restored in a specific order. It should be possible to determine such a sequence from the BIOS init code. It would be for Mach64 and Rage128 variants, I know. But I don't happen to have a Radeon BIOS Kit at the moment. Asic initialization involves not only register writes with correct values, but also state waiting, delaying, resetting, etc. Yes, there are initialization tables in Radeon chips embedded in the BIOS images like in Mach64 and R128, but these tables only got standardized in the relative new versions of BIOS. This means using these tables will introduce compatibility problems with old chip/BIOS. While it's possible to resolve these compatibility problems, it will take a lot of work and tests, don't think it's an option for the upcoming v4.3. Anyway, back to this patch, why does it have to set MEM_CNTL to 0? If you simply comment off OUTREG(RADEON_MEM_CNTL, 0) in PreInt10Save, will the patch still work for your special cases? It's interesting how these special cases out-number the single more common case of not having to re-POST the adapter... I agree the re-POST bug could be quite common for secondary card, since BIOS code itself may not be well designed/tested to run under such conditions. Be that as it may, the attached should work as a temporary workaround. Looks like a good workaround, thanks. Hui Marc. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500 Mobility)
On Mon, Jan 27, 2003 at 09:30:09PM +0100, Michel Dänzer wrote: On Mon, 2003-01-27 at 20:48, Charl P. Botha wrote: With NoAccel only (i.e. NO SWcursor) I don't have these messages, but I do get the same symptoms: blank screen and locked keyboard. BTW, how do you verify that the keyboard is 'locked'? None of the caps-lock, scroll-lock or num-lock keys work, judging by their accompanying leds. This is getting weird, assuming ctrl-alt-bs won't let you quit X. Just checked recent changes, can't think of a reasonable explanation. One remote possibility is the SURFACE_CNTL change. In principle, this change shouldn't cause any problem. But I've seen some strange things with this register on other chips. Can you try this: move save-surface_cntl = 0; into #if X_BYTE_ORDER == X_BIG_ENDIAN pass and replace it with old save-surface_cntl = RADEON_SURF_TRANSLATION_DIS If still no luck, I'll try to reproduce this thing here. Hui -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
