Writing NVIDIA drivers to CD on Windows, then running on Linux?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Writing NVIDIA drivers to CD on Windows, then running on Linux?
Already fixed my HDD and my sound via this forum, hope this prob can be fixed too
Atm I have (this) machine running Win98, and it's the only one with an internet connection until I get my network cards etc etc.
My other machine has a fresh install of RH 7.3, with the 2.5.38 kernel installed (to fix HDD ) I need to download the NVidia drivers on here, then burn them to CD, then run them on linux.
When I try to do this, I get errors in linux. If it's RPMs then they can't be unpacked. If it's tar or gz files, the compression format is violated.
Why is this? Could it be something to do with the file naming system or something? If the names are too long they get saved as nvidia~1.rpm or whatever. Also windows has the .tar.gz files named as <name>.tar, with the file icon showing .gz (I'm using PowerArchiver).
How can I get around this problem? I desperately need to install the Nvidia drivers on my linux box... Any ideas?
firstly, always use the source, mcuh better for the drivers i find. right, well try running "file blah.tar.gz" on the files under linux and see what they report. naturally your windows archiver will report them as it has, as windows likes to hide known file extensions... can you get into the files under windows?
GRRR I just spend ages writing a post, then posted it, got taken to the wrong thread, and then came back and nothing had happened.
Anyway. I'll try turning Powerarchiver off first, and see what happens. BTW when I write the CD in Adaptec it says it's being named as foo.tar.gz but it actually gets written as foo~1.gz or whatever. This seems to be because the software is using the MSDOS file naming system? Is that what JOLIET is? Could that be causing the problem or not?
I don't still have the .gz files, but I think I could get into them, although if I recall correctly there was some error or another. I'll d/l them again and see if I can find out what exactly was happening.
I'm using flashget to d/l them, I'm pretty sure that downloads in binary mode, tho I'll check to be sure anyway.
And acid: if I run the tar.gz files in Linux I get an error saying that the compression format has been violated. I can't get the exact wording at the moment because I don't have the files.
Basically it starts unpacking, then fails. Nothing actually gets uncompressed.
Yeh it would be easier to just download them but I don't know how long it's going to be before I get my comps networked - could be a few weeks.
Half-Elf - what can I rename them too? I tried renaming kernel.tar (listed as a .gz file in properties because of powerarchiver) to kerneltar, in the hope it would be known as kerneltar.gz. It was, so I tried to rename it to kernel.tar.gz then unzip it (in linux). This yielded the same results as above.
How do I enable iso-966? Any 'generic' ways? I'll go check the adaptec help anyway. As for Nero - I have an old version, and also Nero 5.5, but it doesnt run on this comp, it moans that it only works with the CDRW it was packaged with Maybe there are some 'help' files to deal with it somewhere.
If your windows machine is connected to net then download either the new version of nero, or the cdrom configuration file. Nero will work with any cd-writer and not just the one it was shipped with. I know that because I got nero with my original scsi writer and have updated twice now, and using a ide drive and same software runs.
it shouldn't matter what the filenames are called but you could rename them like the following.
Yup I've done all the editing stuff and installing from source on my original and first linux, RH7 Thanks anyway tho.
Tried writing as iso9660 but it still had to rename the files from kernel.tar.gz to kernel_tar.gz?
And when I go to linux and rename them and everything, I still get errors when I try to decompress them - format violated. For the GLX it said something about an obscolescent base 64 file, or something similar. It named a particular .so file that had been problematic. Could all these problems be due to the CD Writing??
Well it looks like it could be - when i write via nero i always set it to joiliet, ascii and ensure the greater than 8 directories and filenames greater than 255 chars is selected. if set to 8.3 mode then this is your problem, it doesn't matter about it saying not readable by msdos as you're using it for windows/linux anyway.
I have written lots through windows to cd and can pull them in via linux.
When you drag files from hdd to cd are they written with long filenames on hdd, and lose them when transfer to cd so they report as 8.3 filenames before writing - if so make the changes above first.
Another way is tell it to use the virtual recorder and save as an image on hdd, then use a program like iso buster or winimage to look at the directory structure of iso
1) if iso contains long filenames then burn it to cd and then see if kept names or not. If it doesn't then it would suggest a hardware fault.
2) if iso does not contain long filenames then it would suggest a software configuration error. Try uninstalling then reinstalling software.