tag:blogger.com,1999:blog-7835005092850855540.post2377605883600779766..comments2024-03-22T13:59:33.928+01:00Comments on Lötzimmer: Debian on WD My Cloud Home single-bay (MCH) - part 2 (updated to match latest GPL sources 7.15.0)Unknownnoreply@blogger.comBlogger49125tag:blogger.com,1999:blog-7835005092850855540.post-15327461102479996792022-12-08T23:59:08.535+01:002022-12-08T23:59:08.535+01:00Danke sehr! Nach viel Quälerei hat es nun funkt...Danke sehr! Nach viel Quälerei hat es nun funktioniert, das sda21 als luks2/btrfs anzulegen. Dafür fehlte im Kernel bisher der device-mapper. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-58839735569379457822022-12-08T23:43:30.227+01:002022-12-08T23:43:30.227+01:00Grundsätzlich ist die Installation für den 4.9er K...Grundsätzlich ist die Installation für den 4.9er Kernel nicht anders als für den 4.1.17. Der Kernel und der DeviceTree müssen auf die entsprechenden Partitionen der Festplatte geschrieben werden.<br /><br />Dafür kommen Partitionen 2 und 5 (Boot A),<br />8 und 6 (Boot B) oder<br />16 und 10 (Boot G)<br />in Frage (siehe Partitionstabelle oben).<br /><br />Wie deine der Device Name deiner Festplatte ist, weißt du wahrscheinlich selbst am besten.Alexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-35645030674124301132022-12-08T23:25:16.083+01:002022-12-08T23:25:16.083+01:00Unter dem Kernel-Install ist es für den 4.1 besch...Unter dem Kernel-Install ist es für den 4.1 beschrieben, den Kernel kenne ich gar nicht. Wie ist es damit nun beim 4.9, denn ein /dev/sataaXX gibt es hier ja nicht (mehr). Hätte ich mal irgendwo ein howto finden können, so würde ich das auch selber lesen und nicht so komische Fragen stellen.....<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-17062768880569559392022-12-08T23:08:13.648+01:002022-12-08T23:08:13.648+01:00Sorry, ich dachte, es ginge ums "bauen"....Sorry, ich dachte, es ginge ums "bauen"... der Rest steht eigentlich schon im Beitrag unter "Installing the Kernel".<br /><br />Beim 4.9.266er Kernel liegt der DeviceTree unter arch/arm64/boot/dts/realtek/rtd129x/rtd-1295-monarch-1GB.dtb<br /><br />Das xbuild Script padded das Kernel Image noch (ist aber nach meiner Erfahrung optional):<br />dd if=/dev/zero of=arch/arm64/boot/Image conv=notrunc oflag=append bs=1k count=512<br /><br />Module installierst du wie gewohnt mit "make modules_install".Alexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-77313758748978886972022-12-08T21:41:29.346+01:002022-12-08T21:41:29.346+01:00Danke für die fixe Antwort!
> cp linux-4.9.266...Danke für die fixe Antwort!<br /><br />> cp linux-4.9.266/arch/arm64/boot/sata.uImage .<br />WO ist "." - sprich, wo bin ich an dieser Stelle im Dateisystem?<br /><br />ich hab den Kernel auf der box (nativ) gemacht, dieser liegt nun in /usr/src/linux-4.9.266 ... Was bitte nun? Bei normalen Debian baue ich nun den Kernel und initrd in /boot ein, trage das danach in lilo/grub ein. Wie aber funktioniert es bei der WD-Box?<br /><br />Oben beschrieben kopiere ist uImage und dtb in das aktuelle Verzeichnis, danach werden modules ins Verzeichnis gepackt. In welches Verzeichnis oder fehlt da noch ein entscheidener Befehl? Danke.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-60510988317598569022022-12-08T18:57:21.264+01:002022-12-08T18:57:21.264+01:00Mit den aktuellen GPL sources lässt sich in kürzes...Mit den aktuellen GPL sources lässt sich in kürzester Zeit ein Kernel per Docker bauen (nicht auf der Box selbst, z.B. Docker-Desktop unter Windows):<br /><br />cd GPL_MCH_Monarch_<br />cd dockerfile/<br />docker build -t kdp_build_env .<br />cd ../kernel<br />tar xf linux-4.9.266.tgz<br /># ... .config Datei kopieren oder Patches anwenden<br />docker run -it --rm --privileged=true -e LOCAL_USER_ID=`id -u ${USER}` -e ARCH=arm64 -v "${PWD}:/home/user/build" kdp_build_env /bin/bash<br />cd linux-4.9.266<br /># von nun an kann man per "make menuconfig" den Kernel konfigurieren<br />./xbuild.sh build<br /># baut den Kernel (ca. 1min auf einem Ryzen 7 3700X)<br />exit<br /># verlässt den Container<br />cp linux-4.9.266/arch/arm64/boot/sata.uImage .<br />cp linux-4.9.266/arch/arm64/boot/sata.dtb .<br />cd linux-4.9.266/_install/<br />tar cfz ../../sata.modules.tgz .<br />cd ../..<br /># kopiert alle benötigten Dateien zum anschließenden Transfer auf die BoxAlexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-73582691596534350622022-12-08T17:17:12.889+01:002022-12-08T17:17:12.889+01:00Gibt es irgendwo ein plausibles howto für das Komp...Gibt es irgendwo ein plausibles howto für das Kompilieren vom 4.9.266 Kernel und dessen Installation auf dem My Cloud home? Bei mir läuft dieser Kernel zwar soweit ganz gut, jedoch müsste ich noch Teilen reinkompilieren. Leider finde ich nirgendwo Infos für eine generelle Installation auf der Box.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-66327281019354875972022-03-28T16:38:01.857+02:002022-03-28T16:38:01.857+02:00I have used precisely that uBoot with netconsole b...I have used precisely that uBoot with netconsole before on other devices. I don't think WD bothered to compile that feature though.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-46558377041522918892022-03-28T15:38:48.477+02:002022-03-28T15:38:48.477+02:00Hi Alex, thank you i've saw it and that's ...Hi Alex, thank you i've saw it and that's exactly why i was looking near uboot :)and think about my seagate home with uboot netconsole. i've tried with virtual linux interface and wireshark but no success at this time (no packet from mcu), but i will retry this on 'real' eth, switch and so real promiscous mode. will update if found something. I also want to inspect the 'orignal android partition' to look if i can found some binaries that can interact with uboot... to have use it on my seagate home : it's clearly 'confortable' to have acces to uboot without opening the mcu (for exemple look this https://forum.doozan.com/read.php?3,14,14)PierreMhttps://www.blogger.com/profile/10764387393997860560noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-44321267510060224022022-03-28T15:27:39.054+02:002022-03-28T15:27:39.054+02:00Btw. thanks for the warning! :DBtw. thanks for the warning! :DAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-1543842208983535262022-03-28T15:27:01.048+02:002022-03-28T15:27:01.048+02:00Ohh, that must be a different initrd then... I'...Ohh, that must be a different initrd then... I'll see if I post an updated initrd which I use as debugging then.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-19749708129137852072022-03-28T15:24:12.167+02:002022-03-28T15:24:12.167+02:00Have a look at this for uBoot (I posted this in pa...Have a look at this for uBoot (I posted this in part 4):<br />cd /<br />dd if=/dev/mtd0 bs=1 count=9216 skip=98304 | tar x<br />cat /tmp/factory/env.txt<br /><br />AlexAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-80650666488699419742022-03-28T15:03:36.206+02:002022-03-28T15:03:36.206+02:00@Alex : please modify this :
"Before a Kerne...<br />@Alex : please modify this :<br /><br />"Before a Kernel is made permanent in the boot FW_TABLE it is advisable to copy everything to a USB stick and see if the Kernel actually boots. (e.g. using the original install USB stick without!!! the OMV directory as we don't want to re-install)"<br />With the last version of fox_exe : if you put your new kernel and dtd and suppress "omv" directory the result will be an usable system because it delete / without checking if /omv exist on the usb... (i've tested it ;) )<br />Best way is to use a recovery stick and put the new kernel/dtd to check if all is ok before writing to mcu/hdd. <br />PierreMhttps://www.blogger.com/profile/10764387393997860560noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-35366375354564693332022-03-28T14:56:22.032+02:002022-03-28T14:56:22.032+02:00thank you for updating, i've used your receipe...thank you for updating, i've used your receipe to compil kernel and dtb on my side (on the mcu, like you) and installed my kernel version (same as your). i've update to debian 11 (from 10) to maximize the used space between root and /usr. Now working on uboot to gain access thru 'remote console' ont ethernet (like my seagate home with uboot) to avoid using a real serial console. will update if success. thanks Alex !PierreMhttps://www.blogger.com/profile/10764387393997860560noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-69481649740853248092022-03-17T23:51:56.992+01:002022-03-17T23:51:56.992+01:00I updated the file. Thanks for noticing!I updated the file. Thanks for noticing!Alexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-84155207504828872262022-03-14T22:45:50.411+01:002022-03-14T22:45:50.411+01:00Hi Alex,
perhaps i miss something but available m...Hi Alex, <br />perhaps i miss something but available memory is not 1GB after installing your kernel (from https://loetzimmer.de//patches/) :<br />dd if=MCH_kernel_image_4.1.17 of=/dev/sataa8<br />dd if=MCH_dtb_4.1.17 of=/dev/sataa6<br />fwtablectl-arm64 firmware update /dev/sataa1 RescueKernel MCH_kernel_image_4.1.17<br />fwtablectl-arm64 firmware update /dev/sataa1 RescueDeviceTree MCH_dtb_4.1.17<br />then reboot <br />pierre@FON31-wdnas:~$ grep MemTotal /proc/meminfo<br />MemTotal: 750740 kB<br /><br />I've see that MCH_dtb_4.1.17 is 2021-07-07 and kernel build is 2021-11-15<br />could this be my issue on mem avail ?<br />Many thanks for your great works !<br />PierreMhttps://www.blogger.com/profile/10764387393997860560noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-85708934821693090052022-01-10T22:29:23.596+01:002022-01-10T22:29:23.596+01:00There probably is... there is some source code of ...There probably is... there is some source code of FFMPEG in the GPL download. I haven't dared to look into that - I needed a plain fast NAS, sorry ;)Alexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-83102316507076378462021-12-18T06:04:54.086+01:002021-12-18T06:04:54.086+01:00Reading this post I see that MCH works on RTD1295 ...Reading this post I see that MCH works on RTD1295 SOC.<br />I am wondering if there is a way to use hardware resources for h265 decoding.peppehttps://www.blogger.com/profile/04423150990465521815noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-60373843290689727882021-10-30T11:05:22.130+02:002021-10-30T11:05:22.130+02:00OMG, no problem, I will give MCH away and I will b...OMG, no problem, I will give MCH away and I will buy a PI4, I am also tired to have those limitaion and don't have possibility to make a correct backup without problem with OMV.<br />BTW: thank you Alex!Joahannahttps://www.blogger.com/profile/03996495200259708131noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-45176655347397042982021-10-26T14:47:25.977+02:002021-10-26T14:47:25.977+02:00Not exactly.
Originally WireGuard was released for...Not exactly.<br />Originally WireGuard was released for the Linux kernel, at least kernel 3.10 is required for installation.<br />https://www.wireguard.com/build-status/herrwammhttps://www.blogger.com/profile/14956256014462593452noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-32912721303250414572021-10-26T14:46:28.061+02:002021-10-26T14:46:28.061+02:00Dieser Kommentar wurde vom Autor entfernt.herrwammhttps://www.blogger.com/profile/14956256014462593452noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-36701329320310543162021-10-25T17:52:36.322+02:002021-10-25T17:52:36.322+02:00Ok no problem!
Unfortunately there are some limita...Ok no problem!<br />Unfortunately there are some limitation, I imagined!<br />Thank you for your help!!Samuhttps://www.blogger.com/profile/09764451487595624627noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-53066282252080957452021-10-24T14:10:07.071+02:002021-10-24T14:10:07.071+02:00As far as I know, Wireguard requires at least kern...As far as I know, Wireguard requires at least kernel 5.4.x - this is 4.1.17, long before Wireguard existed.Alexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-6233332829445072582021-10-24T14:06:10.103+02:002021-10-24T14:06:10.103+02:00Don't shoot the messenger... ;)
I'm afraid...Don't shoot the messenger... ;)<br />I'm afraid we'll have to live without proper KVM support. Doing some reading this would require at leat two things:<br /> 1. a more recent Kernel - although not a guarantee that it'll work on the Realtek 1295 but 4.9.x seems to be a must<br /> 2. some modification to the bootloader to put the CPU into nonsec mode, enabling the HYP feature<br /><br />I hate to say, but all of this is probably not worth the effort. Alexander Noackhttps://www.blogger.com/profile/03776828057013811695noreply@blogger.comtag:blogger.com,1999:blog-7835005092850855540.post-20360018843452062802021-10-23T21:06:13.973+02:002021-10-23T21:06:13.973+02:00Hey there!
Is there any way to WireGuard support?
...Hey there!<br />Is there any way to WireGuard support?<br />I suppose the main thing is that there is custom kernel and no linux-headers. So, don't quite understand how to make it work.herrwammhttps://www.blogger.com/profile/14956256014462593452noreply@blogger.com