omg! Con Kolivas is back!

eDio · 2009-12-16 14:18:35

I'm completely not a Linux guru, but BFS (or CK, as I understand, it is the same, right?) is known to improve overall performance and so on and so on... I've decided to try it.

I've installed kernel, edited grub's menu.lst. The system can boot now , but can't find modules for my soundcard (ICE1724, ESI Juli@) and for nvidia card (GT8600). What I should do to fix this?

TNX.

bangkok_manouel · 2009-12-16 14:33:27

eDio wrote:

I'm completely not a Linux guru, but BFS (or CK, as I understand, it is the same, right?)

actually it's not. bfs is part of the -ck patchset. to see the full patches list of -ck, please check the previous page.

eDio wrote:

I've installed kernel, edited grub's menu.lst. The system can boot now , but can't find modules for my soundcard (ICE1724, ESI Juli@) and for nvidia card (GT8600). What I should do to fix this?

for nvidia, you'll have to rebuild your drivers against the -ck kernel (check AUR for some examples if you're not familiar with this). for the other stuff, it looks like a kernel config problem, if you're not too familiar with this, just use arch stock kernel config, that should do it.

Ranguvar · 2009-12-16 18:17:29

You can use the nvidia-all or nvidia-beta-all AUR package.

Procyon · 2009-12-18 17:36:09

It's working great for me. I think CPU and RAM(?) usage is a lot lower. The CPU is colder, it even hit 38C just now. However, I don't notice any performance gains, it doesn't feel snappier and such. Maybe it will hit me when I switch back. I was also using the CFS tweaks mentioned above though, which helped quite a bit from regular CFS.

1LordAnubis · 2009-12-19 16:45:23

Anyone know how to get the nvidia-173xx working? I keep getting

anubis@Thorin ~/devel/abs/nvidia-173xx/ $ makepkg -c -i
==> Making package: nvidia-173xx-ck 173.14.22-1 i686 (Fri Dec 18 23:35:51 EST 2009)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Downloading NVIDIA-Linux-x86-173.14.22-pkg0.run...
--2009-12-18 23:35:52--  http://download.nvidia.com/XFree86/Linux-x86/173.14.22/NVIDIA-Linux-x86-173.14.22-pkg0.run
Resolving download.nvidia.com... 207.138.133.238
Connecting to download.nvidia.com|207.138.133.238|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://http.download.nvidia.com/XFree86/Linux-x86/173.14.22/NVIDIA-Linux-x86-173.14.22-pkg0.run [following]
--2009-12-18 23:35:52--  http://http.download.nvidia.com/XFree86/Linux-x86/173.14.22/NVIDIA-Linux-x86-173.14.22-pkg0.run
Resolving http.download.nvidia.com... 204.245.162.25, 204.245.162.19
Connecting to http.download.nvidia.com|204.245.162.25|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12262547 (12M) [application/octet-stream]
Saving to: "NVIDIA-Linux-x86-173.14.22-pkg0.run.part"

100%[======================================>] 12,262,547  1.19M/s   in 11s     

2009-12-18 23:36:03 (1.11 MB/s) - "NVIDIA-Linux-x86-173.14.22-pkg0.run.part" saved [12262547/12262547]

==> Validating source files with sha256sums...
    NVIDIA-Linux-x86-173.14.22-pkg0.run ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
Creating directory NVIDIA-Linux-x86-173.14.22-pkg0
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86 173.14.22....................................................................................................................................
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1
==> ERROR: Build Failed.
    Aborting...

And is this normal?
anubis@Thorin ~/ $ ls /usr/src/linux-2.6.32-ck/
vmlinux

bangkok_manouel · 2009-12-19 16:52:30

just to be sure, did you modify nvidia.install and PKGBUILD to be built againt the -ck kernel version?

edit: didn't see that

And is this normal?
anubis@Thorin ~/ $ ls /usr/src/linux-2.6.32-ck/
vmlinux

I'm not using the AUR PKGBUILD but there's obviously something fishy with it, as you can see in this thread's previous pages. IIRC there's also a workaround, just check previous posts in this very same thread.

Last edited by bangkok_manouel (2009-12-19 16:57:18)

eldragon · 2009-12-19 17:15:23

what kernel PKGBUILD are you using? if you modified the one in core, remember to create the headers package too (and install it)

