Hi, Are any of these 2 devices capable of WakeOnLAN? If so, how can it be setup? Thank You!by veriqster - Debian
I can mail you mine if it's something you are willing to look at. Not sure I'm seeing things the right way but It has an integrated N wireless and a Z wave so it might make an interesting box to play with for home automation.by veriqster - Debian
it does not, just sits idle. If I try to use the stock kirkwood rootfs with the generated uImage then it boots to a point and then states "attempted to kill init" and "kernel too old". Unless I can find a guide on how to make a DTS file it is my guess that this is a futile attempt at finding shortcuts.by veriqster - Debian
how hard would be to do that given that I have the config for the kernel and the fact that I've never done this before? Is there anything I can do to get over that init message about no processes left?by veriqster - Debian
if I set the environment to this setenv set_bootargs_usb 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=20 $(mtdparts) earlyprintk=serial' I am able to get this far BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | |by veriqster - Debian
tried booting both with root=LABEL=rootfs and with root=/dev/sda1, also tried addint rootfstype=ext2, still gets stuck at trying to find the rootfs code with all 3 attempts attached ootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| |by veriqster - Debian
so I resorted to basic script kid techniques but those fail as well. I tried to pass some arguments to the kernel via the setenv but regardless of what I do, if I run the boot command it still shows Kernel command line: console=ttyS0,115200 rootfstype=ubifs ubi.mtd=ubi ro noswap mtdparts=nand_mtd:2m(uboot),-(ubi) root=ubi0:active mv_net_config=1,(00:26:B8:71:C1:FC,0:1:2:3),mtu=1500 bootmode=by veriqster - Debian
Despite of finishing to compile in a orderly manner the created rootfs does not include a uInitrd, just uImageby veriqster - Debian
Compile finished successfully. Can you please provide instructions on how to copy the files to usb stick and boot it up? I basically have a rootfs folder that is supposed to contain a Lenny. Thank you! P.S. supposedly Marvell did not bother with this chip too much - there's not much public information on it and sources are limited most probably this Verizon release - I could not find aby veriqster - Debian
I started compiling it, had to install a bunch of stuff I've never thought I'll ever use again, like the GCC, older version and all kind of libs necessary to compile for a different architecture. Hoping it finishes before the morning. This thing has been compiling av codecs for the last 45 minutes, one would think it's a NASA image processing server, .... Thank you! I'lby veriqster - Debian
trying to think out of the box in here and find a dirty but easy way out, .... From what I read, it is possible to compile a newer kernel with an older config by doing an oldconfig on the new sources which would prompt for configuring the differences. Assuming my understanding of that is correct, can I unpack the sources published by verizon and compile them, then start updating the kernel soby veriqster - Debian
The only available source for the board has all the sources for all the software on it, including a bunch of verizon crap but it comes with a 2.6 kernel The latest kernel that I could find online is 3.14.32. It is for a different actiontec board that incorporated the same processor but is definitely different component wise though. Is there a guide somewhere on how to build a DTS file basedby veriqster - Debian
Sorry for posting the source file, no harm intended, I thought to just spare someone who actually knows what they are doing the time to download and uncompress the sources.by veriqster - Debian
Looked around and the most recent kernel that is confirmed to have been running on this processor is 3. would that have required a DTS file in order to build?by veriqster - Debian
Would it be included in the sources for building a debian rootfs? If so then the sources are available at https://opensource.actiontec.com/sg200.html. it has the full sources and the script to build them into a full Debian 5. this is one of the config files used for compiling the kernel for this board /******************************************************************************* Copyrighby veriqster - Debian
by the way, those commands were run on a x64 system, not on a kirkwood. would that be the issue?by veriqster - Debian
I actually ran those but with the 4.12 kernel in the rootfs. Can't figure out how to do it with the latest kernel some of the files (initrd) are only generated as the .deb is installed. so I put the rootfs back into the linux box and ran the commands with 12.1 instead of 20.6. They complete and the files are created. sync, unmount and move to the board. Still getting stuck on the same tby veriqster - Debian
took some lines from the dell appliance thread and ran commands; output attached. Basically loaded the uImage and uInit files and booted it. It gets stuck as expected. ▒▒ BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \by veriqster - Debian
if it makes a difference or helps figure this out, the link below supposedly has the full sources for the Debian that is currently running on the device. Judging by the fact that the /etc/shadow in the sources has no password for root and the box does not allow a login without password there's definitely some differences. https://opensource.actiontec.com/sg200.htmlby veriqster - Debian
this is what I get if I try a plain usbboot from rootfs drive Marvell>> usbboot usb 0:1 Loading from USB device 0, partition 1: Name: usbda1 Type: U-Boot ** Unknown image type Marvell>>by veriqster - Debian
output of printenv BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ /by veriqster - Debian
Hi Guys. I've soldered some wires to the serial pins on an ActionTec200 and it has an old U-Boot as well as a debian 5 base system. Created a fresh Kirkwood 4.12 rootfs. The U-Boot This is the output of the help command in uboot BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | |by veriqster - Debian
rootfs code is available if that helps. I could compile as there are directions on how to do that but no directions on how to load the new rootfs to the device itself. Would it be possible to make USB stick with it and boot from it? If it can be figured out somehow then it might make a hlf decent access point / file server, it has an atheros N wireless card and 2 USB available.by veriqster - Off-Topic
this is what I get when I interrupt the boot and do a printenv BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) _by veriqster - Off-Topic
upon closer reading, that explains everything, I was using the wrong header, ...by veriqster - Off-Topic
Gravelrash Wrote: ------------------------------------------------------- > This should help you > > https://wikidevi.com/wiki/Actiontec_SG200 Looked over it and I cannot see a serial connection pinout. I has a 10 pin connector with 5 pins on each of the 2 rows. something like this: |X|X|X|X|X| |X|X|X|X|X| I've tried quite a few combinations of connecting the wires to tby veriqster - Off-Topic
Hi. Sorry to resurrect this. Did anyone manage to figure out how to connect to the SG200 Actiontec via serial console? I've tried hooking up to it but the output is all gibberish, maybe I have the settings for Putty wrong or the wiring misconnected. Supposedly it should allow a no password root login via SSH but I've reset mine a few times and it still asks for a password which I caby veriqster - Off-Topic
Ended up using the HDD for the rootfs. Created a 8GB partition at the beginning of each HDD and labeled one of them as rootfs. Installed everything and it works like a charm Debian 9 with OMV 4. Once installed I created a tarball of the system and stored it on the 8GB partition that is no labeled. Untarred and now I have a rootfs ready to go in case something happens. All that needs to be doneby veriqster - Debian
Hi all, I'm not even sure this is related to the systemd, although the 4.12 rootfs seems to cause the drives to crash almost every time there's intense disk access activity, the 4.4 is a coin toss. There's a bug somewhere and I don't have the skills to find it. Bottom line is the 16GB Sandisk Cruzer Glide (2 of them) and the 32GB Sandisk Cruzer Glide (3 of them) do notby veriqster - Debian
keeps throwing the "usb reset" at me every time I try to get something installed. For some reason I am under the impression that I see the EXT4-fs module mentioned close before the reset. Could this cause a problem? 3 times out of 4 when it gets stuck and I reboot I get this Warning: File system check failed but did not detect errors [ 25.760380] EXT4-fs (sda1): mounting ext3by veriqster - Debian