headers
belatronix | 23 Mar 2012 10:23
Picon
Favicon

Booting rootfs over NFS stops after linking Phy

Hello,

i build the ELDK 5.1.2 from the sources and try to boot the core basic image over nfs with the build 3.1.4
Kernel on an powerpc architecture (TB5200L). Another, self configured Kernel (v3.1.5) with NFS support
build in has the same behaviour.

Getting the Kernel uImage via TFTP works and booting stops not with a panic or an reboot. 
My Problem is that after booting the kernel the system stops booting after linking the ethernet PHY
[  134.418108] PHY: f0003000:00 - Link is Up - 100/Fullwhere it try to mount the rootfs.

Mounting the NFS share over another machine works without problems.

How can i fix this? Any hints?

Regards

Axel

---
Nutzen Sie freenet Mail optimal angepasst für Ihr iPhone, Android oder Nokia Handy auch von unterwegs.
Alle Infos und Download unter http://mail.freenet.de/mobile-email/index.html
Permalink | Reply |
headers
Wolfgang Denk | 23 Mar 2012 14:07
Picon
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

Dear Axel,

In message
<59713f769a2fa6fa7a7fbd73318805197d716553@...>
you wrote:
> 
> i build the ELDK 5.1.2 from the sources and try to boot the core
> basic image over nfs with the build 3.1.4 Kernel on an powerpc
> architecture (TB5200L). Another, self configured Kernel (v3.1.5) with
> NFS support build in has the same behaviour.

Have you tried these kernel images with another root file system?

This would be helpful to figure out if your kernel configuration and
your device tree blob are OK.

> Getting the Kernel uImage via TFTP works and booting stops not with a
> panic or an reboot. My Problem is that after booting the kernel the
> system stops booting after linking the ethernet PHY [ 134.418108]
> PHY: f0003000:00 - Link is Up - 100/Fullwhere it try to mount the
> rootfs.

This looks more like a kernel problem than a root file system issue to
me.

Run a network sniffer (wireshark) and analyze the logs wher eit really
stops working.

Best regards,
(Continue reading)

Permalink | Reply |
headers
Axel Beierlein | 23 Mar 2012 14:17
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

Hello Wolfgang,

Am 23.03.2012 14:07, schrieb Wolfgang Denk:
> Dear Axel,
>
> In
message<59713f769a2fa6fa7a7fbd73318805197d716553@...>
 you wrote:
>>
>> i build the ELDK 5.1.2 from the sources and try to boot the core
>> basic image over nfs with the build 3.1.4 Kernel on an powerpc
>> architecture (TB5200L). Another, self configured Kernel (v3.1.5) with
>> NFS support build in has the same behaviour.
>
> Have you tried these kernel images with another root file system?
>
Yes, i have checked it with different rootfs'. But they all from the 
eldk-5.1.2 build. I will have a check with a complete different (working 
old) one later.

> This would be helpful to figure out if your kernel configuration and
> your device tree blob are OK.
>
The device tree blob is that one wich was build with 'make tqm5200.dtb'

>> Getting the Kernel uImage via TFTP works and booting stops not with a
>> panic or an reboot. My Problem is that after booting the kernel the
>> system stops booting after linking the ethernet PHY [ 134.418108]
>> PHY: f0003000:00 - Link is Up - 100/Fullwhere it try to mount the
>> rootfs.
(Continue reading)

Permalink | Reply |
headers
Wolfgang Denk | 23 Mar 2012 14:44
Picon
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

Dear Axel,

In message <4F6C77F1.8050701@...> you wrote:
> 
> >> i build the ELDK 5.1.2 from the sources and try to boot the core
> >> basic image over nfs with the build 3.1.4 Kernel on an powerpc
> >> architecture (TB5200L). Another, self configured Kernel (v3.1.5) with
> >> NFS support build in has the same behaviour.
...
> The device tree blob is that one wich was build with 'make tqm5200.dtb'

TQM5200 != TB5200L

This is most likely the cause of your problems.

Best regards,

Wolfgang Denk

--

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
Things that try to look like things often do look  more  like  things
than things. Well-known fact.       - Terry Pratchett, _Wyrd Sisters_
Permalink | Reply |
headers
Axel Beierlein | 23 Mar 2012 15:03
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

