You are not logged in.
@falconindy - Perhaps unrelated to the cp warning, but this discussion is related to the problem that syne had, no? Linux-ck uses the same configs are the ARCH kernel package. In this case the configs in 3.2.7-1-ARCH and 3.2.7-2-ck are fine when paired with mkinitcpio-0.8.2-3 or am I mistaken?
Am 21.02.2012 22:05, schrieb Dan McGee:
> On Tue, Feb 21, 2012 at 2:57 PM, Ionut Biru <ibiru at archlinux.org> wrote:
>> On 02/21/2012 07:38 PM, Tobias Powalowski wrote:
>>> https://bugs.archlinux.org/task/25341
>>> - ext4 manages now ext2/ext3 and ext4
>>>
>>> Please report if any issues happen, here all went fine on all machines.
>>> I had not to change any config file like fstab or mkinitcpio.conf.
>>>
>>> greetings
>>> tpowa
>>>
>> Why do we do config changes in bug fix releases?
>> Can't this change be delayed until 3.3?
> Please revert this change. Thomas explicitly said to try this in 3.3,
> and you went ahead with it in 3.2.7 and broke boot on at least one
> user's system because this hadn't been tested with mkinitcpio yet [1].
>
> -Dan
>
> [1] https://bugs.archlinux.org/task/28569
This is what testing is for, now it's fixed and no need to revert.
greetings
tpowa
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
cp warning is a completely separate issue caused by someone having the filesystems hook _and_ ext[23] in MODULES=. I'm not fixing this unless someone gives me a truly compelling reason.
Syne's issue is/was caused by the autodetect hook not resolving aliases (translating ext3 -> ext4). That's already fixed by 0.8.2-3.
Offline
Hey there - first time user of the ck kernel (ck-kx in my case), and apart from having to re-do oss, catalyst and virtualbox no problems so far, thank you. I have noticed that a server I run on mono is using approx 10% less CPU than it was - is this a direct result of BF scheduling? If so, wow, good job
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
/ is the root of all problems.
Offline
@Roken - It could be. Best you can do to prove it is to look at average load over time under each kernel. Enjoy. The BFS rocks for "small" systems. In my experience, even 16 cores (dual quads + HT).
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
cp warning is a completely separate issue caused by someone having the filesystems hook _and_ ext[23] in MODULES=. I'm not fixing this unless someone gives me a truly compelling reason.
Thanks, it was exactly as you described. I had thought it was related because I didn't see it prior to this upgrade.
Offline
In this case the configs in 3.2.7-1-ARCH and 3.2.7-2-ck are fine when paired with mkinitcpio-0.8.2-3 or am I mistaken?
I just put linux-ck-atom on my netbook from the repo two days ago (a big thanks BTW). The first round I didn't do a whole lot of reading and figured I'd just dive in. I was unable to boot to the default image but fallback worked. I added ext4 to modules of mkinitcpio.conf, rebuilt initramfs, then it worked fine. The next day mkinitcpio rev-3 was out of [testing] and into the regular repo; I updated, removed ext4 from the config, rebuilt initramfs with the default configs, and it works perfectly.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Just as intended. Glad everything is copecetic.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Hi,
I've got this error while trying to upgrade 3.2.9 > 3.2.11
==> Starting build: 3.2.11-1-ck
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [autodetect]
-> Parsing hook: [pata]
-> Parsing hook: [scsi]
-> Parsing hook: [sata]
-> Parsing hook: [filesystems]
-> Parsing hook: [usbinput]
-> Parsing hook: [consolefont]
-> Parsing hook: [keymap]
==> ERROR: module not found: `bfq-iosched'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-ck.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Image generation successful
Is it expected? Previous versions installed just fine with the same mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="bfq-iosched"
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.conf"
FILES="/etc/modprobe.d/modprobe.conf"
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
#
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata filesystems usbinput consolefont keymap"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Offline
Such things happened before: https://bbs.archlinux.org/viewtopic.php?id=133545
Offline
Yes, I figured. I was having this problem > http://bbs.archbang.org/viewtopic.php?id=2304 I thought it was related. Apparently not.
Offline
Hi,
I've got this error while trying to upgrade 3.2.9 > 3.2.11
==> Starting build: 3.2.11-1-ck -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [autodetect] -> Parsing hook: [pata] -> Parsing hook: [scsi] -> Parsing hook: [sata] -> Parsing hook: [filesystems] -> Parsing hook: [usbinput] -> Parsing hook: [consolefont] -> Parsing hook: [keymap] ==> ERROR: module not found: `bfq-iosched' ==> Generating module dependencies ==> Creating gzip initcpio image: /boot/initramfs-linux-ck.img ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Image generation successful
Is it expected? Previous versions installed just fine with the same mkinitcpio.conf
Did you build this from the AUR or download from the repo? If you built it from the AUR, please post the output of:
$ head /path/to/linux-ck/PKGBUILD
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
No, from the repo.
Offline
OK.. I haven't tried invoking it this way before. Can you verify that the module is indeed present and probe'able manually?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
The module is present and everything is fine now. I think the problem was happening because I was using mkinitcpio from [Testing], I downgraded it along with udev, mkinitcpio-busybox and util-linux yesterday to fix the boot problem in post #735.
Edit: The problematic version(now in core) is 0.8.4-1.
Last edited by rAX (2012-03-15 08:42:11)
Offline
How can I add into linux-ck the following modules 'vboxguest vboxsf vboxvideo'? I want to run an Arch virtual machine with linux-ck.
The box said Windows XP or better. So I installed Linux.
Offline
How can I add into linux-ck the following modules 'vboxguest vboxsf vboxvideo'? I want to run an Arch virtual machine with linux-ck.
Install virtualbox-source and run vboxbuild once and after major kernel updates (e.g. from 3.1 to 3.2).
BTW: wiki would have had that answer as well…
Last edited by jakob (2012-03-19 12:29:15)
Offline
I get this error after running 'vboxbuild'
/usr/bin/vboxbuild: line 5: /etc/vbox/vbox.cfg: No such file or directory
error: missing vbox.cfg
The box said Windows XP or better. So I installed Linux.
Offline
I get this error after running 'vboxbuild'
/usr/bin/vboxbuild: line 5: /etc/vbox/vbox.cfg: No such file or directory error: missing vbox.cfg
Um, do you have VirtualBox itself installed?
ᶘ ᵒᴥᵒᶅ
Offline
After installing virtualbox I get this error when running 'vboxbuild':
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
error: `/lib/modules/3.2.11-1-ck/build' does not appear to be a valid kernel build directory.
Last edited by sergiuniculescu (2012-03-19 13:03:48)
The box said Windows XP or better. So I installed Linux.
Offline
After installing virtualbox I get this error when running 'vboxbuild':
:: Removing all old VirtualBox kernel modules [FAIL] :: Removing all old VirtualBox kernel modules [FAIL] :: Removing all old VirtualBox kernel modules [FAIL] error: `/lib/modules/3.2.11-1-ck/build' does not appear to be a valid kernel build directory.
You're probably missing the kernel headers package for your CK kernel.
ᶘ ᵒᴥᵒᶅ
Offline
I've installed the 'linux-ck-headers' and after running 'vboxbuild' I get this:
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Recompiling VirtualBox kernel modules (3.2.11-1-ck) [DONE]
And when I rebooted the virtual machine I got the same warnings when loading user specified modules:
WARNING: Module vboxguest not found
WARNING: Module vboxsf not found
WARNING: Module vboxvideo not found
The box said Windows XP or better. So I installed Linux.
Offline
I have no experience with running Arch in a VM, but perhaps those modules need to be included in the initramfs. In that case you would add them to the MODULES line in /etc/mkinitcpio.conf and rebuild the image with:
# mkinitcpio -p linux-ck
ᶘ ᵒᴥᵒᶅ
Offline
The same error appeared after I added those modules in /etc/mkinitcpio.conf:
┌─[ sergiu @ sergiu-vbox ] - [ ~ ]
└─[$]> sudo mkinitcpio -p linux-ck
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck.img
==> Starting build: 3.2.11-1-ck
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [autodetect]
-> Parsing hook: [pata]
-> Parsing hook: [scsi]
-> Parsing hook: [sata]
-> Parsing hook: [filesystems]
-> Parsing hook: [usbinput]
-> Parsing hook: [fsck]
==> ERROR: module not found: `vboxguest'
==> ERROR: module not found: `vboxsf'
==> ERROR: module not found: `vboxvideo'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-ck.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck-fallback.img -S autodetect
==> Starting build: 3.2.11-1-ck
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [pata]
-> Parsing hook: [scsi]
-> Parsing hook: [sata]
-> Parsing hook: [filesystems]
-> Parsing hook: [usbinput]
-> Parsing hook: [fsck]
==> ERROR: module not found: `vboxguest'
==> ERROR: module not found: `vboxsf'
==> ERROR: module not found: `vboxvideo'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-ck-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Image generation successful
The box said Windows XP or better. So I installed Linux.
Offline
Take a good look where you actually need those modules (client or server), where you build them and where you (optionally) include them.
ᶘ ᵒᴥᵒᶅ
Offline
With the new nvidia-utils I am unable to install nvidia-ck-corex due to version mismatches, (295.33 versus 295.2) on the ck repo. I'm sure this will get updated soon though (meanwhile I will do my best using elinks). Great repo and work with this Linux-ck. I've benchmarked before and after to see positive results compared to the vanilla kernel. There was about an 8-11% improvement.
Offline