arcNumber should be 2097 for the rescue system. Do you keep a log of you old envs? something else might be missing.by bodhi - uBoot
I should have mentioned this new feature (described in the first post): Quote- The default envs were modified slightly to make it more robust. If you are upgrading u-boot, there is no need to reflash, but worth taking a look at the envs text file to see the differences.by bodhi - uBoot
For anybody who has this T5325 box and only follows this thread. I've released 2016.05-tld-1 U-Boot images in the main u-boot release thread.. Please go there for general information about the new u-boot-2016.05-tld-1.by bodhi - uBoot
I've released 2016.05-tld-1 U-Boot images. Please see 1st post for download link.by bodhi - uBoot
Francesco, I don't have this box so I'm not sure.by bodhi - Debian
nibbler , QuoteFirst I set the device to boot from the USB with the "usb-debian-uboot.tar.gz". Then I installed the system following the instructions from here and using a single ext3 partition. Somewhere in this thread: http://forum.doozan.com/read.php?2,14351,page=1. You'll find the u-boot envs adjustment to boot with stock u-boot. The errors in indicated that your u-bootby bodhi - Debian
Install locale: apt-get install localesby bodhi - Debian
Create rootfs on USB drive following instruction from the kernel/rootfs thread: http://forum.doozan.com/read.php?2,12096. In section: QuoteUpdated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1. To boot with stock u-boot, pay attention to section 4 Quote4. Create uImage with embedded DTB for booting with oldby bodhi - Debian
> Tried booting to a fresh USB drive created from > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. > Then followed the instructions for installing the > Kirkwood U-Boot. I had to install mtd-utils, but > after that the instructions were successful and > I'm now booting straight into the USB drive!!! That was what I suspected above why you did not get network cby bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > > :o) you been having a tipple?? > > > > Too early in the day for that :)) > > Care to share? > > WTF is tipple....I realize my geezerhood may > prevent me from being aware of moderby bodhi - Debian
> :o) you been having a tipple?? Too early in the day for that :))by bodhi - Debian
Peter, > It boots from rescue, even though You wrote "NOTE: > the envs below are not to be used in your box. > They are for example only.". These were the same > settings before flashing the ENVs (except bootcmd > value). I should have worded it a little bit more clear (late night and all that :). These were from my log long ago. So I can't be sure if I hby bodhi - uBoot
Francesco, > > i've applied first option and work fine. Now for > save the boot parameter in eeprom, what should I > do? > 1. Sanity check: - Boot up with serial console again. - Interrupt serialconsole - Enter the evns like you did before - Copy this serial console log to your note to reference it later - Boot into Debian like before 2. Do it for real:by bodhi - Debian
notoneofmyseeds, Best way to do this is: create a new rootfs on USB drive (wheezy or jessie where appropriate). Do all the experiments on it and keep a log. Backup as you go, when you think it is messed up and you've lost track then just restore the last backup. You might do many iterations until you get a good installation. And then go back to your log and make clean procedure, do real iby bodhi - Debian
You don't have any rescue set up in your envs. They are your box-specific. Look back to where you save your current envs before flashing u-boot and u-boot envs. They look like this. NOTE: the envs below are not to be used in your box. They are for example only. rescue_installed=1 rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdby bodhi - uBoot
Add the nameserver to your resolv.conf. cat /etc/resolv.conf nameserver 8.8.8.8by bodhi - Debian
Peter, The default envs does not activate netconsole by default (this is your box-specific). You have to do it explicitly. This is to avoid confusion for people who has serial console and loose it temporarily if netconsole is activated by default. To activate netconsole, copy and paste this command in Debian, don't type it (because a typo here will be really bad, could lock you out).by bodhi - uBoot
Lennong, Cool :) everything looks great. > > Thank You for your work and patience! A donation > is coming, where do I put it? No need to. But if you'd like: bodhi's corner.by bodhi - uBoot
Ah, I see. Did you flash the new default uboot envs image? And if you did, did you restore your box-specific envs as instructed? If you like, interrupt serial console, list the envs with printenv and post here.by bodhi - uBoot
I see. It was a botched attempt to install OpenWrt. So it can not boot either OpenWrt or Debian. You said you can adjust the envs to boot into Debian, let's do that again. Adjust the envs, but before booting, printenv and then boot. The dmesg error that you've listed previously is not relevant to Ethernet. As long as you have ethaddr set correctly, then it should be OK. Soby bodhi - uBoot
Looks like I misunderstood what you said. Is the Debian rootfs booting OK?by bodhi - uBoot
Francesco, Look at 2 possible reasons. Mount the rootfs on Ubuntu and examine it. 1. Our bootargs expects the rootfs to be labeled rootfs (lowercase). Quotesetenv usb_make_boot_args 'setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:$(uboot_size)@$(uboot_start)(uboot),$(env_size)@$(env_start)(env),$(kernel_size)@$(kernel_start)(zImage),$(initrd_size)@$(initrd_start)(initrd),3by bodhi - Debian
notoneofmyseeds, > I don't have this directory: > /usr/share/squeezeboxserver/CPAN/arch/5.20/ > > I created /usr/share/squeezeboxserver/ > > used wget to grab the file from the link with it > and extracted there but it did not work. > > sent earlier. But his instructions on how to > install does not work for me. And this is perhaps > what Iby bodhi - Debian
notoneofmyseeds, He (daniel) said it is a binary file, ready to install, not source code. QuoteYou can download them here: https://server.vijge.net/static/sque...i-64int.tar.gz Just extract this to /usr/share/squeezeboxserver/CPAN/arch/5.20/ After that you can start LMS with "sudo /etc/init.d/logitechmediaserver start" He has a GitHub, but not apparent how to download source foby bodhi - Debian
Peter, 1. Your envs is old. It means you did not flash the new default envs? 2. When rescue system is booting like that, your USB rootfs is having problem. This is not even to the point where FDT is coming to play. 3. The amber LED indicate that the rescuse system is stuck. Try a. Mount your USB rootfs on another Linux box and fsck it for error. b. List some info and kernel files (assby bodhi - uBoot
Last post moved to its own thread: http://forum.doozan.com/read.php?3,28599,28599#msg-28599by bodhi - uBoot
notoneofmyseeds, > This person, went through the trouble and put the > file here: > > https://server.vijge.net/static/squeezebox/arm-lin > ux-gnueabi-thread-multi-64int.tar.gz Where is the writeup for this file? meaning discussion, or description that said this is for jessie?by bodhi - Debian
> Particularly interesting is the approach the the > cutting edge rolling distro's have taken. They followed the first law of computing :)by bodhi - Off-Topic
If you have a lot of time on your hand, this is entertaining and informative: https://lwn.net/Articles/690151/ But no systemd debate please :) we don't want any flame war.by bodhi - Off-Topic