ping, please see if you can help
--
Thanks,
Sivaprakash
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60875): https://lists.yoctoproject.org/g/yocto/message/60875
Mute This Topic: https://lists.yoctoproject.org/mt/100784732/21656
Group Owner:
Hi,
we have been using a custom initramfs image in our Yocto BSP, the initramfs
contains busybox and a custom init script to mount the ext4 based root
filesystem and start the init process in the root file system using switch_root
utility.
now we want to move to the systemd as our init
SYSTEMD_SERVICE *:${PN}* fixed my issue.
And thanks for your hint regarding systctl service, I will try it
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60688): https://lists.yoctoproject.org/g/yocto/message/60688
Mute This Topic:
On Sun, 2023-07-30 at 04:00 -0700, daniel_herrman...@web.de wrote:
> Hello,
> I have a problem enabling a simple systemd service.
> I need a manual "systemctl enable" once after boot to enable my
> service.
> If anybody has an idea, it would be very cool.
> Here are my files.
> distro conf:
>
Hello,
I have a problem enabling a simple systemd service.
I need a manual "systemctl enable" once after boot to enable my service.
If anybody has an idea, it would be very cool.
Here are my files.
*distro conf:*
DISTRO_FEATURES:append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED +=
systemd seems to be missing a service.
systemd-sysusers.service
now it appears based on the bitbake that its removed because of musl. However
it remains in some service files... causing an error to be listed in the
service report.
systemd-sysusers.service not-found inactive dead
systemd-timesyncd uses /var/lib/systemd/timesync/clock to maintain a
monotonic system time across reboots even in the presence of RTC failures.
If this file doesn't exist, "at the minimum, it will be set to the systemd
build date".
I dug through systemd's build process, and found that it will
Hey,
I'm trying to configure my yocto image that runs on an MS Surface Go 2
to suspend when pressing the power key shortly, and to poweroff if the
key is held longer.
Systemd theoretically supports that by creating the following file:
cat >
Guess you'll have to provide more than just "It doesn't work" if you want any
serious assistance.
The source code would help. Also telling us whether the drivers actually probe
if you load them manually using modprobe.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
Thanks Mike for your advice!
I've replaced underscore to hyphen and rerun a build from fetch, but
unfortunately that didn't invoke auto-load.
In fact, my modules are device drivers developed in out-of-tree repositories.
Some user-space applications depend on them, so I wanted them to be
*SUMMARY
*
What should I do to enable auto-loading kernel modules in a systemd-employed
system IN ADDITION TO setting KERNEL_MODULE_AUTOLOAD?
*DETAILS*
I'm trying to automatically load out-of-tree kernel modules in my distro (built
using Dunfell) that uses systemd.
Kernel modules and the
Hi,
In 3.1.12, I noticed weston service type was changed to Nofity. This make
weston service cannot be restarted by "systemctl restart weston@root" command.
The service is then timeout and fail.
Investigating systemd unit document, it seems that the notification message is
required for a
Hi Guys i am new in YOCTO project. i have build images before and the images
were included the "ls" and "clear" and all busybox commands. i do not know what
happend now the image does not have anymore the "ls" or "clear" and all that
commands and also there is a folder named && in the root
Hi,
Is it possible to set systemd environment variables from a recipe to do the
same as ' systemctl set-environment SOME_ENV_VAR'?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54911): https://lists.yoctoproject.org/g/yocto/message/54911
Mute
On Tue, 2021-06-01 at 09:23 -0700, Khem Raj wrote:
>
> On 6/1/21 9:13 AM, Luca Boccassi wrote:
> > On Tue, 2021-06-01 at 07:58 -0700, Khem Raj wrote:
> > > On 5/31/21 3:40 PM, Paul Eggleton wrote:
> > > > Hi folks
> > > >
> > > > Upstream in the systemd project, a proposal has been made to add a
On 6/1/21 9:13 AM, Luca Boccassi wrote:
On Tue, 2021-06-01 at 07:58 -0700, Khem Raj wrote:
On 5/31/21 3:40 PM, Paul Eggleton wrote:
Hi folks
Upstream in the systemd project, a proposal has been made to add a special
section to output ELF binaries to record soft runtime dependencies, so
On Tue, 2021-06-01 at 07:58 -0700, Khem Raj wrote:
>
> On 5/31/21 3:40 PM, Paul Eggleton wrote:
> > Hi folks
> >
> > Upstream in the systemd project, a proposal has been made to add a special
> > section to output ELF binaries to record soft runtime dependencies, so that
> > they could be read
On 5/31/21 3:40 PM, Paul Eggleton wrote:
Hi folks
Upstream in the systemd project, a proposal has been made to add a special
section to output ELF binaries to record soft runtime dependencies, so that
they could be read and utilised by distribution build systems such as ours
(they would be
Hi folks
Upstream in the systemd project, a proposal has been made to add a special
section to output ELF binaries to record soft runtime dependencies, so that
they could be read and utilised by distribution build systems such as ours
(they would be translated into RRECOMMENDS in our case). At
Maybe this should be added to sshd.service [unit] part
(to have added dependency) to solve this problem:
> The sshd.service file is as follows:
> [Unit]
> Description=OpenSSH server daemon
> Documentation=man:sshd(8) man:sshd_config(5)
> After=sshdgenkeys.service
> Wants=sshdgenkeys.service
Seems strange to me too...I had been troubleshooting the sshd.service issue for
two days. There was no logs, nothing. I was just hitting the wall. I tried a
lot of combinations to get it to work but all failed.
The sshd.service was starting, if I manually did a systemctl start
sshd.service.
> There was a sshd.socket file in /lib/systemd/system which had the following
> line in it.
Interesting... Pushed/forced me to think.
There is no formal dependency between sshd.service and sshd.socket!
[vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.service
| grep ssh
>
> Seems that some leftovers from System V still reside in YOCTO...
> Correct???
>
Not sure about that.
The problem I faced was because there was a sshd.socket that had the following
line in it. The sshd.socket comes with openssh.
Conflicts=sshd.service
So I had two options. either to add
Interesting... Here is what I have on Fedora32:
[root@fedora32-ssd system]# pwd
/lib/systemd/system
[root@fedora32-ssd system]# cat /lib/systemd/system/sshd.service
[Unit]
Description=OpenSSH server daemon
Documentation=man:sshd(8) man:sshd_config(5)
*After=network.target sshd-keygen.target*
Hello All,
I finally got it to work!!!
There was a sshd.socket file in /lib/systemd/system which had the following
line in it.
Conflicts=sshd.service
I remove it and added the following two lines:
After=network.target
Before=sshd.service
And that did the trick. Now sshd service starts on
Hello Srijan,
Did you recap/look into this sshd.service file?
https://lists.yoctoproject.org/g/yocto/message/49993
Zoran
___
On Fri, Sep 18, 2020 at 8:07 PM wrote:
>
> Hello Khem,
>
> With the above sshd.service file the sshd daemon fails to start. It gives an
> error "(code=exited,
Hello Khem,
With the above sshd.service file the sshd daemon fails to start. It gives an
error "(code=exited, status=203/EXEC)".
Cannot figure out as to why the systemd for sshd fails to work, while the other
systemd files are working perfectly fine.
-=Srijan Nandi
-=-=-=-=-=-=-=-=-=-=-=-
I am facing a peculiar problem with openssh. I have built openssh_8.0p1on zeus.
The sshd.service file is as follows:
[Unit]
Description=OpenSSH server daemon
Documentation=man:sshd(8) man:sshd_config(5)
After=sshdgenkeys.service
Wants=sshdgenkeys.service
[Service]
Type=simple
Hi all,
While trying to build core-image-base, I'm facing with the error "could not
invoke dnf. command". Is there any solutions for this?
Log file error:
ERROR: Could not invoke dnf. Command
We have a legacy device with following configurations:
Chipset Architecture : Intel NM10 express
OS : Yocto warrior
CPU : Atom D2250 Dual Core
Volatile Memory : 2GB DDR3
CPU core : 4
I have generated 64-bit core-image-sato and run on my device but *systemd*
freezes execution with SIGILL (as
Hi,
Where is the systemd service environment set from?
Here is the systemd service env:
SHLVL=1
JOURNAL_STREAM=8:30355
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
INVOCATION_ID=fbd7ba8782544a828902301423a98196
LANG=C
PWD=/
How can I set up systemd service to use the root
Got it figured out, Seems that the default values from
meta/recipes-core/systemd/systemd-serialgetty.bb for SERIAL_CONSOLES in are
being processed instead of the expansion in our layer. Even though
SERIAL_CONSOLES is using SERIAL_CONSOLE. Our solution is to declare
SERIAL_CONSOLE and
Thank you for the quick reply,
in our machin confif only SERIAL_CONSOLE is set, it is:
>
> SERIAL_CONSOLE = "115200 ttyO0"
But yocto then uses that to set SERIAL_CONSOLES
In bitbake -e I see SERIAL_CONSOLE and SERIAL_CONSOLES set to :
>
> # $SERIAL_CONSOLE [3 operations]
> # set
>
On Mon, Jan 27, 2020 at 12:16 PM William Durocher wrote:
>
> We have a build using warrior it boots up well but has a very long boot time
> of around 95 sec. Using systemd-analyze I notice that we the boot takes a
> long time before getting to multi-user.target. As can be seen for the
>
34 matches
Mail list logo
