megal0maniac Wrote: > It also seems to be ignoring bootcmd. I first > changed it to boot from USB followed by flash, > then removed the section about flash altogether > but it still boots from flash. Not sure what the > entry point is if not bootcmd... Don't forget you need to saveenv if you want to make the boot environment changes permanent after a power cycle. Buby LeggoMyEggo - Debian
You got me inquisitive, this one would be a Marvell based beast running as a Debian router. Linksys wrt1900atc. Based on SOC, very doable if you can get serial console.by LeggoMyEggo - Debian
Also, you could try these env's but don't do a saveev. Simply repower if it hangs. setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10' setenv load_usb 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x1100000 /boot/uInitrd' setenv bootcmd_usb 'setenv bootargs $(bootargs_usb); run load_usb; bootm 0x800000 0x1100by LeggoMyEggo - Debian
I would try to boot off embedded sheevaplug dtb and see if that gets you further. It seems like the most generic.by LeggoMyEggo - Debian
See this thread: QiZhiTong 501mv2. Might be useful for EA4500 as they appear to be similar devices.by LeggoMyEggo - Debian
rkrug Wrote: ------------------------------------------------------- > I'll see which way I'll go - exernal eSATA housing > sounds tempting due to the included power supply. > If I interpret the picture correctly, an old PC > housing is used for the housing and power supply > of the hdds - correct? Interesting idea, > especially if I can use a multiplier on theby LeggoMyEggo - Off-Topic
bobafetthotmail Wrote: ------------------------------------------------------- > As long as the hardware works decently, the > software side is fine. The problem you can run into is a wireless network device works fine as a client but doesn't work as a host because of driver issues. At least that's been my experience and observation.by LeggoMyEggo - Debian
bodhi Wrote: > Thanks. This is a very good box (no SATA but 4 > Gbit ports). Plentiful used supply and cheap now because of age. Looks like you could pick one up for less than $30 shipped. Even with 128MB RAM, would still make a good Debian device but I wonder how all the pieces would work together for hostapd, iptables and such to get routing and AP functions working. Then againby LeggoMyEggo - Debian
You need something like this if you are talking about bare 2.5 drives: 22 Pin Sata Extension Cable If you put the 2.5 drive(s) in an esata enclosure with it's own power, you would need this cable: 22 Pin Male to 7 Pin Female with Power Sata Cable and this adapter: Sata to Esata Adapter. Note in this situation you would not be using the power part of the SATA cable so you could fold anby LeggoMyEggo - Off-Topic
bodhi, this guy looks like your kind of hacker :) Hacking the "Candyhouse" Impressive resume too........... Regarding Debian / Openwrt, it looks like both have already been figured out. I wonder if "bodavian" would make it better?by LeggoMyEggo - Debian
EA4500 running Debian would be awesome. I am afraid however, getting all the built in networking devices to operate and cooperate may be a struggle. At least that's been my experience with Guruplug and Dreamplug. Libertas based firmware devices suck.by LeggoMyEggo - Debian
Note for anyone who wants to make their own serial console cable, here are the parts you would need from Digikey for the T5325 side in order to make it work: 4 Position Molex PicoBlade Connector Pre-crimped wire assembly for connector These things are alot tinier than they look in pictures so don't even think about crimping wires yourself - buy the pre-crimped wires I have linked toby LeggoMyEggo - Debian
bodhi Wrote: ------------------------------------------------------- > @CV & Leggo, > > You have the separated DTB, perhaps you should try > this DTB to see if it makes any difference. Put the T5325 aside and am now playing with a previously hopeless Sheevaplug I picked up extremely cheaply because it had a torched PS. Bypassed the PS with a new barrel plug and am experiby LeggoMyEggo - Debian
LeggoMyEggo Wrote: ------------------------------------------------------- > When I did the fw_setenv I got an error about > writing to mtd0. Evidently this wasn't a problem > however. Now that I think about this more, when I had the T5325 open and on serial console (and before I performed your operation), I may have executed a setenv bodhi or you had posted earlier that enaby LeggoMyEggo - Displays
Gravelrash, I followed your instructions verbatim and they worked fine on a fresh rootfs running 3.17. Good job! Couple things I experienced. When I did the fw_setenv I got an error about writing to mtd0. Evidently this wasn't a problem however. For /etc/x11, there was no existing xorg.conf file in the main directory or the subs so all I had to do was copy over the file you poby LeggoMyEggo - Displays
Gravelrash Wrote: ------------------------------------------------------- > @Leggo - would you be willing to share you alsa > conf files and alsastate file. i would like to > compare with mine and see if its actually a > harware fault i have with the unit as i get no > sound, but alsa reckons to be fuctioning and > outputting to the correct device. Not using builtby LeggoMyEggo - Debian
Thought I would post a pic of my T5325 running headless with Debian 3.17 loaded per this thread. I'm using it as a combo PBX (running IncrediblePBX for Pogoplug from here: IPBX on PP) and as a Squeezelite client (notice the Plantronics DECT base which I use for wireless music listening). I was also able to compile the 8812au driver for the shown Trendnet AC1200 wireless adapter using thisby LeggoMyEggo - Debian
bodhi Wrote: ------------------------------------------------------- > It's 3.17. OK then, ignore my earlier post :)by LeggoMyEggo - Debian
I'm trying to remember the first rootfs with dtb. Was that 3.17 or 3.18?by LeggoMyEggo - Debian
bohi, any way you can provide another download for 4.4.0 rootfs with Wheezy instead of Jessie? Didn't realize till too late that the 4.4 rootfs d/l was already upgraded to Jessie. TIAby LeggoMyEggo - Debian
Gravelrash Wrote: ------------------------------------------------------- > WIFI > Should be a no brainer as its been covered many > times before > > Bluetooth > because everything is better with Bluetooth and > its been covered before on other units On my T5325 these worked without issue using the standard means to enable a USB device of these types.by LeggoMyEggo - Debian
Quick question for bodhi, will the kirkwood-t5325.dtb file work to boot with earlier, non-Jessie, rootfs'? I ask because I am trying to modify an existing 4.1 wheezy flash drive that has everything I need already loaded and I would like to use the T5325 for those functions.by LeggoMyEggo - Debian
bodhi Wrote: ------------------------------------------------------- > > any idea how to enable the VGA display? > > No idea, I don't have any VGA display to try. I'm > relying on you guys to test this! have you plugged > one in? Yes tried but nothing displayed. Thought I would get at least command line but nothing.by LeggoMyEggo - Debian
Catching breath tonight after success with this thing, let me say thanks bodhi for your effort. You've brought a new life to these T5325 boxes. GOOD JOB! Rest on your laurels for a little while :) After you've rested and been fed your grapes (LOL) any idea how to enable the VGA display?by LeggoMyEggo - Debian
bodhi Wrote: > See step 6. Didn't matter, the new env's were trying to boot dtb for the E02 because it was loaded by the new env's. Once I revised the rootfs USB disk on another Debian box to boot with separate DTB then updated the env's to dtb_file=/boot/dts/kirkwood-t5325.dtb, it booted fine and did not throw a kernel panic.by LeggoMyEggo - Debian
Think the new env's might need adjustment: Hit any key to stop autoboot: 0 T5325> printenv arcNumber=2097 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=mw 0x800000 0 1; run load_uimage; if run load_initrd; then if run l oad_dtb; tby LeggoMyEggo - Debian
I don't have an mtd2. Like I said, this box was messed up by the previous owner and hence why it was so cheap :) Can I create a mtd2 partition from the command line in Debian or do I have to do it from serial console? Either way, how do I do create the new partition?by LeggoMyEggo - Debian
Houston, we have a problem: The box I have has not booted to the HP OS since I received it - I think somebody borked it experimenting. However, with serial console I was able to boot using the stock u-boot into your 4.4 Debian rootfs. I successfully flashed the new uboot to mtd0. However, it appears I have no mtd2 to flash the env to: root@debian:~# flashcp -v uboot.2014.07-tld-3.enby LeggoMyEggo - Debian
bodhi Wrote: ------------------------------------------------------- > I've uploaded u-boot and envs images and > installation instruction in this thread: > http://forum.doozan.com/read.php?3,26562 When creating the rootfs for this operation, does one need to embed dtb into uImage or do your new env's provide for separate dtb booting? Regardless of separate or embedded,by LeggoMyEggo - Debian
Great T5325 reference page with uboot info and links to SATA and GBE mods: http://www.parkytowers.me.uk/thin/hp/t5325/index.shtmlby LeggoMyEggo - Debian