kwboot for Windows: Ok, after perusing the Cygwin documents and spending way too much time researching it, I couldn't find a clear answer as to whether or not it's permissible to distribute their DLL with my EXE. I believe I'm not doing improper, but if I hear otherwise I'll take it down. https://www.dropbox.com/s/76uw8kxjoh9o6ag/kwboot-windows.zip?dl=0 bodhi, if youby renojim - Debian
bodhi Wrote: ------------------------------------------------------- > Excellent! one more good tool to have for people > already have Cygwin :) can you post it somewhere > so I can add it to the Wiki. I wanted to just post a link to my exe, but I got scared by the fact that there's Cygwin usage terms (mind you, I haven't read the terms, I just know they exist). Technicby renojim - Debian
bodhi Wrote: ------------------------------------------------------- > > kwboot is only available in Linux. > I have built and run kwboot under Cygwin, so it's possible, but it may not be worth the trouble of installing Cygwin just for kwboot.by renojim - Debian
Here ya go: https://www.dropbox.com/s/iogxvtsw937spyv/KaceM300-Stock_sda.tar.bz2?dl=0by renojim - Debian
bodhi Wrote: ------------------------------------------------------- > I've wiped my internal SSD and put the latest > rootfs on it. No problem at all so far with > booting or apt-get update/upgrade so far. > Sounds good for you, but bad for me. I think it;s going back on the shelf.by renojim - Debian
Yeah, I think I need to take a step back or try a hard disk in place of the 16GB SSD. As another data point, I backed up uImage and recreated it with the previous dtb (before bodhi took out the GPIO keys) just to see what happens and sure enough if it boots just trying to run fw_printenv will cause a kernel panic. I then restored uImage from the backup (the one created with the dtb with the GPIby renojim - Debian
Uh, oh! I don't know what happened:root@kaceM300-1:/boot# apt-get update apt-get: symbol lookup error: /usr/lib/arm-linux-gnueabi/libstdc++.so.6: undefined symbol: _ZNSt7num_getIcSt19istreambuf_iteratorIcSt11char_tra)tsIcEEE2idE, version GLIBCXX_3.4 root@kaceM300-1:/boot# apt-get clean apt-get: symbol lookup error: /usr/lib/arm-linux-gnueabi/libstdc++.so.6: undefined symbol: _ZNSt7num_geby renojim - Debian
bodhi, Yes, I believe it boots consistently. To be honest, I was only doing the apt-get update as some kind of stress test since I've been fooled before thinking, "it booted, so everything must be ok". I've done the apt-get update and apt-get upgrade successfully multiple times on the 16GB SSD. When I've had successful boots in the past (without anything inserted inby renojim - Debian
Looks pretty much the same:ø __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |___by renojim - Debian
bodhi, I thought you were onto something (although notice it still performed a reset on the way to booting):ø __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_by renojim - Debian
I added a printenv right before the bootm command to leave no doubt as to what the environment variables hold:bootcmd_usb=echo Booting USB.; usb reset; run load_uimage_usb; run load_initrd_usb; printenv; bootm $(load_uimage_addr) $(load_initrd_addr) bootcmd_ide=echo Booting IDE .; ide reset; run load_uimage_ide; run load_initrd_ide; printenv; bootm $(load_uimage_addr) $(load_initrd_addr) -JTby renojim - Debian
Reset env variables to not try USB; no USB drive inserted: Marvell>> setenv bootcmd 'run kernel_config; run set_bootargs_sata; run bootcmd_ide' Marvell>> printenv bootcmd bootcmd=run kernel_config; run set_bootargs_sata; run bootcmd_ide Marvell>> run bootcmd Booting IDE . Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMby renojim - Debian
Successful boot from SSD w/o USB drive inserted: | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__|by renojim - Debian
Boot w/USB drive failed followed by successful SSD boot (same as above, but wait two minutes for the IDE boot attempt): | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __|by renojim - Debian
This is what happens when it fails to boot from my USB boot drive: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |__by renojim - Debian
Boot w/no USB drive attempt 1 (hung at /scripts/init-bottom for ~2 minutes, then hung forever): __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _by renojim - Debian
Let me see if I can summarize my findings: haveged doesn't make a difference Booting from USB drive usually works (could be my cheap USB drive) Booting from SSD without USB drive inserted gives unpredictable results (hangs, unstable system, kernel panics, etc.) Inserting pretty much any USB drive allows SSD booting to succeed (USB drive can be removed after booting) [*} It's not gooby renojim - Debian
mikeh49 Wrote: > Tried renojim suggestion of inserting a USB drive, so used a random FAT32 key: > Booting USB. (Re)start USB... USB: scanning bus for devices... 3 USB Device(s) found Waiting for storage device(s) to settle before scanning... T I saw this many times. I think it's trying to boot off the USB and if you wait long enough it will eventually try IDE and successfullby renojim - Debian
I'm giving up on SSD booting for now. What I've noticed is that if I have a USB drive inserted (doesn't have to be a boot drive or even extX formatted drive), it will boot off of SSD and be stable. If there's no drive inserted it may or may not boot and if it does it's very unstable. I've verified that the load addresses are identical in all cases. Once it'by renojim - Debian
Did you do this from one page back? 5. In Debian, modify the /etc/fw_config.env to enable access to u-boot envs. echo "/dev/mtd1 0x0 00001000 0x00001000" > /etc/fw_env.configby renojim - Debian
You're missing a "run":setenv bootcmd 'run kernel_config; run set_bootargs_usb; run bootcmd_usb; run set_bootargs_sata; run bootcmd_ide'by renojim - Debian
Since I just setup a M300 with 5.2.9-kirkwood-tld-1 I thought I'd try this installation just for the fun of it. I didn't have any problem, but I didn't follow the instructions exactly. I installed the packages in this order:apt-get install mariadb-server-10.3 apt-get install mariadb-server apt-get install php-mysql apt-get install apache2 apt-get install php php-mbstring I thby renojim - Debian
I use Windows and Putty, so that's probably not the problem. Just make sure you're copying and pasting the whole line and do it one line at a time. My thought with being able to boot from either USB or SSD was that I'd use the SSD to boot 99.9% of the time. I'd only want to boot from USB to either do a full backup of the SSD or if there was some problem with the SSD. Rigby renojim - Debian
bodhi Wrote: > Your envs are wrong. The load addresses need to be > set up the same way as booting with USB rootfs. I thought they were? That was my intention. Of course I was doing this at 4 in the morning... > > I will create a well organized envs set to boot > both USB or SATA. Great! -JTby renojim - Debian
I'm trying to boot from the SSD, but I'm having all kinds of problems. Sometimes it boots, sometimes it leaves me in initramfs, sometimes it kernel panics, etc. Even when it does boot, it's very unstable. Here's what I did: I deleted the partitions on the SSD and created one ext3 partition. I copied my working USB flash file system to the SSD (tar -cpvjf ... to backup,by renojim - Debian
I just installed 5.2.9 on my M300. Great work as always bodhi! I have two questions: 1) Is the other 270M or so of RAM unavailable? Stock: total used free shared buffers cached Mem: 2074580 192664 1881916 0 6000 76316 5.2.9: total used free shared buff/cache available Mem: 1804by renojim - Debian
bodhi Wrote: ------------------------------------------------------- > All, > > I plan to revisit the 2GB RAM issue on this box. > Please remind me in a few weeks if I forget. Cool! I've been wanting to dig mine out for a while now, but other priorities keep getting in the way. I've been pushing my beloved Dockstar too hard and I'm tired of the OOM killer kicby renojim - Debian
I can't really help, but I did find this: https://github.com/nodesource/distributions It gives instructions for installing node.js. For what it's worth, I use a Phillips Hue emulator for my home automation. It uses Python. ;-) -JTby renojim - Debian
I haven't tried to install nodejs, but isn't there just a plain nodejs package (there is for Debian 8)? Is there a reason you're trying to install nodejs-legacy? -JTby renojim - Debian
It works for me.by renojim - Debian