ChromiumOS not booting

[Peter Lang]

Hi have a variety of devices that I am trying to get to run ChromiumOS. They are as follows:

Device 1.

Processor: Intel Atom N280

Memory: 1GB DDR-3

Graphics: Intel GL40

Device 2.

Processor: AMD Sempron 2100+

Memory: 1GB DDR-2

Graphics: ATI Radeon X1250

Device 3.

Processor: VIA Eden CA22/P680

Memory: 1GB

Graphics: VIA S3

Device 4.

Processor: AMD Dual-core T56N

Memory: 2GB

Graphics: AMD Radeon HD 6320

None of the devices will boot. I do not see anything on the screen when they try. I know my build is ok, as I have tried it on my desktop and it boots into ChomiumOS fine, but on any of these devices I get nothing, not even an error. At frist I thought it was a known problem with the Radeon graphics card, but device 1 does not have that, it has an Intel card.

Any ideas of where I should be looking. I would REALLY like to get these devices running.

[Peter Lang]

Anyone able to chime in on this?

[Sonny Rao]

The machine with radeon graphics might require more tweaking, as you said.  For the one with Intel graphics

try building the image with more kernel output. You can try passing this to build_image

--enable-serial=tty1

and see if you get anything on the screen during boot

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
 

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

[Brandon Nozaki Miller]

before installing, had you tried running it on that exact machine from USB?

[Peter Lang]

Yes, I am not trying to install it, but instead I want it to run from USB.

[Brandon Nozaki Miller]

You might just go over all of the specs one more time and make sure you have the right build, is it x86 or 64? Is it ARM, AMD or intel?

If you triple check everything and it still doesn't work, it could just be that Chromium wont work with the hardware you have. But be sure to check everything closely.

[Peter Lang]

Sorry it took so long to get back to you, but I tried adding the flag you mentioned but got nothing. I am running the dev build so should it not show kernel output by default anyway? It tried tty0 also, but that did not work.

[Sonny Rao]

what bootloader are you using, grub? You should be able to look at
the grub config files on partition 12 and see the kernel command lines
used. Can you double check if you have console=tty1 and loglevel=7 ?

[Peter Lang]

Finally!!! I have the solution.

Sonny, you were quite right, we were editing the wrong file. We both knew that, but I could not find the right file. Where I failed was not reading the README file in the syslinux directory, which clearly states "Partition 12 contains the the active bootloader configuration when booting from a non-Chrome OS BIOS."

Doh!!!! So yeah, I mounted that partition and hey presto, there are my config files. Changed the /tempmount/syslinux/usb.A.cfg file to boot from root=/dev/sda3 and hey presto, it booted no problem.

Thank you for your help in fixing this issue. I would not have got there without you.

Peter

On Fri, Oct 11, 2013 at 6:28 PM, Sonny Rao <sonn...@chromium.org> wrote:

On Fri, Oct 11, 2013 at 3:21 PM, Peter Lang <pe...@thelangclan.com> wrote:
> I do not think they are that numerous or confusing. There is one that is the
> main config file (syslinux.cfg). It specifys the various other files and
> what they do. The default.cfg file specifies the default, which in this case
> is chromeos-usb. In the syslinux file comeos-usb is told to us
> /syslinux/usb.A.cfg as its config file. In usb.A.cfg is where the bootloader
> is told what kernel to use and the perrameters to send to it.

I just remember getting confused about which one got used in the past,
because it wasn't obvious for some reason but I can't remember the
details, which is why i was suggesting trying to change more
entries/files just to be sure that it's using the one you think it
is.. because evidence seems to say it's not using the one that you
think it should right now, doesn't it ?

>
> The interesting thing thought is that in the grub config file (which we are
> not using) the USB boot option is told to use a completely different kernel
> that resides on the same partition as the config files (which is not the
> case with the kernel that syslinux uses).
>
> Why is that I wonder?

Well grub is more advanced than syslinux, It can read more
filesystems, and I think syslinux probably cannot.  But you're right
that it's somewhat arbitrary, and one might just consider that to be a
bug.

