| 00:09:55 | jacques | ?? |
| 00:10:00 | jacques | has anybody done what? |
| 00:11:12 | as_ | Using a tux to share an internet connection. |
| 00:11:19 | as_ | As a proxy I guess. |
| 00:15:50 | jacques | i think some ppl here have done ie |
| 00:15:50 | jacques | it |
| 00:16:02 | jacques | hardest part is getting two NICs in there :-) |
| 00:16:21 | jacques | you need two that fit at the same time |
| 00:16:43 | as_ | Mmm, would a modem on the serial port work? |
| 00:17:48 | jacques | not too well since no hardware flow control |
| 00:17:57 | as2 | Ahh. |
| 00:17:59 | jacques | pcmcia modem should work tho |
| 00:18:04 | jacques | as long as it;s nt a winmodem |
| 00:20:19 | as2 | Hmm, any reason hardware flow control wont work? |
| 00:27:37 | as2 | Missing hardware or just not worked out yet? |
| 00:30:21 | jacques | hardware does not support it |
| 00:31:22 | sjm | jacques: ? schematics show CTS/RTS are connected |
| 00:32:10 | prpplague | anyone here used a trizeps module before? |
| 00:32:16 | prpplague | sjm: morning |
| 00:32:24 | prpplague | sjm: hows life down under? |
| 00:33:06 | sjm | prpplague: so so, 'twas my birthday yesterday, and my wife sent balloons to the office, so I've been coping a bit of flack :) |
| 00:33:59 | prpplague | doh |
| 00:34:12 | prpplague | sjm: thats why i don't tell anyone when my birthday is |
| 00:34:54 | sjm | prpplague: It's a bit hard not to, when a bunch of balloons arrives for you. |
| 00:58:17 | jacques | sjm: connected to what? AFAIK the sa11xx does not support it |
| 01:05:38 | sjm | jacques: looks like they go to GPIO pins, so I guess it's not true HW handshaking, you'd need some sw to toggle those bits. |
| 01:10:26 | jacques | hmmm |
| 01:10:37 | jacques | i wonder if that software exists |
| 01:10:42 | jacques | it would be useful |
| 01:26:09 | jacques | tho it's kinda ineffecient to not have hardware do it based on a hardware fifo |
| 01:53:36 | as2 | That would make me wonder how the modem is connected. |
| 01:54:02 | as2 | I'll have to have a look at the schematics, if there are any. |
| 02:04:18 | TomW | BZFlag: who did the schematics for the Tux CPU board? I have a correction for them. |
| 02:17:51 | BZFlag | don't recall. the schematics wiki page should say. |
| 02:19:53 | GPSFan | TomW: I did them, what did you find? |
| 03:34:19 | pik_ | Crap crap crap, I think I just bricked my tuxscreen with the 0.6 images.. |
| 03:35:30 | fontenot | what happened? |
| 03:35:50 | pik_ | When I turn the power on, the backlight turns on and the Message light flashes, but Minicom doesn't get anything. Just sits there. |
| 03:36:29 | fontenot | how did it happen? what did you do? |
| 03:36:33 | pik_ | I downloaded and flashed the blob, and rebooted, and that blob (20020501a) came up. So I downloaded and flashed the ramdisk image, rebooted, and.... pow. |
| 03:38:10 | fontenot | :-\ |
| 03:39:21 | pik_ | Guess it's time to learn to use a JTAG. But any ideas on why the blob would come up once, and not again? |
| 03:40:48 | fontenot | not unless it somehow got overwritten |
| 03:41:00 | fontenot | how many times have you power cycled it? |
| 03:41:05 | pik_ | Perhaps flashing the ramdisk didn't go right. |
| 03:41:12 | pik_ | Er.. a few, since then. |
| 03:41:41 | fontenot | well no matter how scrweed up the ramdisk is, it should not kill blob |
| 03:41:46 | fontenot | that's the point |
| 03:41:51 | pik_ | That's what I thought. |
| 03:42:10 | fontenot | you should be able to flash ramdom bits as a ramdisk and still boot to blob |
| 03:42:25 | pik_ | But if it got flashed to the wrong location..? |
| 03:42:35 | fontenot | well then it could have overwritten part of blob |
| 03:42:49 | fontenot | but i havent heard of that happening |
| 03:43:12 | fontenot | did you change anything in your minicom connection since you flashed blob and it worked? |
| 03:43:24 | pik_ | No. |
| 03:43:28 | pik_ | Same session. |
| 03:47:42 | pik_ | Looking through my transcript, I see that I flashed the new ramdisk, then typed 'boot' instead of rebooting, assuming that the new kernel would be used. But it looks like it tried to boot the old kernel, couldn't find init, and died. That's when I power cycled, and nothing came up. |
| 03:48:22 | pik_ | So what I should have done is reboot blob. |
| 03:53:11 | pik_ | Or (more than likely) I completely misunderstood the point of the 0.6 images, having the kernel inside the ramdisk image and using a new blob that understood that. |
| 04:03:30 | TomW | pik_: FWIW, I have noticed that when I switched from 2.0.4 to 2.0.5 (before latest jffs2 change), I had to "erase <parm, kernel, ramdisk>. It seemed that 2.0.4 kept a table of some kind as to where stuff was located, erase-ing made stuff work correctly. |
| 04:04:44 | TomW | pik_: maybe something like that is in the jffs2 blob. When I tried the latest stuff, I automatically erased param, kernel, and ramdisk, then uploaded the new image. |
| 04:05:37 | pik_ | Hmmm. That would make sense. |
| 04:06:12 | pik_ | I may never know if that would have done it, though :) |
| 04:07:04 | TomW | pik_: IIRC, when I did a "status" on the newly blob-ed flash, it came up saying that the kernel was at 0x20000 and that the ramdisk was at 0x1000000 (something like that), when I erased, the ramdisk showed up as being the same address as the kernel image. |
| 04:08:16 | pik_ | When I did status before I tried to boot, it showed the kernel and the ramdisk at 0x20000. |
| 04:08:24 | TomW | pik_: BTW, I stopped using that kernel, my pcmcia wouldn't work and I have things to get accomplished, so after some fussing with it, I scrapped it. |
| 04:08:39 | pik_ | Which kernel? |
| 04:08:52 | TomW | the latest CVS. |
| 04:09:08 | TomW | ... I prefer to build from source. |
| 04:09:43 | pik_ | I always did before, but I really wanted to start writing some graphical stuff, and didn't want to mess around with it. |
| 04:09:52 | pik_ | ..mistake :) |
| 04:10:00 | TomW | mmm. |
| 04:10:40 | TomW | JTAG hasn't been a big joy either. The thing acts really strange, almost like it is haunted. |
| 04:11:12 | pik_ | As long as it will work once. |
| 04:11:48 | pik_ | My electrical skills are way too out-of-use for this. |
| 04:12:14 | TomW | I spent several hours trying to get my JTAG working so I could put a fresh blob into a board that I screwed. I even redid the cabling, but the damned thing acted like it was getting a lot of noise from someplace. Then, suddenly, it started working for no apparent reason! |
| 04:12:40 | pik_ | ooh, bummer. |
| 04:12:56 | TomW | ... even tried two different Tux units and had the same problem with them all. |
| 04:13:05 | TomW | pik_: it is scary! |
| 04:13:52 | TomW | After an hour, I was praying "Lord, if I can get blob back in this thing, I promise..." ;-) |
| 04:14:13 | TomW | that was one of my 64Meg boards! |
| 04:16:06 | pik_ | I so wanted to write some interesting apps for the thing. I even inherited a pcmcia 802.11b card... but I guess it's no go for now. |
| 04:18:06 | TomW | That's why I have six Tux's, if I break one, I have more. I sacrificed (destroyed) one CPU board tracing out the PCB wiring to figure out how to upgrade the DRAM. |
| 04:19:04 | TomW | Now I only have four working units, the fifth one's CPU is being used for some other project. I can put that one back together later. |
| 04:19:58 | pik_ | Geepers. How do you get on with only four? |
| 04:20:11 | TomW | heh |
| 04:20:45 | TomW | Two are development units, the other two (a 16Meg & a 64Meg) units are in storage. |
| 04:21:43 | pik_ | I thought they were all 8MB, unless you replaced the sodimm. |
| 04:22:28 | TomW | I pulled one of them apart, the CPU is running on the workbench hooked up to a perf board. That CPU has an interface atteched to J602 in which I am attempting to get an IDE drive working on it. |
| 04:22:56 | pik_ | Ah-hah, there you are, J100. |
| 04:23:38 | TomW | No, you can replace the 8 one meg RAMs with 8 four meg RAMs on the main CPU board, then stick a 32Meg SODIMM into it to make a total of 64Meg of DRAM. |
| 04:23:56 | pik_ | oh. |
| 04:24:34 | pik_ | I am far too much of a moron to be doing this. Software is what I know. But I want to learn.. |
| 04:24:36 | TomW | pik_: http://TuxScreen.net/wiki/view/32MegRamUpgrade |
| 04:25:15 | pik_ | TomW: I think I remember the discussion on the list. |
| 04:25:26 | TomW | pik_: Hey! I have a lot of busted boards / designs littering my path to where I am now. |
| 04:26:01 | TomW | each time I learned a little more.. |
| 04:26:17 | pik_ | Problem is, I'm poor. |
| 04:26:28 | TomW | Tux's are cheap. |
| 04:26:41 | TomW | limited quantity, but cheap. |
| 04:26:59 | pik_ | You solder _those_ little things? You're an animal. |
| 04:29:03 | TomW | heh, takes practice. |
| 04:30:07 | TomW | I cheat, I use an X-acto knife to cut their pins loose from the bodies, then "wipe" the pins off the board. |
| 04:30:45 | TomW | I then have a $2K hot-air reflow setup that I use to solder them back on (solder paste). |
| 04:30:50 | pik_ | I knew I should have gone into electrical engineering. You people have so much more fun.. |
| 04:31:14 | TomW | yeah, if it don't do what you want it to, rewire it. |
| 04:31:43 | pik_ | Hmm, I always thought it was, "rewrite it". |
| 04:33:14 | TomW | depends on your point of view. I like to do software, it is just that when the platform is lacking, change it. I like doing that, actually both: software & hardware. |
| 04:33:29 | pik_ | Makes sense. |
| 04:34:03 | TomW | unfortunately, stuff like the Tux doesn't have SIMM sockets. |
| 04:34:20 | TomW | ... or schematics for that matter. |
| 04:34:23 | pik_ | ..or pci slots :) |
| 04:35:03 | TomW | heh |
| 04:35:23 | TomW | do you write software for a living, or just hacking around? |
| 04:35:42 | pik_ | I suppose you could call it a living. |
| 04:36:23 | TomW | uh-oh, sounds like a frustrated windoze programmer to me. You do your best work and the shit still crashes, eh? |
| 04:36:24 | pik_ | I'm an undergraduate in CS at Utah State, but most of the real software stuff I do is for the Debian packages I maintain. |
| 04:36:33 | pik_ | Oh no, I don't touch Windows. |
| 04:36:51 | pik_ | I enjoy what I do, and it's all linux, all the way, but I don't get paid all that much :/ |
| 04:37:03 | TomW | sometimes I have to, I cannot avoid it. I am a consultant and sometimes I need the money. |
| 04:37:29 | bmidgley | TomW: what route did you go to get a 32m sodimm working? |
| 04:37:31 | TomW | mostly Delphi. |
| 04:37:38 | pik_ | I'm still hoping to avoid that. I can do the visual c++ thing, but I really hate it. |
| 04:38:14 | TomW | I don't like C++, there are some redeming qualities about it, I like the operator overloading. |
| 04:38:51 | pik_ | Same here. C is far more elegant. |
| 04:39:00 | TomW | bmidgley: it is all documented on: http://TuxScreen.net/wiki/view/32MegRamUpgrade. The key is that you MUST get a 4K refresh 32Meg SODIMM. |
| 04:39:51 | TomW | I have been doing more perl for the down-n-dirty software that I need to crank out bytes to a laserjet or similar. |
| 04:40:42 | pik_ | I do that as well. I'm surprised, because I think perl is one of the ugliest hacks the open-source world has seen, but it does get a lot of jobs done fast. |
| 04:40:46 | TomW | ... but, you just cannot get the kernel to load a driver written in perl.. :-( |
| 04:41:17 | TomW | what do you do with debian? |
| 04:41:59 | pik_ | I maintain a few packages |
| 04:42:47 | pik_ | And I sponsor some packages for a friend of mine. |
| 04:42:52 | TomW | ok, I don't know if I could deal with that. Logistically it would drive me nuts trying to merge stuff and keep it running correctly. |
| 04:43:48 | pik_ | They're not X or anything. They're small enough that one person can maintain them. The easiest ones are the ones you write yourself :) |
| 04:44:00 | TomW | essentially, you are a step above what we used to call a 'librarian'? |
| 04:44:32 | TomW | not to denigrate what you are doing.. |
| 04:44:49 | pik_ | Close enough. |
| 04:45:07 | pik_ | But librarians don't get to rewrite the books they don't like. |
| 04:45:20 | TomW | yeah, doesn't pay that much. But, you are undergrad. In time.. |
| 04:46:01 | TomW | In time you can make really big mistakes and screw stuff up like the rest of us in the "real" world. :-D |
| 04:46:13 | pik_ | And get paid a lot more for it! |
| 04:46:26 | TomW | lol |
| 04:46:29 | bmidgley | TomW: looks tough. is there a way to get 40M without any soldering? |
| 04:49:27 | TomW | bmidgley: you cannot get 40Meg, I think that 24Meg is the most you can get due to the way the ARM kernel is structured. I keeps the RAM banks in "slots", then logically merges those "slots" to form a contiguous RAM image. The number of slots is limited, IIRC, to 8 slots. |
| 04:51:11 | bmidgley | maybe i'll get someone to part with a 64M board. i do have a day job :) |
| 04:51:50 | bmidgley | ...or use vnc for everything |
| 04:52:03 | TomW | bmidgley: IIRC, with a 4K refresh SODIMM (32Meg) installed in a stock Tux, then changed blob to use 12 ROWS on the DRAM, I got 32 Meg, not 40. But, my memory is not clear on that, I just replace the RAM on the CPU board and get 32Meg on the CPU board. Only takes me about two housr to change the RAM, test the unit, and put it back together. |
| 04:53:19 | bmidgley | that's not bad. did you just have to mask off pin71? |
| 04:53:47 | bmidgley | for the former i mean |
| 04:53:49 | TomW | No, I cut the traces that were grounded. Don't bother with tape, just cut them. |
| 04:55:43 | TomW | The SODIMM socket in the Tux is not a *standard* SODIMM socket, they added a whole bunch of other signals to the socket (address lines). Those "extra" pins are used to signal what type of SODIMM it is, a notebook will use an I/O port to read those pins so it can set the DRAM controller up to take full advantage of the SODIMM you insert. |
| 04:56:34 | TomW | When you put a "stock" SODIMM into a Tux, you short these "extra" address lines on the socket to GND. Then your Tux won't boot. |
| 04:57:27 | bmidgley | just pins 11 and 71? |
| 04:57:37 | TomW | There is only 4..5 pins that could cause problems like that, just buzz them out with an Ohmmeter and cut the offending ones loose from GND. |
| 04:58:03 | bmidgley | i see now, 11,69,70,71 |
| 04:58:18 | TomW | yup. |
| 04:59:29 | TomW | if you work in manufacturing, make friends (or give money to) one of the electronics techs that work with surface mount components, they can change the RAM for you. |
| 05:00:08 | bmidgley | i do live close to lineo. there are a bunch of tux freaks around |
| 05:00:42 | TomW | pik_: just for giggles, I want to take this one 64Meg Tux, add the 10Gig harddrive to it, then make it into a webserver. |
| 05:01:20 | bmidgley | if you power it with a potato maybe you could get on slashdot |
| 05:01:21 | pik_ | :) Why not just have it work over nfs? |
| 05:01:29 | TomW | hahaha! |
| 05:01:50 | TomW | pik_: naw, I has to run standalone. |
| 05:02:36 | pik_ | Maybe if you made it a *wearable* standalone wireless webserver powered by a potato... |
| 05:02:53 | bmidgley | ...in a beowulf cluster |
| 05:03:08 | TomW | lemons, I'll power it off lemons.. |
| 05:04:11 | bmidgley | well i better get to bed while the kids are sleeping. thx tom |
| 05:04:19 | TomW | bmidgley: later |
| 05:04:29 | TomW | pik_: you write X apps? |
| 05:04:39 | pik_ | Yeah. |
| 05:05:36 | TomW | I was looking at the matchbox sources, it kind of reminds me of my early windoze 3.1 programming. So much detail goes into getting things accomplished! |
| 05:06:12 | pik_ | When they just use X calls, that is absolutely true. |
| 05:06:14 | TomW | bitblt and all that junk. |
| 05:06:41 | TomW | do you use any libs? Athena or something? |
| 05:07:05 | TomW | If you tell me TrollTech, I won't talk with you anymore! |
| 05:07:11 | TomW | heh |
| 05:07:29 | TomW | hates QT embedded license. |
| 05:07:32 | pik_ | gtk is the one I know best. |
| 05:07:59 | TomW | hmm, wonder how that would translate into ARM code on the Tux? |
| 05:08:25 | pik_ | There was some work making gtk run right on a framebuffer, but I'm not sure where that has gone. |
| 05:09:06 | TomW | same ol' story: if you do embedded stuff, you have to do it all yourself.. |
| 05:09:18 | pik_ | Good way to learn stuff. |
| 05:09:40 | pik_ | I'd personally love to see gtk on a framebuffer; I wouldn't have to run X as much. |
| 05:09:57 | TomW | lousy way to get big projects accomplished. Just when you get it down, someone comes along with a Delphi / Kylix. |
| 05:09:58 | Russ | TomW: there have been gtkfb ports in the past |
| 05:10:46 | TomW | Russ: We'll have to get pik_'s Tux fixed then an turn him loose on it. ;-) |
| 05:11:00 | Russ | whats wrong with it |
| 05:11:20 | pik_ | I bricked it trying to install the 0.6 images. |
| 05:11:39 | TomW | sounds like blob is screwed. |
| 05:11:50 | Russ | pik_: what excatly happened? |
| 05:12:11 | Russ | http://news.gnome.org/gnome-news/978625013/index_html |
| 05:12:47 | pik_ | Russ: I just found on gnome.org that gtkfb seems to be a stable part of gtk+-2.0. |
| 05:13:13 | Russ | http://people.redhat.com/~alexl/gtkfbscreenshots.html |
| 05:13:23 | Russ | http://www.directfb.org/gtk.xml |
| 05:13:26 | TomW | Russ: impressive. |
| 05:13:28 | pik_ | Russ: I downloaded and flashed the blob-20020501a, and it came up when I rebooted to it.. |
| 05:14:31 | pik_ | So I xdownloaded and flashed the ramdisk image. 'status' looked like everything was ok, so I tried 'boot' and the old kernel started to boot, couldn't find init, and panic'd. When I power cycled nothing came up, nothing went to minicom, and I can't get it to do anything now. |
| 05:14:59 | Russ | at what baud? |
| 05:15:11 | pik_ | 115200 |
| 05:15:36 | Russ | http://people.redhat.com/~sopwith/images/bargain.jpg |
| 05:15:43 | Russ | do you have flow control on? |
| 05:17:03 | pik_ | No. I was talking to the tux before with minicom, when I was flashing, etc, and it was the same minicom session. |
| 05:17:17 | Russ | right, but do you? |
| 05:17:32 | TomW | Russ: heh, you shop there often? |
| 05:17:40 | Russ | not my image |
| 05:18:04 | pik_ | No, flow control is definitely off. |
| 05:18:30 | TomW | pik_: what part of the US are you in? |
| 05:20:05 | pik_ | Northern Utah |
| 05:20:37 | TomW | mmm, guess you won't be driving into NorthEastern PA to get your Tux reflashed then? |
| 05:20:59 | pik_ | hmmmmm. |
| 05:21:09 | TomW | yeah, right. |
| 05:21:32 | pik_ | I'm within an hour and a half of andersee and tim riker, but I think I might need to learn this myself |
| 05:22:05 | TomW | well, there you go. Drive over to Tim's and pick up a dongle. |
| 05:22:39 | pik_ | Does he have a lot? |
| 05:23:16 | TomW | He had dongles, then was out of them, IIRC he said he had more coming in? |
| 05:23:46 | TomW | andersee: do you know if BZFlag has more JTAGs yet? |
| 05:24:57 | TomW | Russ: thanks for those links, gtkfb looks interesting. |
| 05:25:27 | pik_ | http://developer.gnome.org/doc/API/2.0/gtk/gtk-framebuffer.html seems to be the place to go. |
| 05:26:35 | TomW | yeah, more detailed. |
| 05:27:07 | TomW | added that one to my "bookmarks I'll never get around to later", life is too short. |
| 05:33:30 | pik_ | I've heard some of the people I work around mention JTAGs.. they work with AICs and SICs and such. Might theirs work for me, if I get those 13 pins soldered to J100? |
| 05:36:13 | TomW | probably better off getting one of your own, you never know when it could happen again and they are $30. |
| 05:36:28 | pik_ | bummer. |
| 05:36:54 | pik_ | But would theirs work, at all? Is it the same thing? |
| 05:37:13 | TomW | You could wire one up yourself, there is < $8 in parts needed to build one of those things. |
| 05:37:53 | TomW | Theirs could work, let them look at the schematics that are on the Wiki for the JTAG. |
| 05:38:15 | pik_ | good deal. I'll try to make my own, I believe. |
| 05:38:32 | TomW | ... assuming, of course, that they can read schematics... You know these software pukes can't read. :-D |
| 05:38:42 | TomW | heh heh |
| 05:38:56 | pik_ | :) |
| 05:40:34 | TomW | just keep the wires short, lay them out so they look almost like you used a comb to make them look nice. |
| 05:40:52 | TomW | resist the urge to "bundle" them together. |
| 05:41:13 | TomW | It shouldn't be critical. |
| 05:42:15 | TomW | I have to buzz out the wiring on the Tux CPU, the schematics on the Wiki are wrong. |
| 05:42:29 | TomW | <sigh> I am procratinating again.. |
| 05:42:45 | TomW | s/procratinating/procrastinating/ |
| 05:44:15 | pik_ | Shoot, I wish I hadn't tried to use those images. |
| 05:45:01 | pik_ | I think I could get gtkfb working on the thing, that's right up my alley. |
| 05:45:08 | TomW | that is what developing is about, calculated mistakes. |
| 05:45:34 | TomW | it happens. |
| 05:46:00 | pik_ | Yup. |
| 05:46:02 | TomW | knowing myself, I ordered a JTAG with the 2nd Tux. |
| 05:46:19 | DarkDream | Yo |
| 05:46:21 | DarkDream | :) |
| 05:46:28 | DarkDream | Little hello from Belgium |
| 05:46:41 | DarkDream | I've just get up ;) |
| 05:46:41 | TomW | yeah, short. |
| 05:46:45 | DarkDream | TomW: :p |
| 05:47:26 | DarkDream | I've a little question :) |
| 05:47:41 | TomW | pik_: just don't you love that sickening feeling that you get when you screw something up? Makes you feel more alive.. :-/ |
| 05:48:04 | TomW | DarkDream: go ahead. |
| 05:48:06 | DarkDream | I've ordered a Tux in Belgium. Is it possible to share an Internet Connection with the Tux ? |
| 05:48:41 | pik_ | DarkDream: Sure, no reason why not. |
| 05:48:53 | TomW | Theoretically, you could add two PCMCIA network cards into it, probably get netfilter + iptables running in the kernel.. |
| 05:49:54 | TomW | it is Linux, just running under an ARM processor. |
| 05:49:57 | DarkDream | Ok :) and is it possible easily to upgade the memory ? And do you have a tweak to add mass storage ? :) |
| 05:50:01 | pik_ | There is a working netfilter in the arm kernel tree. |
| 05:50:14 | TomW | pik_: cool. |
| 05:50:15 | DarkDream | TomW & pik_: Thx :) |
| 05:51:00 | TomW | I am running 64Meg of DRAM in two of my Tux's. |
| 05:51:29 | TomW | still working at getting a 10Gig IDE notebook drive to work.. |
| 05:51:39 | DarkDream | Wowwwwwwwwwwwwwwww :) |
| 05:52:03 | pik_ | How well do pcmcia microdrives work? |
| 05:52:13 | TomW | the jury is still out on that one. I have some problems to iron out with the signals / operation of J602 on the CPU board. |
| 05:53:15 | TomW | Dunno, there was someone using a Type-II microdrive, took up both PCMCIA slots. fontenot is running a PCMCIA --> IDE adaptor card to use a 3Gig drive in one of his. |
| 05:54:15 | TomW | this is DRAM upgrade info: http://TuxScreen.net/wiki/view/32MegRamUpgrade |
| 05:54:36 | DarkDream | TomW: easy to upgrade for a dimmie in electronic ? :) |
| 05:55:04 | DarkDream | File Not Found |
| 05:55:25 | DarkDream | The requested URL was not found on this server. |
| 05:55:41 | DarkDream | I've often this message for a lot of pages... |
| 05:56:03 | pik_ | DarkDream: ? TomW's link comes up ok for me. |
| 05:56:16 | TomW | DarkDream: comes up for me (in U.S.). |
| 05:56:42 | DarkDream | it's very strange |
| 05:56:43 | TomW | Must be that someone didn't pay the EU Custom charges? :-) |
| 05:56:58 | DarkDream | because tuxscreen.net works |
| 05:57:05 | DarkDream | but not this page |
| 05:57:26 | TomW | Then goto "wiki changes", type 32Meg in the Search. |
| 05:58:48 | pik_ | DarkDream: It comes up ok for me from an account on a machine in NL, as well. |
| 05:59:04 | DarkDream | pik_: very strangeeeeeeeeeeeeeeeeeeeee |
| 05:59:12 | pik_ | nods |
| 05:59:22 | DarkDream | I can only go on the main page (TuxScreen.net) |
| 06:00:16 | TomW | maybe it is a prob with Konquerer? It works with netscape. |
| 06:00:35 | DarkDream | TomW: even with mozilla and opera |
| 06:01:08 | TomW | Are you behind a firewall / proxy? |
| 06:01:42 | DarkDream | even in windows when I work (sometimewellwell :) |
| 06:01:49 | DarkDream | TomW: no direct connection |
| 06:02:00 | DarkDream | I've this problem and some friends also |
| 06:02:01 | TomW | try this then: http://www.openhardware.net/TuxScreen/32MegDram.html |
| 06:02:33 | DarkDream | it works |
| 06:02:44 | DarkDream | :) |
| 06:02:50 | DarkDream | Strange no ? |
| 06:03:27 | TomW | yeah, you probably got some kind of firewall there looking for CodeRed or something. It sounds as if your ISP is "helping" to keep you away from "bad" things. |
| 06:04:05 | DarkDream | TomW: the error message comes from the webserver... |
| 06:04:09 | TomW | heh, or they are runing Win2k servers and it don't like linux sites? |
| 06:04:46 | DarkDream | My provider don't know Linux I think :) |
| 06:06:36 | DarkDream | TomW: check the error message comes from the webserver.... try a wrong url your site you will have the same message |
| 06:07:07 | DarkDream | Few days that I wanted to say that to you on icq but I've never seen you online :D |
| 06:07:35 | DarkDream | Sorry for my poor English |
| 06:07:36 | DarkDream | :/ |
| 06:09:05 | andersee | TomW: I'm afraid I don't know if he has anymore... |
| 06:09:17 | TomW | k, tnx Erik. |
| 06:09:47 | DarkDream | Is it dangerous to Flash the Tux ? |
| 06:10:53 | TomW | it is the time when things could go very wrong. It doesn't happen if you carefully follow the directions (http://www.openhardware.net/TuxScreen/index.html) but it can happen occasionally. |
| 06:11:35 | TomW | you have to reflash the Tux to get the blob installed. Blob is what is used to install linux. |
| 06:11:41 | pik_ | Yeah, some people never have problems *sniff* |
| 06:12:00 | TomW | pik_: chin up old boy. |
| 06:12:12 | pik_ | chins up an old boy |
| 06:12:17 | TomW | pik_: take it like a nerd. |
| 06:12:23 | DarkDream | TomW: Well I've to go work |
| 06:12:25 | pik_ | :) |
| 06:12:26 | DarkDream | heurk :) |
| 06:12:37 | TomW | DarkDream: later. |
| 06:12:40 | DarkDream | With these japanese people |
| 06:12:43 | DarkDream | :) |
| 06:13:06 | DarkDream | They work like crazy |
| 06:13:20 | DarkDream | byeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee |
| 06:14:25 | TomW | hmm, looks like GPSFan has some other schematics on the Wiki for the CPU board, maybe these are the ones that are corrected. |
| 06:18:47 | TomW | nope, those are incorrect as well. well, looks like I will spend a few hours with the Ohmmeter tomorrow tracing out the wiring. |
| 06:19:18 | pik_ | TomW: So how do I get a job where I can play around with TuxScreens for hours every day? |
| 06:19:39 | TomW | practice. |
| 06:19:53 | TomW | then some day you can have a job like mine. |
| 06:20:51 | TomW | pik_: work is slow right now, so I am trying to learn a new skillset so that I can market it later (ARM). |
| 06:25:34 | pik_ | I believe I'm going to bed. jtags can wait for another day. |
| 09:00:00 | | bonjour, mallum |
| 09:00:00 | mallum | hi |
| 12:17:26 | Harlekin | Morn: ping |
| 12:17:27 | Harlekin | Morn: ping |
| 13:26:12 | | privet, Morn |
| 13:26:12 | Morn | hi |
| 13:26:23 | Morn | I'm still not up, really |
| 13:26:27 | Morn | this is ghost typing |
| 13:27:27 | Harlekin | Morn: how is opie on tuxscreen peforming right now? |
| 13:28:14 | Morn | I have to reinstall it, I redid the server that the NFS mount was on and forgot to back up the opie dir (duh!) |
| 13:36:31 | Harlekin | Morn: what about the tuxscreen memory |
| 13:36:34 | Harlekin | and progress there? |
| 13:36:43 | Harlekin | Morn: so opie can be put on there |
| 14:17:29 | Morn | Harlekin: I don't think anything has been done with the memory issue yet |
| 14:24:45 | Harlekin | Morn: btw, do you need special start parameter for opie on tuxscreen? like rotation or screen width? |
| 14:25:04 | Morn | I just changed the init script to not rotate it |
| 14:25:19 | Harlekin | and width, hight? |
| 14:25:34 | Harlekin | so tuxscreen needs rotation=0 |
| 14:25:36 | Morn | they just work ok |
| 14:25:48 | Harlekin | is there any tuxscreen specific file in /proc? |
| 14:25:59 | Harlekin | Morn: i am right now making the start script better |
| 14:26:04 | Harlekin | autodetection |
| 14:27:12 | file | peers around the room |
| 14:27:20 | Morn | cool |
| 14:27:24 | file | pokes prpplague |
| 14:27:32 | Harlekin | Morn: but you need to increase teh screensize to |
| 14:27:43 | Morn | I didn't increase the screen size |
| 14:27:46 | Morn | it just worked |
| 14:27:50 | Harlekin | Morn: so its only 320x240 |
| 14:28:02 | file | prpplague : awaken please |
| 14:28:04 | Morn | I removed the line to reszie/rotate |
| 14:29:37 | Harlekin | there is no size line |
| 14:29:38 | Harlekin | hmm |
| 14:29:45 | Harlekin | Morn: any spezific file in proc? |
| 14:32:37 | file | slaps prpplague |
| 14:36:06 | prpplague | file: whats up? |
| 14:36:12 | file | prpplague : any news? |
| 14:36:27 | prpplague | file: please..... |
| 14:36:32 | file | stop asking? |
| 14:36:40 | prpplague | file: i said at least a couple of weeks |
| 14:36:54 | file | it's been a week! |
| 14:37:02 | prpplague | hmm, couple=2 |
| 14:37:03 | file | :) |
| 14:37:14 | file | well I thought maybe there'd be a LITTLE news |
| 14:37:46 | file | hums |
| 14:38:03 | TomW | prpplague: good morning. |
| 14:38:15 | prpplague | TomW: morning, how goes the dev board? |
| 14:38:23 | TomW | excellent! |
| 14:39:06 | file | that's good |
| 14:39:15 | prpplague | TomW: i'm still waiting on parts |
| 14:39:18 | TomW | there is a mod that has to be done to the CPU board to allow the J602 connector to write data. Without the mod, it is a read-only port. The mod is fairly simple. |
| 14:39:40 | TomW | prpplague: you want the "advance" schematic? |
| 14:40:00 | | i heard prpplague was mailto:dave123@abcsinc.com |
| 14:40:00 | prpplague | ibot: prpplague |
| 14:40:13 | TomW | ok. |
| 14:40:50 | prpplague | TomW: so you got the drive working? |
| 14:42:36 | TomW | prpplague: not yet, it took me many hours to figure out how to make J602 write to the drive. I am now writing data into the drive registers and reading the values back out again. I can assert a hardware RESET to the drive. |
| 14:44:14 | TomW | GPSFan: correction on the schematics. U500.4 actually goes to U403.48 and U402.36 goes to U403.25 |
| 14:44:53 | TomW | prpplague: I sent the ps file as for some reason Acrobat won't print the pdf. |
| 14:45:46 | file | sighs |
| 14:45:47 | TomW | prpplague: the mod is simple: lift one pin, cut one trace and add two jumper wires. |
| 14:45:50 | file | I think I'm bored |
| 14:45:59 | TomW | file: your fault then! |
| 14:46:09 | TomW | heh |
| 14:46:24 | file | I'm gonna go code |
| 14:48:31 | TomW | prpplague: you cannot use A0 from J602, don't know why it is there? You can only put #CS3 into 16bit mode. Maybe the ARM has something like emitting an A0 value if you access a u16 on an uneven boundry? I don't know ARM that well. |
| 14:49:38 | file | erm |
| 14:49:39 | prpplague | TomW: fun |
| 14:49:41 | file | thinks |
| 14:49:52 | prpplague | TomW: i hope to do some tinkering this weekend |
| 14:50:18 | prpplague | TomW: have you made any decisions on processor type for your customer? |
| 14:50:39 | TomW | nope, still tinkering at my end as well. |
| 14:51:51 | TomW | all the work on the IDE drive will payoff when I start working with the perf board (evaluation), now I know how to do "it". |
| 14:53:21 | prpplague | TomW: gotcha |
| 14:53:25 | file | hrm |
| 14:53:41 | prpplague | TomW: well when you start getting to the point of making a decision, let me know |
| 14:54:13 | prpplague | TomW: there are about 5 of us who have seperate projects, maybe when can pull resources and get a single board done and save some money |
| 14:54:28 | TomW | prpplague: I would like to issue an IDENTIFY command to the drive and see what happens next. That will be a test of my interface to the 16bit data port of the drive. |
| 14:55:10 | prpplague | TomW: man, sounds like your doing some fun hacking |
| 14:55:20 | prpplague | is still stuck doing SCO2Linux migration |
| 14:55:48 | TomW | prpplague: or, at least avoid duplication of efforts in designing various (sub)systems of the board(s). |
| 14:56:17 | TomW | worthy project, soon you will be cleansed of SCO. |
| 14:56:30 | prpplague | amen |
| 14:56:48 | TomW | ... then you can "play" with linux. |
| 14:59:11 | TomW | this is fun? well, hacking the hardware is serious business, this way I get to understand more about the ARM processor, and, even get a more potent toy to play with. :-D |
| 15:00:26 | CosmicPenguin | prpplague: another nail in the coffin for SCO, eh? |
| 15:00:36 | CosmicPenguin | prpplague: sucks for us - nobody wants SCO emulation anymore,,, :) |
| 15:00:41 | TomW | GPSFan: signals on pins 7 & 8 of J602 should be swapped: pin 7 is UDC+ signal. |
| 15:00:58 | prpplague | CosmicPenguin: lol |
| 15:01:01 | TomW | lol. |
| 15:01:30 | TomW | ... all that investment in time & money, down the toilet.. |
| 15:02:10 | CosmicPenguin | Yeah, but Caldera lost money last year, but Rasom Love says that was a good thing: http://www.linuxandmain.com/modules.php?name=News&file=article&sid=57 |
| 15:02:46 | TomW | he probably will claim that it was a "strategic re-alignment". |
| 15:03:36 | TomW | "no, honest, we'll make money next quarter...". :-/ |
| 15:07:10 | CosmicPenguin | LinuxDevices.com just reported on the scoop about the anti GPL clause in the CIFS licence for Microsoft... good to see that they're on the ball... :( |
| 15:08:00 | TomW | prpplague: do me a favor, can you print that pdf that I sent to you? Will Acrobat print it? |
| 15:08:59 | prpplague | TomW: ya give me a sec |
| 15:09:39 | prpplague | TomW: hmm, haven't got anything yet |
| 15:10:29 | TomW | that is what I was afraid of, either my EagleCAD makes crappy postscript output files, or ps2pdf is goofy. |
| 15:10:55 | prpplague | TomW: no, i mean i've not receive an email yet |
| 15:13:08 | TomW | looks like it left here.. |
| 15:14:46 | prpplague | TomW: we are having a lot of internet issues here in east texas this morning |
| 15:14:53 | prpplague | TomW: bad storm last night |
| 15:18:36 | TomW | prpplague: dave123@abcsinc.com _User_Unknown/Giving_up_on_12.148.134.2 |
| 15:19:17 | TomW | prpplague: yup, it bounced. |
| 15:28:29 | prpplague | TomW: hmm |
| 15:29:17 | prpplague | TomW: try it now, dave123@abcsinc.com |
| 15:33:18 | TomW | prpplague: looks like it went through this time? |
| 15:33:48 | TomW | prpplague: yup, it is there. |
| 15:34:22 | prpplague | TomW: yep got it |
| 15:34:26 | prpplague | TomW: give me a sec |
| 15:36:07 | prpplague | TomW: looks good, nice clean readable |
| 15:36:27 | TomW | prpplague: the pdf printed ok? |
| 15:36:48 | prpplague | TomW: ya i printed from xpdf on rhat 7.1 with no problems |
| 15:37:11 | TomW | drat, that means it is the freakin' cups is messed up. |
| 15:37:36 | TomW | I am beginning to hate cups. |
| 15:39:28 | prpplague | TomW: ya, i'm more on the end of lpd and even more simple redirection |
| 15:39:45 | TomW | prpplague: AHA! I am running the 2.4.3 kernel right now, let me reboot under 2.4.18 brb |
| 15:44:41 | TomW | prpplague: nope, cups is buggered. |
| 15:45:05 | TomW | will never learn |
| 16:16:55 | CosmicPenguin | How many times do I have to tell you? Kids never learn |
| 16:17:29 | dc_ | CosmicPenguin: don't say that :/ |
| 16:18:21 | CosmicPenguin | dc_: tis a simpson's quote. TomW's comment just reminded me of it |
| 16:18:46 | dc_ | :} |
| 16:21:21 | GPSFan | TomW: got your changes, that was an area that was quite involved to trace out. Thanks for the corrections, I'll get them in soon. |
| 16:25:14 | TomW | GPSFan: I have a schematic to submit to the wiki. It is a mod to allow data to be written to J602. |
| 16:28:03 | | well, 2.4.3 is scary code |
| 16:28:03 | fontenot | 2.4.3 ? |
| 16:31:10 | TomW | ah! I got the drive ID data from the Identify Drive command. Looks like it is working! |
| 16:44:11 | GPSFan | TomW: what we usually do with schematics id produce a .ps and .pdf. If you can generate them I'll integrate them into the wiki page, or you can do it youreself. Looks like your IDE mod is well on its way to working. |
| 16:51:42 | prpplague | TomW: wahoo, you got the ID? cool |
| 17:00:34 | TomW | prpplague: .. and the number of cylinders and number of heads. |
| 17:10:09 | TomW | ok, can read both drives, the 10G IBM and the 340M Seagate. |
| 17:21:57 | Morn | is away: grocery shopping... |
| 17:36:27 | prpplague | returns after cooling fan upgrade |
| 18:42:20 | file | waves to prpplague |
| 18:43:04 | prpplague | file: howdy howdy |
| 18:43:23 | file | wazzup? |
| 18:43:26 | prpplague | ssdd |
| 18:44:27 | pattieja | hello prpplague |
| 18:44:51 | prpplague | pattieja: howdy, long time no chat |
| 18:44:56 | prpplague | pattieja: how goes it? |
| 18:45:30 | pattieja | installing OPIE on the iPAQ |
| 18:45:41 | pattieja | PDA that is |
| 18:46:05 | pattieja | I'm really thinking about trying to get either Qtopia or OPIE (most likely OPIE after what I've seen of it) onto my iPAQ IA-1 at home |
| 18:46:55 | file | is coding |
| 18:47:03 | file | and going |
| 18:47:04 | file | bbl |
| 20:27:41 | andersee | is away: off to the bank to shuffle money about |
| 21:21:59 | andersee | is back (gone 00:54:18) |
| 21:27:39 | as_ | Evnin all. |
| 21:38:39 | pik_ | I have borrowed a JTAG from the lab next door made by Insight Electronics. The leads have all the same names as the ones in the wiki, but the schematics seem different. Anyone know if I'm safe trying to use it? |
| 21:38:49 | pik_ | ..on my tux, that is |
| 22:01:26 | Vito` | Over 300? Thought it was down to over 200. |
| 22:04:15 | jacques_gone | stupid chanserv keeps scrweing up the topic |
| 22:05:01 | jacques | correct figure is 200 |
| 22:12:04 | jacques | hi andersee |
| 22:12:15 | jacques | i believe ti mis out of jtag at the moment too |
| 22:13:08 | andersee | hi jacques |
| 22:13:24 | andersee | I wish the topic wouldn't keep getting messed up |
| 22:13:35 | jacques | andersee: Ive been too busy to build a new toolchain :-( |
| 22:13:45 | jacques | me too |
| 22:25:09 | pik_ | Okay, I'm trying my jtag. Will it work without the touchscreen and keypad connected? |
| 22:30:19 | pik_ | Well, if anyone was wondering, the Insight JTAG is not working. I get "failed to read device ID" with and without power to the device, and with or without the touchscreen and keypad connected. |
| 22:33:24 | andersee | jacques: no problem. I'm been awfully busy myself |
| 23:53:43 | jacques | how are ppl doing with the latest buildroot? |
| 23:54:01 | jacques | is there a tag for the old kernel/ramdisk scheme? |
| 23:54:13 | jacques | what about ppl who are too scared to try the new blob? |
| 23:56:09 | jacques | what's the success rate for new blob? |
| 23:56:20 | jacques | any tips to avoid bricking? |
| 23:58:39 | pik_ | jacques: I bricked mine with 20020501a |
| 23:58:48 | jacques | pik_: not good not good not good |
| 23:58:51 | jacques | "=( |
| 23:58:54 | jacques | :-( |
| 23:59:13 | jacques | pik_: what's the size of that blob? |
| 23:59:23 | pik_ | 28108 |
| 23:59:36 | jacques | arg |
| 23:59:44 | jacques | did you ever find out what the problem is? |
