You are not logged in.
Pages: 1
Hi,
I'm a bit confused with the [dsdt] hook... If anyone could please kindly help me to clarify...
1. Is the /lib/initcpio/custom.dsdt file only a renamed DSDT.aml or should it be something else...?
2. Then, on the mkinitcpio wiki page, concerning DSDT hook, it's mentioned :
INSTALLATION
Loads a custom acpi dsdt file during boot. Place your custom dsdt file for inclusion at /lib/initcpio/custom.dsdtRUNTIME
The custom dsdt file is automatically used by the kernel if it is present in initramfs.
Why is it question of initramfs here ? Shouldn't it be initcpio ?
Thanks in advance.
Cheers
Offline
Yes IIRC you should rename the recompiled dsdt file to "custom.dsdt" and move it to /lib/initcpio assuming that you decompiled /proc/acpi/dsdt to dsdt.dsl and recompiled it after making some changes to "DSDT.aml". I don't remember compiller switches and default names but I believe output binary file was called "DSDT.aml" and that's what should be renamed to custom.dsdt - simply check the output of the compiler to be sure.
And I don't know if you can call initcpio image as initramfs. Maybe it's something left from the kernel26beyond docs? Anyway, it just works for both...
Offline
Yes IIRC you should rename the recompiled dsdt file to "custom.dsdt" and move it to /lib/initcpio assuming that you decompiled /proc/acpi/dsdt to dsdt.dsl and recompiled it after making some changes to "DSDT.aml". I don't remember compiller switches and default names but I believe output binary file was called "DSDT.aml" and that's what should be renamed to custom.dsdt - simply check the output of the compiler to be sure.
And I don't know if you can call initcpio image as initramfs. Maybe it's something left from the kernel26beyond docs? Anyway, it just works for both...
i only renamed DSDT.aml to /lib/initcpio/custom.dsdt and ran mkinitcpio -g /boot/kernel26-dsdt-custom.img and works well
Offline
And I don't know if you can call initcpio image as initramfs. Maybe it's something left from the kernel26beyond docs? Anyway, it just works for both...
This is just one of those goofy naming things. "initramfs" is the name of the filesystem in-kernel. An "initramfs" filesystem is loaded from a compressed cpio archive. The reason this is called "mkinitcpio" is simply because mkinitramfs is over-used and we already had an mkinitramfs for the beyond kernel. So seeing that the "ramfs" is loaded from a "cpio" image, I went with "initcpio" in place of "initramfs" to get rid of future naming conflicts.
Offline
OK....
How do I use the kernel26-dsdt-custom.img ? Or it is atomadicly used after running
mkinitcpio -g /boot/kernel26-dsdt-custom.img
OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec
Offline
OK I got it ![]()
I just needed to edit my grub menu list...
OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec
Offline
Pages: 1