[00:00] dcordes, I think I would have rephrased that question if I were you. [00:01] jo-erlend: Sorry ? [00:02] jo-erlend: I think he is referring to the Toshiba AC100 that ogra_ac is on. And yes, it is a Tegra 2 system. [00:02] ah. :) [00:07] * dcordes is waiting for decent qualcomm smartbook [00:07] Keeping track of one SoC is enough [00:08] Only need to convince somebody I can't make it through the winter term alive without one :D [00:08] ha! [00:09] Doubt it will work but I need to find a job anyway [00:12] Is it possible that it is my monitor that causes this? http://pastebin.com/6hAjUwCW [00:14] I think it's unlikely. I think you have to pass a framebuffer mode argument. Are you booting from recent dailies, or something else? [00:14] beta. It seems to be the only readily available image? [00:15] Oh, if you're using raw beta, that ought be passing a parameter [00:16] http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/ has some more recent images. Mind you, those are entirely unvalidated, so might not work, or not exist, etc. on any given day. [00:17] grand! Thank you. I'll give that a go immediately. I couldn't find that earier today. Perhaps I gave up too quickly. :) [00:18] hm, ureadahead is now using a 8mb buffer, instead of 128mb [00:18] persia: did come out some upgrades to maverick today? [00:18] interesting [00:19] persia: I found my usb-audio device. RCA & SPDIF in/out. Tested ok on my laptop. What were you suggesting I test it on? [00:19] and should fix the oom killer messages at beagleboard [00:19] GrueMaster, Anywhere you can, once per kernel flavour. No point on two devices with the same kernel, but otherwise. [00:20] I'll add it to the to-do list. [00:20] GrueMaster, rlamiero was reporting that on IGEPv2 (omap3) with the kernel from "linux", usb audio didn't work. I wouldn't be surprised to see other kernel flavours affected. [00:21] As it stands, my XM is the only one with spare USB ports, and it is borked. [00:21] well it work on i686 [00:21] No rush, but it would be nice to be able to tell folks they can use usb-audio in the event that we don't have working wiremaps for various boards. [00:21] rlameiro, Sure, but that's a different kernel flavour: linux-generic vs. linux-omap (although it comes from the same source package, which means we're more likely to have it just work) [00:22] yeap [00:22] GrueMaster: so, did you test the audio at the c4? [00:22] it is weird because the problem aplay output was about the bit rate or something like that [00:22] if it's not working this could explain why the same behavior at the xM [00:22] and a regression, as it worked fine for lucid [00:23] different kernel tree though [00:23] rsalveti: On my beagle, I had to tweak alsamixer settings to get the alsa speaker-test to work. [00:23] GrueMaster: same for xM, am I right? [00:23] My xm has other issues. [00:23] (like getting through a boot process). [00:23] but last time you tested audio you said it worked after setting up alsa-mixer correctly, IIRC === amitk is now known as amitk-afk [00:24] I thought I had. With as much testing as I do, unless I find a bug, I tend to forget what I tested where. [00:24] And it is very hard to test everything on everything. [00:25] haha, np [00:25] Especially with special requests coming in fast & furious. [00:25] but yeah, I remember you tested at the xM and you got it working after setting up alsa-mixer [00:26] that's why we discussed it at our call [00:26] and where we got the idea to test it on a normal beagle [00:26] because with lucid it just works [00:27] Right. [00:27] But now I can't get my XM to boot through a known good image. [00:28] These sudden audio issues eat at my soul. [00:28] this is something weird, let me try to boot mine [00:28] GrueMaster: what errors are you getting? [00:31] On which? Audio or XM in general? [00:33] can someone translate this for me? "omapfb.mode=dvi:1024x768MR-16@60". It's the bootargs I've been told to use. :) [00:33] xM in general [00:33] persia: usb-audio device shows up and is configurable on dove. Still no audio output from rythmbox. [00:34] jo-erlend: while setting up omapfb with dvi, this should be your default resolution [00:34] otherwise you'll get 640x480 [00:34] rlameiro, Does GrueMaster's report on dove match your experience on the IGEPv2? [00:34] that's the default one [00:34] rsalveti, what would happen if my monitor didn't support that resolution? [00:34] rsalveti: On my XM, it fails randomly. Sometimes it is a corrupted filesystem on second boot, sometimes it gets most of the way through oem-config before it crashes. [00:34] jo-erlend: will probably give out of sync or something like that [00:35] jo-erlend: use the Digital output of omap framebuffer driver with a res of 1024x768 with a bit depth of 16 bits at 60 hz refresh rate [00:35] I have not seen any errors that could be traceable. [00:35] GrueMaster: sounds like the random mem issues I'm facing with 512 [00:35] Possibly. [00:35] mine just works when I add mem=256M [00:35] persia: i didnt used rythmbox, but yea, it is configured but no sound output [00:35] I'll give it a try. [00:35] Hate hacking the boot.scr [00:36] the interesting thing is that some times it just works fine, but most of the time I try to boot with 512mb it'll give me random segfaults [00:36] I thought that since it fails to load the omapfb module, it might be because the modes were incorrect? [00:36] welcome to the club [00:36] How about lower level sound tests? Let's find the point at which it breaks. [00:37] jo-erlend: default should be safe, then you can try different resolutions [00:37] aplay should be a good ground level [00:37] persia: [00:37] Morning all [00:37] jo-erlend: what's you problem regarding omapfb? [00:37] lag: haha, morning [00:37] crazy timezone [00:37] rlameiro, I don't have an environment to help: tell GrueMaster :p [00:37] australia? [00:37] rsalveti, http://pastebin.com/6hAjUwCW [00:37] taiway [00:37] persia: speaker-test works with usb-audio on dove. [00:37] *taiwan [00:38] jo-erlend: oh, ok, the missing fb0 [00:38] jo-erlend: can you grab your dmesg? [00:38] haha? [00:38] Oh, I see [00:38] :) [00:39] rsalveti, I'm currently overwriting the memorycard with todays daily to see if that works. [00:39] rlameiro: Weren't you having issue with *any* audio? I don't think you were using pulse. [00:39] i dont use pulse [00:39] just lasa [00:39] alsa [00:39] if alsa is broken, pulse will be also [00:40] jo-erlend: could be better, but it's probably not going to fix this weird missing fb0 error [00:41] because we didn't change our kernel much regarding this driver [00:41] rlameiro: too true. [00:41] but please try, let's see what happens [00:41] if still doesn't work, you can try linaro's kernel [00:49] persia: GrueMaster http://pastebin.ubuntu.com/497342/ [00:52] rlameiro: Try "speaker-test -c 2 -t wav -Dhw:1" [00:53] GrueMaster: persia http://pastebin.ubuntu.com/497343/ [00:54] hmm [00:54] seems not using andchat gets me a far more stable network [00:54] i should remind that this usb interface doesnt have software mixer [00:55] rlameiro: try without the -D parameter. [00:55] that will play on the board. [00:56] Worked on usb-audio here. [00:56] the daily image doesn't seem to have anything except the boot partition. Well there is another partition too, but it only contains lost+found. [00:56] the daily should have 2 partitions [00:57] boot and rootfs, that will get resized at the first boot [00:57] GrueMaster: its working on the board output [00:57] yes, it does, but the rootfs is empty. [00:57] jo-erlend: after or before the first boot? [00:57] sorry.... Nautilus fooled me. :) [00:58] uh. I get lots of io errors now. [00:59] rsalveti, what do you mean? Everything should be on the board before the first run? [00:59] GrueMaster: speaker-test says this at the help file --- Recognized sample formats are: S8 S16_LE S16_BE FLOAT_LE S32_LE S32_BE [00:59] jo-erlend: sorry, after you putting the card and giving the first boot or before [01:00] but i am prety sure my board only send 24bit streams [01:00] any way it should work [01:01] * rsalveti brb [01:01] i will try the interface with the advanced mode off [01:02] lol another problem, each time I unplug a usb device, when i plug it back it cant be enumerated [01:02] i need to restart the board [01:11] GrueMaster, persia http://pastebin.ubuntu.com/497351/ [01:12] strange is that the stream of the driver is defined to 44100hz when the board is capable and hardware selected to 48000 [01:13] I forced speaker-test to the driver parameter and it worked, just the problem was that the audio file was at 48khz, so nothing happened [01:13] rlameiro, That looks like a deep bug, and ALSA is probably doing some internal resampling. Probably worth running the testing shell script and sending it upstream. [01:13] humm [01:14] persia: is that test on the repos? [01:16] * persia isn't sure [01:22] found this [01:22] it says nothing special [01:22] persia: unless this ----EDIROL UA-4FX at usb-ehci-omap.0-1.2, full speed [01:23] Hrm. [01:23] this means that the driver is on the specific module usb-ehci-omap.0-1.2 ? [01:24] i dont have the sources of the kernel from rcn-ee so i cant check it out [01:25] rlameiro: Unfortunately, I have a completely different usb-audio device. http://paste.ubuntu.com/497363/ [01:25] And it supports 48000 [01:26] well, then yeah, this driver is completely broken [01:26] I just wanted to know where do i find the sources for it [01:27] Either in the kernel or from http://alsa-project.org. [01:27] What is loaded by Ubuntu is in the kernel. [01:28] alsa-project.org may have newer updates that will be in the next kernel. [01:30] well, but it works on my laptop, i even helped testing the patch made for this device some years ago [01:30] and it went already to alsa release [01:30] and it is fully supported on ubuntu, so i dont get it, it shouldnt be platform dependent should it? [01:32] No, it shouldn't. [01:33] well i gues i will digg into it tomorrow [01:33] /proc/asound/card1/stream0 should be identical across platforms. [01:33] well i will compare it with the one on my laptop [01:33] 1 sec [01:36] GrueMaster: well its definetly an ARM/Board/ubuntu kernel issue or ubuntu driver [01:36] http://pastebin.ubuntu.com/497368/ [01:37] interesting. [01:38] Same kernel on both? [01:38] it seems something is wrong with the driver that doesnt detect the card correctly [01:38] nope [01:38] The omap driver is part of the main stream kernel. [01:38] Linux studiobeta 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:24:04 UTC 2010 i686 GNU/Linux [01:38] Linux beagleboard 2.6.35.4-l1 #1 PREEMPT Fri Aug 27 22:09:57 UTC 2010 armv7l GNU/Linux [01:39] apples<>oranges. [01:40] Unfortunately. [01:40] ?? [01:40] Completely different alsa versions. [01:41] cat /proc/asound/version [01:41] Say, is Tegra2 going to be an officially supported architecture? [01:41] my is 1.0.23 [01:41] rlameiro: on both? [01:41] Supported as in, has kernels built and won't get illegal-instruction errors? [01:41] this is on arm, let me check the board [01:41] DanaG: If someone pushes a kernel into the pool, sure. [01:41] 1.0.21 [01:42] regression? [01:42] rlameiro: very possibly. [01:42] "has kernels built" could even be unofficial, as rcn-ee's OMAPs are/were/are. [01:42] well, then i have to download the ubuntu beta to test it... [01:42] rlameiro: Try downloading one of the ubuntu i386.iso files and run it live. Compare results. [01:42] A bigger concern is the CPU instruction-set support -- can't use NEON on it. [01:43] rlameiro: I would try a daily. [01:43] http://cdimage.ubuntu.com [01:43] DanaG: Shouldn't be an issue. Marvell doesn't either. [01:43] Most apps don't care. [01:43] Marvell doesn't even do armv7l, at least in any currently available products. =/ [01:44] oversized images... [01:44] rlameiro: Write one to USB. faster and doesn't waste a CD. [01:44] Use usb-creator to make a bootable usb stick. [01:44] well downloading [01:45] i need to buy a usb stick for this stuff :D [01:45] 1438 KB/s not bad... [01:45] rlameiro: WIll your laptop boot from SD? [01:46] dont think so [01:46] I'm jealous btw. My max speed is 468KB/s :P [01:46] GrueMaster: never tried it, it does have an removable disk options [01:46] axel rocks :D [01:46] great downloader for the cli [01:47] Where are you on this great rock in space? [01:47] Portugal [01:47] Ah. Closer to our servers. [01:47] UK? [01:47] I'm in Oregon, USA. Much farther for bits to travel. [01:48] Yes. Millbank, I believe. [01:48] rsalveti, you're right. It didn't change anything. Which files do you want? [01:48] i will test some download from Oregon after the download finish [01:48] do you have some link to a mirror from a uni there or something? [01:50] You can try http://members.dsl-only.net/~tdavis/beagleboard-bug.jpg [01:50] lol [01:50] Not very big, but it is my ISP. [01:50] too small to test [01:51] There is a mirror server at http://ubuntu.osuosl.org/ubuntu/ [01:51] but i will try anyway [01:53] GrueMaster: Downloaded 694,7 megabytes in 8:14 seconds. (1437,95 KB/s) [01:53] I hate you. :P [01:54] I have DSL here. And I am paying premium for the fastest speed available. [01:54] jo-erlend: dmesg would help, for sure [01:54] And I still get pidgeon-net speeds. [01:54] yeap, the connection to there is way worse than to the ubuntu server [01:55] GrueMaster: i have DSL to, my sync is about 17 MB/s [01:56] rsalveti, rbelem has quit (Quit: Leaving) [01:56] * o [01:56] bah. :) [01:56] rsalveti, http://pastebin.ubuntu.com/497379/ [01:57] [ 1.497497] omapfb omapfb: no displays [01:57] [ 1.501312] omapfb omapfb: failed to setup omapfb [01:57] probably because of: [01:57] [ 0.269592] omapdss VENC error: can't get VDDA_DAC regulator [01:57] [ 0.269622] omapdss CORE error: Failed to initialize venc [01:58] which points to bug 607250 [01:58] Launchpad bug 607250 in linux (Ubuntu) "omapdss: VDDA_DAC regulator on IGEPv2 (affects: 1) (heat: 65)" [Undecided,Incomplete] https://launchpad.net/bugs/607250 [02:00] rsalveti, do you think changing the kernel would fix this? [02:01] probably not, as this was reported to linux-linaro [02:01] any ideas at all? [02:02] GrueMaster: rebooting, going to test it now [02:03] ok [02:03] jo-erlend: needs to find the missing patch for it [02:04] Is there a page that that pic goes with? [02:08] jo-erlend: could be this one: http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/2.6-stable/annotate/head:/patches/igepv2/0001-ARM-OMAP3-Add-S-Video-output-to-IGEPv2-board.patch [02:08] will build a new kernel for you to test, give me 10 min [02:08] thanks :) [02:15] GrueMaster: well, back [02:16] the card was detected correctly, speaker test gave the same error but i think it has to do with the format of the streaming "SE24_LE" [02:18] Hmmm. [02:18] the iso is not woking ok, it didnt booted completely after selecting try it.. lol i had to use ctrl+alt+F1 :D [02:18] jo-erlend: please test http://people.canonical.com/~rsalveti/kernel/uImage.igep2 [02:18] jo-erlend: just copy it over your uImage from the first partition [02:18] rsalveti, then I simply replace the uImage with that one? [02:18] right. [02:19] then please get your dmesg for me again [02:21] rsalveti: brasileir? [02:21] brasileiro? [02:21] rlameiro: sim, portugues? [02:21] BOA ! [02:21] :-) [02:22] !pt :p [02:22] Factoid 'pt :p' not found [02:22] !pt [02:22] Por favor, use #ubuntu-br para ajuda em brasileiro. Para entrar no canal por favor faça "/join #ubuntu-br" sem as aspas. Para a comunidade local portuguêsa, use #ubuntu-pt. Obrigado. [02:22] persia: :P [02:23] persia: lol, we got it, it was just that moment of hapiness finding a language brother :D [02:23] I know :) [02:24] And since the two of you have such similar interests, I suspect there's going to be a lot of value to portuguese coordination for ARM audio :) [02:24] rsalveti: also into audio? [02:24] haha, not yet, still fighting with display issues :-) [02:24] lol [02:25] i took that out of the picture, [02:25] Hey, alsa on armel sounds the same, regardless of language. :P [02:25] * rlameiro runs is board headless :D ssh rulezzz [02:25] haha, for sure, but we need to get it working for our users haha [02:25] * rlameiro ssh -X even better :D [02:25] haha :-) [02:26] Not when your armel laptop is closer than your desktop :p [02:26] rsalveti, http://pastebin.ubuntu.com/497388 [02:26] jo-erlend: [ 0.000000] Linux version 2.6.35-22-omap (buildd@satinash) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4) ) #32-Ubuntu Fri Sep 17 09:09:03 UTC 2010 (Ubuntu 2.6.35-22.32-omap 2.6.35.4) [02:26] jo-erlend: still not my kernel [02:27] rsalveti, what I did, was to rename uImage to uImage.old and then rename uImage.igep2 to uImage. [02:27] same one as before [02:27] jo-erlend: hm, weird, could be a bug at u-boot [02:27] we got a similar bug with the older u-boot we used for panda [02:28] I should delete uImage.old as well? [02:28] to make sure, copy your files to your pc, give mkfs.vfat -F 32 /dev/sd and then copy them again [02:28] if you're facing the same bug, then it's not going to work even if you remove the older uImage [02:28] rsalveti, I read somewhere that using -F 32 wouldn't work though. It was old, but still. [02:29] well, don't know much of igep2 [02:29] do it as you can find at your igep2 tutorial :-) [02:29] but recreate it and then copy the new files [02:29] what is the problem with it? [02:29] in this case, just copy the new uImage [02:30] rlameiro: display not working for igep2 using default kernel for omap3 [02:30] omapfb? [02:30] yup [02:30] I found a patch but waiting jo-erlend to test it [02:31] this is mine dmesg [02:31] http://pastebin.ubuntu.com/497390/ [02:32] and boot args, sorry for the flood [02:32] fatload mmc 0:1 0x80000000 uImage [02:32] fatload mmc 0:1 0x82000000 uInitrd [02:32] setenv bootargs-base vram=12M omapfb.mode=dvi:hd720-16@50 [02:32] bootm 0x80000000 0x82000000 [02:33] rlameiro: which kernel? [02:33] rsalveti: Linux beagleboard 2.6.35.4-l1 #1 PREEMPT Fri Aug 27 22:09:57 UTC 2010 armv7l GNU/Linux [02:33] rcn-ee one [02:33] rlameiro: cool, the patch I found was applied at his kernel [02:34] and it's not giving you errors [02:34] so it seems to fix it [02:34] once confirmed will send to the kernel team [02:35] i can try to test it tomorrow on my hdmi tv, my girl is sleeping there now..... she will kill me if I wake her up :D [02:35] rlameiro: haha, don't need to worry, I completely understand you :-) [02:37] rsalveti: lol, and I am Ricardo too [02:37] w00t [02:37] #win [02:37] :-) [02:38] rsalveti, http://paste.ubuntu.com/497395 [02:39] hm, weird, same error [02:39] jo-erlend: could you try rlameiro's boot args? [02:39] vram=12M omapfb.mode=dvi:hd720-16@50 [02:41] well it is for a tv, but should be ok [02:42] but now a different error [02:42] rsalveti, I keep the others, I just add those arguments? [02:42] [ 0.269592] omapdss VENC error: can't get VDDA_DAC regulator [02:42] [ 0.269622] omapdss CORE error: Failed to initialize venc [02:42] and now [02:42] [ 0.255493] omapdss SDI error: can't get VDDS_SDI regulator [02:42] [ 0.255493] omapdss CORE error: Failed to initialize SDI [02:43] jo-erlend: change omapfb.mode=dvi:1024x768MR-16@60 to vram=12M omapfb.mode=dvi:hd720-16@50 [02:44] hm, currently you don't have vram [02:44] mem=512M console=ttyS2,115200n8 console=tty0 omapfb.mode=dvi:1024x768MR-16@60 root=/dev/mmcblk0p2 rw rootwait text [02:44] this is your current boot line [02:45] try just adding vram=12M first [02:45] * GrueMaster is calling it a day. [02:45] while a look for an additional patch [02:45] *I [02:51] rsalveti, no change. [02:52] rsalveti, http://paste.ubuntu.com/497402 [02:53] could be another bug =\, just a moment, looking for other patches [02:54] thank you. I appreciate it. [02:54] well. I did change the omapfb.mode setting. I had already done that when you told me to only add the vram setting. Does that matter? [02:55] nops, seems a different bug [02:55] but wanted to check just to be sure [02:55] rsalveti: do you want my uImage? [02:55] rlameiro: no thanks, I got the sources of it already, trying now to understand what's missing [02:59] seems that it's just missing a regulator definition [03:06] is that something you can fix? :) [03:08] jo-erlend: it seems I found the problem, working for a fix [03:09] seems that the cause is another dss2 patch that we got at our tree [03:10] jo-erlend: give me some minutes and I'll send another uImage to test [03:11] great! :) [03:18] building a new kernel [03:19] :) [03:19] it would be really cool if that worked. I think the board is very cute, but it would be nice to be able to use it for something too :) [03:20] sure :-) [03:22] jo-erlend: http://people.canonical.com/~rsalveti/kernel/uImage.igep2-v2 [03:22] same procedure, please :-) [03:23] hopefully at least a different error message [03:23] :-) [03:25] rsalveti, hey, I have something! [03:25] I have text! It's kinda blue! [03:25] quick Q for those "in the know" ... the default netbook launcher (clutter one) ... what ships there for sound ? that depend on pulse ? or is it also using canberra ? [03:25] jo-erlend: awesome [03:25] oh nvm, I can find out via synaptic [03:25] blue should be fine [03:25] at least I get blue text at my panda [03:25] but it works fine on X [03:26] * rsalveti never tested the clutter based netbook launcher [03:26] jo-erlend: can you send me your dmesg [03:27] jo-erlend: even if you get something, to be able to login at your serial you probably need to create a ttyS2.conf file for your upstart [03:27] with correct parameters [03:27] devilhorns, I believe the default stack should be canberra-on-pulse: which layer a given app hits depends on the app. More use of canberra for simple alerts would be appreciated. [03:27] rsalveti, I have no serial :/ [03:27] oh, that's fine [03:27] jo-erlend: so you should be able to see something at your monitor [03:28] persia, ok, just wanted to check if canberra was the way we want to go wrt the efl one [03:28] I get a fatal error, missing files in /lob/modules/blabla. I noticed that before, I have no /lib/modules directory. Am I supposed to? [03:29] jo-erlend: that's ok for now, that's just because I got you just the uImage [03:29] devilhorns, I think we should go that way, as it makes it easier long-term to have global alert management. [03:29] still missing the modules [03:29] jo-erlend: but does it stops at this fatal errors? [03:29] persia, fair enough :) [03:30] rsalveti, it does. [03:30] jo-erlend: ok, let me get you the kernel modules [03:31] rsalveti, and I get lots of "modules does not exist" in my xorg.log. [03:32] hm, could be another issue [03:32] devilhorns, That said, if you know of some reason why it's better not to use libcanberra, I'd be happy to hear arguments, but based on everything I've heard, it's a sensible direction. [03:32] but can you see something from your X11 session? [03:32] I mean, does it show something at your monitor? [03:32] rsalveti, no. [03:33] one step at a time :-) [03:33] jo-erlend: can you paste me your dmesg? [03:33] yes! I have characters on my screen. That's awesome :) [03:34] rsalveti, http://paste.ubuntu.com/497419 [03:35] hmm... [ 0.000000] Linux version 2.6.35.4+ (rsalveti@evatp) (gcc version 4.4.5 20100824 (prerelease) (Ubuntu/Linaro 4.4.4-9ubuntu2) ) #42 Mon Sep 20 22:15:20 BRT 2010 (Ubuntu 2.6.35-21.31-omap 2.6.35.4) <-- Didn't it say that before too? [03:36] yup, but check the timestamp [03:36] it's now different [03:36] persia, no particular reason comes to mind ... I was just curious if canberra was the "preferred" way to go wrt sounds, or if it was just something the netbook-efl devs dropped in [03:36] actually it isn't. It sais 1/1 2000. [03:36] jo-erlend: hm, with error and etc [03:36] hmm? [03:37] so same dmesg as before [03:37] were you able to login and get the dmesg? [03:37] devilhorns, it's currently used in many flavours (Ubuntu Desktop, Ubuntu UEC live, Edubuntu Desktop, Edubuntu Desktop KDE, Xubuntu Desktop, Mythbuntu Desktop, Ubuntu Netbook), so I think it's safe to say it's well-supported in Ubuntu. [03:37] if not you're probably pasting the older one [03:37] no. I had to eject the card and mount it in my laptop. [03:38] Doesn't seem to be in Kubuntu Desktop or Netbook, but since it's in Edubuntu Destktop KDE, I suspect there's some integration bits in place. [03:38] well, it's the same dmesg [03:38] same kernel [03:38] rsalveti, perhaps I can just remove the logs? [03:38] same timestamp and same errors [03:38] sure [03:38] try generating a new one [03:38] persia, well, support wasn't my concern :) just didn't know if the netbook-efl devs picked it out of the blue or something :) [03:38] right. Is it ok to simply delete them, or must I create a new empty one? [03:39] just delete them [03:39] it should create a new one when booting [03:39] devilhorns, At least everyone else uses it. I can't say much more :) [03:39] persia, ok :) [03:42] persia, was wondering cause gonna be adding sounds back into the new one soon [03:44] Cool! [03:45] rsalveti, http://paste.ubuntu.com/497424 [03:45] jo-erlend: still the old one [03:45] weird [03:46] heh, I deleted all the logs! :) [03:46] but you spoke of a bug earlier.. Perhaps I should try to create a new fat32 partition again? [03:46] haha, not possible, at least the timestamp should be different [03:47] jo-erlend: please [03:47] and remove all your logs again [03:48] persia, btw, new one supports changing icon sizes too :) [03:52] rsalveti, I think I know the problem... :) [03:53] gedit was smart enough to know that it already had the file open, but not smart enough to understand that the file had changed. [03:53] :-) [03:53] rsalveti, http://paste.ubuntu.com/497433 [03:54] OK, now it's different [03:54] yes. What are all those filesystem errors? [03:56] jo-erlend: probably because you're still using the pre-installed image without resizing the disk [03:56] you're only able to do that when using the uInitrd and giving at least one boot [03:57] oh, ok. Does it have any consequences? [03:57] yep, you're going to be able to do much work on it [03:57] :) [03:57] the good thing is that we now have the display fixes [03:57] so I'll submit them and when we get them applied you'll need to change just the x-loader and u-boot, if needed [03:58] yes. It looks to me that the missing /lib/modules is what's causing it to halt. [03:58] probably [03:58] I'm uploading the modules for you [03:58] but for the moment you could try to mount your sd card at your host and get inside with qemu [03:58] devilhorns, careful now, you might make something so nice nobody wants the clutter version :) [03:58] and try to run depmod [03:59] this will create the modules.xxx files that the boot is complaining [03:59] rsalveti, can you be a little more spesific? :) [03:59] or wait until I get my package uploaded, so you can install it by using qemu [03:59] jo-erlend: which ubuntu release are you using at your host? [03:59] if you're using ubuntu :-) [03:59] maverick. [03:59] cool [04:00] so you could get inside your partition with chroot and qemu, to install the needed packages [04:00] like running it at your arm machine [04:00] mount your sd card at your host computer [04:01] then get inside the rootfs partition [04:01] cp /usr/bin/qemu-arm-static usr/bin/ [04:01] mount --bind /dev dev [04:01] mount -t proc proc proc/ [04:01] and then you can just give chroot /media/ [04:01] persia, that's the idea :) [04:01] now you're running an arm environment, and able to give apt-get normally [04:02] then all you need to do is to get my kernel package and give dpkg -i on it [04:02] umount everything, boot your arm board and be happy with it [04:03] One may well have to install qemu-kvm-extras-static to make that procedure work... [04:04] yup, was too lazy to find the package for it :-) [04:05] rsalveti, I'm in an arm chroot with the rootfs from my memorycard. [04:07] ... now what? :) [04:08] jo-erlend: create the correct kernel directory for the kernel I sent you [04:09] mkdir /lib/modules/2.6.35.4+ [04:09] I guess [04:09] then run depmod with correct parameter, one sec [04:11] depmod -a 2.6.35.4+ [04:11] please try it [04:12] uh, how? :) [04:12] at your chroot [04:12] mkdir /lib/modules/2.6.35.4+ [04:12] depmod -a 2.6.35.4+ [04:12] I did that. No response [04:12] that's fine [04:13] ls -l /lib/modules/2.6.35.4+ should show you some files [04:13] now exit your chroot [04:13] umount dev [04:13] umount proc [04:13] and umount the rootfs [04:13] put your card at your board and boot it [04:13] it does. [04:14] you mean I exit my chroot by issuing those commands? [04:15] no, after you get out your chroot [04:15] how do I do that? "exit"? [04:15] yep [04:15] or control + d [04:19] rsalveti, well. Some of the errors have gone, but I'm stuck with one: "mount: unknown filesystem type 'binfmt_misc' [04:20] and that's where it stops. [04:20] hm, ok, so it's really missing some modules [04:20] jo-erlend: http://people.canonical.com/~rsalveti/kernel/linux-image-2.6.35.4+_2.6.35.4+-43_armel.deb [04:20] you can find all kernel modules you need on it [04:21] then I enter a chroot again, download that package and install it? [04:21] jo-erlend: yup [04:22] jo-erlend: but I'm afraid you'll get fs errors [04:22] let's see [04:22] just dpkg -i [04:26] hmm. it seems I don't have networking in the chroot? [04:26] oh. nvm [04:27] you have it, could be a problem with your resolv.conf file [04:30] jo-erlend, You have qemu-kvm-extras-static installed? [04:31] possibly. Why? [04:32] persia: he was able to get inside the chroot before [04:32] so it should be able to get inside it again [04:32] rsalveti, when installing the package inside the chroot, I got _lots_ of "Unsupported ioctl: cmd=0xc020660b" [04:32] jo-erlend: that's normal [04:33] Well, rather, it's a bug, but it doesn't break installing a kernel [04:34] rsalveti: dpkg: error prosessing linux-image-blabla: failed in write on buffer copy for backend dpkg-deb during /lib/modues/2.6.35.4+/kernel/drivers/media/common/tuners/tda18271.ko": no space left on device [04:34] jo-erlend: :-( [04:34] that's the fs error I was afraid of [04:34] this is because your kernel never got the resize [04:35] jo-erlend: so you need to start from beginning [04:35] how much from the beginning? [04:35] dd the daily build [04:35] hm [04:35] oh.. [04:35] probably by copying the uInitrd from the daily image [04:35] and uImage [04:36] here's the problem, you need to at least boot the image using the original uImage and uInitrd once [04:36] it'll just resize it (with some additional things) [04:36] and reboot [04:36] oh. The guide from igeps wiki told me to delete those. [04:37] jo-erlend: yep, the guide is wrong :-( [04:37] well, everything except uImage. [04:37] after the first boot and reboot, you're able to do whatever you need/want with your image [04:37] ok. Is it sufficient to copy the uInitrd back into the boot partition and run it? [04:37] without facing these weird fs errors [04:37] probably [04:38] do I need MLO and u-boot.bin? [04:38] nops [04:39] yours should be fine [04:40] jo-erlend: just make sure you have the right commands to load uInitrd and uImage at your boot.scr or boot.ini [04:40] depends on what you have [04:40] http://paste.ubuntu.com/497451/ [04:40] example from beagle [04:40] fatload mmc 0:1 0x80000000 uImage [04:40] fatload mmc 0:1 0x81600000 uInitrd [04:40] than your boot cmd line [04:40] and: [04:40] bootm 0x80000000 0x81600000 [04:40] with that you should be able to load uImage and uInitrd [04:41] the uInitrd is the responsible for calling jasper, the one responsible for resizing it [04:41] oh, ok. [04:42] jo-erlend: well, need to go now, quite late already [04:42] jo-erlend: please try using uInitrd and let me know what happens [04:43] if not, the recommended step would be to start from the beginning, but without removing the uInitrd file [04:43] will do. [04:43] jo-erlend: just don't give up :-) [04:43] I'm able to help you again tomorrow [04:43] I've seen text! That gives me courage. :) [04:43] jo-erlend: :-) [04:43] thank you very much :) [04:43] jo-erlend: if you're able to test, please update bug 607250 [04:43] Launchpad bug 607250 in linux (Ubuntu) "omapdss: VDDA_DAC regulator on IGEPv2 (affects: 2) (dups: 1) (heat: 24)" [Undecided,Confirmed] https://launchpad.net/bugs/607250 [04:44] once we have a successful test, I'll send to the kernel team [04:44] one more thing... [04:44] the kernel patches, if you're interested: http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-maverick.git;a=shortlog;h=refs/heads/fix-igepv2-display [04:44] sure [04:44] in that fatload directive, you use some numbers. Are they ok to use? [04:44] yup, should be fine [04:46] what about those other lines? [04:46] "fixrtc" should I add that? Should I add the bootm directive? [04:46] the third one should be your own cmd line [04:46] that you were using before [04:46] you could, should cause no harm [04:47] bootm 0x80000000 0x8200000 is just to load from the memory location [04:47] fatload mmc 0:1 0x80000000 uImage means to load uImage from mmc0 partition 1 to memory addr 0x80000000 [04:47] the bootm says that you should now boot from this memory location [04:47] ah, the joys of uboot [04:47] ah. [04:48] Martyn, You have a grub port yet? [04:48] jo-erlend: time to go now, anything else I can do to help? [04:49] I guess not today, but if you're around tomorrow, I'm sure I will have something. :) [04:49] thanks again for your help. [04:50] wow that was a tough ride [04:50] jo-erlend: sure, np! [04:50] see ya [04:50] persia : There will be no grub port. Once we added Jason and Rob to the SStone team, we went for u-boot as the solution [04:50] * rsalveti out for bed [04:50] hours of debbuging [04:50] rsalveti, sleep well. :) [04:50] rlameiro, I got more normal text now! Improvement. :) [04:50] Martyn, Awww.. but... :( [04:50] persia : So we're concentrating on that, and adding what we need to u-boot to make the platform work [04:51] persia : No buts .. it came down to return for the time spent on it .. and grub2 was going to be too much work to be worth it. [04:51] persia : Michael's software bootloader also went by the wayside .. it's always the same story. [04:52] BUT .. we got pxe working .. and that's something [04:52] That's something. [04:52] Now I just have to find another group that's more idealistic than underfunded :) [04:53] lol [04:53] is uboot beeing customized for ubuntu? [04:54] detection routines? [04:59] rlameiro, I believe the plan is to mostly use linaro's uboot, and leave the coordination between the many uboot trees to the linaro project. [04:59] yep [05:00] and eventually probably move to UEFI, but who knows when that will work... [05:00] nice [05:00] We're good at making a distribution, but we're less good at making individual bits of software good for everyone. Some of us work upstream in various ways, but as a team, it's better to focus on integration. [05:00] I never got that linaro heads stuff [05:00] Martyn, UEFI works without a second-stage? [05:00] UEFI works when device tree is finished [05:01] rlameiro, I don't understand linaro "heads" stuff either, but the linaro project does seem to be putting a lot of effort into collaboration between different trees, making it *lots* easier for us to select the right thing when building a general-purpose distribution. [05:01] and yeah .. UEFI is a complete little boot shell [05:01] 'little' [05:01] kinda lilo ? hehe [05:01] So, what was the deal with all the amd64 grub2 stuff this cycle to make it work for UEFI? [05:02] persia : Because I went to LinuxCon:Boston .. my boss won't let me to go LinuxCon Japan :( :( [05:02] I'm a sad panda [05:03] Clearly you shouldn't have attended LC:B :) [05:03] MIssed you last time, but if you come visit when I'm actually on this side of the world, be fun to do something. [05:03] Yeah :) [05:03] Coming to UDS:Orlando? [05:07] That's the current plan. === DanaG1 is now known as DanaG === DanaG1 is now known as DanaG [05:11] Great :) See you there :() [05:11] :) === DanaG1 is now known as DanaG === DanaG1 is now known as DanaG [05:13] oopsie, that was me having two computers with pidgin open. === DanaG1 is now known as DanaG [05:16] DanaG, Thanks for sorting it quickly :) By the way, you might be interested in using smuxi or bip or similar sorts of things if you often want to IRC from multiple computers. [05:17] * GrueMaster uses quasselcore on a server and connects to it from multiple laptops. [05:19] persia: While i am thinking of it. I filed two regression bugs; Bug 644028 & Bug 644037 [05:19] Launchpad bug 644028 in linux-meta-mvl-dove (Ubuntu) "Audio regression on Marvell Dove images (affects: 1) (heat: 8)" [High,New] https://launchpad.net/bugs/644028 [05:19] Launchpad bug 644037 in pulseaudio (Ubuntu) "defaults need adjustment for Dove A0 for audible audio (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/644037 [05:19] GrueMaster, Why is 644037 a pulse bug? [05:19] Surely it's best to fix in ALSA or udev or the kernel. [05:20] It is a duplicate of Bug #451635 [05:20] Launchpad bug 451635 in pulseaudio (Ubuntu Karmic) (and 8 other projects) "defaults need adjustment on dove X0 for audible audio (affects: 1) (heat: 11)" [Undecided,New] https://launchpad.net/bugs/451635 [05:20] That was fixed in Lucid. [05:20] But fixed with a dirty hack, and nobody went back to clean it up, and now we have a regression :( [05:20] So much for getting 10.10 installed on an imac 27" ... display port detection is broken in the current kernel [05:20] I was kind of hoping I could convert this thing to a useful machine :) [05:21] GrueMaster, Grab a kernel guy, and make alsa/udev see the right thing and report the right thing to pulse :) [05:22] A good fix for 644028 might also fix 644037 [05:22] persia: That may be part of the fix needed for the first bug. [05:23] I'll test the Beta image on beagle tomorrow to see if it regressed as well. [05:23] At any rate, wife calls. Must go veg in front of the TV before bed. [05:34] I still have yet to see where you get one of those "dove" boards. [05:34] ddon't bother [05:35] the panda board is as good for development :) [05:35] the Marvell boards were useful stepping stones, but I see the panda board as being a good measuring stick [05:36] I mean, I've never even seen so much as a picture of said "dove" boards... the only things I've seen retail are the old Kirkwood. [05:39] I don't believe there are any retail dove boards. [05:39] I believe the only retail stuff on which Ubuntu is easily available is imx51 or omap3 currently. [05:41] yep [05:42] the Marvell boards I got were direct from the engineering group [05:42] the whole point of the Dove boards is like the Lange boards .. engineering testing and development === amitk-afk is now known as amitk [08:23] morning === amitk is now known as amitk-afk === amitk-afk is now known as amitk [12:00] bah, sigh [12:01] two openoffice build. one linux-linaro and more linux builds in the queue [12:01] * ogra guesses we wont see much from the buildds today [12:04] why two OO.org? [12:05] maverick and a lucid SRU [12:10] maverick is a good thing. This one should build. [12:15] its the same source for both [12:22] is it possible to install ubuntu-arm on very old dell axim x5? [12:22] what CPU is in it ? [12:23] it is not [12:23] mk0: its armv5 [12:23] should be fine with jaunty [12:23] pxa27x iirc [12:23] but nothing newer [12:23] ogra: jaunty works on 64MB ram? [12:23] (userspace at least, kernel and bootloader is up to you) [12:23] I'd recommend installing Debian on an ARMv5 device. [12:24] hrw, Sufficiently stripped, yeah. [12:24] hrw, yes, we offered an NSLU2 image in jaunty [12:24] its super painful, but works ... kind of [12:25] oh shi... too advanced answers [12:25] for me [12:26] ogra: nslu2 can have 256MB ram ;D [12:26] all depends on soldering skills [12:26] we only used the default [12:30] I want to drop my beagleboard to floor and jump on it few times [12:31] You'd end up having to get a new one ... [12:31] persia: I have other C3 here [12:31] but it will not change situation. even worse [12:31] mk0, Short answer: you'd do better to install Debian. Ubuntu support for that device happened once, but isn't continuing. [12:31] both my C3 have usb problem [12:32] but one which I use has expansion header soldered so usb fix was easier [12:32] persia, thanks) will lurk towards deb [12:33] but even there you might need to do a kernel and bootloader setup on your own [12:34] bootloader at least. I believe there to be pxa2xx kernels in Debian [12:37] persia: what? [12:37] pxa2xx kernels in debian :? [12:38] persia: i use pxa270 board [12:38] zumbi, Maybe it was just leftover (unused) config in a kernel source I read once. I haven't looked recently. I'll trust your word over my memory. [12:39] persia: debian arm sadly does not provide pxa2xx support :/ [12:39] persia: i am fighting kernel guys and see if we are lucky to include mv78xxx machines [12:40] It's always a matter of having kernel folk to support stuff. [12:40] but kernel build takes so long in native that it is a blocker for adding more platforms [12:40] Clearly you need more, faster, buildds :) [12:40] well.. now we have them, so we'll see if more platforms are added [12:41] but with the freeze, all development is somehow stalled on bugfixing [12:41] This is a good thing :) [12:42] well, it is good yes, for release (I hate releases :) ) [12:43] btw, are you guys playing on omap4? [12:44] Some folk have dev boards. [12:44] 10.10 on arm require 768MB ram or 512MB is enough? [12:44] zumbi, well, we release images for it :) [12:44] ogra: omap4 seems to be a beast [12:45] hrw, 256M should be enough, 512M is recommended [12:45] 384 is the regular requirement. 256 may work, depending. [12:45] right [12:46] 256M should kind of work [12:46] with -fun :) [12:46] Just don't try to do too many things at once :) [12:46] I need to kill plymouth, ureadahead and then maybe it will finally boot [12:46] +fun starts at 512M and above :) [12:46] hrw, ureadahead is supposed to be fixed in the recent images [12:46] +fun is *supposed* to happen at 384MB. Do the requirements need a bump? Do we need a general bloat reduction push again? [12:47] nah [12:47] +ok starts at 384 [12:47] +fun starts at 512 :) [12:47] Ah. [12:47] ogra: first I need to boot to be able to run apt [12:47] yeah, booting is such a thing ... [12:48] * ogra is really happy that all his ubuntu probs vanished when he started to use the tegra netbook [12:49] ogra: how much it costs? [12:49] 380-400 € [12:49] What do you mean "all ubuntu probs vanished"? You aren't using Ubuntu anymore? [12:49] ogra: too much ;) [12:49] persia, no, i have only android probs now [12:50] heh. Ubuntu problems *exist* but aren't quite as intense. [12:50] nice... bb hang on [12:50] beagle login: hrw [12:50] ogra: bought from where? [12:50] suihkulokki, media markt in germany [12:50] they sell it off the shelf here [12:51] interesting [12:51] but its locked down and runs android ... i managed to unlock it and can run ubuntu chroots just fine for working ... but there is no way to access the bootloader to change the preinstalled os [12:51] did you write up hacking notes somewhere? [12:52] someone did [12:53] suihkulokki: pandaboard is very much near if you want A9 hw [12:53] near in time [12:54] nice... /var/lib/dpkg/status trashed [12:55] suihkulokki, http://tosh-ac100.wetpaint.com/ [12:56] wow, the rooting howto is completely worng :P [12:57] /data is mounted noexec there is no way to run binaries in it ... funny [12:57] i wonder if people test such stuff if they write howtos [12:59] in glibc systems noexec has no meaning iirc === Neko is now known as NekoSchool [13:01] ouch, ac100 needs "rooting"? :D [13:01] damn toshiba :D [13:02] NekoSchool, its android [13:02] ogra: I am sure there will be ways eventually [13:02] yeah sure but there isn't some nice standard bootloader in there like redboot or uboot with a serial console or something and some pads on the board for a serial cable? [13:03] i dont think anyone ever shipped an andriod based device off the shelf with root enabled [13:03] NekoSchool, nope, nothing like that [13:03] its a patches down android fastboot bootloader it seems [13:03] even if you ship a completely locked down software on a device, this isn't a phone.. running ubuntu on it should be a nice feature for those who have the right SD card or something :D [13:03] dcordes, ? [13:04] ogra: do boot your own kernel/initramfs [13:04] dcordes, ways to install ubuntu you mean ? [13:04] ah, likely [13:04] the more people complain to toshiba the more likelier it gets [13:04] DIY [13:04] it seems to use a raw partition for the bootloader stuff [13:05] * ogra made a dd copy from the eMMC [13:05] They don't have to let you boot your own kernel so I think it does not matter how many people will complain. [13:05] first partition only starts at block 33 so there is "free space" before it [13:05] ogra: what's eMMC? Any documentation ? [13:05] a builtin flash like device that exposes itself as MMC [13:05] dcordes, It's the same as MMC, except you can't remove it. [13:06] ok [13:06] i think the e stands for embedded (not sure though) [13:06] ogra: can you provide the dd ? [13:06] not sure if thats legal, so not publically, no [13:07] ok [13:07] Are any system upgrades anounced by toshiba ? [13:10] apparently there is an andriod 2.2 one expected in the next 4-6 weeks [13:10] oh ! [13:10] eMMC describes an architecture comprised of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array (BGA) package. [13:10] It is based upon the industry-standard MMC system specification version 4.1/4.2 and JEDEC BGA packaging standards [13:10] * ogra just found a proper recovey mode by accident ! [13:10] thats from JEDEC informations [13:11] hrw: thanks [13:11] AC100 looks real nice. Checking some videos [13:12] hrw: hey! i got that jedec document :P [13:13] ogra, You mean that next time you brick it, you can recover without help? [13:13] persia, not sure, depends if the bootloader is in two parts :) [13:13] * persia continues to hold off on a purchase decision [13:13] * ogra doesnt know where that recovery mode lives ... first or second stage [13:14] and i wont play with it right now [13:14] * ogra has work stuff to do :) [13:14] Of course :) [13:16] ogra: Did you think about possibility to boot new kernel from within running system ? [13:17] dcordes, that would require kexec support in the running kernel [13:17] dcordes, Most kernels provide a userspace environment that prohibits that. [13:18] grep -i kexec ac100_defconfig [13:19] CONFIG_KEXEC=y [13:20] ogra: j/k :> [13:21] ogra: you have a 3g device ? [13:21] yes, but no sim [13:24] ogra: I have a hard time finding the ac100 kernel source code. Do you have a link ? [13:24] dcordes, i dont think its public, toshiba will liekly ship it to you if you give them the product id [13:25] * ogra goes for some late lunch [13:26] That might apply to the MIT licensed userspace portions.. [13:27] I want to see the ac100 kernel sources and I don't have the device [13:30] morning [13:31] rsalveti, good morning! :) [13:31] jo-erlend: hey! [13:32] rsalveti, I re-dd [13:32] dcordes, Just convince ogra to make a kernel source request, and share it with you :) [13:32] uh.. I re-dd'd my memorycard and booted it with uInitrd. It did change the partitions, but now I'm stuck. Where do I go from here? [13:33] jo-erlend: cool, you just need to boot it once [13:34] to get the resize, then mount it at your host, and use chroot to install my kernel package [13:34] persia: I don't want to have to convince anybody to anything when all I want is to read kernel source [13:34] that is GPL licensed [13:34] Why? [13:34] rsalveti, ah. I just replaced the uImage with the one you sent me. That didn't work. [13:34] There's no requirement for GPL code to be public. [13:35] jo-erlend: it'll break the same way as before, because of missing modules [13:35] There exist licenses that require code to be public, but most folk don't like them, and they fail the desert-island-test of freedom. [13:35] (because if you're on a desert island with no connectivity, you'd be restricted from modifying the code, since you couldn't make the modifications public) [13:36] GPL only7 requires that you give the source to a user you sold the binary to [13:36] ok [13:36] no requirement to make it public at all [13:36] at least GPL v2 [13:37] rsalveti, I still have two partitions, but now the second partition contains /boot and has some files in it. Is that the way it's supposed to be? [13:37] i think it changed a bit for v3 [13:37] ogra, No, GPL requires you give the source to anyone who has your source or binaries, regardless of whether they use it or whether they paid for it. [13:37] jo-erlend: yep, that's fine [13:37] and there's still no public requirement for GPLv3 [13:37] jo-erlend: because u-boot uses the files from the first partition, so it just ignores the /boot [13:37] how would one get the binaries without buying the device ? [13:37] thats a moot point [13:38] jo-erlend: you should have vmlinuz and initrd.img from your kernel [13:38] ogra, Maybe one got a developer sample. Maybe one downloaded a recovery image. Maybe someone posted a copy of the kernel on the internet. Lots of ways. [13:38] ogra: 'CONFIG_IKCONFIG_PROC=y' ? [13:38] ogra: you have /proc/config.gz file ? [13:39] sure [13:39] can you pastebin ? [13:40] persia: ogra mentioned they are planning an upgrade to new android version. as android makes many depencies on kernel level this will likely involve new kernel binary [13:41] persia: the question is if it will be some OTR thing or also password restricted for the device buyers [13:41] dcordes, So, when that happens, if it's an open download, download that binary. Once you have it, request source. [13:41] Could be either way. Doesn't really matter. the kernel source can be made available as soon as someone posts it. there's no restriction on posting except motivation of folks. [13:41] Hence the value of convincing folk to do stuff :) [13:42] Actually I don't like the fact such things must be discussed.. I am just recovering of the DELL Streak gpl violation thing [13:42] persia: so a 'leaked' binary can also be jurisdical base to enforce gpl ? [13:43] * persia refuses to provide a legal opinion [13:43] That said, it probably depends on how the leak happened, etc. Quite possibly. [13:43] the GPL requires source to be made available to anyone to whom a binary is made available. [13:44] But you'd have to make a GPL claim against the leaker, which may have repurcussions, rather than against the original patch authors whose code was included in the leak. [13:45] So if the leaker was a friend, you might not want to do that. If the leaker was a whistleblowing organisation, you don't help their cause by making claims against them. [13:45] GPL only gives you the right to request source code from the same folk that provided the binary. [13:46] yep [13:46] how does nokia handle it with n900 and friends ? [13:46] with a written offer [13:46] the whole source-for-device-owner-only thing is new to me [13:46] I believe they offer code for allthe GPL stuff. [13:46] with good lawyers [13:46] they offer in the ftp servers [13:46] easier way [13:46] rsalveti, I do. They point to vmlinuz-2.6.35-19-omap [13:46] instead of waiting requests from everybody [13:47] dcordes, It's not source-for-device-owner-only! It's that the source only needs to be made available to folks that receive the binaries. Most large projects end up with a public repo, but that's just a matter of convenience. [13:47] jo-erlend: sure, the default kernel [13:47] jo-erlend: now just install mine with dpkg -i [13:47] dcordes, once any owner receives the source, they are free to post to the internet anywhere they like. [13:47] you should get new vmlinuz and initrd.img [13:47] i think toshiba plans that too, there is a URL in the license agreement [13:47] then you generate your own uImage and uInitrd from it [13:47] (which doesnt work yet) [13:48] persia: yeah that's what I mean. Matter of convenience. I haven't seen that toshiba behaviour before [13:48] * persia has often had such limits in contracts, because the client didn't want their code distributed, and I wanted to write GPL code. [13:49] ogra: can you pastebin the /proc/config.gz ? [13:49] dcordes, toshiba hasnt provided android devices before [13:50] persia: that's interesting. I once got a contract offering from people who wanted to make shanzai android phone.. it was same story [13:51] dcordes, Not uncommon: lots of companies want to time their releases. Doesn't make the code less GPL when users get it. [13:51] in case of HTC you also see such delays but it's always in an acceptable frame [13:52] you need to sell early publicing of code as "free QA review from community" [13:52] the ac100 got on the market 10 dys ago or so [13:52] * ogra_cmpc wouldnt see that as inacceptable if it happens at some point soon [13:53] rsalveti, how do I do that? [13:53] suihkulokki, I think that doing so requires a bit more stature than being able to require GPL which requires more than random coding. [13:53] jo-erlend: what exactly? generate uImage and uInitrd? [13:53] yes [13:53] with mkimage [13:53] ogra_cmpc: if you understood it, I did not mean to compare to toshiba there [13:53] persia: well yes of course [13:54] rsalveti, little more details please? := [13:54] mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs -d initrd.img uInitrd [13:54] mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d vmlinuz uImage [13:54] Here that was ridiculous story http://laforge.gnumonks.org/weblog/2010/09/13/#20100913-dell_streak_sources [13:54] and it's not over yet. [13:54] jo-erlend: install package uboot-mkimage [13:55] rsalveti, I have. I used it to create the boot.ini file. [13:55] after installing my package, run these commands with the new initrd.img and vmlinuz [13:55] then you'll have a new uInitrd and uImage [13:55] they'll be placed in rootfs/boot? [13:55] copy them to the first partition, recreating it first [13:56] jo-erlend: after installing the package you can find them at rootfs/boot, but after generating the uI* files you need to copy them to the first partition [13:56] right. [14:00] rsalveti, I got the same error today when installing the package, although on a different file. No space left on device. [14:00] jo-erlend: this is weird, if you got the resize working, you should have enough space [14:01] how much space left do you have at your sd card? [14:01] GrueMaster, how was the oo.o testing ? [14:01] (doko just asked) [14:01] rsalveti, well. Nautilus shows it as a 7.9GB volume, but from within the chroot, df -h displays it as 2.0GB. [14:01] I didn't get to it. Swamped with alsa testing. [14:01] GrueMaster, well [14:02] the packages are in the archive now [14:02] hm, so it was probably not resized correctly, werid [14:02] ok [14:02] I had also downloaded them to my server. Just never got a chance. [14:02] jo-erlend: did you boot it once with the original uImage and uInitrd, right? [14:02] yes [14:03] jo-erlend: did you see if you got the reboot? or how long did you wait before turning the device off? [14:03] rsalveti, I might have made a mistake along the way. It was 6am when I tried the last time, so I was a bit sleepy. I think I'll start over. [14:03] you should wait at least 5 minutes [14:03] oh, ok. [14:03] I don't think I waited that long. [14:03] :-) === kmargar is now known as markos_ [14:15] rsalveti, should I use the uImage you sent me for the first boot? [14:16] jo-erlend: use the original one, with original uInitrd [14:16] to be sure we don't face any issues [14:16] just boot and wait for 5,8 minutes [14:16] The original initrd has some extra code to resize the filesystem, etc. [14:16] persia: that's why we're doing this [14:53] does anyone have a beagleboard up and running who can quickly do "cat /proc/asound/cards" and report me the output? [14:53] rsalveti, this is very strange. I booted the board with the original uImage and uInitrd and left it running for 15-20 minutes. When I mounted it on my laptop, Nautilus reports it as a 7.9GB filesystem, but also reports that is has only 298,7MB of free space. [14:54] jo-erlend: sigh [14:54] jo-erlend: for some reason the resize is not working, I believe [14:54] can I do it manually? [14:55] probably [14:55] let me try to find the command [14:57] berco, http://paste.ubuntu.com/497723/ [14:57] persia, thanks [14:58] persia, I think we are missing the equivalent of that twl4030 field on pandaboard [14:58] this is why my alsa/SDP4030.conf file doesn't get read [14:58] jo-erlend: http://bazaar.launchpad.net/~ogra/jasper-initramfs/trunk/annotate/head:/scripts/local-premount/jasper_growroot#L82 [14:58] quite a few steps [14:59] resize_partitions to change the disk size [14:59] berco, What does the pandaboard report? [15:00] then e2fsck and resize2fs [15:01] rsalveti, the disk size seems to have changed. [15:01] fdisk should show you [15:01] but if you get it right at nautilus, it's probably changed [15:01] persia, pandaboard reports this http://paste.ubuntu.com/497729/ [15:02] Yeah, that's missing the machine configuration entirely. [15:02] persia: when I use iwatch I can see the file is not accessed whereas when I do the test on my PC, the .conf is accessed [15:04] rsalveti, palimpsest shows /dev/sdb2 as a 7.9GB Ext3 filesystem+ [15:05] jo-erlend, what about df -h [15:05] it shows 2.0GB. [15:05] right [15:05] rsalveti: in the meeting you talked about "a bug for the kernel and another for u-boot", it this related to sound ? [15:05] mpoirier: nops, LED [15:05] ok. [15:05] mpoirier, no, to new panda HW [15:05] oh, that one [15:05] ignore me :P [15:06] ogra: I can do that ! [15:06] mpoirier: bug 626795 [15:06] Launchpad bug 626795 in linux-ti-omap4 (Ubuntu) "Missing LED support for Pandaboard (affects: 1) (heat: 8)" [Low,Fix released] https://launchpad.net/bugs/626795 [15:06] Just for clarity. [15:06] mpoirier, Do you have any recommendations for berco? He's working on a userspace workaround in case you don't find a kernelspace fix, but the kernel isn't reporting enough to dynamically load the right configuration :( [15:06] fdisk sais it's a 8GB disk... [15:07] jo-erlend, fdisk and the gnome tool report partition sizes [15:07] jo-erlend, df shows filesystem size [15:07] so no resize [15:07] persia: berco: I'm just getting started - give me a few days and I'll have an opinion. [15:07] well, resize_partitions has run [15:07] but not resize2fs [15:07] yup [15:07] ah. Then palimpsest was confusing, since it sais "7.9GB ext3" [15:08] weird, but without console and display working, no much to say, unless checking jasper logs [15:15] rsalveti, I won't have to manually create the /lib/modules directory like I did yesterday? [15:16] jo-erlend: nops, because now you installed by kernel package [15:16] *my [15:16] or, you will install it when you're able to resize it [15:20] yes, it's being installed. [15:21] GrueMaster, hmm, do you see update-manager popping up automatically on the images ? [15:21] * ogra juts ran an apt-get update, that should trigger u-m i think [15:21] I haven't looked. Had been focusing on a lot of other issues lately. [15:22] will look on omap4 now. [15:22] jo-erlend: so, did you resize it by hand? [15:25] ogra: apt-get update usually will trigger it within a few minutes. Will let you know if I see any activity. [15:26] I know it works on Lucid. It shows up at least weekly on my babbage. [15:26] k [15:27] no hurry, was just a question out of interest [15:28] * ogra takes a break [15:35] ogra: The "Install OMAP4 addons" icon is in "Other" on 20100920, but the cmdline fails. [15:38] rsalveti, does it matter if I create uInitrd and uImage from the chroot or not? [15:38] jo-erlend: nops [15:38] rsalveti, I resized by hand, yes. [15:38] cool [15:38] so you should now have enough space to play with it later :-) [15:38] yes, and the kernel installed properly. :) [15:39] nice :-) === hrw is now known as hrw|gone [15:40] GrueMaster, yeah, its partially fixed in 21.1 [15:40] ok. [15:40] but needs a sw-center fix first [15:40] which is in the tree but wasnt uploaded [15:41] rsalveti, I should use initrd.img-2.6.35.4+? [15:41] * ogra_ac wishes he could find an IRC client for android with a lag meter [15:41] Just so you know, I really have a hard time testing dailys and apps and special requests on a daily basis. [15:41] I'm getting overwhelmed. [15:42] why is that ? because your boards are busy doing other stuff ? [15:42] Boards are slow, and some of the tests can take hours. [15:42] well, omap4 should be rather fine for quick tests [15:43] i agee for beagle and dove [15:43] jo-erlend: yep [15:43] Even just running checkbox with only known supported tests can take a day. [15:43] sorry, seems my notification system is not working properly [15:43] ogra, An 8-way 5Ghz 32Gb system would be slow for some tests. [15:44] sigh [15:44] This is part of why I haven't jumped on open office yet. Install alone will take 20 minutes. [15:44] ogra_ac: what happens with your client? [15:44] * ogra_ac pokes android in the eye [15:45] client is fine, the wifi is unstable after some time [15:45] ralink NIC [15:45] with binary driver it seems [15:46] hm, ok [15:46] i have to connect to teh Ap with teh worst signal to make it work at all [15:46] might be my local setup or some channel interference between the tree APs i have [15:47] seems the card is more fragile than my others [15:47] the annoying part is that i cant find a client that shows me the lag so i dont even notice i'm disconnected [15:51] ogra: hi! i have a question for you... [15:51] ndec, shoot [15:51] ogra: i want to mount the ext3 partition from the .img in qemu on my laptop... what is the magic command line? [15:51] ogra: qemu arm i mean [15:52] i guuess you need to loop mount it, then use /dev/loop* for aemu [15:52] *qemu [15:52] rsalveti, I have graphics! Welcome to Ubuntu :) [15:52] for the -hda option [15:52] ndec: First, run "file " to find out the partition info. Then run "sudo mount -o loop,offset=$((512*))" [15:55] ogra: GrueMaster: thanks. I will try this. I didn't realize I could a mount point to -hda, i was looking to a way to pass the offset to qemu. [15:55] ogra_ac: Looks like update-notifier is not working at all. I also tried it on my netbook running maverick. [15:55] bah [15:55] update-manager works though, i just did an update [15:55] anything in .xsession-errors ? [15:57] probably the behavior changed and we just dont know [15:58] jo-erlend: nice :-) [15:58] (the default i mean) [16:01] ogra_ac: I'm not seeing anything since it's startup note. [16:01] k [16:01] * ogra_ac will ask mvo in #ubuntu-devel if there are deliberate changes [16:03] jo-erlend: so it did fixed, can you please then update the bug report? [16:07] GrueMaster, update-notifier --debug-update seems to be the magic to find out whats wrong [16:08] Looks like the update interval is set ot 7 days in gconf. [16:08] yes, thats normal [16:08] was like that in lucid too [16:08] (and karmic) [16:08] Ok, so... [16:09] its just the cron timer, but u-n should run in the session too and pick up changes if you run apt-get update [16:10] It also says "/usr/lib/update-notifier/apt-check returned 38 (security: 0)" [16:10] that sounds right, weird that it doesnt pop up [16:10] 38 normal packages, 0 security updates [16:11] Yes, that sounds accurate since I ran apt-get update before restarting update-notifier. [16:11] i would think we miss something on arm in teh efl session, but if you see it too on x86 ... === bjf[afk] is now known as bjf [16:14] Just restarted on x86-64 desktop (my netbook). apt-check returns 12 updates (0 security). No notification there either. [16:15] * GrueMaster grumbles and files yet another bug that should have been picked up elsewhere. [16:16] gruemaster ... why elsewhere ? [16:17] If it exists on x86, it should have been tested & reported there. [16:17] well, its a bug ... we are just the lucky ones having teh idea to test it :) === ogra_ac2 is now known as ogra_ac [16:22] rsalveti, I will. However, I see no signs of networking, either cabled or wireless. [16:24] jo-erlend: hm, then need first to find the chip responsible for networking [16:26] ogra_ac: Bug 644459 filed. [16:26] Launchpad bug 644459 in update-notifier (Ubuntu) "update-notifier not reporting updates available (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/644459 [16:27] rsalveti, and I get a very low resolution, and I can't change it in System > Preferences > Monitors. All the controls are deactivated. [16:27] GrueMaster, thanks [16:27] jo-erlend: you can't, you need to specify the correct one by giving it to the omapfb parameter [16:28] oh. [16:29] argh, seems I'm getting random temperatures report from my acpi [16:29] and sometimes my kernel decides to halt to protect me [16:29] but it's not hot, and I'm tracing the temperature, weird [16:29] must be a bios issue... [16:30] rsalveti, which omapfb mode should I use for 1920x1080? [16:31] jo-erlend: nops, omap 3 doesn't support it [16:31] hmm? [16:32] it's supposed to be able to use much higher resolutions than that [16:33] at 1bit depth ? [16:33] 1280x1024@50 or 1280x720@60 I guess [16:33] yeah [16:34] they say it supports up to 2048x2048. [16:34] ogra_ac, who do I ping about build machine weirdness [16:34] you could get more than that, but need to adjust the timings and etc [16:34] jcrigby, lamont [16:34] jo-erlend: hm, if igepv2 is the same chip we have for beagle, probably not [16:34] jcrigby, whats wrong ? [16:34] the pixel clock can't get that higher [16:35] jo-erlend: using 16bit [16:35] ogra_ac, we are waiting for a kernel build. It starts up building, runs for a couple minutes then goes idle. Seems to keep bouncing between hubbard and hawthorn [16:35] weird [16:35] I pinged lamont on #is but he is away [16:36] well, he is the master of arm buildds and knows the queue software [16:36] not sure whom to ping else on such an issue [16:36] ok, thanks === NekoSchool is now known as Neko [16:39] rsalveti, ok. What do I use to get 1280x720? [16:39] jo-erlend: vram=12M omapfb.mode=dvi:1280x720MR-16@60 [16:40] thanks. === XorA is now known as XorA|gone [16:42] ogra_ac: Stop using my name in vain - jerk [16:42] ;) [16:44] * ogra_ac thinks lag meter is a valid device though [16:45] rsalveti, hmm. The bootpartition is suddenly empty. [16:45] * lag is |-..........................| [16:45] jo-erlend: ouch, shouldn't be [16:45] the boot fs, I mean. [16:45] * lag is |-----......................| [16:45] * lag is |---------..................| [16:45] * lag is |-------------..............| [16:45] * lag is |-----------------..........| [16:45] heh [16:45] * lag is |---------------------......| [16:45] :D [16:46] how is asia ? [16:46] Hot and sticky [16:46] heh, nothing new then [16:46] Have you been here? [16:46] only once on my flight to the second UDS [16:47] i had a smoke break in singapore [16:49] lag, btw, ac 100 rooted :) [16:49] Where was the second UDS? [16:49] and i bricked one already [16:49] Well done [16:49] And not so well done [16:49] that was in sydney [16:49] How did you do it? [16:49] Cold card? [16:49] well, got an immediate replacement at the shop [16:49] Wow - when's the next Aus UDS? [16:49] no, more embarrasing [16:49] Go on? [16:50] i accidnetially removed /bin/sh [16:50] HA [16:50] Isn't it just a simlink? [16:50] androids init calls shell scripts [16:50] yes [16:50] So? [16:50] i wanted to link it to busybox [16:50] So do it [16:50] but messed it up [16:51] it didnt boot anymore [16:51] no way to access it [16:51] Oh, I see [16:51] That was the first one? [16:51] What about the new one? [16:51] so i carried it back to the shop "doesnt boot !!" [16:51] they just handed me a new one [16:51] without words [16:52] the new one is rooted and i run an ubuntu chroot on SD now [16:52] dont want to brick it again so i wait until someone else figures out teh bootloader [16:52] So, how did you root it? [16:52] Odd that they make it impossible to recover. [16:52] the chroot is fine for compiling etc [16:53] there is a tool called rageagainstthecage that uses a kernel exploit by opening endless amounts of file descriptors [16:53] works quite well [16:53] you run it, the next shell you open is a rootshell [16:54] then you can make busybox suid root and use the busybox su command in the future [16:54] GrueMaster, it apparently has a recovery mode i discovered today [16:54] but its kind of a blind flight [16:55] heh [16:55] and requires a specisl nvflash to access the device [16:55] What did you expect, a bios prompt & boot menu? [16:55] which isnt in teh tegr4linux tools [16:55] i'd lobe to have USB serial, yeah [16:55] *love [16:55] What bootloader are they running? [16:55] fastboot i think [16:56] its android after all [16:56] the normal recovery mode can only reset to factory or install update.zip [16:56] nothing more [16:56] btw: linaro call in 3 minutes. [16:56] and update.zip requires a toshiba kesy [16:57] oh, thanks i forgot about it [16:57] as usual [16:57] * ogra_ac goes upstairs [16:59] bug 642117 [16:59] Launchpad bug 642117 in pencil (Ubuntu) (and 4 other projects) "[armel] QFloat / double / float confusion (affects: 1) (heat: 8)" [Medium,Confirmed] https://launchpad.net/bugs/642117 [17:00] now this is much better: http://www.pastebin.ca/1945897 [17:00] tho have to bring the Res down still [17:02] devilhorns, WOW! [17:03] ogra, hmm ? [17:03] awesome numbers [17:03] :) [17:03] getting there [17:03] still a bit more work todo ... want to trim that Res down some more [17:03] ideally I'd like to get to <= 10m [17:04] well, we still run half of gnome ... even these values are awesome [17:05] but already trimmed roughly 10,000 from the Virt, and 1m from the shared [17:05] ogra, half of gnome ? why ? ... wrt this new one, the only thing that will need to be running is a "window manager" to draw borders, handle minimize, etc, etc [17:06] devilhorns, we need to run the indicator applets and all the other ubuntu stuff [17:06] everything that hooks into the system needs to work [17:07] and all the old things are turned into the new indicator things === amitk is now known as amitk-afk [17:09] (volume control, network management, time, app indicators etc) [17:10] ahh yea, will still have to run the gnome-panel [17:10] not much I can do about that tho :/ [17:27] ogra: not arm related problem... but I am trying to upgrade my laptop to maverick. i am running a custom lucid (i am running maverick lts backport kernel + a maverick thunderdird), when I try to upgrade the tool refuses to continue with 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.'. is it safe to replace lucid by maverick in my source.list and run dist-upgrade? or is the upgrade tool doing more than [17:28] its doing more [17:28] you should talk to mvo in #ubuntu-devel, he maintains the upgrade tools [17:29] he will surely be intrested in your situation since he loves to cover all corner cases for upgrading [17:50] guys any clue where the Applications Places System menu is defined in gnome or xfce or whatever config? [17:50] we have a button size problem here and I'd like to go about hacking in a fix but it seems to be automagically created [17:52] Neko: What are you referring to? [17:53] Looks like an Ubuntu Desktop issue. [17:53] (not armel). [17:54] yeah, likely a question for #ubuntu-desktop [17:54] http://launchpadlibrarian.net/55758568/screenshot.png [17:54] like that [17:54] it happens on GNOME too just so you know, but some people don't see it [17:55] Interesting. I'm not seeing it on my netbook, and it is running Maverick amd64. [17:56] But you might want to bring it up in #ubuntu-desktop. They could probably help more on this. [17:56] right [17:56] I just did and they said they are in a meeting [17:57] yeah, they have a silly policy to hold their meetings in their channel instead of using #ubuntu-meeting like all other teams [17:57] * ogra got trapped by that several times already [18:05] oh, sweet, seems someone found acces to the ac100 bootloader [18:11] ogra, sweet [18:12] no way to replace kernel etc yet, but they got access ... so linux is just a step away [18:12] * ogra_ac got careful with his, i dont want to have to replace it again so i'll wait for someone else to figure it out [18:12] Yep very nice [18:13] ogra_ac: ac100? [18:13] prpplague, yeah, toshiba ac100 ... tegra2 based [18:14] ahh [18:14] sadly it comes with locked down android preinstalled [18:14] but i rooted mine and use an ubuntu chroot for testbuilding packages for omap already ;) [18:15] panda is better though ... but less portable [18:16] indeed [18:16] ogra_ac: hopefully we can remedy the portable portion soon [18:17] yeah, a nice light netbook based on panda would be awesome [18:19] (and indeed with ubuntu preinstalled) [18:19] ;) [18:25] some stable wlan would be cool though [18:25] * ogra_ac sighs about teh ralink adapter [18:33] Hi, how can I copy the image ubuntu-4.10-server-armel omap.img for SDcard through the windows? [18:35] ubuntu-4.10? [18:37] I can not mount the SDcard from Linux, I need to know the exact modules. [18:37] or [18:37] or [18:38] learn how to copy the image through the windows [18:38] prpplague: I hadn't had a chance to test it before now, but panda ES2 works on my hdmi switch now. Way cool. I might even be able to reduce monitor count back to 5 or 6. [18:38] hehe [18:38] GrueMaster: yea robclark and i spent some time testing [18:39] okay here's a question a bit generic but relevant to arm all the same [18:39] how do I magically invoke the thing that makes an initrd for me [18:39] seems if I installed a kernel package it'd do it for me but I don't have one yet [18:39] and I need it [18:39] update-initramfs I believe. [18:41] prpplague: Thanks a lot for your efforts. It really does help me a lot. [18:41] :) [18:42] Uh, oh. May have spoken too soon. It just came up in X for oem-config. Looks aweful on my 1440x900 monitor. [18:42] Will reboot. switch had lost focus for a bit. [18:42] doh [18:43] splash looks ok. [18:43] GrueMaster, with no arguments or so? [18:43] just use teh right glasses :P [18:43] prpplague: Ok, non-issue. [18:44] ogra_ac: I only have one pair. [18:44] ah, thats the prob then :) [18:45] Neko: There are only a few parameters. use update-initramfs -h to list. [18:45] for initial creation you want -c and -k [18:47] Now I can effectively test both es2 boards in parallel. (as if I didn't have enough to do). :P [18:47] and in theory it just copies a bunch of stuff from the modules directory into a ramfs plus some userspace stuff? [18:47] so I can create a ramfs for another system as long as I have the modules around (and it's set to "most" or "all" or something?) [18:49] hrm [18:52] Neko, no, initramfs-tools provides a lot of files in /usr/share/initramfs-tools [18:52] and every package can put scripts or hooks in there [18:52] they all end up in the initramfs [18:54] Hi again [18:54] ogra_ac: looked at some more ac100 stuff and the device is really nice. What is the canonical attitude towards adding images for additional machines ? [18:54] there is none [18:55] ogra_ac: So if you would be up to adding ac100 images you could just put them ? [18:55] i wouldnt [18:55] .. I just want to know if I can generate an initramfs without booting that particular system [18:55] I mean all the stuff for an exactly the same userspace should basically be common right? [18:56] except the modules? [18:56] and I specify which one it trawls with -k [18:56] dcordes, such situations were the reason why i wrote rootstock [18:56] Neko, just chroot into your SD card and run update-initramfs ether [18:56] *there [18:57] then you can be sure all scripts and hokks needed by installed packages are in your initrd [18:58] yes but imagine I am in rootstock and I have a bunch of kernel files there extracted somehow, and I run update-initramfs is it going to work [18:58] considering this userspace will work on 20 different systems if I only put the right modules in place :D [18:58] armv7 is armv7 at the end of the day and there are no board-specific stuff required [18:58] except the modules [18:59] i think rcn-ee once added an option for rolling initramfses inside rootstock [18:59] Neko: Do you have an armv7 that you can use to modify SD cards on the fly? That would be easiest. [18:59] there might be no HW specific suff, but system specific stuff [19:00] yeah I do [19:00] GrueMaster chroot under x86 would be even easier [19:00] I can boot the fs on my efikamx [19:00] thats why we have qemu-arm-static [19:00] but I want to generate the one for the netbook without having to boot it on the netbook too [19:00] then I can work out how to do it in a chroot on my x86_64 box [19:01] ogra_ac: I was thinking of something more stable. Like a babbage or something. [19:01] apt-get install qemu-arm-static .... mount SD ... copy the qemu-arm-static binary into SD [19:01] chroot /sd-mountpoint [19:01] thats it [19:02] ogra_ac: Thats assuming you are running maverick, which isn't fully stable yet. Otherwise you get an older version of qemu. [19:02] * ogra_cmpc gibes up on 6teh ac100 wlan [19:03] GrueMaster, no, we have it since karmic [19:03] works fine without any probs [19:03] and a lot faster than natively [19:03] and the static chroot part was always stable [19:03] apart from running mono [19:03] mono is another beast entirely. [19:03] which is why we dont use it for image builds [19:04] update-initramfs is just a script [19:04] using the chroot method your scripts run at host speed [19:04] no offense but the desktop on ubuntu is a horrible, horrible mess [19:05] compiling runs at qemu speed though... thats why we dont use the chroot method for compiling either [19:05] Neko, ? why [19:06] I have deep disdain for any system that has to dereference 20 different things to finally get down to a default, and then find that it is called "/usr/share/backgrounds/warty-final-ubuntu.png" [19:06] lol [19:06] thats historically based [19:06] why didn't they just make it called default-backdrop.png [19:06] file a bug [19:07] i think nobody ever cared [19:07] oh god I can't be bothered, nobody fixes this stuff. By the time it gets looked at, it'll be WONTFIX and someone will have posted "does this still happen in Narwhal?" [19:07] well, you are free to use whatever value for teh gconf key anyway in a custom image [19:08] what I can't find is what is the canonical (pun intended) place to set that gconf key and how on earth I do it without dicking around as the "gdm" user in a logged in system [19:08] so just call it ... umm ... default-backdrop.png for example :) [19:09] you do it as all system wide gconf keys under /usr/share/gconf/default [19:09] the basic idea is that I can change something in a chroot or just in /mnt/usr/share/gconf or something and the system will be fine when it boots [19:09] you can [19:09] and that script is how I do it? [19:09] thats how we customize images [19:09] but that is only run when update-gconf-defaults is run [19:10] I can't run that I can "only" edit text files [19:10] no, it needs to generate the xml [19:10] you could probably do that too by hand indeed [19:10] so if I edit that, where do I edit the xml? [19:10] to match and so that it works first time and then forever after? :D [19:11] is it possible to enable on screen keyboard in oem-config via configuration ? I am looking for a workaround to bug 626055 as it seems it is a 'wontfix' [19:11] Launchpad bug 626055 in ubiquity (Ubuntu) "oem-config: make on-screen keyboard available (affects: 1) (heat: 159)" [Low,New] https://launchpad.net/bugs/626055 [19:11] read rthe gconf source ... no idea [19:11] ughhhhh [19:11] or do it properly [19:11] and roll a package [19:11] I give up for now we'll just ship with the horrible placeholder backdrop :D [19:11] that carries your defaults [19:13] GrueMaster: ping.. can you help with the above ? [19:14] dcordes: Not really at this time. I would have to learn how oem-config works, and I am really only a QA guy. [19:17] Ok thanks anyway [19:19] ogra, rsalveti [19:19] what is this line for in rootstock? [19:19] rm /usr/lib/ubiquity/plugins/ubi-tasks.py* [19:20] Neko: ogra_ac should know it [19:24] potentially it's the bit that sorta goes "which desktop do you want, dude?" [19:24] which is kinda pointless then [19:24] but then again so is partition management and suchlike [19:24] it disables tasksel in oem-config [19:24] because of? [19:24] a bug? [19:24] no [19:25] because you dont want to run tasksel if you already provided your tasks at buildtime [19:25] oem-config-prepare does not such thing so I would assume that it lets it stay in by default everywhere except a rootstock [19:25] other images use preseed files [19:25] so tasksel isnt run [19:26] ok [19:26] it might not even be in teh maverick oem-config anymore [19:27] since ubiquity was nearly completely rewritten [19:27] that explains why it never f**king works :D [19:28] it does [19:28] in lucid and karmic [19:29] regardless of what I do, if I run oem-config-prepare or just manually touch that /var/lib/oem-config/run thing.. [19:29] all I get is back to the gdm login prompt [19:29] you shoudnt run -prepare [19:29] just use teh touch [19:30] all -prepare does is touch, rm -f persistent net rule, pop up a zenity dialog unless you said quiet [19:30] iirc it also creates a user [19:30] and remove the oem-config-prepare-gtk.desktop from /usr/share/applications iirc [19:30] no not here [19:30] ah, then thats the bit that runs during teh live env [19:31] -prepare is in two parts iirc [19:31] just dont use it [19:31] touching teh file after creating teh dir should be just fine [19:31] sigh, it doesn't :( [19:31] well, works on our aily images [19:31] it never runs. I have no initramfs but then I don't see how that makes any difference at all [19:31] *daily [19:32] the file is not in the ramfs, and what is.. is just shit like cryptsetup [19:32] udev and dbus .... etc etc [19:32] if you run rootstock that's not in the system anyway [19:32] udev is the thing that runs it? [19:32] right, rootstock never gets you the same as an install [19:32] no [19:32] udev is in iniramfs [19:33] but they're also in the rootfs so udev and dbus don't matter then [19:34] friggin' thing it's supposed to start this upstart job but it's never run [19:35] gdm runs before it [19:35] so since gdm is running.. it seems not to run since the display manager is taken [19:35] ubuntu hate++ [19:36] * ogra_ac gives up ... its no fun to help you if you offed all teh software we work on [19:36] offed? === JaMa is now known as JaMa|AFK [19:38] it's no fun to work on this because everything is undocumented and somehow some internal canonical secret that doesn't exist on any other linux distribution.. all I can say is I am only glad this isn't SuSE because I would have ripped my eyes out before working on YaST plugins to do this :D [19:41] Neko: Unfortunately, complaining and ranting doesn't help. While ogra_ac has been trying to help, it is hard to work through all the rants. And it keeps others from helping or getting help as well. If you know anything about development cycles, you'd know that 30% is spent on development and 70% is spent on documentation. We simply can't afford that 70% at the moment. [19:42] If you would like to help, the wiki is open for adding documentation. Launchpad is open fir filing bugs. [19:42] And we would certainly welcome the assistance. [19:42] and it's not a internal canonical secrect [19:43] I have a good idea oem services charges for the stuff we're trying to do here and I know what you get at the end is a frozen, no security updates repository, with still no documentation for the money paid... I'm not sure what you mean by "afford" here [19:43] Well, we are not oem services, for one. [19:44] I don't see what me adding to the wiki solves. I don't know what I am doing, or where I am looking, which is why I ask in here.. if I knew already why would I be looking for support? If I did know you can be sure I'd put it on a wiki or a blog somewhere [19:44] I don't even know what I'd file a bug against or what the description is besides "nobody knows how this works, but somehow it's broken" [19:45] We are a small handful of engineers (and one tester) trying to get working images on prerelease hardware. We spend days trying to fix issues like broken kernels and video corruption. [19:45] Not much time left in the day for documenting how to roll your own images on unsupported hardware. [19:46] there is a ton of documentation on th ewiki [19:46] especially for cutomizing stuff [19:46] well, where I work, I do all that here too.. that is why I am here asking. We have one guy, which is me, no testers, besides me.. no experience, besides mine, which is admittedly tantamount to zero on this stuff [19:46] unfortunately the hardware is *retail* and was shipping 4 weeks ago [19:46] or 8 months ago for the efikamx [19:47] I don't have the luxury of letting it break for another release, it is soul destroying to run karmic on an mx51 [19:48] So if something is shipping we should arbitrarily just support it? Intel has been shipping Poulsbo based systems for 2 years, but even they don't support it in Linux. [19:50] * GrueMaster wanders off to do more testing. === hrw|gone is now known as hrw [20:00] no I just don't get to spend all my days fixing little issues like video corruption because we can't even get oem-config to work [20:00] I found a description of what is going on and I'm going to report it [20:01] feature :D [20:03] do you think that it is possible that oem-config systems are meant to run tasksel such that gdm is installed after creating a user? [20:13] bug 644638 [20:13] Launchpad bug 644638 in ubiquity (Ubuntu) "maverick oem-config gtk frontend does not start on first boot because gdm runs before it (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/644638 [20:13] ogra: I tried the cdimage.. very slick :-) [20:13] but: mem=460M@0x80000000 mem=256M@0xA0000000 [20:14] is there a reason for omitting the last 256mb? [20:14] ogra_ac: ^^^ [20:18] robclark: the weird mem corruption bug we're facing with highmem [20:18] there's a bug for it, one sec [20:19] bug 633227 [20:19] rsalveti: ahh.. so you are using 768 without highmem? [20:19] Launchpad bug 633227 in linux-ti-omap4 (Ubuntu) "instabilities with highmem activated (affects: 2) (heat: 508)" [Undecided,New] https://launchpad.net/bugs/633227 [20:19] robclark: we have highmem activated, but not using the last 256mb [20:19] when we use it, we can easily get memory issues [20:19] hmm.. ok, so it is last 256mb that is the issue? [20:20] just try to build a kernel [20:20] yeah, I've seen the issues.. [20:20] yep.. [20:21] we got a patch that improved a little bit, but it's still broken [20:21] ok, yeah.. I saw that. I just wasn't expecting skipping last 256m would work around the issue.. interesting [20:21] robclark: any idea if x-loader could be the culprit? [20:22] we wanted to test current upstream, but mmc is broken [20:23] not sure.. I assumed it was highmem, but I don't know enough about highmem to know why it would make a difference, 768 vs 1024.. [20:25] robclark: yep... [20:25] from http://lkml.org/lkml/2010/9/8/425 it shows that this issue was happening with others too [20:25] but then with the proposed fix we're still facing issues [20:26] better, but not yet fixed [20:29] * rsalveti brb === JaMa|AFK is now known as JaMa === hrw is now known as hrw|gone [22:32] rsalveti: w/ the cdimage filesystem (with initrd and all that), are there any special instructions to use my own (cross-compiled) kernel? [22:32] ie. does the initrd need to be updated w/ new modules or anything like that? [22:35] robclark: I'm not that sure if you'll need a new uInitrd, as I generally get the new generated one when I install my package [22:35] if you're running your board already, just install your new kernel package, that's enough to regenerate the initrd.img [22:35] than I believe flash-kernel could do the work of updating it for you [22:35] if the links are correct at /boot [22:36] hmm.. and if I'm building the kernel on my laptop? [22:36] ok.. so scp over my uImage and modules, and then run flash-kernel? [22:36] robclark: that's ok, what I mean is that if you plan to install it at your running panda or planning to mount the sd card at your host and then install the package [22:37] oh, what you're planning? to copy the modules by hand or to install the generated deb file? [22:37] I generally run: make -j 6 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- CONFIG_DEBUG_SECTION_MISMATCH=y deb-pkg [22:37] I could do it either way.. whatever is easier.. [22:37] hmm, ok.. there is a deb-pkg make target? [22:38] then scp the kernel-image, dpkg -i, check the link and flash-kernel [22:38] I guess that is something on the ubuntu kernel? Or is that in upstream kernel makefiles? [22:38] robclark: yep :-) [22:38] robclark: upstream [22:38] oh.. cool [22:40] * robclark learns something new every day [22:41] hm..., raining a lot today, if I get off-line that should be the reason [22:44] swim faster. [22:44] weather.com says that we might get some rain tomorrow.. then again, the weather rarely does what the forecast says here [22:45] * GrueMaster gets weather updates from Dr. Quid B. Wong. [22:45] * robclark usually finds out about the weather after the fact [22:48] * rsalveti uses the gnome-weather applet :-) [23:30] devilhorns, Earlier you said we had to run gnome-panel: would it not be possible to host indicators and/or menus somewhere else? [23:30] persia, ideally yes ... gnome-panel is very heavy :( [23:31] tho the only other thing I know if is lxde-panel [23:31] or perhaps xfce-panel [23:31] Those share a common ancestor :) [23:31] yea :/ [23:33] persia, I'd like to be able to make an efl panel that would be able to host them ... but that means I'd have to dig into the core applet system and figure out how they are expected to be hosted, etc, etc [23:33] lots of issues there :/ [23:34] persia, devilhorns lets not go too crazy here please [23:34] Indeed. [23:34] davidm, hehe indeed :) [23:35] hence why I was just gonna forget about it for now :) [23:35] that sounds like a natty thing (if at all) :-) [23:35] davidm, No worries. Just idly chatting about lean and fast :) [23:35] Maybe even natty+ [23:35] Very much not maverick [23:35] persia, don't forget to remind folks that we need blueprint ideas this week, I've told everyone but .... [23:36] persia: alsa update. I am able to play audio on beagle using paplay, but not any of the GUI apps (totem, rhythmbox). I think it is mainly due to memory limitations. === persia changed the topic of #ubuntu-arm to: Ubuntu ARM Discussion & Development | https://wiki.ubuntu.com/ARM | Want to Submit a Bug? https://bugs.launchpad.net/ubuntu/+filebug | Build a rootfs from scratch: https://wiki.ubuntu.com/ARM/RootfsFromScratch | wanna cross build ? see http://idlethread.blogspot.com/2010/09/cross-compilation-redux.html | Maverick is frozen: start submitting natty blueprints [23:37] GrueMaster, Heh. Thanks for testing that with paplay though.