Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: Time is lagging substantially on Netgear ReadyNAS RN102 and RN104 - 16 days ago
Trond, That was a shot in the dark on my part :) > Is time good on your Mirabox (with NTP disabled)? > Are you able to make it lag or gain by modifying > it's clock definition? I've been pretty busy with other things so have not booted up the Mirabox yet! I think we need to read the driver code to see what's going on. ./drivers/clocksource/timer-armada-37by bodhi - Debian
Re: Bricked Synology DS218j - 16 days ago
> Ok, I have found a package from Synology which is > not encrypted and will try to create an uImage > using the RS816 DTB. I assume that is the best. Not really. You need the kernel images from DSM, similar to ones you used before. tftpboot 0xd00000 zImage tftpboot 0x800000 rd.bin tftpboot 0x1000000 dtbdump_3.dtb Also look for Rescue FW that run from USB upon power up.by bodhi - uBoot
Re: NAS326 how to boot with UART? - 16 days ago
@martini, Nice! It will come in handy when I start working on u-boot for this box. @mijzelf, QuoteThat is a neat trick. Do you have any idea why it works? I'd say that for ddr training it doesn't matter if the binary is read from uart or from nand. So which subtle effect is causing this? The ddr training is the same, but IIRC these old bin_hdr binaries have something in it thby bodhi - uBoot
Re: Time is lagging substantially on Netgear ReadyNAS RN102 and RN104 - 17 days ago
Hi Trond, Please try these 2 new DTB. Basically, the new node in this version is + timer@20300 { + clock-frequency = <600000000>; + status = "okay"; + }; +by bodhi - Debian
Re: Time is lagging substantially on Netgear ReadyNAS RN102 and RN104 - 17 days ago
Hi Trond, Yes the clock source is the common armada_370_xp_clocksource, due to those compatible attributes in the node. I have not booted up my Mirabox yet. But here is the old log. Mirabox [ 0.000000] Switching to timer-based delay loop, resolution 53ns [ 0.000006] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114840871909ns [ 0.007894] clocksource: armada_by bodhi - Debian
Re: Bricked Synology DS218j - 18 days ago
elexidor , > I have no clue what I want or need. :) At this > point I just want to bring up the Synology DSM > again. OK. I was not aware that is the only goal you are after :) Then there is no need to do much Debian-wise further. You should look for DSM firmware kernel image and initrd and then write them to flash. > Swap: 0B 0B 0B Swap fby bodhi - uBoot
Re: Time is lagging substantially on Netgear ReadyNAS RN102 and RN104 - 18 days ago
HI Trond, > My understanding is that the kernel reads the RTC > when booting, but maintains it's own time > thereafter. Of course, you're right. I meant to say "driver" above and instead mispoke as RTC. I'm thinking some clock/time driver is broken, not hardware. > NTP normally compensates for drift, > but on the RN102 and RN104 the drift is soby bodhi - Debian
Re: Bricked Synology DS218j - 19 days ago
elexidor, > Attached is a log file from start to finish at the > debian login, then a lsblk -f command to show the > file system and finally a reboot command. Congrats! you're almost done. The reason the reboot does not work because you have not set up the u-boot envs to boot automatically and save them to flash. So at the u-boot prompt you will need to execute them againby bodhi - uBoot
Re: Bricked Synology DS218j - 19 days ago
elexidor, > The file system thing is little bit strange. I do > not have an Ubuntu/Linux machine so I used > DiskGenius on Winows for creation of the USB disk > partion/filesystem (ext3). That explained the weird problem. As always, the rootfs must be created natively on a Linux system. > root@debian:~# lsblk > sda 8:0 1 239G 0 disk > `-sda1by bodhi - uBoot
Re: Bricked Synology DS218j - 20 days ago
I was reponding to previous post wiht the log synology_ds218j_boot_5_2_9_maintenance.txt.by bodhi - uBoot
Re: Bricked Synology DS218j - 20 days ago
I see. Everything was looking really good until the rootfs mounting. The rootfs was created incorrectly. I mentioned this above QuoteMake sure you follow the instruction verbatim. Being root user (not sudo), create a single partition, format it using Ext3 (not Ext4) file system, and label it as rootfs. When you run a Ubuntu VM or similar, you need to use command line to create the partitiby bodhi - uBoot
Re: Bricked Synology DS218j - 20 days ago
elexidor, > I have a feeling we're getting closer with 5.2.9 > :) Yes! > However, If I use the following envars mentioned > erlier in this thread a lot of things happening. > It checks the root file system and comes to 92.7% > according to the attached file. At the end a > maintenance shell is started and I can explore the > USB-stick: What do you meby bodhi - uBoot
Re: Cubox 510 1st gen kirkwood + debian 11 - 21 days ago
CUBOX_K, As I mentioned, I have not tested sound on my T5335z box. So not sure how to help.by bodhi - Debian
Re: Bricked Synology DS218j - 21 days ago
Here is what salahuddin did to boot this box with RS816 DTB. Quotesetenv load_image_addr 0x02000000 setenv load_initrd_addr 0x3000000 setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0; scsi read $load_image_addr 0x5000 0x2F00' setenv load_initrd 'echo loading uInitrd from raw HDD ...; scsi device 0; scsi read $load_initrd_addr 0xA000 0xAF00' setenvby bodhi - uBoot
Re: Time is lagging substantially on Netgear ReadyNAS RN102 and RN104 - 21 days ago
Hi Trond, > The RN102 is now about 4 s ahead. I would say the > RTC is off the hook? I would not say that RTC is off the hook. Given we know RTC is working with a cron job, the system clock should have been automatically updated using RTC without that cron job. So the issue could be somehow related to RTC driver. Did you check dmesg and syslog if there is anything interesting?by bodhi - Debian
Re: Bricked Synology DS218j - 22 days ago
Now I've checked the main release thread and realized that this has been worked on. salahuddin used the the RS816 DTB. Quote- Thanks salahuddin for bring up the Synology DS218j. https://forum.doozan.com/read.php?2,76314,122749#msg-122749 Must be my memory is no longer it used to be after the pandemic :)) Please use the RS816 DTB for testing.by bodhi - uBoot
Re: Bricked Synology DS218j - 22 days ago
This test is better: synology_ds218j_boot_uimage116_k607_only.txt But it seems you did not have the USB rootfs attached to the port. Also if you could, remove the HDD from the slot. Reason: the USB rootfs is going to be /dev/sda1 if it is the only storage drive attached. The HDD is always assigned first, so if there is HDD in slot it will take /dev/sda1. And then the USB will be /dev/sby bodhi - uBoot
Re: Bricked Synology DS218j - 22 days ago
elexidor, This uimage2350_k607 was created incorrectly. It is showing the RS816 being used in the log synology_ds218j_boot_uimage2350_k607.txt ======================= Here is another set of 3 tests (replace uImage with each flavor). setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage bby bodhi - uBoot
Re: GTI Mirabox and Netgear RN120 (Armada 370) Installation & Kernel Upgrade (Linux-5.19.2) - 22 days ago
Hi Trond, echo default-on > /sys/class/leds/rn104:blue:sata1/trigger echo none > /sys/class/leds/rn104:blue:sata1/trigger echo default-on > /sys/class/leds/rn104:blue:sata1/trigger echo none > /sys/class/leds/rn104:blue:sata1/trigger And do the same for sata2. Did the LED turn on/off when set you trigger as above? I double checked the DTS patches, and turn out that I setby bodhi - Debian
Re: Time is lagging substantially on Netgear ReadyNAS RN102 and RN104 - 22 days ago
Hi Trond, > Is the input clock frequency given correctly in > the > dts > file? The input clock frequency is specified > here > by Arnaud Ebalard, the original author of the dts > file, but this is, of course, not really an > authoritative source. I think natisbad.org has been a quite reliable source over the years. And your problem could be the RTC driver anby bodhi - Debian
Re: Netgear Stora - Debian rootfs questions - 26 days ago
spaceballz, > All went perfectly Bodhi. Apart from those usb bad > device messages. Is that just because I have no > USB inserted? Exactly. Because the booting script in the envs scans everything that would be available for a Kirkwood box. To make it less noisy and faster boot, set the envs to the way you boot this box: SATA rootfs and then USB if no SATA drive. fw_setenv bby bodhi - Debian
Re: debian on synology ds214 - periphery issues - 27 days ago
Oh, and please change the thread subject to: Debian on Synology DS214 If you could not as a normal user, I'll change it for you.by bodhi - Debian
Re: debian on synology ds214 - periphery issues - 27 days ago
Hi Martin, Could you post a summary to help future users looking for how to install Debian this box. It does not have to be too detailed. Just these information below. Stock u-boot What u-boot envs are used to boot Debian rootfs on USB 3.0 drive Rootfs and Kernel I've attched the latest DTB file in this post: armada-xp-synology-ds214.dtb. My next kernel release (6.1.x-mvebu-tlby bodhi - Debian
Re: Netgear Stora - Debian rootfs questions - 27 days ago
spaceballz, You've missed an important env in running new kernel: dtb_file. You can set it either temporarily using uEnv.txt (see u-boot 2017.07 installation instruction). Or set it permanently fw_setenv dtb_file /boot/dts/kirkwood-netgear_stora_ms2000.dtb When you boot the new kernel, make sure that the uImage is the original one (no DTB appended to it). This is because u-boot wby bodhi - Debian
Re: Bricked Synology DS218j - 28 days ago
I recall Martin has reported that the kernel 5.13.8-mvebu-tld-1 might be a bit flaky, especially testing different DTB from other boxes. Quotehttps://forum.doozan.com/read.php?2,133377,133377#msg-133377 - the 5.13.8 kernel was not very stable, but just enough to get install the 6.0.7 kernel, which works very well. Took a few reboots. So if you see problems like a kernel dump about cpu stallsby bodhi - uBoot
Re: Bricked Synology DS218j - 28 days ago
elexidor, > Here is my console log. For some reason I can't > interrupt at the count down but due to the CRC > error it stops anyway just after. Congrats for a good progress! Looks like a lot are working so we know it is close. SPI flash, [ 3.203342][ T1] spi-nor spi0.0: mx25l6405d (8192 Kbytes) [ 3.209084][ T1] 6 fixed-partitions partitions found on MTDby bodhi - uBoot
Re: Bricked Synology DS218j - 28 days ago
- Copy the kernel files uImage116 and uInitrd to tftp root. - Insert the USB rootfs to the box USB port next to the Ethernet port (probably does not matter which one, but in case only one USB port works, try this first). - Power up, interrupt serial console at countdown. - Get the listing of current envs. It will be needed later. printenv - Boot with tftp setenv fdt_skip_update yby bodhi - uBoot
Re: Fw_setenv no longer available in u-boot-tools - 28 days ago
> Joins the club of over 30 > Pogoplug(19), Kace (7), Cisco (2), Globalscale (6) > and Akitio (1)devices. Welcome to the club of pogoplugs fanatics :))by bodhi - uBoot
Re: Bricked Synology DS218j - 29 days ago
> I tried all three files but non worked. It comes to the "Uncompressing Linux... done, booting the kernel." and hangs there. > Unfortunately, I'm a Linux rookie sitting behind > Windows and not sure how to boot from USB... Duh! > :) Of course when I mentioned booting from USB. The first thing you should try is to boot the uImage, uInitrd, and DTB from the USB.by bodhi - uBoot
Re: Bricked Synology DS218j - 29 days ago
elexidor, If you are trying to get Synology DSM to work, I cannot help much. However, you could try to boot Debian on USB. Use the Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2. The DTB files you can try are: In the rootfs folder /boot/dts: armada-385-synology-ds116.dtb armada-385-synology-rs816.dtb armada-385-thecus-n2350.dtb ======= The kernel files corruption is apparenby bodhi - uBoot