Quotebodhi > > Both front buttons do nothing in debian. I > don't > > fully understand how those should be declared > in > > the DTS files, any hints ? > > Look in my patch linux-6.7.5-mvebu-tld-1.patch in > the > tarball > linux-6.7.5-mvebu-tld-1-bodhi.tar.bz2. And > find the armada-385-thecus-n2350.dts. There are 3 > buttons definedby bodhi - Debian
> HWmon > hwmon2 does not exist. It seems like > hwmon1/temp1_input is the SoC temperature, and i'm > not sure hwmon0/temp1_input is working as the > value stays the very same. No fan input so far... That's strange. There should be 3 hwmons. CPU, Fan, and Ethernet. But the order is not guaranteed to be the same for different boards. For example, the DS116: lsby bodhi - Debian
> > So does the power button work OK? > > > No wont work right now but i sorted some other > problems out Yeah, it's nice to have button, but not too important. > Like transferrate > I now get about 38mb/s both ways using XFS > filesystem on both drives > > And im able to boot reliable without errors Cool! > But the problem with thby bodhi - uBoot
Robin, > Thanks for your quick reply. The original RTC > battery was dead, I replaced it before the first > boot and I didn't set the time since. I'll check > tomorrow but it's probably nothing to be concerned > about. OK. > > I felt like the SPI flash issue was indeed minor, > if LEDs and Buttons requires us to edit a separate > DTS forby bodhi - Debian
In any case, we should stop discussing hdd temp here before it gets out of topic of this thread.by bodhi - Debian
> The correct replacement for hddtemp is the > 'drivetemp' kernel module. Load the module as > follows: > > echo drivetemp > > /etc/modules-load.d/drivetemp.conf > > > Then on the next boot the sensors command from > lm-sensors will also report the drive > temperature. > Ray, Yes, I'm aware of drivetemp. I think it is not aby bodhi - Debian
th3l0lb0y, So does the power button work OK?by bodhi - uBoot
Hi Robin, Thanks for bringing up the DS216 box. Well done :) I'll add this to the support list. RTC is working but, [ 2.598291][ T1] armada38x-rtc f10a3800.rtc: setting system clock to 1970-01-01T04:11:32 UTC (15092) Perhaps the battery is dead? did you try to set the date and see if it will keep time correctly? SPI flash is working OK. [ 2.412375][ T1] spi-nor spiby bodhi - Debian
Hi Chris, Sorry, I don't have any IMX6 board, so I have not built kernel for this architecture. Hopefully others will have info for you.by bodhi - Debian
raffe, load_bootm=bootm 0x800000 0x2100000 load_usbuimage=ext2load usb 0:1 0x800000 /boot/uImage load_usbuinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd load_myhdduimage=ext2load ide 0:1 0x800000 /boot/uImage load_myhdduinitrd=ext2load ide 0:1 0x2100000 /boot/uInitrd bootcmd_myhdd=ide reset; run set_mw; run load_myhdduimage; run load_myhdduinitrd; run load_bootm bootcmd=run bootcmd_usby bodhi - Debian
markro76, When you creates the rootfs, you did Step 4 incorrectly. Quote4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time, or running kwboot with latest u-boot image). Please replace kirkwood-goflexnet.dtb below withby bodhi - Debian
> A quick look at the various boot logs shows all > images where the kernel is less than 6 MB boot > successfully. The boot where kernel > 6 MB do not > boot. Does the load address need to be adjusted? > > Ray That's what I'm thinking about, and want to see the boot log and envs. The load addresses are plenty far apart. What it could've meant is thisby bodhi - Debian
raffe, This might be because of this stock u-boot. 1. Do you have the original envs listing of stock u-boot (before setting up the new envs to boot Debian). Please post it here. 2. Try booting again with latest kernel 6.7.5. Power up, interrupt the u-boot count down and printenv And post the bootlog here.by bodhi - Debian
Hi raffe, > I had some problems a few months ago when I tried > to update my LG N1T1 NAS from 6.5.7 to 6.6.3, it > would not boot with the new uImage and uInitrd. It > stopped just after reading them. The problem is that the kernel has not started. > Should I change bullseye to stable > and try aptitude safe-upgrade ? It is not in Debian yet, so upgrading will noby bodhi - Debian
Max, > Is this happening because I used the wrong command > for mkimage I used the updated automated script > which is one or two posts under the one you linked > at ?It uses another mkimage commands > Yes, I forgot that the load address 0x3000000 correct for this box. mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -n initramfs 6.5.7-mvebu-tldby bodhi - Debian
@Max, Boot with USB, log in and do modprobe mmc_block See if it is now initiliazed. If it's OK, add the mmc_block module to initramfs: https://forum.doozan.com/read.php?2,134563,136672#msg-136672 Note that since you are running 6.5.7, the mkimage command should be: mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.5.7-mvebu-tld-1 -d iby bodhi - Debian
barroshelder, > I was looking for alternatives and found this one > https://rockstor.com/linux-btrfs-nas-server.html. > It is open source and the "ready package" runs on > openSUSE, but the Rockstor backend is developed in > Python and the frontend in Javascript (EJS): > https://github.com/rockstor/rockstor-core > Do you thing it would be possible to run onby bodhi - Debian
> An > attempt of automated installation script by mmm > which can be used as a reference My bad. I forgot mmm has written this. Yes, that script should be used as a reference.by bodhi - Debian
QuoteThese are the numbers that I stuck to. However when copying a 2Gb mkv video file to and from the CenOS 7 server, the file transfer started off at around 60MB/s but within 10 seconds ramped down to 20. Try again after you set the NFS thread. And check the swap size while it is running. If there was any increase in swap size, set the swapiness to 1.by bodhi - Debian
@Tedious_1, > Also, the suggestion to change the threads does > not work. That was a temporary change. To make it permanent, change the default settings in /etc/default/nfs-kernel-server # Number of servers to start up RPCNFSDCOUNT=1 Restart the service and verify /etc/init.d/nfs-kernel-server restart cat /proc/fs/nfsd/threadsby bodhi - Debian
QuotePL2303TA USB-TTL Image This looks good. Don't connect the 5V, only connect RX to TX, TX to RX, and GND to GND. QuoteI used this picture as a basis for wiring. Image's page The serial pinouts above is good. Note: pay attention to the Pin 1 marking. Many Synology NAS boxes have different orientation (sometime the header is upside down, sometime it's right side up). Theby bodhi - uBoot
Krisztian12005, > How can i do the unbricking? > Also there is anything what i need to have for it? As I recalled here is where we left off: https://forum.doozan.com/read.php?2,135749,136022#msg-136022 So there is nothing comming out of the serial console, no matter what serial converter you used? ======= Here is a successful kwboot run on the DS411slim (by Nefarious19):by bodhi - uBoot
maxt1907, We don't have the installation instruction written for this box yet. But basically you'd start from Mischif's post here: https://forum.doozan.com/read.php?2,134563,134729#msg-134729 QuoteI create a FAT32 partition mounted at /mnt/bootfs to hold the kernel/initrd/wloader.conf, then I create an ext3 filesystem mounted at /mnt/rootfs to hold the rootfs. From thby bodhi - Debian
raffe, > I did find something strange: The device names for > hard drives and USB-drives can switch between > boots. > > This is both from the same device. > > Just after I have updated from 6.6.2 to 6.7.5, > before reboot USB is: > sdb1: > > root@debian:/boot# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 1 1by bodhi - Debian
raffe, > Naturally it booted up just fine when I had it > connected with serial console (and I do not need > to disconnect wires to make it work). That's interesting. So the serial behavior on your box is different from what I recall on my box.by bodhi - Debian
Unfortunately, I am not using btrfs on any of my NAS. Perhaps others might chime in.by bodhi - Debian
> I setup a btrbk remote backup that transfers btrfs > subvolumes. Source is a amd64 machine targetting a > NSA325v2 with latest kirkwood kernel and bookworm > tarball. > > It fails with the error message "ERROR: ... > invalid tlv in cmd tlv_type = 816" on the target > machine. > Any advice how to continue? > If you have not done this. The fiby bodhi - Debian
raffe, > It boots with a USB and continue with the rest on > HD. But it never booted up. Wife want me out for > dinner, so I did not have much time to check why. > Then I read > https://forum.doozan.com/read.php?2,32146 "Updated > 16 Dec 2023: Rootfs > Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 has > been uploaded. ". Is this something I need to do?by bodhi - Debian
Daniel, The rootfs is basic rootfs with only a few necessary packages installed. It is a debootstrap rootfs, and the following packages installed on top: Quotehttps://forum.doozan.com/read.php?2,12096 - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-by bodhi - Debian
This is quite serious for Internet facing servers. SSH was compromized by a backdoor in xz-utils (specifically xz versions 5.6.0 and 5.6.1) https://lwn.net/Articles/967180/ QuoteAndres Freund has posted a detailed investigation into a backdoor that was shipped with versions 5.6.0 and 5.6.1 of the xz compression utility. It appears that the malicious code may be aimed at allowing SSH authentby bodhi - Debian