milomouse · 2009-12-19 23:09:59

Just a quick question before I try this: Right now I have kernel26-bfs, kernel26-headers, kernel26-firmware and kernel-headers installed. Both kernel26-headers and kernel26-firmware were installed through kernel26-bfs. Now, if I install kernel26-ck it will install kernel26-ck and kernel26-ck-headers. I'm no veteran at all this but are all these headers necessary? glibc wants the regular kernel-headers so I couldn't uninstall that even without having vanilla kernel anymore, but this will make 3 header packages in total. I guess they're required for each differnet kernel?

Also, do I need to build firmware for kernel26-ck as well, because if this works I'll be uninstalling the regular kernel26-bfs since ck includes it already.

Sorry for all the questions.

ngoonee · 2009-12-20 23:18:11

Please differentiate packages and files. With 2.6.32 the stock Arch kernel has had the headers split out, which is stuff that goes into /usr/src/kernel26-ARCH. Prior to that those files were just installed within the kernel26 package. Most custom kernels still do that (kernel26-ice for example). However some newer packages like kernel26-ck follow the kernel26 PKGBUILD method, so they have kernel26-ck-headers, which installs to /usr/src/kernel26-ck. You need those packages to build any custom modules, like nvidia or phc or virtualbox modules.

Zariel · 2009-12-20 23:26:36

Running 1000hz is recommended, even with a quad core? Shouldn't 4x250 suffice?

jac · 2009-12-21 00:24:19

Zariel wrote:

Running 1000hz is recommended, even with a quad core? Shouldn't 4x250 suffice?

Quoting from Ranguvar on the kernel26-ck AUR page:

Ranguvar wrote:

@mechmg93: Doesn't matter nearly at all, because most people should be using dynamic HZ (CONFIG_NO_HZ=y, default in main Arch and this config), but as far as I can tell, make it 1,000Hz.
I heard that it's per-core, as in, a quad-core user like me should set 250Hz for 1,000Hz behavior, but I asked the Linux devs and even they aren't sure / don't care because of CONFIF_NO_HZ

I set it to 1000Hz, but I have no idea

eldragon · 2009-12-21 03:29:20

ngoonee wrote:

Please differentiate packages and files. With 2.6.32 the stock Arch kernel has had the headers split out, which is stuff that goes into /usr/src/kernel26-ARCH. Prior to that those files were just installed within the kernel26 package. Most custom kernels still do that (kernel26-ice for example). However some newer packages like kernel26-ck follow the kernel26 PKGBUILD method, so they have kernel26-ck-headers, which installs to /usr/src/kernel26-ck. You need those packages to build any custom modules, like nvidia or phc or virtualbox modules.

if you are not going to have the stock kernel installed, just use abs, include the patches where appropriate, and leave the kernel name alone

i strongly advice against it since one small mishap and you are out of your system

milomouse · 2009-12-21 13:03:29

eldragon wrote:

ngoonee wrote:
Please differentiate packages and files. With 2.6.32 the stock Arch kernel has had the headers split out, which is stuff that goes into /usr/src/kernel26-ARCH. Prior to that those files were just installed within the kernel26 package. Most custom kernels still do that (kernel26-ice for example). However some newer packages like kernel26-ck follow the kernel26 PKGBUILD method, so they have kernel26-ck-headers, which installs to /usr/src/kernel26-ck. You need those packages to build any custom modules, like nvidia or phc or virtualbox modules.
if you are not going to have the stock kernel installed, just use abs, include the patches where appropriate, and leave the kernel name alone
i strongly advice against it since one small mishap and you are out of your system

So, I could technically uninstall the stock kernel headers and re-build nvidia (broadcom, etc) against kernel26-bfs{-ck}-headers? I still have the stock kernel-headers in my /var in case I need to reinstall it. If not that's fine, I just don't like having packages I don't require anymore.

eldragon · 2009-12-21 13:45:36

milomouse wrote:

eldragon wrote:
ngoonee wrote:
Please differentiate packages and files. With 2.6.32 the stock Arch kernel has had the headers split out, which is stuff that goes into /usr/src/kernel26-ARCH. Prior to that those files were just installed within the kernel26 package. Most custom kernels still do that (kernel26-ice for example). However some newer packages like kernel26-ck follow the kernel26 PKGBUILD method, so they have kernel26-ck-headers, which installs to /usr/src/kernel26-ck. You need those packages to build any custom modules, like nvidia or phc or virtualbox modules.
if you are not going to have the stock kernel installed, just use abs, include the patches where appropriate, and leave the kernel name alone
i strongly advice against it since one small mishap and you are out of your system
So, I could technically uninstall the stock kernel headers and re-build nvidia (broadcom, etc) against kernel26-bfs{-ck}-headers? I still have the stock kernel-headers in my /var in case I need to reinstall it. If not that's fine, I just don't like having packages I don't require anymore.

well, yes, when you build an external module, its built against the running kernel, and thus, against the kernel's headers.

the stock headers are for the stock kernel.

you need a header folder under /usr/src for each installed kernel if you plan to build modules for those kernels.

ngoonee · 2009-12-21 23:29:48

You shouldn't uninstall the stock kernel headers. If kernel26-bfs/ck-headers conflicts with stock kernel headers, they need to be fixed. I have 3 kernels (kernel26, kernel26-ice, kernel26-rt-ice) with their respective separate headers installed, and I can build modules separately for all of them (check out nvidia-beta-all for an example).

milomouse · 2009-12-22 14:40:04

ngoonee wrote:

You shouldn't uninstall the stock kernel headers. If kernel26-bfs/ck-headers conflicts with stock kernel headers, they need to be fixed. I have 3 kernels (kernel26, kernel26-ice, kernel26-rt-ice) with their respective separate headers installed, and I can build modules separately for all of them (check out nvidia-beta-all for an example).

They don't conflict AFAIK. I just find it hard to imagine I >>need<< the vanilla kernel-headers even if I don't have vanilla kernel26 installed. I'd like to think my ck-{bfs-etc,-}headers are useful too. If I build everything against them why do I still need vanilla kernel-headers? Shouldn't they contain basically the same stuff? I'm really curious.

1LordAnubis · 2009-12-22 16:46:17

So just how do you get kernel26-ck-headers ?
The kernel installs fine, but no headers... am I missing something?

milomouse · 2009-12-22 16:51:28

pkgname=('kernel26-ck') # Build stock -ck kernel
# pkgname=('kernel26-ck' 'kernel26-ck-headers') # uncomment this and comment the above

Did you do this?

#pkgname=('kernel26-ck') # Build stock -ck kernel
pkgname=('kernel26-ck' 'kernel26-ck-headers') # uncomment this and comment the above

It should build the headers this way if you comment out the stock kernel and uncomment the kernel and kernel headers line.

1LordAnubis · 2009-12-22 17:10:33

milomouse wrote:

pkgname=('kernel26-ck') # Build stock -ck kernel
# pkgname=('kernel26-ck' 'kernel26-ck-headers') # uncomment this and comment the above
Did you do this?
#pkgname=('kernel26-ck') # Build stock -ck kernel
pkgname=('kernel26-ck' 'kernel26-ck-headers') # uncomment this and comment the above
It should build the headers this way if you comment out the stock kernel and uncomment the kernel and kernel headers line.

I did that, but I still get this:

anubis@Thorin ~/ $ ls /usr/src/linux-2.6.32-ck/
vmlinux

ngoonee · 2009-12-23 00:17:40

milomouse wrote:

ngoonee wrote:
You shouldn't uninstall the stock kernel headers. If kernel26-bfs/ck-headers conflicts with stock kernel headers, they need to be fixed. I have 3 kernels (kernel26, kernel26-ice, kernel26-rt-ice) with their respective separate headers installed, and I can build modules separately for all of them (check out nvidia-beta-all for an example).
They don't conflict AFAIK. I just find it hard to imagine I >>need<< the vanilla kernel-headers even if I don't have vanilla kernel26 installed. I'd like to think my ck-{bfs-etc,-}headers are useful too. If I build everything against them why do I still need vanilla kernel-headers? Shouldn't they contain basically the same stuff? I'm really curious.