Hello Wolfgang,

Am 23.03.2012 14:44, schrieb Wolfgang Denk:
> Dear Axel,
>
> In message<4F6C77F1.8050701@...>  you wrote:
>>
>>>> i build the ELDK 5.1.2 from the sources and try to boot the core
>>>> basic image over nfs with the build 3.1.4 Kernel on an powerpc
>>>> architecture (TB5200L). Another, self configured Kernel (v3.1.5) with
>>>> NFS support build in has the same behaviour.
> ...
>> The device tree blob is that one wich was build with 'make tqm5200.dtb'
>
> TQM5200 != TB5200L
>
Ok. Booting a TB5200 with an 2.6.x Kernel and this Blob was no problem. 
Also the rootfs mount via NFS. (I try this a few Month ago - not with 
this actual setup -)
But i will have a look.
Do you have a working one by any chance ;-) ?

Let me guess. This was the reason why the SM501 on the Board gets not a 
correct init, too.

> This is most likely the cause of your problems.
>
> Best regards,
>
> Wolfgang Denk
(Continue reading)

Permalink | Reply |
headers
Wolfgang Denk | 23 Mar 2012 17:14
Picon
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

Dear Axel,

In message <4F6C82C0.3080200@...> you wrote:
> 
> > TQM5200 != TB5200L
> >
> Ok. Booting a TB5200 with an 2.6.x Kernel and this Blob was no problem. 

Hm... Can you dig out and try this configurationm, then?

> Do you have a working one by any chance ;-) ?

Sorry, we have not had access to a TB5200 yet.

> Let me guess. This was the reason why the SM501 on the Board gets not a 
> correct init, too.

Probably...

Best regards,

Wolfgang Denk

--

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
We, the unwilling, led by the unknowing, are doing the impossible for
the ungrateful. We have done so much, for so long, with so little, we
are now qualified to do anything with nothing.
(Continue reading)

Permalink | Reply |
headers
belatronix | 30 Mar 2012 00:39
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

I try an old working SELF from the eldk311 to test if the nfs connection was the prob. But this
FS was mounted. With this new 3.1.5 Kernel and the not 100% fitting tq5200.dtb.

Could it be that the Yocto FS are not bootable over nfs? Do i have a look for special things like permissions
and other things?

Regards

Axel 

> -----Ursprüngliche Nachricht-----
> Von: Wolfgang Denk 
> Gesendet: Fri. 23.03.2012 17:14
> An: Axel Beierlein 
> Kopie: eldk@...
> Betreff: Re: [ELDK] Booting rootfs over NFS stops after linking Phy
>
> Dear Axel,
>
> In message  you wrote:
> >
> > > TQM5200 != TB5200L
> > >
> > Ok. Booting a TB5200 with an 2.6.x Kernel and this Blob was no
> problem.
>
> Hm... Can you dig out and try this configurationm, then?
>
> > Do you have a working one by any chance ;-) ?
>
(Continue reading)

Permalink | Reply |
headers
Wolfgang Denk | 30 Mar 2012 09:19
Picon
Picon
Favicon

Re: Booting rootfs over NFS stops after linking Phy

Dear Axel,

please do not top post / full quote (see
http://www.netmeister.org/news/learn2quote.html).

In message
<b562448e5fb8a0d8bdae3ff83e0435d32128285a@...>
you wrote:
> 
> I try an old working SELF from the eldk311 to test if the nfs
> connection was the prob. But this FS was mounted. With this new 3.1.5
> Kernel and the not 100% fitting tq5200.dtb.

OK, so it appears the kernel is working.  Now focus is on the root
file system and the NFS server setup.

> Could it be that the Yocto FS are not bootable over nfs? Do i have a
> look for special things like permissions and other things?

We use these images over NFS all the time - and for the kernel it does
not make much of a difference what the underlying file system type is;
NFS or ext* or xfs or whatever (assuming some minimal requirements are
met).

I don't know much about your setup, so I can only speculate... Either
something went wrong when installing the root file system, or there
are problems with your nFS server configuration.

- Did you try a fresh installation of the root file system?
(Continue reading)

Permalink | Reply |

Gmane