[ptxdist] ptxdist on a x86 target, grub problem ?

[ptxdist] ptxdist on a x86 target, grub problem ?

[Stella GZ]

[-- Attachment #1.1: Type: text/plain, Size: 1332 bytes --]

Hello,

I'm trying to use ptxdist for a x86 target, using these versions of
software for ptxdist, Toolchain and BSP:
ptxdist-2012.12.0

OSELAS.Toolchain-2012.12.0/

OSELAS.BSP-Pengutronix-Generic-2012.12


I've selected this configuration:

     configs/i586-qemu/platformconfig


After building the image I can check that all works as expected using Qemu.


Now I would like to use this image to boot on the target device. The target
boots from a CF card.


I select Grub as the bootloader, and also make sure to enable the following:


Enable decompression in stage 2

Serial terminal support

File System support -> ext2

Device of root fs -> /dev/hda1


I copy the resulting hd.img image to a CF (using dd) and try to boot on the
target:


GRUB seems to start ok

I get the GRUB menu with standalone boot / network boot options. I guess
this means that GRUB can

find the stage2 files

In fact from the GRUB shell I can inspect the contents of (hd0,0) and all
the files are there

However when I try to boot (standalone option) I get this:


root (hd0,0)

Filesystem type is ext2fs, partition type 0x83

kernel /boot/bzImage root=/dev/hda1 console=ttyS0,115200

[Linux-bzImage, setup=0x3800, size=0xe9db0]


Ant then nothing more.


Can someone help? Any hints of what may be wrong? Any pointers are welcome.


Regards,

Stella

[-- Attachment #1.2: Type: text/html, Size: 8536 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] ptxdist on a x86 target, grub problem ?

[Juergen Borleis]

Hi Stella,

On Monday 12 May 2014 14:12:08 Stella GZ wrote:
> [...]
> GRUB seems to start ok
>
> I get the GRUB menu with standalone boot / network boot options. I guess
> this means that GRUB can
>
> find the stage2 files
>
> In fact from the GRUB shell I can inspect the contents of (hd0,0) and all
> the files are there
>
> However when I try to boot (standalone option) I get this:
>
> root (hd0,0)
> Filesystem type is ext2fs, partition type 0x83
> kernel /boot/bzImage root=/dev/hda1 console=ttyS0,115200
> [Linux-bzImage, setup=0x3800, size=0xe9db0]

Does GRUB also use the serial console for its output?

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] ptxdist on a x86 target, grub problem ?

[Juergen Borleis]

Hi Stella,

please keep the mailing list on CC.

On Monday 12 May 2014 14:26:50 Stella GZ wrote:
> On 12 May 2014 14:20, Juergen Borleis <jbe@pengutronix.de> wrote:
> > On Monday 12 May 2014 14:12:08 Stella GZ wrote:
> > > [...]
> > > GRUB seems to start ok
> > >
> > > I get the GRUB menu with standalone boot / network boot options. I
> > > guess this means that GRUB can
> > >
> > > find the stage2 files
> > >
> > > In fact from the GRUB shell I can inspect the contents of (hd0,0) and
> > > all the files are there
> > >
> > > However when I try to boot (standalone option) I get this:
> > >
> > > root (hd0,0)
> > > Filesystem type is ext2fs, partition type 0x83
> > > kernel /boot/bzImage root=/dev/hda1 console=ttyS0,115200
> > > [Linux-bzImage, setup=0x3800, size=0xe9db0]
> >
> > Does GRUB also use the serial console for its output?
>
> GRUB output is going to VGA
>
> I also tried booting the kernel without the console= parameter but got the
> same results..

If you use the "console=ttyS0,115200" do you see some output on your target's 
serial interface?
Is VGA support enabled in your kernel config?

We should continue on the oselas.community mailing list instead, because your 
issue is not PTXdist related (or at least it seems so).

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] ptxdist on a x86 target, grub problem ?

[Stella GZ]

