You are not logged in.
@enihcam - Please report this to Palolo.
Where can I find Palolo?
Offline
here http://ck-hack.blogspot.co.uk/
ps i had the same issue & can confirm that removing the elevator from the kernal line allows successful boot
If I'm curt with you it's because time is a factor. I think fast, I talk fast and I need you guys to act fast if you wanna get out of this. So, pretty please... with sugar on top. Clean the [censored] car. -The Wolf
Offline
graysky wrote:@enihcam - Please report this to Palolo.
Where can I find Palolo?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
here http://ck-hack.blogspot.co.uk/
ps i had the same issue & can confirm that removing the elevator from the kernal line allows successful boot
The issue has already been reported:
https://groups.google.com/forum/#!topic … 4Lg5INzQ-k
@graysky, here's the patch:
https://groups.google.com/group/bfq-ios … r=0&view=1
Last edited by enihcam (2013-08-21 09:40:51)
Offline
I had the same problem with failure to boot and removal of the elevator worked, but I believe performance suffers as a result. I downloaded the patch and attempted to apply but the patch command halted at “line 15” due to lack of a target file. I searched for *bfq* files but while several were listed the “bfq-iosched.c” file contained in the patch did not show up. Since I use your Repo-ck packages I assume the patch is applied to the kernel before you publish it which I think explains why it is not on my computer. Am I correct in assuming that you will issue a new package with the patch applied and the elevator=bfq can then be added back to the kernel parameters?
Offline
czubek, read this
If I'm curt with you it's because time is a factor. I think fast, I talk fast and I need you guys to act fast if you wanna get out of this. So, pretty please... with sugar on top. Clean the [censored] car. -The Wolf
Offline
@ flipper. Thanks flipper. I just caught that thread and was about to edit my post.
Upgraded ck, added elevator and all is golden. Thanks graysky.
Last edited by czubek (2013-08-22 21:04:32)
Offline
There seems to be a file conflict between the official nvidia-304xx package and nvidia-304xx-ck.
Packages (6):
Name Old Version New Version Net Change
core/gettext 0.18.3-1 0.18.3.1-1 0.01 MiB
extra/git 1.8.3.4-1 1.8.4-1 0.80 MiB
core/linux 3.10.7-1 3.10.9-1 0.00 MiB
extra/nvidia-304xx 304.88-16 304.108-2 0.02 MiB
repo-ck/nvidia-304xx-ck-kx 304.88-10 304.108-1 0.01 MiB
extra/nvidia-304xx-utils 304.88-1 304.108-1 0.07 MiB
Total Installed Size: 174.03 MiB
Net Upgrade Size: 0.91 MiB
:: Proceed with installation? [Y/n] y
(6/6) checking keys in keyring [##########################################################] 100%
(6/6) checking package integrity [##########################################################] 100%
(6/6) loading package files [##########################################################] 100%
(6/6) checking for file conflicts [##########################################################] 100%
error: failed to commit transaction (conflicting files)
/usr/share/licenses/nvidia-304xx/LICENSE exists in both 'nvidia-304xx' and 'nvidia-304xx-ck-kx'
Errors occurred, no packages were upgraded.
Never had this "problem" in the past. I could remove the kernel module for the official kernel since I don't use it but it's not a clean solution.
Looks like nvidia-304xx is being dropped into AUR, anyway. If repo-ck would still maintain it for the ck kernel that would be awesome.
Last edited by blackout23 (2013-08-24 21:26:30)
Offline
There seems to be a file conflict between the official nvidia-304xx package and nvidia-304xx-ck.
...
Entirely my fault and fixed in 304.108-2. Expect the repo to have the updated pkgs in <5 min. Thanks for pointing this out.
EDIT: Repo refreshed. All should be well.
Last edited by graysky (2013-08-24 23:58:49)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Awesome, thanks! It would be wonderful if you'd continue to support 304xx. I don't think there will be a lot of updates in the future.
Last edited by blackout23 (2013-08-25 00:06:10)
Offline
No plans on changing the currently supported packages. I actually have two only machines that use the 304 series.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
$ kde4-config -v
Qt: 4.8.5
KDE Development Platform: 4.11.00
kde4-config: 1.0
$ uname -r
3.10.9-1-ck
grep "model name" /proc/cpuinfo
model name : AMD Phenom(tm) II X4 965 Processor
model name : AMD Phenom(tm) II X4 965 Processor
model name : AMD Phenom(tm) II X4 965 Processor
model name : AMD Phenom(tm) II X4 965 Processor
$ sudo cpupower -c all info
System's multi core scheduler setting: not supported
System's thread sibling scheduler setting: not supported
System does not support Intel's performance bias setting
analyzing CPU 0:
analyzing CPU 1:
analyzing CPU 2:
analyzing CPU 3:
$ zgrep SCHED_MC /proc/config.gz
CONFIG_SCHED_MC=y
is it okay that "System's multi core scheduler setting: not supported" ?
Offline
is it okay that "System's multi core scheduler setting: not supported" ?
No idea based on the output you posted. On my i7-k3770:
*htop shows 8 cores
*dmesg shows 8 cores:
% dmesg | grep CPUs
[ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=8.
[ 0.282438] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.403461] Brought up 8 CPUs
If I look at the oldest multicore system I have, an E5200:
*htop shows 2 cores
*dmesg shows 2 cores:
% dmesg | grep CPUs
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.089948] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.089960] Brought up 2 CPUs
Now if I look at an ancient machine running a single core processor:
*htop shows 1 core
*dmesg shows 1 core:
% dmesg | grep CPUs
[ 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.
[ 0.040014] Brought up 1 CPUs
Last edited by graysky (2013-08-25 15:17:47)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
#dmesg | grep CPUs
[ 0.000000] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.179963] Brought up 4 CPUs
[ 1.027611] ledtrig-cpu: registered to indicate activity on CPUs
Offline
@PG - I would say your i686 kernel has detected 4 cores.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
@graysky, I got x86-64 kernel.
Offline
@graysky, I got x86-64 kernel.
I assumed i686 based on your 8 CPUs below (you must have custom build and limited them to 8 in the nconfig). No matter. Your kernel is seeing all your cores.
#dmesg | grep CPUs [ 0.000000] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Can someone buy graysky an ATI/AMD graphics card so he can provide catalyst-ck?
Offline
Can someone buy graysky an ATI/AMD graphics card so he can provide catalyst-ck?
Catalyst is not as straight forward as the Nvidia stuff. AMD is pretty bad at keeping up with the Xorg updates, which is why on the wiki page, the recommended course of action is to use the unofficial repos for old Xorg versions. So if graysky were to even think about this, he would suddenly have to start providing large swaths of X as well.
Offline
Unfortunately I am unable to use linux-ck as I am reliant on suspend/resume functionality.
Everytime I suspend, I get a partial suspend (suspend is successful but all fans are still spinning), the screen is black.
The only way to resume everything to a working condition is to reboot the whole computer. I have read that the latest kernels changed the suspend/resume cycle and I find it unfortunate that I am able to suspend with the vanilla kernel but not with the linux-ck.
Hopefully, there will be some sort of fix for this at some point...
I am using Phenom processor with HD5770 (r600 open-source drivers) in case someone is wondering.
Offline
Headers for 3.10.10 and virtualbox too and broadcom-wl updated for i686 but the kernel no
so now I have a 3.10.9-ck-atom whit broadcom-wl, headers and virtualbox rebuilds for 3.10.10-ck and 24 and not updated the 3.10.10-ck-atom kernel
so I miss my 3.10.10-ck-atom kernel
Well, I suppose that this is somekind of signature, no?
Offline
@Jristz - Thanks for reporting; it's up there now. Please try again:
# pacman -Syyu
Last edited by graysky (2013-08-30 23:16:25)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
What's happened to the generic linux-ck package? It's not listed here: http://repo-ck.com/i686.htm and is now absent from my repo-ck.db! So I have an up-to-date linux-ck-headers, and a "foreign" linux-ck which I would have to update from the AUR...
Hope ck-generic hasn't been booted for some reason.
Offline
@Kebertx - Same problem that affected the atom package not getting sync'ed into my local repo before indexing. Fixed now, refresh your db and it will come:
# pacman -Syyu
Last edited by graysky (2013-08-31 17:42:47)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Hello everybody! 0/
I'm not much of an asker so i just shoot the best i can:
are these kernels (the p4 one, in particular) aufs_friendly?
Thanks!
Offline