[Solved] nvidia-beta & linux headers

Just installed nvidia-beta 310.14 & appears to be working fine.
However, when i run:
sudo pacman -R $(pacman -Qqdt)
it offers to remove linux-headers 3.6.6-1.
This seems like a very bad idea. As far as i know, they are in use:
$ uname -a
Linux archlinux 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux
Would someone kindly explain ?
Last edited by flipper T (2012-11-12 20:29:38)

It's required if you want to build kernel modules for example.
If you don't want it to show up when doing "pacman -Qqd" just install it explicity.
edit: And take a look at the nvidia-beta PKGBUILD to see why it was installed.
Last edited by loafer (2012-11-12 20:22:15)

Similar Messages

NVIDIA beta, Linux-CK & Bumblebee

Hi all,
I have been wondering about this "issue" -- for a long time I used -bumblebee versions of (lib32-)nvidia-utils and the nvidia kernel driver, modified for linux-ck, not knowing they had disappeared from AUR.
Now I'd like to be able to continue using linux-ck and use the NVIDIA beta driver along with Bumblebee. Is there any way to achieve that, apart from maintaining my own version of Bumblebee since the default depends on nvidia?
Thanks for any insight. Clay

It's required if you want to build kernel modules for example.
If you don't want it to show up when doing "pacman -Qqd" just install it explicity.
edit: And take a look at the nvidia-beta PKGBUILD to see why it was installed.
Last edited by loafer (2012-11-12 20:22:15)

[solved] nvidia: requires linux 3.2

pacman -Syu wrote:...
warning: nvidia: ignoring package upgrade (285.05.09-3 => 290.10-2)
warning: nvidia-utils: ignoring package upgrade (285.05.09-1 => 290.10-1)
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia: requires linux<3.2
I've downgraded nvidia because nvidia-290.10 doesn't work at all for me.
Q: Now, what options do I have?
To cut a long story short...
A: use pacman -Syud
Thanks again, I've learned a lot these days.
Last edited by rtfreedman (2012-01-25 16:49:42)

rtfreedman wrote:
Hm, I don't get pacman to upgrade - ignoring nvidia
I tried 'pacman -Syu --force' to no avail
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia: requires linux<3.2
I was going to upgrade the kernel, going to init 1 and compiling the nvidia.ko from source.
How do I do it?
I got the same problem, and my solution was:
1) Use pacman -U to install nvidia-290.10-2 and nvidia-utils-290.10-1 (downloaded directly from a mirror). This will force a kernel upgrade.
2) Use pacman -Syu to make entire system up-to-date
3) Use pacman -R nvidia to remove this package
4) Through ABS get the PKGBUILD of nvidia-utils version 290.10 and change the version to 285.05.09
4a) You must also change the md5sum number, for i686 it's 2d469a90abef50320f548cfa8085e3a0
4b) Use makepkg to build the package, and install both created packages (nvidia-utils and opencl-nvidia)
5) Through ABS get the PKGBUILD of nvidia version 290.10 and change the version to 285.05.09 and pkgrel from 1 to 3.
5a) You must also change the md5sum number, for i686 it's 2d469a90abef50320f548cfa8085e3a0
5b) Use makepkg to build the package, and install created package nvidia
6) Edit /etc/pacman.conf add opencl-nvidia to the ignore list
7) Reboot and enjoy
Hope this works for you too.
Ps: Just for the record, I really hate nvidia for not supporting my graphic card anymore...

The "nvidia-beta-ck" aur package and the "linux-ck" package issue?

I use the linux-ck unofficail repo to install the BFQ scheduler enabled kernel. Today it upgraded to the 3.8.8 and it updated fine but the 319 nvidia beta drivers weren't installed after the update. So I reinstalled the nvidia-beta aur package and everything was fine. Is there a way for it to automatically hook the nvidia drivers into the kernel -- say with dkms or will I need to re-install the drivers everytime the kernel updates.

I think there's an nvidia-all package in the AUR no? You can probably modify that to work with the beta package.

[SOLVED]When pacman is updating linux-headers and linux, catalyst-hook

Hello-
I wanted this to be out there on the web so that people could find it. I'm not sure if this could be considered a 'bug' for catalyst hook or for.. something, or if it is expected behavior.
I ran pacman -Suy on my system today, and ran into errors about catalyst hook failing.
Closer inspection indicated that it was trying to build based on headers of the version of linux that had just been removed, but the new linux headers hadn't been installed yet (after the hooks ran, then the linux-headers were installed)
If you see this error during an upgrade, to resolve the issue simply run mkinitcpio -p linux after the install completes.
Below you can see log/errors/progression
[dylan@shoparch ~]$ sudo pacman -Suy
:: Synchronizing package databases...
catalyst is up to date
core 105.8 KiB 175K/s 00:01 [######################] 100%
extra 1522.0 KiB 1221K/s 00:01 [######################] 100%
community 2.0 MiB 1184K/s 00:02 [######################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Packages (11): chromium-31.0.1650.63-1 grub-1:2.00.1282.g5ae5c54-1
gtk3-3.10.6-1 jasper-1.900.1-10 libpipeline-1.2.5-1
libvpx-1.3.0-1 linux-3.12.3-1 linux-headers-3.12.3-1
lua-5.2.3-1 opus-1.1-1 python2-setuptools-1.4.2-1
Total Download Size: 99.26 MiB
Total Installed Size: 314.59 MiB
Net Upgrade Size: 4.49 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
grub-1:2.00.1282.g5... 5.2 MiB 1438K/s 00:04 [######################] 100%
libpipeline-1.2.5-1... 34.9 KiB 6.82M/s 00:00 [######################] 100%
linux-3.12.3-1-x86_64 49.9 MiB 3.29M/s 00:15 [######################] 100%
linux-headers-3.12.... 5.8 MiB 1890K/s 00:03 [######################] 100%
opus-1.1-1-x86_64 175.2 KiB 1734K/s 00:00 [######################] 100%
chromium-31.0.1650.... 29.0 MiB 2.66M/s 00:11 [######################] 100%
gtk3-3.10.6-1-x86_64 7.9 MiB 2.97M/s 00:03 [######################] 100%
jasper-1.900.1-10-x... 159.8 KiB 181K/s 00:01 [######################] 100%
libvpx-1.3.0-1-x86_64 620.0 KiB 764K/s 00:01 [######################] 100%
lua-5.2.3-1-x86_64 195.9 KiB 1555K/s 00:00 [######################] 100%
python2-setuptools-... 331.9 KiB 1495K/s 00:00 [######################] 100%
(11/11) checking keys in keyring [######################] 100%
(11/11) checking package integrity [######################] 100%
(11/11) loading package files [######################] 100%
(11/11) checking for file conflicts [######################] 100%
(11/11) checking available disk space [######################] 100%
( 1/11) upgrading opus [######################] 100%
( 2/11) upgrading chromium [######################] 100%
( 3/11) upgrading grub [######################] 100%
( 4/11) upgrading gtk3 [######################] 100%
( 5/11) upgrading jasper [######################] 100%
New optional dependencies for jasper
freeglut: for jiv support [installed]
glu: for jiv support [installed]
( 6/11) upgrading libpipeline [######################] 100%
( 7/11) upgrading libvpx [######################] 100%
( 8/11) upgrading linux [######################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.12.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
-> Running build hook: [fglrx]
Building fglrx module for 3.12.3-1-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
- /usr/lib/modules/3.12.2-1-ARCH looks like unused, maybe remove it manualy?
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.12.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
-> Running build hook: [fglrx]
Building fglrx module for 3.12.3-1-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
- /usr/lib/modules/3.12.2-1-ARCH looks like unused, maybe remove it manualy?
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
( 9/11) upgrading linux-headers [######################] 100%
(10/11) upgrading lua [######################] 100%
(11/11) upgrading python2-setuptools [######################] 100%
[dylan@shoparch ~]$ less /var/log/catalyst-install.log
2013-12-08 10:51:04
Building fglrx module for 3.12.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.12.3-1-ARCH/build doesn't exist! Game over
2013-12-08 10:51:12
Building fglrx module for 3.12.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.12.3-1-ARCH/build doesn't exist! Game over
[dylan@shoparch ~]$ sudo mkinitcpio -p linux
[sudo] password for dylan:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.12.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
-> Running build hook: [fglrx]
Building fglrx module for 3.12.3-1-ARCH kernel ...
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.12.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
-> Running build hook: [fglrx]
Building fglrx module for 3.12.3-1-ARCH kernel ...
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Last edited by thenextdon13 (2014-01-01 20:21:37)

Karol-
That thread doesn't seem to be closed, and the thread it points to doesn't appear to really have a solution either, unless i'm missing something.
clfarron4;
I have this service running, but was concerned by the error message that i wouldn't have gui (and would have to drag out my laptop to do troubleshooting) upon reboot. Next time I will let it be and make sure the service works correctly
That said, I _did_ fix the distrust (or in this case non-rememberance) by running mkinitcpio -p linux. Initial post has this detail in it.
[dylan@shoparch ~]$ sudo systemctl status catalyst-hook.service
[sudo] password for dylan:
catalyst-hook.service - Catalyst's fglrx kernel' module builder
Loaded: loaded (/usr/lib/systemd/system/catalyst-hook.service; enabled)
Active: active (exited) since Sun 2013-12-08 15:50:36 PST; 25min ago
Process: 269 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 269 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/catalyst-hook.service
Dec 08 15:50:36 shoparch systemd[1]: Started Catalyst's fglrx kernel' module builder.
[dylan@shoparch ~]$

[SOLVED]linux-headers upgrade fails with PGP signature error

Whe trying to upgrade the linux kernel using:
pacman -S linux linux-headers
it fails with the following error:
(2/2) checking package integrity [#################################] 100%
error: linux: signature from "Tobias Powalowski <[email protected]>" is unknown trust
error: linux-headers: signature from "Tobias Powalowski <[email protected]>" is invalid
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
I have tried deleting /etc/pacman.d/gnupg and the recreating it with
pacman-key --init
, I have also run
pacman -Syy
to make sure the repository is up to date. I read the wiki post about time, but my ntp daemon is running, and I have confirmed that my time is exactly right.
Last edited by MikeDacre (2013-04-01 23:32:27)

Hi,
Sorry, but that doesn't help me. I can't find any reference in that post to this problem. I get a similar issue when I try to upgrade mysql:
>> sudo pacman -S mariadb libmariadbclient mariadb-clients 16:06 Mon 04-01-2013
resolving dependencies...
looking for inter-conflicts...
:: libmariadbclient and libmysqlclient are in conflict. Remove libmysqlclient? [y/N] y
:: mariadb-clients and mysql-clients are in conflict. Remove mysql-clients? [y/N] y
:: mariadb and mysql are in conflict. Remove mysql? [y/N] y
Targets (6): libmysqlclient-5.5.30-6 [removal] mysql-5.5.30-6 [removal]
mysql-clients-5.5.30-6 [removal] libmariadbclient-5.5.30-2 mariadb-5.5.30-2
mariadb-clients-5.5.30-2
Total Download Size: 16.85 MiB
Total Installed Size: 152.41 MiB
Net Upgrade Size: 28.51 MiB
Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
libmariadbclient-5.5.30-2-x86_64 6.6 MiB 1479K/s 00:05 [#################################] 100%
mariadb-clients-5.5.30-2-x86_64 871.8 KiB 421K/s 00:02 [#################################] 100%
mariadb-5.5.30-2-x86_64 9.4 MiB 440K/s 00:22 [#################################] 100%
(3/3) checking package integrity [#################################] 100%
error: libmariadbclient: key "BBE43771487328A9" is unknown
:: Import PGP key , "Bartlomiej Piotrowski <[email protected]>", created 2011-10-10? [Y/n] y
error: key "Bartlomiej Piotrowski <[email protected]>" could not be imported
error: mariadb-clients: key "BBE43771487328A9" is unknown
:: Import PGP key 487328A9, "Bartlomiej Piotrowski <[email protected]>", created 2011-10-10? [Y/n] y
(3/3) checking package integrity [#################################] 100%
error: libmariadbclient: signature from "Bartlomiej Piotrowski <[email protected]>" is unknown trust
error: mariadb-clients: signature from "Bartlomiej Piotrowski <[email protected]>" is unknown trust
error: mariadb: signature from "Bartlomiej Piotrowski <[email protected]>" is unknown trust
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

Nvidia-beta-dkms + linux-git = no CUDA

hello everyone!
I recently made the switch from the official repo-kernel to the git version (driver issues) and am now forced to use the nvidia-beta-dkms package. but now my current cuda code, which used to be working just fine does still execute, but at runtime no cuda device is detected. I have installed the latest the official cuda package. what is going wrong?
thanks in advance for any help!

I think there's an nvidia-all package in the AUR no? You can probably modify that to work with the beta package.

[SOLVED]Problem updating nvidia-beta

If I update nvidia-utils-beta it tells me I need nvidia-beta
If I try updating nvidia-beta it gives me the following error:
error: target not found: nvidia-utils-beta=275.09.07
==> ERROR: 'pacman' failed to install missing dependencies.
==> ERROR: Makepkg was unable to build nvidia-beta.
Last edited by sbfreak (2011-06-15 10:48:43)

That would take me to the stable branch would it not ? I just want to keep using nvidia-beta to have the latest driver,beta or not.

[SOLVED] linux-headers package creation

Given a full kernel sources folder, how do I recreate the whole set of files that the package linux-headers provides?
"make headers_install" provides some but not all of those.
How is the package created? Is there any info on the logic behind it?
Thanks
Last edited by evilteq (2013-10-01 10:03:49)

https://projects.archlinux.org/svntogit … ages/linux

Request for developers to include the Dell Quadro FX 3450 in their beta linux flashplayer for 10.1

request for developers to include the Dell Quadro FX 3450 in their beta linux flashplayer for 10.1. i'm guessing it wouldn't be hard to do. its the same chip that is used in the Nvidia Geforce 6800. It has NV42GL core processor. please don't leave this device behind, any acceleration that can be done to the existing flash player would definitely count, as great.
thank you

Hi it turns out that the SVN version is the most up to date which does not need to be patched as it has the right version numbers. I have created a new PKGBUILD.
# Maintainer: kso <keansum AT gmail DOT com>
pkgname=freechart-svn
pkgver=r3169
pkgrel=1
pkgdesc="Free powerful charting library based on wxWidgets."
arch=('x86_64' 'i686')
url="http://wxcode.sourceforge.net/components/freechart/"
license=('custom:"wxWindows"')
depends=('wxgtk')
makedepends=('subversion')
source=('svn+http://svn.code.sf.net/p/wxcode/code/trunk/wxCode/components/freechart/')
md5sums=('SKIP')
_svntrunk=http://svn.code.sf.net/p/wxcode/code/trunk/wxCode/components/freechart/
_svnmod=freechart
pkgver() {
cd "$_svnmod"
local ver="$(svnversion)"
printf "r%s" "${ver//[[:alpha:]]}"
build() {
cd "$srcdir"
msg "Connecting to SVN server...."
if [[ -d "$_svnmod/.svn" ]]; then
(cd "$_svnmod" && svn up -r "$pkgver")
else
svn co "$_svntrunk" --config-dir ./ -r "$pkgver" "$_svnmod"
fi
msg "SVN checkout done or server timeout"
msg "Starting build..."
rm -rf "$srcdir/$_svnmod-build"
svn export "$srcdir/$_svnmod" "$srcdir/$_svnmod-build"
cd "$srcdir/$_svnmod-build"
# BUILD HERE
./configure --prefix=/usr
make
package() {
cd "$srcdir/$_svnmod-build"
make DESTDIR="$pkgdir/" install
# install LICENSE
install -D -m644 $srcdir/$_svnmod/license.txt "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
I have uploaded onto the AUR. I have checked using namcap. Please let me know if there are any mistakes. Many thanks!

[Solved] Nvidia after kernel update

The nvidia wiki clearly states that: "Every time the kernel26 package is updated, it is a requirement to reinstall the nvidia package and rebooting afterwards. "
But my question is, why? I mean, if the module was to be recompiled, that would make sense. But what does just reinstalling the driver accomplish? In my system, pacman -Ql nvidia shows:
$ pacman -Ql nvidia
nvidia /etc/
nvidia /etc/modprobe.d/
nvidia /etc/modprobe.d/nouveau_blacklist.conf
nvidia /lib/
nvidia /lib/modules/
nvidia /lib/modules/2.6.35-ARCH/
nvidia /lib/modules/2.6.35-ARCH/kernel/
nvidia /lib/modules/2.6.35-ARCH/kernel/drivers/
nvidia /lib/modules/2.6.35-ARCH/kernel/drivers/video/
nvidia /lib/modules/2.6.35-ARCH/kernel/drivers/video/nvidia.ko
From what I've read, I think the kernel update process copies the compiled modules into the proper folder (inside /lib) named by the kernel version. Should this not be the case with nvidia? If it is not, then is this why the reinstall is needed?
Thanks in advance (and my apologies if I've glossed over something that's patently obvious --- while I've searched for the answer before posting, I am still quite the novice at tinkering with the kernel)
EDIT: just after posting I've realized that maybe this post belongs in "Kernel and Hardware Issues" subforum. But the truth is this isn't really an "issue"... it's more a question from, well, a newbie :-)
Last edited by gauthma (2010-09-28 21:53:04)

gauthma wrote:
Thank you for the feedback.
ngoonee wrote:Of course, if you're using nvidia-beta or some other AUR nvidia driver, you need to reinstall it.
Running the risk of asking what might be obvious to some, why?
The driver speaks to the kernel. When the kernel updates, the language used might have changed in various ways. Since nvidia is closed-source, its not always obvious whether what has changed affects it. The same applies to xorg-server, when it updates you should recompile your nvidia driver. Its SOMETIMES not needed, but when it is, would you rather be solving it from the tty?
quathma wrote:
ngoonee wrote:That's what the wiki is referring to. Even if the kernel major version has not updated (for example 2.6.35.5 to 2.6.35.6 is only a minor version bump) the driver may need to be recompiled. Safer to just do it everytime and restart the machine.
Now I'm confused. Are you saying that the safest approach is to recompile and (re)install the nvidia module after each kernel update? And does this only apply to modules from beta & AUR, or [extra] as well? And shouldn't all this issue of recompiling modules also apply to every other module installed in the system?
Yes that's the safest approach. [extra] is taken care of by the devs, the simple way is to assume they'll bump it if needed (and you don't need to do anything).
The same thing applies to almost any kernel module (AFAIK). It applies to virtualbox's modules, for sure, as well as phc-intel (the only other 2 external modules I use). Most kernel modules are actually compiled in to the kernel26 package anyway, so its not very many. I just automatically recompile the ones I use whenever I notice a kernel/xorg update.

Pacman -Qdt and linux-headers

I was looking to clean up my system after installing a bunch of packages, so I ran pacman -Qdt and it spit this out:
pacman -Qdt wrote:[tyler@arch etc]$ pacman -Qdt
compiz-bcop 0.8.8-2
compizconfig-python 0.8.4-4
git 1.8.1.2-1
jshon 20121122-1
libidl2 0.8.14-2
libwnck 2.30.7-1
linux-headers 3.7.5-1
python-distribute 0.6.34-1
I got curious when I saw the linux-headers 3.7.5-1, so I ran uname -a to see my kernel and it spit out:
uname -a wrote:3.7.5-1-ARCH
My questions are, why is that in the cleanup list if it is the version I use? Will removing it be harmful? Or was it just installed to compile the kernel?
Last edited by defkult (2013-02-05 16:01:16)

anonymous_user wrote:linux-headers is not required by the kernel. It is used when building a module such as nvidia, catalyst, virtualbox-modules, etc.
So I should leave it installed for later updates, if I don't want to have to re-download it every time something updates. Correct?

[Solved] Nvidia-ck question

Hi.
I'm currently running the linux-ck, and nvidia-ck, packages from Graysky's repo.
When I go to update my total system, I get two instances of nvidia to upgrade.
Is there any way to remove the dependencies on the opencl-nvidia package, and just use the nvidia-ck?
EDIT:
Upgraded around the one package that refuse to uninstall, re-logged in, and successfully uninstalled said package.
Last edited by *nixer (2011-11-24 00:17:52)

Apologies...
What I originally had going was the default Arch kernel, and the non-free Nvidia drivers installed. I did some reading on the BF scheduler, and decide your prebuilt kernel, headers, and nvidia packages would be the most optimal. My PC is too old to compile a kernel every update...
When I was comfortable with the results, I uninstalled the linux, and linux-headers. If I tried to uninstall the opncl-nvidia package, all of my nvidia dependant packages prevented it, and this was despite myself already running your ck kernel+nvidia setup.
I'm not sure why, but after I manually upgraded all the packages shown by 'pacman -Syu' with the exception of opencl-nvidia, I was then able to uninstall it just fine after a logout/login.

[SOLVED] Change from linux-lts to latest linux

Hello.
I want to change from the lts kernel to the latest kernel yet, when I type
# pacman -S linux linux-headers
It seems to install the latest kernel but when I reboot and I type:
$ uname -a
I get this:
Linux oblivion 3.14.29-1-lts #1 SMP Fri Jan 16 20:57:17 CET 2015 x86_64 GNU/Linux
Wich means I'm still using the lts kernel, how can I start using the latest kernel? I don't need the lts anymore.
Last edited by d15d18a (2015-01-22 16:11:51)

Trilby wrote:You have to change your bootloader to point to the regular kernel. You can have many kernels installed, the bootloader determines which is booted.
That's right! Changing the contents of the syslinux.cfg file solved this issue; I've also created an entry for the LTS kernel down that one, just in case I have hardware problems again.
Thank you very much!
Last edited by d15d18a (2015-01-22 16:12:34)

Atheros ethernet, compat-drivers & linux-headers version mismatch

I just installed a new mobo (GA-H77M-D3H) which has an atheros ar8161 ethernet chip.
The old mobo had a realtek ethernet chip which worked fine (but the RAM didn't).
Arch (and other distros) doesn't have drivers for the new atheros one (there's a bit of a fight over its support in the linux kernel).
I see many posts on how to fix this, but the solution isn't working for me yet.
The solution seems to be to use the compat-drivers package. However, I'm having trouble building it (I'm not that great at solving these things yet).
I am downloading compat-drivers from: https://www.kernel.org/pub/linux/kernel … ts/stable/
(From the unzipped source, I am using ./script/driver-select alx)
The problem is compat-drivers needs linux headers for my current kernel, 3.7.10-1-ARCH, but the version on the arch download page is Arch is 3.8.3-2 and I don't know where to find an earlier version.
The download link I use for linux-headers is: https://www.archlinux.org/packages/core … x-headers/
Note: I'm downloading on another computer as the one with no ethernet has no ethernet.
"uname -r" gives me:
3.7.10-1-ARCH.
And I can't update without ethernet.
The build error message is:
make: *** /lib/modules/3.7.10-1-ARCH/build: No such file or directory. Stop.
So, my questions are:
1. Is there anywhere I can get linux-headers for 3.7.10-1-ARCH? (and would this be the right way?)
2. Can I force make to pretend I'm using 3.8.3-2? would this have any chance of success?
3. Is there another way to fix this?
Thanks.
PS: It took me about 10 minutes to get through the forum register "captcha" due to bugs and my laptop not having accurate US time... I see lots of complaints about it online, so please fix (a regular captcha is far harder to spam).

This works for me:
1. Get latest kernel 3.8.3-2
2. wget https://www.kernel.org/pub/linux/kernel … -u.tar.bz2
3. Use https://backports.wiki.kernel.org/index … at-drivers documentation, but simply:
- tar jxvf compat-drivers-2013-03-15-u.tar.bz2
-./scripts/driver-select alx
- make
- make install
- modprobe alx
verify with lsmod | grep -i alx, if module is loaded.
Note:
compat-drivers-3.8.3-2-snpu.tar.bz2 didn't work for me with latest kernel 3.8.3-2.

[Solved] nvidia-beta & linux headers

Similar Messages

Maybe you are looking for