>
>
> On Fri, Oct 11, 2013 at 6:11 PM, Sonny Rao <sonn...@chromium.org> wrote:
>>
>> On Fri, Oct 11, 2013 at 8:25 AM, Peter Lang <pe...@thelangclan.com> wrote:
>> > ok, so I have made something of a breakthrough, but still not there.
>> >
>> > On playing around and reading I discovered that by default you can
>> > interupt
>> > the bootloader at boot time by having the CRTL and ALT key pressed (not
>> > sure
>> > if it is just one of those keys, but pressing both work). Then, with no
>> > other hard drive in the system, if I feed the commands to the bootloader
>> > it
>> > loads fine on 'root=/dev/sda3'. So I know the settings are correct. One
>> > vital setting is the rootwait flag, which is needed to give the kernel
>> > time
>> > to recognize the USB drive.
>> >
>> > However, it still does not boot when I do not interupt the bootloader.
>> > Something weird is going on, and I suspect that whatever parameters
>> > being
>> > passed to the bootloader are not being read from the config files. The
>> > settings MUST be coming from somewhere else, but I have looked and can
>> > not
>> > see where.
>> >
>> > Any ideas?
>>
>> my only idea here is that the config files are numerous and confusing
>> and maybe trying changing all of them to be the same?  just to be sure
>> it's not choosing the wrong one somewhere
>>
>> >
>> >
>> > On Fri, Oct 11, 2013 at 9:30 AM, Peter Lang <pe...@thelangclan.com>
>> > wrote:
>> >>
>> >> So I tried changing the flags you suggested for PROMPT and TIMEOUT and
>> >> nothing happened. I then added TOTALTIMEOUT but still nothing
>> >> different.
>> >>
>> >> I changed the root settings in root.A.cfg to 'root=/dev/sda3' nothing
>> >> happened.
>> >>
>> >> I removed i915.modeset=1 from usb.A.cfg nothing happened. The console
>> >> was
>> >> already set to tty1.
>> >>
>> >> Basically, no matter what I change in any of these confg files, nothing
>> >> changes.
>> >>
>> >>
>> >> On Fri, Oct 11, 2013 at 9:01 AM, Peter Lang <pe...@thelangclan.com>
>> >> wrote:
>> >>>
>> >>> I have been wondering what the i915.modeset setting was about. Any
>> >>> ideas?
>> >>>
>> >>> So I did some interesting digging, based in part on an article I found
>> >>>
>> >>> http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-a-cr-48
>> >>>
>> >>> When I run 'rootdev -s' i get /dev/sdb3 when there is a hard drive
>> >>> present. When I run 'cgpt show /dev/sdb' it shows that partition 3 is
>> >>> labeled "ROOT-A", which means I would assume that it uses partition 2
>> >>> -
>> >>> labelled "KERN-A" for its kernel. This would lead me to believe that
>> >>> the
>> >>> boot is governed by root.A.cfg and not usb.A.cfg. Problem comes in
>> >>> then as
>> >>> in root.A.cfg the root is set to 'root=HDROOTA'. This may be a wild
>> >>> goose
>> >>> chase, but I am going to play with this and the settings you suggested
>> >>> and
>> >>> see where I get to.
>> >>>
>> >>> I appreciate all your help with this.
>> >>>
>> >>>
>> >>> On Thu, Oct 10, 2013 at 5:19 PM, Sonny Rao <sonn...@chromium.org>
>> >>> wrote:
>> >>>>
>> >>>> you won't see anything if syslinux is used
>> >>>> in the syslinux.cfg file you could try changing PROMPT and TIMEOUT to
>> >>>> see if something shows up
>> >>>> I did notice in your usb.A.cfg that it says console=tty2
>> >>>> you might try changing it to tty1 and get rid of i915.modeset=1 and
>> >>>> see if anything shows up
>> >>>>
>> >>>> On Thu, Oct 10, 2013 at 1:03 PM, Peter Lang <pe...@thelangclan.com>
>> >>>> wrote:
>> >>>> > I thought the the root flag was simply to say where the root
>> >>>> > filesystem
>> >>>> > should be mounted? In the grub conf, after  linux
>> >>>> > (hd0,3)/boot/vmlinuz
>> >>>> > .....
>> >>>> > there is also root/dev/sdb3 for example.
>> >>>> >
>> >>>> > I have tried editing both the conf files and nothing changes. Also,
>> >>>> > if
>> >>>> > the
>> >>>> > system was reading the syslinux conf files or the grub conf files,
>> >>>> > should I
>> >>>> > not be able to see the menu items?
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > On Thu, Oct 10, 2013 at 3:42 PM, Sonny Rao <sonn...@chromium.org>
>> >>>> > wrote:
>> >>>> >>
>> >>>> >> syslinux specifies it on the command line
>> >>>> >> so if you look at a mounted partition 12 from the image
>> >>>> >> there's a bunch of config files in the syslinux directory like
>> >>>> >> syslinux/usb.A.cfg
>> >>>> >>
>> >>>> >> which has :
>> >>>> >>   menu label chromeos-usb.A
>> >>>> >>   kernel vmlinuz.A
>> >>>> >>   append quiet console=tty2 init=/sbin/init boot=local rootwait ro
>> >>>> >> noresume noswap loglevel=1 noinitrd root=/dev/sdb3 i915.modeset=1
>> >>>> >> cros_legacy cros_debug
>> >>>> >>
>> >>>> >> label chromeos-vusb.A
>> >>>> >>   menu label chromeos-vusb.A
>> >>>> >>   kernel vmlinuz.A
>> >>>> >>   append quiet console=tty2 init=/sbin/init boot=local rootwait ro
>> >>>> >> noresume noswap loglevel=1 noinitrd dm_verity.error_behavior=3
>> >>>> >> dm_verity.max_bios=-1 dm_verity.dev_wait=0 root=/dev/dm-0
>> >>>> >> i915.modeset=1 cros_legacy cros_debug dm="1 vroot none ro 1,0
>> >>>> >> 2097152
>> >>>> >> verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=2097152
>> >>>> >> alg=sha1
>> >>>> >> root_hexdigest=16051e84d7663da468475406005369cee35bb969
>> >>>> >>
>> >>>> >>
>> >>>> >> salt=5d0c76b035b7ad1074568f5649559d5c97655e0b6a7899187cbb7ffe748b5098"
>> >>>> >>
>> >>>> >>
>> >>>> >> and you see the root=/dev/sdb3 in there under chromeos-usb.A
>> >>>> >>
>> >>>> >> that is where the implict assumption of USB being the 2nd device
>> >>>> >> exists
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >> On Thu, Oct 10, 2013 at 11:59 AM, Peter Lang
>> >>>> >> <pe...@thelangclan.com>
>> >>>> >> wrote:
>> >>>> >> > No, this just gets more and more weird... I can not see where
>> >>>> >> > syslinux
>> >>>> >> > specifies any information about which drive/partition to use.
>> >>>> >> > The
>> >>>> >> > grub.conf
>> >>>> >> > does however.
>> >>>> >> >
>> >>>> >> > grub.conf:
>> >>>> >> > menuentry "Alternate USB Boot"  {
>> >>>> >> >   linux (hd0,3)/boot/vmlinuz .....
>> >>>> >> >
>> >>>> >> > Which seems like it would be correct if there is no other drives
>> >>>> >> > present
>> >>>> >> > hd0
>> >>>> >> > = first hard drive ,3 = third partition
>> >>>> >> >
>> >>>> >> > syslinux config files have nothing like that.
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > On Thu, Oct 10, 2013 at 2:12 PM, Sonny Rao
>> >>>> >> > <sonn...@chromium.org>
>> >>>> >> > wrote:
>> >>>> >> >>
>> >>>> >> >> On Thu, Oct 10, 2013 at 10:46 AM, Peter Lang
>> >>>> >> >> <pe...@thelangclan.com>
>> >>>> >> >> wrote:
>> >>>> >> >> > So, you're saying if you remove the 4gb SDD flash module,
>> >>>> >> >> > that
>> >>>> >> >> > same
>> >>>> >> >> > machine with the USB stick won't boot?
>> >>>> >> >> >
>> >>>> >> >> > Yes - weird right?
>> >>>> >> >> >
>> >>>> >> >> > It shouldn't.  I'm not aware of any requirement on there
>> >>>> >> >> > being a
>> >>>> >> >> > hard
>> >>>> >> >> > drive.  It really doesn't know what kind of device it's
>> >>>> >> >> > booting
>> >>>> >> >> > from
>> >>>> >> >> > (HDD, SSD, USB, MMC card), it just uses whatever is specified
>> >>>> >> >> > on
>> >>>> >> >> > the
>> >>>> >> >> > command line.
>> >>>> >> >> >
>> >>>> >> >> > I am wondering if it is a grub issue, where it assumes there
>> >>>> >> >> > is
>> >>>> >> >> > a
>> >>>> >> >> > hard
>> >>>> >> >> > drive
>> >>>> >> >> > present on /dev/hdaX and assumes that the usb drive will be
>> >>>> >> >> > the
>> >>>> >> >> > next
>> >>>> >> >> > device
>> >>>> >> >> > /dev/hdbX - if that makes sense
>> >>>> >> >>
>> >>>> >> >> Yeah, it sounds like it could be a bootloader issue. it looks
>> >>>> >> >> like
>> >>>> >> >> syslinux is assuming /dev/sdb for it's USB configs which would
>> >>>> >> >> in
>> >>>> >> >> fact
>> >>>> >> >> require another disk, so that's probably the issue right there.
>> >>>> >> >> if you change the syslinux to use sda instead of sdb, does it
>> >>>> >> >> boot
>> >>>> >> >> ?
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> > On Thu, Oct 10, 2013 at 1:26 PM, Sonny Rao
>> >>>> >> >> > <sonn...@chromium.org>
>> >>>> >> >> > wrote:
>> >>>> >> >> >>
>> >>>> >> >> >> On Thu, Oct 10, 2013 at 9:51 AM, Peter Lang
>> >>>> >> >> >> <pe...@thelangclan.com>
>> >>>> >> >> >> wrote:
>> >>>> >> >> >> > OK, so I have made a breakthrough. The device I was trying
>> >>>> >> >> >> > to
>> >>>> >> >> >> > boot
>> >>>> >> >> >> > to
>> >>>> >> >> >> > USB
>> >>>> >> >> >> > does not have a hard drive in it. It is a thin client with
>> >>>> >> >> >> > no
>> >>>> >> >> >> > flash.
>> >>>> >> >> >> > I
>> >>>> >> >> >> > was
>> >>>> >> >> >> > messing around with an old 4gb SDD flash module, trying to
>> >>>> >> >> >> > get
>> >>>> >> >> >> > ubuntu
>> >>>> >> >> >> > installed on it, and accidentally left my Chomium USB
>> >>>> >> >> >> > drive
>> >>>> >> >> >> > in the
>> >>>> >> >> >> > machine.
>> >>>> >> >> >> > It booted, kind of. I did not get the ChromeOS welcome
>> >>>> >> >> >> > screen, but
>> >>>> >> >> >> > I
>> >>>> >> >> >> > was
>> >>>> >> >> >> > able to Crtl + Alt + F2 and get to the logon prommt and
>> >>>> >> >> >> > login.
>> >>>> >> >> >>
>> >>>> >> >> >> So, you're saying if you remove the 4gb SDD flash module,
>> >>>> >> >> >> that
>> >>>> >> >> >> same
>> >>>> >> >> >> machine with the USB stick won't boot?
>> >>>> >> >> >>
>> >>>> >> >> >> >
>> >>>> >> >> >> > However I am still not seeing any logging messages as it
>> >>>> >> >> >> > is
>> >>>> >> >> >> > booting,
>> >>>> >> >> >> > so
>> >>>> >> >> >> > I am
>> >>>> >> >> >> > still struggling to see which bootloader it is using
>> >>>> >> >> >> > (although I
>> >>>> >> >> >> > suspect
>> >>>> >> >> >> > it
>> >>>> >> >> >> > is syslinux).
>> >>>> >> >> >> >
>> >>>> >> >> >> > Why does chromium need to have a hard drive in the device
>> >>>> >> >> >> > to
>> >>>> >> >> >> > boot?
>> >>>> >> >> >>
>> >>>> >> >> >> It shouldn't.  I'm not aware of any requirement on there
>> >>>> >> >> >> being
>> >>>> >> >> >> a
>> >>>> >> >> >> hard
>> >>>> >> >> >> drive.  It really doesn't know what kind of device it's
>> >>>> >> >> >> booting
>> >>>> >> >> >> from
>> >>>> >> >> >> (HDD, SSD, USB, MMC card), it just uses whatever is
>> >>>> >> >> >> specified
>> >>>> >> >> >> on the
>> >>>> >> >> >> command line.
>> >>>> >> >> >>
>> >>>> >> >> >> >
>> >>>> >> >> >> > Peter
>> >>>> >> >> >> >
>> >>>> >> >> >> >
>> >>>> >> >> >> > On Tue, Oct 8, 2013 at 7:25 PM, Peter Lang
>> >>>> >> >> >> > <pe...@thelangclan.com>
>> >>>> >> >> >> > wrote:
>> >>>> >> >> >> >>
>> >>>> >> >> >> >> I will need to research that and get back to you. Thanks
>> >>>> >> >> >> >> for
>> >>>> >> >> >> >> the
>> >>>> >> >> >> >> direction.
>> >>>> >> >> >> >>
>> >>>> >> >> >> >>
>> >>>> >> >> >> >> On Tue, Oct 8, 2013 at 7:23 PM, Sonny Rao
>> >>>> >> >> >> >> <sonn...@chromium.org>
>> >>>> >> >> >> >> wrote:
>> >>>> >> >> >> >>>
>> >>>> >> >> >> >>> I think that would imply that you're booting using
>> >>>> >> >> >> >>> syslinux
>> >>>> >> >> >> >>> and
>> >>>> >> >> >> >>> not
>> >>>> >> >> >> >>> grub.  grub will only be used if your BIOS is using EFI
>> >>>> >> >> >> >>> mode.
>> >>>> >> >> >> >>>
>> >>>> >> >> >> >>> Try changing the syslinux config files (which are more
>> >>>> >> >> >> >>> numerous)
>> >>>> >> >> >> >>>
>> >>>> >> >> >> >>> On Tue, Oct 8, 2013 at 4:20 PM, Peter Lang
>> >>>> >> >> >> >>> <pe...@thelangclan.com>
>> >>>> >> >> >> >>> wrote:
>> >>>> >> >> >> >>> > I did not.
>> >>>> >> >> >> >>> >
>> >>>> >> >> >> >>> >
>> >>>> >> >> >> >>> > On Tue, Oct 8, 2013 at 7:11 PM, Sonny Rao
>> >>>> >> >> >> >>> > <sonn...@chromium.org>
>> >>>> >> >> >> >>> > wrote:
>> >>>> >> >> >> >>> >>
>> >>>> >> >> >> >>> >> hmm, do you actually see the grub menu pop up?  it's
>> >>>> >> >> >> >>> >> possible
>> >>>> >> >> >> >>> >> that
>> >>>> >> >> >> >>> >> its
>> >>>> >> >> >> >>> >> booting using syslinux rather than grub if you do not
>> >>>> >> >> >> >>> >> see it.
>> >>>> >> >> >> >>> >>
>> >>>> >> >> >> >>> >> On Tue, Oct 8, 2013 at 4:09 PM, Peter Lang
>> >>>> >> >> >> >>> >> <pe...@thelangclan.com>
>> >>>> >> >> >> >>> >> wrote:
>> >>>> >> >> >> >>> >> > Totally, but it is the only grub.conf I could find.
>> >>>> >> >> >> >>> >> > I
>> >>>> >> >> >> >>> >> > found
>> >>>> >> >> >> >>> >> > it
>> >>>> >> >> >> >>> >> > in
>> >>>> >> >> >> >>> >> > boot/efi/boot, does that sound right?
>> >>>> >> >> >> >>> >> >
>> >>>> >> >> >> >>> >> >
>> >>>> >> >> >> >>> >> > On Tue, Oct 8, 2013 at 6:59 PM, Sonny Rao
>> >>>> >> >> >> >>> >> > <sonn...@chromium.org>
>> >>>> >> >> >> >>> >> > wrote:
>> >>>> >> >> >> >>> >> >>
>> >>>> >> >> >> >>> >> >> Yes you should see a good bit of spew to the
>> >>>> >> >> >> >>> >> >> console.
>> >>>> >> >> >> >>> >> >> Is
>> >>>> >> >> >> >>> >> >> it
>> >>>> >> >> >> >>> >> >> possible
>> >>>> >> >> >> >>> >> >> that you're not updating the correct grub config
>> >>>> >> >> >> >>> >> >> file?
>> >>>> >> >> >> >>> >> >>
>> >>>> >> >> >> >>> >> >> On Tue, Oct 8, 2013 at 2:17 PM, Peter Lang
>> >>>> >> >> >> >>> >> >> <pe...@thelangclan.com>
>> >>>> >> >> >> >>> >> >> wrote:
>> >>>> >> >> >> >>> >> >> > Thanks for the reply Sonny, I think I must be
>> >>>> >> >> >> >>> >> >> > doing
>> >>>> >> >> >> >>> >> >> > something
>> >>>> >> >> >> >>> >> >> > wrong
>> >>>> >> >> >> >>> >> >> > here. I
>> >>>> >> >> >> >>> >> >> > made the changes to grub.cfg as suggested, but
>> >>>> >> >> >> >>> >> >> > when
>> >>>> >> >> >> >>> >> >> > I
>> >>>> >> >> >> >>> >> >> > try
>> >>>> >> >> >> >>> >> >> > to
>> >>>> >> >> >> >>> >> >> > boot,
>> >>>> >> >> >> >>> >> >> > like
>> >>>> >> >> >> >>> >> >> > I
>> >>>> >> >> >> >>> >> >> > said nothing. Now when I take it to a dell
>> >>>> >> >> >> >>> >> >> > OptiPlex
>> >>>> >> >> >> >>> >> >> > 745
>> >>>> >> >> >> >>> >> >> > it
>> >>>> >> >> >> >>> >> >> > boots,
>> >>>> >> >> >> >>> >> >> > but
>> >>>> >> >> >> >>> >> >> > I
>> >>>> >> >> >> >>> >> >> > would have thought that changing the loglevel
>> >>>> >> >> >> >>> >> >> > would
>> >>>> >> >> >> >>> >> >> > make
>> >>>> >> >> >> >>> >> >> > the
>> >>>> >> >> >> >>> >> >> > system
>> >>>> >> >> >> >>> >> >> > spit
>> >>>> >> >> >> >>> >> >> > out
>> >>>> >> >> >> >>> >> >> > a load of messages before you go the the
>> >>>> >> >> >> >>> >> >> > Chromium
>> >>>> >> >> >> >>> >> >> > Welcome
>> >>>> >> >> >> >>> >> >> > message. Am
>> >>>> >> >> >> >>> >> >> > I
>> >>>> >> >> >> >>> >> >> > wrong?
>> >>>> >> >> >> >>> >> >> >
>> >>>> >> >> >> >>> >> >> > Peter
>> >>>> >> >> >> >>> >> >> >
>> >>>> >> >> >> >>> >> >> >
>> >>>> >> >> >> >>> >> >> > On Tue, Oct 8, 2013 at 1:32 PM, Sonny Rao
>> >>>> >> >> >> >>> >> >> > <sonn...@chromium.org>
>> >>>> >> >> >> >>> >> >> > wrote:
>> >>>> >> >> >> >>> >> >> >>
>> >>>> >> >> >> >>> >> >> >> that's wierd, absolutely nothing?  Hmm, does it
>> >>>> >> >> >> >>> >> >> >> hae the
>> >>>> >> >> >> >>> >> >> >> i915.modeset=1
>> >>>> >> >> >> >>> >> >> >> in the command line? If it does, try taking
>> >>>> >> >> >> >>> >> >> >> that
>> >>>> >> >> >> >>> >> >> >> out.
>> >>>> >> >> >> >>> >> >> >> Also
>> >>>> >> >> >> >>> >> >> >> try
>> >>>> >> >> >> >>> >> >> >> adding
>> >>>> >> >> >> >>> >> >> >> earlyprintk to the command line
>> >>>> >> >> >> >>> >> >> >>
>> >>>> >> >> >> >>> >> >> >> On Tue, Oct 8, 2013 at 7:40 AM, Peter Lang
>> >>>> >> >> >> >>> >> >> >> <pe...@thelangclan.com>
>> >>>> >> >> >> >>> >> >> >> wrote:
>> >>>> >> >> >> >>> >> >> >> > I made the changes above and still nothing
>> >>>> >> >> >> >>> >> >> >> > shows
>> >>>> >> >> >> >>> >> >> >> > up.
>> >>>> >> >> >> >>> >> >> >> > Any
>> >>>> >> >> >> >>> >> >> >> > suggestions?
>> >>>> >> >> >> >>> >> >> >> >
>> >>>> >> >> >> >>> >> >> >> >
>> >>>> >> >> >> >>> >> >> >> > On Tue, Oct 1, 2013 at 6:46 PM, Peter Lang
>> >>>> >> >> >> >>> >> >> >> > <pe...@thelangclan.com>
>> >>>> >> >> >> >>> >> >> >> > wrote:
>> >>>> >> >> >> >>> >> >> >> >>
>> >>>> >> >> >> >>> >> >> >> >> OK, will give that a go. I will not be able
>> >>>> >> >> >> >>> >> >> >> >> to
>> >>>> >> >> >> >>> >> >> >> >> look
>> >>>> >> >> >> >>> >> >> >> >> into
>> >>>> >> >> >> >>> >> >> >> >> it
>> >>>> >> >> >> >>> >> >> >> >> until
>> >>>> >> >> >> >>> >> >> >> >> monday,
>> >>>> >> >> >> >>> >> >> >> >> but thank you for the help.
>> >>>> >> >> >> >>> >> >> >> >>
>> >>>> >> >> >> >>> >> >> >> >>
>> >>>> >> >> >> >>> >> >> >> >> On Tue, Oct 1, 2013 at 6:41 PM, Sonny Rao
>> >>>> >> >> >> >>> >> >> >> >> <sonn...@chromium.org>
>> >>>> >> >> >> >>> >> >> >> >> wrote:
>> >>>> >> >> >> >>> >> >> >> >>>
>> >>>> >> >> >> >>> >> >> >> >>> You could just edit the file and make it
>> >>>> >> >> >> >>> >> >> >> >>> console=tty1
>> >>>> >> >> >> >>> >> >> >> >>> and
>> >>>> >> >> >> >>> >> >> >> >>> loglevel=9
>> >>>> >> >> >> >>> >> >> >> >>> tty1 is the one thats up by default when
>> >>>> >> >> >> >>> >> >> >> >>> you're
>> >>>> >> >> >> >>> >> >> >> >>> booting,
>> >>>> >> >> >> >>> >> >> >> >>> so
>> >>>> >> >> >> >>> >> >> >> >>> that's
>> >>>> >> >> >> >>> >> >> >> >>> the
>> >>>> >> >> >> >>> >> >> >> >>> one you want to use
>> >>>> >> >> >> >>> >> >> >> >>>
>> >>>> >> >> >> >>> >> >> >> >>> On Tue, Oct 1, 2013 at 1:44 PM, Peter Lang
>> >>>> >> >> >> >>> >> >> >> >>> <pe...@thelangclan.com>
>> >>>> >> >> >> >>> >> >> >> >>> wrote:
>> >>>> >> >> >> >>> >> >> >> >>> > It would appear to be console=tty2 and
>> >>>> >> >> >> >>> >> >> >> >>> > loglevel=1.
>> >>>> >> >> >> >>> >> >> >> >>> > Should
>> >>>> >> >> >> >>> >> >> >> >>> > I
>> >>>> >> >> >> >>> >> >> >> >>> > change
>> >>>> >> >> >> >>> >> >> >> >>> > the
>> >>>> >> >> >> >>> >> >> >> >>> > log
>> >>>> >> >> >> >>> >> >> >> >>> > level and build with
>> >>>> >> >> >> >>> >> >> >> >>> > --enable_serial=tty2?
>> >>>> >> >> >> >>> >> >> >> >>> >
>> >>>> >> >> >> >>> >> >> >> >>> >
>> >>>> >> >> >> >>> >> >> >> >>> > On Tue, Oct 1, 2013 at 4:09 PM, Sonny Rao

[Sonny Rao]

glad to hear it

[Peter Lang]

Oh, would you look at that, some clever person already forsaw this issue and allowed the builder to pass in a flag to the ./build_image script. You can pass in --usb_disk=<location> 

Going to try it out.

Peter