dingo, > The added file contains the complete serial log > from a normal boot from uboot to login. Your log got cut off, missing 5 seconds. QuoteStarting kernel ... [ 5.818432][ T1] printk: console enabled [ 5.828194][ T1] printk: bootconsole disabled Please post the missings 5 seconds from dmesg (It looks like you need to adjust bootargs envs). dmesg Alsoby bodhi - Debian
mah941, > > Max mount count for / (mmcblk0p2) partition > (14/10) > mmcblk0: retrying using single block read > mmcblk0: error -110 sending read/write command, > response 0x0, card status 0x480b00 > end_request: I/O error, dev mmcblk0, sector 12272 I'm not familiar with this board. But is the MMC card removable? or is it eMMC?by bodhi - uBoot
DS214se, It's a different board. So it's not applicable.by bodhi - uBoot
MM & cmp18, Thanks for the log. Yes, the i2c pinctrl error need to be fixed before we can see the hub spins up or not!by bodhi - Debian
DS214se, Good works! > Lastly, is there a way, using UART, to save the > entire firmware on an USB stick or HDDs? > I've seen that the firmware chips can go bad, > too. SSH into the running DSM OS. And use command line to dump the flash partitions to the USB/HDD drive. But first, you need to post the serial console boot log so I can give precise commands to do thaby bodhi - uBoot
dingo, The NSA310S and NSA320S are clones (88f6702 SoC). Sounds like this 86946 is a Medion box also with 88f6702 SoC, the md86783 DTB is the right one to use. Check the LEDs ls -l /sys/class/leds/ Now try testing it by turning OFF and ON: echo none > /sys/class/leds/md86783:blue:sys/trigger echo default-on > /sys/class/leds/md86783:blue:sys/trigger Do the same test for /by bodhi - Debian
> Funny how these boxes can consume all spare time > when you're not looking. :) yup! one thing led to another....by bodhi - Debian
Kurlon, > I haven't tested with stable Debian, but on my 13 > test setup on a GoFlex Net I'm seeing a massive > influx of modules get loaded by... something at > startup and I haven't been able to nail down why. Probably bug in Debian testing and/or systemd. I have not seen this. > [ 0.000000] [ T0] Linux version > 6.12.5-kirkwood-tld-1 (root@by bodhi - Debian
Hi Trond, > I recall we removed the audio controller node from > the DTB and the time lag was reduced a bit. Was > that 4.9 s/min ? or is 4.9 s/min the original > lag? > > Originally, the lagging was between 6 and 7 s/min > (see > https://forum.doozan.com/read.php?2,133814,133814#msg-133814). > Thanks! based on that, the kernel drivers seems to be theby bodhi - Debian
Jungle, > Is this going to be an issue when using unattended > updates? If you don't reboot automatically after unattended upgrades, then there is no problem running the system. The potential issue is when you reboot the system after unattended upgrades. The system should boot OK with the old initramfs (in the old uInitrd). But things might have changed in the rootfs relatedby bodhi - Debian
Kurlon, Very nice! There are countless numbers of USB DisplayLink users out there who will benefit from this. I'll change the thread subject and make this a sticky thread.by bodhi - Displays
Timo1979, > I want to try install debian onto my old good > Zyxel NAS326. > But before I begin, I have some questions. > 1. In case of NAS unable to boot after modifying > u-boot environment, I want to be able to connect > with serial console and revert environment to the > original state. > I have an USB-UART converter with > "3.3V / 5V" switchby bodhi - Debian
Hi Trond, > That is 4.9 s/min which is about the same as 5 > months ago. I recall we removed the audio controller node from the DTB and the time lag was reduced a bit. Was that 4.9 s/min ? or is 4.9 s/min the original lag?by bodhi - Debian
Kurlon, > So, just went through this battle. I can say, the > new DRM version of the driver works well, damage > is supported, screen corruption seems minimal. > Running Firefox remote to my GoFlex via direct tcp > X11 (no SSH tunnel) I was able to do full screen > video at 1280x720. Cool! it would be great if you can post your kernel and xorg config. I've noby bodhi - Displays
MM, OK. Let's use 0x1a as you've reported seeing in u-boot above. 0x64 is most definitely irrelevant.. QuoteMarvell>> i2c probe Valid chip addresses: 1A 64 Attached is the DTB, also the DTS so you guys can double check what I did. ===== [ 5.267166] kirkwood-pinctrl f1010000.pin-controller: pin PIN8 already requested by f1012100.serial; cannot claim for f1011000by bodhi - Debian
Hi Trond, Please recreate your uImage using the attached DTB. And try running your timelag test.by bodhi - Debian
MM, > Marvell>> i2c probe > Valid chip addresses: 1A 64 Thanks! Have you tried the new kernel 6.12.6 with a USB drive attached yet? if you did, please post dmesg.by bodhi - Debian
Hi Trond, > I have successfully installed Linux kernel version > '6.12.6-mvebu-370xp-tld-1' on a Readynas RN102. It > seems to work a expected. Output from 'dmesg' > attached. Thanks for the report! > > BTW, did you find anything interesting related to > the lagging system time in the boot log with stock > firmware posted on November 19tby bodhi - Debian
https://github.com/systemd/systemd/releases QuoteAnnouncements of Future Feature Removals: * Support for System V service scripts is deprecated and will be removed in v258. Please make sure to update your software *now* to include a native systemd unit file instead of a legacy System V script to retain compatibility with future systemd releases. 1. For those who aby bodhi - Debian
adrien60, > Kernel works great, thks ! > > Additionally, I could verify that the 4 disk leds > can be triggered on my RN104 :) > Cool! > The leds are in inverted order :) as long as we know the order, and can control them, I think it's OK for now. I'm guessing Arnaud (the original developer of the RN104 DTS) did not notice this.by bodhi - Debian
Kernel 6.12.6-mvebu-370xp-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
Alex, > Besides, if you see the openwrt as an add-on to > already existing debian installation I do see it as a rescue system. Debian is something you run everyday. So we were done with this goal when you can run it as the ReadyNAS Duo V2. Anything more is just an experiment to see what-ifs. > But, because that RTL8188eus wifi device is still > not working, > (it hasby bodhi - Rescue System
cmp18, Do you have any instruction for people to do it on their own? or at least the log of how did you do it?by bodhi - Rescue System
Kernel 6.12.6-mvebu-tld-1 package has been uploaded. See 1st post for download link. Please create a new thread for any installation problem or questions.by bodhi - Debian
Alex, At the moment, I'm not interested in any of that. I'm intererested in what I've recommended for your next step (the 3rd bullet): https://forum.doozan.com/read.php?4,138683,138712#msg-138712 QuoteSummary: - No change to the rootfs is necessary. - Just run the system as the ReadyNAS Duo v2. - Find a way to replace the uImage in the kernel volume with the MOI+by bodhi - Rescue System
One thing I have not found is what to use for the I2C address in the DTS, so I used the default address. Hopefully it will work (if PromWad does not do anything fancy!).by bodhi - Debian
I've released 6.12.6-kirkwood-tld-1 kernel. https://forum.doozan.com/read.php?2,12096 QuoteUpdated 20 Dec Nov 2024: Kernel linux-6.12.6-kirkwood-tld-1 package has been uploaded. The following features were added/updated This kernel has new DTB for both PromWad Wtplug and Thin Client. So save your DTB before installation. Happy New Year!by bodhi - Debian
Kernel linux-6.12.6-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
Alex, > thats the RTL8188EUS WIFI chip on the board > still not being used, openwrt or debian > the same thing. Is it a pci > or usb thing? It's USB. > 1. ubinized uImage > kernel.ubi OK > 2 mkfs.ubifs -o rootfs.ubifs rootfs/ > 3. ubinized rootfs.ubifs > rootfs.ubi Should not do 2 and 3 above. You alread have a working roofs for ReadyNAS Duo V2by bodhi - Rescue System
Work in progress to install OpenWrt on unsupported boxes. Using the TBS MOI+ as example. https://forum.doozan.com/read.php?4,138683by bodhi - Debian