development artifacts of XFree86 needed for certification effort
We want to use XFree86 in an avionics sofware product certified to DO-178B. To get XFree86 certified we need to reference any requirements standards, design standards and coding standards that have been used in the development of XFree86. I found something that looks like a part of design standards in doc/DESIGN. Is there anything else? We also need to provide the high level requirements of the software. Is there anything that could help us putting them together? Thank you Robert -- EuroAvionics Navigationssysteme Am Lindenberg 8 D-71263 Weil der Stadt Germany Tel.: +49 (0)7033 1380 351 Fax: +49 (0)7033 1380 111 Mail: [EMAIL PROTECTED] Web: www.euroavionics.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: REGION_* rework (CVS Update: xc (branch: trunk))
Marc Aurele La France wrote (in a message from Wednesday 3) On Thu, 4 Dec 2003, Harald Nordgård-Hansen wrote: Marc Aurele La France [EMAIL PROTECTED] writes: Log message: An improved implementation of ... 573. Rework REGION_* macros to eliminate NEED_SCREEN_REGIONS build failures (Marc La France). ... to eliminate the extra store that was introduced. I just tried to compile current HEAD here, and this change causes compilation errors in xc/programs/Xserver/Xext/security.c, which uses the REGION_*-macros. I guess that one needs updates as well. Details? I see no such failures here. I see that on OpenBSD too. I've not had time on investigate yet: cc -c -O2 -ansi -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes - Wmissing-declarations -Wnested-externs -Wundef -fno-stack-protector -I. -I../ include -I../../../exports/include/X11 -I../../../include/extensions -I../../../include/fonts -I../mi -I../render -I../../../programs/Xserver/hw/xfre e86/common -I../../../include/fonts -I../../.. -I../../../exports/ include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DT OGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -D GCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -D XFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -D BUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO =15 -DNARROWPROTO -DMITMISC -DXTEST -DXTRAP -DXSYNC -DXCMISC -DXRECORD -DMITSH M -DBIGREQS -DXF86VIDMODE -DXF86MISC -DDBE -DDPMSExtension -DEVI -DSCREENSAVER - DXV -DXVMC -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_ MESA -DFONTCACHE -DRES -DDEFAULTPOLICYFILE=\/usr/X11R6/lib/X11/xserver/Secur ityPolicy\ security.c security.c: In function `SecurityCensorImage': security.c:1232: dereferencing pointer to incomplete type security.c:1233: dereferencing pointer to incomplete type security.c:1236: dereferencing pointer to incomplete type security.c:1236: warning: left-hand operand of comma expression has no effect security.c:1307: dereferencing pointer to incomplete type security.c:1308: dereferencing pointer to incomplete type *** Error code 1 Stop in /local/X11R6-test/build/programs/Xserver/Xext (line 1106 of Makefile). *** Error code 1 Stop in /local/X11R6-test/build/programs/Xserver (line 1380 of Makefile). *** Error code 1 Stop in /local/X11R6-test/build/programs (line 1026 of Makefile). *** Error code 1 Stop in /local/X11R6-test/build (line 977 of xmakefile). *** Error code 1 Stop in /local/X11R6-test/build (line 1057 of xmakefile). *** Error code 1 Stop in /local/X11R6-test/build (line 45 of Makefile). Exit 1 Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
hi
Watch the Hottest Adult Hustler DVD's All at Megasixtynine for Just $1!!! CLICK HERE FOR A FREE TOUR! no more of these
Re: REGION_* rework (CVS Update: xc (branch: trunk))
Matthieu Herrb [EMAIL PROTECTED] writes: I see that on OpenBSD too. On Debian stable and unstable it says: security.c: In function `SecurityCensorImage': security.c:1232: error: dereferencing pointer to incomplete type security.c:1233: error: dereferencing pointer to incomplete type security.c:1236: error: dereferencing pointer to incomplete type security.c:1236: warning: left-hand operand of comma expression has no effect security.c:1307: error: dereferencing pointer to incomplete type security.c:1308: error: dereferencing pointer to incomplete type security.c:1236: warning: value computed is not used The reason seems to be the changes in Xserver/input/regionstr.h, probably the referencing of pScreen-myNum, which would indicate that security.c has an incomplete understanding of the structure of pScreen or something. -Harald -- Harald Nordgård-Hansen, Linpro AS, Wilbergjordet 1, NO-1605 Fredrikstad, Norway Phone/Fax: +47 6935 9255/56 http://harald.nordgard-hansen.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: (Warning long!) Re: X11 CVS with linux 2.6.0-test9?
maybe there is just a power save flaw, ACPI has been significantly reworked, and I think it's on by default now. ACPI BIOS implementations are also notoriously buggy. ACPI can also affect your IRQ routing etc, so if you're using it you might want to try turning it off and seeing what happens. Craig Ringer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: (Warning long!) Re: X11 CVS with linux 2.6.0-test9?
I suppose I could have a hardware problem, since my PC is a couple years old now. However, I can leave the same computer just running a 2.4.x kernel for days with no problems. Would the redesigned kernel 2.6.x bang the hardware so much more; going beyond that of kernel 2.4.x? It can be that a new kernel does make use of resources that were previousely ignored. in the past e.g. turning on fast writes on the AGP bus lead several systems to instable behaviour - the chipset claimed it supports that but when enabling this it all turned out to be of questionable use. maybe there is just a power save flaw, a problem with IRQ coding or something else that hits the system at a rather sporadic rate - it is hard to say what it is. sometimes only an analysis with quite advanced hard and software tools can shed a light on the root cause. -Alex. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
AFTER-HOURS TRADING - Breaking News...barbara
AFTER-HOURS TRADING - BREAKING NEWS Get Quote - http://quote.money.cnn.com/quote/quote?symbols=htds Hard to Treat Diseases Incorporated - HTDS - Announces: Receipt of Tubercin Toxicity Study and Formation of Scientific Advisory Panel - Wednesday December 3, 8:04 pm ET DELRAY BEACH, Fla.--(BUSINESS WIRE)--Dec. 3, 2003--Hard to Treat Diseases Incorporated (Pink Sheets: HTDS) announces today that the spokesperson for the independent medical group conducting the testing for HTTD (HTDS) has forwarded the formal Testing Results of Tubercin®'s Toxicity Trials to HTTD. Tubercin of five different concentrations was administered to five groups of mice. A pathologist at the University of Oklahoma Health Science Center performed autopsies. The mice were randomized and only the control mouse was known to the pathologist, as stated in the cover letter of the Pathology Report. The report concludes, All tissues evaluated, visceral organs and the brain were essentially normal in appearance. The importance of this report is even better than I expected, stated the spokesperson for the medical group. As the testing continues and if the results are similar to those of Chemotherapy and or radiation with no harmful side effects, Tubercin has enormous potential for the treatment of cancer and the immune system. The President and CEO of HTTD, Mr. Colm J. King is in the process of forming a Scientific Advisory Panel with leading Oncologists and Immunologists from prestigious institutions in the U.S. The panel will review the reports and results of Tubercin®'s findings and will report back to Mr. King with the ongoing reports in layman language for the shareholders. We are continuing to receive promising results regarding Tubercin® and we're looking forward to additional positive results in the near future, stated Mr. King. These tests prove that Tubercin® is non-toxic and is the first step on the way to human clinical trials as well as the first positive breakthrough conducted in the United States with an independent medical group for Tubercin®. Operating out of Delray Beach, Florida, Hard to Treat Diseases Incorporated (HTTD) holds the international marketing rights, except South Korea, to Tubercin®, a patented immunostimulant developed for combating Cancer under medical patent (US Patent 6,274,356). The unique properties unlike other cancer products are clearly stated in the abstract summary of the patent... A carbohydrate complex, which is a mixture of low molecular-weight polysaccharides of an arabinomannan structure extracted from Mycobacterium tuberculosis, is highly effective in treating various cancer patients without incurring any adverse side effects. Statements in this press release that are not historical facts are forward-looking statements within the meaning of the Securities Act of 1933, as amended. Those statements include statements regarding the intent, belief or current expectations of the Company and its management. Such statements reflect management's current views, are based on certain assumptions and involve risks and uncertainties. Actual results, events, or performance may differ materially from the above forward-looking statements due to a number of important factors, and will be dependent upon a variety of factors, including, but not limited to, our ability to obtain additional financing and access funds from our existing financing arrangements that will allow us to continue our current and future operations and whether demand for our product and testing service in domestic and international markets will continue to expand. The Company undertakes no obligation to publicly update these forward-looking statements to reflect events or circumstances that occur after the date hereof or to reflect any change in the Company's expectations with regard to these forward-looking statements or the occurrence of unanticipated events. n wruorxtkljcjfj w o hx zov kx
RE: (Warning long!) Re: X11 CVS with linux 2.6.0-test9?
On Wed, 3 Dec 2003, Alexander Stohr wrote: I tried just leaving the display running without doing anything interactive with the interface and X ran for several hours before freezing. All that was running was Xscreensaver. I then tried again using X normally but with a different window manager (XFCE 4) and it worked for about an hour and then froze again. having a machine frozen after several hours could mean a thermal problem. this can inlcude even overclocked CPUs or instable RAM or anything else on the bus or the grafics. I suppose I could have a hardware problem, since my PC is a couple years old now. However, I can leave the same computer just running a 2.4.x kernel for days with no problems. Would the redesigned kernel 2.6.x bang the hardware so much more; going beyond that of kernel 2.4.x? -Alex. Fred Error Loading Explorer.exe You must reinstall Windows. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: REGION_* rework (CVS Update: xc (branch: trunk))
On Thu, 4 Dec 2003, Harald Nordgård-Hansen wrote: Matthieu Herrb [EMAIL PROTECTED] writes: I see that on OpenBSD too. On Debian stable and unstable it says: security.c: In function `SecurityCensorImage': security.c:1232: error: dereferencing pointer to incomplete type security.c:1233: error: dereferencing pointer to incomplete type security.c:1236: error: dereferencing pointer to incomplete type security.c:1236: warning: left-hand operand of comma expression has no effect security.c:1307: error: dereferencing pointer to incomplete type security.c:1308: error: dereferencing pointer to incomplete type security.c:1236: warning: value computed is not used The reason seems to be the changes in Xserver/input/regionstr.h, probably the referencing of pScreen-myNum, which would indicate that security.c has an incomplete understanding of the structure of pScreen or something. It turns out I didn't see this because my builds include the MultiBuffer extension. Anyway, this, along with glitches in fbcompose fbglyph others have reported, should now be fixed (or at least after cvsup's next resync). 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. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
On Thu, 4 Dec 2003 07:49:05 -0800 (PST), Alex Deucher [EMAIL PROTECTED] wrote: Like I said before: If you MB is 8x you will need to patch your 2.4 kernel with 8x support (or if you can set your BIOS to 4x only mode) or use a 2.6 kernel. once you have that done you can just use the DRI snapshots. This will allow you to use 4x mode. if you want to use 8x, you will have to apply michel/hui's, or keith's 8x patch. With my 9800XT I have the same problem, but my Mobo has only 4x AGP, so I don't have any clue as to why it doesn't work. I always get these errormessage when I load agpgart and fglrx and then startx. The weird thing is that X starts up with this gray screen and the mouse working. It only crashes the instant when the KDE dialog should be coming up. (==) Using config file: /etc/X11/XF86Config-4 (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found Could not init font path element /usr/X11R6/lib/X11/fonts/local/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! DCOP aborting call from 'anonymous-3627' to 'kded' ERROR: KUniqueApplication: DCOP communication error! DCOP aborting call from 'anonymous-3630' to 'knotify' ERROR: KUniqueApplication: DCOP communication error! startkde: Shutting down... -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] Radeon 920, hardware 3D
I always get these errormessage when I load agpgart and fglrx and then startx. The weird thing is that X starts up with this gray screen and the mouse working. It only crashes the instant when the KDE dialog should be coming up. (==) Using config file: /etc/X11/XF86Config-4 (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found Could not init font path element /usr/X11R6/lib/X11/fonts/local/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! DCOP aborting call from 'anonymous-3627' to 'kded' ERROR: KUniqueApplication: DCOP communication error! DCOP aborting call from 'anonymous-3630' to 'knotify' ERROR: KUniqueApplication: DCOP communication error! startkde: Shutting down... looks to me like your KDE install is somewhat corrupted. how about a totally pure and simple XFree86? this will launch an X-Server without any window manager. shut it down with CTRL-ALT-Backspace if the mouse moves. other attempt, try fvwm2, twm or GNOME window manager. it should be configureable by your system software or via hidden files at your user's home directory. -Alex. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: (Warning long!) Re: X11 CVS with linux 2.6.0-test9?
FH I suppose I could have a hardware problem, since my PC is a couple years FH old now. However, I can leave the same computer just running a 2.4.x FH kernel for days with no problems. HZ is 1000 by default in 2.6; the different scheduling might perhaps cause a deadlock somewhere. Can you try with a 2.6 kernel compiled with HZ being 100 and see whether you can reproduce the problem? Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
On Thu, 4 Dec 2003 18:57:10 +0100, Alexander Stohr [EMAIL PROTECTED] wrote: how about a totally pure and simple XFree86? this will launch an X-Server without any window manager. shut it down with CTRL-ALT-Backspace if the mouse moves. OK. Never thought of that. On the other hand my desktop works fine as long as I don't use the agpgart with th fglrx driver. As sonn as I load agpgart before fglrx (which should enable 3D) I get this problem. other attempt, try fvwm2, twm or GNOME window manager. Thanks. I try that. -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
On Thu, 4 Dec 2003 18:57:10 +0100, Alexander Stohr [EMAIL PROTECTED] wrote: how about a totally pure and simple XFree86? this will launch an X-Server without any window manager. shut it down with CTRL-ALT-Backspace if the mouse moves. other attempt, try fvwm2, twm or GNOME window manager. it should be configureable by your system software or via hidden files at your user's home directory. Thanks! You really made my day! :)The last days I was hunting for some info and I couldn't find anything. I dind't know what to try else, so this gave me at least a little boost, even though I still have no 3D yet. I tried running fvwm2 and it worked. I verified with lsmod and I could see at the usagecount that X was indeed using the fglrx driver. Normally it is 0 and now it was 6 and 4 (agpgart). I tried running glxgears but it gave me an Breakpoint/Trap something errormessage. The same for fgl_glxgears, glxinfo, etc.) was always the same. OpenGL should work in fvwm2 the same as in KDE, right? The question now is, what should I do next? I'am running KDE 3.1 so I should be quite fine. Do you mean I should reinstall KDE? Or is there something else? This really helped a lot, because now I'm at least a (even though a tiny) step further. :) -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
KDE probably crashes or locks up since it preloads libGL. it's all related to the fact that HW 3D doesn't work. perhaps you have multiple versions of libGL floating around? Alex --- Gerhard W. Gruber [EMAIL PROTECTED] wrote: On Thu, 4 Dec 2003 18:57:10 +0100, Alexander Stohr [EMAIL PROTECTED] wrote: how about a totally pure and simple XFree86? this will launch an X-Server without any window manager. shut it down with CTRL-ALT-Backspace if the mouse moves. other attempt, try fvwm2, twm or GNOME window manager. it should be configureable by your system software or via hidden files at your user's home directory. Thanks! You really made my day! :)The last days I was hunting for some info and I couldn't find anything. I dind't know what to try else, so this gave me at least a little boost, even though I still have no 3D yet. I tried running fvwm2 and it worked. I verified with lsmod and I could see at the usagecount that X was indeed using the fglrx driver. Normally it is 0 and now it was 6 and 4 (agpgart). I tried running glxgears but it gave me an Breakpoint/Trap something errormessage. The same for fgl_glxgears, glxinfo, etc.) was always the same. OpenGL should work in fvwm2 the same as in KDE, right? The question now is, what should I do next? I'am running KDE 3.1 so I should be quite fine. Do you mean I should reinstall KDE? Or is there something else? This really helped a lot, because now I'm at least a (even though a tiny) step further. :) -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
run ldd on your glxgears or glxinfo executables and see which libGL it is using. Alex --- Gerhard W. Gruber [EMAIL PROTECTED] wrote: On Thu, 4 Dec 2003 11:52:43 -0800 (PST), Alex Deucher [EMAIL PROTECTED] wrote: KDE probably crashes or locks up since it preloads libGL. it's all related to the fact that HW 3D doesn't work. perhaps you have multiple versions of libGL floating around? How can I verify that? I think I looked into that, but the problem is that I don't really know where to look, so I might have missed something. -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
On Thu, 4 Dec 2003 12:35:57 -0800 (PST), Alex Deucher [EMAIL PROTECTED] wrote: run ldd on your glxgears or glxinfo executables and see which libGL it is using. It is using the ones from the driver. It uses libGL which points to a link which is the drvier lib. I made a diff on the file which is in the driver directory and the installed libGL.so.1.2 and they are the same. When I run glxgears I get now 300FPS which is a little better because previously I had 99FPS but I think that was because I was using sync to vert retrace. when I run enemy territory it always claims that I'm using Mesa, though I don't know why it thinks this. I already uninstalled Mesa, so there shouldn't be any files there. -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
On Thu, 04 Dec 2003 21:02:44 +0100 (CET), [EMAIL PROTECTED] wrote: You found that quickly. I don't know what the chipset is. How can I figure that out? I am researching the kernel. Their ads sayit has a via chipset. So I tried tust the via-agp module and got the same problem. I looked again and the mother board should have a Via ProSavage KN400 chipset. I can't imagine what the marketeers at VIA are smoking. The graphics engine they are now labelling ProSavage KN400 is NOT, in fact, a Savage. It is a CastleRock. There is a CastleRock driver available from VIA, but it is completely separate from their Savage driver. This is going to cause no end of grief. I've always said that the XFree86 Savage driver supports every graphics chip with Savage in the name. Now, that is no longer true. -- - Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] Radeon 920, hardware 3D
run ldd on your glxgears or glxinfo executables and see which libGL it is using. It is using the ones from the driver. It uses libGL which points to a link which is the drvier lib. I made a diff on the file which is in the driver directory and the installed libGL.so.1.2 and they are the same. diff does not work on binary files, you better compare the file sizes. i dont have to doubt, ldd must resolve the active files all the time. When I run glxgears I get now 300FPS which is a little better because previously I had 99FPS but I think that was because I was using sync to vert retrace. the 2nd is a reasonable effect. the first case should have some 2.000 fps or more, i think its software. try re-running glxgears with settings LIBGL_VERBOSE=1 and LIBGL_DEBUG=1 in the hosting shell, somtimes that gives some more hint. when I run enemy territory it always claims that I'm using Mesa, though I don't know why it thinks this. I already uninstalled Mesa, so there shouldn't be any files there. depends on distor and setup, sometimes there are standalone Mesa packages and other times it is all merged into the XF86 libGL packages as the non-optional sofware renderer fallback. -Alex. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
patch for a crash in x86 emulator
Hi, I've been running XFree86 4.3.0.1 on a machine with a particularly weird videocard and I've got the VESA driver craching. If anyone wonders, the BIOS data in the log is: (II) VESA(0): VESA BIOS detected (II) VESA(0): VESA VBE Version 3.0 (II) VESA(0): VESA VBE Total Mem: 1024 kB (II) VESA(0): VESA VBE OEM: Intel(R) 810, Intel(R) 815 Chipset Video BIOS (II) VESA(0): VESA VBE OEM Software Rev: 37.16 (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(R) 810, Intel(R) 815 Chipset (II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0 The machine is a retail box with embedded LCD touch-screen. A little investigation has shown that it crashes in x86emuOp_mov_word_SR_RM() (in programs/Xserver/hw/xfree86/int10/ops.c which is symlinked from extras/x86emu/src/x86emu) on the underlined line: case 3: /* register to register */ destreg = decode_rm_seg_register(rh); DECODE_PRINTF(,); srcreg = DECODE_RM_WORD_REGISTER(rl); DECODE_PRINTF(\n); TRACE_AND_STEP(); *destreg = *srcreg; ^^ break; This happens because destreg is 0, because it's returned that way from decode_rm_seg_register(). rh is 4, and that's the value that decode_rm_seg_register() in decode.c (also linked from extras) does not understand. I've looked it up in the manual and actually the value 4 is for FS and value 5 is for GS. So here is the patch (also attached, to avoid corruption by the mailer): -- cut here --- *** decode.c.0 Thu Dec 4 15:42:51 2003 --- decode.cThu Dec 4 17:15:29 2003 *** *** 699,705 --- 699,709 DECODE_PRINTF(DS); return M.x86.R_DS; case 4: + DECODE_PRINTF(FS); + return M.x86.R_FS; case 5: + DECODE_PRINTF(GS); + return M.x86.R_GS; case 6: case 7: DECODE_PRINTF(ILLEGAL SEGREG); -- cut here --- This patch made the X server to work with this card. Could someone please check it in? I've looked in CVS and the most recent version still has this bug in it. There is also a more general question: in case when an instruction opcode can't be decoded, many routines in decode.c rely on just calling HALT_SYS() for error handling. However HALT_SYS() expands to X86EMU_halt_sys() which does nothing but sets a flag. The decode routines return 0 instead of all kinds of pointers to their caller which would immediately try to reference that pointer and crash. That means that any misformatted routine met in BIOS will make the X server to crash. I think that it's not good. I think that in case of a bad opcode an error message has to be printed into the log, so that the user would have some clue, and then the decoders must return not NULL pointer but a valid pointer to some trash value, so that their caller would be able to reference it without crashing before the interpreter has a chance to halt. If I make a patch to fix it as described, would anyone be willing to review and commit it? (BTW, any pointers to how to print an error message properly from the bowels of the i86 interpreters would be appreciated too). -SB decode.df.gz Description: GNU Zip compressed data
Re: bugs [WAS:] XFree86 4.4.0 RC1
On Thu, 2003-12-04 at 20:19, David Dawes wrote: If you have any open bugs in our bugzilla, you need to verify whether or not they are still valid against this release candidate. Send a note here for bugs that are confirmed to still be a problem, and close ones that you confirm are fixed. Bugs that are not confirmed against a release candidate will be closed as a matter of course when 4.4 is released. If you could take a look at http://bugs.xfree86.org/show_bug.cgi?id=651, that would be superb. Thanks, Donnie Berkholz signature.asc Description: This is a digitally signed message part
Re: patch for a crash in x86 emulator
On Thu, 04 Dec 2003 20:35:02 -0500, Sergey Babkin wrote: I've been running XFree86 4.3.0.1 on a machine with a particularly weird videocard and I've got the VESA driver craching. ... A little investigation has shown that it crashes in x86emuOp_mov_word_SR_RM() ... This happens because destreg is 0, because it's returned that way from decode_rm_seg_register(). rh is 4, and that's the value that decode_rm_seg_register() in decode.c (also linked from extras) does not understand. I've looked it up in the manual and actually the value 4 is for FS and value 5 is for GS. So, the conclusion here is that the Intel 815 BIOS uses FS and GS? That is both surprising and disturbing. The BIOS runs in real/v86 mode, and is not generally allowed to make any assumptions about the addressing in the machine. XFree86 doesn't map in any low-memory sections other than the segments at 0, A, B, and C. Given that, it is hard to imagine a scenario where DS and ES are not completely sufficient to do the job. Do you know what call is being made at the time of the crash? -- - Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
Hi! What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? Original Message Subject: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Date: Mon, 01 Dec 2003 23:51:57 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=931 Summary: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Product: Client Libraries Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Freetype AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] RFE: Update xc/extras/freetype2/ to Freetype 2.1.7 (current version seems to be V2.1.4). -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: patch for a crash in x86 emulator
On Thu, Dec 04, 2003 at 05:57:44PM -0800, Tim Roberts wrote: On Thu, 04 Dec 2003 20:35:02 -0500, Sergey Babkin wrote: I've been running XFree86 4.3.0.1 on a machine with a particularly weird videocard and I've got the VESA driver craching. ... A little investigation has shown that it crashes in x86emuOp_mov_word_SR_RM() ... This happens because destreg is 0, because it's returned that way from decode_rm_seg_register(). rh is 4, and that's the value that decode_rm_seg_register() in decode.c (also linked from extras) does not understand. I've looked it up in the manual and actually the value 4 is for FS and value 5 is for GS. So, the conclusion here is that the Intel 815 BIOS uses FS and GS? That is both surprising and disturbing. The BIOS runs in real/v86 mode, and is not generally allowed to make any assumptions about the addressing in the machine. XFree86 doesn't map in any low-memory sections other than the segments at 0, A, B, and C. Given that, it is hard to imagine a scenario where DS and ES are not completely sufficient to do the job. I have an Intel 810 with a BIOS that uses some 32-bit addressing modes that I hadn't seen used in other BIOSes. I put a bunch of updates for those into our emulator about a year ago. I haven't come across them using FS or GS though, but I'm not as surprised as I once would have been. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
Does fontconfig work with it yet? When FreeType 2.1.7 was announced I tried building it, then building fontconfig 2.2.1 and finding fontconfig couldn't build since it didn't use the #include MACROs preferred by the FreeType developers, and now required to use the FreeType headers in 2.1.7. I haven't had a chance to go back and check if fontconfig CVS was fixed. -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc.- Sun Software Group User Experience Engineering: G11N: X Window System Roland Mainz wrote: Hi! What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? Original Message Subject: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Date: Mon, 01 Dec 2003 23:51:57 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=931 Summary: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Product: Client Libraries Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Freetype AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] RFE: Update xc/extras/freetype2/ to Freetype 2.1.7 (current version seems to be V2.1.4). -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
On Fri, Dec 05, 2003 at 03:16:23AM +0100, Roland Mainz wrote: Hi! What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? The feature freeze was over 6 weeks ago. The integration phase is over. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Fwd: [OT] rsync 2.5.6 security advisory
--- Forwarded message --- From: Fabian Uebersax [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [OT] rsync 2.5.6 security advisory Date: Thu, 4 Dec 2003 10:02:06 +0100 From http://rsync.samba.org/ : December 4th 2003 Background The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this attack was conducted and we are releasing this advisory as a result of our investigations to date. Our conclusions are that: * rsync version 2.5.6 contains a heap overflow vulnerability that can be used to remotely run arbitrary code. * While this heap overflow vulnerability could not be used by itself to obtain root access on a rsync server, it could be used in combination with the recently announced brk vulnerability in the Linux kernel to produce a full remote compromise. * The server that was compromised was using a non-default rsyncd.conf option use chroot = no. The use of this option made the attack on the compromised server considerably easier. A successful attack is almost certainly still possible without this option, but it would be much more difficult. Please note that this vulnerability only affects the use of rsync as a rsync server. To see if you are running a rsync server you should use the netstat command to see if you are listening on TCP port 873. If you are not listening on TCP port 873 then you are not running a rsync server. New rsync release In response we have released a new version of rsync, version 2.5.7. This is based on the current stable 2.5.6 release with only the changes necessary to prevent this heap overflow vulnerability. There are no new features in this release. We recommend that anyone running a rsync server take the following steps: 1. Update to rsync version 2.5.7 immediately. 2. If you are running a Linux kernel prior to version 2.4.23 then you should upgrade your kernel immediately. Note that some distribution vendors may have patched versions of the 2.4.x series kernel that fix the brk vulnerability in versions before 2.4.23. Check with your vendor security site to ensure that you are not vulnerable to the brk problem. 3. Review your /etc/rsyncd.conf configuration file. If you are using the option use chroot = no then remove that line or change it to use chroot = yes. If you find that you need that option for your rsync service then you should disable your rsync service until you have discussed a workaround with the rsync maintainers on the rsync mailing list. The disabling of the chroot option should not be needed for any normal rsync server. The patches and full source for rsync version 2.5.7 are available from http://rsync.samba.org/ and mirror sites. We expect that vendors will produce updated packages for their distributions shortly. Credits The rsync team would like to thank the following individuals for their assistance in investigating this vulnerability and producing this response: * Timo Sirainen tss.iki.fi * Mike Warfield mhw.wittsend.com * Paul Russell rusty.samba.org * Andrea Barisani lcars.gentoo.org - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.4.0 RC1
I forgot to add that the latest online docs are available at http://www.xfree86.org/~dawes/pre-4.4/. Updates are welcome. Especially updates for the release notes. On Thu, Dec 04, 2003 at 08:19:59PM -0500, David Dawes wrote: The first release candidate for XFree86 4.4.0 (aka 4.3.99.901) was tagged late on 2 December. Links to the source can be found in the usual place http://www.xfree86.org/develsnaps/. I'm hoping that we'll have some binary sets available for people to download in the next day or so. The release candidates need to get as much testing as possible. Problems should be reported here [EMAIL PROTECTED]. If you have any open bugs in our bugzilla, you need to verify whether or not they are still valid against this release candidate. Send a note here for bugs that are confirmed to still be a problem, and close ones that you confirm are fixed. Bugs that are not confirmed against a release candidate will be closed as a matter of course when 4.4 is released. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
On Fri, Dec 05, 2003 at 04:58:07AM +0100, Roland Mainz wrote: David Dawes wrote: What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? The feature freeze was over 6 weeks ago. The integration phase is over. I wasn't considering this as feature, more as a way to get rid of the problems with PS Type1 fonts in the tree (and likely some other stuff was fixed, too) ... 25% of the FreeType changelog since 2.0 is for changes since 2.1.4. For integration purposes, that counts as a feature. ... OK... agreed ;-( If there are specific isolated fixes that would address the Type1 issues, they could certainly be considered. There is a simple fix for the FreeType Type1 parser which corrects the problem when someone has placed PostScript comments into Type1 fonts... maybe that's worth enougth for a backport to Xfree86 CVS... or not... If it's a problem people are running into, then it might be worth it. How does 2.1.4's handling of Type1 fonts compare with the Type1 backend? Do you mean xc/lib/font/Type1/ vs xc/lib/font/FreeType/ ? In my opinion the xc/lib/font/Type1/ should be retired since it causes server crashes such as Fatal server error: Beziers this big not yet supported and seems to have huge problems with rasterisation at higher resolutions. At Yeah, FatalError() from a font backend is bad. It ought to print a warning and return a relevant error code rather than killing the whole server. least for PS Type1 fonts the current code in xc/lib/font/FreeType/ is mature[1] enougth to let it handle all PS Type1 fonts (*.pfa, *.pfb). Unfortunately there are still the CID fonts where the FreeType backend and the FreeType library do not offer support for... but the question is - do we still need CID fonts when we have TTF/OTF font support ? I recently tracked down a problem report related to CID fonts, so I guess someone is using them. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
David Dawes wrote: How does 2.1.4's handling of Type1 fonts compare with the Type1 backend? Do you mean xc/lib/font/Type1/ vs xc/lib/font/FreeType/ ? In my opinion the xc/lib/font/Type1/ should be retired since it causes server crashes such as Fatal server error: Beziers this big not yet supported and seems to have huge problems with rasterisation at higher resolutions. At Yeah, FatalError() from a font backend is bad. It ought to print a warning and return a relevant error code rather than killing the whole server. Unfortunately it isn't easy to handle that kind of error in a simple way... you can use setjmp/longjmp() for that case but that doesn't do any cleanup nor will it reset the Type1 engine... least for PS Type1 fonts the current code in xc/lib/font/FreeType/ is mature[1] enougth to let it handle all PS Type1 fonts (*.pfa, *.pfb). Unfortunately there are still the CID fonts where the FreeType backend and the FreeType library do not offer support for... but the question is - do we still need CID fonts when we have TTF/OTF font support ? I recently tracked down a problem report related to CID fonts, so I guess someone is using them. What about handling *.pfa/*.pfb via the FreeType backend and let CID fonts be handled via the old Type1 backend ? At least the risk of hitting the Beziers this big not yet supportedco. minefield will be greatly lowered - and the workaround would be to remove the CID fonts from the font path (which doen't harm most users... removing all PS Type1 fonts from the font path will harm LOTS of users... ;-(). Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, CJAVASunUnix programmer /O /==\ O\ TEL +49 2426 901568 FAX +49 2426 901569 (;O/ \/ \O;) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
On Fri, Dec 05, 2003 at 06:04:54AM +0100, Roland Mainz wrote: David Dawes wrote: How does 2.1.4's handling of Type1 fonts compare with the Type1 backend? Do you mean xc/lib/font/Type1/ vs xc/lib/font/FreeType/ ? In my opinion the xc/lib/font/Type1/ should be retired since it causes server crashes such as Fatal server error: Beziers this big not yet supported and seems to have huge problems with rasterisation at higher resolutions. At Yeah, FatalError() from a font backend is bad. It ought to print a warning and return a relevant error code rather than killing the whole server. Unfortunately it isn't easy to handle that kind of error in a simple way... you can use setjmp/longjmp() for that case but that doesn't do any cleanup nor will it reset the Type1 engine... Yeah, it wouldn't be simple. Disabling the Type1 engine completely when one of these errors happens would even be preferable to aborting the whole X server. least for PS Type1 fonts the current code in xc/lib/font/FreeType/ is mature[1] enougth to let it handle all PS Type1 fonts (*.pfa, *.pfb). Unfortunately there are still the CID fonts where the FreeType backend and the FreeType library do not offer support for... but the question is - do we still need CID fonts when we have TTF/OTF font support ? I recently tracked down a problem report related to CID fonts, so I guess someone is using them. What about handling *.pfa/*.pfb via the FreeType backend and let CID fonts be handled via the old Type1 backend ? That is the current default behaviour. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: bugs [WAS:] XFree86 4.4.0 RC1
On Thu, Dec 04, 2003 at 08:36:57PM -0500, Donnie Berkholz wrote: On Thu, 2003-12-04 at 20:19, David Dawes wrote: If you have any open bugs in our bugzilla, you need to verify whether or not they are still valid against this release candidate. Send a note here for bugs that are confirmed to still be a problem, and close ones that you confirm are fixed. Bugs that are not confirmed against a release candidate will be closed as a matter of course when 4.4 is released. If you could take a look at http://bugs.xfree86.org/show_bug.cgi?id=651, that would be superb. Thanks for pointing it out. I've just committed the fix. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Radeon 920, hardware 3D
I've got my new machine with the Radeon 9200. I want to try and setup the hardware 3D support for it. I am going to build the latest development snapshot and or the CVS and try to set it up. How stable are these? Do you have any tips or suggestions on the building or configuration? Is there an easier way? Thanks, Tom Corner On 20-Nov-2003 Alex Deucher wrote: one thing you will run into is that if your new motherboard supports 8x and your radeon supports 8x, you will need a patched version of agpgart that supports 8x or the DRI will not work if you are using linux 2.4.x. 2.6 supports 8x natively. Just a heads up. Alex --- [EMAIL PROTECTED] wrote: I signed onto the developer list too now. When the computer comes, I am thinking of trying driver snapshots or CVS versions. I have heard that ATI does not support their own driver very well. Thanks again, Tom On 20-Nov-2003 Alex Deucher wrote: The drivers do not currently have support for agp 8x. Michel has a patch on his website from ati, but it hasn't been applied/tested yet as far as I know. I don't have the link off hand. I doubt you will notice any difference between 8x and 4x. Let me know how it goes. Alex --- [EMAIL PROTECTED] wrote: Thanks. I don't get to test it until the laptop with radeon mobility 9200 comes next week. I understand the 9200 is the same as the 9000 except that the agp is 8x instead of 4x. Can I specify agp 8x to take advantage of the higher speed? Thanks again, Tom Corner __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 20-Nov-2003 16:50:41 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 04-Dec-2003 11:47:41 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Radeon 920, hardware 3D
Like I said before: If you MB is 8x you will need to patch your 2.4 kernel with 8x support (or if you can set your BIOS to 4x only mode) or use a 2.6 kernel. once you have that done you can just use the DRI snapshots. This will allow you to use 4x mode. if you want to use 8x, you will have to apply michel/hui's, or keith's 8x patch. Alex --- [EMAIL PROTECTED] wrote: I've got my new machine with the Radeon 9200. I want to try and setup the hardware 3D support for it. I am going to build the latest development snapshot and or the CVS and try to set it up. How stable are these? Do you have any tips or suggestions on the building or configuration? Is there an easier way? Thanks, Tom Corner On 20-Nov-2003 Alex Deucher wrote: one thing you will run into is that if your new motherboard supports 8x and your radeon supports 8x, you will need a patched version of agpgart that supports 8x or the DRI will not work if you are using linux 2.4.x. 2.6 supports 8x natively. Just a heads up. Alex --- [EMAIL PROTECTED] wrote: I signed onto the developer list too now. When the computer comes, I am thinking of trying driver snapshots or CVS versions. I have heard that ATI does not support their own driver very well. Thanks again, Tom On 20-Nov-2003 Alex Deucher wrote: The drivers do not currently have support for agp 8x. Michel has a patch on his website from ati, but it hasn't been applied/tested yet as far as I know. I don't have the link off hand. I doubt you will notice any difference between 8x and 4x. Let me know how it goes. Alex --- [EMAIL PROTECTED] wrote: Thanks. I don't get to test it until the laptop with radeon mobility 9200 comes next week. I understand the 9200 is the same as the 9000 except that the agp is 8x instead of 4x. Can I specify agp 8x to take advantage of the higher speed? Thanks again, Tom Corner __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 20-Nov-2003 16:50:41 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 04-Dec-2003 11:47:41 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
can't get direct 3D with Radeon 9200
I have tried everything. I have kernel 2.6.0test10 with radeon module(radeon.ko). I am running on an Acer 1355LMi_ATI laptop with a Radeon mobility 9200. I have loaded glx and dri in XF86Config. I have radeon selected as device. When this didn't work I went to the dri wiki web site and loaded and installed their latest package. Oh I forgot to mention I downloaded compiled and installed XFree86-4.3.99.16.tar.bz2. That is my current setup. When the radeon module from dri didn't help I went back to the radeon.ko module from 2.6.0test10. glxinfo says: (more from me after) name of display: :0.0 display: :0 screen: 0 direct rendering: No server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_make_current_read client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group GLX extensions: GLX_ARB_get_proc_address, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.4 Mesa 5.0.2 OpenGL extensions: GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_point_parameters, GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_texture_mirror_once, GL_ATI_texture_env_combine3, GL_IBM_texture_mirrored_repeat, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_texgen_reflection, GL_NV_texture_rectangle, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SGIX_shadow_ambient glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat -- 0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None 0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None 0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None 0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None 0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None 0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None 0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None should I go back to kernel 2.4.22? Should I use the dri wiki? Should I try the XFree86 CVS? Should I try ATI's package again. They don't seem to have put much work into it. Thanks, Tom Corner --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 04-Dec-2003 17:34:42 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: can't get direct 3D with Radeon 9200
what does your xfree86 log say? how about the output of lsmod or your dmesg? Alex --- [EMAIL PROTECTED] wrote: I have tried everything. I have kernel 2.6.0test10 with radeon module(radeon.ko). I am running on an Acer 1355LMi_ATI laptop with a Radeon mobility 9200. I have loaded glx and dri in XF86Config. I have radeon selected as device. When this didn't work I went to the dri wiki web site and loaded and installed their latest package. Oh I forgot to mention I downloaded compiled and installed XFree86-4.3.99.16.tar.bz2. That is my current setup. When the radeon module from dri didn't help I went back to the radeon.ko module from 2.6.0test10. glxinfo says: (more from me after) name of display: :0.0 display: :0 screen: 0 direct rendering: No server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_make_current_read client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group GLX extensions: GLX_ARB_get_proc_address, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.4 Mesa 5.0.2 OpenGL extensions: GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_point_parameters, GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_texture_mirror_once, GL_ATI_texture_env_combine3, GL_IBM_texture_mirrored_repeat, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_texgen_reflection, GL_NV_texture_rectangle, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SGIX_shadow_ambient glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat -- 0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None 0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None 0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None 0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None 0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None 0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None 0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None should I go back to kernel 2.4.22? Should I use the dri wiki? Should I try the XFree86 CVS? Should I try ATI's package again. They don't seem to have put much work into it. Thanks, Tom Corner --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 04-Dec-2003 17:34:42 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? Free Pop-Up Blocker - Get it now
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
On 04-Dec-2003 Alex Deucher wrote: what does your xfree86 log say? how about the output of lsmod or your dmesg? lsmod: Module Size Used by ati_agp 6284 - via_agp 5600 - sis_agp 3840 - amd_k7_agp 5548 - evdev 7296 - snd_via82xx21568 - ohci_hcd 16000 - ide_scsi 12164 - rtc10600 - XFree86.0.log: _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/wanderer:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 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.3.99.16 Release Date: 20 November 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.0-test10 i686 [ELF] Current Operating System: Linux wanderer 2.6.0-test10 #2 Thu Dec 4 02:37:18 CET 2003 i686 Build Date: 04 December 2003 Changelog Date: 21 November 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. 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: Thu Dec 4 17:31:00 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor flatpanel (**) | |--Device radeon-9200 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout de (**) XKB: layout: de (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X 11/fonts/75dpi/:unscaled,/ usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X 11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fo nts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 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.3.99.16, 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.3.99.16, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8090, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3205 card 1106,7205 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b168 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 104c,ac50 card , rev 02 class 06,07,00 hdr 02 (II) PCI: 00:08:0: chip 104c,8026 card 1025,0033 rev 00 class 0c,00,10 hdr 00 (II) PCI: 00:09:0: chip 10ec,8180 card 10ec,8180 rev 20 class 02,00,00 hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1025,0033 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1025,0033 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1025,0033 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3104 card 1025,0033 rev 82 class 0c,03,20 hdr 00 (II) PCI: 00:11:0: chip 1106,3177 card 1025,0033 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1025,0033 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:5: chip 1106,3059 card 1025,0033 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:11:6: chip 1106,3068 card 1025,0033 rev 80 class 07,80,00 hdr 00 (II) PCI: 00:12:0: chip 1106,3065 card 1025,0033 rev 74 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1002,5c61 card 1025,0033 rev 01 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
it seem to be an AGP problem: (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module is loaded before the radeon kernel module. it looks like you have lots of agp modules loaded (ati_agp, via_agp, sis_agp, amd_k7_agp). AGP in 2.6 is somewhat different than 2.4. rather than a single agpgart module it has an agpgart module plus various chipset specifc drivers. you need to load the one for you chipset. what chipset do you have? Alex --- [EMAIL PROTECTED] wrote: On 04-Dec-2003 Alex Deucher wrote: what does your xfree86 log say? how about the output of lsmod or your dmesg? lsmod: Module Size Used by ati_agp 6284 - via_agp 5600 - sis_agp 3840 - amd_k7_agp 5548 - evdev 7296 - snd_via82xx21568 - ohci_hcd 16000 - ide_scsi 12164 - rtc10600 - XFree86.0.log: _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/wanderer:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 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.3.99.16 Release Date: 20 November 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.0-test10 i686 [ELF] Current Operating System: Linux wanderer 2.6.0-test10 #2 Thu Dec 4 02:37:18 CET 2003 i686 Build Date: 04 December 2003 Changelog Date: 21 November 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. 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: Thu Dec 4 17:31:00 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor flatpanel (**) | |--Device radeon-9200 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout de (**) XKB: layout: de (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X 11/fonts/75dpi/:unscaled,/ usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X 11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fo nts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 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.3.99.16, 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.3.99.16, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8090, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3205 card 1106,7205 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b168 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 104c,ac50 card , rev 02 class 06,07,00 hdr 02 (II) PCI: 00:08:0: chip 104c,8026 card 1025,0033 rev 00 class 0c,00,10 hdr 00 (II) PCI: 00:09:0: chip 10ec,8180 card 10ec,8180 rev 20 class 02,00,00 hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1025,0033 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1025,0033 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1025,0033 rev 80 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
You found that quickly. I don't know what the chipset is. How can I figure that out? I am researching the kernel. Their ads sayit has a via chipset. So I tried tust the via-agp module and got the same problem. I looked again and the mother board should have a Via ProSavage KN400 chipset. I can't tell whether that includes the agp. I have agp support built into the kernel, but the chipset specific stuff shoukd be in the agp modules you saw. I have loaded basicly all of them and yes Windows says the agp is via, but via-agp doesn't work. Tom On 04-Dec-2003 Alex Deucher wrote: it seem to be an AGP problem: (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module is loaded before the radeon kernel module. it looks like you have lots of agp modules loaded (ati_agp, via_agp, sis_agp, amd_k7_agp). AGP in 2.6 is somewhat different than 2.4. rather than a single agpgart module it has an agpgart module plus various chipset specifc drivers. you need to load the one for you chipset. what chipset do you have? Alex --- [EMAIL PROTECTED] wrote: On 04-Dec-2003 Alex Deucher wrote: what does your xfree86 log say? how about the output of lsmod or your dmesg? lsmod: Module Size Used by ati_agp 6284 - via_agp 5600 - sis_agp 3840 - amd_k7_agp 5548 - evdev 7296 - snd_via82xx21568 - ohci_hcd 16000 - ide_scsi 12164 - rtc10600 - XFree86.0.log: _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/wanderer:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 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.3.99.16 Release Date: 20 November 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.0-test10 i686 [ELF] Current Operating System: Linux wanderer 2.6.0-test10 #2 Thu Dec 4 02:37:18 CET 2003 i686 Build Date: 04 December 2003 Changelog Date: 21 November 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. 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: Thu Dec 4 17:31:00 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor flatpanel (**) | |--Device radeon-9200 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout de (**) XKB: layout: de (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib /X 11/fonts/75dpi/:unscaled,/ usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr /X 11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fo nts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 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.3.99.16, 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.3.99.16, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8090, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3205 card 1106,7205 rev 00
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
take a look at the output of dmesg or your kernel log. You need to load via_agp.ko and agpgart.ko and radeon.ko Alex --- [EMAIL PROTECTED] wrote: You found that quickly. I don't know what the chipset is. How can I figure that out? I am researching the kernel. Their ads sayit has a via chipset. So I tried tust the via-agp module and got the same problem. I looked again and the mother board should have a Via ProSavage KN400 chipset. I can't tell whether that includes the agp. I have agp support built into the kernel, but the chipset specific stuff shoukd be in the agp modules you saw. I have loaded basicly all of them and yes Windows says the agp is via, but via-agp doesn't work. Tom On 04-Dec-2003 Alex Deucher wrote: it seem to be an AGP problem: (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module is loaded before the radeon kernel module. it looks like you have lots of agp modules loaded (ati_agp, via_agp, sis_agp, amd_k7_agp). AGP in 2.6 is somewhat different than 2.4. rather than a single agpgart module it has an agpgart module plus various chipset specifc drivers. you need to load the one for you chipset. what chipset do you have? Alex --- [EMAIL PROTECTED] wrote: On 04-Dec-2003 Alex Deucher wrote: what does your xfree86 log say? how about the output of lsmod or your dmesg? lsmod: Module Size Used by ati_agp 6284 - via_agp 5600 - sis_agp 3840 - amd_k7_agp 5548 - evdev 7296 - snd_via82xx21568 - ohci_hcd 16000 - ide_scsi 12164 - rtc10600 - XFree86.0.log: _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/wanderer:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 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.3.99.16 Release Date: 20 November 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.0-test10 i686 [ELF] Current Operating System: Linux wanderer 2.6.0-test10 #2 Thu Dec 4 02:37:18 CET 2003 i686 Build Date: 04 December 2003 Changelog Date: 21 November 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. 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: Thu Dec 4 17:31:00 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor flatpanel (**) | |--Device radeon-9200 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout de (**) XKB: layout: de (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib /X 11/fonts/75dpi/:unscaled,/ usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr /X 11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fo nts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 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.3.99.16, 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.3.99.16, module version = 1.0.0 ABI class: XFree86 Video
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
grep through the dmesg for agp stuff. the kernel log is usually /var/log/messages Alex --- [EMAIL PROTECTED] wrote: On 04-Dec-2003 Alex Deucher wrote: take a look at the output of dmesg or your kernel log. You need to load via_agp.ko and agpgart.ko and radeon.ko Alex demesg is just full of debug messages from acpi and where is the kernel log? It's getting late here. --- [EMAIL PROTECTED] wrote: You found that quickly. I don't know what the chipset is. How can I figure that out? I am researching the kernel. Their ads sayit has a via chipset. So I tried tust the via-agp module and got the same problem. I looked again and the mother board should have a Via ProSavage KN400 chipset. I can't tell whether that includes the agp. I have agp support built into the kernel, but the chipset specific stuff shoukd be in the agp modules you saw. I have loaded basicly all of them and yes Windows says the agp is via, but via-agp doesn't work. Tom On 04-Dec-2003 Alex Deucher wrote: it seem to be an AGP problem: (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel mod --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 04-Dec-2003 21:58:47 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] Re: can't get direct 3D with Radeon 9200
It always works if you watch it close enough. Actually I changed kernel to the 2.6.0-test11 that just came out. I kept the old configuration except I compiled agpgart as a module instead of being built into the kernel. now glxinfo says it's doing direct rendering!! glxgears gives about 1000 FPS although the gears don't seem to move much faster. Also there seems to be some hesitation or jerkiness in there movements. dmesg: ide1: BM-DMA at 0x2068-0x206f, BIOS settings: hdc:DMA, hdd:pio hda: IC25N060ATMR04-0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: PIONEER DVD-RW DVR-K12RA, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 117210240 sectors (60011 MB) w/7884KiB Cache, CHS=16383/255/63, UDMA(100) uhci_hcd :00:10.1: UHCI Host Controller uhci_hcd :00:10.1: irq 5, io base 2020 .. mice: PS/2 mouse device common for all mice synaptics reset failed synaptics reset failed synaptics reset failed Synaptics Touchpad, model: 1 Firmware: 5.8 180 degree mounted touchpad Sensor: 29 new absolute packet format Touchpad has extended capability bits - 4 multi-buttons, i.e. besides standard buttons - multifinger detection - palm detection input: SynPS/2 Synaptics TouchPad on isa0060/serio1 serio: i8042 AUX port at 0x60,0x64 irq 12 input: AT Translated Set 2 keyboard on isa0060/serio0 serio: i8042 KBD port at 0x60,0x64 irq 1 Advanced Linux Sound Architecture Driver Version 0.9.7 (Thu Sep 25 19:16:36 2003 UTC). request_module: failed /sbin/modprobe -- snd-card-0. error = -16 ALSA device list: No soundcards found. ACPI Debug] String: CMBatt - UPBH.BAT1 [ACPI Debug] Package: Elements Ptr - dfeede68 IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 bind 65536) NET: Registered protocol family 1 NET: Registered protocol family 17 ACPI: (supports S0 S3 S4 S5) kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 168k freed Adding 2097136k swap on /dev/hda5. Priority:-1 extents:1 EXT3 FS on hda6, internal journal Real Time Clock Driver v1.12 Linux agpgart interface v0.100 (c) Dave Jones ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device scsi0 : SCSI host adapter emulation for IDE ATAPI devices Vendor: PIONEER Model: DVD-RW DVR-K12RA Rev: 1.10 Type: CD-ROM ANSI SCSI revision: 02 Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 5 eth0: Setting full-duplex based on MII #1 link partner capability of 45e1. ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ohci_hcd: block sizes: ed 64 td 64 [ACPI Debug] String: QUERY_09 [ACPI Debug] String: CMBatt - SMSL [ACPI Debug] String: QUERY_20 [ACPI Debug] String: QUERY_20 via82xx: Assuming DXS channels with 48k fixed sample rate. Please try dxs_support=1 option and report if it works on your machine. PCI: Setting latency timer of device :00:11.5 to 64 [ACPI Debug] String: QUERY_09 [ACPI Debug] String: CMBatt - SMSL [ACPI Debug] Integer: 00F1 . [ACPI Debug] String: QUERY_20 [ACPI Debug] String: QUERY_20 [ACPI Debug] String: QUERY_09 [ACPI Debug] String: CMBatt - SMSL [ACPI Debug] String: QUERY_20 [ACPI Debug] String: QUERY_20 agpgart: Detected VIA KM400/KM400A chipset agpgart: Maximum main memory to use for agp memory: 438M agpgart: AGP aperture is 256M @ 0xe00comment: it seems to have found the chipset on the modprobe agpgart I don't seem to have the radeon here, but it did show up. I'd have to go through the dmesg dumps again to find everything. Right now I'm going to look at the kernel configuration to see if I can turn off the damn ACPI Debug messages. Thanks for the help, Tom Corner --- |\/\/\___/\/\/| Carol Anne Corner \ o o / Thomas Corner [EMAIL PROTECTED] ) ( 04-Dec-2003 23:54:16 Vienna, Austria ( * * ) mailer: xfmail \___/ Web Page: www.corner.chello.at --- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
