**** BEGIN LOGGING AT Fri May 11 02:59:56 2007
May 11 03:06:26 <summatusmentis> willie: there is not an 'official' opie angstrom image
May 11 03:41:12 <summatusmentis> how do i change the structure of the 'icons' on the desktop in GPE
May 11 05:06:56 <willie> summatusmentis: yeah thats OK, what I need is a to know exactly what files I need to avoid turning the Zaurus into a brick :-)
May 11 07:46:44 <XorA> morning
May 11 09:54:22 <XorA> koen: I thought you turned on epoch support in Angstrom?
May 11 09:54:35 <koen> ?
May 11 09:54:42 <koen> it's in bitbake 1.8.2 and OE
May 11 09:54:52 <koen> you can't 'turn it on' in a distro
May 11 09:55:01 <XorA> koen: packages dont have epoch in the version
May 11 09:55:06 <XorA> koen: but build dirs do
May 11 09:56:05 <koen> have you checked the control file?
May 11 09:56:39 <XorA> Version: 1:0.02+cvs20070510-r0
May 11 09:56:39 <koen> http://www.angstrom-distribution.org/repo/?action=details&pnm=xserver-kdrive-fbdev has an epoch
May 11 09:56:52 <koen> right, that's an epoch
May 11 09:56:55 <XorA> ah right, I thought it was in package filename as well
May 11 09:56:58 <koen> :)
May 11 09:57:38 <XorA> that confuses my feed syncing :-(
May 11 09:57:45 <XorA> Ill have to rethink
May 11 10:04:48 <polyonymous> or resync? :)
May 11 10:05:14 <XorA> polyonymous: I based my syncing on the filename, not the Version in control file
May 11 10:05:22 <XorA> polyonymous: I might have to actually parse control file
May 11 10:05:40 <polyonymous> Quite understandable way of syncing.
May 11 10:16:44 <pH5> hm.. I suspended my Bv4 yesterday and now it doesn't wake up. the backlight is on, the lcd flickers strangely.
May 11 10:17:11 <pH5> I can ping it but not ssh into it. After about 30s the speakers did a 'pop' and the backlight turned off again.
May 11 10:17:21 <pH5> wrong channel anyway.
May 11 10:17:25 <pH5> good morning koen
May 11 10:17:56 <koen> hey pH5 
May 11 10:18:43 <koen> hrw: how much from poky do we need to copy before xorg 1.3.0 builds?
May 11 10:20:39 <hrw> koen: probably only 1.3.0.0
May 11 10:21:36 <hrw> I pushed some OE ones and same stuff which I earlier added into OE + xserver 1.3.0.0
May 11 12:30:52 <XorA> damn minimo and backtraces :-(
May 11 12:49:20 <XorA> mtn-0.35:  7,365/16,129 a while to go yet
May 11 13:31:46 * XorA has been lied to
May 11 13:32:02 <koen> you have?
May 11 13:32:07 <koen> kill the bastards!
May 11 13:32:14 * koen starts hiding
May 11 13:32:21 <XorA> the meaty hosting machine is actually a Celeron
May 11 13:32:54 <koen> heh
May 11 13:33:01 <koen> that's rather skinny
May 11 13:33:23 <XorA> ah well wolfson OE mirror will be back online tomorrow proably
May 11 13:33:36 <XorA> and should at least this time stay working :-)
May 11 13:39:34 * koen removes the stinking OABI image from his neo
May 11 13:41:02 <XorA> koen: I guess thats you out of the GPS game :-)
May 11 13:41:07 <koen> no
May 11 13:41:14 <koen> chroot to oabi on sd :)
May 11 13:41:33 * XorA wonders if you could munge binaries to fix ABI
May 11 13:41:38 <koen> I just can't stand all those *stupid* bugs in the openmoko stuff
May 11 13:41:55 <XorA> koen: Id like to see GPE Phone Edition on Neo
May 11 13:42:17 <koen> I fixed up libgemwidget last week
May 11 13:42:30 <koen> and uploaded a large portion of it to the feeds
May 11 13:42:41 * koen scratches head
May 11 13:42:49 <koen> maybe only the armv5 feed
May 11 13:43:05 <XorA> We could get a working smartphone quicker that way I think :-)
May 11 13:43:16 <koen> dunno
May 11 13:43:29 <koen> gpepe is missing a same gsm (de)muxer and lib
May 11 13:43:33 <koen> s/same/sane/
May 11 13:43:56 <koen> and kernelconcepts is still refusing to acknowledge that there is something else than gtk 2.6.10
May 11 13:43:58 <XorA> at least GPE apps open this week on 200Mhz machines
May 11 13:46:33 <koen> XorA: gpe-phone image + gsmd + openmokodial minus openmoko-theme
May 11 13:49:27 <pH5> hmm, I'd like that.
May 11 13:49:39 <pH5> once gsmd stops eating SMS messages 'cause it still doesn't understand +CMT
May 11 13:52:40 <koen> just for maintenance ease I'd like to have _only_ *one* gsm implementation in angstrom
May 11 13:56:37 <XorA> pH5: youre the phone genius, we expect it working on sunday :-D
May 11 13:57:18 <XorA> 9,555/16,129 getting closer
May 11 14:02:54 * koen builds qt3-x11 and qt4-x11
May 11 14:20:43 <XorA> koen: http://groups.google.com/group/linux.debian.ports.arm/browse_thread/thread/f8487a6cf911fec5/a44ef61ba32fe8b2#a44ef61ba32fe8b2
May 11 14:36:27 <koen> XorA: I saw that
May 11 14:36:36 <koen> XorA: but I don't see the point
May 11 14:37:08 <koen> we have to compile seperately for strongarm anyway, so why put in 3 extra isns on every function return?
May 11 14:37:17 <XorA> koen: make a SLOW feed for those who insist on super optimising by using EABI :-D
May 11 14:37:33 <XorA> koen: the gentoo fanboys of Zaurus land
May 11 14:38:32 <koen> if someone shows me a sa1100 with vfp I might reconsider :)
May 11 14:40:57 <XorA> its more use to debian so that can add one more tickbox
May 11 14:41:08 <XorA> well thats if they ever stop bickering
May 11 14:41:50 <koen> it the debian-arm 'developers' stop being utter idiots
May 11 14:42:16 <XorA> is there an ubuntu-arm yet?
May 11 14:42:34 <koen> or if arm pays people that know what a compiler is instead of hiring wookey's goonsquad
May 11 14:43:31 <koen> that put debian-arm about a year behind
May 11 14:45:12 <koen> I should have taken Lennert's job offer to do debian/EABI :)
May 11 14:58:56 <XorA> 10,790/16,129
May 11 14:59:15 <XorA> koen: :-D
May 11 15:26:07 <XorA> http://venturebeat.com/wp-content/uploads/2007/05/beforeafter1.jpg
May 11 15:26:18 <XorA> that is insane, the before example is so blurred it hurts my eyes
May 11 15:31:31 <hvontres|poodle> XorA: so what are they trying to sell?
May 11 15:32:16 <XorA> hvontres|poodle: software to make the text on the right which is apparently more readable
May 11 15:32:23 <XorA> hvontres|poodle: to me both sides hurt my eyes
May 11 15:32:28 <XorA> hvontres|poodle: its on /.
May 11 15:33:55 <hvontres|poodle> XorA: hehe...yeah, the right side is just blurry, but the left side looks like it was typset by an angry chimp..
May 11 15:34:22 <hvontres|poodle> XorA: or maybe they accidentaly used the "Ransom Note" style sheet :)
May 11 17:10:40 * Furre has managed to get $80 so far :x
May 11 17:25:11 <sts_> Hi koen.  I keep getting a flash write error with the 20070507 poodle image
May 11 17:25:51 <sts_> zImage-2.6.20-poodle-20070507183346.bin to be specific
May 11 17:27:51 <hvontres|poodle> sts_: did you verify the md5sum to make sure the file didn't get corrupted somewhere along the line?
May 11 17:28:16 <sts_> yep; I asked for the md5sums the other day, they checked out
May 11 17:28:19 <Furre> Err, are you people sure that "PriceJapan.com" is a good place to buy a zaurus from? it says its 18cm thick o.o
May 11 17:29:16 <hvontres|poodle> sts_: hmmm... and when are you getting the error?
May 11 17:29:56 <sts_> on flashing.  gives the kernel OK, does the erase, then at the end of the ROM write I get a flash error
May 11 17:31:53 <sts_> that may not be a zImage problem, though, but one with initrd?  kernel is the zImage, no?
May 11 17:32:28 <hvontres|poodle> sts_: yes, the zImage seems to be flashing ok, but the initrd isn't
May 11 17:33:04 <sts_> Was I supposed to do something besides downloading the one ending in .jffs2.bin and renaming to initrd.bin?
May 11 17:33:52 <hvontres|poodle> sts_: I think I see the problem. the jffs file is too big to fit :( What does ls -l initrd.bin tell you?
May 11 17:34:42 <sts_> not sure where I'd do that; let me see if the thing boots and I'll check
May 11 17:35:29 <hvontres|poodle> sts_: do you have a card reader you can put your CF card in ?
May 11 17:35:47 <sts_> yeah.  oooooh, cool boot screen.
May 11 17:36:35 <hvontres|poodle> sts_: hopefully you didn't need the last 2 megs :)
May 11 17:37:00 <sts_> 24,772,608 bytes according to Windows (ducks behind couch)
May 11 17:38:26 <sts_> boot seems to hang at 98% of crawlbar, no surprise
May 11 17:38:32 <hvontres|poodle> sts_: well, according to df -k on my poodle /dev/mtdblock2 (/) is only 22528 K
May 11 17:38:52 <hvontres|poodle> sts_: <fn>-left arrow to get to conole window
May 11 17:40:05 <sts_> ok.  mine reports 22528 as well.
May 11 17:40:20 <hvontres|poodle> sts_: and unfortunately 24192
May 11 17:40:31 <hvontres|poodle> sts_: and unfortunately 24192 K > 22528 K 
May 11 17:40:54 <sts_> sad but true, even here in Washington
May 11 17:41:15 <hvontres|poodle> sts_: State or City?
May 11 17:41:48 <sts_> District of Columbia (though I'm home right now outside Baltimore)
May 11 17:42:18 <hvontres|poodle> sts_: Try reflashing inside the Capitol, since normal math does not seem to apply there ;)
May 11 17:45:13 <hvontres|poodle> koen: Are we still using ROOT_FLASH_SIZE for checking angstrom images? it looks like the latest X11 image for poodle is ~2MB over the limit :(
May 11 17:47:24 <sts_> I'll try installing 20070422 and keep checking the site
May 11 17:47:43 <hvontres|poodle> sts_: do you have a spare SD card that you wouldn't mind formating to ext2?
May 11 17:49:09 <sts_> no problem, are there ext2 tools at my current poodle console?
May 11 17:49:56 <sts_> have to go get my son at school, will be back in a bit
May 11 17:50:07 <hvontres|poodle> sts: np
May 11 17:52:02 <hvontres|poodle> sts_: IIRC the ext2 tools should be there.
May 11 18:02:50 <koen> hvontres|poodle: it was never used
May 11 18:05:11 <hvontres|poodle> koen: ah. Tha makes sense. 
May 11 18:05:58 <hvontres|poodle> koen: should we maybe look at adding a check to the jffs image stuff to throw up a warning if the image is too big?
May 11 18:06:16 * hvontres|poodle puts that on his mental to-do..
May 11 18:07:08 <hvontres|poodle> koen: also, is http://www.angstrom-distribution.org/unstable/images/poodle/20070507/zImage-2.6.20-poodle-20070505215413.bin set up to boot from SD?
May 11 18:07:46 <koen> yes
May 11 18:08:16 <hvontres|poodle> koen: yes to which one?
May 11 18:08:59 <koen> sd
May 11 18:09:08 <koen> and the error :)
May 11 18:09:48 <hvontres|poodle> koen: ok. I'll try to take a look at that this weekend when I am done shoveling dirt :)
May 11 18:10:45 <Furre> ;/, tried selling my PSP to get a better Zaurus, but the one that wanted to pay the most wanted to pay $60 for it :/, must find another way ._.
May 11 18:36:07 <sts_> hvontres: ok I'm back
May 11 18:38:01 <sts_> rebooted with the 0507 image; waiting to dump to console...
May 11 18:39:07 <sts_> ... and there I am.
May 11 18:40:14 <sts_> test
May 11 18:40:42 <sts_> sd card is already formatted ext2 - do i need to blank it out?
May 11 18:43:07 <hvontres|poodle> sts_: what do you have on there right now?
May 11 18:43:47 <sts_> I know it's not empty.  Just ran mke2fs on it.
May 11 18:44:00 <sts_> waiting for mke2fs to finish
May 11 18:44:19 <sts_> mke2fs done
May 11 18:44:34 <hvontres|poodle> sts_: Ok. So the plan here is the follownig: 
May 11 18:45:08 <hvontres|poodle> 1) untar http://www.angstrom-distribution.org/unstable/images/poodle/20070507/Angstrom-x11-image-test-20070507-poodle.rootfs.tar.gz to the SD card
May 11 18:45:46 <hvontres|poodle> 2) put http://www.angstrom-distribution.org/unstable/images/poodle/20070507/zImage-2.6.20-poodle-20070505215413.bin on your CF card and get rid of initrd.bin
May 11 18:45:54 <hvontres|poodle> 3) flash only the kernel
May 11 18:46:09 <hvontres|poodle> 4) put the SD card in and reboot. 
May 11 18:46:42 <hvontres|poodle> The new kernel is compiled to boot directly from the SD card, bypassing your internal flash completely :)
May 11 18:47:34 <hvontres|poodle> sts_: based on my previous testing of X11 on poodle, you might want to set up a ~64MB swap file or a swap partition on the SD card as well
May 11 18:48:31 <sts_> I assume I still rename the zImage...413.bin to zImage.bin, yes?
May 11 18:50:18 <hvontres|poodle> sts_: correct
May 11 18:52:46 <sts_> ok, have to think about the best way to untar that .tar.gz to the SD card.
May 11 18:53:03 <sts_> guess I can put it on the CF temporarily and untar from there?
May 11 18:54:43 <hvontres|poodle> sts_: that should work :)
May 11 18:54:58 <hvontres|poodle> sts_: so the poodle is you only linux system right now?
May 11 18:55:31 <sts_> no, I run opensuse on my notebook and feisty on a desktop
May 11 18:55:48 <sts_> guess it doesn't show
May 11 18:56:40 <hvontres|poodle> sts_: just making sure you won't be too hosed if this messes up :)
May 11 18:57:10 <hvontres|poodle> sts_: a card reader would probably be a good idea too :)
May 11 18:57:36 <sts_> yeah, the multicard reader on my hp is the only thing opensuse doesn't support
May 11 18:58:12 <hvontres|poodle> sts_: heh...I just have some cheap USB one that works great :)
May 11 18:58:30 <sts_> I've never been able to successfully move files to a CF and flash from linux, either, it's the only reason I'm using windows right this second.
May 11 19:02:55 <sts_> copying the .tar.gz
May 11 19:07:56 <sts_> untarring
May 11 19:09:13 <sts_> now, will I do the regular steps to "flash only the kernel", since there's no initrd on the CF card, or do I do something special?
May 11 19:12:19 <koen> it will do
May 11 19:23:20 <sts_> got the 'no space left' error again :(
May 11 19:27:33 <sts_> what happened to the initrd.bin it already had put in flash?
May 11 19:31:20 <hvontres|poodle> sts_: it's still there
May 11 19:31:55 <hvontres|poodle> sts_: you could use the "Format" button to clear it, IIRC
May 11 19:33:42 <hvontres|poodle> sts_: or even better, you could flash a Console-image like http://www.angstrom-distribution.org/unstable/images/poodle/20070505/Angstrom-console-image-test-20070505-poodle.rootfs.jffs2.bin
May 11 19:34:44 <summatusmentis> will someone help me get my networking functioning again?
May 11 19:35:13 <summatusmentis> I had it working last night, on my symbol spectrum24 wifi card, but today, for some reason, it's not working
May 11 19:35:52 <summatusmentis> the light on the card is blinking(just the steady, not connected to any wap blink), and the module 'orinoco' is loaded, but it won't connect
May 11 19:36:21 <Laibsch> koen: CAn you tell me once more how to compile the kernel to boot from SD?
May 11 19:37:08 <hvontres|poodle> sts_: btw, when you get things working again, could you try to verify if the screen gets corrupted after a suspend ?
May 11 19:38:29 <koen> Laibsch: http://rafb.net/p/7YeaH487.html
May 11 19:38:42 <koen> Laibsch: and set the sd module to <Y> instead of <M>
May 11 19:38:50 <koen> (and ext2)
May 11 19:40:29 <Laibsch> thanks
May 11 19:46:52 <memeruiz> hvontres|poodle, I can verify the resumen problem. I am having the problem of the screen corrupted during resuming in the poodle. This problem is not happening with kernel 2.6.17.
May 11 19:48:10 <Laibsch> koen: Thus the machine will always boot from SD or just when a card is inserted?
May 11 19:56:01 <sts_> hvontres|poodle, I wonder if there's any way to get updater (which I guess handles this) to erase the RO file system without then flashing with initrd?
May 11 20:02:53 <summatusmentis> where do I set the hierarchy for desktop icons?
May 11 20:13:45 <koen> Laibsch: boot from sd or kernel panic
May 11 20:17:47 <hvontres|poodle> memeruiz: thanks. Do you have a pxa250 or pxa 255?
May 11 20:20:51 <memeruiz> hvontres|poodle, pxa250
May 11 20:30:29 <hvontres|poodle> memeruiz: Thanks.
May 11 20:33:44 <hvontres|poodle> sts_: do you know if your poodle has a pxa250 or a pxa255?
May 11 20:34:19 <hvontres|poodle> sts_: the only way I could think of would be to have an empty initrd.bin file...
May 11 20:43:49 <sts_> I have a 250
May 11 20:44:26 <sts_> I tried the console-only initrd you suggested, but now it doesn't seem to be doing anything with the boot image on the card
May 11 20:44:42 <sts_> sorry, the files I untarred to the card
May 11 20:45:07 <sts_> It boots console-only just fine, though (although the boot screen is landscape)
May 11 20:46:06 <hvontres|poodle> sts_: did you try flashing the other zImage?
May 11 20:49:14 <sts_> sigh.  looks like I used the 20070507...  Ugh, let me try again
May 11 20:50:44 <hvontres|poodle> sts_: well, at least that works :)
May 11 20:57:47 <sts_> OK.  Having flashed with the updater, zImage and initrd from 20070505 -- but the rootfs from 20070507 untarred on the SD card -- I get a kernel panic.
May 11 20:58:34 <hvontres|poodle> sts: what does the message say?
May 11 20:58:41 <sts_> hang on.
May 11 20:59:10 <hvontres|poodle> sts: hmmm, what command did you use to create the fs on the card?
May 11 20:59:43 <sts_> VFS:  Cannot open root device "mmcblk0p1" or unknown-block(0,0)
May 11 21:00:02 <sts_> Please append a correct "root=" boot option
May 11 21:00:35 <sts_> Kernel panic - not syncing:  VFS:  Unable to mount root fs on unknown-block(0,0)
May 11 21:00:46 <hvontres|poodle> sts: did you create the fs in /dev/mmcblk0 or /dev/mmcblk0p1 ?
May 11 21:01:41 <sts_> I just did a mke2fs on it and untarred.  I don't recall having partitioned it.
May 11 21:02:34 <hvontres|poodle> sts_: ah, theres your problem (sounding like Adam from mythbusters)...the kernel asumes the rootfs in /dev/mmcblk0p1
May 11 21:03:02 <hvontres|poodle> sts_: good thing the cosole image still works :)
May 11 21:05:24 <sts_> ok, so what's my fdisk call to create that partition (1GB sd card)
May 11 21:09:22 <hvontres|poodle> sts_: fdisk /dev/mmcblk0 , then create a primary partintion, type 83. I woould also reccomend a ~64MB partition for swap space as well
May 11 21:38:59 <sts_> Sorry for the delay, was having trouble with that kernel panic, had to reflash to 20070507 despite the lack of space.
May 11 21:39:13 <sts_> fdisk is destructive, no?
May 11 21:40:45 <hvontres|poodle> sts_: yes. and after fdisk, run mke2fs /dev/mmcblk0p1 and mkswap /dev/mmcblk0p2 (if you created a swap partition)
May 11 21:46:23 <sts_> OK.  Funny thing.  mount shows /dev/mmcblk0p1 mounted as /media/card.  Wonder why we couldn't find the rootfs there?
May 11 21:48:22 <hvontres|poodle> sts_: hmmm, so /media/card is where you untarred stuff to, right?
May 11 21:49:09 <sts_> yep.  I moved the .tar.gz file there, untarred locally, then deleted the .tar.gz file
May 11 21:49:17 <hvontres|poodle> sts_: in fdisk, print out the partition table. I wonder if the type for /dev/mmcblk0p1 is set correctly
May 11 21:49:33 <sts_> ok, hang on
May 11 21:49:46 <hvontres|poodle> sts_: so, unmount /media/card/ and run fdisk /dev/mmcblk0 and see what the partition table is set to
May 11 21:50:23 <sts_> ugh.  device busy
May 11 21:50:36 <hvontres|poodle> sts_: cd / :)
May 11 21:51:18 <sts_> I have a case of the stupids today, I swear
May 11 21:53:44 <sts_> Disk /dev/mmcblk0p1:  1030 MB, 10301504 bytes
May 11 21:54:07 <sts_> 4 heads, 16 sectors/track, 31436 cylinders
May 11 21:54:16 <sts_> The "Device" table is empty
May 11 21:57:38 <sts_> Units = cylinders of 64 * 512 = 32768 bytes
May 11 21:58:53 <sts_> Could be I never made it bootable!
May 11 22:02:39 <hvontres|poodle> sts_: try fdisk /dev/mmcblk0
May 11 22:05:03 <sts_> disk /dev/mmcblk0: 1030MB, 1030225930 bytes
May 11 22:05:30 <sts_> 4 heads, 3 sectors/track, 167680 cylinders
May 11 22:05:56 <sts_> Units = cylinders of 12* 512 = 6144 bytes
May 11 22:06:53 <sts_> Device /dev/mmcblk01 start 21 end 167680 blocks 1005958+ Id System FAT16
May 11 22:06:56 <sts_> WTF?
May 11 22:07:49 <hvontres|poodle> sts_: change the type to Linux (83) using t 
May 11 22:08:14 <hvontres|poodle> sts_: and that should be non-destructive :)
May 11 22:09:08 <sts_> now write and exit?
May 11 22:09:15 <hvontres|poodle> sts_: yup
May 11 22:10:02 <sts_> failed with error 16, says it'll use the new table on the next reboot.
May 11 22:11:56 <sts_> so, reboot?
May 11 22:12:11 <sts_> did I need to make it bootable?
May 11 22:12:15 <hvontres|poodle> sts_: well, you need to flash the kernel back to the root on SD one.
May 11 22:12:18 <hvontres|poodle> sts_: nope
May 11 22:17:35 <sts_> ok.  so, that's zImage...20070505215413.bin on the CF as zImage.bin, the corresponding updater.sh, and no initrd.bin
May 11 22:18:58 <hvontres|poodle> sts_: correct.
May 11 22:21:51 <sts_> here goes nothin'
May 11 22:22:26 <XorA|gone> koen: wolfson mirror should be functioning again
May 11 22:23:18 <sts_> ok, I got no messages from the updater program.  no kernel progress, no RO erase, just "please reset"
May 11 22:25:04 <sts_> I recopied and will try again
May 11 22:33:53 <sts_> OK, that booted all the way in to the 20050507 image.  woo-hoo!  shows only 1MB of system memory free, though.  still, looks and runs great
May 11 22:35:15 <hvontres|poodle> sts_:you will need a swapfile to do anything usefull :)
May 11 22:40:45 <sts_> yeah.  reset the machine as it wasn't picking up my wifi card, now I've got another kernel panic
May 11 22:40:57 <sts_> rebooted, I should say
May 11 22:41:24 <hvontres|poodle> hmm.... that seems strange
May 11 22:43:22 <hvontres|poodle> sts_: one thing you could do is to flash the console image and the newer z image, then install kexec tools, put the root-on- sd kernel on the sd card and use kexec -l and kexec -e to boot from the SD.
May 11 22:43:42 <hvontres|poodle> sts_: you might need to run fsck on your SD card as well
May 11 22:44:04 <sts_> reflashed from the CF I just used, and it seems to be booting OK
May 11 22:44:34 * CoreDump|home waves
May 11 22:44:42 <hvontres|poodle> CoreDump|home: hello way over there :)
May 11 22:44:48 <CoreDump|home> =)
May 11 22:50:49 * CoreDump|home start
May 11 22:51:00 <CoreDump|home> s a build of angstrom-x11-image
May 11 22:51:25 <CoreDump|home> shouldn't the angstrom*image.bb's be in images/, not in angstrom/ ?
May 11 22:51:39 <hvontres|poodle> CoreDump|home: koen'ism :)
May 11 22:52:23 <CoreDump|home> I thought he would be the first to standardise the image.bb locations
May 11 22:52:34 * CoreDump|home pokes koen 
May 11 22:52:53 <hvontres|poodle> CoreDump|home: actually, I think it had to do with bb not being able to handle bb's in images/angsrtom
May 11 22:53:46 <CoreDump|home> of course, but there is no need for images/angstrom in the first place
May 11 22:53:48 <hvontres|poodle> ok, time to go home. have a good weekend everybody
May 11 22:53:55 <CoreDump|home> have fun hvontres|poodle 
May 11 22:54:07 * hvontres|poodle is going home to shovel some dirt :)
May 11 22:56:57 <sts_> hey, will I have kernel problems if I try to flash back to the current oz/gpe?
May 11 23:11:54 <summatusmentis> CoreDump|home: fyi, I tried an angstrom-x11-image for my terrier, and it borked the NAND
May 11 23:12:11 <summatusmentis> I'm using one of the pre-built images provided by Angstrom
May 11 23:12:20 <summatusmentis> but you've got more experience w/ imaging than me
May 11 23:12:31 <CoreDump|home> I'll see
May 11 23:12:59 <CoreDump|home> I intend to flash a barebone image into the NAND and install the x11 image onto HDD
May 11 23:13:19 <summatusmentis> I seem to be having keymap issues when I ssh into my Z, is there something I can do about it?
May 11 23:13:44 <summatusmentis> I don't know what happened, nor why it did that, but I couldn't get the Z to boot, I had to restore the NAND
May 11 23:15:07 * CoreDump|home dunnos
May 11 23:17:30 <summatusmentis> :-D
May 11 23:18:07 <summatusmentis> or maybe it's just vim that's fucked up, but in insert mode, I cant use the arrow keys to travel accross letters, it borks hardcore
May 11 23:18:22 <polyonymous> summatusmentis, echo $TERM ?
May 11 23:18:45 <summatusmentis> polyonymous: vt100
May 11 23:18:56 <polyonymous> polyonymous, are you in rxvt?
May 11 23:19:13 <polyonymous> export TERM=rxvt maybe?
May 11 23:19:54 <summatusmentis> s/polyonymous/summatusmentis/ :-D I'm in ssh right now
May 11 23:20:00 <polyonymous> :))))))))
May 11 23:20:11 <polyonymous> I'm talking to myself - must be tired.
May 11 23:20:12 <summatusmentis> the keymap works fine on the Z, it's in ssh that I'm having issues, using my laptop keyboard
May 11 23:20:21 <summatusmentis> lol, at least you're not answering yourself
May 11 23:20:26 <polyonymous> in ssh from what terminal?
May 11 23:20:37 <polyonymous> summatusmentis, just wait a bit and I will :)
May 11 23:20:41 <summatusmentis> konsole(on the laptop)
May 11 23:20:54 <polyonymous> what is your $TERM in konsole?
May 11 23:21:05 <summatusmentis> xterm
May 11 23:21:11 <polyonymous> export TERM=xterm then.
May 11 23:21:27 <polyonymous> Also can you tell me what is `grep TERM /etc/profile` on Z?
May 11 23:21:29 <summatusmentis> will that screw w/ the keymap on the Z?
May 11 23:21:56 <polyonymous> it won't affect nothing but current shell and its children.
May 11 23:22:09 <summatusmentis> TERM="vt100" from /etc/profile
May 11 23:22:13 <polyonymous> aha
May 11 23:22:20 <summatusmentis> polyonymous: ah, so I'd need to do that everytime I ssh in?
May 11 23:22:20 <polyonymous> root@pangolin:~# grep TERM /etc/profile
May 11 23:22:21 <polyonymous> test -z "$TERM" && TERM="vt100" # Basic terminal capab. For screen etc.
May 11 23:22:44 <polyonymous> :) you should probably rebake base-files, I've committed the change yesterday or so.
May 11 23:22:59 <polyonymous> not if you upgrade base-files :)
May 11 23:23:11 <summatusmentis> does base-files have dependencies? or is it in the feeds yet?
May 11 23:23:15 <polyonymous> or if you edit your /etc/profile manually.
May 11 23:23:29 <polyonymous> ah.. I thought you're building yourself.
May 11 23:23:43 <polyonymous> Well, I don't know about the feeds. You can safely edit profile yourself, actually :)
May 11 23:24:31 <polyonymous> And base-files do not have runtime dependencies, I bet they'd pull half-a-tree for build :)
May 11 23:24:48 <summatusmentis> heh, no, I tried, and it killed my NAND, so I'm using the 'official' build
May 11 23:25:11 <polyonymous> what was the feeds browser again?
May 11 23:25:13 <summatusmentis> polyonymous: I'm not against re-baking it, I just don't want to have to scp a bunch of other .ipks
May 11 23:25:38 <polyonymous> scp?
May 11 23:25:46 <summatusmentis> www.angstrom-distribution.org/repo
May 11 23:25:55 <polyonymous> you don't have apache on your build machine?
May 11 23:25:59 <summatusmentis> yeah, to move the ipks built w/ OE to my Z, for installation
May 11 23:26:01 <summatusmentis> no
May 11 23:26:08 <polyonymous> ah
May 11 23:26:10 <polyonymous> ok.
May 11 23:26:20 <summatusmentis> you mean I can set up a feed on my host machine?
May 11 23:26:48 <polyonymous> and r65 is in the feed for fic-gta01 :)
May 11 23:27:11 <polyonymous> (r65 is base-files with changed TERM-line)
May 11 23:27:22 <polyonymous> Yes, that's what I'm doing for my feed
May 11 23:28:04 <polyonymous> but well, just edit your profile - that's the easiest way
May 11 23:28:08 <summatusmentis> fic-gta01 doesn't do it for my terrier, I'd be interested in instructions for setting up a feed
May 11 23:28:10 <summatusmentis> I'm doing that now
May 11 23:28:31 <polyonymous> that's the only difference between r64 and r65 :)
May 11 23:28:57 <polyonymous> Hmm... well, you just point apache to tmp/deploy/*/ipk/ (or whatever it is)
May 11 23:29:11 <polyonymous> and point your /etc/ipkg* to this location.
May 11 23:29:28 <polyonymous> and bitbake package-index to get your index.
May 11 23:29:34 <summatusmentis> is there a way to setup a specific feed? I don't want to built everything
May 11 23:30:21 <polyonymous> summatusmentis, you mean, you want half of the packages from official and some in yours?
May 11 23:30:40 <polyonymous> I don't know if it's a good idea, but I wouldn't do it.
May 11 23:30:54 <summatusmentis> yeah, just specific ones from mine, I'd like to use mostly the official feed
May 11 23:30:55 <polyonymous> but technically you can add your feed to official
May 11 23:31:19 <polyonymous> I mean have both your feed and official in configuration
May 11 23:31:20 <summatusmentis> my host is a laptop, and it's not overly powerful, and running gentoo, and beryl, so it's slow
May 11 23:31:39 <summatusmentis> is ipkg smart enough to choose the newest version?
May 11 23:32:54 <polyonymous> I think yes.
May 11 23:33:46 <polyonymous> Well, I'm outta here.
May 11 23:33:53 <summatusmentis> ok, thanks
May 11 23:34:03 <polyonymous> Goodnight, polyonymous - thank you, polyonymous ! 
May 11 23:34:13 <summatusmentis> :-P
**** ENDING LOGGING AT Sat May 12 02:59:56 2007