**** BEGIN LOGGING AT Fri Oct 22 02:59:58 2010 Oct 22 03:28:34 anybody know where I can get a static version of libpthread for the gcc-arm-4.5 compiler? Oct 22 06:38:20 hi Oct 22 06:43:44 compile some source packages, them need depend other package Oct 22 06:44:25 where are there package depend table ? Oct 22 07:19:19 asmcos: in debian/control? Oct 22 07:19:50 asmcos: sudo apt-get build-dep $yourpackage might do the trick Oct 22 07:20:32 asmcos: or you use pbuilder that automatically satisfies build dependencies in the chroot Oct 22 07:29:54 oh Oct 22 07:30:04 i can get list table? Oct 22 07:30:14 about the depend Oct 22 07:35:04 asmcos: grep-dctrl -n -s Depends Depends debian/control Oct 22 07:35:14 asmcos: does ~ what you want Oct 22 07:36:34 example Oct 22 07:36:54 python-gtk depend gtk Oct 22 07:37:04 gtk depend cario Oct 22 07:37:12 cario depend xxx Oct 22 07:37:27 so ,i need build python-gtk Oct 22 07:37:36 i need build gtk first Oct 22 07:38:37 i need the order Oct 22 08:18:06 re Oct 22 08:34:45 * XorA|gone finds the lack of positive feedback when booting ubuntu on beagle disturbing Oct 22 09:12:26 XorA, ? Oct 22 09:12:35 you dont get a splash screen ? Oct 22 09:24:08 ogra: DVI is totally dead on release images Oct 22 09:24:27 * XorA is finding debugging hard by heartbeat LED Oct 22 09:26:47 ah, 3rd reboot I get splash Oct 22 09:28:14 * XorA has no idea what it was doing Oct 22 09:28:15 XorA, known issue, fix pending .... nicely nobody told us about the rewiring of the latest boards, so a kernel patch is missing Oct 22 09:28:36 this is a beagle, not an XM Oct 22 09:28:57 oh Oct 22 09:34:06 ogra_ac: it seems to be just plain random if dvi comes up :-( Oct 22 09:34:18 weird Oct 22 09:34:37 sounds more like a HW issue to be honest Oct 22 09:34:53 i havent seen or heard about such behavior yet Oct 22 09:35:54 not an issue I saw on Angstrom :-( Oct 22 09:36:06 * XorA hopes the dust on the board didnt break it Oct 22 09:38:59 * XorA gives up and looks at some other toy Oct 22 10:13:02 berco, ndec, alsa-utils should be all fixed now, please test Oct 22 10:13:22 it also shouldnt matter if the state file exists or not now Oct 22 10:13:50 ogra_ac: thanks. we will :) Oct 22 12:34:49 ogra_ac: alsa-utils fails to install. I believe some scripts are run under sudo (sudo apt-get install) and it complains. http://pastebin.ubuntu.com/518025/ Oct 22 12:35:55 berco, hmm, could you try on a panda ? i tested it here Oct 22 12:36:00 didnt have such issues Oct 22 12:36:18 ogra_ac: it's on a panda :) Oct 22 12:36:44 how can that be ? Oct 22 12:37:00 it reports the wrong device name Oct 22 12:37:02 ogra_ac: I took the 10.10 .img and configured firewall + proposed, that's it Oct 22 12:37:19 hmm Oct 22 12:37:29 ogra_ac: let me check, maybe my mistake :) too many boards on my desk Oct 22 12:37:29 your kernel definitely is to old Oct 22 12:38:16 ogra_ac: I confirm it's on a panda but I didn't upgrade the kernel yet Oct 22 12:38:22 ah Oct 22 12:38:28 * ogra_ac sighs Oct 22 12:38:41 ok so process is to upgrade kernel, i'll do it Oct 22 12:38:46 i really dont see a way how to tell alsa-utils to make sure the kernel is new enough Oct 22 12:39:02 i cant add a dependency for that Oct 22 12:39:22 berco, well, it needs to work automatically Oct 22 12:39:35 and we need the alsactl init call once Oct 22 12:40:05 else the systems wont be initialized at all and the state file will just save the uninitialized state Oct 22 12:40:25 ogra_ac: well in this case, alsa-utils needs to be fixed to depend on a kernel version Oct 22 12:40:31 berco: you need to update from maverick-updates before doing the upgrade for maverick-proposed. Oct 22 12:40:43 * ogra_ac will never let such stuff slip again into an update, working sound needs to become a requirement pre-release Oct 22 12:41:02 ndec, the kernel he needs is also in proposed Oct 22 12:41:05 thats my prob Oct 22 12:41:19 berco, alsa-utils cant depends on a kernel Oct 22 12:41:24 berco: did you run an upgrade, or just install alsa-utils? Oct 22 12:41:50 ndec, the prob is that the new kernel will only be there after the upgrade Oct 22 12:41:53 ndec: just installed alsa-utils. I was very basic and just read the email I received from Lauchpad Oct 22 12:42:16 and als-utils will come in with the same upgrade *before* the kernel is running Oct 22 12:42:18 ogra_ac: i see... catch 22 ;-) Oct 22 12:42:21 yes Oct 22 12:42:24 * ogra_ac curses Oct 22 12:42:38 this sound stuff turns into an etarenal problem Oct 22 12:42:44 *eternal Oct 22 12:43:04 its all trivial ... but fixing it in an upgrade starts to seem impossible Oct 22 12:43:25 probably persia has an idea Oct 22 12:43:40 i'm clearly running out of ideas Oct 22 12:45:00 ndec: ogra_ac: after the upgrade is "sudo flash-kernel" needed? or is it automatically done? Oct 22 12:45:13 berco, its all automatic Oct 22 12:45:25 waoh! nice :) Oct 22 12:45:52 you should also get a notification on the desktop that a reboot is required after a kernel upgrade Oct 22 12:46:51 ogra_ac: ok, upgrade is taking place... Oct 22 12:46:53 ogra_ac: run the init at next boot instead of in postinst? Oct 22 12:47:03 ndec, how ? Oct 22 12:47:20 there are only two ways i can run the init Oct 22 12:47:52 one is the postinst, the other is from the initscript ... if i run it from the initscrip i can only call it if no state file exists Oct 22 12:48:19 else it would run every time and the state file would never restore the mixer settings Oct 22 12:49:25 ndec, the core problem is that the driver (unlike all other drivers) needs the alsactl init call Oct 22 12:50:47 ogra_ac: can it be called in alsa-utils? if file does not exist then call alsactl init Oct 22 12:51:25 berco, thats what alsa-utils does already Oct 22 12:51:45 berco, the file always exists if you rebooted once Oct 22 12:52:28 the prob is that a) the call is needed at all and b) that we cant call the init on a totally virgin system (since we upgrade we dont know how often the user rebooted already) Oct 22 12:52:30 ogra_ac: ok, I think I missunderstood the issue you were discussing. your pb is when the upgrade happens and file exists, tight? Oct 22 12:52:37 yes Oct 22 12:52:40 s/tight/right/ Oct 22 12:52:51 thats what the postinst is supposed to solve Oct 22 12:53:05 but i didnt take into account that kernel and alsa arrive at the same time Oct 22 12:53:19 even a dependency wouldnt help since the kernel needs to be active first Oct 22 12:53:35 (beyond the fact that i cant add a dep on kernel to alsa) Oct 22 12:53:58 as nicolas said, its a catch 22 Oct 22 12:54:44 but if you are able to notify reboot, it means you know that a kernel upgrade happened. You can just delete state file in this case Oct 22 12:55:03 next boot it will be created correctly Oct 22 12:55:21 the state file is created on shutdwon Oct 22 12:55:39 i would have to do heavy hacks to upstart to not make that happen Oct 22 12:55:43 not an option Oct 22 12:56:04 hmm Oct 22 12:56:18 the whole alsa setup is really not designed to kack around such driver probs in upgrades ... thats the prob Oct 22 12:56:23 *hack Oct 22 12:56:34 usually drivers properly initialize Oct 22 12:56:40 so you dont need such a call Oct 22 12:57:20 we need to get that definitely fixed for natty Oct 22 12:57:32 in the driver ... Oct 22 12:57:44 sadly i have no clue why it doesnt initialize :/ Oct 22 13:01:35 ogra, I'm note quite sure what I'm supposed to have an idea about. Is it that you need to run `alsactl init` before asound.state exists, and once asound.state exists, you can never do this? Oct 22 13:01:40 s/note/not/ Oct 22 13:01:58 persia, i can do this Oct 22 13:02:29 persia, new kernel is in proposed ... adding functionallity alsa needs ... alsa update is in proposed, needing the kernel features ... Oct 22 13:02:57 persia, both updates arrive together, alsa needs to call alsactl init once to make the card work Oct 22 13:03:15 but the init only works if the kernel is actively running Oct 22 13:03:16 Ah, but the kernel needs to have already been updated before alsa-utils can be updated? Oct 22 13:03:20 yes Oct 22 13:03:28 Oh, updated && rebooted. Oct 22 13:03:36 right Oct 22 13:03:45 `alsactl init` is currently in postinst? Oct 22 13:04:02 and in alsas initscript if no state file exists Oct 22 13:04:15 the state file is created on shutdwon Oct 22 13:04:33 i cant call aslactl init on every boot because that would reset the mixer settings Oct 22 13:05:14 Ah, so it can't ever work: either you aren't running the new kernel *OR* you will clobber the user's mixer settings. Is that accurate? Oct 22 13:05:36 right Oct 22 13:06:27 one evil hack i can imagine is to put an initscript in place that checks the kernel version and the existence of a file we create once alsactl init was run Oct 22 13:06:29 With the old notification system, there used to be a way to send an alert to the user that they needed to take action, and they could select there, so we could have a one-time thing that would reset based on user choice on first reboot. Oct 22 13:06:41 I don't think that works with the new notificaiton system (no action support). Oct 22 13:07:01 right, it wont work with the new system Oct 22 13:07:30 That's not that evil a hack, it's basically how the old system worked, except that I'm not sure how to ask the user if they don't mind if we clobber their mixer settings. Oct 22 13:07:35 its also still a myth to me why we need to call aslactl init at all Oct 22 13:07:44 no other driver needs that Oct 22 13:07:47 "myth"? "mystery"? Oct 22 13:07:51 yes Oct 22 13:09:03 Did mvo fix the debconf dialog bug? Oct 22 13:09:10 not yet i think Oct 22 13:09:18 i'm not even sure he works on it Oct 22 13:09:22 Then I think we can't talk to the user in any sane way. Oct 22 13:09:48 Which makes the choices 1) documentation or 2) break custom configurations once. Oct 22 13:09:55 even if we could, what would we say ? Oct 22 13:11:05 "It appears that your kernel doesn't have support for the SDP4430 audio interface, which is available on your computer. Would you like this to be set up at the next reboot? This will reset any mixer settings you may have adjusted." Oct 22 13:11:32 Or something like that. Oct 22 13:11:41 and then ? Oct 22 13:11:54 how do we set them up at next boot ? Oct 22 13:11:58 The user would answer "yes" or "no" and we'd use that information to clobber or not clobber the config. Oct 22 13:12:09 that doesnt require a question Oct 22 13:12:22 we can clobber the config Oct 22 13:12:29 there was no sound support at all before Oct 22 13:12:30 Have the postinst run a special script in /var/lib/ if it's present, and delete the script when the script has run once. Oct 22 13:12:52 I don't like just clobbering the config very much, but that's easy to do. Oct 22 13:13:11 i dont care about the config, since there never was a working one Oct 22 13:13:20 we can just wipe it Oct 22 13:13:23 Just force-delete asound.state and run `alsactl init` ONCE only after verifying correct architecture and kernel version. Oct 22 13:13:32 right Oct 22 13:13:38 Some folk may have working USB-audio or something. Oct 22 13:13:43 how do i delete the state file ? Oct 22 13:13:47 rm Oct 22 13:13:55 at boot ? Oct 22 13:14:14 after fs mount, obviously. Oct 22 13:14:31 upstart cretaes it on shutdown so we need to rm it on boot Oct 22 13:14:37 and do that only once Oct 22 13:14:47 And only do that when we're clobbering. Oct 22 13:14:49 if the file doesnt exist i dont need to do anything Oct 22 13:14:54 have the entire thing in a script Oct 22 13:15:03 alsactl init is run automatically on device init Oct 22 13:15:05 have the script only get installed on panda Oct 22 13:15:16 Have the script run only if a supporting kernel is available. Oct 22 13:15:28 ugh Oct 22 13:15:34 thats realy ugly and hackish Oct 22 13:16:07 but unless we have a driver that dosnt need the alsactl init it might be the only option Oct 22 13:16:19 Trigger it with something like [ -x ${SCRIPT} ] && "${SCRIPT}" && rm "${SCRIPT}" Oct 22 13:16:25 USB Oct 22 13:16:27 i dont really see yet how to have that only installed on pandas Oct 22 13:16:49 Check for some signature prior to emplacing the script. Oct 22 13:17:31 cp it from postinst ? Oct 22 13:17:38 Maybe "/var/lib/alsa/SDP4430.cleanup" ? Oct 22 13:17:51 alsa-utils turns into a very ugly thing through me Oct 22 13:17:52 No, here-file it from postinst. Oct 22 13:18:08 hmm Oct 22 13:18:32 well, i need an upstart job too Oct 22 13:18:42 not sure that can come from a here doc Oct 22 13:18:42 Why? Oct 22 13:19:00 because something needs to trigger the script Oct 22 13:19:23 on boot Oct 22 13:19:26 Just modify /etc/init/alsa-mixer-save.conf Oct 22 13:19:34 ugh Oct 22 13:19:48 thats only run on shutdown Oct 22 13:20:02 Ugh, so you need two. Hrm. Oct 22 13:20:11 right Oct 22 13:20:43 You could add a udev rule that ran the script (if present) on SDP4430 load... :) Oct 22 13:21:40 hmm Oct 22 13:21:47 apropos udev rules Oct 22 13:21:56 ogra@panda:~$ ls /dev/snd/ Oct 22 13:21:57 by-path pcmC0D0p pcmC0D12c pcmC0D15c pcmC0D16p pcmC0D18c pcmC0D20c pcmC0D3p pcmC0D5p pcmC0D8c timer Oct 22 13:21:57 controlC0 pcmC0D10c pcmC0D13p pcmC0D15p pcmC0D17c pcmC0D19c pcmC0D2c pcmC0D4p pcmC0D6p pcmC0D8p Oct 22 13:21:57 pcmC0D0c pcmC0D11p pcmC0D14p pcmC0D16c pcmC0D17p pcmC0D1c pcmC0D2p pcmC0D5c pcmC0D7p pcmC0D9p Oct 22 13:22:00 Good use of "apropos" ! Extra points. Oct 22 13:22:09 where the heck do the devices get there ? Oct 22 13:22:32 s/where/how/ Oct 22 13:22:44 ALSA/ASoC Oct 22 13:22:50 persia, nope Oct 22 13:23:02 we dont create any devices under /dev/snd in maverick Oct 22 13:23:05 paste me an lsmod? Oct 22 13:23:20 all sound devices are in /dev directly on maverick Oct 22 13:23:31 Not on my install. Oct 22 13:23:49 persia, but on all others Oct 22 13:23:58 Not on *any* of my installs. Oct 22 13:24:16 persia, maverick dropped all udev rules that mangle sound device creation Oct 22 13:24:18 And most of them are native-maverick rather than upgrades. Oct 22 13:24:29 Use of /dev/snd isn't mangling. Oct 22 13:24:30 they *have* to live in /dev Oct 22 13:24:44 unless the kernel creates them directly in there Oct 22 13:24:50 which afaik it doesnt Oct 22 13:25:56 persia, grep snd /lib/udev/rules.d/* Oct 22 13:26:13 nothing puts them there unless the kernel does it itself Oct 22 13:26:19 I still think it's somewhere in /sbin/alsa-utils Oct 22 13:26:35 But it wouldn't surprise me if the kernel put them there, really. Oct 22 13:27:10 well, it must either be a udev rule or the kernel Oct 22 13:28:15 I think "snd" ends up being part of DEV_BASENAME somehow Oct 22 13:28:28 i dont have it on my ac100 Oct 22 13:28:33 so it must be the kernel Oct 22 13:28:42 since i have mavericks alsa Oct 22 13:28:43 Quite possibly. Oct 22 13:28:51 and mavericks udev Oct 22 13:29:07 (talking about my SB play USB card though) Oct 22 13:29:24 What happens if you plug that into the panda? Oct 22 13:29:33 never tried ;) Oct 22 13:29:44 and i'm to lazy to go upstaris atm Oct 22 13:31:38 persia, i think i'll drop the whole posinst hackery and hack up /sbin/alsa-utils with a kernel check Oct 22 13:31:48 that should DTRT Oct 22 13:32:33 Don't. Oct 22 13:32:36 http://paste.ubuntu.com/518046/ Oct 22 13:32:40 You want the run-once functionality. Oct 22 13:32:41 thats what we already have Oct 22 13:33:18 i can just touch an additional file Oct 22 13:33:42 check state file, check kernel, look for file Oct 22 13:34:00 Do a here-file run-once script in the postinst. Oct 22 13:34:26 then replace the -f call with [ -x "${SCRIPT}" ] && "${SCRIPT}" && rm "${SCRIPT}" Oct 22 13:34:56 te -f call needs to stay Oct 22 13:35:00 *the Oct 22 13:35:10 thats for virgin installs Oct 22 13:35:19 where no state exists Oct 22 13:35:26 (natty) Oct 22 13:36:19 (and where we indeed have the right kernel in advance) Oct 22 13:37:28 Right, but stick that in the run-once script. Oct 22 13:38:06 Actually, doesn't matter. Fresh installs can't have asound.state Oct 22 13:38:13 And we're force-clobbering it anyway. Oct 22 13:38:36 well, for natty my requirement is that the driver behaves properly Oct 22 13:38:52 so i hope we wont need that hack at all there Oct 22 13:39:04 but until thats the case this code stays wheer it is Oct 22 13:39:16 the hack i will add now will be maverick only Oct 22 13:40:25 hmpf Oct 22 13:40:31 and a have to do a dpkg check Oct 22 13:40:39 That's a bad place for the code: you end up running every boot. Oct 22 13:40:55 Really, do a run-once script trick in place of the -f business. Oct 22 13:41:10 Then in the run-once script do your dpkg-check, -f check, etc. Oct 22 13:41:14 yes, like the other hacks in the preinit_levels_on_card() function Oct 22 13:41:27 You can always exit 1 to get out without deleting it, and run it next time. Oct 22 13:41:30 thats what this function is for, other cards use it too for hackish stuff Oct 22 13:41:36 (mainly intel hda) Oct 22 13:41:36 Oh, fine. Oct 22 13:41:49 and powermac Oct 22 13:42:06 so the natty side is ok here Oct 22 13:42:16 the maverick one isnt Oct 22 13:42:32 and i'm still not happy with the postinst run-once idea Oct 22 13:42:48 i wonder if we cant get someone to instead fix the driver Oct 22 13:43:19 but the call was just cancelled, so discussion of that has to wait until UDS Oct 22 13:44:53 (at which point i wanted to have that completely fixed ... sigh) Oct 22 13:45:43 Fixing the driver is *hard*, or we would have dropped all the stuff currently in place a month ago. Oct 22 13:45:46 ndec, we need to discuss a lot of stuff next week (i had wished the call wasnt canceled today) Oct 22 13:46:09 It's not like the way to solve it changed in that time: it just took that long for anyone to begin to fix the driver enough that we could start using it. Oct 22 13:46:10 persia, there was no work since two weeks Oct 22 13:46:18 since everyone thinks its fixed Oct 22 13:46:41 I know. Still, the solution in place is the one we knew about 6 weeks ago. Oct 22 13:46:53 which doesnt help Oct 22 13:47:00 its half breeded Oct 22 13:47:01 Anyway, point being that fixing it is *hard*. We need to have a better understanding of what is needed. Oct 22 14:19:00 persia, hmpf ... another issue ... how would i know which kernel actually runs ? Oct 22 14:19:17 uname only gets me everything up to the ABI version Oct 22 14:19:28 dpkg-query -W -f='${Version}\n' linux-image-$(uname -r) Oct 22 14:19:41 that gets me the installed version but doesnt tell me if it runs Oct 22 14:21:02 i dont think there is a way to get the info i actually need Oct 22 14:27:58 ogra, I think you can't. Oct 22 14:28:22 You can only tell if a given ABI is running. Oct 22 14:28:32 Complain to the kernel team, if you like. Oct 22 14:28:55 persia, nah, just found a way Oct 22 14:29:03 ogra@panda:~$ cat /proc/version_signature Oct 22 14:29:03 Ubuntu 2.6.35-903.15-omap4 2.6.35.3 Oct 22 14:30:11 Yet another reason it's good to ask questions of the right folk :) Oct 22 14:30:30 heh Oct 22 17:48:51 ahoy there Oct 22 17:49:03 guys, there's a server session scheduled early monday at UDS-N Oct 22 17:49:23 I'd like some linaro people to attend to see where we can help, but it conflicts with our roundtable Oct 22 17:49:27 could we move it around? Oct 22 17:55:58 kiko, The schedule is still very dynamic. Subscribe your folks as "participation essential" to both sides of the conflict, and it ought mysteriously disappear. Oct 22 17:56:14 I don't believe anyone likely to be active in this channel has special scheduling rights. Oct 22 17:57:01 persia, well, I know, but in our case we can't easily add essential participants to our roundtable. I'll try though Oct 22 17:57:21 Hrm. no idea. Oct 22 17:57:46 You might ask in #ubuntu-locoteams : I don't know *why* the summit devs tend to chat about the code there, but it seems to be the place. Oct 22 17:57:49 persia, I can move it manually? Oct 22 17:57:57 if you say it's okay to have that in the second slot Oct 22 17:58:03 If you can move stuff, but don't make other people conflict :) Oct 22 17:58:39 done! thanks persia Oct 22 17:58:54 * persia has a strong suspicion that humans should avoid trying to find a best-fit simultaneous schedule for ~300 participants, and register preferences instead Oct 22 18:48:15 Doing a update from stock 10.10 image for OMAP4 (running on Pandaboard) -- is taking a loooong time.. any known issues? Oct 22 18:51:08 Hundreds :) Oct 22 18:52:28 :D Oct 22 18:52:59 desktop update is smooth.. but on panda.. slow like a tortoise.. Oct 22 18:53:05 But the two main factors you are hitting are 1) ports.ubuntu.com is painfully slow, and 2) there's something like 100 updates since release Oct 22 18:53:52 Downloadding updates went pretty quick Oct 22 18:53:57 (we released 3 weeks early, and it just isn't as polished as we like, but we used to release at the beginning of October, and will be in *much* better shape to ensure the next release isn't broken) Oct 22 18:54:02 Installing is the slow part.. I guess it's the MMC card! Oct 22 18:54:12 should use USB stick... that should speed things up Oct 22 18:54:37 understand Oct 22 18:54:40 Oh, if the download is done, yeah, it's the MMC being slow, and probably made slower by the dpkg/fsync thing combined with the FTL eraseblock management. Oct 22 18:54:54 I see Oct 22 18:55:48 dpkg breaks fairly spectacularly if the state on disk isn't accurate, so it ends up calling fsync all the time because it can't trust the filesystems (no transaction support). Oct 22 18:56:33 But that means, essentially, no useful disk cache for dpkg operations, which makes slow storage painful (and moreso for managed flash, because each fsync ends up marking an eraseblock used, which means the FTL has to do all sorts of things) Oct 22 18:57:13 I see.. thanks for give the details of what might be happening... Oct 22 18:57:29 Just a guess though :) Oct 22 18:57:43 Understand Oct 22 19:39:15 persia, i got a new stereo BT headset ... Oct 22 19:39:54 funnily its not found on the ac100 (while i see lots of phones from 300m distant neighbors) Oct 22 19:40:18 persia, any idea what i should look for ? BT seems to be fine, BT audio doesnt Oct 22 19:40:59 Heh. Oct 22 19:41:20 ogra, Bring it to UDS. I'm not going to dig up a BT headset at 4:30 to test this with you today. Oct 22 19:41:23 its a really cool one for music and calls Oct 22 19:41:31 bah, slacker !!!! Oct 22 19:41:41 ... i'll indeed bring it ;) Oct 22 19:41:53 thanks for answering at that time :) Oct 22 19:41:56 No, just need to proof-read and publish a bundle of specs and a couple documents before UDS. Oct 22 19:42:17 what happened to the schedule ... the other channel reads funny Oct 22 19:42:19 * persia isn't especially diurnal or anything :p Oct 22 19:43:24 I'm not sure precisely. Everything went wonky, and I started using LP to look at specs. Oct 22 19:43:43 well, seems in order again Oct 22 19:43:49 my specs are still all there Oct 22 19:43:58 and even at more convenient times now Oct 22 19:44:32 * ogra_ac reboots to see if BT behaves differently if plugged at boot Oct 22 19:44:44 Shouldn't, Oct 22 19:50:43 ha Oct 22 19:51:15 it helps if the headset isnt paired with my phone while searching for it Oct 22 19:52:23 now how do i tell alsa about it ... hmm Oct 22 19:58:55 yay, bluetooth music Oct 22 19:59:27 So, you figured out you had to tell pulse, rather than ALSA? Oct 22 19:59:44 well Oct 22 19:59:48 its a bit tricky Oct 22 20:00:03 i have to recompile the kernel with a hack to make the tegra card modular Oct 22 20:00:14 then pulse doesnt eat 100%CPU Oct 22 20:00:33 *then* i can let pulse start with dummy device Oct 22 20:00:41 and *then* bt sound works Oct 22 20:00:58 as well as my soundblaster USB card btw Oct 22 20:01:15 heh. Oct 22 20:01:16 intrestingly i have no volume control Oct 22 20:01:32 i can control app volume in RB but no master in the panel or pulse Oct 22 20:01:39 and mic input doesnt seem to work Oct 22 20:01:40 Yes you do, but there's a bug that the default volume control doesn't actually control the volume of the output you are using. Oct 22 20:01:53 This is most unexpected when you have a USB headset with HID volume buttons. Oct 22 20:01:55 it works with the usb card Oct 22 20:02:14 If you go into the detailed volume control and fiddle levels on the individual devices, it ought work. Oct 22 20:02:16 more important is though that i get the mic working Oct 22 20:02:27 i want to mumble with the headset Oct 22 20:02:39 It works on whatever it thinks is default, which is fine for folks that only have one sound output (who are becoming an increasingly small proportion) Oct 22 20:02:50 It's probably muted. Oct 22 20:02:58 not in the UI Oct 22 20:03:37 Try muting and unmuting. Sometimes the uninitialised state is incorrectly displayed. Oct 22 20:04:36 hmm, i will try Oct 22 20:04:59 * ogra_ac isnt sure if he can swithc from hifi to telephony mode without breaking RB Oct 22 20:06:01 I doubt it: they are different BT profiles. Some hardware supports input and output with hifi, some requires a profile switch. Oct 22 20:06:41 well, music stops if i switch to the telephony profile Oct 22 20:06:58 heh, and RB paused properly Oct 22 20:07:57 A profile switch ends up being like a hardware change, from pulse's perspective (as I understand it) Oct 22 20:08:03 ah Oct 22 20:08:35 hmm, no peaks on the meter Oct 22 20:09:16 if i only knew where the mic sits in this gem of industrial design Oct 22 20:10:05 its a jabra halo btw Oct 22 20:10:08 You might want to chat about BT stuff in some channel baptistemm haunts, as he seems to be our current primary maintainer. Oct 22 20:10:51 (although, like most sensible folk in his part of the world, he's probably not in front of his computer now) Oct 22 20:11:08 yeah Oct 22 20:11:11 its not urgent Oct 22 20:11:20 i need the non NEON QT forst anyway Oct 22 20:11:25 *first Oct 22 20:11:32 else i cant run mumble Oct 22 20:11:37 You know, some folk like NEON. Oct 22 20:11:45 and that might still be bulding Oct 22 20:11:48 You're the one on unsupported hardware. Oct 22 20:11:55 good for them Oct 22 20:14:01 we guarantee that nothing is built with NOEN in maverick Oct 22 20:14:02 *NEON Oct 22 20:14:02 a fix is already in proposed Oct 22 20:15:44 well Oct 22 20:15:49 still building it seems Oct 22 20:15:52 https://edge.launchpad.net/ubuntu/+source/qt4-x11/4:4.7.0-0ubuntu4.1/+build/2012722 Oct 22 20:16:09 i wonder if it will make it before i step on the plane Oct 22 20:23:20 Who guarantees that? I'm certain it's not true. Oct 22 20:23:52 I doubt it. qt4-x11 takes *forever*, and seems to die during build every once in a while (based on whackamole observations) Oct 22 20:25:46 yeah Oct 22 20:26:08 well, in any case that build is with -no-neon Oct 22 20:26:22 if it succeeds i hope it's actually true :) Oct 22 20:29:09 I'm surprised rbelem didn't have anything to say: I think he needs NEON to run at a decent speed on his n900 :) Oct 22 20:29:35 well Oct 22 20:29:42 it breaks all QT apps on dove Oct 22 20:29:48 david was pretty upset Oct 22 20:30:06 (and indeed on ac100 but thats rather less important) Oct 22 20:30:48 Who uses Qt on dove? :) Oct 22 20:30:53 no idea Oct 22 20:30:59 but we guarantee that it works Oct 22 20:31:03 That's what I thought. Oct 22 20:31:04 Who? Oct 22 20:31:23 I'm absolutely certain there's vast chunks of stuff in the archive that uses NEON in one way or another. Oct 22 20:31:42 Simply because of all the effort to *ADD* NEON support some time back. Oct 22 20:31:47 sure, but none of the core libs in main Oct 22 20:32:03 Well, except Qt :) Oct 22 20:32:21 And everything built on Qt (you will be testing the entire rdepends stack, right?) Oct 22 20:33:15 nope Oct 22 20:33:43 So, what about regression potentials? Oct 22 20:33:54 i will test what i can Oct 22 20:34:12 it wont regress on anything but arm Oct 22 20:34:33 So? There's plenty of users of Qt on ARM. Oct 22 20:34:48 And all the testing was done on NEON-capable platforms, etc. Oct 22 20:35:23 its very very unlikely that you have NEON stuff on app level Oct 22 20:52:58 hah ! Oct 22 20:53:01 https://edge.launchpad.net/ubuntu/+source/qt4-x11/4:4.7.0-0ubuntu4.1/+build/2012722 Oct 22 20:53:06 finished successfully Oct 22 21:03:29 Hi all Oct 22 21:04:06 hi, can someone helb my with a beaglebord c4 an ubuntu? Oct 22 21:04:13 I recently bought Beagleboard Rev A3 .. However HDMI / DVI to LCD tv was not working Oct 22 21:05:39 persia, fyi, mumble works fine with the new QT, no SIGILL anymore Oct 22 21:05:42 i have problems with the installiation Oct 22 21:06:01 I checked up and found out a bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663642 .. and reinstalled OMAPMaverickInstall ... Still now no DVI output but now Xorg fails with /dev/fb0 not found Oct 22 21:06:02 Launchpad bug 663642 in linux-linaro (Ubuntu Maverick) (and 3 other projects) "DVI doesn't work at BeagleBoard xM rev A3 (affects: 1) (heat: 16)" [Undecided,Fix committed] Oct 22 21:06:06 Any help would be appreciated Oct 22 21:11:15 i have a beagle c4 with android. now i want to install Ubuntu , but i it dount start the Image from sdcard Oct 22 21:11:57 and yes.. i am a dau Oct 22 21:13:10 Guest60685, What doesn't work? Oct 22 21:13:46 linux_manju, Unfortunately, it needs a kernel change, which complicates installation. I'd recommend following that bug, and either helping to test, or waiting until the fix is released. Oct 22 21:14:07 geruds, On my C4, I have to hold down S1 for a long time to get it to boot from SD. Oct 22 21:14:29 the user button? Oct 22 21:14:58 persia: I did install the recomended kernel as suggested here : https://wiki.ubuntu.com/ARM/OMAPMaverickInstall Oct 22 21:15:20 persia: Its been 7 days sofar.. I have been banging my head on this. but to no avail :( Oct 22 21:17:05 linux_manju, I don't know what to suggest. Maybe someone else with that hardware that got it working will have an answer. Oct 22 21:17:19 geruds, Yes. Oct 22 21:17:41 hmpf ... Oct 22 21:17:51 pulse doesnt like to work with mumble Oct 22 21:17:51 persia: NP .. Thanks for trying though :) Oct 22 21:17:55 i will try. moment Oct 22 21:18:19 persia: Its dumb from beagle board side to change the HW without notice Oct 22 21:18:27 ogra, No. You need to fiddle mumble in lots of different ways. I remember NCommander trying to get my handset to work with mumble: after about 4 hours he gave up. Oct 22 21:19:07 linux_manju, Hardware vendors often do this, unfortunately: the issue is mostly related to timing: when a change like that happens right before a release, it's hard to make sure things are supported. Oct 22 21:19:07 well, it works fine with my wired headset on the laptop Oct 22 21:19:38 geruds, What I do is hold it down *before* adding power, wait for all the lights to come up, and release only then (10-15 seconds later). Oct 22 21:20:02 ogra, Right, because wired uses ALSA. BT is kinda special, because it talks to pulse directly (this is part of why we want pulse by default). Oct 22 21:20:13 mumble is just kinda broken, sadly. Oct 22 21:21:40 bah Oct 22 21:21:50 and the server kicks me out all the time Oct 22 21:22:17 ok.. it dosent work. so my image on the sd shoud be faild Oct 22 21:22:58 i got the massage "no MMc card found" Oct 22 21:23:27 geruds, You have just the one SD slot? Oct 22 21:23:52 jap. only thoe one on the bord Oct 22 21:24:43 and a new installation off android will work fine Oct 22 21:24:55 so i thing the hardware is ok Oct 22 21:27:29 new Message:"Unknow command 'mmcinit' Oct 22 21:29:24 And this is a C4? Oct 22 21:29:45 jap Oct 22 21:29:56 written on the bord ;-) Oct 22 21:29:58 Dunno then. Works for me. Oct 22 21:30:15 How did you write the SD? Oct 22 21:30:58 i use this tutorial https://wiki.ubuntu.com/ARM/OMAPMaverickInstall Oct 22 21:31:35 if you have a smarter one i will try it ;-) Oct 22 21:32:57 What I did was `gunzip ./ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz && dd if=./ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img of=/dev/sdc bs=1M` Oct 22 21:33:07 Obviously, you might not be using sdc :) Oct 22 21:33:25 But I've heard of other folk who had success with dd and lack of success with cat Oct 22 21:34:09 *g* ok.. i will use sdb ;-) Oct 22 21:47:28 persia the same problem 'no mmc card found' 'unkown command 'mmcinit' Oct 22 21:49:42 And you verified the checksum of the download? Oct 22 21:50:13 hmm Oct 22 21:50:25 i seem to be able to get it working with the usb headset Oct 22 21:50:31 but i cant hear a thing Oct 22 21:50:59 ofcorse not ;-) Oct 22 21:51:14 i make a new download an check it Oct 22 21:55:19 sigh, thats annoying Oct 22 22:19:07 persia, you dont feel like mumbling for a second i guess ? Oct 22 22:19:38 * ogra_ac finally found a HW config where the input seems to work Oct 22 22:24:17 hei persia, ok i check the md5 its al ok. i try 10.10. and 10.4 ; every time the same problem Oct 22 22:24:47 geruds, Hrm. I'm not sure what to tell you. I wonder if there are some different revisions of "C4" or something. Oct 22 22:24:49 i thing the problem ist here : On omap3 systems with a modified NAND (i.e. beaglebord C series) do the following: Oct 22 22:24:49 On a serial console connected to the system, halt any autoboot script and type Oct 22 22:24:50 setenv bootcmd 'mmc init;fatload mmc 0 0x82000000 boot.scr;source 0x82000000'; setenv autostart yes; saveenv; boot Oct 22 22:24:50 The system should start booting (note that this step is only necessary if you have a NAND and the system does not default to reading boot.scr) Oct 22 22:25:56 Hrm. Dunno. I never succeeded in seeing anything on serial: I just held down the button and it booted from the SD and worked. Oct 22 22:26:21 Bit slow and not much RAM, but otherwise. Oct 22 22:27:44 ok. i thing i will make a brake for today and will go on tomorow Oct 22 22:28:34 realy thanks for your help. it show me that i am not realy stuped ;-) Oct 22 22:29:00 if i finde a solution i will tell you Oct 22 22:29:33 If you don't mind, it would be better to add it to the wiki. Oct 22 22:30:03 Works for me, meaning I'm not likely to add it, and if you find a good workaround, maybe if someone else with a C4 has your issue, they can try that (but note that not all C4s have the issue). Oct 22 22:30:43 Same as where rsalveti added notes on his MX that linux_manju was using to try to get the XM/A3 working. Oct 22 22:32:01 jap i will poste it. i thing the problem is that androide is now in the NANE. if you have a new beagle the problem newer exist Oct 22 22:32:21 NAND Oct 22 22:32:56 You think the android bootloader in NAND is getting in the way of booting off MMC? Oct 22 22:33:12 yes Oct 22 22:33:19 You might try one of the recovery techniques from elinux.org to see if you can clear the NAND (obviously, backup anything interesting first) Oct 22 22:34:26 nice idear Oct 22 22:34:56 i will try it tomorrow.. Oct 22 22:35:00 thx Oct 22 22:50:35 Hello, I ran the a rootstock command from my host machine to generate a rootstock .img, but I get a non fatal error, and no .img in the end : chroot: failed to run command `/bin/installer': Exec format error, I: Cleaning up..., I: Unmounting temporary image Oct 22 22:50:44 Do you have any idea what goes wrong ? Oct 22 22:51:38 Oops, sorry, just after the 'Extracting ' step, I get "chroot: failed to run command `debootstrap/debootstrap': Exec format error" also Oct 22 22:55:48 I followed the RootstockFromScratch howto Oct 22 23:05:49 Getting better with the --no-root switch, but "No space left on device" : where does the image build process occurs ? I will stretch the mount point Oct 22 23:06:06 /tmp ? Oct 22 23:06:22 I suspect it is /tmp, but I'm just guessing. Oct 22 23:06:35 Maybe check with df just when you fill up the filesystem? Oct 22 23:06:43 Ok :) Oct 22 23:07:33 Strange, df shows me : sysfs 5160576 3176456 1721976 65% /sys Oct 22 23:07:45 No /, /home , /var, .. Oct 22 23:08:05 Are you in the chroot? Oct 22 23:08:40 I run a debian lenny host, and a maverick chroot. I'm building the .img file from the chroot, to install it on a phone after Oct 22 23:08:50 I don't want to install the img in the maverick chroot Oct 22 23:09:33 Ah ok, df always show those mount point from inside a chroot, must be normal Oct 22 23:09:57 pwork, if your going to run rootstock, i'd either run in on a 10.10 host, or in a armel machine running atleast squeeze.. otherwise you will have qemu issues... Oct 22 23:10:01 Right. You need to run df in lenny to find out what is full. Oct 22 23:10:18 rcn-ee, Doesn't a lucid host work also? Oct 22 23:11:00 the qemu in maverick is much more reliable.. (i can get small xfce images built in maverick that fail n lucid) Oct 22 23:11:04 rcn-ee, So I can't build a img from inside a chroot. Will I be able to make it from a maverick live CD if it exists ? Oct 22 23:12:31 pwork, i'd use virtual box over a live cd... it's going to eat a lot of ram creating the arm rootfs.. Oct 22 23:14:14 rcn-ee, You mean I can run the maverick live cd ISO from Virtualbox running on my lenny's host OS ? Oct 22 23:14:16 I can do this Oct 22 23:14:57 I'd probably run an *install* of maverick in Virtualbox running on lenny. Oct 22 23:15:04 persia, Strange, the host df shows nothing full Oct 22 23:15:12 Odd. Something wonky. Oct 22 23:15:13 yeah... but i mean create the virtual harddrive and install the iso on lenny in virtual box.. rootstock is going to eat 2gig's of space, so you'd run out of ram in any live cd pretty quick... Oct 22 23:15:39 Or use heaps of swap, but allocated storage is usually faster than swap. Oct 22 23:18:31 persia, Ok. I have a big swap partition, but on the host OS. I imagine that if it fails with "No space left", swap was filled before filling hard disk space Oct 22 23:18:58 I don't know if a chroot benefit from the swap partition. I imagine yes Oct 22 23:19:29 chroot relies on the running kerne. Oct 22 23:19:37 I'll be back to you if this succeeds in a vbox ran from host ;) Oct 22 23:19:41 Thanks for advice Oct 22 23:20:09 I'm not convinced that the binfmt-misc/qemu hacks used in rootstock work properly against a Debian kernel, but they may. Oct 22 23:20:51 Is a kernel distribution specific ? it's a linux 2.6.32 kernel Oct 22 23:21:00 Doesn't sound debian specific :s Oct 22 23:22:33 If I do this from vbox, will it uses the virtual OS kernel, or the host one ? Oct 22 23:23:03 If I run it from a live CD, I understand memory will be too short, but it will use a ubuntu kernel Oct 22 23:24:11 Many folk run kernels with distribution-specific patches added on. Many don't. I have no idea how much of the binfmt-misc stuff is Ubuntu-specific vs. upstream. Oct 22 23:25:00 pwork, What we're advising is to create a ~5G virtual disk in VBox, and install Maverick into that from the CD, and then use that VBox environment to run rootstock. Oct 22 23:25:14 Once you have an image, you ought be able to scp it back to your host, and then get it to your target. Oct 22 23:25:37 Ok, wrote it down :) Oct 22 23:26:15 persia, You're my favorite video game ! Oct 22 23:26:15 :p Oct 22 23:26:32 Tell you tommorow what the result is Oct 22 23:26:39 Good night/day Oct 23 02:41:55 Say, how "official" is the Ubuntu support for ARM, and how "official" is it for PowerPC? I'd say the ARM support is better than PPC, right? **** ENDING LOGGING AT Sat Oct 23 02:59:57 2010