[00:01] <lool> http://joze100s.wordpress.com/category/samsung/ says it's an arm
[00:03] <amortvigil> how did you find that i spent the whole night to find that lool 
[09:59] <jerryfan> is there any way to emit fake acpi event by command line?
[10:11] <LTSPTNK> guys, is it possible to install Ubuntu 8.04 MID on eee pc?
[10:12] <LTSPTNK> I have EEE PC 701 and it wont boot on Ubuntu MID image?
[10:13] <LTSPTNK> I mean I burned the image to CD and using USB cd drive
[10:15] <ogra> it will likely only work on the atom models
[10:16] <ogra> and you should rather use dd and make a binary 1:1 copy of the image to a usb key an boot from that 
[10:17] <ogra> i doubt it will "just boot" from an iso you mak of it without modifying bootfiles etc
[10:36] <LTSPTNK> but isnt the 700MHz celeron part of McCaslin platform?
[10:36] <LTSPTNK> Or so I thought?
[10:37] <LTSPTNK> Ogra, how do I make that copy? 
[10:37] <persia> LTSPTNK: Nope.  McCaslin is A100 or A110
[10:37] <LTSPTNK> The Intel processors A100 and A110 are x86 architecture low-power microprocessors (code-named Stealey), with a Dothan core derived from the Intel Pentium M, built on a 90 nm process with 512KB L2 cache and 400MHz front side bus (FSB).
[10:37] <LTSPTNK> ^^wikipedia
[10:37] <persia> Note that some other chips can boot a McCaslin environment, but aren't properly McCaslin.  The C7-M cannot boot McCaslin.
[10:38] <LTSPTNK> and this Celeron is most definatly based on Dothan Core, so it should support all the same features
[10:38] <persia> Right.  McCaslin is Stealey + a matching chipset.
[10:38] <LTSPTNK> off course, the whole platform
[10:39] <LTSPTNK> anyway then use normal Ubuntu 8.04 normal image and install the fansy looking interface of the MID version?
[10:40] <persia> Not quite.  Some things are compiled differently for lpia, which makes the interface different.
[10:40] <LTSPTNK> becouse, we have been researching the usage of EEE PC's in school envinroment, but the Xandros, unfortunately, sucks.
[10:41] <LTSPTNK> Ubuntu would be quite good, but while not having good interface for 7" display, it will not be an option
[10:41] <persia> LTSPTNK: Try using the dd command mentioned earlier to create a USB key with the image, and boot off that.  It may work.
[10:41] <LTSPTNK> But ubuntu would have working samba, likewise and all other things
[10:42] <LTSPTNK> dd= and then, havent used linux more than 9 months, so last time i used dd command I just erased my whole hard drive, while I mentioned to erase USB key which had contained sercert things :D
[10:44] <persia> LTSPTNK: Hmm.  I don't have a better solution for you.  You may wish to wait until some other installer becomes available.
[10:45] <LTSPTNK> but do U know the options I should use?
[10:47] <persia> dd if=$(downloaded image file) of=$(device path for USB stick) bs=1024
[10:47] <persia> The easiest way to determine the path for your USB stick is to call dmesg | tail immediately after connecting it.
[10:47] <LTSPTNK> and path is /media/disk or something else?
[10:48] <persia> Nope.  /dev/sd$(something)
[10:48] <LTSPTNK> ohh u mean device path?
[10:48] <LTSPTNK> gparted tells it :)
[10:48] <LTSPTNK> /dev/sdc
[10:49] <LTSPTNK> this is something I love with Linux, U can really get help :)
[11:08] <ogra> persia, btw i think we urgently need a gui for that dd stuff ... i'f i'm not busy with classmate images on the weekend i'll attack that 
[11:09] <persia> ogra: Cool.  Thanks,.
[11:09] <ogra> (only needs three gui elements anyway)
[11:09] <persia> File chooser, File chooser, Status report?
[11:10] <ogra> file chooser for image, puldown menu with detected USB keys and a progress bar 
[11:10] <ogra> well, and to buttons "ok" "go"
[11:10] <ogra> *two
[11:10] <persia> How to differentiate between USB key and other storage?  sysfs tree?
[11:10] <ogra> err, "go"  "cancel" :)
[11:10] <ogra> hal 
[11:11] <ogra> just ask hal for all devices that are tagged removabe, then check if they are usb
[11:12] <persia> Probably want to display the volume name as well, for those with persistant USB connections to stuff.
[11:12] <ogra> volume name only
[11:12] <persia> How about auto-unmounting it as well, as nautilus will auto-mount
[11:12] <ogra> i dont want /dev/something exposed to users :)
[11:12] <persia> I don't like volume name only: I've a couple keys with the same volume name, but track which I connected last.
[11:12] <ogra> (probably in brackets behind the name, but not as default)
[11:13] <ogra> not sure you ever used my cmpc installer ... :) 
[11:13] <persia> That works: cater to both classes of user, with /dev-aware as second-class
[11:13] <ogra> but i would just take the code i use there
[11:13] <persia> Nope: I don't have a cmpc
[11:14] <ogra> it should roughly work on every celeron with intel graphics (roughly as in you will have probs with wlan etc because thats customized)
[11:14] <persia> Should the cmpc build work on the SR8, or is it too HW specific to even boot?
[11:14] <ogra> i tried it on the Q1 :) and it worked fine 
[11:14] <ogra> at the last sprint 
[11:14] <persia> I'll give it a try this weekend then.
[11:15] <ogra> well, its supposed to go away anyway at some point in favour of the actual UNR build ... but there is a lot code we cn surely reuse or modify for the intrepid pieces we need
[11:16] <LTSPTNK> atleast the image booted
[11:16] <persia> ogra: Where is it?  I don't see it on cdimages.u.c, and google isn't playing nice.
[11:16] <ogra> http://people.ubuntu.com/~ogra/classmate/images/hardy/
[11:16]  * persia should have guessed :)
[11:16] <ogra> its a bit outdated ... the one i'm working on will be ful lpia
[11:17] <persia> That's OK.  I'm more just curious about it, as some of it may be interesting, and you've added lots of hacks.
[11:17] <persia> Just put on USB, and boot?
[11:19] <LTSPTNK> seems to not work
[11:19] <LTSPTNK> it has been in same point for 5 minutes
[11:20] <LTSPTNK> #attached scsi generic sg0 type 0
[11:20] <LTSPTNK> and not writing hard disk
[11:22] <ogra> persia, xactly 
[11:24] <LTSPTNK> what could be problem with this thingie? the SSD hard disk most propably?
[11:25] <persia> LTSPTNK: Rather assumptions in the installer that you have exactly the right arrangement of hardware.
[11:26] <lool> asac: Around?
[11:26] <persia> You could mount the squashfs in loopback and hack it, but it won't install cleanly on your machine because of different device assignment.
[11:26] <LTSPTNK> and now one has customized this image for EEE PC?
[11:26] <LTSPTNK> ^^no one
[11:31] <persia> LTSPTNK: There've been a few Eee users in the channel, but I've not seen any specific reports about what customisation is required.
[11:32] <ogra> many of them used atom based devices afaik
[11:33] <LTSPTNK> yeah, problem is that here far in the north where Linux was born, everything arrives 6 months later and costs like hell
[11:33] <LTSPTNK> so that why I'm having 701 now :(
[11:40] <LTSPTNK> any EEE PC users here?
[11:44] <LTSPTNK> any advices what should i do with the Image Creator thingies?
[11:45] <asac> lool: how can i serve you?
[11:49] <lool> asac: I just wanted to tell you that I ported evolution-rss to xulrunner 1.9's libxul-embedding :)
[11:49] <asac> lool: hah
[11:50] <lool> asac: Following yesterday's theory, I applied it on evolution-rss and got it to build then to not crash
[11:50] <lool> asac: So thanks again :)
[11:51] <lool> asac: The last xulrunner 1.9 thing I'm more or less tracking is the mbf one
[11:51] <lool> asac: Do you think you could dig a tree with it?
[11:51] <lool> asac: I'd love to close this upstream and in hardy
[11:52] <asac> lool: whats the current state in hardy?
[11:52] <lool> (to stop having to use and test xulrunner 1.8 apps)
[11:52] <lool> asac: Current state is we are using an old mbf which is 1.8
[11:52] <asac> its manually patched in the package? or not ported at all
[11:52] <asac> hmm
[11:52] <lool> It's not ported at all
[11:52] <asac> didnt you upload something?
[11:52] <lool> I would prefer a new upstream release of mbf
[11:52] <lool> No, I tested it
[11:52] <asac> ok, so you just uploaded to PPA?
[11:52] <asac> ah
[11:52] <lool> No
[11:53] <lool> First, it was around UME release and we had other things in the pipe, and I thought upstream would respond quickly
[11:53] <lool> Second, the changes were quite intrusive and we didn't have a patch system or anything to track changes
[11:53] <lool> so doing it downstream would have required many cleanups, adding a patch system then adding the intrusive changes
[11:53] <asac> lool: ok. I'll look where those bits are and how much i need to reshape them ;)
[11:53] <lool> asac: Cool
[11:53] <asac> then push to alioth ;)
[11:53] <asac> hehe
[11:54] <lool> asac: I would say the top notch thing for upstream would a git tree derived from their master with the last bits of xulrunner 1.9 support as individual commits
[11:55] <lool> asac: If you like to look at evolution-rss, it's at svn+ssh://svn.debian.org/svn/pkg-evolution/unstable/evolution-rss
[11:55] <lool> asac: It might be crashing on exit, but I don't care too much about that
[11:55] <lool> asac: One thing which was different is that the profile path was setup first thing, and this crashes with xulrunner 1.9
[11:55] <lool> Moving it later fixed this crash
[11:56] <asac> lool: yes makes sense
[11:56] <asac> you cannot use any embedding symbols until GRE is booted
[11:56] <asac> as they all point to 0x0
[11:56] <asac> ;)=
[11:57] <asac> lool: why does it crash on exit?
[11:57] <asac> lool: if you use startup_push (not always required), you also need startup_pop on shutdown
[11:57] <lool> asac: I didn't check whether this was done properly
[11:57] <asac> ok
[11:57] <lool> asac: It might be an unrelated crash
[11:57] <asac> most likely not
[11:58] <lool> I'll tell you in a sec
[11:58] <lool> Ah it's not unrelated, sorry
[11:58] <lool> asac: Oh ok, makes sense for the not booted use of symbols
[11:58] <lool> asac: Concerning the crash on exit, I'll look at it later, hopefully this afternoon
[11:59] <lool> It was using startup_push() before my changes already
[11:59] <lool> I confirmed that disabling the RSS plugin prevents the crash on exit, but I don't know whether it's an historical bug in the rss plugin
[11:59] <lool> The code has tons and tons of warnings, some scary one
[11:59] <lool> s
[12:00] <lool> There's a gtk_moz_embed_pop_startup ();
[12:00] <lool> in gecko_shutdown()
[12:01] <lool> #ifdef HAVE_BUGGY_GECKO
[12:01] <lool>         if (2 == render)
[12:01] <lool>                 system("killall -SIGTERM evolution");
[12:01] <lool> #else
[12:01] <lool>         gecko_shutdown();
[12:01] <lool> #endif
[12:01] <lool>         //really find a better way to deal with this//
[12:01] <lool>         //I do not know how to shutdown gecko (gtk_moz_embed_pop_startup)
[12:01] <lool>         //crash in nsCOMPtr_base::assign_with_AddRef
[12:01] <lool> asac: See what I meant :)
[12:02] <lool> That's only set if test "x$GECKO" == "xfirefox" fortunately
[12:05] <asac> fortunately?
[12:42] <lool> asac: Well at least we're not in that case is what I meant
[12:43] <asac> ok
[12:44] <TuxOne> hi
[12:44] <TuxOne> just heard about the MID...can we embed this system in to smartphone?
[12:45] <persia> TuxOne: Maybe, if your smartphone is sufficiently powerful, and you have a dialer app.
[12:46] <TuxOne> hmm
[12:46] <persia> The target for the recent release was the 4-6" handheld segment, but much of the code may also be used in other applications.
[12:47] <TuxOne> Does it run as a VM? something similar to j2me?
[12:48] <persia> It runs on the device directly.  There are VM images available for preview on a desktop system.
[12:48] <TuxOne> could you please send me the link?
[12:49] <TuxOne> ah...i got it
[22:43] <RemsSs> bonjour a tous
[22:43] <RemsSs> je cherche des gadgets avec ubuntu dedans est ce que ca existe ?