proprietary gfx drivers packages

General talk about packaging procedures and packages.
User avatar
skywaker
Posts: 3
Joined: 17. Sep 2009, 12:41
Contact:

proprietary gfx drivers packages

Post by skywaker »

Hi. How will be do a propiertary drivers for graphics cards like radeon hd or nvidia in salix?
Last edited by gapan on 19. Sep 2009, 09:23, edited 1 time in total.
Reason: title typo
User avatar
thenktor
Salix Wizard
Posts: 2426
Joined: 6. Jun 2009, 14:47
Location: Franconia
Contact:

Re: propiertary gfx drivers packages

Post by thenktor »

Hmm, at least for me using the nvidia install script is more straight forward as using packages for this, because everytime a new kernel is in the repos a new driver package has to be done simultaneously.
Image
burnCDDA (burns audio CDs)
geBIERt (German beer blog)
User avatar
skywaker
Posts: 3
Joined: 17. Sep 2009, 12:41
Contact:

Re: propiertary gfx drivers packages

Post by skywaker »

i only ask becouse i am zenwalk user and i allways for my radeonhd use propertary driver.. i am not going to zenwalk official forum i only use zenwalk and what i dont know i find on the net but now i read about Salix and is interest for me.
User avatar
thenktor
Salix Wizard
Posts: 2426
Joined: 6. Jun 2009, 14:47
Location: Franconia
Contact:

Re: propiertary gfx drivers packages

Post by thenktor »

I have no idea about radeonhd drivers :roll:
Image
burnCDDA (burns audio CDs)
geBIERt (German beer blog)
User avatar
JRD
Salix Warrior
Posts: 950
Joined: 7. Jun 2009, 22:52
Location: Lyon, France

Re: propiertary gfx drivers packages

Post by JRD »

I made a ZENBUILD that pick up the last nvidia driver from the website automatically and build a new package uppon it.
I prefer packages.
I can adapt the ZENBUILD to a SLKBUILD.

It could be a good idea to install a nvidia meta-package that add an entry in a menu (and a script in /usr/sbin).
When you click on it (or launch the script), it build the package and install (or update) it.
What do you think of that ? It's inspired of how the media codecs are done in Salix.
Image
User avatar
Duncan_Idaho
Posts: 216
Joined: 19. Sep 2009, 01:43
Location: Sietch Tabr, Planet Arrakis

Re: propiertary gfx drivers packages

Post by Duncan_Idaho »

JRD wrote: It could be a good idea to install a nvidia meta-package that add an entry in a menu (and a script in /usr/sbin).
When you click on it (or launch the script), it build the package and install (or update) it.
What do you think of that ? It's inspired of how the media codecs are done in Salix.
hi, it would be great if this could be done for the ati catalyst driver too :mrgreen:
User avatar
laprjns
Salix Warrior
Posts: 1105
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: propiertary gfx drivers packages

Post by laprjns »

JRD wrote:... When you click on it (or launch the script), it build the package and install (or update) it.
I believe this will require the kernel-source package to installed on the systems.
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
User avatar
gapan
Salix Wizard
Posts: 6241
Joined: 6. Jun 2009, 17:40

Re: propiertary gfx drivers packages

Post by gapan »

laprjns wrote:I believe this will require the kernel-source package to installed on the systems.
Correct!
Image
Image
User avatar
JRD
Salix Warrior
Posts: 950
Joined: 7. Jun 2009, 22:52
Location: Lyon, France

Re: proprietary gfx drivers packages

Post by JRD »

Yes for now, the kernel-source package is required.
But only a few includes files are required in fact, not the "source" files. kernel-headers should be enought, but for a bit of time, the slackware kernel-headers package is bad done. Same for VirtualBox drivers.
Maybe we must check what is missing from kernel-headers and correct it ?
Image
User avatar
laprjns
Salix Warrior
Posts: 1105
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: proprietary gfx drivers packages

Post by laprjns »

JRD wrote:Maybe we must check what is missing from kernel-headers and correct it ?
Depending on the kernel version, it seems to be a moving target. For the 2.6.28 kernel, I found this:
http://support.zenwalk.org/viewtopic.php?f=7&t=21680; which eventually got fixed in one of the later version of 2.6.30. For the 2.6.30 kenrel, i found this: http://support.zenwalk.org/viewtopic.php?f=42&t=24487. Since this is posted in the developers forum, gapan probabily doesn't have access so I copy it here.
laprjns from ZW forum wrote: Although the problem in this thread got fixed, it came back on the 2.6.29 kernel and continues on the 2.6.30 kernel. These kernels with just the kernelheader package installed, do not allow compiling of drivers for VirtualBox and NVIDIA. The kernelsource package; a package that is very large and takes a long time to download and install, is required.
Since this doesn't seem to be the case for other distributions I have looked into what needs to be added to the header package to allow the compiling of these drivers. I found that adding /trace directory and it's 15 files found in the /usr/src/linux-2.6.30.5/include/ directory of the kernelsource package to the kernelheader directory tree fixed the problem. Just adding this one directory , ~ 18kb in size, allows the compiling of these drivers without installing the kernel source package.
Rich
I never could figure out what was missing in the 2.6.29 kernel; it wasn't really around that long on ZW. I did take a quick look at the Salix 2.6.29 kernel and my impression was that there was a lot more missing than just a link and /or a directory.
Rich
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
Post Reply