| twb | lilstevie: ok so cros is built now; I guess I need to grok abootimg next? | 01:14 |
|---|---|---|
| twb | Is the abootimg config file (e.g. $bootsize etc) the same for my CrOS 2.6.38 as the one that shipped with your 2.6.36-based tarball? | 01:18 |
| twb | Hmm, another strange thing -- holding voldn gets me into asus bootloader's "android or factory reset?" UI, and but if I pick the latter it boots normally and goes into X, whereas it ought to be running the SOS kernel which has single | 01:27 |
| lilstevie | twb: the bootsize is the same size as the partition | 01:52 |
| lilstevie | also did you make sure to hit vol-up within 5 secs | 01:52 |
| twb | Yeah, I got the little onscreen thing which has an icon of android on the right, and some factory reset type thing on the left | 01:59 |
| twb | AIUI the left icon actually means SOS | 01:59 |
| lilstevie | hm that shouldn't happen | 02:08 |
| lilstevie | if you press vol-down with power and don't press vol-up within 5 seconds that menu shows up | 02:09 |
| lilstevie | that is the datawipe menu | 02:09 |
| twb | OK so that's the wrong menu | 02:18 |
| lilstevie | yeah, when you press vol-down, there is a bit of writing that shows at the top left that says "press <vol-up> to boot RCK | 02:20 |
| lilstevie | " | 02:20 |
| twb | I can't seem to get to that | 02:21 |
| lilstevie | hm | 02:25 |
| lilstevie | did you manually flash the SOS kernel | 02:25 |
| twb | Not sure what you mean | 02:26 |
| lilstevie | how did you flash up the device | 02:26 |
| twb | What's on there now is basically the 2.6.36 setup you prepared as linux-flash-kit | 02:27 |
| lilstevie | ok, well I didn't flash an SOS kernel | 02:27 |
| twb | Hm | 02:27 |
| twb | I appear to be doing so | 02:27 |
| lilstevie | not with pure | 02:27 |
| lilstevie | you would need to manually prepare and flash your SOS kernel | 02:28 |
| twb | http://paste.debian.net/142822/ | 02:28 |
| twb | AFAIK that's what I put on there a few weeks back. | 02:28 |
| lilstevie | hm | 02:30 |
| === l00nr_ is now known as l00nr | ||
| happydebugging | Oneric on Pandaboard. Distorted display at install and afterwards. Are there known issues with HDMI to DVI? HDMI to DVDI-D Cable is known good. | 05:41 |
| misham | Hello. I've compiled a kernel for my BeagleBoard-xM rev C using Linus' git tree and when I boot it, it hangs on mmcblk0: p1 p2 | 07:16 |
| misham | how would I debug this problem? | 07:16 |
| twb | Well, that line is it finding two partitions on the first MMC (SD card) block device. | 07:30 |
| twb | Not sure why that's hanging, tho | 07:30 |
| misham | it is finding those partitions | 07:36 |
| misham | here's full boot log: https://gist.github.com/1341243 | 07:38 |
| misham | at least I think it's finding 2 partitions | 07:41 |
| === Quintasan_ is now known as Quintasan | ||
| Dawgmatix | hello i am trying to run the ubuntu oneiric preinstalled image on a beagleboard xm and cannot get the board to boot | 13:54 |
| Dawgmatix | boot has errors like - Wrong Image Format for bootm command, ERROR: can't get kernel image | 13:55 |
| Dawgmatix | are there any folks here successfully using the beagleboard xm? | 13:57 |
| ben22 | Hello. May I ask a question regarding an armv5 chip in this channel? | 14:08 |
| shadeslayer | lilstevie: whats this I hear about new flashkit and stuff :D :D :D | 16:43 |
| sveinse | Any activity here now? Anyone running i386 Natty? Would be nice if anyone could confirm #886690. | 22:25 |
| sveinse | bug 886690 | 22:25 |
| ubot2 | Launchpad bug 886690 in qemu-linaro "qemu segfaults in armel chroot on i386 host" [Undecided,New] https://launchpad.net/bugs/886690 | 22:25 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!