[Buildroot] Issue with login

Mohd Faiz Rohani mohd.faiz.rohani at gmail.com
Tue Feb 22 01:34:29 UTC 2022


Im booting through the sd card. If I am using the same partitions and
uenv.txt configurations (with old kernel version such as 4.4.155) i have no
problem booting up. However with the new 5.15 kernel i got this message.
Could it be a setting issue (buildroot)?

I have tried using the pastebin, but it seems its only allowed text correct?

Thanks


On Tue, Feb 22, 2022, 3:32 AM Giulio Benetti <
giulio.benetti at benettiengineering.com> wrote:

> Hi Mohd,
>
> Il giorno 21 feb 2022, alle ore 15:16, Mohd Faiz Rohani <
> mohd.faiz.rohani at gmail.com> ha scritto:
>
> 
> Hi Giulio,
>
> Update: I have tried the latest kernel (5.15) with buildroot toolchain.
> result is same, RFS mounting error (refer attached)
>
>
> Please use https://pasteboard.co/ for images, but it would be definitely
> better to have a pastebin.
>
> As I see it fails to mount mmc0blk0p2. But are you trying to boot from
> sd-card or eMMC?
>
> If from sd-card make sure you have partition 2 with fdisk.
> Same goes for eMMC, you need to check the partitions.
>
> Maybe simply rootfs is on partition 1?!?
> And so you only need to pass a different rootfs argument to bootargs.
>
> What happens if instead you build Buildroot beaglebone_defconfig?
>
> Can you give a go with that and use its instructions found in
> board/beaglebone/readme.txt please?
>
> If that works at least we know the HE is alive.
>
> Thank you
> Giulio
>
>
>
> On Mon, Feb 21, 2022 at 5:46 PM Mohd Faiz Rohani <
> mohd.faiz.rohani at gmail.com> wrote:
>
>> Yes I will, even though I'm not in IRC for quite some time now. :).
>> Thanks a lot Giulio!
>>
>> On Mon, Feb 21, 2022 at 5:43 PM Giulio Benetti <
>> giulio.benetti at benettiengineering.com> wrote:
>>
>>>
>>> Il giorno 21 feb 2022, alle ore 10:33, Mohd Faiz Rohani <
>>> mohd.faiz.rohani at gmail.com> ha scritto:
>>>
>>> 
>>> Btw, is the mailing list correct platform for Buildroot Q&A? Do you have
>>> any related forum for the purpose? Thanks
>>>
>>>
>>> It’s one of its purpose, but I suggest you to also join IRC #buildroot
>>> channel.
>>>
>>> Best regards
>>> Giulio
>>>
>>>
>>> On Mon, Feb 21, 2022, 4:44 PM Giulio Benetti <
>>> giulio.benetti at benettiengineering.com> wrote:
>>>
>>>> Hi Mohd,
>>>>
>>>> On 21/02/22 06:16, Mohd Faiz Rohani wrote:
>>>> > Hi guys,
>>>> >
>>>> > Thank you for your help.I have overlooked the required setting as
>>>> > normally I will leave the setting to the default, as I assume
>>>> Buildroot
>>>> > has selected the required settings. Anyway I have managed to login
>>>> > successfully now.
>>>> >
>>>> > I have turned on BR2_PACKAGE_SYSTEMD_LOGIND and
>>>> > BR2_PACKAGE_UTIL_LINUX_LOGIN settings, while the rest does not change.
>>>>
>>>> Perfect, team working with Edgar worked :-)
>>>>
>>>> > Fyi, I have tried the newer versions of Linux Kernel (5.15) and Uboot
>>>> > (v2022.01) with the Linaro 7.5 toolchain, but got an error during the
>>>> > booting process where the RFS cannot be mounted. It may be my fault
>>>> > through the settings though, that is why I am trying the old version
>>>> and
>>>> > it worked.
>>>>
>>>> I would avoid using gcc 7.5 on such new kernel/uboot. Maybe if you try
>>>> to rebuild using an external prebuilt toolchain like the Bootlin one,
>>>> or
>>>> you build a Buildroot toolchain with latest versions, like gcc 10.x you
>>>> could obtain different results.
>>>>
>>>> > I am planning to use Buildroot for my future development and keen to
>>>> > contribute wherever I can. Still lots to learn though.
>>>>
>>>> Well!
>>>>
>>>> > Thank you again guys.
>>>>
>>>> You're welcome
>>>>
>>>> Best regards
>>>> --
>>>> Giulio Benetti
>>>> Benetti Engineering sas
>>>>
>>>> > Regards.
>>>> > Faiz
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Mon, Feb 21, 2022 at 2:33 AM Mohd Faiz Rohani
>>>> > <mohd.faiz.rohani at gmail.com <mailto:mohd.faiz.rohani at gmail.com>>
>>>> wrote:
>>>> >
>>>> >     Thanks, I'll check them out. Will update the outcome once the
>>>> >     installation is done.
>>>> >
>>>> >     Thank you.
>>>> >
>>>> >     On Mon, Feb 21, 2022, 1:56 AM Giulio Benetti
>>>> >     <giulio.benetti at benettiengineering.com
>>>> >     <mailto:giulio.benetti at benettiengineering.com>> wrote:
>>>> >
>>>> >         Hi Edgar,
>>>> >
>>>> >         please reply to all in Mailing List, I add Mohd in Cc,
>>>> >
>>>> >         On 20/02/22 17:18, Edgar Bonet wrote:
>>>> >          > Hi!
>>>> >          >
>>>> >          > In his config file, Mohd wrote:
>>>> >          >> BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_10=y
>>>> >          >> BR2_LINUX_KERNEL_VERSION="4.4.155"
>>>> >          >
>>>> >          > This may cause problems. C.f. docs/manual/configure.txt:
>>>> >          >
>>>> >          >      If you use kernel headers that are more recent than
>>>> the
>>>> >         Linux
>>>> >          >      kernel you run on your embedded system, then the C
>>>> >         library might
>>>> >          >      be using interfaces that are not provided by your
>>>> Linux
>>>> >         kernel.
>>>> >
>>>> >         Good catch Edgar!
>>>> >         So Mohd, what you need here is a toolchain with older libc.
>>>> >
>>>> https://buildroot.org/downloads/manual/manual.html#_cross_compilation_toolchain
>>>> >         <
>>>> https://buildroot.org/downloads/manual/manual.html#_cross_compilation_toolchain
>>>> >
>>>> >
>>>> >         But again, do you really need to use so such old versions
>>>> >         instead of try
>>>> >         to use buildroot's beaglebone_defconfig?
>>>> >
>>>> >          > In the same config file, there is:
>>>> >          >> # BR2_PACKAGE_BUSYBOX is not set
>>>> >          >
>>>> >          > When disabling busybox, you should have seen the message:
>>>> >          >
>>>> >          >      You may need to enable other packages to get a working
>>>> >         system
>>>> >          >      You better know what you're doing!
>>>> >
>>>> >         Despite of what I've written on my previous e-mail(my test was
>>>> >         wrong),
>>>> >         he has BR2_INIT_SYSTEMD=y that works as Init System, so
>>>> that's ok.
>>>> >
>>>> >          > And then:
>>>> >          >> # BR2_PACKAGE_SYSTEMD_LOGIND is not set
>>>> >
>>>> >         Good catch again Edgar! This ^^^ should be the point. Because
>>>> it's
>>>> >         exactly the systemd login dameon.
>>>> >
>>>> >          >> # BR2_PACKAGE_UTIL_LINUX_LOGIN is not set
>>>> >
>>>> >         This ^^^ is not selected by systemd, so I expect
>>>> >         BR2_PACKAGE_SYSTEMD_LOGIND to do the job(even if I'm not a
>>>> systemd
>>>> >         expoert at all).
>>>> >
>>>> >         But as Edgar pointed linux headers don't match so you have 3
>>>> >         choices:
>>>> >         1) find a toolchain with linux-headers <= 4.4.*
>>>> >         2) update linux version
>>>> >         3) start from scratch using buildroot beaglebone_defconfig
>>>> >
>>>> >         Best regards
>>>> >         --
>>>> >         Giulio Benetti
>>>> >         Benetti Engineering sas
>>>> >
>>>>
>>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at buildroot.org
>>> https://lists.buildroot.org/mailman/listinfo/buildroot
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20220222/2a174b12/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20220221_211831.jpg
Type: image/jpeg
Size: 150206 bytes
Desc: not available
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20220222/2a174b12/attachment-0001.jpg>


More information about the buildroot mailing list