kernel-headers and kernel26-headers are different. And you'd always want the kernel26 in any case as a fallback in case you screw up your kernel26-ck. You'd also need kernel26-headers so you can have your modules there (nvidia/fglrx primarily, else it wouldn't be much good as a fallback).

And basically the same stuff yes. To 'share' headers you'd have to modify the install locations of the modules themselves, as well as where they search for their headers. May not work, YMMV. The package is small, just install it. You use more disk memory just installing any GUI app, almost.

rebegin · 2009-12-23 09:40:26

1LordAnubis wrote:

milomouse wrote:
pkgname=('kernel26-ck') # Build stock -ck kernel
# pkgname=('kernel26-ck' 'kernel26-ck-headers') # uncomment this and comment the above
Did you do this?
#pkgname=('kernel26-ck') # Build stock -ck kernel
pkgname=('kernel26-ck' 'kernel26-ck-headers') # uncomment this and comment the above
It should build the headers this way if you comment out the stock kernel and uncomment the kernel and kernel headers line.
I did that, but I still get this:
anubis@Thorin ~/ $ ls /usr/src/linux-2.6.32-ck/
vmlinux

building it with yaourt didn't install both packages here either....try building it with makepkg and check if you get kernel26-ck and also kernel26-ck-headers packages.

ngoonee · 2009-12-23 23:23:13

rebegin wrote:

building it with yaourt didn't install both packages here either....try building it with makepkg and check if you get kernel26-ck and also kernel26-ck-headers packages.

Building with yaourt calls makepkg... yaourt is a helper, not a separate app.

rebegin · 2009-12-28 12:30:09

ngoonee wrote:

rebegin wrote:
building it with yaourt didn't install both packages here either....try building it with makepkg and check if you get kernel26-ck and also kernel26-ck-headers packages.
Building with yaourt calls makepkg... yaourt is a helper, not a separate app.

of course, i only suggested building it manualy with makepkg as on my laptop upgrading the package kernel26-ck with yaourt didn't install the newly added kernel26-ck-headers and as finishing the installation, nothing has left in the /tmp/yaourt-tmp-... folder. so i had to run makepkg and install packages manually. i'm sorry for the misunderstanding, english is not my native language.

bangkok_manouel · 2009-12-31 10:46:30

2.6.32-ck2 uploaded.

Primoz · 2009-12-31 10:48:08

After so much trouble I'm saddened to say that my ck kernel is worse than normal arch kernel...
I don't know what exactly it is, I suspect the scheduler or something. As it caches more memory and it also uses more CPU...
But I think this was done by me in kernel configuration...

Arch Linux

#226 2009-12-16 14:18:35

Re: omg! Con Kolivas is back!

#227 2009-12-16 14:33:27

Re: omg! Con Kolivas is back!

#228 2009-12-16 18:17:29

Re: omg! Con Kolivas is back!

#229 2009-12-18 17:36:09

Re: omg! Con Kolivas is back!

#230 2009-12-19 16:45:23

Re: omg! Con Kolivas is back!

#231 2009-12-19 16:52:30

Re: omg! Con Kolivas is back!

#232 2009-12-19 17:15:23

Re: omg! Con Kolivas is back!

#233 2009-12-19 23:09:59

Re: omg! Con Kolivas is back!

#234 2009-12-20 23:18:11

Re: omg! Con Kolivas is back!

#235 2009-12-20 23:26:36

Re: omg! Con Kolivas is back!

#236 2009-12-21 00:24:19

Re: omg! Con Kolivas is back!

#237 2009-12-21 03:29:20

Re: omg! Con Kolivas is back!

#238 2009-12-21 13:03:29

Re: omg! Con Kolivas is back!

#239 2009-12-21 13:45:36

Re: omg! Con Kolivas is back!

#240 2009-12-21 23:29:48

Re: omg! Con Kolivas is back!

#241 2009-12-22 14:40:04

Re: omg! Con Kolivas is back!

#242 2009-12-22 16:46:17

Re: omg! Con Kolivas is back!

#243 2009-12-22 16:51:28

Re: omg! Con Kolivas is back!

#244 2009-12-22 17:10:33

Re: omg! Con Kolivas is back!

#245 2009-12-23 00:17:40

Re: omg! Con Kolivas is back!

#246 2009-12-23 09:40:26

Re: omg! Con Kolivas is back!

#247 2009-12-23 23:23:13

Re: omg! Con Kolivas is back!

#248 2009-12-28 12:30:09

Re: omg! Con Kolivas is back!

#249 2009-12-31 10:46:30

Re: omg! Con Kolivas is back!

#250 2009-12-31 10:48:08

Re: omg! Con Kolivas is back!

Board footer