meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

Quoted 25 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep 
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

So is the bitbake command showing the results before the cedartrail.conf options take affect??

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 49 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

The integration between the boot loader options is something that needs work. At some point I hope to replace GRUB with syslinux in all possible situations in order simplify the option handling and present a consistent boot interface between live images, iso limages, and disk images.

Quoted 64 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Quoted 5 lines

The integration between the boot loader options is something that needs work. At some point I hope to replace GRUB with syslinux in all possible situations in order simplify the option handling and present a consistent boot interface between live images, iso limages, and disk images.

Quoted 86 lines · jfabernathy

Quoted 63 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

Quoted 8 lines

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Sorry, ddimage wasn't meant to fix the issue, just as a slightly more convenient/safe wrapper around dd.

I'm not familiar with the error you are seeing with the live image. Can you point me to the thread or the bug?

--
Darren

Quoted 5 lines

Quoted 5 lines

The integration between the boot loader options is something that needs work. At some point I hope to replace GRUB with syslinux in all possible situations in order simplify the option handling and present a consistent boot interface between live images, iso limages, and disk images.

Quoted 96 lines · Darren Hart

Quoted 86 lines · jfabernathy

Quoted 63 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

Quoted 8 lines

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Quoted 5 lines

Sorry, ddimage wasn't meant to fix the issue, just as a slightly more convenient/safe wrapper around dd.

I'm not familiar with the error you are seeing with the live image. Can you point me to the thread or the bug?

Well this boot error issue seems to be USB Key related because I just did the ddimage script on a edison core-image-sato image using the .hddimg file and it worked correctly on a hard drive. This was a 1.2GB image. Now I'll have to add in the parameters that give you more free disk space now that I'm testing with a real hard drive.

The readme in most of the x86 BSP directory in meta-intel talk about if you get boot errors to:

dd if=/dev/zero of=/dev/sdf bs=1M count=512

I have not found this to work. Maybe it's a count size issue. I always use 512, but maybe it should be 4096 for a 4GB USB key.

Quoted 110 lines · jfabernathy

Quoted 95 lines · Darren Hart

Quoted 86 lines · jfabernathy

Quoted 63 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

Quoted 8 lines

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Quoted 5 lines

Sorry, ddimage wasn't meant to fix the issue, just as a slightly more convenient/safe wrapper around dd.

I'm not familiar with the error you are seeing with the live image. Can you point me to the thread or the bug?

Well this boot error issue seems to be USB Key related because I just did the ddimage script on a edison core-image-sato image using the .hddimg file and it worked correctly on a hard drive. This was a 1.2GB image. Now I'll have to add in the parameters that give you more free disk space now that I'm testing with a real hard drive.

The readme in most of the x86 BSP directory in meta-intel talk about if you get boot errors to:

Quoted 5 lines

dd if=/dev/zero of=/dev/sdf bs=1M count=512

I have not found this to work. Maybe it's a count size issue. I always use 512, but maybe it should be 4096 for a 4GB USB key.

What is the boot error?

Quoted 114 lines · Darren Hart

Quoted 112 lines · jfabernathy

Quoted 95 lines · Darren Hart

Quoted 86 lines · jfabernathy

Quoted 63 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

Quoted 8 lines

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Quoted 5 lines

Sorry, ddimage wasn't meant to fix the issue, just as a slightly more convenient/safe wrapper around dd.

I'm not familiar with the error you are seeing with the live image. Can you point me to the thread or the bug?

Well this boot error issue seems to be USB Key related because I just did the ddimage script on a edison core-image-sato image using the .hddimg file and it worked correctly on a hard drive. This was a 1.2GB image. Now I'll have to add in the parameters that give you more free disk space now that I'm testing with a real hard drive.

The readme in most of the x86 BSP directory in meta-intel talk about if you get boot errors to:

dd if=/dev/zero of=/dev/sdf bs=1M count=512

Quoted 5 lines

Quoted 3 lines

I have not found this to work. Maybe it's a count size issue. I always use 512, but maybe it should be 4096 for a 4GB USB key.

What is the boot error?

SYSLINUX 4.03 2010-10-22 CHS Load error- Boot error

Jim A

Quoted 119 lines · jfabernathy

Quoted 118 lines · Darren Hart

Quoted 107 lines · jfabernathy

Quoted 95 lines · Darren Hart

Quoted 86 lines · jfabernathy

Quoted 63 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

Quoted 8 lines

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Quoted 5 lines

