You are not logged in.
Pages: 1
Hi all,
Am thinking of trying out the nouveau driver, since I've been gaming a LOT less lately. I understand I need xf86-video-nouveau (roughly analogous to the nvidia-utils package), nouveau-firmware, and nouveau-drm (roughly analogous to the nvidia package).
Thing is, I use 3 kernels and switch between them fairly regularly. Because of this I use (and maintain) the nvidia-beta-all package on the AUR. In order to get this same level of functionality with nouveau I'd need something like nouveau-drm-all.
There is an nouveau-drm-bfs PKGBUILD in the AUR, but all that does is copy the .ko files built for 2.6.33-ARCH to a new /lib/modules/* location. I'm pretty sure that wouldn't work for all kernels (especially the -rt kernel I'm fond of using), so I'd like to ask those who are already using nouveau, do you use custom kernels? Does re-running the nouveau-drm PKGBUILD on your custom kernel work?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
i dont know about kernels 2.6.33 and older. but there was a recent discussion concerning the nouveau API and its incompatibility with old kernels.
so, if you plan on using/testing 2.6.34, the nouveau userspace wont be compatible with 2.6.33.
bear this in mind when 2.6.34 is released.
Offline
our testing nouveau-drm package is pulled from a late git snapshot. it's more recent than the code in kernel 2.6.34rc1. if you want to use nouveau-drm wit other kernels you need to build yourself corrsponding -drm-custom packages. Use our PKGBUILD as protoype. Just change the pkgname and install paths also in the install file.
Offline
our testing nouveau-drm package is pulled from a late git snapshot. it's more recent than the code in kernel 2.6.34rc1. if you want to use nouveau-drm wit other kernels you need to build yourself corrsponding -drm-custom packages. Use our PKGBUILD as protoype. Just change the pkgname and install paths also in the install file.
Thanks a lot Andy! Exactly the information I was looking for. When I write up the PKGBUILDs (busy day, maybe later) I'll be sure to post them up here + AUR.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
I don't think there's much of a need to post them -- just changing _kernver in the abs PKGBUILD should be enough.
Offline
Actually, more needs to be done, since the PKGBUILD I have in mind will build N copies of nouveau-drm .ko files if you have N kernels installed. I've never understood, for example, why nvidia-beta is written in such a way that if I use it in my custom kernel and for some reason can't boot the custom kernel, I don't have nvidia.ko in my stock -ARCH kernel so I can't even get GUI on that.
In any case, I believe I would also have to modify the Makefile, which uses `uname -r` in several places. nouveao-drm-bfs doesn't, because that PKGBUILD writer assumed that you would run it while kernel26-bfs is already installed and running. My nvidia-beta-all PKGBUILD can be used whatever kernel happens to be booted at the time.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
In any case, I believe I would also have to modify the Makefile, which uses `uname -r` in several places.
Actually only in one place, and that's only if you don't set LINUXDIR. I like the idea though, I'm going to try to get it working for nouveau-drm-git.
Offline
Pages: 1