No, I’m on a pc intel. I have to forget something, I turn under strech x64, and it is the kernel of my system that is taken into account.
‘x64’ is actually the amd64 architecture. Created by AMD, copied by Intel. So your 64-bit Intel processor is running an AMD architecture…
Just replace sources in APT and run dist-upgrade.
Also you can use qemu-user-static and run dist-upgrade in chrooted wheezy/jessie.
One note: Use kernel 3.2.68 or compile your own.
Thank you for these precisions, now that you say, this architecture was created with the athlon 64 if I say no bullshit?
Intel so crushed the market, that we forget the very amd work at the time.
Openssh-server does not start, i did a test last night, i suspect a conflict between sysvinit and systemd.
Check PFE module: Is it load correctly? (pfe,ko = network driver for gen1 devices)
I compiled a stretch arm from my cloud directly, which fixed the problem of pointing to the right folder.
But, new problem in syslog, “Failed to set invocation ID on control group”, this function is supported by systemd only from kernel 3.12 :
[quote]Sorry, we do not support such old kernels with system 232. See README. The minimum required kernel version is 3.12.
Your old kernel does not support xattrs on cgroupfs, simply because it is too old.
Sorry if htat’s disappointing.[/quote]
So I think we can sit on stretch, unless wd updates the kernel, but for an old machine like wdmycloud gen1, we can leave on esperance zero
Syslog after upgrade from Jessie : http://pasted.co/515cdd37
Services do not start.
Gen1 newer got updates.
Gen2 and other - have different CPU (Marvell Armada 3xx) and have support in mainline kernel. In most cases all what we need - correct DTB (dts) file. (And i make few for 3.2.x kernel. But i cant run latest 4.x kernel… idk why… )
Thanks for the hint, I just noticed Florian_Hahner had the compiled gen2 kernel available in post #1265. I replaced the uImage in /boot, and ACL works like a charm! Managing permissions is much easier now!
Really hope DSM would work for gen2 myclouds…
What do I have to do to perform an update or a complete reinstallation on my GEN2?
At the moment I still use the debian for gen2 from fox …
But would gladly update/use the version from florian …
Only I’m not sure what I have to do with the kernel.config / uimage and uramdisk.
Because the how-to from fox for a clean-install doesn´t help further or pased.
Or did I really have to make everything new and save the data from sda2…
so how can i changed from fox to florian
Do not need any more help, I still managed.
i have installed a fresh Debian on my WD Mycloud GEN2 now.
I cant detect any USB device.
I did Install USB Tools to check with lsusb, but i only get an error:
unable to initialize libusb: -99
i Allready did get an hint to add to /etc/fstab these line:
usbfs /proc/bus/usb usbfs defaults 0 0
But didnt work ;-(
Hello thanks a lot.
it did work for:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
But it dowsnt detect my connected USB Hardisk will not be listed as sdb
Could you explain how.
Now it becames really Strange.
I left the usb drive connected and it cames up after more than 30 minutes.
After rebbot it wasnt detected again ;-(
Also i couldnt mount it becasue of error message.
just copy the files from archive to /root/boot on sda3
use the how_to.txt for debian as base
# Prepare new firmware: mount /dev/sda3 /mnt/root tar xvf /mnt/data/rootfs-jessie.tar.xz -C /mnt/root mkdir -p /mnt/root/boot cp /mnt/data/uImage /mnt/root/boot/uImage cp /mnt/data/uRamdisk /mnt/root/boot/uRamdisk umount /mnt/root
So all 3 Files are in : root@mycloud:/boot and must be overwritten
but i can not change the hardware clock/time when i used the files from florian.
No matter what I tried or changed, after each reboot I did again:
Thu Jan 1 01:09:47 CET 1970
Hwclock doesn´t work:
root@mycloud-8tb:/boot# hwclock --debug
hwclock from util-linux 2.25.2
hwclock: cannot open /dev/rtc: No such file or directory
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
And on apt-get update sometimes it shows runlevel errors/problems
So i didn´t know if this Versions Works finally on every WD Cloud Drives
RTC present in Gen2, but dont have battery (And no any pinouts for connect it), so RTC is useless.
Use “fake-hwclock” app instead.
Help. I did a big mistake.
I have changed the network configuration. Because I only did have 10 mbit/s.
I have changed the advanced settings. Now my network didn’t came up again…
Is possible to boot by USB and change settings manual via telnet? Where it the file for network setting stored?
Thanks a lot.