Sorry, ddimage wasn't meant to fix the issue, just as a slightly more convenient/safe wrapper around dd.

I'm not familiar with the error you are seeing with the live image. Can you point me to the thread or the bug?

Well this boot error issue seems to be USB Key related because I just did the ddimage script on a edison core-image-sato image using the .hddimg file and it worked correctly on a hard drive. This was a 1.2GB image. Now I'll have to add in the parameters that give you more free disk space now that I'm testing with a real hard drive.

Quoted 8 lines

The readme in most of the x86 BSP directory in meta-intel talk about if you get boot errors to:

dd if=/dev/zero of=/dev/sdf bs=1M count=512

I have not found this to work. Maybe it's a count size issue. I always use 512, but maybe it should be 4096 for a 4GB USB key.

What is the boot error?

Quoted 3 lines

SYSLINUX 4.03 2010-10-22 CHS Load error- Boot error

Jim A

OK, I suggest following the instructions for creating a USBZIP format in README.hardware. If that fails, this merits a bug. Regardless, as rework the images for 1.3, we should be able to avoid the many many boot errors like this that people have been reporting and we've been working around.

Quoted 4 lines · Darren Hart

Quoted 4 lines

Quoted 2 lines

What is the boot error?

SYSLINUX 4.03 2010-10-22 CHS Load error- Boot error

Quoted 6 lines

Quoted 1 line

Jim A

OK, I suggest following the instructions for creating a USBZIP format in README.hardware. If that fails, this merits a bug. Regardless, as rework the images for 1.3, we should be able to avoid the many many boot errors like this that people have been reporting and we've been working around.

I'll test the USBZIP method, but that has a many steps as the How Do I- hard drive method. I think we need a script like ddimage for USBZIP method.

Quoted 11 lines · jfabernathy

Quoted 10 lines · Darren Hart

Quoted 5 lines

Quoted 2 lines

What is the boot error?

SYSLINUX 4.03 2010-10-22 CHS Load error- Boot error

Jim A

OK, I suggest following the instructions for creating a USBZIP format in README.hardware. If that fails, this merits a bug. Regardless, as rework the images for 1.3, we should be able to avoid the many many boot errors like this that people have been reporting and we've been working around.

Quoted 3 lines

I'll test the USBZIP method, but that has a many steps as the How Do I- hard drive method. I think we need a script like ddimage for USBZIP method.

Attached. I've passed this out to a few people. Would people like to see this in scripts/contrib?

Quoted 16 lines · Darren Hart

Quoted 14 lines · jfabernathy

Quoted 10 lines · Darren Hart

Quoted 5 lines

Quoted 2 lines

What is the boot error?

SYSLINUX 4.03 2010-10-22 CHS Load error- Boot error

Jim A

OK, I suggest following the instructions for creating a USBZIP format in README.hardware. If that fails, this merits a bug. Regardless, as rework the images for 1.3, we should be able to avoid the many many boot errors like this that people have been reporting and we've been working around.

I'll test the USBZIP method, but that has a many steps as the How Do I- hard drive method. I think we need a script like ddimage for USBZIP method.

Quoted 3 lines

Attached. I've passed this out to a few people. Would people like to see this in scripts/contrib?

I think the script is great and should be in the contrib directory. One question about it. on the instructions to remove and reinsert the usb key, mine automounts on reinsertion. Is that going to create a problem?? What the script created booted, but it seemed odd that the automount happened, and the script seems to mount in the /tmp dir.

Quoted 110 lines · jfabernathy

Quoted 95 lines · Darren Hart

Quoted 86 lines · jfabernathy

Quoted 63 lines · Darren Hart

Quoted 56 lines · jfabernathy

Quoted 48 lines · Darren Hart

Quoted 47 lines · jfabernathy

Quoted 24 lines · Darren Hart

Quoted 15 lines · jfabernathy

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

Quoted 8 lines

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Quoted 8 lines

Lets make sure your environment is what we expect. Please provide the output of:

$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=

If it is not "115200 ttyS0" then it is getting overwritten somewhere either in your config, or possibly by an inappropriate selection of an assignment operator (=, ?=, etc.) in edison.

okay now I'm confused. while the cedartrail.conf file has the following:
SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

The output of the bitbake command you suggested above gives:

jim@ubuntu-x64:~/poky/build$ bitbake core-image-minimal -e | grep
SERIAL_CONSOLE=

# SERIAL_CONSOLE=115200 ttyS0
SERIAL_CONSOLE="115200 ttyS0"
jim@ubuntu-x64:~/poky/build$

