You are not logged in.
@lucas - https://wiki.archlinux.org/index.php/Li … _Scheduler
@kitsuna - Are your servers up-to-date? I have no problems.
% sudo pacman -S ck-piledriver
:: There are 8 members in group ck-piledriver:
:: Repository repo-ck
1) broadcom-wl-ck-piledriver 2) linux-ck-piledriver 3) linux-ck-piledriver-headers 4) nvidia-304xx-ck-piledriver
5) nvidia-340xx-ck-piledriver 6) nvidia-ck-piledriver 7) virtualbox-ck-guest-modules-piledriver
8) virtualbox-ck-host-modules-piledriver
Enter a selection (default=all): 2 6
resolving dependencies...
looking for conflicting packages...
:: linux-ck-piledriver and linux-ck are in conflict. Remove linux-ck? [y/N] y
:: nvidia-ck-piledriver and nvidia-ck are in conflict. Remove nvidia-ck? [y/N] y
Packages (4) linux-ck-4.3.6-1 [removal] nvidia-ck-361.28-2 [removal] linux-ck-piledriver-4.3.6-1
nvidia-ck-piledriver-361.28-2
Total Download Size: 62.37 MiB
Total Installed Size: 79.59 MiB
Net Upgrade Size: -0.14 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
linux-ck-piledriver-4.3.6-1-x86_64 56.8 MiB 5.33M/s 00:11 [############################################] 100%
nvidia-ck-piledriver-361.28-2-x86_64 5.6 MiB 6.01M/s 00:01 [############################################] 100%
(2/2) checking keys in keyring [############################################] 100%
(2/2) checking package integrity [############################################] 100%
(2/2) loading package files [############################################] 100%
(2/2) checking for file conflicts [############################################] 100%
:: Processing package changes...
(1/2) removing nvidia-ck [############################################] 100%
In order to use nvidia module, reboot the system.
(2/2) removing linux-ck [############################################] 100%
(1/2) installing linux-ck-piledriver [############################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux-ck.preset: 'default'
-> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck.img
==> Starting build: 4.3.6-1-ck
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-ck.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-ck.preset: 'fallback'
-> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck-fallback.img -S autodetect
==> Starting build: 4.3.6-1-ck
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
Optional dependencies for linux-ck-piledriver
crda: to set the correct wireless channels of your country
nvidia-ck: nVidia drivers for linux-ck
modprobed-db: Keeps track of EVERY kernel module that has ever been probed - useful for those of us who make localmodconfig
(2/2) installing nvidia-ck-piledriver [############################################] 100%
In order to use nvidia module, reboot the system.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I already said in my original post that I followed what the wiki says. That's why I asked here. My question isn't how to enable it I've done it many times in the past. My question is why this time /sys/block/sda/queue/scheduler still says [cfq] is selected no matter what I do (compiling it with _BFQ_enable_="y", using the elevator=bfq parameter, etc).
bfq is there but the kernel just doesn't want to use it for whatever reason.
edit: Well I'm able to set it with echo bfq > /sys/block/sda/queue/scheduler (as root, not sudo) at least. I guess being able to set it manually is ok for now.
Last edited by lucas7_ (2016-03-25 06:33:59)
Offline
Use the tmpfile method as shown in the wiki, works for me.
Speak your mind even if your voice shakes.
Offline
Compiling it in and compiling it in and defaulting it are two different options.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Use the tmpfile method as shown in the wiki, works for me.
Yeah I tried that method once and it didn't do anything but now it works for some reason. I don't know what changed. Thanks anyways!
Offline
@all - I have updated the linux-ck family of packages for 4.4-ck1 in the AUR only at this point. I have asked AUR users to build and test. Repo to be updated shortly.
Last edited by graysky (2016-03-26 00:04:00)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
linux-ck-headers has a wrong filename. When dl'ing the snapshot, it has the name "linux-ck.tar.gz" (without -headers). Or is this meant to be that way?
Last edited by Thorsten Reinbold (2016-03-25 19:30:20)
Offline
Thorsten, it's a split package.
Offline
Yes, sorry. I've seen it now in the PKGBUILD.
Offline
@graysky: Compiled. Run's without problems together with nvidia-ck from the AUR. Thanks!
Offline
Which kernel package should I use for a Skylake Intel system? There doesn't appear to be a linux-ck-skylake. Should I use the generic one, or can I try broadwell as the most recent Intel chipset prior to Skylake?
Avatar by Ditey: https://twitter.com/phrobitey
Offline
I would use ck-generic at this point. I do not build a skylake flavor.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Take a look and available CPU instruction sets, but I think you be better off with broadwell than generic.
Offline
Correct, the patch does provide the optimized gcc options; I am not building that Arch for repo-ck at the moment.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Ah. I'll probably stick with Generic when I can get to it - at the moment I'm going to have to compile linux-mainline with a patch in order to get this hardware working properly anyway until 4.6. (And both of these will need to be done on a different system given I'm guessing an Intel Core m5 11-inch convertible tablet is not the best thing to compile a kernel on, anyway.)
Last edited by GourdCaptain (2016-03-27 19:39:27)
Avatar by Ditey: https://twitter.com/phrobitey
Offline
Sorry for no reply, ended up reinstalling my OS since it was kinda due anyway. Everything works now! well except virtual box but that is probably my fault. I was wondering, does this kernel have any of the flags it needs to use either apparmour or SElinux?
Offline
Sorry for no reply, ended up reinstalling my OS since it was kinda due anyway. Everything works now! well except virtual box but that is probably my fault. I was wondering, does this kernel have any of the flags it needs to use either apparmour or SElinux?
From what I can see in the source files, graysky follows the Archlinux kernel sources very closely. SELinux isn't in either at all and it doesn't look like AppArmor is enabled.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
Graysky do I need to uninstall the virtualbox-ck-guest/host-modules-piledriver in order to upgrade to 4.4.6-1? currently running 4.3.6-1. I get this when try to upgrade:
bill@arch-bill ~ % sudo pacman -S ck-piledriver
:: There are 6 members in group ck-piledriver:
:: Repository repo-ck
1) broadcom-wl-ck-piledriver 2) linux-ck-piledriver 3) linux-ck-piledriver-headers 4) nvidia-304xx-ck-piledriver 5) nvidia-340xx-ck-piledriver
6) nvidia-ck-piledriver
Enter a selection (default=all): 2 3
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-ck-guest-modules-piledriver: installing linux-ck-piledriver (4.4.6-1) breaks dependency 'linux-ck-piledriver<4.4'
:: virtualbox-ck-host-modules-piledriver: installing linux-ck-piledriver (4.4.6-1) breaks dependency 'linux-ck-piledriver<4.4'
∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞
Offline
@WFV - Yes, remove and build on your own until Arch upstream changes the packages back. See the note on https://wiki.archlinux.org/index.php/Re … stallation
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Thought I'd mention the newly pushed linux-ck-4.4.7 runs on the Skylake chips suffering c-state based crashes at boot without tweaking. (Got to use the generic package for now, since there's no Skylake one as of now, but it beats using 4.6rc2 and its issues.)
Avatar by Ditey: https://twitter.com/phrobitey
Offline
I added the needed support to build skylake packages now. I don't want to rebuild 4.4.7-1 but these will build on the next kernel build. Paolo has indicated that BFQ for 4.5 is ready now, and just needs to be packaged so it will likely be in 4.5.1-1 unless he drags his feet in which case it will be 4.4.8-1.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I added the needed support to build skylake packages now. I don't want to rebuild 4.4.7-1 but these will build on the next kernel build. Paolo has indicated that BFQ for 4.5 is ready now, and just needs to be packaged so it will likely be in 4.5.1-1 unless he drags his feet in which case it will be 4.4.8-1.
Cool. Thanks for the repo! (Having a working stable kernel on this means I can finally set up Virtualbox, which is hilariously unstable on 4.6rc2. To be fair, it hasn't been updated with 4.6 support, so I can't blame them, it's just funny how it literally crashes just as the Windows installer loads in the VM.)
Avatar by Ditey: https://twitter.com/phrobitey
Offline
OK. The ck-skylake group is officially support in 4.4.8-1 which is online now. Enjoy!
Last edited by graysky (2016-04-20 21:32:02)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Not like I install/use the -headers package anyway... but since it wants to build regardless, I noticed the following bizarre error.
for i in $(find . -name "Kconfig*"); do
...
The cp line fails with:
cp: failed to access '/var/aur/linux-ck/pkg/linux-ck-headers/usr/lib/modules/4.4.8-1-ck/build/./Documentation/kbuild/Kconfig.recursion-issue-01'$'\n''./Documentation/kbuild/Kconfig.recursion-issue-02'$'\n''./Documentation/kbuild/Kconfig.select-break'$'\n''./Kconfig'$'\n''./arch/Kconfig'$'\n''./arch/alpha/Kconfig'$'\n''./arch/alpha/Kconfig.debug'$'\n''./arch/arc/Kconfig'$'\n''./arch/arc/Kconfig.debug'$'\n''./arch/arc/plat-axs10x/Kconfig'$'\n''./arch/arc/plat-sim/Kconfig'$'\n''./arch/arc/plat-tb10x/Kconfig'$'\n''./arch/arm/Kconfig'$'\n''./arch/arm/Kconfig-nommu'$'\n''./arch/arm/common/Kconfig'$'\n''./arch/arm/crypto/Kconfig'$'\n''./arch/arm/firmware/Kconfig'$'\n''./arch/arm/kvm/Kconfig'$'\n''./arch/arm/mach-alpine/Kconfig'$'\n''./arch/arm/mach-asm9260/Kconfig'$'\n''./arch/arm/mach-at91/Kconfig'$'\n''./arch/arm/mach-axxia/Kconfig'$'\n''./arch/arm/mach-bcm/Kconfig'$'\n''./arch/arm/mach-berlin/Kconfig'$'\n''./arch/arm/mach-clps711x/Kconfig'$'\n''./arch/arm/mach-cns3xxx/Kconfig'$'\n''./arch/arm/mach-davinci/Kconfig'$'\n''./arch/arm/mach-digicolor/Kconfig'$'\n''./arch/arm/mach-dove/Kconfig'$'\n'<mercy_snip/>: File name too long
Closer investigation reveals that for any split PKGBUILD, the second package_*() function runs with an IFS=":"
For inscrutable reasons, makechrootpkg doesn't seem to have the same problem. But a fresh user does.
...
What on earth could this possibly mean??????????
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline