**** BEGIN LOGGING AT Thu Jul 07 02:59:56 2011 Jul 07 04:16:26 hi all, may i ask what is the status of GDB? i always run into SIGILL in dl_main... any idea? Jul 07 04:17:25 Try asking in #linaro. They tend to work with those tools far more often, and I believe they may actually be supporting it on arm directly. Jul 07 04:17:42 ok thanks! Jul 07 05:12:15 why cant i find the package that libXxf86misc.so is in?!?! Jul 07 05:14:14 try "dpkg-query -S /libXxf86misc.so Jul 07 05:15:16 nope Jul 07 05:15:23 seems ubuntu chose not to include this library Jul 07 05:15:43 Oh, are you looking for it to install? Jul 07 05:17:07 X11_Xxf86misc_LIB Jul 07 05:17:17 cant divine out the source package name Jul 07 05:18:42 May not be in the images anymore. I am not seeing it on oneiric arm. Jul 07 05:19:32 And it isn't on my natty amd64 netbook either. Jul 07 05:19:43 seems to be depricated. Jul 07 05:19:51 so much for libfreenect on ubuntu-arm Jul 07 05:20:02 oddly enough on 11.04 ubuntu intel ITS THERE Jul 07 05:20:38 stupid caps lock trigger finger Jul 07 05:21:19 oh wait Jul 07 05:21:24 intel debian had it Jul 07 05:21:24 11.04 was natty. Jul 07 05:21:30 10.04 maybe. Jul 07 05:21:34 11.04 arm ubuntu lacks it Jul 07 05:21:45 now my facts feel a little straiter Jul 07 05:22:37 there have been source packages for it in ubuntu until 10.10 as far as i can see Jul 07 05:23:23 Well, the last build I have for it in armel is 2009-12-03 Jul 07 05:24:01 i am on launchpad, and saus its not released for natty Jul 07 05:24:45 Ok. I was looking direclty on my mirror, which has everything from 10.04 forward for arm. Jul 07 05:24:58 But LP is more diffinative. Jul 07 05:25:54 At any rate, I'm running on fumes. 13 hour workday. Jul 07 05:26:03 night Jul 07 05:27:39 Meh. That's hardly over half time. Jul 07 06:23:57 cvdemo has a decent frame rate on panda connected to a kinect Jul 07 06:24:03 i am not entirely unpleased Jul 07 07:25:58 Hi, does anyone know how to change the extraversion variable when creating kernel packages with dpkg-buildpackage? Jul 07 07:26:09 I've tried EXTRAVERSION=-leon dpkg-buildpackage -B -uc -us but that didn't work :) Jul 07 07:26:47 make-kpkg doesn't work. It complains about some missing commands from a x86 only package Jul 07 08:51:26 x-loader-omap4 was deprecated in favour or x-loader - right? Jul 07 08:53:17 ogra_: bug 806864 is for you Jul 07 08:53:18 Launchpad bug 806864 in x-loader-omap4 "remove from repository" [Undecided,New] https://launchpad.net/bugs/806864 Jul 07 08:59:35 hrw: You win a bug closure! ;) Jul 07 09:09:36 fun is that I have this message on oneiric Jul 07 09:10:02 once it will finish upgrade I will sent apport-collect Jul 07 09:10:18 hrw: Which means you have/had the package installed at one point, and now dpkg has gotten grumpy about the stanza... Jul 07 09:10:56 hrw: Perhaps worth filing a bug against dpkg for suddenly being irked by version numbers that it used to let slide. Jul 07 09:11:00 un x-loader-omap4 (no description available) Jul 07 09:11:03 ii x-loader-omap4-panda 1.5.0+git20110325+b6bbfe7-1ubuntu1 Board initialization helper for TI OMAP 4 Panda boards Jul 07 09:11:23 hrw: Yes, note the "had"... The stanza is in there because you used to have it installed, I assume. Jul 07 09:11:43 added dpkg to bug Jul 07 09:11:46 hrw: Or you have maverick in your sources.list or something... Jul 07 09:12:24 hrw: (apt-cache policy x-loader-omap4) Jul 07 09:12:48 none Jul 07 09:12:55 N: Unable to locate package x-loader-omap4 Jul 07 09:14:24 Kay, then it's just stale info in the available DB from having it previously installed. Jul 07 09:15:24 added data to bug Jul 07 09:15:37 You can fix *your* issue with "dpkg --forget-old-unavail" probably. Jul 07 09:15:52 But the part where dpkg suddenly got stricter is still a bug/misfeature. Jul 07 09:17:02 will leave it like it is for now Jul 07 09:17:26 infinity, hmm, do you knnow if GrueMaster re-tested omap3 images ? Jul 07 09:17:48 ogra_: What's to re-test, we didn't change them, did we? Jul 07 09:18:04 (the u-boort bug is supposed to be fixed, the iso tracker still lists it) Jul 07 09:18:12 Oh. Jul 07 09:18:17 we respun all images yesterday Jul 07 09:18:32 I'm not sure what the status of omap3 stuff is, to be fair. You'll have to ask him in the morning. Jul 07 09:18:35 i see he tested all omap4 and omap3 wont have a fixed kernel Jul 07 09:18:40 i was just curious Jul 07 09:19:48 Speaking of images, though. We still have resizing issues on desktop, apparently. Jul 07 09:20:12 Fails to actually resize, explodes with ext3 errors. Jul 07 09:20:18 Yet server works fine. Jul 07 09:20:33 (Again, this is all second-hand from GrueMaster, so you might want to follow up with him) Jul 07 09:21:48 yeah, we'll skip desktop for A2 i think Jul 07 09:22:12 that will likely need some bigger changes, alonngside with the live-build ones Jul 07 09:22:34 Fun, fun. Jul 07 09:22:56 looks to me like the underlying filesystem isnt really resize friendly ... alongside with bugs in jasper Jul 07 09:23:26 Well, I'll mangle live-build tomorrow (obviously not uploading until after A2), and pass it by you for a quick review. Jul 07 09:24:13 I need to get involved in live-build upstream, I think. There are things I need to do to it that won't be pretty without upstream buy-in. Jul 07 09:24:48 But first, I need sleep. Jul 07 09:24:57 yeah, go to bed Jul 07 09:25:07 Yes mom. Jul 07 09:25:13 :) Jul 07 09:27:47 hrw: Oh, wait. I just realised that issue you were seeing was a warning, not an error. Jul 07 09:28:08 * Do not allow versions starting with non-digit when doing strict parsing, Jul 07 09:28:09 warn otherwise. Jul 07 09:28:35 hrw: Probably not really bug-worthy at all, just annoying that someone (glances at ogra_) used a policy-breaking version number in the past. :P Jul 07 09:29:14 ?? Jul 07 09:29:22 from where is that ? Jul 07 09:30:48 ogra_: In maverick, you shipped an x-loader-omap4 that had an "L" as the first character in the version. Jul 07 09:31:06 uh, yeah upstream ... Jul 07 09:31:08 ogra_: New dpkg is stricter about policy compliance and now vomits warnings about that being in the status file. Jul 07 09:31:20 hrm ... Jul 07 09:31:43 (Traditionally, when upstreams have non-policy-compliant versions, we mangle them, like 0.L4-whatever, etc) Jul 07 09:31:50 Anyhow, can't go back in time and fix it. Jul 07 09:32:10 nope, sadly ... that stain stick on me now Jul 07 09:32:16 And the number of users who will be upgrading from maverick on omap4 systems can probably be counted without removing my socks. Jul 07 09:32:16 *sticks Jul 07 09:32:43 oh, we might have more then ten that do it Jul 07 09:32:53 not by much though i belive Jul 07 09:32:56 Possibly, but I wouldn't say it's a large number. :P Jul 07 09:33:56 I don't doubt there were a chunk of maverick omap4 users, but the tester/devel types are probably reinstalling every 3 minutes, and the "normal users" (all 4 of them) are more likely to just re-flash new images than upgrade, on these sorts of devices. Jul 07 09:34:02 So. Meh. Whatever. Jul 07 09:34:51 yep Jul 07 09:35:34 I think I'll just close this dpkg bug then. Jul 07 09:36:09 hrw: You can hit me later for having marked two tasks in a row as "invalid" on this bug. :P Jul 07 09:36:18 hrw: But at least I left a friendly comment! Jul 07 09:37:08 i wonder why lintian didnt complian, i never roll new packages without checking, i think i would have noticed such an error ... Jul 07 09:38:07 Dunno. Seems odd that it wouldn't, since this has been in policy for over a decade. Jul 07 09:38:24 Oh, but it's a "should", not a "must". Jul 07 09:38:31 aww Jul 07 09:38:32 Hence why dpkg is warning, not erroring, I guess. :P Jul 07 09:38:38 Small mercies. Jul 07 09:39:27 infinity: thx Jul 07 09:40:31 hrw@panda:~$ LC_ALL=C dpkg --forget-old-unavail Jul 07 09:40:31 dpkg: warning: obsolete '--forget-old-unavail' option, unavailable packages are automatically cleaned up. Jul 07 09:40:35 ;D Jul 07 09:40:52 I had to switch to English translation cause I was unable to understand Polish one ;D Jul 07 09:42:17 Automatically cleaned up, eh? Seems not, in your case. :P Jul 07 09:48:50 ;) Jul 07 09:52:18 hrw: --clear-avail probably still works. :P Jul 07 09:53:44 yes, it does Jul 07 09:54:23 For entertainment value, there's a huge policy-versus-dpkg debate in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620566 Jul 07 09:54:25 Debian bug 620566 in dpkg "dpkg: "version number does not start with digit" is in" [Normal,Open] Jul 07 10:00:44 hi all Jul 07 10:01:12 iam running ubuntu 10.04 on my pandaboard Jul 07 10:01:39 now i builded a kernel with xenomai Jul 07 10:02:16 i replaced uImage of previously running kernel which i got from preinstalled images Jul 07 10:02:33 but it giving me some errors Jul 07 10:03:08 Is there any documentation to built the ubuntu filesystem for custom builded kernels Jul 07 10:06:55 update-initramfs -c -kVER-OF-YOUR-KERNEL? Jul 07 10:08:33 the error its giving me is unable to load modules Jul 07 10:15:50 Did you install your modules after you compiled the kernel? Jul 07 10:20:21 also copying the config to /boot/config-$version helps Jul 07 10:20:59 iirc update-initramfs checks for that too Jul 07 10:21:38 yes i installed my modules Jul 07 10:22:11 update-initramfs -c -k 2.6.37.6 Jul 07 10:23:29 you could add -v then you see what exactly it tries to do ... Jul 07 10:23:36 might reveal you more info Jul 07 10:39:48 ogra_: on the transformer I do not have the same issue with size Jul 07 10:40:06 size ? Jul 07 10:40:10 ogra_: my partition is 8MB flat, but can be extended if needed Jul 07 10:40:32 ah, then you have a more friendly bootloader :) Jul 07 10:40:38 the ac100 one can be changed as well Jul 07 10:40:39 heh :) Jul 07 10:40:55 in fact NCommander did that for many models areound we installed Jul 07 10:41:13 well I am compressing the initramfs LZMA to fit Jul 07 10:41:18 but its not really an enduser task to hack around in the bootloader Jul 07 10:41:36 well resizing can be done with nvflash Jul 07 10:41:41 my size probelm is a problem with this specific kernel i think Jul 07 10:41:56 ah Jul 07 10:42:10 ogra_: you seen it running on the transformer yet? Jul 07 10:42:16 yep Jul 07 10:42:20 pretty slow though Jul 07 10:45:01 yeah Jul 07 10:45:09 need to start on some optimizations Jul 07 10:45:15 fb is the biggest issue Jul 07 10:45:30 up to 70% usage on one core at a time Jul 07 10:45:47 at any one time* Jul 07 10:58:28 you could try the nvidia driver ;) Jul 07 10:58:46 https://launchpad.net/~ac100/+archive/ppa/ Jul 07 10:58:53 should work on the transformer too Jul 07 10:59:03 GLES is still a problem though Jul 07 11:02:20 I get a black screen Jul 07 11:02:35 with that driver ? Jul 07 11:02:44 and I still have no wifi :) Jul 07 11:02:50 the nvidia driver Jul 07 11:02:54 got an Xorg log ? Jul 07 11:02:57 injected using their script Jul 07 11:03:00 nothing on it Jul 07 11:03:30 no idea what their script does or if it hooks into the right places in the system Jul 07 11:05:06 well it is done through an xorg.conf in /etc/X11 Jul 07 11:05:21 ?? Jul 07 11:05:27 I still have everything in my fs, minus that config file Jul 07 11:05:30 you mean the script puts that in place Jul 07 11:05:34 yeah Jul 07 11:05:38 right Jul 07 11:06:09 well, it needs to mangle the ldconfig configuration, and should set the right alternative for the driver Jul 07 11:06:18 ah Jul 07 11:06:29 I will try through the PPA then Jul 07 11:06:32 it should also put udev rules in place to get you the proper acls for the kernel devices the driver needs to access Jul 07 11:06:42 still need to figure out this fing wifi though Jul 07 11:07:21 well, there are several broadcom drivers you should be able to try Jul 07 11:09:19 I don't know if that will help Jul 07 11:12:53 my driver is identical to the xoom one apart from like 6 lines (wakelock defs) Jul 07 11:13:01 the xoom one works, mine doesnt Jul 07 11:17:43 ogra_, how is the new kernle Jul 07 11:18:15 apw, all fine, thanks :) Jul 07 11:19:23 update-initramfs -c -k [2.6.37.6] update-initramfs: No match. Jul 07 11:19:48 update -initramfs -c -k -v Jul 07 11:20:40 []2.6.37.6 ] Jul 07 11:20:51 even that also gicing the same error Jul 07 11:20:55 no match Jul 07 11:21:25 i have moved config and system map files to boot Jul 07 11:27:44 why did you put the version in brackets ? Jul 07 11:32:53 when i run update-initramfs -c -k Jul 07 11:33:04 it showing me options Jul 07 11:33:54 test06:/media/disk-3/etc# update-initramfs -c -k /usr/sbin/update-initramfs: option requires an argument -- k Usage: /usr/sbin/update-initramfs [OPTION]... Options: -k [version] Specify kernel version or 'all' -c Create a new initramfs -u Update an existing initramfs -d Remove an existing initramfs -t Take over a custom initramfs with this one -b Set alternate bo Jul 07 11:34:38 stm__: yeah replace [version] with the version not put it in the brackets :) Jul 07 11:34:57 update-initramfs -c -k 2.6.37.6 Jul 07 11:35:46 thanks Jul 07 11:36:00 is that the only change i have do Jul 07 11:36:19 inorder to boot withe the new uImage Jul 07 11:41:56 ogra_: do you have sound working on the AC100 Jul 07 11:42:06 no Jul 07 11:42:08 not yet Jul 07 11:42:21 there is active work going on though Jul 07 11:42:25 ok :) Jul 07 11:42:33 and i gave a device to one of the ubuntu alsa guys Jul 07 11:42:43 but he is on paternity leave for a few weeks now Jul 07 11:43:06 ah Jul 07 11:44:15 others in #ac100 are hacking on it though Jul 07 11:45:39 I can get aplay to show the device but not play anything Jul 07 11:46:31 same here Jul 07 11:46:39 what coded does the transformer use ? Jul 07 11:46:51 *codec Jul 07 11:46:52 WM8903 Jul 07 11:47:22 hmm, no idea about that one Jul 07 11:47:35 ac100 uses a relatek Jul 07 11:47:41 *realtek Jul 07 11:47:55 ah Jul 07 11:48:11 alc53** Jul 07 11:48:16 or so Jul 07 12:24:04 hi all Jul 07 12:28:05 the modules for the new kernel have only drivers directory Jul 07 12:28:20 when i run update initramfs Jul 07 12:28:30 it giving me the error Jul 07 12:28:40 but you ran make mudules_install when you built your kernel ? Jul 07 12:28:49 yes Jul 07 12:28:52 i ran Jul 07 12:29:18 it given me 2.6.37.6 directory Jul 07 12:29:21 so /lib/modules/$(uname -r)/ should have modules if you selected any in the config Jul 07 12:29:21 in lib Jul 07 12:30:39 i mean it giving me the error cound not find crzpto directory Jul 07 12:30:48 crypto Jul 07 12:31:21 when you installed the crypto stuff should have been removed by the installer ... strange Jul 07 12:31:45 unless you selected "encrypt my home dir" on the user creation page Jul 07 12:32:26 you can manually uninstall cryptsetup though Jul 07 12:32:40 if your kernel has no support for it Jul 07 12:33:56 what is the relation with crypt stuff and initrd image Jul 07 12:34:22 to unencrypt filesystems before they get mounted you need to get the password Jul 07 12:34:30 that happens in initrd Jul 07 12:35:04 for all filesystems that have to be in place before login Jul 07 12:35:46 ok Jul 07 12:37:00 iam sorry for these type questions . iam bit new to this . Jul 07 12:38:15 then do i need to uninstall crzpto stuff Jul 07 12:38:29 crypto stuff Jul 07 12:38:43 to make update this initramfs Jul 07 12:56:03 wm8xxx are nice supported in linux usually Jul 07 13:04:28 lilstevie: broonie (Mark Brown) is maintainer of wm**** drivers Jul 07 13:28:20 @ogra : do i need to change boot args Jul 07 13:28:40 for the root device Jul 07 13:30:35 no, the installer should have set the UUID properly Jul 07 13:34:49 Is it possible to install the prebuild arm Ubuntu rom on a random omap4 android phone without typing phone-specific commands? Jul 07 13:35:52 strange, yesterday someone in #pandaboard asked nearly the same and couldn't believe that pandaboard images were not at all meant for his funky motorola thing. Jul 07 13:47:04 what are "phone-specific" commands Jul 07 13:47:40 whisteling the right tunes to imitate a keypad ? Jul 07 13:47:58 heh Jul 07 13:48:28 Mean you no need to modify command that you type according to the phone you have… Jul 07 13:49:15 * LetoThe2nd guesses he refers to obscure rooting and flashing command from some homebrew-rom-installer board. Jul 07 13:49:31 c3would you mind giving an example, link? Jul 07 13:56:18 .. can't think of an example .. Jul 07 14:06:39 then how did you get the idea it could be necessary? Jul 07 14:10:56 As people prefer step by step instruction but to any things that need to test and correct themselves…… Jul 07 14:13:12 *** statement parsing error: ENOTUNDERSTANDABLE - bailing out. Jul 07 14:15:18 in another word people doesn't like thinking… Jul 07 14:56:35 hi Jul 07 14:56:57 it i mean the booting prcess giving me the same result Jul 07 14:57:11 uncompressing linux done Jul 07 14:57:20 booting the kernel Jul 07 15:33:15 ogra_: having the large partition is extremely nice, no cosntant out of disk spce warnings :-) Jul 07 15:34:04 i never have that :) Jul 07 15:34:25 but i also dont use much data on the local disk ... my payload lives externally Jul 07 15:39:20 ogra_: Where is the delta review page? Jul 07 15:39:29 ogra_: I don't see what delta I have Jul 07 15:39:51 lag, no idea, i didnt even know about that spec :) Jul 07 15:45:29 I need to figure out how to layout my emmc :p Jul 07 15:45:30 I crave the speed of moving internal Jul 07 15:46:28 emmc? Which platform? Jul 07 15:46:36 transformer i guess Jul 07 15:50:33 that one :) Jul 07 15:50:59 not much different from ac100 in that regard Jul 07 15:51:13 more ram, bigger panel and different wlan Jul 07 15:51:16 gpt on the ac100? Jul 07 15:51:24 ah, no Jul 07 15:51:32 don't forget the different audio codec :p Jul 07 15:51:35 i thought it used a fastboot based installer too Jul 07 15:51:41 oh, yeah Jul 07 15:51:51 well, they are both tegra2 :P Jul 07 15:51:54 heh Jul 07 15:52:02 is yours harmony or ventana Jul 07 15:52:15 harmony based i think Jul 07 15:52:22 * ogra_ isnt sure Jul 07 15:52:26 ah ok, this one is ventana Jul 07 15:52:45 bah, so they are totally different devices that pretend to be the same :P Jul 07 15:52:51 heh Jul 07 15:54:55 i have included earlyprintk /boot/boot.script stiliam seeing nothing after uncompressing linux Jul 07 15:55:09 but it booting fine if i replaces the uimage Jul 07 15:58:39 ogra_: wifi is not looking good on this device Jul 07 15:59:14 there is a userland binary which runs after module is loaded and firmware has been uploaded Jul 07 18:59:50 hi all Jul 07 19:00:33 i have problem while booting with the custom uImage Jul 07 19:00:48 its giving me uncompressing linux Jul 07 19:01:16 if i change root to /dev/mmcblk0p2 Jul 07 19:01:28 then the root device is notmounting Jul 07 19:02:03 Do you have a rootfs on a device that your kernel detects as /dev/mmcblk0p2 ? Jul 07 19:02:31 i have ubuntu rootfs on device Jul 07 19:02:44 i have bulded a custom uImage Jul 07 19:03:10 it is booting good if i used the preinstalled images from ubuntu Jul 07 19:03:22 if i change the uImage Jul 07 19:03:55 How did you construct the uImage? Jul 07 19:03:56 then it just showing me uncompressing linux Jul 07 19:04:14 i downloaded the kernel Jul 07 19:04:24 then patched with adeos ipipe Jul 07 19:04:33 and then compiled it Jul 07 19:06:03 Which kernel did you download? Jul 07 19:06:17 2.6.37.6 Jul 07 19:06:24 From where? Jul 07 19:07:24 git://git.xenomai.org/ipipe-gch.git Jul 07 19:08:16 Are you certain that this kernel includes all the patches from the Ubuntu kernel? My suspicion is that your new kernel isn't representing your storage in the same manner. Jul 07 19:09:13 ok Jul 07 19:09:44 then how can i boot this kernel with ubuntu Jul 07 19:10:24 Firstly, you'd need to understand how that kernel represents the storage area into which you have placed the rootfs, and pass the correct argument. Jul 07 19:10:53 Secondly, you'd need to be sure that kernel had the appropriate support for the Ubuntu booting procedures, etc. Jul 07 19:13:15 Is there any link for the ubuntu booting procedures on pandaboard Jul 07 19:15:22 No, but there's nothing remarkably special about the pandaboard in this case. Jul 07 19:15:51 For the least-failure-prone path, I'd recommend starting with the Ubuntu omap4 kernel sources, and then trying to apply patches to that. Jul 07 19:16:06 If that result doesn't work, you can be fairly sure that this is due to the patch. Jul 07 19:16:25 Conversely, if you select an arbitrary kernel, the source of possible failures can be large. Jul 07 19:21:13 yes but here the constraint is the ipipe support for pandaboard . They did not released it as a patch . thez released it as patched kernel Jul 07 19:23:10 You referenced a git tree: you ought to be able to use git to determine which patches have been applied which are not applied in the Ubuntu tree. Jul 07 19:28:41 ndec: i'm trying to get my new blaze board to boot ubuntu Jul 07 19:28:53 ndec: but it's not even showing uboot Jul 07 19:29:10 ndec: i'm trying to boot from SD Jul 07 19:35:43 demarchi: you need a special x-loader and u-boot for blaze Jul 07 19:36:18 demarchi: for Maverick https://wiki.ubuntu.com/ARM/OMAPMaverickInstall Jul 07 19:36:47 then to support Natty I believe you can just use the same x-loader/u-boot combination Jul 07 19:37:05 just need to check if the kernel supports blaze, and as I don't have one I never tested Jul 07 19:37:24 GrueMaster: did you ever tested natty on a blaze? Jul 07 19:37:51 demarchi: do you know which ES rev do you have at your blaze? Jul 07 19:38:03 we only support >= ES2.x Jul 07 19:42:44 rsalveti: it's ES2.2 GP Jul 07 19:43:06 rsalveti: what's the difference between EMU and GP? Jul 07 19:44:31 demarchi: hm, quite new actually Jul 07 19:44:44 demarchi: not sure, maybe you can find it at http://www.omappedia.org/wiki/Blaze Jul 07 19:44:57 or maybe robclark can help us :-) Jul 07 19:45:01 otherwise ndec is your man Jul 07 19:46:11 demarchi, an EMU is sort of half way between a HS and GP device.. Jul 07 19:46:33 HS has all the security and firewall stuff.. and is generally a pita to debug / use jtag, etc.. Jul 07 19:46:47 GP is wide open.. Jul 07 19:47:17 and EMU has all the security features but can be opened up.. basically intended for R&D.. Jul 07 19:47:34 (maybe I paraphrase a bit.. but that is the general idea) Jul 07 19:48:23 robclark: depending on my version, i need a different MLO, right? Jul 07 19:48:51 yes.. or rather HS and (I think) EMU would need a signed bootloader Jul 07 19:49:08 robclark: i have a GP one Jul 07 19:49:34 ok, then don't worry about EMU/HS stuff ;-) Jul 07 19:49:52 nice... Jul 07 19:49:59 just use normal blaze/panda/whatever MLO.. depending on what board you are using Jul 07 19:50:34 maybe the problem was because i didn't rename the gp_MLO to MLO when copying to the sd card? Jul 07 19:50:48 yeah.. that would be a problem Jul 07 19:59:36 robclark: it didn't work Jul 07 19:59:45 robclark: no output on console :-/ Jul 07 20:00:48 well.. what board, what bootloader? Jul 07 20:01:13 fwiw, ubuntu itself isn't very chatty on the serial console.. but you should see *something* for the boot-loader.. Jul 07 20:02:00 robclark: nothing... i don't see u-boot on this board Jul 07 20:02:55 hmm.. I'm guessing the default ubuntu image has a panda boot-loader.. Jul 07 20:03:07 so I'm assuming you replaced that already w/ something for blaze? Jul 07 20:08:25 robclark: the guide for android has the uboot and mlo Jul 07 20:08:30 robclark: i tried those Jul 07 20:09:13 where did those come from? And are they actually for a GP device? Jul 07 20:09:26 robclark: that should work for ubuntu as well Jul 07 20:09:28 I think most of the android folks are using either EMU or HS Jul 07 20:09:31 http://www.omappedia.org/wiki/Android:_Working_with_pre-built_binaries Jul 07 20:09:47 there's a gp_MLO there Jul 07 20:10:14 and looking at this thread, i think it should work: http://permalink.gmane.org/gmane.comp.hardware.microcontrollers.omap/69 Jul 07 20:10:40 hmm.. Jul 07 20:11:05 well, the non-gp MLO name seems to imply it is for an es2.1.. so it's possible you need something newer.. Jul 07 20:14:03 robclark: humn.... true Jul 07 20:14:11 well, MLO and u-boot are easy enough to build.. Jul 07 20:14:15 robclark: i'll just try to compile a newer version Jul 07 20:14:30 it might be easier to just clone the git trees and build your own.. Jul 07 20:15:09 I think if you take whatever versions are used in 11.04 and just build em w/ sdp4430 config (or whatever it is called..) Jul 07 20:36:57 rsalveti: I think I tested Blaze back with Natty Beta 1 Jul 07 20:37:49 Does it need anything than a different u-boot? Could support be added to our u-boot tree? Jul 07 20:38:27 persia: needs support at the x-loader and u-boot Jul 07 20:38:37 but TI didn't actually pushed the support upstream Jul 07 20:38:51 they are maintaining it at their own tree at omapzoom Jul 07 20:39:05 iirc, the mlo/u-boot for blaze from Maverick worked with natty as well. Jul 07 20:39:15 Kernel is good. Jul 07 20:39:20 just need to test if it works with es2.2 Jul 07 20:39:36 If I get time, I'll check it out, but it is currently low priority for me. Jul 07 20:39:37 rsalveti, Ah. Is there something deeply incompatible, or is it just a matter of not having gotten around to it yet? Jul 07 20:39:46 I only have a 2.0 Jul 07 20:40:08 persia: lack of hardware for the upstream maintainers and missing someone to actually push the patches upstream Jul 07 20:40:23 so we can only wait TI to do it :-) Jul 07 20:41:07 Well, or someone with compatible hardware and sufficient motivation, but yeah, that's most likely TI. Jul 07 20:41:28 with pandas around, don't know why someone would use a blaze Jul 07 20:41:35 I mean, from community Jul 07 20:42:07 It has a nice plastic box, and nice screens, and bamboos are hard to find? Jul 07 20:42:09 persia, usually bootloader needs to be updated for a new ES.. if nothing else, to add a new Si revision id.. but usually there are different settings for voltage rails, different memory settings, etc, etc.. Jul 07 20:42:20 There's lots of us that don't like dev boards as a form factor. Jul 07 20:42:30 persia: it's expensive, hard to get and so on :-) Jul 07 20:42:41 robclark, Right. I thought that was just compile-time choices. Jul 07 20:42:43 so it is safe to assume that bootloader needs to be rev'd whenever there is a new ES Jul 07 20:42:56 no, it is even runtime.. Jul 07 20:42:57