| 00:06:23 | Russ|werk | away (doesn't work :() |
| 00:10:55 | jacques | lol |
| 00:12:48 | jacques | ARG |
| 00:13:03 | jacques | 2.95 toolchain is having issues trying to build |
| 00:13:52 | jacques | i would paste the error but it's long and does not look helpful at all |
| 00:13:59 | jacques | dammit |
| 00:14:09 | jacques | i am not effectively shutout |
| 00:14:20 | jacques | my toolchain no longer builds uclibc and I cant build one that does |
| 00:14:27 | jacques | not==NOW |
| 00:16:36 | jacques | andersee: does 2.95 toolchain actually build when TARGET_PATH != "${BASEDIR}/toolchain" ? |
| 00:17:04 | jacques | I seem to remember having a similar issue with the 3.x toolchain |
| 00:19:02 | TomW | is away: I'm busy |
| 00:19:15 | TomW | is back (gone 00:00:13) |
| 00:19:44 | jacques | someone's fancy sed line appears to be getting confused |
| 00:27:32 | jacques | WTF??? |
| 00:28:01 | jacques | drivers/char/char.o(__ksymtab+0xe8): undefined reference to `spi_cleanup' |
| 00:28:09 | jacques | i had only gotten that with gcc3 |
| 00:28:13 | jacques | until now |
| 00:29:19 | TomW | jacques: what *are* you doing?! |
| 00:29:57 | jacques | scrwe it |
| 00:30:00 | jacques | giving up |
| 00:30:07 | TomW | oh |
| 00:30:16 | jacques | TomW: Im trying to do soehting I have dont a 100 times |
| 00:30:20 | jacques | build buildroot |
| 00:30:31 | TomW | latest from cvs? |
| 00:30:34 | jacques | but since uclibc changed so that my toolchain wont compile it anymore |
| 00:30:40 | jacques | i have to use a differnt toolchain |
| 00:30:50 | jacques | and thus started my current problems |
| 00:31:21 | TomW | what toolchain is required now? |
| 00:31:45 | jacques | bserver% which arm-linux-gcc |
| 00:31:45 | jacques | /usr/local/arm/bin/arm-linux-gcc |
| 00:31:46 | jacques | bserver% arm-linux-gcc -v |
| 00:31:46 | jacques | Reading specs from /usr/local/arm/lib/gcc-lib/arm-linux/2.95.4/specs |
| 00:31:46 | jacques | gcc version 2.95.4 20010319 (prerelease) |
| 00:31:55 | jacques | bserver% ls -l /usr/local/arm/bin/arm-linux-gcc |
| 00:31:55 | jacques | -rwxr-xr-x 1 fontenot fontenot 201905 May 21 16:40 /usr/local/arm/bin/arm-linux-gcc* |
| 00:32:09 | jacques | so I;m not using the wrong gcc or anything stupid like that |
| 00:32:20 | jacques | TomW: seems like any toolchain but mine |
| 00:32:27 | jacques | since as usual I am the only one havin gproblems |
| 00:32:32 | TomW | hmmm. |
| 00:33:40 | TomW | if you had vmware you could install a fresh copy of linux into a virtual machine, install toolchain & buildroot and develope from there? |
| 00:34:11 | jacques | but which toolchain? |
| 00:34:25 | jacques | i dont like being dependednt and not knowing what's going on with the toolchains |
| 00:34:32 | jacques | which is why i like to use ones I have built |
| 00:34:58 | jacques | apt-get arm-cross-whatever is not for me |
| 00:35:12 | TomW | I am using 2.95.3, but haven't messed with the cvs stuff in a while now (> 4 weeks) |
| 00:35:37 | TomW | heh, you don't have 4 hours to compile glibc, eh? |
| 00:35:44 | jacques | well someone has to try building the cvs stuff, and it's turning out to be a dirty job |
| 00:36:05 | TomW | I'll give it a quick shot with 2.95.3... |
| 00:36:52 | jacques | let me know if resolve.c in uclibc craps out with internal compiler error, but I dont expect it will for you |
| 00:40:20 | TomW | building the kernel now |
| 00:40:34 | jacques | rebuilding toolchain without touching the makefile this time |
| 00:40:45 | jacques | TomW: the error I get is in uclibc |
| 00:41:07 | andersee | jacques: details? |
| 00:41:24 | andersee | jacques: things have been a'changin in CVS... |
| 00:43:08 | jacques | andersee: which details would you like? |
| 00:43:35 | andersee | jacques: the part about " |
| 00:43:41 | jacques | andersee: I believe we determined tha the internal compiler error I am getting in uclibc resolve.c is my toolchain's problem since nobody else has it |
| 00:43:43 | andersee | resolve.c in uclibc craps out" |
| 00:43:49 | andersee | ahh |
| 00:43:57 | | toolchain is at http://handhelds.org/z/wiki/Toolchains |
| 00:43:57 | andersee | What toolchain? |
| 00:44:03 | jacques | andersee: one I built myself |
| 00:44:04 | | Sorry, andersee, I'll keep my mouth shut. |
| 00:44:04 | andersee | ibot: shutup |
| 00:44:41 | jacques | andersee: mine is based on 2.95 head of a couple months ago and the phil blundell patch on his web page - none of the debian patches |
| 00:44:56 | andersee | k |
| 00:45:07 | jacques | andersee: I am more concerned about the problem I had trying to build your 2.95 toolchain |
| 00:45:19 | andersee | which was? |
| 00:45:21 | jacques | and the subsequent problem I had trying t ocompile the buildroot kernel with it |
| 00:45:43 | jacques | andersee: toward the end of the toolchain build, it errored out on a sed line |
| 00:46:00 | andersee | details? |
| 00:46:11 | jacques | andersee: I had changed the Makefile to TARGET_PATH=/usr/local/arm |
| 00:46:23 | andersee | recent cvs changes for i18n could easily have broken it... |
| 00:46:25 | jacques | I dont know if that caused it, but that's all I did |
| 00:46:37 | andersee | uClibc cvs that is... |
| 00:46:49 | jacques | ok I am trying to build the toolchain without touching the makefile now |
| 00:47:05 | jacques | if that fails in the same way, I will try older uclibc snaps and the release version |
| 00:47:11 | andersee | jacques: setting TARGET_PATH shouldn't make any difference. |
| 00:47:48 | spd_racer911 | TomW: I just sent you a reply via e-mail |
| 00:47:54 | andersee | needs to return some books and CDs to the public library |
| 00:48:00 | andersee | back in a bit |
| 00:48:03 | jacques | andersee: and get this - I tried building buildroot with your toolchain even though the build errored out, and I got that "drivers/char/char.o(__ksymtab+0xe8): undefined reference to `spi_cleanup'" error in the kernel build |
| 00:48:08 | spd_racer911 | andersee: linux books I hope |
| 00:48:20 | andersee | is away: I'm busy |
| 00:48:30 | jacques | which I had only seen with gcc3 before |
| 00:49:02 | spd_racer911 | jacques: I just want to personally say you and Tom W have done a great job getting tinyx running on the Tux! |
| 00:50:07 | jacques | spd_racer911: thanks :-) |
| 00:50:20 | jacques | d'oh sae error building toolchain |
| 00:50:23 | jacques | same |
| 00:50:29 | jacques | will try older uclibc snaps now |
| 00:51:23 | TomW | jacques: built ok under 2.95.3 |
| 00:53:29 | jacques | TomW: great :-\ |
| 00:53:36 | TomW | heh |
| 00:54:10 | TomW | I need a Root Beer Float with Vanilla ice cream. bbl |
| 00:54:13 | TomW | is away: I'm busy |
| 01:10:19 | jacques | andersee: same toolchain build error with uclibc snap from sometime before May 8th |
| 01:27:37 | Morn | hi |
| 01:58:44 | prpplague | hmm, must have gotten a "wild" card,lol |
| 03:17:25 | prpplague | andersee: OLS? |
| 03:35:34 | Morn | is away: sleeping |
| 04:07:37 | andersee | prpplague: no plans to attend at the moment... |
| 04:07:54 | prpplague | andersee: bummer |
| 04:09:02 | prpplague | andersee: so far it sounds like it should be "ottawa embedded linux syposium" |
| 04:09:04 | jacques | andersee: I had the same problem trying to build the 2.95 toolchain with a uclibc snap from before May 8th |
| 04:09:37 | jacques | andersee: can you just download the 2.95 tarball and type 'make' ? |
| 04:09:43 | jacques | I think you should see the problem |
| 04:09:47 | andersee | prpplague: sounds like it would be a lot of fun. But it is a bit expansive and with a new baby here, my wife would be ticked if I took off. |
| 04:10:05 | andersee | jacques: Hmm. It worked for me... |
| 04:10:20 | andersee | dunno. |
| 04:10:35 | prpplague | andersee: ohh i forgot about the new "sub processor unit" lol |
| 04:10:42 | andersee | I'm getting the gcc 3.1 build put together at the moment.. |
| 04:10:49 | prpplague | andersee: doing well? |
| 04:11:07 | jacques | andersee: OK |
| 04:11:16 | jacques | andersee: it worked for you when? |
| 04:11:57 | prpplague | andersee: hope you got a diaper genie....... |
| 04:12:24 | jacques | andersee: if I can build the kernel with 3.1 maybe I dont care about 2.95 |
| 04:13:11 | prpplague | andersee: btw, dis-assembled mac se-30's make great toys, lol |
| 04:16:51 | andersee | prpplague: I've got a disassembled Qube2 on my desk. That count? |
| 04:17:38 | prpplague | hmm, the mac keyboards are just so much fun.......... |
| 04:18:53 | andersee | hehe |
| 04:22:31 | jacques | downloading 2.95 toolchain source ot my home mahine to see if it works there |
| 04:29:49 | prpplague | well of to bed, i have another [ ! $highly_rewarding ] of non posix ksh conversions to posix sh tomorrow |
| 04:30:48 | prpplague | night all |
| 04:30:54 | jacques | night prpplague |
| 04:58:36 | jacques | same problem building 2.95 toolchain on my home machine |
| 04:59:15 | jacques | error is half a page long |
| 10:10:40 | Sammy | can any one give me a hint about what terminal mode should tuxscreen use ? |
| 10:10:50 | Sammy | is that 9600 8N1 ? |
| 10:11:01 | ctr | 115200 |
| 10:11:36 | Sammy | ctr: 115200 at ttyS0 ? |
| 10:12:03 | ctr | yesh |
| 10:13:09 | Sammy | because , I use jtag download the blob into tuxscreen , but after it finish , and terminal don't show any info ... |
| 10:13:19 | Sammy | should I reboot ? |
| 14:06:55 | pattieja | is away: iTEC |
| 14:51:41 | Morn | is back (gone 11:16:08) |
| 19:44:49 | MicroChip32 | hmmm no more jtags? does that mean no more availble, or theyre not needed any more ? |
| 19:46:12 | MicroChip32 | is the basic tux have sufficient memory in it to do a remote boot, aka boot and run from a remote partition ? |
| 19:58:09 | MicroChip32 | anyone alive ? |
| 20:01:17 | prpplague | MicroChip32: just means that BZFlag has no more jtags |
| 20:01:46 | prpplague | MicroChip32: yes it has suffiecient memory for remote boots, i've even used mine with ltsp |
| 20:01:57 | prpplague | MicroChip32: and no, no one is alive |
| 20:19:35 | MicroChip32 | prpplague can you help me set up for remote boot? I havent done anything to the tux yet (as far as linuxing it) and dont have $ to get a pcmcia drive or other form of memory expansion |
| 20:23:04 | BZFlag | jtag is not required for a linux install. |
| 20:23:12 | BZFlag | just for recovery of a bad install |
| 20:23:44 | BZFlag | well, a bad bootloader install. kernel/rootfs can be recovered without jtag. |
| 20:23:49 | kergoth | BZFlag: did sharp ever get you a jtag for the Z? |
| 20:23:54 | BZFlag | nope. |
| 20:23:54 | kergoth | (OT) |
| 20:23:58 | kergoth | thats annoying. |
| 20:24:02 | BZFlag | yep. |
| 20:24:15 | MicroChip32 | BZFlag: yep i know that, i have the chips to make my own jtag if necessary |
| 20:24:29 | kergoth | BZFlag: is any of the work on porting the Z kernel forward done and open sourced atm? |
| 20:25:13 | MicroChip32 | right now im just looking for how to set up for a remote boot over serial since I understand the raw tux doesnt have sufficient memory for a full linux system |
| 20:40:56 | MicroChip32T | grrr, daggone ghosts |
| 20:47:26 | MicroChip32T | kicks microchip32 |
| 20:48:41 | MicroChip32 | ha, eat that, ghost |
| 20:52:50 | BZFlag | kergoth: a plan yes, but I have not had the time to put into it. |
| 21:04:00 | kergoth | BZFlag: k, cool. just checking. I decided to start on it, since im bored. |
| 21:07:00 | kergoth | BZFlag: is the Z a sa1100 or sa1110? |
| 21:07:42 | kergoth | sa1100 right? |
| 21:15:27 | BZFlag | kergoth: sa1110 |
| 21:16:00 | Morn | is away: I'm busy |
| 21:16:17 | BZFlag | kergoth: I'd recommend starting with 2.4.18-rmkfoo and applying the z patch to it, then fixing any issues. |
| 21:16:24 | kergoth | BZFlag: ah, thanks. needed to know which clock scaling routines to link in. |
| 21:17:11 | kergoth | BZFlag: yep, thats what i'm doing. I grabbed 2.4.18-rmk6 .. then i started analyzing the patch to determine its implications before applying. tried to isolate COLLIE and IRIS specific aspects, and aspects which were for the oom_kill, and for the XIP stuff |
| 21:17:27 | kergoth | BZFlag: but perhaps i should apply first, then fix as you suggested |
| 21:31:56 | kergoth | hmm there's no APM for arm anymore? odd. wonder if CONFIG_PM is sufficient |
| 21:32:33 | MicroChip32 | ok what do i do after reset and ctrl-a for remote shell ? |
| 21:39:09 | MicroChip32 | argh, is there nobody here? |
| 21:40:50 | prpplague | MicroChip32: see the wiki for instructions |
| 21:41:16 | prpplague | MicroChip32: the tux has enought flash to place a relatively functionaly linux system on it |
| 21:42:07 | MicroChip32 | prp i cant find much decent docs on the wiki, prolly looking in the wrong place, but i got a bigger prob at the moment ... |
| 21:42:39 | MicroChip32 | i reset then ctrl a with windows terminal on the other end of null modem cable ... tux seems to be in a loop reporting stats |
| 21:47:51 | MicroChip32 | its repeatedly sending ... DECa[newline]119, shanmon v1.13-a (103 MHz)[newline]....sboot jumpstart vector: 0x40 |
| 22:07:09 | collord | are there any bugaboos specific to netlink stuff when using ulibc? |
| 22:11:52 | BZFlag | kergoth: yes, CONFIG_PM should suffice iirc |
| 22:12:30 | BZFlag | MicroChip32: that's the remote debug interface. |
| 22:12:50 | kergoth | BZFlag: cool, thanks |
| 22:13:00 | BZFlag | MicroChip32: hook up with InfernoRemote and type "b" to get back to normal boot. |
| 22:13:13 | MicroChip32 | BZFlag: yea but why did it keep repeating ? anyway, i finally pulled the plug and rebooted to inferno gui at the moment |
| 22:13:31 | MicroChip32 | what am i supposed to have on the pc side to get this started ? |
| 22:13:33 | BZFlag | MicroChip32: you need to use InfernoRemote, not a terminal app. |
| 22:13:42 | MicroChip32 | i have inferno emu, is that it ? |
| 22:13:43 | BZFlag | use InfernoRemote. |
| 22:13:47 | BZFlag | yes. |
| 22:14:22 | MicroChip32 | ok have it up at ; prompt, now i do the bind and rdp right ? |
| 22:14:34 | BZFlag | yep. |
| 22:14:50 | BZFlag | I assume you are trying FlashUnlock right? |
| 22:14:54 | MicroChip32 | ; bind -a '#t' /dev ; rdp -s9600 -r |
| 22:15:20 | MicroChip32 | Well, i seem to remember getting the flash unlocked a few months ago, when devel here was hot |
| 22:15:47 | MicroChip32 | so now i wanna get the sysem actually linuxed, ideally with a remote boot setup |
| 22:16:14 | MicroChip32 | i get differing opinions on how much of a linux system can be installed on the basic tux |
| 22:20:55 | BZFlag | MicroChip32: buildroot (v0.6) has TinyX matchbox and rxvt in flash. |
| 22:22:01 | MicroChip32 | erm, one thing at a time <G> just did inferno, bind as above, reset tux esc/ctrl-a, now blank screen on tux and <sending reset> on emu |
| 22:23:41 | MicroChip32 | brb, nature calls |
| 22:28:11 | MicroChip32 | *sigh* |
| 22:32:45 | MicroChip32 | hmmm how do i tell it which serial port its on, on the pc ? |
| 22:33:29 | MicroChip32 | ahhh, well switch the cable to the other port it works :) |
| 22:38:27 | MicroChip32 | hmm ok, all but some of the low-address blocks are unprotected, do i need to unprot those before blobing ? |
| 22:50:31 | jacques | hello |
| 22:51:07 | | andersee was last seen on #tuxscreen 18 hours, 32 minutes and 14 seconds ago, saying: hehe [Wed May 22 05:18:53 2002] |
| 22:51:07 | jacques | ibot: seen andersee |
| 22:51:20 | | tomw was last seen on #tuxscreen 21 hours, 57 minutes and 7 seconds ago, saying: is away: I'm busy [Wed May 22 01:54:13 2002] |
| 22:51:20 | jacques | ibot: seen tomw |
| 22:53:39 | jacques | what's the latest on mounting tux parts in case/s suitable for mobile (automobile) installations? (and power supplies) |
| 22:53:55 | | redbaron was last seen on #tuxscreen 62 days, 6 hours, 43 minutes and 56 seconds ago, saying: Tangent: Howdy [Thu Mar 21 16:09:59 2002] |
| 22:53:55 | jacques | ibot: seen redbaron |
| 23:14:08 | jacques | goes to look at the wiki. |
| 23:16:31 | MicroChip32 | are there different blobs for different purposes, or what, and where do i get the appropriate/latest blob ? |
| 23:17:49 | jacques | MicroChip32: right now there are two main blobs |
| 23:17:56 | sjm | MicroChip32: yes, that latest blob allows the kernel/filesystem to be programmed as one. Earlier blobs required the kernel and filesystem to be programmed individually. |
| 23:18:15 | jacques | MicroChip32: one we have been using for many months, and the other one is new |
| 23:18:56 | jacques | the new one understands jffs2 and can find the kernel on it, so no need for a separate kernel parition and we can have modular kernels thus saving flash |
| 23:19:00 | MicroChip32 | is the latest (kernel/fs) stable or beta ? |
| 23:19:46 | MicroChip32 | and what real benefits of the new one ? how much bigger than the old ? |
| 23:19:54 | jacques | i would definitely say beta |
| 23:20:09 | MicroChip32 | ok so unless i really needed it prolly wanna use the old then right ? |
| 23:20:28 | jacques | unfortunately, the latest cvs buildroot assumes you are using the new blob |
| 23:20:48 | jacques | and AFAIK there is no tag or branch for the previous method |
| 23:21:09 | MicroChip32 | that aint nice |
| 23:22:05 | MicroChip32 | how beta is the new one, its not gonna barf and turn my tux into a brick is it ? |