[00:17] <inuka> bryce: Do you now which package I need to install to get the poulsbo drivers in ubuntu?
[00:17] <inuka> bryce: Your packages worked correctly against the moblin kernel.
[00:18] <bryce> inuka, excellent to hear!
[00:19] <inuka> bryce: but since I was not abie to find the poulsbo drivers for the ubuntu kernel I was not able to test them against the ubuntu kernel
[00:19] <bryce> inuka, can you confirm from /var/log/Xorg.0.log that you're running psb version 0.2.6-0ubuntu1~psb1?
[00:20] <bryce> er, that should be psb2
[00:20] <inuka> bryce, I am not....  , where is the package posted? 
[00:20] <bryce> ok, so you installed and tested my libdrm2*~psb1, and the *-psb-0.2.6-0ubuntu1~psb2 driver, and X came up?
[00:21] <bryce> could you email me the Xorg.0.log from the system?
[00:21] <inuka> yes libdrm2 and xf driver, against moblin and moblin poulsbo kernel driver
[00:22] <inuka> if you point me to the package which contains the psb-kernel driver for ubuntu I can test against the ubuntu kernel
[00:22] <bryce> http://launchpadlibrarian.net/11274048/libdrm2_2.3.0-4ubuntu2%7Epsb1_lpia.deb, http://launchpadlibrarian.net/11330118/xserver-xorg-video-psb_0.2.6-0ubuntu1%7Epsb2_lpia.deb
[00:23] <inuka> bryce: thanks let me check it out
[00:23] <bryce> hmm, that I'm not so sure about...  however it should be one of the packages at https://launchpad.net/~ubuntu-mobile/+archive
[00:24] <inuka> bryce, I got those two..... but I need the kernel drivers the package is psb-kmd...
[00:27] <bryce> hmm
[00:27] <bryce> well, I don't see it there either.  My guess is that it's incorporated into one of the linux-ubuntu-modules packages, or perhaps linux-restricted-modules
[00:28] <bryce> let me check more
[00:28] <inuka> bryce, I will also check and try to find out, if not I will rebuild the kernel driver just to test
[00:32] <bryce> inuka, based on StevenK's suggestion of either l-r-m or l-u-m, I guess maybe try installing http://launchpadlibrarian.net/11327679/linux-restricted-modules-lpia_2.6.24.4.4%7E804um1_lpia.deb and http://launchpadlibrarian.net/10664305/linux-ubuntu-modules-2.6.22-14-lpia_2.6.22-14.41_lpia.deb
[00:33] <StevenK> bryce: One of them is 2.6.24 and the other is 2.6.22
[00:34] <bryce> huh, well that's what's on the PPA.  But I'm just pulling guesses out of my ass here.
[00:34] <inuka> bryce, I will try that if I dont get the kernel driver I will just build that we know for usre the changes will work against the ubuntu kernel
[00:35] <bryce> ok
[00:35] <StevenK> inuka, bryce: Give me a sec, I'll have a look.
[00:49] <bryce> inuka, here is the 2.6.24 lum:  https://edge.launchpad.net/ubuntu/hardy/+source/linux-ubuntu-modules-2.6.24/2.6.24-4.7
[00:53] <inuka> bryce, thanks I will chekc it out
[01:58] <bryce> inuka, luck so far?  I'm working on reverting my box from the C0 to B0 board
[02:00] <inuka> bryce, the kernel drivers installled through the linux-ubuntu-modules package seems bad.... I am recompiling the kernel drivers manually to see if I can get it to work
[02:03]  * bryce nods
[02:06] <bryce> yep, it's the board
[02:06] <bryce> wow
[04:06] <HappyCamp> StevenK, Is it something quick?
[04:07] <StevenK> HappyCamp: Quickish. It seems --bypass-rootstrap is a no-op in image-creator. Could you add that your list of stuff to investigate.
[04:07] <HappyCamp> Okay, is there a bug on that?
[04:08] <StevenK> Happy to file one, if you point me where
[04:08] <HappyCamp> https://bugs.launchpad.net/moblin-image-creator/ should do
[04:08] <HappyCamp> That way the other guy working on image creator also know.  Plus they will nag us about it in the bug meeting.
[04:08] <StevenK> HappyCamp: Aye. I'll point you at the bug number after I file it.
[04:08] <HappyCamp> Thanks!  I've got to go.
[04:09] <HappyCamp> Please do post the bug number and feel free to assign it to me HappyCamp so I get the emails right away.
[08:00] <dholbach> good morning
[10:41] <dholbach> Mithrandir, StevenK: is anything blocking the upload of bug 181304?
[10:41] <ubotu> Launchpad bug 181304 in bluez-gnome "[bluez-gnome] Please upgrade to new upstream version release" [Undecided,New] https://launchpad.net/bugs/181304
[10:42] <Mithrandir> dholbach: I don't think so.  StevenK should know.
[10:43] <StevenK> I thought I uploaded that ...
[10:43] <StevenK> Is that 0.15?
[10:43] <StevenK> Hrm. Seems I'm wrong
[11:02] <StevenK> dholbach: Sorry, I've uploaded it. I could have sworn I had already...
[11:03] <dholbach> StevenK: if it's done, that's cool :)
[12:51] <Mithrandir> StevenK: you noticed the hostname/sudoers problem earlier, did you commit a fix for it?
[12:51] <StevenK> No, since I wasn't happy with my solution.
[12:52] <Mithrandir> ok
[12:52] <Mithrandir> fair enough
[12:53] <StevenK> Would you like to see my solution?
[12:53] <Mithrandir> sure
[12:59] <StevenK> Mithrandir: http://paste.ubuntu.com/3576/
[13:00] <Mithrandir> seems sane enough to me, or we can just drop the mangling completely
[13:01] <Mithrandir> I've never understood why it's there in the first place.
[13:01] <StevenK> Changing the hostname at boot just seemed ... hacky
[13:02] <StevenK> And editing files with sed during boot made me feel dirty
[13:02] <Mithrandir> you could have used sed -i
[13:02] <StevenK> My sed foo isn't particularly strong
[13:03] <StevenK> That sort of thing should be done at the end of the flashing process, though. Then we don't need to do it during boot.
[14:36] <Mithrandir> amitk_: just testing the image before I give it to you so you don't waste more time than you need to.
[14:55] <Mithrandir> amitk_: try http://err.no/tmp/menlow_full_install-usb.img ?
[14:59] <Mithrandir> (and anybody else with a menlow system who wants to try it out)
[15:12] <amitk_> Mithrandir: downloading now
[18:44] <inuka_desk> ping amitk)
[18:44] <inuka_desk> ping amitk_
[18:44] <amitk_> inuka_desk: brb (10-15 minutes)
[18:45] <inuka_desk> amitk_ , is the poulsbo kernel driver in the ubuntu modules deb good. I installed it yesterday and seems bad. I tried the packages for both 22 and 24. 
[18:48] <inuka_desk> amik_ , this is against the ones in ppa
[18:49] <inuka_desk> ping bryce, I sent you my number give me a call 
[19:20] <inuka_desk> bryce, how are is the libdrm xf driver test going on. Looks like I will have to recompile the ubuntu mobile kernel to recompile the psb drivers
[19:21] <amitk_> inuka_desk: hi
[19:22] <inuka_desk> amitk_, hi did see my previous message I typed away without paying attention 
[19:22] <amitk_> inuka_desk: please delete all your projects and create a new one with the kernel and modules from today
[19:22] <bryce> inuka_desk: smagoun was able to get an image with all the required pieces in place, but X did not start up:
[19:22] <inuka_desk> bryce, did the screen blink?
[19:22] <bryce> http://paste.ubuntu-nl.org/52040/
 bryce: note that I installed the xorg-modules-xpsb package (which contains /usr/lib/xorg/modules/drivers/Xpsb.so ) in hopes that it would help. No luck though.
