Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 28 days ago
i5Js, > I’ve tried with the cross connections and > direct, but it did not work. Sometimes, as I > mentioned before, I can see some characters when I > move the wires, That would be the noise on the wires when you move them. > but I don’t know how to double > check if everything is well solder > You can check one end to make sure it is OK (on the serverby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 28 days ago
https://community.wd.com/t/bricked-my-ex2-also-how-i-unbricked-it/98660/9 QuoteThe connector has the following pin map: 5 o <-- RX Data 4 (No pin) 3 o — N/C (3.3V) 2 o — GND 1 o --> TX Data Also QuoteOn the PCB inside the EX2, there is an (un)populated 5pin header on the back (side opposite the CPU). You can see the header I am talking about in the bottom image on thisby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 28 days ago
> I have some Rasp, and I'm doing some tests.... but > nothing works :( sometimes moving the pins in the > board I get som characters, but it's strange > because with a multi tester the connection between > both works... honestly I don't know that else I > can do. Check GND wire. You should connect only 3 wires GND, TXD, and RXD. > Do I need to conneby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 28 days ago
i5Js, > I also get another uart interface, but it don't > know why it doesn't work. I don't have anything > the screen. I'm trying to use my Mac, or a windows > machine with puttt, but nothing works. Just two > questions before giving up: > > ** should I need a raspberry to connect to the box > using the uart? You can run Linux VM on yourby bodhi - Debian
Re: Problems booting Debian on 88f6283 - 29 days ago
gt, Do you have serial console connected (if this box has serial header)? QuoteI followed great guide by bodhi, but the booting of new system fails because the dtb is nowhere to be found. The 88f6283 is a close cousin of the 88f6282. That would be the Zyxel NSA325. Try using the kirkwood-nsa325.dtb. Also the Silverstore (kirkwood-silverstore-hncn2.dtb)by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
i5Js, I recalled the issue now that I've reread CyberPK's post. The problem is the env locations in these WD NAS series actually overlaps the kernel uImage location. So you cannot save the env. If you do save them in serial console, the stock kernel on NAND will be corrupted. So now you have to make a choice. Either - Booting Debian permanently with the rootfs Debian-5.13.8by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
And read CyberPK installation post for more details. https://forum.doozan.com/read.php?2,28939,98649#msg-98649by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
Hold on. CyperPK said this https://forum.doozan.com/read.php?2,99079,106494#msg-106494 QuotePlease, note that this address is valid only for the patched uboot. As explained in my post, the stock address is overlapping with the uImage partition, so it isn't usableby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
i5Js, Now I remember, from the working thread for WD Ex2 Ultra https://forum.doozan.com/read.php?2,99079,105704#msg-105704 /dev/mtd0 0x100000 0x80000 0x20000 4 I guess you should also post the dmesg here, perhaps I can find something wrong from that. Let's capture the whole set of info in 1 post. dmesg cat /proc/mtd cat /etc/fw_env.config fw_printenvby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
Try echo “/dev/mtd0 0x100000 0x80000 0x20000 4” > /etc/fw_env.config fw_printenvby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
i5Js, I've not seen serial boot log for this Ex2 box. Perhaps I did in this forum and did not pay attention to it. The WD My Cloud series seem to use the same u-boot source, and it prints out the info about the envs. Like in Storm's post in this thread https://forum.doozan.com/read.php?2,132015,132426#msg-132426 QuoteU-Boot Environment: 0x00000000:0x00080000by bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 29 days ago
> > See if you can find the LEDs the same way in > > /sys/class? > > > > > root@LWT0080XXXXXXXX:/etc/apt# ls -l > /sys/class/leds/ > total 0 > lrwxrwxrwx 1 root root 0 2022-11-01 09:35 mmc0:: > -> ../../devices/platform/sdhci-mv.1/leds/mmc0:: > So it looks like the LEDs controls were hardcoded in this kernel.by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 29 days ago
i5Js, QuoteI've tried with the all combinations I found here for the fw_env.config, but none of them work: cat /proc/mtd might not give you the real mtd partition layout. It is best to see it in stock u-boot log, and also while in stock OS to confirm. However, according to the Ex2 Ultra stock u-boot log, the env location is at 0x00080000. This Ex2 might be the same. Try using thby bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 29 days ago
wildhem > The T10 does not differ much from the T50, it > lacks internal memory and has other software > pre-loaded as standard. Then perhaps the GPIOs are the same. > > The led and the power button are working properly > on this old ubuntu. See if you can find the LEDs the same way in /sys/class? ls -l /sys/class/leds/by bodhi - Debian
Re: Onespace X5 (Armada 385) Question - 30 days ago
JayX, > Looks like the new dtb works fine.But it still > stuck at 'LABEL=rootfs does not exist.' Also the > led on the usb disk was off always. What are plugged in storage devices? SATA, USB, MMC ? And perhaps it is time to try to run USB rootfs, like I suggested previously (loading kernel from MMC, with USB rootfs attached). It is easier to debug when you can run Deby bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 30 days ago
> > > root@debian:/# ls -lR /sys/class/leds/ > /sys/class/leds/: > total 0 > drwxr-xr-x 2 root root 0 Oct 31 09:28 . > drwxr-xr-x 55 root root 0 Oct 31 09:28 .. > lrwxrwxrwx 1 root root 0 Oct 31 09:41 > input4::capslock -> > ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/inputby bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 30 days ago
> However, do this to check > > > ls -lR /sys/class/leds/ > > > And where xxx is the name of each LED GPIO, > > > cat /sys/class/leds/xxx/trigger > NVM. The DTS does not have any LED GPIOs defined yet :)by bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 30 days ago
> I ran debian on my t10 :) Cool! > with the power button and the green LED is > blinking all the time That could mean the LED GPIOs are different. However, do this to check ls -lR /sys/class/leds/ And where xxx is the name of each LED GPIO, cat /sys/class/leds/xxx/triggerby bodhi - Debian
Re: Linux Kernel cleanup question - 30 days ago
dexter, It is better to update to linux-5.4.210-oxnas-tld-1.by bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 4 weeks ago
wildhem Wrote: ------------------------------------------------------- > the commands mentioned earlier to boot from usb do > not work for me, can there be any other options > for wloader to initiate usb memory? > > I don't have any previous linux kernel in memory, > just a wloader. I dont have any idea about wloader. Others should answer this.by bodhi - Debian
Re: NSA320 fails uboot after upgrade debian buster to bullseye - 4 weeks ago
Bandicoot, Sure, you can go ahead and install 5.19.2 again. dpkg will just overwrite the current 5.19.2. Or if you want to, you can remove it before installing.by bodhi - uBoot
Re: Onespace X5 (Armada 385) Question - 4 weeks ago
The stock DTB is too old. So I create a new DTS for this box based on armada-385-db-ap.dts. Please try the attached DTB!by bodhi - Debian
Re: NSA320 fails uboot after upgrade debian buster to bullseye - 4 weeks ago
bandicoot, > I got it to run again by doing a fsck (appeared to > be nothing wrong?!) and copying uImage and uIntrd > from your rootfs to /boot on my disk, thanks. Cool! so now you can reinstall the kernel with linux-image-5.2.9-kirkwood-tld-1 using dpkg -i. I would do that to make sure it's OK. I think after that, whatever file system errors will go away. Not sure why fsby bodhi - uBoot
Re: Debian on Dell Wyse T10 / T50 - 4 weeks ago
wildhem, > maybe it can help give our devices freedom? > https://lore.kernel.org/all/20220102002841.gl4oienifm2nv4bs@pali/T/ I was close as you can see :) but I need to do some more testing with a rebuilt stock u-boot for UART booting. Been trying to get soem free time before I can get back to it.by bodhi - Debian
Re: Onespace X5 (Armada 385) Question - 4 weeks ago
JayX, OK so the Reference Board DTS cannot be used for this box. Let's go back to the ubuntu DTS. And boot with kernel on eMMC, but with rootfs on USB. - Create the rootfs on USB, like I posted before Quote3. Create uImage with DTB appended. cd /media/sdb1/boot cp -a zImage-5.13.8-mvebu-tld-1 zImage.fdt cat dts/ubuntu_armada-38x.dtb >> zImage.fdt cp -a uImage uImage.orby bodhi - Debian
Re: NSA320 fails uboot after upgrade debian buster to bullseye - 4 weeks ago
bandicoot, As always, next time please post the entire serial boot log, so I don't have to guess. I assume you are running 2017.07-kirkwood-tld-1 u-boot? Quotedevice ide 0:1 ext4fs_devread read outside partition 18446744073262735360 Usually this error indicates the file system is corrupted. Quoteloading uImage ... ** Bad device usb 0 ** loading uInitrd ... ** Bad device usby bodhi - uBoot
Re: Onespace X5 (Armada 385) Question - 4 weeks ago
JayX, > The stock U-Boot may disable USB function in some > way.So I am trying to boot with eMMC directly. Yeah, looks like the kernel could not detect the eMMC or SD device during boot. Likely because the DTS (ie. DTB) is old and the binding does not match with new kernel binding. ============== Try booting with this reference board DTB: /boot/dts/armada-388-db.dtb. It can beby bodhi - Debian
Re: Onespace X5 (Armada 385) Question - 4 weeks ago
JayX, I need to check the kernel config to see if MMC was configured in or not. None of the Marvell Armada boxes we support has MMC, yours is the first box that does. So it might be the case that I did not have MMC in the kernel config, or it must be loaded explicitly from module. In the mean time, since this box has USB, try booting with USB roots using the USB 2.0 slot. Create the USB rooby bodhi - Debian
Re: Onespace X5 (Armada 385) Question - 4 weeks ago
JayX, QuoteBut I dont have uInitrd in the latest post.So I just bootm uImage. That's not correct. You need to boot with uInitrd, it is in the rootfs /boot folder. So now that you haved populated the rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 on eMMC (note that it should be exactly the same way of ussing SD card). Do the Step 3 to create uImage. And then boot this way,by bodhi - Debian
Re: Onespace X5 (Armada 385) Question - 4 weeks ago
JayX, You did not do what I posted above.by bodhi - Debian