Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ugenn, im trying to PM u but the forums wont let me (no idea why)
Ive finally got a stable linux to screw with, SuSE. Im running xfree86 4.3, and the SMP kernel 2.6.4.
I copied over the driver from winichofer, as well as SiSctrl. I cannot get SiSctrl to function, so i cannot get my dual monitors to function correctly.
Would i have better luck just switching to Xorg? also how hard is that to do? and finally, whats this people are saying about recompiling the kernel with the driver?
Sorry buddy, I'm can't help you with the dual mon part. As for xorg, if your distro has it, get the packages from them. I believe all the major distros have switched to xorg since the xf86 licensing fiasco.
For the kernel compiling part, it depends depends on which driver you're referring. Kernel drivers will obviously need the kernel source tree to be built. The X drivers (sis_dri.so and sis_drv.o) require the X source to build.
I still cant get sisctrl to run...its dependency hell...i killed my install trying to solve it.. yes..suse told me "try reinstalling SuSE to solve the problem".....last time i try to update for that
I had to masacre my XF86Config. took only one shot, worked perfectly! ill figure out DRI and 3D support later....im still happy from my victory here
Ok i hate to digup an old thread...as i was the last poster...
im not on yoper 2.0, SMP kernel 2.6.8.1-2, xfree4.4. whats the status on DRI and sisfb? Yoper complains bout there being no sisfb at startup...well used to until they fixed the splash.
im mainly interested in the billiards game lol and if at all possible quake 3
My guess is that the splash uses vesafb by default for rendering and the video ioports are allocated to the vesa driver so whem sisfb tries to reserve those ports, a resource conflict results causing the load failure. You may need to compile sisfb statically to fix this or do w/o splash.
i think i do...i dont have sisfb in the kernel now...or anywhere for that matter..thats not my issue, it loads fine and all, im just curious about the DRI.
now if openGL is not written for sis, how does FooBilliard work?
I can tell that I have been trying everything to get 3D acceleration working with my SiS card (300 series), and that after the latest update to Xorg-6.8 it is for the first time working well. Tuxracer, Foobillard, and glxgears without a problem. haven't managed to get Cube run smoothly though...
Don't know if I catch the above discussion well, but if you want to use sisfb, make sure not to have any other framebuffer starting during boot. So disable the vesafb in the kernel config. See winisschofer's guide for these details. http://www.winischhofer.net/linuxsisvga.shtml
i just want to be able to get the 3D accelaration to play those games. How did you get to that? is sisfb what i need or what? or do i hafta compile something into the kernel?
On the 300 series, sisfb on kernel older than 2.6.3 furthermore plays an important role in connection with DRI: Sisfb manages the memory heap used by DRI for 3D texture and other data. This memory management is required for using DRI and has not been implemented into the X driver for the following simple reason: DRI does not necessarily have to be used with X.org/XFree86 only; a quite large part of the DRM/DRI infrastructure is part of the kernel and thus memory management should be in the kernel as well. (For more information, see my DRI page.)
Kernels >= around 2.6.3 do not need sisfb any longer for DRI memory management. The SiS DRM driver has been updated and features a memory manager of its own (which will be used if sisfb is not compiled). So unless you want a graphical console, you don't need sisfb.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.