TuxScreen on SourceForge TuxScreen CVS search the Wiki
Browsing -> Wiki -> Users -> [CarlWorth]
Google
Topic:
edit, info, topics, orphans, hubs and nodes, or recent changes in the Wiki create a new user or login

15 December 2001

Just flashed and installed Linux for the fourth time on a TuxScreen. I only do this about once every two months and find myself having to visit several pages to remind myself how to do everything. Time to make some InstallationReminders to put the essential steps in one place.

Just put 0.5 on a phone, but tone dialing and speakerphone don't work. The audio in the handset is extremely faint. The current thought is that some delays in the wheaties driver are not long enough. Trying now with another phone to see if I fair any better.


13 August 2001

After a two-month break I finally got back to my TuxScreen. A lot of development occured in my absence. Today I followed the InstallingLinux instructions and have now logged in over the serial port to my linux-running TuxScreen!

My Socket LP-E compact flash ethernet card works perfectly! :)

Next, I'll have to try the 64MB SODIMM and try to get my 802.11 card working.


16 June 2001

Initial experiments with the 64MB SODIMM were not successful. :-(

I spent a fair amount of time poking around the inferno shell looking for a way to determine how much memory was available before I finally realized the initial splash screen reports the amount of memory down at the bottom *blush*.

A normal boot sequence is something like this:

# Message light blinks and LCD powers up # LCD blinks off # Splash screen fades in and reports available memory

With the factory-installed SODIMM installed the machine boots and reports 16MB. With an empty socket it boots and reports 8MB. When I put 64MB SODIMM in the socket, (Crucial CT16M32E8T6), the boot sequence stops after the step (1) above. That is, with the 64MB SODIMM the message light blinks and the LCD powers up but nothing happens after that.

I wonder if we might still be able to get a 64MB SODIMM working with another bootloader...

Also I have not yet checked to see if the steps detailed at InfernoRemote might still work even though the machine seems hung, (my guess is no).

In other news, I have confirmed that I have a bad IO board in my machine. I took a working tuxscreen and swapped the processor boards and the top half of the case, (UI board w/buttons + display). (I would have simply swapped IO boards but there's some solder to the battery connector -- this is equivalent except for plastic.) The non-functioning behavior stayed with the IO board from my original machine.


14 June 2001

TimRiker said he's seen the same blinking red "There is a problem..." message before on his units. So that's probably not related to my broken phone.

I got a working TuxScreen from a colleague this morning. I'll try swapping boards around tonight to isolate the problem.


13 June 2001

Well, thanks to Tim's trick on SoftwareDownload I can now get back to the original Inferno "desktop". Still no progress on the dead phone. I'll try swapping IO boards with a known good phone tomorrow to try to isolate the problem.

Not sure if it is related to my phone problems or not, but two times now my machine has booted to a blinking red screen with the following message:

> There is a problem with your Phillips IS2630 screen phone that could not be corrected. Please call hotline for additional help. (See Owners Manual)

A hard reset seems to have cleared this both times. Not sure what that is all about.


12 June 2001

Told TimRiker about my problems. He said he hasn't seen anything like it with any of his units. He suggest reseating the IO board which I tried, but that didn't help.

TimRiker also pointed me to Shaggy's Shannon Support Center which has a lot of useful tricks, (like how to drop to an inferno shell). I tried the magic sequence ##314159265359** which didn't do anything since my buttons don't work.

I was able to get to a shell by following these steps, (courtesy of Shaggy)

# Press ESC at the splash screen # Press CTRL-P to get to an sboot prompt # consoleprint=1 # shell=/dis/sh.dis # b F!kern1

Poked around the inferno file hierarchy a bit. Found some binaries that might be interesting (netflash), as well as some that weren't so useful, (logon brings up an xdm-like Inferno logon window, but I couldn't find any working username to type in). Time for me to learn more about Inferno I guess...

Oh, and I don't get the standard desktop when I boot anymore. :( It now just boots to the "Software Download" dialog with Dial/Cancel buttons. Dial doesn't work, (since I have no dialtone), and cancel just reboots the machine, (and gets me back to the same point).

I'm starting to wonder about firmware/software revisions. Shaggy mentions sboot version 2.4 - 2.6. I never found numbers in that range, but I did see sboot 0.7 (maybe 0.7.1?). Could that really be the same version? yikes!


11 June 2001

I received my TuxScreen today!

I plugged it in and found that the builtin Inferno software really isn't that bad. There is a usable notepad and a calendar. Haven't tried the web browser or email programs yet.

Unfortunately, I can't get the phone part working yet. There's no dialtone, the buttons don't do anything, and the message light always stays on. I also haven't heard anything from the speaker yet. Can't wait to get this all going as my wife is excited to have web access from her kitchen desk soon. :)

I pulled it apart and looked for loose connectors. I reseated the ribbon cables going to to UI board, (with all the buttons), but no luck yet.

SourceForge Content of these pages are owned and copyrighted by the poster. SourceForge