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
maframan Wrote: ------------------------------------------------------- > Hi Bodhi, > > is possible that my serial have problem because I > run my ubuntu on VMWare? > Maybe you should try without vmware, you say? > > Thanks and regards > Francesco Yes, it's possible a VM problem. If you have a Mac then see here: http://forum.doozan.com/read.php?3,26098,by bodhi - Debian
Mr Dini Wrote: ------------------------------------------------------- > Hi! > > I have a ZyXEL NSA320S and I am interested to boot > up a Debian system eith a fresh kernel on it. > Because the old (2.6.31.8) kernel has a lot of > disabled thing (for example the wifi support) and > if I create a custom kernel it works, but a bit > buggy... > > So I decidby bodhi - Debian
maframan Wrote: ------------------------------------------------------- > Add other information found on /var/log/syslog on > my ubuntu: > > > Jun 16 00:22:21 ubuntu kernel: [ 1481.008195] > pl2303 2-2.2:1.0: pl2303_vendor_write - failed to > write [0008]: -110 > Jun 16 00:22:21 ubuntu kernel: [ 1481.276319] > pl2303 2-2.2:1.0: pl2303_vendor_write - failed tby bodhi - Debian
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Any disk would be fine. nanddump outputs a > binary > > file so Linux does not care. > > I see why I was confused. You are assuming doing > the nand dump from within a running bodhi Debian > rootby bodhi - Debian
LeggoMyEggo Wrote: ------------------------------------------------------- > Where am I dumping the file to, an attached USB > flash drive? That's the part (no pun intended) I > don't understand. If FD, should it be ext3 > partition or is FAT ok? Any disk would be fine. nanddump outputs a binary file so Linux does not care.by bodhi - Debian
Francesco Wrote: ------------------------------------------------------- > Hi Bodhi, > > in serial console, after set env with the follow > configuration > > usb_make_boot_args=setenv bootargs > console=ttyS0,115200 > mtdparts=orion_nand:$(uboot_size)@$(uboot_start)(u > boot),$(env_size)@$(env_start)(env),$(kernel_size) > @$(kernel_start)(zImage),$(initrby bodhi - Debian
Lennart, Something is wrong about your rootfs. I think your best approach right now is to create a USB rootfs type Ext3. Using the Debian 4.4.0-kirkwood-tld-1 like you did before. And boot with that, and examine your SSD rootfs. Note that the USB rootfs will need to have a different label. So label it usb_rootfs to make it different from the main SSD rootf. And then boot it this way:by bodhi - uBoot
Francesco, No, you are just too careless :) be a very careful when messing with u-boot envs or u-boot. To recover, starting form this post: http://forum.doozan.com/read.php?3,25120,25668#msg-25668 Download that mtd0.bin file and run kwboot as I described in next post after that: ./kwboot -t -B 115200 /dev/ttyUSB0 -b mtd0.bin -p If it load and runs, when you see the countdown, typby bodhi - Debian
Lennong, Missed the run cmd :) setenv uenv_load 'ide reset; setenv uenv_loaded 0; for devtype in ide; do for disknum in 0; do run uenv_read_disk; done; done' run bootcmd_uenv printenv run scan_disk run set_bootargs run bootcmd_execby bodhi - uBoot
Francesco, I said above 2. If the test in step 1 is successful then go ahead and set up booting with USB rootfs. Your step 1 was not successful. Step 2 should not have been executed. The only advice I have now is to unplug the power, and wait a few minutes - power up - immediately pounding on the keyboard to interrupt serial console. - If you see the u-boot prompt then you are Oby bodhi - Debian
Francesco Wrote: ------------------------------------------------------- > Hi Bodhi, > > now the storage does not start and remains with > display blue and the fan at max speed. > The serial console does not work. > > Thanks > Francesco Unplug power. Wait a few minutes and plug it back in.by bodhi - Debian
Lennong, Too bad that your rootf is on your SATA disk, if it were on a USB then it is much more manageble. This problem is quite easy to solve with USB drive where you can unplug it and mount on another Linux box. But anyhow, we'll fix it in your configuration (but if your HDD does not have anything in it, then consider booting USB first). Power up and interrupt serial console, and theby bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > I just acquired a Pogoplug E01 the original Cloud > Engines plug. The internal board is manufactured > by GlobalScale Technologies and indicates a REV3.0 > It is a 1.2Ghz 88F6281 with 512MB Hynix NAND and > 256MB Elpida RAM. There is only a single USB 2.0 > and Gigabit Ethernet via the 88E1116Rby bodhi - uBoot