udev/modutils issues with the system bringup

udev/modutils issues with the system bringup

[Holger Freyther]

Hi all,

I have experienced two issues that should exist for others as well.


1.) udevd not starting on second boot. The /etc/init.d/udev script attempts
to detect the first/second boot by checking for /etc/dev.tar and then is
executing the following:

#!/bin/sh -e
...
if [ -e /etc/dev.tar ]; then 
        (cd /; tar xf /etc/dev.tar 2>&1 | grep -v 'time stamp')
        not_first_boot=1
fi

and somehow the "grep -v 'time stamp'" makes this whole expression
evaluate to 1 which makes the script exit at this part. So I am not sure
when/where/how this problem got introduced, if this is a change in the
return value of grep.. (I am just lazy here right now)


2.) Chicken egg problem with firmware
I have some kernel modules that require firmware but they should be
loaded on start. So right now the modutils.sh script is executed before
udev which means that firmware loading will be loaded before
  a) sysfs is mounted...
  b) udev will handle it..

my local workaround is to move the modutils.sh script after both sysfs
and udev.

holger

Re: udev/modutils issues with the system bringup

[Holger Freyther]

Holger Freyther <holger@...> writes:

> #!/bin/sh -e
> ...
> if [ -e /etc/dev.tar ]; then 
>         (cd /; tar xf /etc/dev.tar 2>&1 | grep -v 'time stamp')
>         not_first_boot=1
> fi

Okay, it is efce51ec11cc2a908833e80b65d2f5db81bb2fec which only works
if the time is broken... I assume one wants to add an || true or such to the
command.

Re: udev/modutils issues with the system bringup

[Saul Wold]

On 06/06/2011 02:21 AM, Holger Freyther wrote:
> Holger Freyther<holger@...>  writes:
>
>> #!/bin/sh -e
>> ...
>> if [ -e /etc/dev.tar ]; then
>>          (cd /; tar xf /etc/dev.tar 2>&1 | grep -v 'time stamp')
>>          not_first_boot=1
>> fi
>
> Okay, it is efce51ec11cc2a908833e80b65d2f5db81bb2fec which only works
> if the time is broken... I assume one wants to add an || true or such to the
> command.
>
Holger,

I would take a patch for that.

Sau!

> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>

Re: udev/modutils issues with the system bringup

[Saul Wold]

On 06/17/2011 12:25 PM, Holger Hans Peter Freyther wrote:
> On 06/06/2011 05:18 PM, Saul Wold wrote:
>
>>> Okay, it is efce51ec11cc2a908833e80b65d2f5db81bb2fec which only works
>>> if the time is broken... I assume one wants to add an || true or such to the
>>> command.
>>>
>> Holger,
>>
>> I would take a patch for that.
>
> Hi,
>
> not sure what is the best way to send patches (if they need a SoB, if they
> should go through oe-core...). The first adds a '|| true' to the udev start
> script so udevd is started on second boot, the second move modutils after
> udev.. if there is a module needed to make udev work... then the first boot
> will fail as modules are only configured by S9XConfigure..
>
Yes, these should really go against oe-core with proper SoBs.  Please 
re-submit there.

Thanks
	Sau!

> holger
>
> PS: I was away from my build machine so the patches might be outdated.