Quoted 7 lines

Quoted 2 lines

So is the bitbake command showing the results before the cedartrail.conf options take affect??

variable assignments can be tricky, and are not the easiest things to track down. I suggest looking through your configured layers and looking for all the SERIAL_CONSOLE assignments using ttyS3 and ttyS0 and see if you can determine what is overriding your cedartrail.conf setting.

Quoted 6 lines

What I found out is the only variable that matters for login console in my situation is SERIAL_CONSOLE because I have to use grub and the boot from hard drive method because my image can't be put on a USB Flash for some reason. So I manually have to edit the grub.cfg file as documented on the wiki "How Do I" section of putting Yocto on a hard drive. Adding console=ttyS0,115200 on the linux statement takes care of the boot console.

Quoted 4 lines

I believe this is a manual process currently. Please open an enhancement in bugzilla for your specific situation and I'll incporporate into the larger boot process and image revamp we're doing for 1.3.

I'll make the entry.

Quoted 13 lines

Quoted 8 lines

So the question is has there been any thought about automating the choice of boot loader and the parameters that are needed or optional? In the case of meta-cedartrail, the cedartrail.conf assumes syslinux is the boot loader. When I could use a USB Flash key, creating a boot device was a trivial dd statement. Because I have to use a hard drive now, I have to do a number of manual steps. Or is there a way to create a boot-able hard drive with syslinux so the cedartrail.conf parameters are all that is needed to adjust?

This is all good feedback to consider as we work through making more universally bootable images. This is becoming a hot topic as people are using Yocto in more and more situations and as things like EFI become more commonplace.

Quoted 4 lines

There is no reason you can't just dd (have a look at scripts/contrib/ddimage) the image to a hard disk instead of a usb stick. You may need a USB to SATA adapter for your host (this is what I use). If you have a USB port, you could just use the install option.

Quoted 8 lines

This script does not eliminate the boot error I get with syslinux on USB flash keys. I noticed the script is not in edison but is in denzil, so I got it there and tried to run it against an image created with edison. I still get the same boot error I get with dd, which is understandable since that's what the script uses. Not sure if this is a size issue because my image is over a 1GB. I'm guessing this this will still fail on a hard drive with the dd'ing of the .hddimg, but I'll test it anyway.

Quoted 5 lines

Sorry, ddimage wasn't meant to fix the issue, just as a slightly more convenient/safe wrapper around dd.

I'm not familiar with the error you are seeing with the live image. Can you point me to the thread or the bug?

Well this boot error issue seems to be USB Key related because I just did the ddimage script on a edison core-image-sato image using the .hddimg file and it worked correctly on a hard drive. This was a 1.2GB image. Now I'll have to add in the parameters that give you more free disk space now that I'm testing with a real hard drive.

The readme in most of the x86 BSP directory in meta-intel talk about if you get boot errors to:

Quoted 5 lines

dd if=/dev/zero of=/dev/sdf bs=1M count=512

I have not found this to work. Maybe it's a count size issue. I always use 512, but maybe it should be 4096 for a 4GB USB key.

What is the boot error?

Next test is to see how to override the syslinux and kernel boot console statements in cedartrail.conf by placing statements in local.conf.

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Jim A

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 12 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

Quoted 6 lines

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Thanks
-Kishore.

Quoted 20 lines

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Jim A

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 12 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

Quoted 6 lines

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Thanks
-Kishore.

Quoted 20 lines

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

If this is considered a bug I can put it on bugzilla.

Jim A

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 26 lines · Kishore K

Quoted 12 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

Quoted 6 lines

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Quoted 3 lines

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Jim A

Quoted 12 lines

Quoted 12 lines

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

Quoted 8 lines

Quoted 8 lines

If this is considered a bug I can put it on bugzilla.

Jim A

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

-----Original Message-----
From: Hart, Darren
Sent: Thursday, May 31, 2012 12:43 PM
To: jfabernathy
Cc: Bodke, Kishore K; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 27 lines · jfabernathy

Quoted 26 lines · Kishore K

Quoted 12 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

Quoted 6 lines

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Quoted 9 lines

Quoted 3 lines

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Ah yes, this rebuild is a bit frustrating. I believe it is the task_core* tasks you need to rebuild. bitbake -u depexp -g core-image-base (whatever your image is) will allow you to view which task_ tasks it is building, try cleansstate'ing those and rebuilding the image.

--
Darren

Quoted 22 lines

Jim A

Quoted 12 lines

Quoted 12 lines

