[07:18] <persia> amitk, http://netbook-remix.archive.canonical.com/updates/pool/public/l/linux-fsl-imx51/ has a couple different trees for imx51 stuff.  I think "araneo" is the PC-Z1 and "sendai" the PC-T1, but I'm not 100% sure.
[08:24] <hrw> morning
[10:11] <alf_> does anyone here have any experience setting up the TI SDP 4430 (development board)?
[10:21] <sebjan_> alf_: you may try on #linux-omap channel as well which may have more SDP4430 users
[10:22] <alf_> sebjan_: thanks
[10:55] <hrw> someone remember where I find panda kernel package?
[11:03] <sebjan_> hrw: it's linux-ti-omap4 source package. Is this what you look for?
[11:04] <hrw> was looking for binaries rather but found them already
[11:05] <hrw> ubuntu/arm concentrates on 'install on sd' way when I have different needs now
[11:05] <hrw> 512MB sd as /boot + 10GB partition on usb harddrive as / + 300GB /home on same hdd
[11:11] <sebjan_> hrw: right now, easiest may be to first install on SD, and then move the ext3 partition to your USB storage (while keeping the bootloaders and kernel on the SD card).
[11:39] <hrw> ~curse cdimages.ubuntu.com mirrors for lack of armel
[11:49] <cwillu> you... you don't make your own images?
[11:49] <cwillu> for _shame_
[11:50] <hrw> cwillu: I would rather prefer to grab uimage+uinitrd and boot into installer
[11:51] <hrw> similar to x86(-64) and debian/arm
[11:51] <hrw> but instead I fetched 512MB image which unpacks to 2GB image which dds to 4GB card and will be copied to 10GB partition after boot
[11:52] <cwillu> btrfs root, eh?
[11:52] <hrw> no, ext4
[11:53] <cwillu> ext4 snapshotted into btrfs?
[11:54] <hrw> no, no no
[11:54] <hrw> no btrfs for me until it will get 3 kernel releases without experimental sign
[11:58] <cwillu> suit yourself
[11:59] <cwillu> I prefer my filesystem developers to be overly cautious with that tag than under cautious, like some ext related filesystems I know :p
[11:59] <cwillu> er, unlike
[12:02] <hrw> ok, pandaboard booted
[12:48]  * hrw upgrades pandaboard to natty
[12:53] <hrw> btw - why only 665MB ram on pandaboard?
[13:17] <hrw> o... people arrive
[13:29] <persia> hrw, I don't remember the details, but I think there were prior conversations about some boot parameter that helped decide how much memory to allocate for dedicated buffers and how much for system RAM.  Check the documentation carefully.
[13:30] <berco> persia: do you know how the 3PA works? I wonder if we can upload natty source package and test how it builds. Seems our 3PA are set to Maverick only...
[13:31] <persia> berco, I don't know much about them.  I think that you can upload to any release, and it will do the right thing (just use changelog).  You can probably get a more authoritative answer in #launchpad.
[13:31] <berco> persia: ok. I'll give it a try first and see how it goes.
[13:33] <GrueMaster> persia: I thought there was a checkbox or something in the private ppa (3pa) to select build distro and arch?
[13:35] <persia> GrueMaster, Could be.  I'm unsure.  I know that one has to set the target in the changelog for an upload, but don't know if one has to pre-enable first.
[13:35] <GrueMaster> ah.
[13:36] <berco> GrueMaster: that might a be at the admin level... I browsed all the links on launchpad and didn't see such option I could set. However the sources.list only displays maverick in the tech details link
[13:36] <hrw> persia: will check
[13:37] <GrueMaster> ok.  I personally haven't done anything with ppa building, but I thought I had seen something like that.
[13:37] <persia> berco, the "technical details" link is likely to be based on either stock text, or what is there today, rather than being a good guide for what can be there.
[13:38] <berco> :)
[14:05] <marvin24> why the hell does the UDF keynote from Mark contains copyrighted material from MontyPython?
[14:05] <marvin24> http://www.youtube.com/watch?v=YUAzicy_01o
[14:06] <armin76> nice :D
[14:07] <marvin24> hey armin76! got a log for me?
[14:13] <marvin24> (not available at least in germany)
[14:16]  * persia didn't think copyright blocked use of small excerpts in other contexts, but isn't qualified to have an actual opinion (but encourages others to either be qualified or seek counsel)
[14:21] <XorA> hmm, the dead distro sketch :-D
[14:24] <marvin24> on the other hand, the intro sounds like a song form a "little big planet", but maybe I'm also not qualified
[14:41] <hrw> btw - is there any work on getting normal ubuntu installer working on armel targets?
[14:45] <hrw> hi prpplague
[14:45] <persia> hrw, Last time I played with it, it worked fine.  Are you having issues?
[14:45] <prpplague> hrw: hey
[14:47] <hrw> persia: I got a feeling that the only way to install ubuntu on omap3/4 is to use preinstalled images or rootstock
[14:48] <hrw> persia: installing by booting uimage+uinitrd would be lovely
[14:48] <GrueMaster> hrw: That is currently correct.  I haven't tested the d-i installer on omap4 yet.
[14:48] <persia> hrw, That's because some folk are convinced that omap3/4 can only boot from the SD card, and haven't read the docs that explain how to boot from USB.
[14:49] <persia> Since the installer has issues when trying to install to the media from which the installer runs, unless using the HD installer target, and folk felt that using the HD installer target would be slow and annoying because of file copying, they invented preinstalls.
[14:49] <hrw> persia: I am fine with having /boot on sd
[14:50] <persia> That won't work.
[14:50] <hrw> why?
[14:51] <hrw> uboot reads kernel+initrd from sd and boots to rootfs on usb-hdd
[14:52] <persia> Right, but it won't work with the way the installer works, because it wants to format /boot and *install* a kernel to it.
[14:52] <hrw> should work when booted kernel+initrd from sd
[14:52] <persia> So, if you happen to have enough internal flash, and want to boot from that, it works fine.  If you set up a system manually, it works just fine.  If you set up an HD-style install from SD, it works just fine.
[14:53] <persia> It just doesn't happen to have any way to make the SD /boot
[14:53] <hrw> as there should be nothing needed on sd during boot
[14:53] <GrueMaster> The problem is that the boot media needs to be vfat.
[14:54] <GrueMaster> And it is a broken vfat implementation at that.
[14:54] <hrw> which can be generated anyway
[14:54] <GrueMaster> (at least that is where MLO and u-boot need to be).
[14:55] <GrueMaster> It can be easily generated, and even setup to mount as /boot, but I believe it is against security policies.
[14:56] <GrueMaster> I'd have to ask our security guru.
[14:57] <GrueMaster> I do know that updating isn't as easy as just copying new files over, due to the vfat bug issue in silicon.
[14:57] <GrueMaster> The partition needs to be wiped and rewritten when updating some of the files.
[14:59] <hrw> ok, so something to try later
[15:00] <hrw> will have to dig my straight serial cable too
[15:00] <GrueMaster> I believe we have plans for getting the debian installer to fully support omap4 this cycle, which will make it easier to do alternative installations (netboot installs, etc).
[15:01] <hrw> good
[15:07] <hrw> hi robclark
[15:07] <robclark> hi hrw
[15:26] <hrw> GrueMaster: where I can find files needed for installation on pandaboard?
[15:26] <GrueMaster> What do you mean?  ppa files?
[15:26] <hrw> sorry
[15:27] <hrw> I meant: where to find (or how to generate) installer kernel/initrd
[15:28] <GrueMaster> Not sure.  what are you trying to do?
[15:29] <hrw> play with other (then preinstall sd) methods  of installing ubuntu on pandaboard
[15:29] <GrueMaster> Ah.
[15:30] <GrueMaster> That I don't know.  I think that they need to be generated by the d-i build process.  Not my area of expertise.
[15:30] <hrw> ok
[15:31] <GrueMaster> ogra, rsavetti, and ncommander would know more, but I think they are in transit to Boston for Linux Plumbers Conference.
[15:31] <hrw> ok
[15:32] <persia> hrw, http://ports.ubuntu.com/ubuntu-ports/dists/maverick/main/installer-armel/current/images/omap/netboot/omap/ has some omap3 images.
[15:32] <persia> Getting omap4 images probably means fiddling with the image build tools.
[15:33] <GrueMaster> persia: afaik, d-i doesn't currently support omap4.
[15:33] <GrueMaster> Which is needed.
[15:33] <persia> GrueMaster, which part?  Are there bugs?  I suspect that at least large chunks of d-i *do* support omap4, or oem-config wouldn't work (as it uses d-i as a backend)
[15:33] <hrw> anyway - it booted from sd to my harddisk
[15:34] <GrueMaster> oem-install doesn't do any hw-config.  It only sets up locale, keyboard, timezone, and user.
[15:35] <GrueMaster> (i.e. no installation steps)
[15:35] <GrueMaster> hw installation, that is.
[15:36] <persia> GrueMaster, Lots of stuff oem-config does aren't expressed in the UI, but yeah, it's a subset.
[15:37] <GrueMaster> Well, the parts that we need for installing on new hw aren't supported yet.  That is the key.
[15:47] <lag> rsalveti: Are you around?
[15:47] <lag> Does anyone have a known good MLO and u-boot.bin for the 6 layer?
[15:51] <GrueMaster> I think the 6 layer was abandoned.
[15:52] <GrueMaster> But you might be able to pull an earlier version from the archive.
[15:58] <lag> But I only have 6 layer and I need to test something
[15:58] <persia> You probably have to dig up old stuff out of launchpad and hack an image.
[16:01] <GrueMaster> lag, if you can pull a package from the archive that is from between Beta and RC, it should work.  Otherwise, pull the RC1 image and run dist-upgrade on it.
[16:02] <GrueMaster> Can't guarantee kernel support though (you know how those kernel guys are).  :P
[16:02] <lag> I'll do that - cheers
[16:03] <GrueMaster> What do you need to test?
[16:05] <lag> Linaro
[16:05] <GrueMaster> Ewww.  I'm getting page allocation failures in the most recent kernel.
[16:06] <lag> I'm unsure whether they have the correct bootloaders
[16:06] <GrueMaster> They should.  I believe that is what we have been using since pre-RC.
[16:06] <GrueMaster> I could be wrong, though.
[16:07] <GrueMaster> afair, the changes dropping 6L support were done during the TI-sprint.
[16:10] <lag> GrueMaster: Where are the histories?
[16:11] <lag> I can only fine the latest builds
[16:11] <sebjan_> lag: I can point you to the MLO commit that led to stop supporting 6-layers if it can help.
[16:13] <GrueMaster> lag: I don't know.  I don't see them on ports, which is strange.  I have a copy on my mirror though.
[16:15] <GrueMaster> I don't even really know which we are using, but I would assume it is pool/main/x/x-loader-omap4.
[16:16] <persia> There's no history in the archives.  Image history is limited to a day or two for selected flavours.  LP has richer history.
[16:16] <GrueMaster> Ah.
[16:16]  * GrueMaster needs to do some house-cleaning of private mirror.
[18:54] <hrw|gone> someone remembers how to get whole 1GB ram on panda?
[18:55] <armin76> use an updated u-boot/x-loader?
[18:56] <hrw|gone> armin76: I thought that maverick release had proper ones
[18:56] <armin76> dunno, blame ogra :P
[18:57] <hrw|gone> will, when he will be back
[18:59] <hrw|gone> btw: I am going thought kde components now as they did not built on arm
[18:59] <hrw|gone> how to request rebuild attempt for armel?
[19:49] <persia> hrw|gone, I'd suggest talking with the folk in #kubuntu-devel: a fair number of them can press the button, and they are also tracking KDE-FTBFS-on-armel issues quite closely
[20:11] <hrw|gone> ok
[20:12] <hrw|gone> persia: I am testing fixes now. will talk there tomorrow
[22:58] <marvin24_DT> what is good linux serial logger program?
[22:58] <marvin24_DT> I have a gadget device /dev/ttyACM0 and want to see what's coming in
[22:59] <marvin24_DT> and I hate minicom
[23:00] <topfs2> I would be interested in knowing that aswell, the only other I've tried is the gtkterminal thing. But minicom is far better than that
[23:00]  * persia remembers plars packaging something recently and hunts
[23:00] <persia> Have either of you tried moserial?
[23:01] <persia> I also know a few folk like to use screen for that.
[23:01] <marvin24_DT> the problem is that the device should log kernel boot messages
[23:02] <marvin24_DT> and it is only created a short time before logging starts
[23:02] <marvin24_DT> and then its over again
[23:02] <marvin24_DT> need something which can listen to a non existing device
[23:02] <persia> Hmm.  That gets tricky.
[23:02] <marvin24_DT> and start printing when it comes up
[23:03] <persia> If you just want a log, you might be able to do something with while(1) polling for device existence and then dumping output.
[23:03] <persia> tail --retry might also help.
[23:03] <marvin24_DT> and how to set the serial parameters?
[23:03] <persia> But either solution is subject to race conditions.
[23:11] <marvin24_DT> mmh, the "while poll loop" and cat /dev/ttyACM0 thing does not work :-(
[23:12] <persia> That's probably the result of incorrect default serial parameters (and I don't know how to set those: I've not played much with serial ports in a long time)
[23:25] <marvin24_DT> google says to start minicom and configure it there, then quit and use e.g. cat
[23:25] <marvin24_DT> found a program called "cu" from the lrzsz package
[23:26] <persia> heh.  `cu` is old-school indeed.
[23:33] <plars> I used to always use cu, much better than minicom, these days I typically just use screen
[23:33] <plars> cu is nice for logging though, in conjunction with script
[23:33] <persia> So while until it exists, then cu to grab the data?
[23:33] <marvin24_DT> looks like ttylog should do the job better
[23:34] <marvin24_DT> while loop and ttylog
[23:34] <marvin24_DT> but I still don't get any output
[23:34] <marvin24_DT> maybe nothing is written to the device
[23:34] <persia> And you're sure some exists?
[23:35] <marvin24_DT> yeah, the device is created
[23:36] <marvin24_DT> but I don't know if the kernel on the other side sends something
[23:36] <marvin24_DT> I put console=ttyGS0,115200n8 to the cmdline
[23:36] <persia> What kernel are you using?  I'm not sure the Ubuntu kernels handle gadget-as-serial-console-on-boot very well yet.
[23:38] <marvin24_DT> it's not an ubuntu kernel, but a "future" ubuntu laptop :-)
[23:38] <marvin24_DT> kernel is from android.git.kernel.org
[23:39] <marvin24_DT> kernel has the gadget is compiled in
[23:40] <persia> Which laptop?
[23:42] <marvin24_DT> ac100
[23:42] <GrueMaster> heh
[23:42] <GrueMaster> cool
[23:43] <GrueMaster> Of course, it would come out 3 weeks after I bought a new Acer Aspire One.
[23:44] <persia> Yeah.  The ac100 is *really* close.  Just needs a more recent kernel (although there were some folk at UDS talking about trying to upload a .29)
[23:46] <marvin24_DT> well, 2.6.35 is at least booting to the point it initialized the gadget ...
[23:46] <persia> Excellent!
[23:47] <persia> Is that Android, or mainline+patches?
[23:47] <marvin24_DT> the latter
[23:47] <persia> Oh, lovely.  With Ubuntu sauce also?
[23:47] <marvin24_DT> no, http://android.git.kernel.org/?p=kernel/tegra.git;a=summary
[23:47] <marvin24_DT> + a proper machine description
[23:48] <marvin24_DT> but it seems that these patches will get merged sooner or later