You are not logged in.
Offline
But meanwhile, ignore repo-ck updates? Or should I downgrade as well? I'm not experiencing any crashes.
Pretty much. I think that once Linux 4 gets back in the repo, the pkgrel will be higher. You'll have to confirm that with graysky though, as he will be the only one to know.
EDIT:
yochaigal
follow this:
yaourt -G acpi_call-ck
cd acpi_call-ck/
sed -i 's/4.0/3.19/' PKGBUILD && sed -i 's/4.0/3.19/' *.install
sudo pacman -R acpi_call-ck
yaourt -Syuu
makepkg -srci
Why?
Last edited by runical (2015-04-30 15:32:03)
Offline
There is no need to ignore the repo as version 3.19.6-1-ck and corresponding modules are online now. Upstream has the 3.19.x branch still marked as 'stable' and I expect they will release 3.19.7 in parallel with 4.0.2 so no worries of critical patches being missed at least short term. Once CK stabilizes linux-4.0-ck1 I will verify with users before pushing updates to [repo-ck].
Last edited by graysky (2015-04-30 19:08:50)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
You can add me to the kernel panics and hang list for 4 -ck
upgraded linux-ck-sandybridge (3.19.5-1 -> 4.0-1)
& not happening with non ck kernelUpdate: No problems found with linux-ck-atom 4.0-1 archlinux i686
I have also not been experiencing any issues with linux-ck-atom 4.0-1, runs flawlessly on my atom based netbook, strange why atoms are not affected, at least have not read any error posts regarding ck-atom
I suppose a downgrade is not needed in my case....
Cheers
Offline
I was experiencing crashes/panics before when I first udpated to 4.0.0-1-ck, but after switching the I/O scheduler to CFQ I haven't experienced any such crashes. It could be a coincidence, but I suspect it has to do mostly with BFQ.
14:50:00 ~ $ eaten -- "-ck"
linux-ck-nehalem
nvidia-340xx-ck-nehalem
virtualbox-ck-host-modules-nehalem
14:50:03 ~ $ alias eaten
alias eaten='pacman -Qsq'
Offline
And here I thought my overclock had gone crazy.
It could be a coincidence, but I suspect it has to do mostly with BFQ.
Might actually be true. I haven't had issues on my laptop so far (ck-piledriver) where I don't use BFQ, whereas my desktop machine with BFQ enabled wouldn't even boot most of the time (ck-k10, though, with nvidia-ck).
Offline
. . .
Running 64bit Arch with 4.0.0-1-ck kernel on a Lenovo X1 Carbon (sandybridge).
Isn't the Thinkpad X1 Carbon Ivybridge??
Offline
Yeah, you're totally right.
Offline
. ... .Once CK stabilizes linux-4.0-ck1 I will verify with users before pushing updates to [repo-ck].
How sweet it is... .. !
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
To anyone who experienced a panic under linux-ck-4.0-1, please try linux-ck-4.0.1-2 which contains this patch from Alfred Chen against bfs v462 in ck1. You can either:
1) Get the source and build yourself.
2) Download a pre-compiled version of x86_64 (generic) that I built this morning.
Option 1:
http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-2.src.tar.gz
Option 2:
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-2-x86_64.pkg.tar.xz
and optional headers
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-headers-4.0.1-2-x86_64.pkg.tar.xz
Last edited by graysky (2015-05-03 11:32:05)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Thanks graysky, I used the option 2 and just downloaded and installed the binary packages. For me it does not solve the issue: I've already got two kernel panics...
Offline
Thanks graysky, I used the option 2 and just downloaded and installed the binary packages. For me it does not solve the issue: I've already got two kernel panics...
...using BFQ by chance and if so, can you disable that?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
...using BFQ by chance and if so, can you disable that?
No, I was using deadline on all devices. However I switched to CFQ but still got kernel panics. Then I used option 1 and I built the package from sources and completely disabled the BFQ patches... it made no difference.
Offline
To anyone who experienced a panic under linux-ck-4.0-1, please try linux-ck-4.0.1-2 which contains this patch from Alfred Chen against bfs v462 in ck1. You can either:
1) Get the source and build yourself.
2) Download a pre-compiled version of x86_64 (generic) that I built this morning.Option 1:
http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-2.src.tar.gz
Option 2:
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-2-x86_64.pkg.tar.xz
and optional headers
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-headers-4.0.1-2-x86_64.pkg.tar.xz
I thought unofficial patches were not an option...
Offline
@mauritiusdadd - One more to try if you're up for it. Will post in 15 min or so with the instructions.
@AnAkkk - This is only for testing/troubleshooting purposes and is NOT live in the repo. Note the path to the files:
http://repo-ck.com/PKG_source/next/testing/...
Last edited by graysky (2015-05-03 14:08:02)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
@mauritiusdadd - One more to try if you're up for it. Will post in 15 min or so with the instructions.
Of course, no problem
Offline
@mauritiusdadd - One more to try if you're up for it. Will post in 15 min or so with the instructions.
OK...
Option 1 (roll your own):
http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-3.src.tar.gz
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-3-x86_64.pkg.tar.xz
and optional headers
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-headers-4.0.1-3-x86_64.pkg.tar.xz
...please disable BFQ for the initial test anyway. Thanks!
Last edited by graysky (2015-05-03 14:26:34)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-3-x86_64.pkg.tar.xz
Ok, I tested it for a while (using cfq deadline and bfq) and had no issue until now. I'm going to test it overnight and I'll report back tomorrow (or as soon as I get a kernel panic)
Last edited by mauritiusdadd (2015-05-03 16:07:00)
Offline
Ok, I tested it for a while (using cfq deadline and bfq) and had no issue until now. I'm going to test it overnight and I'll report back tomorrow (or as soon as I get a kernel panic)
Good to hear. This is the patch others are using with ck1 under linux v4.0.1 without issues as well. I have contacted CK for him to review to the code. Would others who have experienced a panic please test also?
Last edited by graysky (2015-05-03 16:46:05)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I'm asking this because of space limitations on my UEFI boot drive. I cannot install two different linux kernels, so I have to boot into live and chroot in to remove/replace the kernel... Does nvidia-ck work with your testing kernel?
edit: I guess I can edit the presets and build the kernel without a fallback img.
edit 2: nvidia-ck doesn't work with the current testing kernel
Last edited by Buddlespit (2015-05-03 17:39:41)
Offline
I'm asking this because of space limitations on my UEFI boot drive. I cannot install two different linux kernels, so I have to boot into live and chroot in to remove/replace the kernel... Does nvidia-ck work with your testing kernel?
edit: I guess I can edit the presets and build the kernel without a fallback img.
edit 2: nvidia-ck doesn't work with the current testing kernel
Sounds like you need a larger UEFI partition.. if it is too much hassle for you to test, you don't need to do it but your solution to not build the fallback img will work; you can so use a more powerful compression like xz to further reduce image footprint. No, you will need to rebuild the nvidia module which is why I provided the headers.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Buddlespit wrote:I'm asking this because of space limitations on my UEFI boot drive. I cannot install two different linux kernels, so I have to boot into live and chroot in to remove/replace the kernel... Does nvidia-ck work with your testing kernel?
edit: I guess I can edit the presets and build the kernel without a fallback img.
edit 2: nvidia-ck doesn't work with the current testing kernelSounds like you need a larger UEFI partition.. if it is too much hassle for you to test, you don't need to do it but your solution to not build the fallback img will work; you can so use a more powerful compression like xz to further reduce image footprint. No, you will need to rebuild the nvidia module which is why I provided the headers.
Ya, I'm testing out win10 for my wife, so I'm booting/mounting thru windows uefi and for the life of me, I cannot resize that tiny 100MB partition. So....
OK, I'm currently running 4.0.1-3-ck with a rebuilt nvidia-ck. I have the elevator set to bfq (I know what you said, but I'm testing!!! Gotta try to break it, ya?). I'm also running F@H set to med while working. That should set some kind of strain on the system. I'll report back if something breaks, or tomorrow morning. Whichever comes first...
Offline
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-3-x86_64.pkg.tar.xz
I didn't catch gummiboot in time to turn off BFQ, but all is well here so far. Not a hint of panic from the kernel. Will report back tomorrow.
@archun: Intel® Core™ i5-4210M • [GPU] Intel® HD Graphics 4600 • [Kernel] linux-ck-haswell
Handmade.Network • GitLab
The Life and Times of Miblo del Carpio
Offline
I guess I'll add my 2 cents on what works and what doesn't. I've been able to compile and run linux-ck and linux-ck-bobcat 4.0.1 on systems that have a BIOS. The one with a UEFI failed and kernel panicked.
The ones that have a BIOS are the Sony VAIO year 2010 and a Dell Latitude D600. The one that failed was a HP Envy d6. I'll try to get together a complete log of the panic and upload it on here.
Hope this helps.
Offline
I guess I'll add my 2 cents on what works and what doesn't. I've been able to compile and run linux-ck and linux-ck-bobcat 4.0.1 on systems that have a BIOS. The one with a UEFI failed and kernel panicked.
The ones that have a BIOS are the Sony VAIO year 2010 and a Dell Latitude D600. The one that failed was a HP Envy d6. I'll try to get together a complete log of the panic and upload it on here.
Hope this helps.
Is this with the most recent patch? I'm on UEFI here and having no problems at all. graysky's linux-ck-4.0.1-3 is still going strong.
@archun: Intel® Core™ i5-4210M • [GPU] Intel® HD Graphics 4600 • [Kernel] linux-ck-haswell
Handmade.Network • GitLab
The Life and Times of Miblo del Carpio
Offline