**** BEGIN LOGGING AT Sun Feb 19 02:59:58 2012 Feb 19 04:10:27 \o/ chromium built on armel, I'll rebuilt for armhf later this weekend Feb 19 04:10:37 *build Feb 19 21:12:56 what package has the dgb symbols for ld-linux ? Feb 19 21:13:13 E: Unable to locate package binutils-dbg Feb 19 21:13:34 got it nvm Feb 19 21:18:33 GrueMaster: I assume this has been going on since the last alsa-utils upload? Feb 19 22:08:10 joined Feb 19 22:08:34 please help me ! ! ! Feb 19 22:10:06 pnphi: ask your question directly Feb 19 22:10:20 i create the image ...but from the step "Setting up xulrunner-1.9.2 (1.9.2.27+build1+nobinonly-0ubuntu0.10.04.1) ...", the process stop ... Feb 19 22:11:33 pnphi: which arm board are you using and which image Feb 19 22:11:44 ? Feb 19 22:12:06 project-rootstock/rootstock --fqdn ubuntu --login ubuntu --password ubuntu --imagesize 10G --seed ubuntu-desktop,gdm --notarball Feb 19 22:12:21 i create the image ...but from the step "Setting up xulrunner-1.9.2 (1.9.2.27+build1+nobinonly-0ubuntu0.10.04.1) ...", the process stop ... Feb 19 22:15:46 E: Sub-process /usr/sbin/dpkg-preconfigure --apt || true returned an error code (100) E: Second stage build in chroot failed ! E: Please see the log to see what went wrong. I: Cleaning up... E: Failure running script /usr/sbin/dpkg-preconfigure --apt || true I: Umounting temporary Image Feb 19 22:15:57 what errors ? Feb 19 22:16:37 how do i load a program while using libc6-dbg ? Feb 19 22:22:49 I am fallowing this guide: http://lists.linaro.org/pipermail/linaro-dev/2011-January/002022.html how do i use debugging packages? Feb 19 22:22:58 pnphi: a lot of things can go wrong when you roll your own image, the xulrunner package got updated recently https://launchpad.net/ubuntu/+source/xulrunner-1.9.2/1.9.2.27+build1+nobinonly-0ubuntu0.10.04.1 Feb 19 22:23:13 like libc6-dbg Feb 19 22:23:20 which install to /usr/lib/debug Feb 19 22:23:43 i tried using LD_LIBRARY_PATH=/usr/lib/debug or prefixing with the true path of the debug linker and that didn't work Feb 19 22:24:22 ok thanks and what errors ? Feb 19 22:24:24 scientes: when you have the debug symbols in place then debuggers like gdb can give a better backtrace by simply having the debug symbols in that folder Feb 19 22:24:34 E: Sub-process /usr/sbin/dpkg-preconfigure --apt || true returned an error code (100) E: Second stage build in chroot failed ! E: Please see the log to see what went wrong. I: Cleaning up... E: Failure running script /usr/sbin/dpkg-preconfigure --apt || true I: Umounting temporary Image Feb 19 22:24:41 pnphi: start by filing a bug against that package Feb 19 22:24:45 xranby, I cant run from gdb cause qemu does not implament ptrace Feb 19 22:25:21 I have to use from gbd target remote localhost:port Feb 19 22:25:25 and someone who are more familiar with xulrunner can probably locate what went wrong during the dpkg-preconfigure apt step Feb 19 22:26:58 scientes: do you have any debugger you can use? the binarys on your system know internally that the debug files are put into the /usr/lib/debug path Feb 19 22:27:22 qemu-arm-static -g 1234 /bin/ls Feb 19 22:27:46 I am using these instructions: http://lists.linaro.org/pipermail/linaro-dev/2011-January/002022.html Feb 19 22:28:14 and i've installed the relevent dbg packages (i believe) Feb 19 22:28:42 for gtk, wxwidgets, and libc6 (probably don't need, but couldn't figure out why i wasn't getting a backtrace) Feb 19 22:28:49 and my main executable is also not stripped Feb 19 22:30:06 ahhh -L to qemu-arm-static Feb 19 22:30:57 hmm, still seeing ?? Feb 19 22:32:00 hello everyone, does anyone know how to install a usb touchscreen for ubuntu arm? Feb 19 22:32:29 ATP, you plug it in Feb 19 22:32:43 yes I did so Feb 19 22:32:46 and use xserver-xorg-input-evdev (standard stuff) Feb 19 22:32:51 what model is it? Feb 19 22:32:54 i installed that too Feb 19 22:33:05 see is lsmod gives you the "usbtouchscreen" driver loaded Feb 19 22:33:06 it's LVDS 10" from chalk - elec Feb 19 22:33:20 thats the monitors stuff, not the touchscreen stuff Feb 19 22:33:33 no it's not there the usbtouchscreen Feb 19 22:33:57 I have a mimo 720 and i had to patch the touchscreen driver, because when i plugged it in it was rotated 180 deg Feb 19 22:33:57 i do have usbhid though Feb 19 22:34:14 mine doesnt even display anything Feb 19 22:34:33 The command " project-rootstock/rootstock --fqdn ubuntu --login ubuntu --password ubuntu --imagesize 5G --seed xubuntu-desktop --notarball" is right ? ? Feb 19 22:34:34 well, to be honest I havn't gotten mine to work in my x86 box Feb 19 22:34:46 but the kernel stuff works and loads, its a X prob Feb 19 22:34:48 :( Feb 19 22:34:51 X doesn't autoconfigure usb stuff Feb 19 22:35:03 so what do? Feb 19 22:35:06 works fine on my arm box Feb 19 22:35:12 write a proper xorg.conf Feb 19 22:35:25 when i try to Xorg -configure I get error Feb 19 22:35:29 do you get a /dev/fb0 ? Feb 19 22:35:35 "segmentation fault" Feb 19 22:35:37 ATP, as i said, it doesn't do it automatically Feb 19 22:35:46 (i've tried the same stuff) Feb 19 22:35:57 when you figure out how to dual monitor it I would like to know Feb 19 22:36:02 hehe nice to see someone was at my situation Feb 19 22:36:05 but yeah, I'm pretty sure it takes a proper x.org Feb 19 22:36:15 but I HAVE gotten mine to work on a headless arm box Feb 19 22:36:16 so do i make an xorg from scratch? Feb 19 22:36:27 xorg.conf* Feb 19 22:36:32 however as I said my touchscreen was 180 deg rotated and I had to patch the kernel driver Feb 19 22:36:59 ATP, please figure it out so I can use yours-- google arch displaylink Feb 19 22:37:08 hehe will do Feb 19 22:37:17 if only i can make an xorg.conf Feb 19 22:37:30 that works Feb 19 22:37:53 but you say this is LVDS, that is totally diffn't than my usb monitor (usb framebuffer too) Feb 19 22:37:58 so it might be a differn't problem Feb 19 22:38:08 should I get a sample one, or create a new one with Xorg -configure? Feb 19 22:38:11 do you have a /dev/fb0 ? Feb 19 22:38:11 excuse me .... Feb 19 22:38:16 project-rootstock/rootstock --fqdn ubuntu --login ubuntu --password ubuntu --imagesize 5G --seed xubuntu-desktop --notarball Feb 19 22:38:19 is right ? Feb 19 22:38:19 how do i see this Feb 19 22:38:21 if you do ATP that means kernel stuff is probably working Feb 19 22:38:42 yes i do have fb0 Feb 19 22:38:51 so what do i do now? Feb 19 22:38:55 Xorg -configure doesn't work, as it is the same thing as the automatic stuff Feb 19 22:39:20 so read up on it so i don't have to pls :)---oh wait, is that /dev/fb0 your main monitor or the touchscreen? Feb 19 22:39:32 see if you have TWO fb0, fb1 Feb 19 22:39:36 check dmesg Feb 19 22:39:38 i have 3 Feb 19 22:39:41 sec Feb 19 22:39:43 oh geeze Feb 19 22:39:48 figure out what is what Feb 19 22:39:52 i can see fb0 fb1 and fb2 Feb 19 22:39:56 ok checking now Feb 19 22:43:02 couldnt find which is which Feb 19 22:43:45 dmesg | grep fb Feb 19 22:43:57 unplug it and the plug it in---oh wait it is LVDS Feb 19 22:44:21 cat /var/log/kmsg* | grep /dev/fb Feb 19 22:44:43 *kern.log Feb 19 22:52:38 nothing Feb 19 22:52:50 with cat /var/log/kern.log* Feb 19 22:52:52 ? Feb 19 22:52:53 yes Feb 19 22:52:58 i tried both Feb 19 22:53:01 nothing comes up Feb 19 22:53:04 well then do with /var/log/dmesg Feb 19 22:53:36 nothing again Feb 19 22:53:53 hmmm Feb 19 22:54:06 i only have one fbcvt which says 1280x720@60 Feb 19 22:57:15 i check lsusb now Feb 19 23:02:54 meh it wont show there :( so maybe hardware issue :((( Feb 20 00:15:50 ATP you said LVDO which isn't usb Feb 20 00:16:19 try tail -f /var/log/kern.log and the unplug and replugin the device Feb 20 02:09:39 TheMuso: I would assume so. The alsa issue on panda was pretty much resolved with my patch to the ucm configs and a kernel patch. Unfortunately, we didn't have images for a week, so I only spotted it Friday. Feb 20 02:17:50 GrueMaster: Right, well I did announce a call for testing for alsa-utils, I know the ubuntu-audio-dev PPA is not building for ARM atm, but I thought you guys would have seen the cft, pulled and rebuilt at least... Feb 20 02:39:39 TheMuso: I have a TF101, I remember there was a problem with oneiric's alsa-utils and I fixed it by cherry-picking precise's... Feb 20 02:40:03 Something festival was triggering Feb 20 02:40:23 Probably unrelated, so ignore me and carry on **** ENDING LOGGING AT Mon Feb 20 03:00:00 2012