Dieter, > uboot is updated and so on. Cool! > I booted lede, but the opkg installation failed: joerg should be able to help you.by bodhi - Rescue System
radsfaninlv, Your u-boot is an older version, so it has problem dealing with a not-perfect USB drive. Quote> U-Boot 2011.12 (Feb 20 2012 - 21:21:59) Pogoplug E02 scanning bus for devices... EHCI timed out on TD - > token=0x80008c80 But this happened a lot in the past. And we just try a different USB thumb drive to make it work. Also try plugging into a different USB port.by bodhi - Rescue System
@radsfaninlv , What joerg_999 said > your Pogo and boot-envs seems to be ok, bot > not your USB Stick See your boot log USB0: USB EHCI 1.00 scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80 unable to get device descriptor (error=-1) 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Unknown command 'ideby bodhi - Rescue System
> I can see the "gpio-keys" section, which is not > working as we want at the moment. It also > specifies some pins. > But why does it also reference this section: > > pinctrl@18000 { > pinctrl-names = "default"; > > pmx_power_button: pmx_power-button { > marvell,pins = "mpp49"; > marvell,functionby bodhi - Debian
> Haha, oh no - still no time to take it out of the > box? :) I'm afraid to burn the whole weekend on the new toy :)) I did open it to check it over, but have not disassembled the case yet. But you are doing a really great job as collaborator, I have not even thought I need to get to it hands on! KEY_116:/usr/bin/logger -s -i "POWER button pushed" KEY_408:/usrby bodhi - Debian
Manuel, GPIO keys testing. apt-get install esekeyd And set it up in the conf file. Here is my test version, where the button push will print out to syslog. Once a button works, replace it with your own action or scripts to do certain things such as shutdown, backup,.... cat /etc/esekeyd.conf POWER:/usr/bin/logger -s -i "POWER button pushed" RESTART:/usr/bin/logger -sby bodhi - Debian
Gitsov, Not very interested to run the kernel in NAND! I think running it in NAND will just delay security updates and limit your system storage, while running it on USB and HDD will be a an up-to-date system all the time. With that said, everybody has different needs. So if you do want to pursue that, then I would recommend running the latest u-boot, which will solve all weird problems yoby bodhi - uBoot
> > My understanding is ALARM (ARCH Linux ARM) has > changed to block the default SSH to make it a more > secure system. I don't need this and am looking to > simply revert the configuration back to a normal > ssh on port 22. I am not worrying this device will > get hacked or not. Then I'd suggest you ask how to do this at ALARM site.by bodhi - uBoot
@MisterD, It is best to upgrade u-boot. Eventhough it is possible to boot Debian with stock u-boot, it will take a bit of works to setup. We are too far beyond stock here in this forum, so you would need to do it yourself (of course I'll help when there is trouble). As Gitsov described above, it is not difficult to recover from bricking if you have serial console and can kwboot into thby bodhi - uBoot
Manuel, > 1. There are actually 6 LEDs: LED2 LED1 and LED4 > were missing in this test. Do you have the board inside the case? I think it is more helpful if we confirm that the LEDs on the outside are what we think they are. For example, Quoten2350:white:sys is indeed the system LED and it turns on when we do "echo default-on" > At the moment LED2 is blinkinby bodhi - Debian
> I did dpkg the packages :), all but the initrd was > installed, it's very odd! List the /boot in chronological order. It must be there. If not, there is something wrong! ls -lart /boot And you can always reinstall the same kernel on top of the same running one.by bodhi - Debian
mpmc, > On the B however, it was a little harder as there > was no "initrd.img-4.16.1-kirkwood-tld-1" included > to the tars so couldn't generate the uinitrd. > Thankfully I was able to copy it over from the S & > it booted up fine! Copy the initrd.img-4.16.1-kirkwood-tld-1 over from a running system would work, as you did! However, that 's is justby bodhi - Debian
MisterD, > The bricked Stora is now restored to it's original > state, thanks to your help! Cool! > I would like to run a Debian OS on this box. Does > that need to be written to the NAND or can it run > on the drive? Could you please show me in the > right direction? > We run the Stora on USB or HDD. There is no need to store it in NAND. Stora rootfby bodhi - uBoot
Manuel, GPIO LEDS gpio-leds { compatible = "gpio-leds"; pinctrl-0 = <&pmx_sata1_white_led &pmx_sata1_red_led &pmx_sata2_white_led &pmx_sata2_red_led &pmx_sys_white_led &pmx_sys_red_led>; pinctrl-names = "default"; white_sata1 { label = "n2350:white:sata1"; gpios = <&gby bodhi - Debian
Manuel, It looks great! we have brought up this box successfully! Let’s move on to other minor topics: Saving envs GPIO I2Cby bodhi - Debian
Carlo, Everything looks great! except the mtdparts. Still set to the default value: mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) Set it to the NSA325 value: fw_setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2by bodhi - uBoot
Manuel, > I think i would like to "saveenv" now. What do i > need to do for that - i don't want to do anything > wrong, even if we have the backup method > available. Excellent works! Scanning it, it looks like everything working. Let me study the serial bootlog a little bit more and get back to you. I would like you to keep this running for a few hours.by bodhi - Debian
Carlo, Power up, interrupt serial console and printenv boot Please post the entire serial bootlog, from u-boot banner to the last thing you see on the screen.by bodhi - uBoot
Dieter Wrote: ------------------------------------------------------- > Dear bodhi, > > the uboot seems to have problems with your > commands: > > All the setenvs were fine, but then: > > ... > dockstar => boot > (Re)start USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 4 USB Device(s) > found > scanning usb forby bodhi - Rescue System
Carlo Wrote: ------------------------------------------------------- > Should I move the file into the Nas memory? > > EDIT: > maybe i've understood: i should hint that > parameter to /boot/.... cause my sata should be > mounted as root, right? Your u-boot envs were already set up to do that. 1. Reboot with only the USB rootfs to see the progress. 2. Afteby bodhi - uBoot
bennytheben, > Have you had any contact with the > people who run > the > wiki at openstora.com? I've been trying to > follow a few guides including ones on that site > and they're all a bit out of date and incomplete > compared to yours. I think people would benefit > from having more links to this forum. Please feel free to post links to Debian andby bodhi - uBoot
ElMariachi, Take out bootcmd_uenv. It is only used when you need uEnv.txt. scandisk is what require to find the partition that contains the kernel files. Normally it does not cause problem to initialize the HDD again. However, in some rare case, such as this SSD, it might help not to do that twice (because of the spinning up time). When you have serial console, or have set up netconsole,by bodhi - uBoot
bennytheben Wrote: ------------------------------------------------------- > How many of these recommended tweaks are already > enabled in your debian rootfs? None of them are. The rootfs is a very basic rootfs. It meant to be Linux learning vehicle, you have to install things you need.by bodhi - Debian
This env is wrong: dtb_file=/mnt/boot/dts/kirkwood-nsa325.dtb It should be dtb_file=/boot/dts/kirkwood-nsa325.dtbby bodhi - uBoot
bennytheben, You've chosen a wrong step 4 during the upgrade to kernel 4.15.2 Since you are booting with the new u-boot, step 4a is the correct one to take. Quote4. Create uImage and uInitrd and setup for booting. I'm using the GoFlex Net booting with USB drive as an example here. Please replace its name (kirkwood-goflexnet.dtb) with the box you are installing on (for exampby bodhi - uBoot
Carlo, > so... i'm ready to reboot? Not yet. There are NSA325 specifics that you have not adjusted. See the bold parts in the quote below. Quote8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8). As described in step 1, u-boot envs must be defined in /etc/fw_env.config as # MTD device name Device offset Env. sby bodhi - uBoot
Carlo, You are still inside stock OS. So the one being used is: /dev/mtd1 0x0000 0x20000 0x20000 4 If you want to verify your envs were flashed and set correctly: cp -a /etc/fw_env.config /etc/fw_env.config.stock echo "/dev/mtd0 0xc0000 0x20000 0x20000" > /etc/fw_env.config fw_printenv Now you can choose to leave the stoby bodhi - uBoot
Ray's post about this HP T5335z: https://forum.doozan.com/read.php?8,33074,33092#msg-33092by bodhi - Off-Topic
Gravelrash, Here is the one listed on eBay US. https://www.ebay.com/itm/HP-t5335z-Smart-Marvell-Arm-1-2GHz-1GB-RAM-2GB-Flash-Thin-Client-w-power/152662252333by bodhi - Off-Topic
Carlo Wrote: ------------------------------------------------------- > i've reached step 9 of the uboot guide.. my > printenv seems a bit redundant... > > > /mnt/boot/dts # fw_printenv > bootargs=console=ttyS0,115200 > mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA000by bodhi - uBoot