Transition Members
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mapero

  • Rank
  1. Hi, this is just a short tutorial how you could modify the boot image, e.g. to include your own kernel. I did not find any tutorial for this use case in the wiki. 1. First you need an existing image file. E.g. synoboot-trantor-dsm4.2-v1.0.img. 2. Do the following as root. 2. Map it to a loop device: $ losetup -f synoboot-trantor-dsm4.2-v1.0.img $ kpartx -a -v synoboot-trantor-dsm4.2-v1.0.img add map loop1p1 (253:4): 0 32067 linear /dev/loop1 63 3. Mount the partition: $ mount /dev/mapper/loop1p1 /mnt 4. Modify it. E.g. copy new kernel to /mnt. 5. Umount it: umount /mnt 6. Remove mapping: $ kpartx -d synoboot-trantor-dsm4.2-v1.0.img loop deleted : /dev/loop1 $ losetup -D Here you go. This is also a memo for myself.
  2. I will PM it to you, and yes ACPI_PROC_EVENT will be in next repack. The question is : like module or built-in ? Thanks for your response. After some struggling i build my own Kernel (you posted in an other thread how you did it, thanks) with working acpi support and some drivers for KVM guest maschines. ACPI is working so far, but it will not shutdown "complete". Linux is going down, black screen, but still powered on. Not sure whats wrong. Maybe you could release your source for kernel somewhere? What i did: 1. Downloaded 3201 source and applied all changes from andys git manuell. 2. Used your .config with the following changes (KVM and ACPI): $ diff .config .config_org 265,274c265 < CONFIG_PARAVIRT_GUEST=y < # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set < # CONFIG_XEN is not set < # CONFIG_XEN_PRIVILEGED_GUEST is not set < CONFIG_KVM_CLOCK=y < CONFIG_KVM_GUEST=y < CONFIG_PARAVIRT=y < # CONFIG_PARAVIRT_SPINLOCKS is not set < CONFIG_PARAVIRT_CLOCK=y < # CONFIG_PARAVIRT_DEBUG is not set --- > # CONFIG_PARAVIRT_GUEST is not set 401c392 < CONFIG_ACPI_PROC_EVENT=y --- > # CONFIG_ACPI_PROC_EVENT is not set 404c395 < CONFIG_ACPI_BUTTON=y --- > CONFIG_ACPI_BUTTON=m 872d862 < CONFIG_VIRTIO_BLK=y 1186d1175 < CONFIG_VIRTIO_NET=y 1490d1478 < # CONFIG_VIRTIO_CONSOLE is not set 2279,2280d2266 < CONFIG_VIRTIO=y < CONFIG_VIRTIO_RING=y 2285c2271 < CONFIG_VIRTIO_PCI=y --- > # CONFIG_VIRTIO_PCI is not set 3. Build busybox from here: with acpid support. 4. Added the following to /etc/acpi/ : DiskStation> cat /etc/acpi/PWRF/00000080 #!/bin/sh poweroff DiskStation> Todo: Startup script for acpid; Fix poweroff-bug
  3. Thanks working great on kvm (proxmox). Thanks for including config.gz. Did you apply any other changes to source beside the config.gz? I want to start and shutdown the VM when start/shutdown the server. proxmox is shutting down the VMs over acpi. This is not working at the moment. In the config CONFIG_ACPI_BUTTON=m is set, but the modul button.ko is missing. Any idea? Edit: Did some more testing by myself. Recompiled busybox with acpid. But i am missing /proc/acpi/events. Can you add CONFIG_ACPI_PROC_EVENT in your next release. Thanks. mapero
  4. Is there any reason why you forward only the first partition (sdb1 / sdc1) of a drive instead the whole drive (sdb/sdc)? It then should be possible to use synologys energy management. Anyway tried your howto but ended with a kernel panic when booting. Edit: Selected another cpu architecture (core2duo) and it booted fine.
  5. Hi. Besitze seit einiger Zeit die DS211j, aufgrund der geringen Geschwindigkeit und Speicherplatzmangel habe ich mir nun den hp n54l Server gekauft. Auf diesem läuft zur Zeit proxmox mit kvm Virtualisierung. Der ursprüngliche Plan war, die 2 Platten in den n54l zu übernehmen und direkt an eine VM mit OMV oder OpenFiler weiterzureichen und das bestehende Raid1 weiterzuverwenden. Jetzt habe ich zufällig dieses Projekt entdeckt. Ist es möglich statt OMV/OF XPEnology zu verwenden und den bestehenden Raid1-Verbund weiter zu nutzen ohne zu formatieren? Synology reserviert sich ja auf dem Verbund einen eigenen Speicherbereich für das System. Hat jemand schonmal sowas gemacht? Gruß, mapero