However, when the image booted, I had no serial console on ttyS0. I checked /etc/inittab and noticed that the following line existed:

S:2345:respawn:/sbin/getty 115200 ttyS3

I changed the ttyS3 to ttyS0 and then I have a serial console on the next reboot. So it appears the override in the .conf file is not working. Also I only have the console from getty, and not the kernel logging console.

Anyone have a solution??

Quoted 8 lines

Quoted 8 lines

If this is considered a bug I can put it on bugzilla.

Jim A

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Quoted 47 lines

-----Original Message-----
From: Hart, Darren
Sent: Thursday, May 31, 2012 12:43 PM
To: jfabernathy
Cc: Bodke, Kishore K; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 27 lines · jfabernathy

Quoted 26 lines · Kishore K

Quoted 12 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

Quoted 6 lines

The cedartrail.conf in the machine directory has the following statements:

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Quoted 9 lines

Quoted 3 lines

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Quoted 5 lines

Ah yes, this rebuild is a bit frustrating. I believe it is the task_core* tasks you need to rebuild. bitbake -u depexp -g core-image-base (whatever your image is) will allow you to view which task_ tasks it is building, try cleansstate'ing those and rebuilding the image.

I had to remove the above 3 lines from cedartrail.conf and SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-base.inc rebuild the image.
It is disabled now.

-----Original Message-----
From: Hart, Darren
Sent: Friday, June 01, 2012 11:12 AM
To: Bodke, Kishore K
Cc: jfabernathy; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 19 lines · Kishore K

Quoted 19 lines

-----Original Message-----
From: Hart, Darren
Sent: Thursday, May 31, 2012 12:43 PM
To: jfabernathy
Cc: Bodke, Kishore K; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 9 lines · jfabernathy

Quoted 8 lines · Kishore K

Quoted 8 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following

statements:

Quoted 29 lines

Quoted 28 lines

Quoted 13 lines

Quoted 13 lines

Quoted 5 lines

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Quoted 9 lines

Quoted 3 lines

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Ah yes, this rebuild is a bit frustrating. I believe it is the task_core* tasks you need to rebuild. bitbake -u depexp -g core-image-base (whatever your image is) will allow you to view which task_ tasks it is building, try cleansstate'ing those and rebuilding the image.

Quoted 2 lines

I had to remove the above 3 lines from cedartrail.conf and SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-

base.inc

Quoted 2 lines

rebuild the image.
It is disabled now.

Did you try with SERIAL_CONSOLE="" in cedartrail.conf ?

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Quoted 66 lines

-----Original Message-----
From: Hart, Darren
Sent: Friday, June 01, 2012 11:12 AM
To: Bodke, Kishore K
Cc: jfabernathy; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 19 lines · Kishore K

Quoted 19 lines

-----Original Message-----
From: Hart, Darren
Sent: Thursday, May 31, 2012 12:43 PM
To: jfabernathy
Cc: Bodke, Kishore K; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 9 lines · jfabernathy

Quoted 8 lines · Kishore K

Quoted 8 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following

statements:

Quoted 31 lines

Quoted 23 lines

Quoted 13 lines

Quoted 13 lines

Quoted 5 lines

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Quoted 9 lines

Quoted 3 lines

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Quoted 5 lines

Ah yes, this rebuild is a bit frustrating. I believe it is the task_core* tasks you need to rebuild. bitbake -u depexp -g core-image-base (whatever your image is) will allow you to view which task_ tasks it is building, try cleansstate'ing those and rebuilding the image.

I had to remove the above 3 lines from cedartrail.conf and SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-

Quoted 5 lines

base.inc

Quoted 2 lines

rebuild the image.
It is disabled now.

Did you try with SERIAL_CONSOLE="" in cedartrail.conf ?

Yes. I tried this. It is disabled.

I again added back in the grub.cfg, serial console hangs.

-----Original Message-----
From: Hart, Darren
Sent: Friday, June 01, 2012 2:17 PM
To: Bodke, Kishore K
Cc: jfabernathy; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 70 lines · Kishore K

Quoted 70 lines

-----Original Message-----
From: Hart, Darren
Sent: Friday, June 01, 2012 11:12 AM
To: Bodke, Kishore K
Cc: jfabernathy; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 19 lines · Kishore K

Quoted 19 lines

-----Original Message-----
From: Hart, Darren
Sent: Thursday, May 31, 2012 12:43 PM
To: jfabernathy
Cc: Bodke, Kishore K; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 9 lines · jfabernathy

