Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I'm sure Winischhofer.net has the driver that is needed to make it work, but I haven't figured out how to install it. I've got the powerarchiver compressed file on my box, but I don't know how to use the powerarchiver utility from the console or where to put the uncompressed files so that XF86Config can find them.
If you're familiar with how that is done, please let me know.
are there problems to the point of it being unusable? looking at www.XFree86.org, the sis315 has been supported since v3.3ish.
i had a sis6326, and it was ok. but then, i think the generic driver was written mainly for that chipset. lucky me
as for where the video drivers should go...
is it /lib/<something about the kernel>../<maybe modules>/drivers/video?
damn i wish i hit the reply button when i'm actually in LINUX.
the uncompressed files, what format are they? *.o? *.gz?
ok, this is the directory: /lib/modules/<kernel version>/kernel/drivers/video
stick the file in there, and modify your XF86Config file to use that driver.
When I would startx I would get a couple screenfuls of info that would end like this:
Quote:
Originally posted by tryangle (EE)Failed to load module "sis 315" (module does not exist, 0)
(EE)No drivers available
Fatal server error:
no screens found
The monitor was found. I have the correct horizontal and vertical frequencies for it. But as you can see, the driver failed to load... subsequently the screen was not found.
When I used just
Driver "sis"
in the XF86Config file it eliminated the first error. Which was an improvement, but it still didn't work.
After I load the video driver in the
Quote:
Originally posted by idiot_child /lib/modules/<kernel version>/kernel/drivers/video
directory would I use the Specific Name of the driver in the XF86Config file?
Like, I don't know, looking at the files that came in the package, I see a whole bunch of files, but among them are: sis_driver.c and sis_driver.h ...hmm, one of those sounds like it might be it.
Re: Thanks for hanging in there with me on this ...
Quote:
Originally posted by tryangle I've tried it with a space "sis 315", without a space "sis315" and just as "sis" So far, "sis" gives me only one error message, whereas the other two, give a second error message about a module not being found.
"module not found" tells you exactly what you need to know. Use the one which doesn't say that. ("sis")
Quote:
I've learned how to mount and umount my floppy and cdrom. This is great stuff working at the console! I was able to get the floppy drive automounted, but for some reason, Not the cdrom drive (directory). I'm trying to make sense of why I have a mnt directory and a misc directory both set up for reading the disc drives! I was able to read the floppy from both of them, but Not the cdrom. I was unable to get the cdrom to work from the misc directory!
I've been using the automounter quite successfully. Only bugger is the delay in unmounting. I found it useful to set the auto-eject feature on the CDROM to let me know when it's done. Re-mounting the disk will automatically pull it back in anyhow.
Quote:
So now, anyway, I loaded the .gz file for the sis315 driver from the Winischhofer site and I loaded power archiver. I need to run the powarc60.exe to set it up and then uncompress the driver. But where do I put the driver so the XF86Config file will find it?
Why on earth are you using powarc under Linux? My Debian system comes with Linux software for Zip, Arj, Rar, and a bunch of other predominantly Windows archiver formats. So much so that I go weeks if not months between booting to my Windows partition. At least, I did until I got this darned SiS650 video card.
As I understand it, you're supposed to grab the sis_dri and sis_drv archives, and then just replace the existing files of the same name, with the new ones. ("locate" is a handy command...)
Unfortunately, all that got me was a monitor that flickers on and off a few times, after which not even the consoles show anything. All I can do is blindly type "shutdown -f -r now", and wait for the system to boot again.
Quote:
Also, I was wondering, is there a -switch|argument|option for the find command that will enable me to search through all directories and all subdirectories from the originating point of conducting the search? I wanted to check to see if powerarc came with the RH8 distro and was already installed. I have no idea, but I thought it would be a good idea to check before I install it.
"find" does exactly that by default. I fotget what the switch is to stop it from doing sub-dir's... Find's also a little slow when you already know the filename you're looking for.
For the purpose of finding the files to replace, "locate /sis_dr" will do a much better job of it. Though I do wish locate supported either globs or regexp's... Still... I think it's database is plaintext, so I should be able to roll together a one-line "locate-regexp" script, or something...
You can identify the pci bus number by running lspci and looking for your controller. The numbering is rendered slightly differently (i.e. 01:09.0 would be 1:9:0 in XF86Config). I think you have to run this as su. If you don't have it, its in pciutils
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.