[XFree86] (no subject)
Почему сегодня все больше и больше людей хотят знать свою родословную? Кого-то хочет иметь возможность поименно почтить в церкви своих предков или верит в родовую карму, другие надеются подтвердить семейные легенды или ищут дворянские (казаческие, купеческие) корни, третьих интересуют вопросы наследства и гражданства, но большинство обращается к памяти о предках просто из чувства долга и любопытства. Пройдет еще немного времени и Ваши дети уже не будут помнить, где родина Ваших бабушек и дедушек, родившихся до 1917 года, и тогда ГЕНЕАЛОГИЧЕСКОЕ ИССЛЕДОВАНИЕ станет практически невозможным из-за крайней скудости информации в документах советского периода. Начните восстановление своей РОДОСЛОВНОЙ пока не поздно! *** Хороший подарок для человека с семейными ценностями - диплом фамилии, содержащий исследование языкового происхождение фамилии. Даже если Ваша фамилия не относится к числу редких, Вы удивитесь тому, как язык смог сохранить о Вашем родоначальнике сведения, которые не запечатлели бы никакие документы. *** Мы можем оформить информацию о Вашем роде, семье и фамилии в виде: родословного древа, семейного альбома, фамильного диплома, семейной иконы и т.д. ТЕЛЕФОН ДЛЯ СВЯЗИ: (095) 509-52-16 E-mail: [EMAIL PROTECTED]
[XFree86] problem solved
I changed ati to vesa in the config file and all works well at high resolution - cheers, ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Compaq Proliant 1800t Laptop woes
I have tried every tweak I can think of and nothing works - I am running RedHat 9 kernel 2.4.20-6 and XFree86 Version 4.3.0 - Any help would be greatly appreciated!!! - thanks (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Here is the Error = ( Samsung LTN150U1-L01 Color, Single, TFT (EE) R128(0): No valid modes found (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Build Host: porky.devel.redhat.com here is my XF86Config file: Section Module # This loads the DBE extension module. Loaddbe # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection extmod Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Loadtype1 Loadfreetype # This loads the GLX module Load glx Load dri EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled #FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled #FontPath /usr/X11R6/lib/X11/fonts/Type1/ #FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ #FontPath /usr/X11R6/lib/X11/fonts/100dpi/ # The module search path. The default path is shown here. #ModulePath /usr/X11R6/lib/modules EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option NoTrapSignals # Uncomment this to disable the CrtlAltBS server abort sequence # This allows clients to receive this key event. #Option DontZap # Uncomment this to disable the CrtlAltKP_+/KP_- mode switching # sequences. This allows clients to receive these key events. #Option Dont Zoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. #Option DisableVidModeExtension # Uncomment this to enable the use of a non-local xvidtune client. #Option AllowNonLocalXvidtune # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. #Option DisableModInDev # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). #Option AllowNonLocalModInDev EndSection # ** # Input devices # ** # ** # Core keyboard's InputDevice section # ** Section InputDevice Identifier Keyboard1 Driver Keyboard # For most OSs the protocol can be omitted (it defaults to Standard). # When using XQUEUE (only for SVR3 and SVR4, but not Solaris), # uncomment the following line. #Option Protocol Xqueue Option AutoRepeat 500 30 # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) #Option Xleds 1 2 3 #Option LeftAlt Meta #Option RightAltModeShift # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: #Option XkbModelpc102 # If you have a US Microsoft Natural keyboard, you can use: #Option
RE: [Xpert]Geforce4 MX 440
Hmmm, my GeForce 4 MX 440 (VisionTek) works beautifully under 4.2.0 under Linux ... so unless there are real differences in the server code between FreeBSD and Linux, I would expect this to work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Vojkovich Sent: Tuesday, June 11, 2002 4:39 PM To: XFree86 mailing list Subject: Re: [Xpert]Geforce4 MX 440 On Tue, 11 Jun 2002, Stephen Wenzler wrote: does 4.2.0. supports Geforce4 MX 440 video card? GeForce4 cards aren't likely to work properly with 4.2.0. They should work fine in XFree86 CVS, however. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Geforce4 MX 440
No, I just installed basic 4.2.0 sources (via gentoo), compiled installed, ran XFree86 -configure, and it worked (even recognized and properly configured my Philips monitor). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Lane Sent: Tuesday, June 11, 2002 5:28 PM To: [EMAIL PROTECTED] Subject: RE: [Xpert]Geforce4 MX 440 At 04:11 PM 6/11/02, you wrote: Hmmm, my GeForce 4 MX 440 (VisionTek) works beautifully under 4.2.0 under Linux ... so unless there are real differences in the server code between FreeBSD and Linux, I would expect this to work. I would assume you have installed Nvidia's drivers right? They are Linux only. -- Mark Lane Hard Data Ltd. mailto:[EMAIL PROTECTED] Telephone: 01-780-456-9771 FAX: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada T5X 1Y3 http://www.harddata.com/ -- Ask me about our Affordable Alpha Systems! -- ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RFI: $150 to first solution: Radeon VE QY (PCI)/DVI plus ATI Mobility dual head (Long Post)
My system is a Compaq M700 laptop, plus an ArmadaStation EM docking station. The ArmadaStation EM has PCI slots (via a PCI to PCI bridge built into the station), one of which is being used for an Appian Hurricane (Radeon VE QY PCI) card. I have an external CRT (Philips 109B) hooked up to the output of the primary video card (built into the M700 -- an ATI Mobility P/M according to Windows 2K -- and hooked up to the external display port on the docking station), and a Philips 170B DVI display hooked up to the DVI output of the Hurricane (the CRT output/second head of the Hurricane is unused). Both the ATI Mobility and the Appian Hurricane seems to be recognized and allocated properly according to /proc/pci (see below for details). The PCI-PCI bridge is working as demonstrated by the fact the the second IDE controller in the docking station works fine (I have a CDRW drive hooked up and working on this controller). Here is what I can figure out: I have tried enabling and disabing just about every combination of options possible in the XF86Config file (including xinerama), but I always get the same INVALID MEM ALLOCATION error upon trying to REGISTER (!) the memory for one or both cards, which curiously seems to apply to the ATI Mobility chip's memory range rather than the Hurricane's (which is where I expected problems). There is a bizzare warning in the X log file before the memory allocation error that there is no Device instance for the Radeon card at 1:0:0 -- but the device at 1:0:0 is NOT the Radeon card but instead the Mobility (maybe this is the problem???). The XF86Config file very clearly has two Device statements, and the correct BusIDs, one for each of the Mobility and Radeon cards (I can provide a XF86Config file upon request, but I am pretty sure that the problem is not there). Also, X seems unable to access the Hurricane's bios which may or may not be important (I can probably provide the necessary information -- memory size, etc. via XF86Config). I am using Gentoo Linux 1.1a built from stage 1 (kernel 2.4.19, XFree86 4.2.0). I also have the 4.2.0 Gatos ATI drivers (tried both with and without these -- same result). Since I have this working in Windows 2000 without any glitches, I thought it might be useful also to know the memory ranges utilized by Windows 2000. They are: ATI Mobility P/M 8MB SDRAM 5000 - 50FF 5100 - 51000FFF 000A - 000B Appian Hurricane 32MB F000 - F7FF FFEE - FFEE Note that the ATI Mobility ranges are the same as in Linux. However, the Hurricane memory ranges are really different. Not sure if this matters. I have been working on this (see below for details) for several weeks on my own, and despite several postings here and elsewhere and bug reports I have submitted, I think I must be the only one out there with this specific problem (might be related to other Radeon VE/QY PCI issues -- not sure). From ploughing through the source code for the ati driver and kernal pci routines, I have mostly determined that the solution is going to take me a while since I am too far down on the learning curve with respect to kernal/device driver memory registration/allocation. So, I am hoping that someone out there with more experience will take me up on the offer ($150 paid via c2it upon sucessful X startup) to provide enough assistance to me to get my X server up an running in dual head mode. I am an experienced if a bit rusty C programmer and have been using Linux for 8 years now, so I can do some of the work myself, but I desparately need help in understanding data structures and operations inside of X and the kernel, and in finding the buggy code so that I can fix it. I am appending to the end of this message (a) XFree86 log output, (b) cat /proc/pci, (c) scanpci output, and (d) lspci output (yes, I know this is repetetive but each contains info in a little different format and detail so I want to be overinclusive). If I am lucky enough to get more than one person helping me, I will allocate the $150 between/among those who provided the most assistance. All resulting code must be contributed back to XFree86 under the XFree86 license. I will be happy to provide more details if needed upon request. Jeff Norman Here are the files in the order listed above: [XFREE86 LOG] 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 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:
[Xpert]Memory allocation code/kernel interfaces? (Resounding Silence!)
Having heard nothing on my specific problem (I have the Compaq Armada M700/ATI Mobility that seems to break under XFree 4.2.0 and 4.1.x but only after docking in the docking station) ... I am going to try to fix this myself. Could someone point me in the right direction (e.g., module, file, line, whatever) to find the point at which XFree (or if application the ATI server code) is trying to find a memory range for the display adapter. Clipped below is the partial output from the log file that should clarify what I am looking for. I suspect, since this problem seems to have crept up in the latest kernel versions, that there is some problem in the kernel's memory management as well so any pointers there would be helpful too. Also, any documentation or explanation as to the data structures used and the sequence of modules/functions called in initializing the PCI/AGP memory space for the device would be most useful. JSN (excerpt from log file below...) XFree86 Version 4.2.0 / 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.18-1mdksmp i686 [ELF] [CLIPPED] (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 = 0x3b54, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card 0e11,b110 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:04:0: chip 104c,ac1b card 4800, rev 03 class 06,07,00 hdr 82 (II) PCI: 00:04:1: chip 104c,ac1b card 5400, rev 03 class 06,07,00 hdr 82 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,80,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 03 class 06,80,00 hdr 00 (II) PCI: 00:08:0: chip 125d,1978 card 0e11,b112 rev 10 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 8086,1229 card 8086,2203 rev 09 class 02,00,00 hdr 80 (II) PCI: 00:09:1: chip 11c1,0445 card 8086,2203 rev 00 class 07,00,00 hdr 80 (II) PCI: 01:00:0: chip 1002,4c4d card 0e11,b111 rev 64 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: 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-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) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x8c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0x3000 - 0x30ff (0x100) IX[B] [1] -1 0x3400 - 0x34ff (0x100) IX[B] [2] -1 0x3800 - 0x38ff (0x100) IX[B] [3] -1 0x3c00 - 0x3cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0x5000 - 0x510f (0x110) MX[B] (II) Bus 1 prefetchable memory range: (--) PCI:*(1:0:0) ATI Mach64 LM rev 100, Mem @ 0x5000/24, 0x5100/12, I/O @ 0x3000/8 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0x000f - 0x000f (0x1) MX[B] [3] -1 0x000c - 0x000e (0x3) MX[B] [4] -1 0x - 0x0009 (0xa) MX[B] [5] -1 0x - 0x (0x1) IX[B] [6] -1 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0x5130 - 0x51300fff (0x1000) MX[B] [1] -1 0x5110 - 0x5111 (0x2) MX[B] [2] -1 0x5128 - 0x51280fff (0x1000) MX[B] [3] -1 0x5000 - 0x53ff (0x400) MX[B] [4] -1 0x5100 - 0x51000fff (0x1000) MX[B](B) [5] -1 0x5000 - 0x50ff (0x100) MX[B](B) [6] -1 0x4080 - 0x4087 (0x8) IX[B] [7] -1 0x4040 -
[Xpert]Radoen QD
I am running SuSE 7.3 and I love it! I purchased an ATI Radeon 32 mb video card only to find out that it has a Radeon QD chipset. Unfortunately Xfree86 and SuSE only partially support this chipset. So much so that when I try to enable 3D acceleration I get a black screen or X freezes completely. I feel Xfree86 is a great product, and regardless of my current situation I will continue to support this project. I was just wondering if anyone out there knows what I can do to fix my problem. I've tried everything and I'm just running in circles. Also, does the new 4.2 version of Xfree86 support my chip set? Any help in this matter would be greatly appretiated. Thanks, Jeff ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
