**** BEGIN LOGGING AT Thu Jun 24 02:59:58 2010 Jun 24 04:07:47 damn it, just missed Martyn Jun 24 04:35:58 any softkey pad application available for arm... Jun 24 06:58:07 NCommander, so your gobject-introspection "fix" ... Jun 24 06:59:09 ogra: yes? Jun 24 06:59:22 NCommander, did you check the dependencies and what changed in them between 0.6.12-1 and 0.6.12-1ubuntu1 ? Jun 24 06:59:48 ogra: dyfet did. Jun 24 06:59:48 since this is not a gobject-introspecion issue but an issue with any build dep Jun 24 07:00:13 i'd rather see us fixing the real issue than changing the code that didnt change before the breakage Jun 24 07:00:30 looking at the deps i'd suspect glib Jun 24 07:00:48 bison, flex and friends didnt change between the two uploads Jun 24 07:00:49 ogra: we need gobject-introspection fixed, you've already said that, I'm glad to hunt for the actual cause of the breakage, but I'm happy to work around it Jun 24 07:01:04 ogra: dyfet said he checked it Jun 24 07:01:07 i'm not sure it wont break it on all other arches Jun 24 07:01:20 ogra: I threw it in a PPA, built on everything Jun 24 07:01:21 you are changing XML that hadnt changed Jun 24 07:01:25 (devirtualized PPA) Jun 24 07:01:38 I only changed the XML to reflect the changed vairable names in the C code Jun 24 07:01:52 yes, but does that change work on all other arches ? Jun 24 07:02:02 * ogra wouldnt even know how to verify that Jun 24 07:02:29 ogra: I ran the test suite on all arches Jun 24 07:02:37 in any case something in a dep changed, just hacking variable definitions in the gobject code doesnt seem like an appropriate fix Jun 24 07:02:48 i'm not talking about the test suite Jun 24 07:02:57 but about the binaries using the code Jun 24 07:03:02 telepathy for example Jun 24 07:03:16 ogra: I didn't change any code expect code used in the test suite Jun 24 07:03:16 was seb128 pulled into the discussion by dyfet as i asked ? Jun 24 07:03:43 ogra: I didn't see any communication from dyfet to seb128. I was waiting for him to show up to pin ghim on desktop Jun 24 07:04:11 hmm, i asked dyfet a week ago at the meeting to discuss it with seb :/ Jun 24 07:04:22 (and agin this week) Jun 24 07:26:03 morning Jun 24 07:41:50 dialpad application in ubuntu avaliable.. Jun 24 11:07:36 NCommander, do you remember the former name of the "source" commnad in old u-boot ? Jun 24 11:07:50 seems enabling hush shell didnt get me source Jun 24 11:08:07 ogra: TI's u-boot might predate that command being added Jun 24 11:08:15 its 1.1.4 Jun 24 11:08:22 Marvell was 1.3.4 Jun 24 11:08:27 gah Jun 24 11:08:42 thats really bad Jun 24 11:08:45 your trying to execute the boot.scr, right? Jun 24 11:08:49 yep Jun 24 11:08:57 do imi *offset* where you loaded it Jun 24 11:09:06 see if panda's u-boot recongizes it as a boot script Jun 24 11:09:36 PANDA # imi 0x80300000 Jun 24 11:09:37 ## Checking Image at 80300000 ... Jun 24 11:09:37 Image Name: Ubuntu boot script Jun 24 11:09:37 Image Type: ARM Linux Script (uncompressed) Jun 24 11:09:37 Data Size: 163 Bytes = 0.2 kB Jun 24 11:09:37 Load Address: 00000000 Jun 24 11:09:39 Entry Point: 00000000 Jun 24 11:09:43 Verifying Checksum ... OK Jun 24 11:09:45 hrm Jun 24 11:09:45 PANDA # Jun 24 11:09:47 yep Jun 24 11:09:59 possible autoscr Jun 24 11:10:05 that might have been the old command for source Jun 24 11:10:23 (it shouldbe in help)_ Jun 24 11:10:23 nope Jun 24 11:10:27 its not Jun 24 11:10:37 (in help) Jun 24 11:11:02 i see test and other hush commands Jun 24 11:12:27 crap Jun 24 11:12:51 its possible that its just not implemented Jun 24 11:12:56 Which means we're screwed Jun 24 11:13:00 (partially) Jun 24 11:13:17 i see "go" but that hangs x-loader if i run it Jun 24 11:13:21 it wouldn't be super-difficult to backport a the necessary commands Jun 24 11:13:28 go is used for jumping to an offset Jun 24 11:14:10 yeah Jun 24 11:14:32 autoscr is there on blaze? Jun 24 11:14:34 * NCommander hasn't checked Jun 24 11:14:38 (or source) Jun 24 11:15:29 hmm, gumstix uses 1.1.4 and has autoscr Jun 24 11:16:05 sounds like something went horribly wrong Jun 24 11:16:42 * NCommander grabs the source Jun 24 11:29:56 aha ... i see (~CFG_CMD_AUTOSCRIPT... Jun 24 12:00:04 PANDA # help Jun 24 12:00:05 ? - alias for 'help' Jun 24 12:00:05 autoscr - run script from memory Jun 24 12:00:08 I WIN !!! Jun 24 13:43:24 GrueMaster ? Jun 24 14:22:17 mpoirier: pong. Still waking up, though. Jun 24 14:22:40 GrueMaster: good morning. Jun 24 14:22:59 your beagle board, it is a C4 ? Jun 24 14:23:37 I assume so. Jun 24 14:25:45 Yes. Store bought, as it were. Jun 24 14:26:59 did you upgrade your MLO and u-boot ? Jun 24 14:27:17 or are they stock ? Jun 24 14:27:45 I believe I am running what is on ogra's image. Jun 24 14:28:06 do me a favor please. Jun 24 14:28:28 boot the board (power cycle) and give me the date you get on the very first line that come up on the screen. Jun 24 14:28:31 mine is: Jun 24 14:28:39 Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24) Jun 24 14:31:37 same Jun 24 14:31:49 That's the xloader Jun 24 14:31:53 yes, indeed. Jun 24 14:32:03 Jun 24 14:32:09 please confirm that you have used the USB EHCI on this board. Jun 24 14:32:27 Huh? Jun 24 14:32:47 the normal looking USB port, next to the SD card slot. Jun 24 14:33:20 of course. That's how I have keyboard, mouse, ethernet, etc. Jun 24 14:34:02 davidm set me a C4 two weeks ago and USB did not work off the box. Jun 24 14:34:13 Ok I'm thinking, hw failure happens... Jun 24 14:34:15 I'm fully hooked up here. Only thing not in use is the otg port. Jun 24 14:34:21 and svideo. Jun 24 14:34:28 Yes, don't use OTG. Jun 24 14:34:44 so I purchase one from Sparkfun and got it yesterday... Jun 24 14:34:51 it too has a problem with USB. Jun 24 14:35:06 I'm aware of that. Jun 24 14:35:21 that is interesting - aware of what ? Jun 24 14:35:32 USB problems with bb ? Jun 24 14:35:33 Bug #566645 Jun 24 14:35:35 Launchpad bug 566645 in linux-ti-omap (Ubuntu Maverick) (and 2 other projects) "OTG configuration is broken on omap kernel (affects: 2) (heat: 64)" [High,Confirmed] https://launchpad.net/bugs/566645 Jun 24 14:35:59 indeed, OTG is not in yet. Jun 24 14:36:24 But both my C4 boards, USB EHCI is not responsive. Jun 24 14:36:43 I was wondering if you were seeing the same thing... Jun 24 14:36:43 Are you running with a powered hub? Jun 24 14:36:48 mpoirier, two boards with fail sound funny, perhaps your USB hub is not working with the hardware? Jun 24 14:37:12 It does work when hooked up to the C2 board... Jun 24 14:37:33 Where are you powering your board from? Jun 24 14:37:55 power supply, not OTG. Jun 24 14:38:05 ok. Jun 24 14:38:28 I'm wondering if u-boot isn't doing something special to enable the port. Jun 24 14:38:34 Something I wouldn't have. Jun 24 14:38:53 two failure on two boards, this isn't right. Jun 24 14:39:56 I have my system booting the uboot from nand when I am running lucid. It is the stock uboot. When I am running maverick, it runs a newer version. Both work fine with USB. Jun 24 14:40:50 The maverick uboot, it is on SD card ? Jun 24 14:41:32 yes. Jun 24 14:42:01 Please email it to me... Jun 24 14:42:36 is there another channel for non ARM ubuntu netbook issues ? Jun 24 14:43:18 Actually, just pull down ogra's test image. http://projects.gnome.org/NetworkManager/developers/ Jun 24 14:43:30 rsavoye: #ubuntu-mobile Jun 24 14:43:40 thanks Jun 24 14:43:46 or #ubuntu-desktop may help Jun 24 14:44:13 I was trying to get a USB install to a Sylvania G netbook to work, it can't find vesa Jun 24 14:49:56 GrueMaster, #ubuntu-mobile is dead Jun 24 14:50:22 netbook issues go to #ubuntu-desktop or for the efl version to us Jun 24 14:50:57 it may be dead, but there is a pile of people Jun 24 14:51:21 yes, we're in the process of either closing it or finding a new adopter Jun 24 14:51:30 the ubuntu mobile team doesnt exist anymore Jun 24 14:52:02 ah... that;s right Jun 24 15:14:12 mpoirier: if you have any kernel testing that needs to be done, just ping me and I can test in my environment. I would like to test fixes to some of these critical bugs as soon as they are available, instead of waiting for the next kernel bump. Jun 24 15:14:35 very well. Jun 24 15:16:12 BTW, the daisy chain fix works well, thanks & kudos. Jun 24 15:16:49 was it just removing CPU_IDLE from the Kconfig? Jun 24 15:17:18 this is just a big hack and shouldn't be considered to be the real thing. Jun 24 15:17:40 removing CPU_IDLE just avoids touching the flaky code. Jun 24 15:18:49 Sometimes it is things like this that need to be done to keep the rest of the teams moving forward while a real fix is pursued. Jun 24 15:19:34 I have no problem with doing that either..,,. Jun 24 15:19:35 It enables people like me to find and report new and annoying bugs. :P Jun 24 15:19:48 but the real fix is still eluding me. Jun 24 15:20:03 and all this time that I'm not fixing other problems... Jun 24 15:20:11 mpoirier, ask koen in #beagle, probably he knows about it and has a patch Jun 24 15:20:38 he is a great source of information if it comes to kernel issues with omap :) Jun 24 15:20:54 ogra: you seems to know something I don't... Jun 24 15:21:14 lag, what was your trick to make HDMI or DVI work on omap4 ? Jun 24 15:21:30 push it in harder? Jun 24 15:21:30 * ogra remembers you talked about that a while ago Jun 24 15:21:39 It doesn't Jun 24 15:21:54 It doesn't ? Jun 24 15:21:59 It doesn't work Jun 24 15:22:17 FBAR Jun 24 15:22:33 neither of the ports ? Jun 24 15:22:57 Neither Jun 24 15:23:20 DVI isn't meant to work Jun 24 15:23:20 robclark, didnt you say there was a trick to make HDMI/DVI work on the panda ? Jun 24 15:23:26 HDMI just doesn't Jun 24 15:23:44 There was a hack to make it work with HDMI/DVI converter Jun 24 15:23:53 But I haven't tried that, as I don't have the cable Jun 24 15:24:03 lag: you hdmi isn't working? Jun 24 15:24:10 Correct Jun 24 15:24:31 lag: which kernel release are you using? Jun 24 15:24:43 lag: L24.7 ? Jun 24 15:24:49 real men use serial Jun 24 15:24:55 armin76: hehe indeed Jun 24 15:25:08 prpplague: gimme omap4! Jun 24 15:25:13 prpplague, we're all using the ubuntu kernel Jun 24 15:25:17 Serial works like a peach Jun 24 15:25:36 prpplague, which should be based on something newer than L24.7 afaik Jun 24 15:25:45 lag, serial doesnt help with images :) Jun 24 15:25:47 ogra: I'm not sure if DVI is up yet.. HDMI works well (at least on the monitor that I have) Jun 24 15:26:10 for L24.7 kernel, you need some bootargs so you have more than 0MB for framebuffer.. Jun 24 15:26:15 the HDMI inteface can be used with a DVI monitor with no problems Jun 24 15:26:19 yup Jun 24 15:26:31 * armin76 tests :D Jun 24 15:26:32 fyi: vram=8M omapfb.vram=0:8M Jun 24 15:26:41 thats all ? no resolution ? Jun 24 15:26:46 lag: most likely you need to allocate some mem for the framebuffer per robclark 's suggestion Jun 24 15:26:50 * ogra tries Jun 24 15:26:57 ogra: for hdmi it will autodetect the best resolution Jun 24 15:27:09 sweet ! Jun 24 15:27:10 ogra: for dvi you will need to specify the mode and resolution Jun 24 15:27:14 yeah Jun 24 15:27:14 Sounds good Jun 24 15:27:19 my monitor has both Jun 24 15:27:43 lag: if you are using the hdmi but with a dvi monitor your will need to specific some additional bootargs Jun 24 15:28:06 I'm not Jun 24 15:28:13 I'm using real HDMI Jun 24 15:28:31 Once my kernel is up again, I'll try those extra args Jun 24 15:28:33 :) Jun 24 15:29:00 lag: ahh ok Jun 24 15:29:09 Could that be the source of the "SYNC_LOST_DIGIT" messages I receive? Jun 24 15:29:29 They swap my system rendering it unusable Jun 24 15:29:43 but 592295 Jun 24 15:29:46 Doh! Jun 24 15:29:54 bug 592295 Jun 24 15:29:59 Launchpad bug 592295 in linux-ti-omap (Ubuntu) "omapdss DISPC error: SYNC_LOST_DIGIT (affects: 1) (heat: 8)" [Medium,Confirmed] https://launchpad.net/bugs/592295 Jun 24 15:30:42 omapfb omapfb: failed to allocate framebuffer Jun 24 15:30:42 omapfb omapfb: failed to allocate fbmem Jun 24 15:30:42 omapfb omapfb: failed to setup omapfb Jun 24 15:30:42 omapfb: probe of omapfb failed with error -12 Jun 24 15:30:44 hmm Jun 24 15:31:08 ogra: someone was seeing that yesterday Jun 24 15:31:24 Can you post your .config? Jun 24 15:31:26 and i see the SYNC_LOST_DIGIT message too at the end of the boot Jun 24 15:31:33 robclark: i was about to ask the same Jun 24 15:31:47 ogra: One is fine Jun 24 15:31:51 It's expected Jun 24 15:31:59 10,000 is not Jun 24 15:31:59 From looking at code, I think that error comes if the kernel is somehow built w/o any DSS drivers enabled.. Jun 24 15:33:42 robclark, http://pastebin.com/HeBHjaAS Jun 24 15:35:04 ogra: hmm.. that looks somewhat ok.. CONFIG_OMAP2_DSS_HDMI=y Jun 24 15:35:06 hmm Jun 24 15:36:23 the monitor is definately initialized but i dont see any output Jun 24 15:36:56 ogra: do cat /dev/urandom > /dev/fb0 Jun 24 15:37:19 i have no shell atm Jun 24 15:37:24 ogra: oh Jun 24 15:37:30 actually, ogra, I think your error is different from one yesterday. Jun 24 15:37:32 ogra: why not? Jun 24 15:37:38 ogra: How many messages do you get? Jun 24 15:37:45 try change CONFIG_OMAP2_VRAM_SIZE=4 to CONFIG_OMAP2_VRAM_SIZE=8 Jun 24 15:37:46 lag, only one Jun 24 15:37:56 That's fine then Jun 24 15:37:57 No problem Jun 24 15:38:06 4mb is not sufficient for 1920x1080x4byte/pixel Jun 24 15:38:12 prpplague, because i dont have a rootfs atm :) Jun 24 15:38:26 oh Jun 24 15:38:33 /* When we enable digit output, we'll get an extra digit Jun 24 15:38:34 * sync lost interrupt, that we need to ignore */ Jun 24 15:38:38 robclark, so it reads the EDID of my monitor and automatically takes the highest res. it finds ? Jun 24 15:38:41 ogra: so how are suppose to know if the hdmi is working? Jun 24 15:38:48 ogra: correct Jun 24 15:38:51 prpplague, kernel messages on tty0 Jun 24 15:39:02 first frame as it takes long time to decode but it later recovers*/ Jun 24 15:39:15 * lag tries again Jun 24 15:39:17 first frame as it takes long time to decode but it later recovers*/ Jun 24 15:39:21 Grr Jun 24 15:39:30 ogra: you are trying to run the hdmi as the console? Jun 24 15:39:36 ogra.. yeah.. but it should reduce the framebuffer size if it doesn't have enough mem.. Jun 24 15:39:39 first frame as it takes long time to decode but it later recovers*/ Jun 24 15:39:40 prpplague, indeed Jun 24 15:39:50 so you should see some resolution like 1920x540 Jun 24 15:39:50 ahh Jun 24 15:40:06 first frame as it takes long time to decode but it later recovers*/ Jun 24 15:40:09 but maybe after some limit it gives up at trying to resize the framebuffer Jun 24 15:40:14 /*commenting below code as with 1080P Decode we see a sync lost digit for Jun 24 15:40:14 first frame as it takes long time to decode but it later recovers*/ Jun 24 15:40:15 Got it Jun 24 15:40:22 Stupid leading / Jun 24 15:40:25 robclark, hmm, my monitor might not do such odd resolutions in HDMI mode Jun 24 15:40:43 hmm, ok.. that could be the issue I suppose Jun 24 15:41:25 ogra: can you pastebin your bootlog? Jun 24 15:41:43 if i boot with serial console i can grab it, yes Jun 24 15:41:46 one sedc Jun 24 15:41:48 *sec Jun 24 15:42:43 http://paste.ubuntu.com/454514/ Jun 24 15:42:49 * prpplague looks Jun 24 15:45:30 ogra: edit your .config file, turn off DSI and set the number of framebuffers to 1 Jun 24 15:46:09 ogra: also turn on the omap2 fb debug support Jun 24 15:46:19 well, i wont compile any kernels now :) Jun 24 15:46:43 * ogra is busy working on images, but i'll file a bug for the kernel team to fix it Jun 24 15:47:19 ogra: oh Jun 24 15:47:46 ogra: is the kernel source for what you are using available somewhere? Jun 24 15:47:57 i usually dont touch kernels if i can avoid :) Jun 24 15:48:12 ogra: ahh Jun 24 15:48:18 https://edge.launchpad.net/ubuntu/maverick/+source/linux-ti-omap4/2.6.34-900.1 Jun 24 15:48:26 * prpplague looks Jun 24 15:48:43 cooloney maintains it, lag gives him a hand Jun 24 15:48:46 * prpplague downloads and builds Jun 24 15:49:24 * prpplague needs a brake from the mailing list flame wars Jun 24 15:49:40 heh Jun 24 15:50:07 jkridner1: morning Jun 24 15:50:26 ogra: i'll have a look at the build and test Jun 24 15:51:47 thanks Jun 24 15:52:40 hi prpplague Jun 24 15:53:13 hrw: greetings Jun 24 15:55:00 ogra: why mem=463M? Jun 24 15:55:39 hrw, thats in the u-boot defaults, i just kept them Jun 24 15:55:41 hrw: the blaze/sdp team were using that value, i never did get an answer for why Jun 24 15:56:03 prpplague: i thought it was for legacy reasons, to set memory aside for dspbridge crap? Jun 24 15:56:18 I ran our machines just fine without mem= on the bootargs Jun 24 15:56:21 ojn: ahh, that might be true Jun 24 15:56:51 prpplague: maybe they had problem with second 512M? Jun 24 15:57:17 hrw: the blaze/sdp doesn't have a second 512M Jun 24 15:57:22 thats why Jun 24 15:57:38 no Jun 24 15:57:49 u-boot passes the amount of memory in the proper atags, no need for bootargs. Jun 24 15:58:16 well, its in the panda u-boot defaults Jun 24 15:58:25 we had 1GB working too (well, 768MB, highmem support was busted back when I tried it last). Jun 24 15:58:33 ogra: Should be bug reported, probably. Jun 24 15:58:34 but i'll remove it in the ubuntu package if its not needed Jun 24 15:58:57 well, in ubuntu we use boot.scr everywhere to set bootargs so i dont really care Jun 24 15:58:59 ojn: on which platform? Jun 24 15:59:27 prpplague: custom boards Jun 24 15:59:34 (4430-based) Jun 24 15:59:47 prpplague and all: 463M is the value for 512M boards.. some memory needs to be reserved for coprocessors Jun 24 16:00:07 in future, syslink will reserve this at boot time using normal kernel memory allocation APIs.. Jun 24 16:00:11 but that isn't implemented yet Jun 24 16:01:50 robclark: ahh dandy Jun 24 16:03:16 btw, is there already u-boot/x-load patches for 1gb panda? Jun 24 16:05:13 GrueMaster: where do I get ogra's test image ? The one you are testing with. Jun 24 16:05:50 mpoirier, people.canonical.com/~ogra/jasper/ Jun 24 16:06:05 mpoirier, note that updating the kernel doesnt work automatically yet Jun 24 16:06:12 and that it uses .34 still Jun 24 16:06:19 ah.. toys Jun 24 16:06:24 i'm only interested in the u-boot. Jun 24 16:06:28 robclark: no not yet Jun 24 16:06:28 will I find it in there ? Jun 24 16:06:42 Oops. Sorry about that. wrong link in the copy buffer for some reason. Jun 24 16:06:47 ogra: kernel building now Jun 24 16:07:16 Use ogra's link. There are only two files there. Jun 24 16:07:42 mpoirier, uboot is in the image Jun 24 16:08:30 ogra: ok thanks. Jun 24 16:09:06 mpoirier: You can mount the boot partition with sudo mount cmdline-maverick-armel+omap3.img mnt/ -o loop,offset=$((32256)) Jun 24 16:09:26 Saves time from having to write the image to SD. Jun 24 16:09:45 I would have just mounted the image. Jun 24 16:13:39 have a nice rest of day Jun 24 16:14:42 mpoirier, oh, i mis-read above, you want u-boot ? Jun 24 16:14:53 I just need uboot. Jun 24 16:15:40 https://edge.launchpad.net/ubuntu/+source/u-boot-omap3/2010.3git20100531-0ubuntu1/+build/1767190 Jun 24 16:15:50 just dpkg -x the .deb Jun 24 16:16:06 ogra; thanks. Jun 24 16:16:40 ogra: the cmdline-maverick-armel+omap3.img image, what format is it ? Jun 24 16:17:02 It is a SD image. 2 partitions. Jun 24 16:17:02 its a two partition img to dd to the SD card Jun 24 16:17:27 yes, but if I want to mount it live on my file system... Jun 24 16:17:38 a simple mount -o loop fails. Jun 24 16:17:54 using "file" on the image yields: x86 boot sector; partition 1: ID=0xc, active, starthead 1, startsector 63, 144522 sectors; partition 2: ID=0x83, starthead 0, startsector 144585, 867510 sectors, code offset 0x0 Jun 24 16:18:01 haven't seen that before. Jun 24 16:18:15 Then you need to find the starting byte of each partition (parted will give you this) and mount with -o loop,offset=. Jun 24 16:18:21 ogra: definetly some weirdness going on with that kernel soruce Jun 24 16:18:41 ogra: ok. Jun 24 16:18:44 prpplague, well, its an ubuntu kernel with the TI patches on top Jun 24 16:18:57 * prpplague digging into it Jun 24 16:18:57 prpplague, afaik sebjan maintains it on the TI side Jun 24 16:18:59 mpoirier: I'll send you a link on how to do this. Jun 24 16:19:52 http://wiki.edseek.com/guide:mount_loopback Jun 24 16:20:25 GrueMaster: I just got it with the offset command you sent me above. Jun 24 16:20:28 I get it now. Jun 24 16:22:22 ogra: interesting, straight out of the box with the defconfig, the kernel fails to compile Jun 24 16:23:05 indeed Jun 24 16:23:30 you need to build it like a debian package Jun 24 16:23:54 it runs various scripts to assemble the different config snippets Jun 24 16:24:19 hi prpplague. I should free up here shortly and can swing by if you let me know where you are at. still don't have the LCD. :( Jun 24 16:24:23 huh? you don't use the defconfigs? Jun 24 16:24:42 prpplague, no Jun 24 16:24:47 jkridner1: E-2126 , just down from geralds office Jun 24 16:24:59 hmm Jun 24 16:25:05 prpplague, there is an ubuntu (non arch specific) config and there is an arch specific one Jun 24 16:25:37 must be somewere in the debian dir, i guess soemone from the kernel team can explain it better than me Jun 24 16:26:13 to build it you definately need to run "fakeroot debian/rules " Jun 24 16:26:18 ogra: i'll dig around and see what i can find Jun 24 16:26:27 debian/rules is the makefile Jun 24 16:26:28 ogra: guess we need to know how to test the ubuntu kernels Jun 24 16:26:41 prpplague, we'll soon have daily images Jun 24 16:26:59 so you can just install the image and regulary upgrade the kernel Jun 24 16:27:14 ogra: well i don't like not knowing, i just assumed ubuntu built the kernel just like the rest of the world, hehe Jun 24 16:27:28 ogra: i mainly do kernel dev Jun 24 16:27:32 it builds it slightly similar to debian Jun 24 16:27:33 ogra: so i need to be able to hack Jun 24 16:28:01 well, the kernel team maintains it in a git tree like any other kernel dev does :) Jun 24 16:28:19 just the build process is different since its wrapped in packaging stuff Jun 24 16:29:14 i'm sure there is a doc somewhere that describes the process Jun 24 16:30:33 right Jun 24 16:32:21 prpplague, https://help.ubuntu.com/community/Kernel/Compile i think Jun 24 16:32:39 * prpplague looks Jun 24 16:33:16 "Build the kernel (when source is from git repository, or from apt-get source)" Jun 24 16:33:21 thats the section you want Jun 24 16:34:09 yea, reading over that now Jun 24 16:34:32 you need beefy hardware though (we do not cross compile) Jun 24 16:35:32 yea looks there are some "multi-boot" issues Jun 24 16:35:34 testing Jun 24 16:38:18 ok, here is the bit Jun 24 16:38:37 ogra: they have the DPI picodlp enabled in the config Jun 24 16:38:49 ouch Jun 24 16:39:00 probably a blaze leftover Jun 24 16:39:33 lag, ^^^ Jun 24 16:39:36 ogra: so if you have that enabled along with the HDMI, you need to change the number of framebuffers to 2 instead of 1, and in addition you need to allocate enough memory for both, 16 is probably enough, but a safe value is 32 Jun 24 16:40:11 lag, can you take care that cooloney gets that info ? Jun 24 16:42:37 GrueMaster: moving to ogra's u-boot fixed my USB EHCI issue - thanks. Jun 24 16:42:48 great :) Jun 24 16:46:38 * prpplague retests with the common config Jun 24 16:47:08 mpoirier, both boards are working now? Jun 24 16:47:25 interesting. Jun 24 16:48:19 Must be a u-boot<>kernel combination issue. I haven't tried the new kernels on the old system. Jun 24 16:54:49 davidm Jun 24 16:55:17 good lord that common image is giant Jun 24 16:57:14 davidm: both boards are working now. Jun 24 17:01:04 ogra: yea looks like the same issue with the common config, they have 3 different dss drivers enabled, DSI, DPI and HDMI, but only have 2 framebuffers allocated Jun 24 17:02:38 ogra: easiest is to just use 32MB for the framebuffers, that should work fine Jun 24 17:05:28 prpplague: we want to have a single kernel image/defconfig for both blaze and panda, so we need to have picodlp activated, right? Are there changes to apply to the config according to you? Jun 24 17:06:22 sebjan: assuming i am using the right config per the instructions, the vram needs to be increased to a min of 16, preferable to 32 Jun 24 17:07:48 well, we have enough ram, 32 should be doable Jun 24 17:08:47 ... and in case we want to use the serial only ;), we can force a lower value in command line then, right? Jun 24 17:09:22 no idea if there is a cmdline override :) Jun 24 17:10:02 sebjan: correct Jun 24 17:10:45 does the vram value override the kernel default ? Jun 24 17:11:37 ogra_cmpc: on the command line it does Jun 24 17:11:46 sebjan: i emailed you the config i am using Jun 24 17:12:11 ah, great, so you only need to change boot.scr Jun 24 17:14:19 prpplague: great thanks, I'll take this change Jun 24 17:24:50 sebjan: np **** ENDING LOGGING AT Fri Jun 25 02:59:57 2010