Quoted 8 lines · Kishore K

Quoted 8 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following

statements:

Quoted 23 lines

Quoted 23 lines

Quoted 22 lines

Quoted 7 lines

Quoted 5 lines

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

Quoted 9 lines

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Quoted 8 lines

Quoted 5 lines

Ah yes, this rebuild is a bit frustrating. I believe it is the task_core* tasks you need to rebuild. bitbake -u depexp -g core-image-base (whatever your image is) will allow you to view which task_ tasks it is building, try cleansstate'ing those and rebuilding the image.

I had to remove the above 3 lines from cedartrail.conf and SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-

base.inc

Quoted 2 lines

rebuild the image.
It is disabled now.

Quoted 4 lines

Quoted 1 line

Did you try with SERIAL_CONSOLE="" in cedartrail.conf ?

Yes. I tried this. It is disabled.

Meaning you do not have to modify ia32-base.inc?

Quoted 2 lines

I again added back in the grub.cfg, serial console hangs.

Added what back in grub.cfg?

I thought you were disabling the serial port...

Where does the serial console hang? In grub? During boot? At the login prompt?

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Quoted 80 lines

-----Original Message-----
From: Hart, Darren
Sent: Friday, June 01, 2012 2:17 PM
To: Bodke, Kishore K
Cc: jfabernathy; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 70 lines · Kishore K

Quoted 70 lines

-----Original Message-----
From: Hart, Darren
Sent: Friday, June 01, 2012 11:12 AM
To: Bodke, Kishore K
Cc: jfabernathy; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 19 lines · Kishore K

Quoted 19 lines

-----Original Message-----
From: Hart, Darren
Sent: Thursday, May 31, 2012 12:43 PM
To: jfabernathy
Cc: Bodke, Kishore K; [email protected]
Subject: Re: [yocto] meta-cedartrail - serial console

Quoted 9 lines · jfabernathy

Quoted 8 lines · Kishore K

Quoted 8 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of jfabernathy
Sent: Thursday, May 31, 2012 9:12 AM
To: [email protected]
Subject: [yocto] meta-cedartrail - serial console

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Using a DN2800MT (Marshalltown) Intel board, I'm testing the meta-cedartrail using edison branch and noticed an issues with the serial console.

The cedartrail.conf in the machine directory has the following

statements:

Quoted 23 lines

Quoted 23 lines

Quoted 22 lines

Quoted 7 lines

Quoted 5 lines

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

I just saw that Edison branch has ttyS3 enabled.

Quoted 9 lines

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Thanks
-Kishore.

So how do you get changes in the cedartrail.conf file to take affect?? I edited the file and did the bitbake again, but nothing changed. I'm guessing I need a bitbake -c cleansstate "somthing" But I don't know what to put there to make rebuild with ttyS0.

Quoted 8 lines

Quoted 5 lines

Ah yes, this rebuild is a bit frustrating. I believe it is the task_core* tasks you need to rebuild. bitbake -u depexp -g core-image-base (whatever your image is) will allow you to view which task_ tasks it is building, try cleansstate'ing those and rebuilding the image.

I had to remove the above 3 lines from cedartrail.conf and SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-

base.inc

Quoted 2 lines

rebuild the image.
It is disabled now.

Quoted 6 lines

Quoted 4 lines

Quoted 1 line

Did you try with SERIAL_CONSOLE="" in cedartrail.conf ?

Yes. I tried this. It is disabled.

Meaning you do not have to modify ia32-base.inc?

I removed the SERIAL_CONSOLE ?= "115200 ttyS0" from ia32-base.inc too.

Quoted 4 lines

Quoted 2 lines

I again added back in the grub.cfg, serial console hangs.

Added what back in grub.cfg?

I added back console=ttyS0,115200 console=tty0 to the grub.cfg file and rebooted to see if I can get the serial console back, but after below boot messages the serial console hangs.

Freeing unused kernel memory: 496k freed udev[77]: starting version 164
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds EXT3-fs (loop0): using internal journal
EXT3-fs (loop0): recovery complete
EXT3-fs (loop0): mounted filesystem with ordered data mode udev[487]: starting version 164
NET: Registered protocol family 10 ADDRCONF(NETDEV_UP): eth0: link is not ready
ip_tables: (C) 2000-2006 Netfilter Core Team nf_conntrack version 0.5.0 (16384 buckets, 65536 max)

Quoted 1 line

Quoted 1 line

I thought you were disabling the serial port...

I wanted to enable and disable the serial console through grub.cfg file.