What ayrlander pointed out was the exact reason why I went for a traditional Debian install. Despite a completely different architecture, the wealth of packages in the repositories means that you can effectively have everything (almost) that you would have for an x86 install. The only thing I've yet to be able to get is Opera for ARM within an X based setup, as they don't have that inby rat - Debian
Did a little digging for how to duplicate the heartbeat function using timer. http://www.plugapps.com/index.php5?title=DockStar_LED # cd /sys/class/leds/dockstar\:orange\:misc # echo timer > trigger # ls brightness delay_off delay_on device max_brightness power subsystem trigger uevent # echo 1000 > delay_on # echo 1000 > delay_off Looks like it's limited to oneby rat - Debian
I have a similar problem but with the LCD Keychain Picture Frame taking the /sda designation and causing bootup hangs or issues. All I can do is remove the LCD, cycle it and wait for it to finish booting before I plug it in.by rat - Debian
petergunn Wrote: ------------------------------------------------------- > Doh! Must be on some sort of timer. Dont think > that can be fixed unless you mod the firmware > somehow. Yeah. I wouldn't even know what to look for, unless I can find something in hex that would roughly translate to: "Put this ugly icon back up every 2 seconds!" ;)by rat - Displays
petergunn Wrote: ------------------------------------------------------- > Can you give it a whirl > an see if it fixes your battery indicator ? That is just so friggin weird. The battery indicator pops up about every 2 1/2 to 3 1/2 blinks and immediately goes away as that 1/2 blink becomes 1. Still an option to keep in case anyone wants it there for reminder that they have an activeby rat - Displays
petergunn Wrote: ------------------------------------------------------- > wait for it... > blinking cursor support. *SSSSSSSSQQQQQQQQQUUUUUUUEEEEEEEEEEEEEEEEE!!!!!!!!!!* *runs out to try it and runs smack into a wall*by rat - Displays
Colin Wrote: ------------------------------------------------------- > Sometimes the most confusing problems have the > simplest solutions :p Good to hear. I've taken a real liking to having my LCD sitting in the drive cradle if just for the visual feedback that it's purring along. I got my DP151 today and my research was spot on. Got the correct v5 model and flashed it..by rat - Displays
>I'm hoping they didn't break support for the LEDs in a later kernel, but odds are, In a sort, they did. Maybe. Not sure. Heh... They renamed dockstar:orange:health to dockstar:orange:misc (which broke a few things as I preferred orange to green) They removed mmc0 from both green and orange, the heartbeat equivalent... OOOOORRRRR... both of those things were always that wby rat - Debian
>But, if you don't want to use kirkwood at all, you might want to apt-get remove it >after you've re-installed the kernel package you'd like to use. That was part of the problem. Got a few scary warnings about the dockstar kernel already existing and that things might break. Hence my post before the one you responded to. And yes, I'm certain it's booting into tby rat - Debian
Jeff Wrote: ------------------------------------------------------- > I think we should be using proper machine IDs > rather than overloading sheevaplug. I plan to add > support a configurable arcNumber variable in the > uBoot environment so we can make the transition a > little easier. > > -- Jeff Running into a bit of a problem with this. I was running the dby rat - Debian
All I can suggest, Colin, is to make sure it's in upload mode before you plug it in (if it doesn't do it automatically) and maybe try using a different cable. The cable that came with my Shift3 would fail on all devices (even my mp3 player) for simple things like copying files. I couldn't get a firmware dump off my Shift3 until I swapped the cable with one I knew that was good.by rat - Displays
When booting up the system after having to shut it down for some hardware mods... the light stopped coming on after it would go through the bootup process. Now it looks like the system went back to using the kirkwood kernel instead of the dockstar one despite it still being installed. Obviously I never did the apt-get remove part for the old kernel. What do I need to do now to get it to switchby rat - Debian
Huh. Interesting on using the USB Host cable. Certainly does open up the possibilities with what you've started with here. As far as the screen refresh goes, the device is supposed to be able to handle about 8-9fps maximum, typing continuously isn't too bad on CPU resources, so a 1s on/1s off blink rate at command prompt shouldn't tax it much. Even on USB1.1 and cpu bound hosts.by rat - Displays
Peter: Funny you should mention screen, it was how I was running the LCD and detaching the ssh session so both st2205term and lcd4linux would remain active. I don't know why it didn't occur to me to switch between screen sessions. (Probably because I'm one of those who likes to have a separate terminal open for each session.) As much as I hate to ask for a device specific feaby rat - Displays
Tried something. Left st2205term running, in SSH, I fired up lcd4linux again. lcd4linux drew my screen update without any harm. Killed lcd4linux, hit space bar, got screen refresh and root prompt again. They coexist. Very nice. Though it does get a little weird when you try to type while lcd4linux has taken over the screen. Screen gets very glitched and goes mostly back.... only changesby rat - Displays
Well, Peter, I tried to update the Picframe wiki ( http://picframe.spritesserver.nl/wiki/index.php/Main_Page ) as much as I could. From what I can see of available models and what both of us have been able to do... Looks like only the DP152 and Shift3 Fats are the easily available hackable LCD models. Updated the device list to say those two are probably the best bet at this point. Also uploadedby rat - Displays
Colin Hickey Wrote: ------------------------------------------------------- > Hi, my cable arrived today so i've hooked it up. > It turned out to have five wires in it (although > only 3 are connected when i openned up the USB > end) so i found a guide which said what to hook up > where and it seemed really positive in that i > could see the boot process start andby rat - Debian
Peter: I'll be working on getting your code running on the Dockstar during the weekend. So I'll let you know what breaks/works/stalls/explodes then. ;) (Though it's likely a keyboard and path issue as there wasn't one hooked up then.) I really like rgtta's suggestion on being able to switch what goes to the LCD. There was only two things I wanted to be able to send toby rat - Displays
And a pic of the setup in action: http://i.imgur.com/ncJD5.jpg (Sorry for the blur. Cellphone camera and all that.)by rat - Displays
Seems to be something broken when you try to go to page 4...by rat - Displays
petergunn Wrote: > Thanks for the info. Does the following fix the > dependency? That did it. Make completed for both parts... Now the fun part. root@pipsqueak:~/st2205term-alpha-0.02# LD_LIBRARY_PATH=/usr/local/lib ./st2205term --font=small --picframe=/dev/sdb --keyboard=/dev/input/event0 --keymap=./us.kmap libst2205: detected device, 128x128, 16 bpp. rote_vt_forkpty: PID=2794by rat - Displays
petergunn Wrote: ------------------------------------------------------- > Then you can download and test st2205term :-) checking for initscr in -lncurses... no configure: error: Need ncurses to compile librote. Stuck there. Might wanna add that to your install instructions earlier in this thread.by rat - Displays
petergunn Wrote: ------------------------------------------------------- > rat - thats it - you hacked it! Grr! Hulk! Smash! Kill! Actually. I did give it a stern look. But that's it. So. The verdict for whoever ended up with a Shift3 and wants to know what to do... Follow every instruction on the first page of this thread for generating a hack. The issue was somehow the comby rat - Displays
Guess I couldn't wait to find out if I could get it working with a few other ideas. Disabled the folder which the compile process failed on. m_innovage or whatever it was. Deleted the folders made for the Shift3 and tried to generate a hack again. Well. Now it displays garbage on the screen instead of hanging. Could ALMOST make out it trying to say something. Interesting. Ran LCDby rat - Displays
petergunn Wrote: ------------------------------------------------------- > Did you modify generate-hack.pl so that spec file > ends up with 24bpp rather than 16bpp? Yep. ;( > Its possible but lets double check the config - > can you attach the generate-hack.log and spec file > from the m_ directory? Attached. I see the process was interrupted on yet another model typby rat - Displays
petergunn Wrote: ------------------------------------------------------- > rat Wrote: > -------------------------------------------------- > ----- > > > Deleted m_shift3 and trying again. > > > > Massive errorspam like before. Attached as > file. > > Looks like generate-hack.pl succeeds in creating a > hack, then it cd's to the hack diby rat - Displays
Went ahead and tried it despite the errorspam. Hung just like before. Gah... This is basically what happens when LCD4Linux is executed: root@pipsqueak:/home/rat/lcd/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf Version 0.11.0-SVN-965 starting libst2205: detected device, 128x128, 24 bpp. (hangs here, both in term and via battery charging indicator on screen) Disconnectingby rat - Displays
petergunn Wrote: ------------------------------------------------------- > Might be worth trying to run that directly and see > if you get more info. Hrmmm... Gave me a file not found error. Could have sworn I compiled it all. And wow. It's in my history, but I guess the compile got interrupted somehow. Deleted m_shift3 and trying again. Massive errorspam like before. Atby rat - Displays
Generated a new hack... Got a new message on the screen this time. "Yay! \o/" Still hung when it asked me to reconnect the device. Disconnecting gives me a flood of readline errors. Making sure I got the original firmware on the device, reflashed it to backup, tried to run lcd4linux: root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -fby rat - Displays
root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# chmod 600 lcd4linux.conf root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# ls -la lcd4linux.conf -rw------- 1 rat rat 3190 2010-11-24 16:22 lcd4linux.conf root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf Version 0.11.0-SVN-965 starting security error: owner and/or group of 'lcd4linux.conf' don't matcby rat - Displays