**** BEGIN LOGGING AT Mon Jul 12 02:59:57 2010
Jul 12 07:02:29 morgen
Jul 12 11:39:42 hello everybody
Jul 12 11:40:01 I'm trying to use rootstock on ubuntu lucid but I have a blocking problem...
Jul 12 11:40:45 anybody have a suggestion?
Jul 12 11:41:04 the error is: /usr/bin/rootstock: line 282: 6890 Segmentation fault qemu-system-arm $QEMUOPTS -append "${APPEND}" > $QEMUFIFO 2>&1
Jul 12 11:41:41 it seems a problem related to qemu itself...
Jul 12 11:46:50 anybody use rootstock from ubuntu lucid?
Jul 12 12:00:15 anybody use rootstock with ubuntu lucid?
Jul 12 12:30:48 furibondox: You may want to report this into launchpad.
Jul 12 12:31:58 vstehle: I've just reported... https://bugs.launchpad.net/ubuntu/+source/rootstock/+bug/570588 (item 13)
Jul 12 12:32:01 Launchpad bug 570588 in rootstock (Ubuntu) (and 1 other project) "qemu-system-arm can not handle more than 256M in versatile machine mode using the -m option (affects: 2) (heat: 53)" [Undecided,Invalid]
Jul 12 12:33:12 I just would like to know if someone experienced the same behaviour and have found a solution/workaround...
Jul 12 12:34:47 if you see the exact same bug, just revert your changes to the rootstock script
Jul 12 12:40:22 ogra: which change?
Jul 12 12:40:51 furibondox, did you read the bug before commenting ?
Jul 12 12:40:57 yes
Jul 12 12:41:05 its about someone who hacked his rootstock script to use 512M
Jul 12 12:41:16 so revert that and it will work
Jul 12 12:42:26 I've also tried to use 512M changing the rootstock script but it fails again
Jul 12 12:43:05 well, qemu cant use 512M
Jul 12 12:43:10 thats what the bug is about
Jul 12 12:44:53 sorry ogra, I know that but I've read some bug report on google describing the same error but in different threads... and I took the 570588 to add a comment
Jul 12 12:45:07 may be is not the more approriate item opened
Jul 12 12:45:47 well, if you changed the script to use 512M thats the bug, if you didnt, its not that bug and should be filed as a new one
Jul 12 12:47:23 I tell you my tests: 1) with 512M 2) with 256M 3) with more seeds 4) with only one seed
Jul 12 12:47:27 the result is the same
Jul 12 12:48:31 and you are onyl using packaged versions of rootstock, qemu and friends ?
Jul 12 12:48:53 * ogra knows that pleanty of people use rootstock under lucid and it works for them
Jul 12 12:50:57 ogra: just to let you know that your udev script worked fine in the end. Can't think I told you.
Jul 12 12:51:13 * ogra hugs berco
Jul 12 12:51:15 perfect !
Jul 12 12:57:16 yes ogra, all my packages (qemu, rootstock, debootstrap etc) come from the lucid repository
Jul 12 12:57:57 in your pm you used rootstock-native, thats definately not packaged
Jul 12 12:59:44 yes sorry... it was just a test...
Jul 12 13:01:51 ii rootstock 0.1.99.3-0ubuntu1 shellscript to create armel rootfs tarballs
Jul 12 13:02:48 May be there's something wrong with my command line?
Jul 12 13:03:07 sudo rootstock -f NGP --seed setserial,openssh-server,ubuntu-minimal -i 1G --serial ttyS2 --doswap --swapsize 256 --restore-package-cache
Jul 12 13:03:27 setserial should be included in ubuntu-minimal, beyond that all looks fine
Jul 12 13:03:42 and adding setserial shouldnt cause issues
Jul 12 13:03:47 ok
Jul 12 13:04:58 but, as far as you know, do you think that is a qemu problem or rootstock problem?
Jul 12 13:05:35 if you think that is a rootstock problem I can try to uninstall/re-install qemu and try again
Jul 12 13:05:41 what do you think?
Jul 12 13:07:43 well, qemu segfaults
Jul 12 13:07:52 its definately not a rootstock problam
Jul 12 13:07:57 *problem
Jul 12 13:08:36 ok
Jul 12 13:08:45 I try to remove all and reinstall
Jul 12 13:09:31 ogra: it's not long ago when I told you how to spell definitely :-)
Jul 12 13:10:01 ukleinek, i blame the heat
Jul 12 13:10:12 * ogra melts slowly
Jul 12 13:10:13 ogra: so Berlin is hot, too?
Jul 12 13:10:23 ukleinek, kassel here
Jul 12 13:10:55 28°C in my office, 36°C outside
Jul 12 13:10:55 ogra: oh, Kassel, I thought you'd live in Berlin
Jul 12 13:11:02 ogra: similar here
Jul 12 13:11:14 i'd love to ... (who wants to live in kassel anyway)
Jul 12 13:11:35 ogra: so why do you?
Jul 12 13:11:51 b-----i------g house
Jul 12 13:11:53 free living :)
Jul 12 13:11:55 :-p
Jul 12 13:12:18 no rent, solar heating system ... major cost factor :)
Jul 12 13:12:46 * ukleinek has a solar heat here for free, too
Jul 12 13:13:54 ogra: I'm retring...
Jul 12 13:16:09 morning
Jul 12 13:21:17 hm, another qemu segfault
Jul 12 13:21:24 interesting that this is happening with lucid
Jul 12 13:22:03 ogra: was finally able to create the rootfs as user, but still have many issues to solve
Jul 12 13:22:23 rsalveti, might be realted to amd64 systems
Jul 12 13:22:33 rsalveti, good to hear :)
Jul 12 13:22:51 first, fuseext2 is incredibly unstable =\
Jul 12 13:23:18 I can create the same image many times, just with 'ro', and get different results everytime
Jul 12 13:23:37 lots of files get the wrong size and data
Jul 12 13:24:01 so just after running the second stage, to be able to test, I mounted as loop, until we get this solved
Jul 12 13:24:14 k
Jul 12 13:24:18 ogra: but my biggest problem is the seg fault that I'm getting most of the time
Jul 12 13:24:29 qemu segfault too ?
Jul 12 13:24:34 ogra: yep :-(
Jul 12 13:24:38 crap
Jul 12 13:24:41 just after running the second stage
Jul 12 13:24:46 x86 or amd64 ?
Jul 12 13:24:55 amd64, this could be the issue
Jul 12 13:24:58 yeah
Jul 12 13:24:59 will try on x86 to see
Jul 12 13:25:20 sebjan: Ping
Jul 12 13:25:30 ogra: see comment 54 on bug 532733
Jul 12 13:25:38 Launchpad bug 532733 in qemu-kvm (Ubuntu Lucid) (and 2 other projects) "apt/dpkg in qemu-system-arm hangs if a big task is installed (affects: 7) (dups: 1) (heat: 79)" [High,Incomplete] https://launchpad.net/bugs/532733
Jul 12 13:25:55 rsalveti, that bug isnt about segfaults
Jul 12 13:26:00 yeah, I know
Jul 12 13:26:13 but many people reported about the segfault while trying to reproduce it
Jul 12 13:26:34 that bug slowly turns into a mess :(
Jul 12 13:26:35 that's why I posted there, cause it can be similar to what people was getting
Jul 12 13:26:47 bug for sure, it's different
Jul 12 13:26:52 the hang doesnt produce any segfaults at all
Jul 12 13:27:09 ogra: are you using x86?
Jul 12 13:27:16 upstream already refused to look at it because of the confusing comments
Jul 12 13:27:18 yes
Jul 12 13:27:23 * rsalveti wasn't able to get just the 'hang'
Jul 12 13:27:32 oh, ok
Jul 12 13:28:05 the hang only shows up if you install a big task like ubuntu-desktop or ubuntu-netbook
Jul 12 13:28:17 dpkg hangs at some point
Jul 12 13:28:29 ogra: yeah, but I'm getting the seg fault before that :-), but I'm using amd64
Jul 12 13:28:33 your segfault seems userspace related
Jul 12 13:28:38 will see with x86
Jul 12 13:32:18 ogra: same error: http://pastebin.ca/1898986 :-(
Jul 12 13:32:45 furibondox: how are you calling rootstock?
Jul 12 13:33:04 sudo rootstock -f NGP --seed openssh-server,ubuntu-minimal -i 1G --serial ttyS2 --doswap --swapsize 256 --restore-package-cache
Jul 12 13:33:24 from ubuntu lucid
Jul 12 13:33:55 all packages (qemu, rootstock, etc...) came from the lucid repository
Jul 12 13:34:28 furibondox: are you running on x86 or amd64?
Jul 12 13:34:53 x86
Jul 12 13:34:54 furibondox: ok, can try to reproduce it here, but many people did run rootstock without this issue on lucid
Jul 12 13:35:47 the only unusual component is that my lucid x86 runs under vmware
Jul 12 13:35:59 heh
Jul 12 13:36:12 :-)
Jul 12 13:36:14 thats probably something you should have told in the beginning :)
Jul 12 13:36:30 not sure if qemu can run inside vmware
Jul 12 13:36:41 yeah, could be the problem
Jul 12 13:36:53 some times ago I tested qemu inside vmware w/o problems
Jul 12 13:37:00 i know qemu cant run inside a kvm instance
Jul 12 13:37:14 or insice vbox
Jul 12 13:37:17 *inside
Jul 12 13:37:28 ogra: uh?
Jul 12 13:37:42 I thought qemu could work just fine in kvm
Jul 12 13:37:44 lool, can it now ?
Jul 12 13:37:53 soren told me it cant
Jul 12 13:37:56 First time I heard it can't
Jul 12 13:38:04 You cant use qemu acceleration though
Jul 12 13:38:05 so i never bothered to try to stack qemu instances
Jul 12 13:38:21 hey asac
Jul 12 13:38:23 You can't run kvm in QEMU though
Jul 12 13:38:31 omg
Jul 12 13:38:36 the heat is on
Jul 12 13:38:40 warm here, eh ?
Jul 12 13:38:45 * ogra grins
Jul 12 13:39:09 ok... so your suggestion is to try within physical ubuntu installation, right?
Jul 12 13:39:46 furibondox: yep, I'm trying it here on x86 with your command line
Jul 12 13:39:49 if you have one around, i would suggest that
Jul 12 13:40:00 tnx rsalveti
Jul 12 13:46:04 lag: pong
Jul 12 13:46:11 * ogra goes to find some icecream
Jul 12 13:46:18 sebjan: HI
Jul 12 13:46:20 Hi*
Jul 12 13:46:33 What's the latest with the Syslink driver?
Jul 12 13:46:44 Is it going to make our build?
Jul 12 13:47:45 I have tested with your last patch update, and could see that the modules where automatically loaded, as expected
Jul 12 13:48:33 we have no solution yet for the issues when it is built as modules. We may have to re-test with syslink v2 and debug on this version rather than on the current one
Jul 12 14:02:37 rsalveti: can you tell me if the building is finished without errors?
Jul 12 14:02:56 furibondox: still going
Jul 12 14:03:22 going to run the full vm now
Jul 12 14:03:38 ok
Jul 12 14:05:35 sebjan: Thanks for the update
Jul 12 14:06:04 sebjan: Do any of your chips have parallel ports?
Jul 12 14:17:22 lag: I don't think we have parallel ports in the OMAP per se, but it can be "emulated" with GPIO if needed.
Jul 12 14:25:49 rsalveti: is finished now?
Jul 12 14:26:41 furibondox: not yet, but it's just finishing the full emulation part, no crash until now
Jul 12 14:26:48 good
Jul 12 14:31:54 ogra: Hey
Jul 12 14:32:01 lool, yup
Jul 12 14:32:06 ogra: Do you folks intend to include x-loader + u-boot in omap pre-installer images?
Jul 12 14:32:12 *pre-installed
Jul 12 14:32:23 yep
Jul 12 14:32:32 ogra: Ok; is this tracked in a bug/blueprint somewhere?
Jul 12 14:33:12 err, sorry, was distracted
Jul 12 14:33:25 we *do* already include both
Jul 12 14:34:12 vstehle: Thanks, but there's no need. The parport_pc driver is crashing your devices.
Jul 12 14:34:37 lool, https://blueprints.edge.launchpad.net/ubuntu/+spec/preinstalled-sd-card-images-for-omap
Jul 12 14:34:49 lool, "Change armel+omap debian-cd scripts to create a two partition image with first partition being vfat with proper bootloader setup"
Jul 12 14:36:39 ogra: Hmm
Jul 12 14:36:40 lool, dailies are here: http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/ (still lacking web indicies, manifest and proper md5sum stuff, but its on teh list)
Jul 12 14:36:57 ogra: Yes, this didn't boot with qemu for me
Jul 12 14:37:08 * ogra never tried it with qemu
Jul 12 14:37:27 did you dd it to an SD card and ran qemu with it as hdd1 ?
Jul 12 14:37:33 ogra: My ports-dev PPA has an updated package
Jul 12 14:38:04 you will definately need a real disk for it
Jul 12 14:38:35 since it tries to expand to the full disk size, it wont work if it cant expand to have free diskspace
Jul 12 14:39:05 we only leave 10M in the root partition that are eaten up ny the ext3fs journal
Jul 12 14:39:12 s/ny/by/
Jul 12 14:39:44 so even if you would get it to boot, it would need to be dd'ed to a bigger sized (i'd recommend 4G) image
Jul 12 14:40:34 lool, your qemu is omap3 i guess, we only include the actual beagleboard MLO in the image atm
Jul 12 14:40:42 ogra: I did a bunzip2
Jul 12 14:40:46 and ran it with qemu -sd
Jul 12 14:40:53 so if you dont strictly emulate a beagle that might be the prob
Jul 12 14:41:02 ogra: My QEMU boots the Angstrom beagleboard image somewhat
Jul 12 14:41:11 Well into kernel boot messages for instance
Jul 12 14:41:28 and ours ? where does it stop ?
Jul 12 14:41:48 * ogra is in the process of updating to x-loader 1.4.4 from 1.4.3 ... probably that helps
Jul 12 14:42:29 i didnt touch the omap3 stuff since pre-A2 but it definately works on real HW
Jul 12 14:42:41 * ogra focuses on omap4 atm
Jul 12 14:43:51 lool, angstrom images are not partitioned, they are tarballs, no ?
Jul 12 14:44:28 ogra: they are
Jul 12 14:44:40 unless something changed significantly recently
Jul 12 14:44:45 ogra: you mean 'narcissus' ones I assume
Jul 12 14:45:00 hrw, no idea what lool used above for qemu tests
Jul 12 14:45:35 neither do I
Jul 12 14:46:18 i know for sure our images work on actual HW and i would have never gotten the idea to try one of them in qemu :)
Jul 12 14:46:44 especially since its quite some hassle you have to do with the image sizing
Jul 12 14:46:55 if you dont actually dd to an SD card
Jul 12 14:47:16 ogra: No, it's a partitioned SD card image
Jul 12 14:47:24 Angstrom-Beagleboard-demo-image-glibc-ipk-2010.3-beagleboard.sd-image-2GiB.img1 * 1 9 72261 c W95 FAT32 (LBA)
Jul 12 14:47:27 Angstrom-Beagleboard-demo-image-glibc-ipk-2010.3-beagleboard.sd-image-2GiB.img2 10 240 1855507+ 83 Linux
Jul 12 14:47:28 where did you get that ?
Jul 12 14:47:38 i only know the tarballs
Jul 12 14:47:53 I know that OE can generate any type of image
Jul 12 14:47:55 the partitioning seems to be identical to ours though
Jul 12 14:48:13 and since we use the same code i bet it actually is :)
Jul 12 14:48:42 so the only difference can be xloader or uboot if you dont get any serial output
Jul 12 14:49:39 our omap3 x-loader package is still at 1.4.3 with the XM patches on top ... in 1.4.4 the XM patches are included, i'll update it this week
Jul 12 14:49:52 lool, so try an image from the end of this week
Jul 12 14:50:08 so we can exclude MLO here
Jul 12 14:50:22 its my only explanation
Jul 12 14:50:41 lool, you can also try to replace the binaries in the vfat and see
Jul 12 14:51:05 furibondox: yep, no problem
Jul 12 14:51:08 furibondox: same arguments
Jul 12 14:51:15 furibondox: vmware can be your problem
Jul 12 14:51:49 thank you very much rsalveti
Jul 12 14:51:55 np
Jul 12 14:52:08 I will try with a native ubuntu installation
Jul 12 14:52:34 ogra: I tried the image from yesterday evening
Jul 12 14:52:52 lool, cant be, the livefs builder was broken since thu :)
Jul 12 14:53:00 rsalveti: I've a question... do you have tested with a lucid?
Jul 12 14:53:03 ogra: I grabbed the "current" image from yesterday
Jul 12 14:53:09 it might be a stale one
Jul 12 14:53:18 lool, as i said above, i'll update x-loader-omap3 this week
Jul 12 14:53:25 ogra: Ok, thanks
Jul 12 14:53:35 until then try to replace the binaries in our image witrh the angstrom ones
Jul 12 14:53:41 and see if it boots then
Jul 12 14:54:30 furibondox: yep
Jul 12 14:54:37 our vfat is exactly 9 clinders and "W95 FAT32 (LBA)" so there shouldnt be a difference apart from MLO and uboot
Jul 12 14:55:00 rsalveti: can you also send me the output of a dpkg -l of your pc?
Jul 12 14:55:02 furibondox: 10.04.1
Jul 12 14:55:16 furibondox: sure, 1 sec
Jul 12 14:55:45 I leave my email in pm
Jul 12 14:55:58 * ogra takes a break and hunts for more icecream
Jul 12 14:57:52 furibondox: http://paste.ubuntu.com/462558/
Jul 12 14:58:08 tnx
Jul 12 15:40:46 lag: did you got working screen finally on panda?
Jul 12 15:41:02 Nope
Jul 12 15:41:08 TI are working on it
Jul 12 15:41:19 I've been working on something else
Jul 12 15:41:59 lag: maybe http://gitorious.org/pandaboard/kernel-omap4/blobs/L24.6_panda/drivers/video/omap2/dss/hdmi.c will help you to find working hdmicode value
Jul 12 15:42:27 or http://omappedia.org/wiki/Bootargs_for_enabling_display
Jul 12 15:42:39 we had all that in the dicussing last week :)
Jul 12 15:43:15 *discussion
Jul 12 15:43:18 ;)
Jul 12 15:43:44 Finding a working hdmicode is not the issue
Jul 12 15:43:49 right
Jul 12 15:44:01 When I use sysfs almost all of them work for me and my monitor
Jul 12 15:44:39 When I use the cmdline arguments, the best I can hope for is a fuzzy screen and an "out of range" message from my monitor
Jul 12 15:45:34 * ogra just thinks its a matter of the right glasses
Jul 12 15:45:47 they should just ship them with the boards ;)
Jul 12 15:55:25 Hello, I am following these instructions to get a rootfs for ARM https://wiki.ubuntu.com/ARM/RootfsFromScratch, I compiled a kernel and generated a zImage, when I try to run qemu (as specified in the tutorial) I got a black screen, I tried adding -d options file.log at the end of the command to get the output but I got nothing, am I missing something?
Jul 12 15:55:38 I changed the -cpu option for amr11mpcore,
Jul 12 15:55:43 thanks in advanced :D
Jul 12 15:58:05 fjrivash, for which release are you building your rootfs ?
Jul 12 15:58:19 lucid
Jul 12 15:58:34 wont run with arm11mpcore
Jul 12 15:58:46 lucid is built for armv7
Jul 12 15:59:02 arm11mpcore is an extended armv6 as i understand it
Jul 12 15:59:51 ohhh I see.
Jul 12 16:00:02 Yes it is compatible with armv6kz
Jul 12 16:00:17 use the binary kernel from the tutorial
Jul 12 16:01:29 well see : I did the first step of this section "Building a root filesystem image instead of a tarball" and after that compiled my own kernel and tried booting : it did not work. After that I got that image and is the same, that is why I am asking.
Jul 12 16:03:44 is there a way to build a rootfs of a release wich support armv6 (or compatible) using rootstock?
Jul 12 16:04:26 fjrivash: Try using Karmic or Jaunty.
Jul 12 16:04:42 Otherwise you are kind of stuck with debian.
Jul 12 16:05:00