[-- Attachment #1.1: Type: text/plain, Size: 1888 bytes --]

Hello Jüergen,



On 12 May 2014 14:34, Juergen Borleis <jbe@pengutronix.de> wrote:

> Hi Stella,
>
> please keep the mailing list on CC.
>
> On Monday 12 May 2014 14:26:50 Stella GZ wrote:
> > On 12 May 2014 14:20, Juergen Borleis <jbe@pengutronix.de> wrote:
> > > On Monday 12 May 2014 14:12:08 Stella GZ wrote:
> > > > [...]
> > > > GRUB seems to start ok
> > > >
> > > > I get the GRUB menu with standalone boot / network boot options. I
> > > > guess this means that GRUB can
> > > >
> > > > find the stage2 files
> > > >
> > > > In fact from the GRUB shell I can inspect the contents of (hd0,0) and
> > > > all the files are there
> > > >
> > > > However when I try to boot (standalone option) I get this:
> > > >
> > > > root (hd0,0)
> > > > Filesystem type is ext2fs, partition type 0x83
> > > > kernel /boot/bzImage root=/dev/hda1 console=ttyS0,115200
> > > > [Linux-bzImage, setup=0x3800, size=0xe9db0]
> > >
> > > Does GRUB also use the serial console for its output?
> >
> > GRUB output is going to VGA
> >
> > I also tried booting the kernel without the console= parameter but got
> the
> > same results..
>
> If you use the "console=ttyS0,115200" do you see some output on your
> target's
> serial interface?
> Is VGA support enabled in your kernel config?
>
> We should continue on the oselas.community mailing list instead, because
> your
> issue is not PTXdist related (or at least it seems so).
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K.                              | Juergen Borleis
>   |
> Linux Solutions for Science and Industry      | http://www.pengutronix.de/ |
>

If I use "console = ttyS0,115200" I don't see any output on my target's
serial interface (I've used minicom to check)

VGA support is enabled in my kernel config.

What do you suggest to do?

Thank you.

Regards,

Stella

[-- Attachment #1.2: Type: text/html, Size: 3036 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] ptxdist on a x86 target, grub problem ?

[Stella GZ]

[-- Attachment #1.1: Type: text/plain, Size: 2575 bytes --]

Hello,

I have tried to specify root=UUID=<uuid_value> but that didn't work either.

VGA support -- I think it is enabled but not 100% sure. Which settings
should I check?

Can I find a step-by-step guide somewhere? As I said I am starting from the
default
ptxdist configuration for the "Generic" BSP (got it working in QEmu), then
enabled grub
and the grub options I stated in my mail, but I cannot get the target to
boot.

I may be missing something obvious but don't know where to look next.

Regards,
Stella


On 12 May 2014 16:55, Stella GZ <gzestela@gmail.com> wrote:

> Hello Jüergen,
>
>
>
> On 12 May 2014 14:34, Juergen Borleis <jbe@pengutronix.de> wrote:
>
>> Hi Stella,
>>
>> please keep the mailing list on CC.
>>
>> On Monday 12 May 2014 14:26:50 Stella GZ wrote:
>> > On 12 May 2014 14:20, Juergen Borleis <jbe@pengutronix.de> wrote:
>> > > On Monday 12 May 2014 14:12:08 Stella GZ wrote:
>> > > > [...]
>> > > > GRUB seems to start ok
>> > > >
>> > > > I get the GRUB menu with standalone boot / network boot options. I
>> > > > guess this means that GRUB can
>> > > >
>> > > > find the stage2 files
>> > > >
>> > > > In fact from the GRUB shell I can inspect the contents of (hd0,0)
>> and
>> > > > all the files are there
>> > > >
>> > > > However when I try to boot (standalone option) I get this:
>> > > >
>> > > > root (hd0,0)
>> > > > Filesystem type is ext2fs, partition type 0x83
>> > > > kernel /boot/bzImage root=/dev/hda1 console=ttyS0,115200
>> > > > [Linux-bzImage, setup=0x3800, size=0xe9db0]
>> > >
>> > > Does GRUB also use the serial console for its output?
>> >
>> > GRUB output is going to VGA
>> >
>> > I also tried booting the kernel without the console= parameter but got
>> the
>> > same results..
>>
>> If you use the "console=ttyS0,115200" do you see some output on your
>> target's
>> serial interface?
>> Is VGA support enabled in your kernel config?
>>
>> We should continue on the oselas.community mailing list instead, because
>> your
>> issue is not PTXdist related (or at least it seems so).
>>
>> Regards,
>> Juergen
>>
>> --
>> Pengutronix e.K.                              | Juergen Borleis
>>   |
>> Linux Solutions for Science and Industry      |
>> http://www.pengutronix.de/  |
>>
>
> If I use "console = ttyS0,115200" I don't see any output on my target's
> serial interface (I've used minicom to check)
>
> VGA support is enabled in my kernel config.
>
> What do you suggest to do?
>
> Thank you.
>
> Regards,
>
> Stella
>

[-- Attachment #1.2: Type: text/html, Size: 4096 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [oselas] ptxdist on a x86 target, grub problem ?

[Guillermo Rodriguez Garcia]

Hello Stella,

Don't know if this is related to your case, however:

There seems to be a problem when building images for an i586 target using the
"Generic x86/ARM BSP" for ptxdist. The generated menu.lst file will always pass
root=/dev/sda1 to the kernel, regardless of your ROOTFS_DEVICE configuration.

I had a quick look to try to find why this happens. Seems that there
is a default
menu.lst template in ${PTXDIST}/generic/boot/grub/menu.lst which is OK (root
device gets replaced dynamically according to your configuration),
however if you
use the "Generic x86/ARM BSP", the following file will take precedence over the
generic one:

${GENERIC_BSP_DIR}/projectroot/boot/grub/menu.lst.i586

In this file, the root parameter is hardcoded to /dev/sda1. So if your
root device
is not /dev/sda1, you will need to edit this manually.

Ptxdist maintainers: Is there a reason for the separate menu.lst.i586
file? Except
for the issue described above it seems to be almost identical to the
generic menu.lst
file in ptxdist.

Best regards,

Guillermo Rodriguez


2014-05-12 17:57 GMT+02:00 Stella GZ <gzestela@gmail.com>:
> Hello,
>
> I have tried to specify root=UUID=<uuid_value> but that didn't work either.
>
> VGA support -- I think it is enabled but not 100% sure. Which settings
> should I check?
>
> Can I find a step-by-step guide somewhere? As I said I am starting from the
> default
> ptxdist configuration for the "Generic" BSP (got it working in QEmu), then
> enabled grub
> and the grub options I stated in my mail, but I cannot get the target to
> boot.
>
> I may be missing something obvious but don't know where to look next.
>
> Regards,
> Stella
>
>
> On 12 May 2014 16:55, Stella GZ <gzestela@gmail.com> wrote:
>>
>> Hello Jüergen,
>>
>>
>>
>> On 12 May 2014 14:34, Juergen Borleis <jbe@pengutronix.de> wrote:
>>>
>>> Hi Stella,
>>>
>>> please keep the mailing list on CC.
>>>
>>> On Monday 12 May 2014 14:26:50 Stella GZ wrote:
>>> > On 12 May 2014 14:20, Juergen Borleis <jbe@pengutronix.de> wrote:
>>> > > On Monday 12 May 2014 14:12:08 Stella GZ wrote:
>>> > > > [...]
>>> > > > GRUB seems to start ok
>>> > > >
>>> > > > I get the GRUB menu with standalone boot / network boot options. I
>>> > > > guess this means that GRUB can
>>> > > >
>>> > > > find the stage2 files
>>> > > >
>>> > > > In fact from the GRUB shell I can inspect the contents of (hd0,0)
>>> > > > and
>>> > > > all the files are there
>>> > > >
>>> > > > However when I try to boot (standalone option) I get this:
>>> > > >
>>> > > > root (hd0,0)
>>> > > > Filesystem type is ext2fs, partition type 0x83
>>> > > > kernel /boot/bzImage root=/dev/hda1 console=ttyS0,115200
>>> > > > [Linux-bzImage, setup=0x3800, size=0xe9db0]
>>> > >
>>> > > Does GRUB also use the serial console for its output?
>>> >
>>> > GRUB output is going to VGA
>>> >
>>> > I also tried booting the kernel without the console= parameter but got
>>> > the
>>> > same results..
>>>
>>> If you use the "console=ttyS0,115200" do you see some output on your
>>> target's
>>> serial interface?
>>> Is VGA support enabled in your kernel config?
>>>
>>> We should continue on the oselas.community mailing list instead, because
>>> your
>>> issue is not PTXdist related (or at least it seems so).
>>>
>>> Regards,
>>> Juergen
>>>
>>> --
>>> Pengutronix e.K.                              | Juergen Borleis
>>> |
>>> Linux Solutions for Science and Industry      |
>>> http://www.pengutronix.de/  |
>>
>>
>> If I use "console = ttyS0,115200" I don't see any output on my target's
>> serial interface (I've used minicom to check)
>>
>> VGA support is enabled in my kernel config.
>>
>> What do you suggest to do?
>>
>> Thank you.
>>
>> Regards,
>>
>> Stella
>
>



-- 
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [oselas] ptxdist on a x86 target, grub problem ?

[Juergen Borleis]

Hi Guillermo,

On Monday 12 May 2014 20:14:08 Guillermo Rodriguez Garcia wrote:
> [...]
> Ptxdist maintainers: Is there a reason for the separate menu.lst.i586
> file? Except for the issue described above it seems to be almost identical to
> the generic menu.lst file in ptxdist.

Sometimes these kind of files where required because at the time of their 
addition PTXdist didn't come with one. And later versions of PTXdist support 
these files and we forget to remove the local file from the BSP.

If you think this file is needless now (and you have tested it), you are 
welcome to send a patch to remove it from the repo.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [oselas] ptxdist on a x86 target, grub problem ?

[Guillermo Rodriguez Garcia]

Hi Juergen,

2014-05-13 9:49 GMT+02:00 Juergen Borleis <jbe@pengutronix.de>:
> Hi Guillermo,
>
> On Monday 12 May 2014 20:14:08 Guillermo Rodriguez Garcia wrote:
>> [...]
>> Ptxdist maintainers: Is there a reason for the separate menu.lst.i586
>> file? Except for the issue described above it seems to be almost identical to
>> the generic menu.lst file in ptxdist.
>
> Sometimes these kind of files where required because at the time of their
> addition PTXdist didn't come with one. And later versions of PTXdist support
> these files and we forget to remove the local file from the BSP.
>
> If you think this file is needless now (and you have tested it), you are
> welcome to send a patch to remove it from the repo.

I would say it should be either removed or fixed. What do you prefer?

Guillermo Rodriguez

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [oselas] ptxdist on a x86 target, grub problem ?

[Guillermo Rodriguez Garcia]

2014-05-13 11:41 GMT+02:00 Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com>:
> Hi Juergen,
>
> 2014-05-13 9:49 GMT+02:00 Juergen Borleis <jbe@pengutronix.de>:
>> Hi Guillermo,
>>
>> On Monday 12 May 2014 20:14:08 Guillermo Rodriguez Garcia wrote:
>>> [...]
>>> Ptxdist maintainers: Is there a reason for the separate menu.lst.i586
>>> file? Except for the issue described above it seems to be almost identical to
>>> the generic menu.lst file in ptxdist.
>>
>> Sometimes these kind of files where required because at the time of their
>> addition PTXdist didn't come with one. And later versions of PTXdist support
>> these files and we forget to remove the local file from the BSP.
>>
>> If you think this file is needless now (and you have tested it), you are
>> welcome to send a patch to remove it from the repo.
>
> I would say it should be either removed or fixed. What do you prefer?

After having a second look: I think the right thing to do would be to remove
this file, however this doesn't work as expected. By default, grub.in defines
a hardcoded path for the GRUB_MENU_LIST option:
${PTXDIST_WORKSPACE}/projectroot/boot/grub/menu.lst

So if the file from projectroot/... is simply removed, the menu.lst from
generic/boot/grub/ is NOT used.

I think this was not the intention (looks like the generic file should be used
if no project specific file is available) but I am not sure how this should be
fixed.

So perhaps the best way is just to patch the local menu.lst file in the
Generic BSP.

-- 
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de