[00:03:52] *** Knocks has joined #chromium-os
[01:34:18] *** Inumedia_ has joined #chromium-os
[01:34:40] *** Inumedia has quit IRC
[02:29:10] *** lipsinV2 has joined #chromium-os
[02:30:18] *** sbyer has quit IRC
[02:48:59] <srao> Knocks: version jumps happen 4 times every weekday
[02:53:03] <Knocks> i see
[02:53:16] <Knocks> yeah it didn't help with the "chromium is repairing itself problem"
[02:53:17] <Knocks> :)
[02:54:04] <srao> oh, I thought you had gotten past that by editing the /sbin/chromeos_startup script ?
[02:54:05] *** Inumedia_ has quit IRC
[02:54:46] *** AndrewN has joined #chromium-os
[02:54:51] *** AndrewN has joined #chromium-os
[02:55:44] <Knocks> didn't help
[02:56:02] <Knocks> i edited it in two different places like you suggested
[02:56:36] <srao> hmm
[02:57:11] <srao> so you changed the 1 to a 3 ?
[02:57:16] <Knocks> yes
[02:57:26] <Knocks> so i opened a new issue
[02:58:07] <srao> on the bug tracker ?
[02:58:15] <Knocks> yeah.   i figured enough people were having it
[02:58:15] <srao> what's the number
[02:58:26] <Knocks> 22274
[02:58:29] <srao> have you talked to others that have it too ?
[02:58:44] <Knocks> no but i searched the web for the error
[02:59:09] <Knocks> it seems to be related to locating the stateful partition, like you though
[02:59:46] *** achuith has quit IRC
[02:59:49] <srao> slightly unrelated.... but did you ever get a bigger USB stick ?
[02:00:42] <srao> so you could try the straight .img file ?
[02:00:59] <Knocks> no, but i tried a couple of other builds that were under 2GB
[02:01:21] <Knocks> hexxeh's "flow" build from late 2010
[02:01:24] <srao> ah, from USB ?
[02:01:33] <Knocks> and dell's custom build from may 2011
[02:01:40] <Knocks> neither of them worked
[02:02:05] <srao> what happened exactly?
[02:02:17] <Knocks> i think black screen with flow
[02:02:29] <Knocks> and a bunch of different errors on the dell build
[02:03:16] <srao> so different things happened... i guess that makes sense
[02:03:28] <srao> one from 2010 would be more like what you had on the cr-48
[02:03:43] <Knocks> yeah i mean those builds might as well all be from different decades
[02:03:48] <srao> but it's a little bit odd
[02:04:04] <Knocks> it's not even worth messing with anything that old
[02:04:11] <srao> i kinda would have thought they might have booted though
[02:04:15] <srao> especially from USB
[02:05:37] <srao> can you give me a pointer to the images you tried ?
[02:05:52] <Knocks> yes
[02:06:16] <Knocks> this is flow
[02:06:17] <Knocks> http://chromeos.hexxeh.net/download.php?release=Flow&type=usb
[02:06:59] <Knocks> and this is dell
[02:06:59] <Knocks> http://linux.dell.com/files/cto/
[02:08:31] <srao> ok... and what about the one you put on the hard drive ?
[02:09:03] <Knocks> i tried the 3 most recent nightly builds
[02:09:21] <Knocks> http://chromeos.hexxeh.net/vanilla.php
[02:09:28] <Knocks> oct 27-29
[02:09:35] <Knocks> and i copied two partitions
[02:10:15] <Knocks> root-a
[02:10:19] <Knocks> 858MB
[02:10:25] <srao> and those vanilla images don't fit on the usb drive ?
[02:10:29] <Knocks> and state 1024MB
[02:10:40] <Knocks> no, they're 2050MB
[02:11:00] <Knocks> because they also have three 16MB and one 8MB parition
[02:11:15] <srao> yeah. the dell one seems slightly smaller
[02:11:19] <srao> 2042643968 2011-05-13 13:28 ChromiumOS_x86_May13.img
[02:11:26] <srao> not a whole lot though
[02:11:29] <Knocks> yeah that's the one i tried
[02:11:39] <srao> so that one fits on your usb stick ?
[02:11:46] <Knocks> yep
[02:12:27] <srao> it's just like 8MB smaller
[02:12:32] <srao> is that right ?
[02:12:40] <Knocks> possibly
[02:12:45] <Knocks> i deleted it
[02:13:16] <srao> looks that way to me... I'm wondering if you could try just putting the vanilla img onto your usb stick
[02:13:28] <Knocks> doesn't fit
[02:13:34] <srao> if I remember correctly, i think the last part  isn't needed
[02:13:37] <Knocks> i tried formatting a dozen different ways
[02:13:42] <srao> yeah but just put whatever fits onto it
[02:13:47] <srao> leave the last few MB off
[02:13:49] <Knocks> fat and fat32 with different cluster sizes
[02:14:01] <srao> ah you shouldn't really have to mess with any of that
[02:14:10] <srao> man windows makes things complicated
[02:14:17] <Knocks> i know but it does give you a few extra bytes when you change it
[02:14:42] <Knocks> i have no way of copying the file partially
[02:15:06] <Knocks> there is only one utililty for windows that writes .img files to removable storage
[02:15:08] <srao> yeah but what I mean is... you should be able to do a raw copy of the file to the usb device... it's really easy in linux... you'd just do a dd
[02:15:11] <Knocks> and it wants the whole thing
[02:15:36] <Knocks> yeah there's no raw copying in windows i'm afraid
[02:15:42] <srao> yeah, the Linux tool would just copy whatever does fit on and leave the rest off
[02:16:03] <Knocks> the EFI partition is unnecessary, right?
[02:16:28] <srao> that's the Fat16 one ?
[02:16:36] <srao> it's necessary if you're booting from usb
[02:16:41] <Knocks> ok
[02:16:53] <Knocks> do you have a tool that let's you edit an .img?
[02:17:09] <Knocks> if you could delete one or two unnecessary partitions, i can try
[02:17:59] <srao> this looks interesting... http://www.chrysocome.net/dd
[02:18:04] <srao> it's a windows version of that dd tool
[02:18:10] <Knocks> the other small partitions are KERN-A, KERN-B, and RWFW
[02:18:30] <srao> yeah you could delete those also
[02:18:34] <srao> i'd have to look for a tool
[02:18:42] <srao> though you could do it with dd also
[02:20:15] <Knocks> i think dd will cut off the EFI partition
[02:21:58] <srao> I think it will cut off KERN-B
[02:23:00] <srao> 12      2017MB  2034MB  16.8MB  fat16        EFI-SYSTEM  boot
[02:23:01] <srao>  4      2034MB  2051MB  16.8MB               KERN-B
[02:23:01] <srao>  5      2051MB  2051MB  512B                 ROOT-B
[02:23:12] <srao> that's what parted tells me is the layout at the end
[02:23:20] <srao> so EFI only goes up to 2034 MB
[02:23:36] <srao> KERN-B goes from 2034 to 2051 which is where you'll run out of space
[02:23:59] <Knocks> yes youre' right
[02:24:08] <Knocks> ok what's the command i should use for dd
[02:24:17] <Knocks> to chrome.img to the g: drive
[02:24:42] <srao> well you'll first have to put in the USB drive and figure out the windows path... I think you can do it with "dd --list"
[02:25:52] <Knocks> \\.\Volume{a0bfe054-00b4-11e1-bf3b-f07bcbef8e4d}\
[02:25:52] <Knocks>   link to \\?\Device\HarddiskVolume8
[02:25:52] <Knocks>   removeable media
[02:25:52] <Knocks>   Mounted on \\.\g:
[02:25:53] *** lipsinV2 has quit IRC
[02:27:23] <srao> just a sec
[02:28:21] <srao> so you'd do something like this
[02:28:48] <srao> dd if=c:\chromiumos_image.img of=\\.\Volume{a0bfe054-00b4-11e1-bf3b-f07bcbef8e4d} bs=1M
[02:29:01] <srao> and put the right path to the image file after "if="
[02:29:57] <Knocks> i love how you think this is easy
[02:29:58] <Knocks> :)
[02:30:36] <srao> well... easy > impossible
[02:30:38] <srao> err
[02:30:43] <srao> something like that :-)
[02:30:52] <srao> maybe *this* > impossible
[02:31:15] *** lipsinV2 has joined #chromium-os
[02:31:18] <srao> it's windows's wierd device naming that makes it hard, IMHO
[02:32:19] <Knocks> dd if=c:\chromiumos_image.img of=\\.\Volume{a0bfe054-00b4-11e1-bf3b-f07bcbef8e4d} bs=1M
[02:32:32] <Knocks> sorry
[02:32:44] <Knocks> Error opening input file: 3 The system cannot find the path specified
[02:33:22] <Knocks> that's what i got after this command
[02:33:49] <srao> hmm
[02:34:03] <srao> try this
[02:34:06] <Knocks> nevermind wrong path
[02:34:09] <Knocks> now i get this error
[02:34:20] <Knocks> The process cannot access the file becasue it is being used by another process
[02:34:22] <srao>  dd if=c:\chromiumos_image.img of=\\?\Device\HarddiskVolume8 bs=1M
[02:34:24] <srao> oh
[02:34:28] <srao> grr
[02:34:33] <Knocks> it's not being used by anything
[02:34:33] <srao> try that 2nd one
[02:34:54] *** sadrul has quit IRC
[02:36:03] <Knocks> Error native opening file: 0 The operation completed successfully
[02:36:16] <srao> man
[02:36:20] <Knocks> lol
[02:36:25] <srao> you're right, it wasn't easy :-)
[02:36:27] <Knocks> so much work to copy a file
[02:36:48] <srao> see, i blame windows though :-)
[02:37:14] <Knocks> yeah but windows is a fact of life
[02:37:16] <srao> makes simple things complicated
[02:37:20] <Knocks> got to work around it
[02:37:34] <srao> I should just mail you a bigger usb stick
[02:37:48] <Knocks> lol i can buy one
[02:37:51] <Knocks> it's like 5 bucks
[02:37:54] <srao> unfortunately I suspect it might not work
[02:38:01] <srao> since all this other stuff hasn't
[02:38:04] <Knocks> i'm not leaving the house because i'm stick and it's freaking snowing out
[02:38:13] <srao> oh yeah east cost snow
[02:38:27] <Knocks> yeah well, it's booting the kernel from the hdd
[02:38:31] <Knocks> so that's good news, right
[02:38:41] <Knocks> maybe you guys can just flag the ext3 partition?
[02:38:46] <Knocks> so it doesn't have to be confused
[02:39:05] <Knocks> that would help legacy users a lot
[02:41:29] <srao> yeah maybe... we focus a lot on security though, it's often tough to make things flexible without opening yourself up to some kind of attack
[02:41:46] <srao> so we end up spending a lot of time on security reviews
[02:42:30] <srao> the other thing we could work on is fixing the repairing error
[02:43:07] <Knocks> it doesn't really open any additional doors
[02:43:23] <Knocks> just a 1-byte flag would help
[02:43:34] <Knocks> if that's what in fact is causing the error
[02:45:03] <srao> well the things you did should have fixed the problem.. maybe it takes a while though... how long did it sit there at the repairing screen?
[02:45:15] <srao> well before I ask that
[02:45:24] <srao> i should ask, can you still read the ext3 partition using that windows tool ?
[02:45:39] <Knocks> it sat there for a good half hour
[02:45:43] <Knocks> i'm pretty sure it's frozen
[02:45:47] <srao> yeah
[02:45:52] <Knocks> i can read it, yeah
[02:45:58] <srao> that's probably more than long enough
[02:50:18] <srao> yeah at this point we have to probably edit the script and change the grub config file
[02:50:26] <srao> not sure you want to really do this
[02:50:36] <Knocks> what script
[02:51:34] <srao> /sbin/chromeos_startup
[02:51:42] <srao> that file I had you edit before
[02:52:07] <Knocks> a bit confused
[02:52:18] <Knocks> the kernel loads fine, so why change the grub file?
[02:52:45] <srao> well because we don't want to display the spash screen and want more debugging output
[02:53:11] <Knocks> so what do you want to point it to?
[02:54:37] <srao> what did you have in the grub config file before ?
[02:56:36] <Knocks> timeout 0
[02:56:36] <Knocks> default 1
[02:56:36] <Knocks> title ChromiumOS
[02:56:36] <Knocks> find --set-root /boot/vmlinuz
[02:56:36] <Knocks> kernel /boot/vmlinuz root=/dev/sda2 rwnoresume noswap i915.modeset=1 loglevel=1 cros_debug
[02:57:22] <srao> yeah so change the kernel line... remove the "i915.modeset=1" and remove "loglevel=1"
[02:58:44] <Knocks> what do those things do?
[02:59:20] <srao> I believe i915.modeset=1 puts the screen into a higher resolution graphics mode (instead of text) so that we can display the splash screen
[02:59:36] <srao> loglevel=1 tells the kernel to only display the most important kernel messages
[02:59:42] <Knocks> ok
[02:59:46] <srao> by taking those out you should see a lot more text on the screen when it boots
[02:59:47] <Knocks> so just change this for now?
[02:59:57] <srao> and it should enable you to see the output of scripts as well
[03:00:00] <srao> sure
[03:00:06] <Knocks> ok
[03:02:18] <Knocks> brb
[03:02:49] *** sadrul has joined #chromium-os
[03:02:52] *** Knocks has quit IRC
[03:04:14] *** AndrewN has quit IRC
[03:11:51] *** Knocks has joined #chromium-os
[03:14:45] <Knocks> ok
[03:15:21] <Knocks> here we are
[03:15:21] <Knocks> http://i41.tinypic.com/e0pz0y.jpg
[03:16:09] <srao> cool, so we got lots of text
[03:16:14] <srao> which is what we wanted, so that's good
[03:16:18] <Knocks> haha yep
[03:16:28] <Knocks> it scrolled fast, so i only captured the end
[03:16:42] <Knocks> but this is where it seemed to stop
[03:17:06] <srao> ok that's fine.. I'm still not seeing any output from the scripts, but that might be expected
[03:17:16] <srao> is there anything on vt2 at this point ?
[03:17:16] <Knocks> which scripts?
[03:17:22] <srao> the chromeos_startup script
[03:17:29] <Knocks> maybe that was in the beginning
[03:17:40] <Knocks> i can switch between this and the other screen
[03:17:51] <Knocks> the other one asks you to log in, just as it did before
[03:17:55] <srao> ok
[03:18:27] <srao> interesting that it got this far
[03:18:32] <srao> that's not what I was expecting
[03:18:43] <Knocks> i was still able to see the chromium repair screen
[03:18:51] <Knocks> with text running on top of it
[03:19:10] <srao> the text just wrote over it I'm guessing
[03:19:28] <Knocks> yeah and the gray squares from it remained
[03:19:34] <Knocks> until i switched to vt2 and back
[03:19:37] <srao> we could disable the screen totally if we changed chromeos_startup
[03:19:44] <srao> but this definitely tells us something
[03:20:01] <Knocks> does it look for the stateful partition before this point?
[03:20:06] <Knocks> or this is when it happens
[03:20:10] <srao> yeah it does so pretty early
[03:21:39] <srao> I don't really understand how it got so far... it should have stopped when it determined that it needed to clobber the stateful partition
[03:21:46] <srao> after it's done it should reboot
[03:22:15] <Knocks> what does clobbering mean
[03:22:41] <srao> well it's the word they use in the script to mean, recreate the stateful partition by reformatting
[03:22:54] <srao> well they actually "clobber" it by writing zeros over it first
[03:23:00] <srao> then reformat
[03:23:04] <Knocks> in which cases does it clobber
[03:23:27] <srao> well if it's unable to mount it
[03:23:34] <srao> if you open up that /sbin/chromeos_startup file
[03:23:42] <srao> you can see the code
[03:23:43] <Knocks> we have no evidence of it unable to mounting it
[03:23:52] <Knocks> other than seeing the repair screen
[03:24:05] <srao> right, that is what I was going off of
[03:24:12] <Knocks> maybe it's using the repair screen generically
[03:24:41] <srao> yeah that's possible... I didn't think that it shows that anywhere else, but i'm not 100% sure of that
[03:25:04] <Knocks> is there a way to search the codebase on where it might be brought up?
[03:26:02] <srao> thinking about it though, the fact that you saw the text overwrite it tells me that it's before we've started x-windows
[03:26:07] <srao> so it is certainly early
[03:26:29] <srao> the odd thing though is that it should stop running other stuff when it's decided to do this clobber
[03:26:36] <srao> unless I'm reading something incorrectly
[03:26:50] <Knocks> x-windows is the gui?
[03:26:56] <srao> yeah
[03:27:08] <srao> well actually i take it back, it's possible other things are running
[03:27:13] <srao> chromeos_startup is just another service
[03:28:11] <srao> so ok things make a bit more sense given that...need to look at the clobber scripts more
[03:28:14] <Knocks> why don't we get the ultimate message on what halted the boot?
[03:28:33] <srao> well because it probably thinks it's still working
[03:28:33] <Knocks> is it the last line about the wifi?
[03:28:42] <srao> nah that's unrelated
[03:28:50] <srao> we try to start up as much as possible in parallel
[03:28:55] <srao> to make the boot happen faster
[03:29:02] <srao> so lots of unrelated things are going on
[03:29:16] <Knocks> would i capture the clobbering messages if i took pictures in the beginning?
[03:29:23] <srao> i don't think so
[03:29:38] <srao> i think we'd have to edit the scripts first to print something out... and then you might see the messages
[03:31:00] <Knocks> ok
[03:31:14] <Knocks> how about make it shut up about the hardware
[03:31:16] <Knocks> like drivers
[03:31:22] <Knocks> and only talk about things we want
[03:31:31] <srao> you can put back in that loglevel=1
[03:31:35] <srao> to the grub conf
[03:31:55] <srao> it probably isn't necessary for what we're doing.. i just wanted to make sure *something* printed to the screen
[03:32:48] <Knocks> but leave i915.modeset=1 out?
[03:33:13] <srao> yeah
[03:33:40] <Knocks> ok
[03:33:52] <Knocks> should i try booting again?
[03:35:14] <srao> well first maybe we should change chromeos_startup to print something out
[03:35:33] <srao> can you open it with a text editor ?
[03:36:41] <Knocks> on ext2?
[03:36:54] <srao> y
[03:37:40] <Knocks> in sbin right
[03:37:44] <srao> yup
[03:37:56] <Knocks> ok
[03:37:58] <Knocks> what do i edit
[03:37:59] <srao> you should see some text like this
[03:38:02] <srao>  # For all other cases, mount stateful partition from STATE_DEV.
[03:38:02] <srao>   elif ! mount -n -t ext4 -o nodev,noexec,nosuid,commit=600 \
[03:38:02] <srao>          "$STATE_DEV" /mnt/stateful_partition; then
[03:38:02] <srao>     # Try to rebuild the stateful partition by  clobber-state
[03:38:02] <srao>     # (for security concern, we don't use fast mode)
[03:38:04] <srao>     [ -z "$BOOT_SPLASH_PID" ] || wait $BOOT_SPLASH_PID
[03:38:06] <srao>     chromeos-boot-alert self_repair /dev/tty1
[03:38:08] <srao>     clobber-log --repair "$STATE_DEV" "Self-repair corrupted stateful partition"
[03:38:10] <srao>     exec clobber-state "keepimg"
[03:38:12] <srao>   fi
[03:38:14] <srao> that's where the clobber happens
[03:38:16] <srao> do you see that ?
[03:38:36] <Knocks> yes
[03:39:37] <srao> ok so let's add some text in there
[03:39:49] <srao> after:  clobber-log --repair "$STATE_DEV" "Self-repair corrupted stateful partition"
[03:40:04] <srao> and before "exec clobber-state "keepimg""
[03:40:09] <srao> add this:
[03:40:38] <srao> print "Mount of $STATE_DEV failed"
[03:41:45] <srao> save that
[03:42:14] <Knocks> does identation matter
[03:42:19] <Knocks> just beginning of the line?
[03:42:19] <srao> not really
[03:42:22] <srao> yeah that's ok
[03:42:32] <srao> it won't look pretty but it'll still work
[03:42:54] <Knocks> fine, i'll align it
[03:42:55] <Knocks> :P
[03:42:56] <Knocks> ok
[03:43:05] <Knocks> so when will this printing happen now?
[03:43:18] <Knocks> together with the text i got previously?
[03:44:12] <srao> you shouldn't see much text this time
[03:44:17] <srao> you
[03:44:29] <srao> you'll see the splash screen again, and hopefully this print out will appear on top of it
[03:44:56] <Knocks> ok
[03:44:58] <Knocks> try now?
[03:45:23] <srao> yeah
[03:45:46] <Knocks> ok
[03:45:54] *** Knocks has quit IRC
[03:50:23] *** Knocks has joined #chromium-os
[03:50:40] <srao> did it work ?
[03:50:45] <Knocks> decompressing linux
[03:51:07] <Knocks> and then the message about the device node mapper\control already existing and a link to it will not be overwritten
[03:51:29] <srao> any splash screen ?
[03:53:13] <Knocks> nope
[03:53:17] <Knocks> just that message
[03:54:03] <srao> hmm wierd
[03:54:27] <srao> oh... you know I forgot something
[03:54:35] <srao> sorry... i just realized the messages would appear on vt 2
[03:54:50] <srao> should have thought of that earlier
[03:55:56] <Knocks> i switched to that also
[03:56:01] <Knocks> nothing interesting
[03:56:32] <srao> so you didn't see anything like Mount of /dev/sda3 failed
[03:56:36] <srao> hmm
[03:56:56] <Knocks> no
[03:57:21] <Knocks> why are you at work on a saturday night btw
[03:57:23] <srao> that's frustrating
[03:57:33] <srao> i'm actually about to head out :-)
[03:57:40] <Knocks> lol it's frustrating to me cause it's my machine
[03:58:01] <srao> yeah I'm sure
[03:58:12] <Knocks> but there's no kernel panic
[03:58:14] <srao> it's frustrating to me cause it doesn't make much sense
[03:58:20] <Knocks> you don't think the drivers are breaking it
[03:58:23] <srao> nope
[03:58:28] <Knocks> and there's nothing about the stateful partition
[03:58:43] <srao> well i guess it's odd that you didn't get a splash screen this time
[03:58:53] <Knocks> oh
[03:58:59] <srao> not sure what caused you to get one last time but not this time
[03:59:04] <srao> maybe the stateful is okay
[03:59:12] <srao> and something else is broken :-)
[03:59:13] <Knocks> remember when you had me edit the stateful partition reference before
[03:59:16] <Knocks> in two places
[03:59:18] <srao> yup
[03:59:21] <Knocks> once i changed it to 3
[03:59:28] <Knocks> the splash screen stopped appearing
[03:59:30] <srao> oh
[03:59:35] <Knocks> even when i went back and edited it back to 1
[03:59:43] <srao> i didn't realize that
[03:59:49] <srao> now that part doesn't make much sense
[03:59:55] <Knocks> i know
[03:59:58] <Knocks> but right now it's back at 1
[04:00:05] <Knocks> because this is a fresh build from hexxeh
[04:00:08] <srao> ah
[04:00:42] <srao> well i've got to run, sorry I couldn't help more
[04:00:57] <Knocks> ok man
[04:00:58] <srao> you might try getting a bigger usb stick and trying it from there
[04:01:01] <Knocks> thanks for the help
[04:01:04] <srao> sure
[04:01:08] <Knocks> i will
[04:01:15] <Knocks> it'll probably fail too :)
[04:01:25] <Knocks> happy halloween!
[04:01:47] <srao> yeah Happy Halloween, later
[04:02:25] <Knocks> later
[04:07:13] *** erikat has quit IRC
[04:19:25] *** Knocks has left #chromium-os
[04:19:26] *** Inumedia has joined #chromium-os
[04:19:28] *** erikat has joined #chromium-os
[04:27:10] *** Inumedia has quit IRC
[04:27:53] *** sadrul has quit IRC
[04:38:04] *** sadrul has joined #chromium-os
[04:41:43] *** Inumedia has joined #chromium-os
[05:51:24] *** sadrul has quit IRC
[06:01:28] *** sadrul has joined #chromium-os
[06:01:28] *** ChanServ sets mode: +v sadrul
[06:48:46] *** magn3ts has quit IRC
[06:50:04] *** satorux_1 has quit IRC
[07:00:05] *** magn3ts has joined #chromium-os
[07:40:10] *** nsylvain has quit IRC
[08:19:35] *** vandebo has quit IRC
[08:57:45] *** vandebo has joined #chromium-os
[08:57:45] *** ChanServ sets mode: +v vandebo
[09:29:53] *** patcito has quit IRC
[10:13:18] *** sakoman__ has joined #chromium-os
[10:13:31] *** sakoman_ has quit IRC
[11:12:41] *** _julian_ has joined #chromium-os
[11:12:46] <_julian_> hi
[11:13:03] <_julian_> anyone in here working on chromiumos on tegra2?
[11:27:32] *** SoulRaven has joined #chromium-os
[12:22:26] *** shiyas has joined #chromium-os
[12:23:19] *** shiyas has left #chromium-os
[14:18:27] *** wbednarski has joined #chromium-os
[14:28:38] *** Inumedia has quit IRC
[14:34:31] *** btipling has joined #chromium-os
[14:49:13] *** Inumedia has joined #chromium-os
[17:00:31] *** D|sT has quit IRC
[17:32:27] *** rosso_ has joined #chromium-os
[17:41:07] *** rosso_ has quit IRC
[17:42:05] *** lipsinV2 has quit IRC
[17:46:30] *** D|sT has joined #chromium-os
[18:15:06] *** nexusz99 has joined #chromium-os
[18:34:18] *** satorux_1 has joined #chromium-os
[18:42:45] *** patcito has joined #chromium-os
[19:20:12] *** Sarten-X has quit IRC
[19:30:25] *** Sarten-X has joined #chromium-os
[19:33:40] *** nexusz99 has quit IRC
[19:45:12] *** D|sT has quit IRC
[20:03:41] *** wbednarski has quit IRC
[20:21:11] *** ChocoboLee has joined #chromium-os
[20:22:03] *** ChocoboLee_ has joined #chromium-os
[20:25:45] *** ChocoboLee has quit IRC
[20:25:45] *** ChocoboLee_ is now known as ChocoboLee
[20:30:33] *** unreal has quit IRC
[20:31:22] *** unreal has joined #chromium-os
[20:44:57] *** Knocks has joined #chromium-os
[21:14:07] <crosbot> tree became '?'
[21:14:22] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2 seaboard full" from 1e0e7f7a2ec6b8d17a27ddeb8f5b79909c0c1d40: Ryo Hashimoto <hashimoto at chromium dot org>)'
[21:18:38] *** gauravsh has joined #chromium-os
[21:18:38] *** ChanServ sets mode: +v gauravsh
[21:27:52] *** rharrison_chrome has joined #chromium-os
[21:28:25] *** rharrison_chrome has quit IRC
[21:30:11] *** D|sT has joined #chromium-os
[21:51:41] <crosbot> tree became 'Tree is open (the seaboard build is green now)'
[22:34:10] *** Ruetobas has quit IRC
[22:42:14] *** D|sT has quit IRC
[22:42:31] *** Ruetobas has joined #chromium-os
[22:56:04] *** gauravsh has quit IRC
[22:57:01] *** Sergiu has joined #chromium-os
[22:57:02] *** Sergiu has joined #chromium-os
[23:19:03] *** gauravsh has joined #chromium-os
[23:19:04] *** ChanServ sets mode: +v gauravsh
[23:46:40] *** SoulRaven has quit IRC





top