[19:23] <inuka_desk> amitk_, so are the updates in the moblin repo as well (if I use image creater create the ubuntu image will it bie sufficient or do I need to pull in from PPA)?
[19:23] <bryce> oh, I'm not sure if that's a log from *his* image, or from Mithrandir's
 bryce: I built your testing debs (psb) on hardy; they fail to display an image at all.  VESA works fine.
[19:24] <bryce>  bryce: confirmed on B0 and C0 boards.  What, if any, useful information can we give you?
[19:24] <amitk_> inuka_desk: I have synced everything to the moblin repo in the last kernel.
[19:25] <bryce> I'm attempting to boot this image myself
[19:25] <inuka_desk> amitk_ , thanks will do
[19:25] <inuka_desk> bryce, weird the log indicates that the kernel driver loaded correctly, which is the issue I was having.
[19:25] <inuka_desk> bryce, let me create a new image and see how far I get.
[19:26] <amitk_> inuka_desk: bryce: I urge you create a new project from scratch with the new kernel. It will avoid us chasing ghosts...
[19:29] <bryce> amitk-bbl: I've been having some trouble getting image-creator to run, but if people point me at img's, I'll be happy to boot and play with them
[19:30] <amitk-bbl> bryce: are you running the one from git or from the hardy repo?
[19:30] <bryce> I'm about to boot the one Mithrandir made earlier
[19:31] <amitk-bbl> bryce: i meant image-creator
[19:31] <bryce> oh, I've tried the one in gutsy and the one from the PPA
[19:32] <bryce> I also have a snapshot I checked out a long time ago that used to work, but it's not now.
[19:32] <bryce> I'm suspecting a configuration issue maybe
[19:33] <bryce> but it just crashes on startup so it's a bit hard to identify what's going wrong with it
[19:33] <amitk-bbl> bryce: gutsy? I am working with Hardy here
[19:33] <amitk-bbl> inuka_desk: are you working with gutsy too?
[19:34] <inuka_desk> amitk-bbl, I tried both before. Right now I will use what ever is on the moblin repository.
[19:34] <bryce> as I was given to understand, the target is to get the X bits working on gutsy
[19:34] <bryce> but I have plenty of hardy systems if things work better there
[19:35] <amitk-bbl> bryce: My focus is to get hardy working
[19:35] <bryce> interesting
[19:36] <amitk-bbl> inuka_desk: I am not sure what you are testing. Aren't you testing the Ubuntu kernel with xorg driver? What are you taking from moblin?
[19:36] <amitk-bbl> bryce: AFAIK, the image provided by Mithrandir is Hardy based
[19:36] <inuka_desk> amitk-bbl, yes thats what I am testing, I am talking about the image-creator ubuntu-kernel fset
[19:37] <amitk-bbl> inuka_desk: aah.. fair enough. :)
[19:38] <amitk-bbl> inuka_desk: make sure it installs linux-image-lpia-2.6.24-4.7
[19:38] <inuka_desk> amitk-bbl, ok I will double check it.
[19:48] <bryce> I've got mithrandir's image installed and booted, and I see it's failing at X
[19:49] <bryce> I'm seeing the ubuntu logo from the startup screen but it's corrupted
[19:50] <bryce> amitk-bbl: ok, some earlier discussions focused on making -psb work on gutsy had me confused that the objective was to get this working on gutsy.  davidm's straightened me out that we're aiming for hardy.
[19:51] <amitk-bbl> bryce: good to be on the same page :)
[19:52] <bryce> the -psb includes a hack that is really only appropriate for gutsy.  So I'm wondering if removing that would make things work better.
[19:52] <bryce> I'll start there.
[19:54] <bryce> ok, booted with vesa...  looks like X works.  The top bar is empty though.  Interesting.
[20:02] <bryce> hmm, no network on this img
[20:40] <amitk-bbl> bryce: the top bar was empty for me too, and nm-applet doesn't work due to some D-bus permission errors
[20:41] <bryce> amitk-bbl: does networking work for you?
[20:41] <bryce> route is empty
[20:45] <amitk-bbl> bryce: no it doesn't. NM is somehow broken...
[20:47] <bryce> hrm
[20:48] <bryce> amitk-bbl: any way to work around it?
[20:50] <amitk-bbl> bryce: you are trying with the usb-ethernet thing that came with the board, right?
[20:50] <bryce> yes
[20:51] <amitk-bbl> bryce: and you don't happen to have another make? 2.6.24 broke the asix driver - totally unrelated, but tragic for our efforts...
[20:52] <bryce> nope
[20:52] <amitk-bbl> I wonder if we can setup IP-over-usb
[20:53] <bryce> hmm, the date on libexa looks correct, and different from -psb's date
[20:53]  * amitk reads up
[20:58] <smagoun> bryce: I was able to use a USB key to install .debs with Mithrandir's image. The key shows up at /dev/sdb
[20:59] <bryce> smagoun: yeah that's what I'm looking at doing; do you have a list of the .debs you tried out?
[20:59] <bryce> (and where they came from?)
[20:59] <smagoun> bryce: On Mithrandir's image or our gutsy build?
[21:00] <bryce> on Mithrandir's image
[21:00] <smagoun> I didn't do much with Mithrandir's image, just tried the xorg-modules-xpsb .deb from our private repo.
[21:01] <smagoun> I did try adding Section "DRI" Mode 0666 EndSection to xorg-crownbeach.conf since Intel said that was required at one point, but no uck
[21:01] <smagoun> s/uck/luck
[21:03] <amitk> bryce: you probably don't have USB host-to-host cables, so I can't think of a better way that throught the usb key
[21:03] <bryce> hrm
[21:07] <bryce> well, let me see if I can get some better debug info on the X lockup first...
[22:22] <inuka> amitk: did you update the psb kernel drivers for gutsy and hardy or just hardy.
[22:29] <amitk> inuka: the gutsy ppa does not have the latest drivers, but the main gutsy kernel git repo now has the updated drivers. They will be built during the next security release though.
[22:43] <inuka> amitk, so if I build an image for gutsy it will grab everything correctly, or do I need to get the source and rebuild?
[22:49] <davidm> amitk, when is the next security release happening do you know?
[22:50] <davidm> If its going to be a while should we just dump the drivers into the PPA until the security upgrade?
[22:51] <bryce> X debugging tips/photos for UME:  http://bryceharrington.org/drupal/node/31
[23:15] <amitk> davidm: I was planning on working on that as soon as the hardy work is done, tomorrow or possible the day after
[23:16] <amitk> inuka: you will need to build from the gutsy git tree. If you work with Hardy though, you have packages ready
[23:18] <davidm> amitk, cool
[23:27] <GrueMaster> So, can we use MIC to build an image from Hardy yet?
[23:28] <inuka> amitk, thanks. 
[23:30] <inuka> bryce, fyi your B0 will need a bios updae if not it will freeze.
[23:35] <bryce> inuka: why's this?
[23:36] <bryce> inuka: and at what point will the freeze appear?
[23:36] <inuka> bryce, if you use todays image-creator it has some taken out some boot options due to a bios fix. 
[23:36] <inuka> bryce, the freeze will be before x starts.
[23:37] <inuka> bryce, the freeze you have experianced is not it.
[23:38] <bryce> ok
[23:38] <bryce> inuka: is there a page describing the bios update and/or downloadable?
[23:41] <GrueMaster> A word of caution on this:  Not every system is running with the AMI bios.
[23:42] <inuka> bryce, I was told that you should be getting the communication with an external link...
[23:42] <GrueMaster> It may be prudent to have an additional grub menu item.
[23:42] <inuka> let me check with our PM if I can send you the files directly.
[23:58] <inuka> amitk, I tried to test using the hardy image created through image-creator, kernel drivers seem to be bad