[yocto] ERROR: Multiple .bb files are due to be built which each provide virtual/libgbm
Hello I try to do a custom linux with yocto and meta-ti for am335x processor. Y use : poky warrior git branch version meta-ti git branch 2019.00 version I do some configuration in the local.conf, bblayers.conf, custom-recipe (Polycaptil-image-minimal), machine.conf, ... to prepare and build my custom linux system for am335x processor (custom board based on the ti am335x-evmsk starter kit dev board). And when I try to compile the linux system, I got this error message "Multiple .bb files are due to be built which each provide virtual/libgbm". Here is what I have on my terminal before, during and after the compilation : https://pastebin.com/cJ9bzMde As it is written there is "Multiple .bb files are due to be built which each provide virtual/libgbm". But I don't know what is mean, what is the problem and how to solve it. Can somebody help me ? Nikola -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto touchscreen
f" (==) Using system config directory "/usr/share/X11/xorg.conf.d" Poky (Yocto Project Reference Distro) 2.6.1 am335x-evm /dev/ttyS0 am335x-evm login: The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported high keycode 372 for name ignored > X11 cannot support keycodes above 255. > This warning only shows for the first high keycode. Errors from xkbcomp are not fatal to the X server [ 15.888959] random: dbus-daemon: uninitialized urandom read (12 bytes read, 65 bits of entropy available) D-BUS per-session daemon address is: unix:abstract=/tmp/dbus-JjEW6Wgjtx,guid=87af020e5c6f1a7e21d449e55ca46df5 Size 1024x768 not found in available modes Error: No calibratable devices found. matchbox: Cant find a keycode for keysym 269025056 matchbox: ignoring key shortcut XF86Calendar=!$contacts matchbox: Cant find a keycode for keysym 2809 matchbox: ignoring key shortcut telephone=!$dates matchbox: Cant find a keycode for keysym 269025050 matchbox: ignoring key shortcut XF86Start=!matchbox-remote -desktop Failed to launch bus: Failed to execute child process ?/usr/bin? (Permission denied) (matchbox-terminal:274): dbind-WARNING **: 08:25:27.404: Error retrieving accessibility bus address: org.a11y.Bus.Error: Failed to execute child process ?/usr/bin? (Permission denied) [ 43.718127] random: nonblocking pool is initialized De : Stanisavljevic Envoyé : lundi 18 février 2019 15:27 À : 'Zoran Stojsavljevic' Cc : 'Yocto Project' ; 'Marc Ferland' Objet : RE: [yocto] yocto touchscreen Hello Zoran I will try these 2 ways. Of course, the second way is the easiest, but I will try also the first way only to see if it is possible. I will keep you in touch if the first way can work. Best regards, Nikola De : Zoran Stojsavljevic < <mailto:zoran.stojsavlje...@gmail.com> zoran.stojsavlje...@gmail.com> Envoyé : lundi 18 février 2019 15:21 À : Stanisavljevic < <mailto:n.stanisavlje...@polycaptil.fr> n.stanisavlje...@polycaptil.fr> Cc : Yocto Project < <mailto:yocto@yoctoproject.org> yocto@yoctoproject.org>; Marc Ferland < <mailto:marc.ferl...@gmail.com> marc.ferl...@gmail.com> Objet : Re: [yocto] yocto touchscreen Hello Nikola, Two things, which immediately came to my mind: [1 - Harder way] Either to change xorg-x11-server in sumo to match at least xorg-x11-server 1.20.3; (harder way, since few people know exact dependencies among various GFX packages, and what and how many packages need to be also changed to make xorg-x11-server 1.20.3 to work) [2 - Easier Way] Either to migrate YOCTO to Thud, where the correct xorg-x11-server package 1.20.3 is already fixed and set! (easier way, since exact dependencies among various GFX packages are already set for 1.20.3) Best Regards, Zoran ___ On Mon, Feb 18, 2019 at 2:48 PM Stanisavljevic < <mailto:n.stanisavlje...@polycaptil.fr> n.stanisavlje...@polycaptil.fr> wrote: Thank you Zoran for trying to help me. I tried to resolve the problem, but I didn’t succeed yet, I think I will to continue, and If after some time I find nothing, I’m going to migrate to the thud version. I will maybe try to use Bugzilla Nikola De : Zoran Stojsavljevic < <mailto:zoran.stojsavlje...@gmail.com> zoran.stojsavlje...@gmail.com> Envoyé : mardi 5 février 2019 19:28 À : Stanisavljevic < <mailto:n.stanisavlje...@polycaptil.fr> n.stanisavlje...@polycaptil.fr> Cc : Yocto Project < <mailto:yocto@yoctoproject.org> yocto@yoctoproject.org>; <mailto:marc.ferl...@gmail.com> marc.ferl...@gmail.com Objet : Re: [yocto] yocto touchscreen Hello Nikola, Let us try to cut to the chase! After reading what Marc Ferland says/writes, and looking into the following: <https://bugzilla.redhat.com/show_bug.cgi?id=1650634> https://bugzilla.redhat.com/show_bug.cgi?id=1650634 I have spotted the following: Pat Riehecky 2018-11-20 14:28:22 UTC the bug remains with the elrepo kernels: kernel-ml-4.19.2-1.el7.elrepo.x86_64 kernel-lt-4.4.163-1.el7.elrepo.x86_64 I never had this problem since I do not use Xorg (GFX), rather I only use serial console from VBox VM from my BBB (pass-through). Thus, my suggestion for you, to skip the whole mess is to rebuild your distro in the light of YOCTO Project 2.6.1 (thud 20.0.0.1). My best guess (then you'll inherit YOCTO kernel 4.20.x with fixed Xorg - X11). I am using Fedora 29 on my laptop. Also from the bugzilla: Pat Riehecky 2018-11-20 15:46:11 UTC Bug resolved by rebuilding xorg-x11-server-1.20.3-1.fc29 [1] for 7.6. With this in mind it appears to be an Xorg server bug rather than fbdev. >From my HP EliteBook 840 G1 Fedora 29, Xorg.0.log - February 5th, 2019., I have the following: [26.955] Kernel command line: BOOT
Re: [yocto] yocto touchscreen
Hello Zoran
I will try these 2 ways.
Of course, the second way is the easiest, but I will try also the first way
only to see if it is possible.
I will keep you in touch if the first way can work.
Best regards,
Nikola
De : Zoran Stojsavljevic
Envoyé : lundi 18 février 2019 15:21
À : Stanisavljevic
Cc : Yocto Project ; Marc Ferland
Objet : Re: [yocto] yocto touchscreen
Hello Nikola,
Two things, which immediately came to my mind:
[1 - Harder way] Either to change xorg-x11-server in sumo to match at least
xorg-x11-server 1.20.3;
(harder way, since few people know exact dependencies among various GFX
packages, and what
and how many packages need to be also changed to make xorg-x11-server
1.20.3 to work)
[2 - Easier Way] Either to migrate YOCTO to Thud, where the correct
xorg-x11-server package 1.20.3
is already fixed and set!
(easier way, since exact dependencies among various GFX packages are
already set for 1.20.3)
Best Regards,
Zoran
___
On Mon, Feb 18, 2019 at 2:48 PM Stanisavljevic mailto:n.stanisavlje...@polycaptil.fr> > wrote:
Thank you Zoran for trying to help me.
I tried to resolve the problem, but I didn’t succeed yet, I think I will to
continue, and If after some time I find nothing, I’m going to migrate to the
thud version.
I will maybe try to use Bugzilla
Nikola
De : Zoran Stojsavljevic mailto:zoran.stojsavlje...@gmail.com> >
Envoyé : mardi 5 février 2019 19:28
À : Stanisavljevic mailto:n.stanisavlje...@polycaptil.fr> >
Cc : Yocto Project mailto:yocto@yoctoproject.org> >;
marc.ferl...@gmail.com <mailto:marc.ferl...@gmail.com>
Objet : Re: [yocto] yocto touchscreen
Hello Nikola,
Let us try to cut to the chase!
After reading what Marc Ferland says/writes, and looking into the following:
https://bugzilla.redhat.com/show_bug.cgi?id=1650634
I have spotted the following:
Pat Riehecky 2018-11-20 14:28:22 UTC
the bug remains with the elrepo kernels:
kernel-ml-4.19.2-1.el7.elrepo.x86_64
kernel-lt-4.4.163-1.el7.elrepo.x86_64
I never had this problem since I do not use Xorg (GFX), rather I only
use serial console from VBox VM from my BBB (pass-through).
Thus, my suggestion for you, to skip the whole mess is to rebuild your
distro in the light of YOCTO Project 2.6.1 (thud 20.0.0.1).
My best guess (then you'll inherit YOCTO kernel 4.20.x with fixed Xorg - X11).
I am using Fedora 29 on my laptop. Also from the bugzilla:
Pat Riehecky 2018-11-20 15:46:11 UTC
Bug resolved by rebuilding xorg-x11-server-1.20.3-1.fc29 [1] for 7.6.
With this in mind it appears to be an Xorg server bug rather than fbdev.
>From my HP EliteBook 840 G1 Fedora 29, Xorg.0.log - February 5th, 2019.,
I have the following:
[26.955] Kernel command line: BOOT_IMAGE=/vmlinuz-4.20.6-200.fc29.x86_64
root=/dev/mapper/fedora-root ro rd.lvm.lv <http://rd.lvm.lv> =fedora/root
rd.lvm.lv <http://rd.lvm.lv> =fedora/swap rhgb
quiet LANG=en_US.UTF-8
[26.955] Build Date: 11 January 2019 12:47:38PM
[26.955] Build ID: xorg-x11-server 1.20.3-3.fc29
[26.955] Current version of pixman: 0.34.0
Best Regards,
Zoran
___
On Tue, Feb 5, 2019 at 2:49 PM Zoran Stojsavljevic
mailto:zoran.stojsavlje...@gmail.com> > wrote:
>
> Hello Nikola,
>
> > I created a kernel recipe with a bbappend file, and, I added
> > the same defconfig that I used for krogoth version.
> > The bbappend for kernel recipe concern meta-ti layer.
> > I didn't edited defconfig file in other layers which contain a
> > kernel recipe.
>
> It could be some problem that Sumo does not take your bbappend file into the
> consideration as placed.
>
> It could be something else, as well.
>
> I have the same issue with my defconfig file for my Thud Beagle Bone Black
> (BBB)
> standard board. Every time I recompile my YOCTO for it for different
> releases, I need
> to import my specific defconfig. But I use complete different repos for my
> standard
> Beagle Bone Black than YOCTO BBB Poky reference distro.
>
> Here is what I use in Thud (my bblayers.conf):
>
> POKY_BBLAYERS_CONF_VERSION = "2"
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /home/user/projects2/beaglebone-black/yocto-thud/meta-bbb \
>
> /home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-networking
> \
>
> /home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-oe \
>
> /home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-python
> \
> /home/user/projects2/beaglebone-black/yocto-thud/meta-qt5 \
> /home/user/projects2/beaglebone-black/yocto-thud/poky/meta \
> /home/user/projects2/beaglebone-black/yocto-thud/poky/meta-poky"
>
> There, I replace defconf
Re: [yocto] yocto touchscreen
Thank you Zoran for trying to help me.
I tried to resolve the problem, but I didn’t succeed yet, I think I will to
continue, and If after some time I find nothing, I’m going to migrate to the
thud version.
I will maybe try to use Bugzilla
Nikola
De : Zoran Stojsavljevic
Envoyé : mardi 5 février 2019 19:28
À : Stanisavljevic
Cc : Yocto Project ; marc.ferl...@gmail.com
Objet : Re: [yocto] yocto touchscreen
Hello Nikola,
Let us try to cut to the chase!
After reading what Marc Ferland says/writes, and looking into the following:
https://bugzilla.redhat.com/show_bug.cgi?id=1650634
I have spotted the following:
Pat Riehecky 2018-11-20 14:28:22 UTC
the bug remains with the elrepo kernels:
kernel-ml-4.19.2-1.el7.elrepo.x86_64
kernel-lt-4.4.163-1.el7.elrepo.x86_64
I never had this problem since I do not use Xorg (GFX), rather I only
use serial console from VBox VM from my BBB (pass-through).
Thus, my suggestion for you, to skip the whole mess is to rebuild your
distro in the light of YOCTO Project 2.6.1 (thud 20.0.0.1).
My best guess (then you'll inherit YOCTO kernel 4.20.x with fixed Xorg - X11).
I am using Fedora 29 on my laptop. Also from the bugzilla:
Pat Riehecky 2018-11-20 15:46:11 UTC
Bug resolved by rebuilding xorg-x11-server-1.20.3-1.fc29 [1] for 7.6.
With this in mind it appears to be an Xorg server bug rather than fbdev.
>From my HP EliteBook 840 G1 Fedora 29, Xorg.0.log - February 5th, 2019.,
I have the following:
[26.955] Kernel command line: BOOT_IMAGE=/vmlinuz-4.20.6-200.fc29.x86_64
root=/dev/mapper/fedora-root ro rd.lvm.lv <http://rd.lvm.lv> =fedora/root
rd.lvm.lv <http://rd.lvm.lv> =fedora/swap rhgb
quiet LANG=en_US.UTF-8
[26.955] Build Date: 11 January 2019 12:47:38PM
[26.955] Build ID: xorg-x11-server 1.20.3-3.fc29
[26.955] Current version of pixman: 0.34.0
Best Regards,
Zoran
___
On Tue, Feb 5, 2019 at 2:49 PM Zoran Stojsavljevic
mailto:zoran.stojsavlje...@gmail.com> > wrote:
>
> Hello Nikola,
>
> > I created a kernel recipe with a bbappend file, and, I added
> > the same defconfig that I used for krogoth version.
> > The bbappend for kernel recipe concern meta-ti layer.
> > I didn't edited defconfig file in other layers which contain a
> > kernel recipe.
>
> It could be some problem that Sumo does not take your bbappend file into the
> consideration as placed.
>
> It could be something else, as well.
>
> I have the same issue with my defconfig file for my Thud Beagle Bone Black
> (BBB)
> standard board. Every time I recompile my YOCTO for it for different
> releases, I need
> to import my specific defconfig. But I use complete different repos for my
> standard
> Beagle Bone Black than YOCTO BBB Poky reference distro.
>
> Here is what I use in Thud (my bblayers.conf):
>
> POKY_BBLAYERS_CONF_VERSION = "2"
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /home/user/projects2/beaglebone-black/yocto-thud/meta-bbb \
>
> /home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-networking
> \
>
> /home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-oe \
>
> /home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-python
> \
> /home/user/projects2/beaglebone-black/yocto-thud/meta-qt5 \
> /home/user/projects2/beaglebone-black/yocto-thud/poky/meta \
> /home/user/projects2/beaglebone-black/yocto-thud/poky/meta-poky"
>
> There, I replace defconfig in this layer:
> /home/user/projects2/beaglebone-black/yocto-thud/meta-bbb
> with my own defconfig.
>
> In the directory:
> /home/user/projects2/beaglebone-black/yocto-thud/meta-bbb/recipes-kernel/linux/linux-stable-4.19/beaglebone
>
> If you use only Poky repository, then you need to read the following
> paragraph (how to use
> your defconfig with Poky):
>
> [2.3.3. Changing the Configuration] YOCTO Project Linux Development Manual
> https://www.yoctoproject.org/docs/2.5/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
> 2.3.3. Changing the Configuration
>
> I hope this will help. Please, keep us posted!
>
> Zoran
> ___
>
>
> On Tue, Feb 5, 2019 at 10:54 AM Stanisavljevic
> mailto:n.stanisavlje...@polycaptil.fr> >
> wrote:
>>
>> Hy Zoran
>>
>> Thank's to take time to answer
>>
>> I created a kernel recipe with a bbappend file, and, I added the same
>> defconfig that I used for krogoth version.
>> The bbappend for kernel recipe concern meta-ti layer.
>> I didn't edited defconfig file in other layers which contain a kernel recipe.
>>
>> I think it's a problem which concern the screen resolution, screen frequency
>> and ad
Re: [yocto] yocto touchscreen
Hy Zoran Thank's to take time to answer I created a kernel recipe with a bbappend file, and, I added the same defconfig that I used for krogoth version. The bbappend for kernel recipe concern meta-ti layer. I didn't edited defconfig file in other layers which contain a kernel recipe. I think it's a problem which concern the screen resolution, screen frequency and adc touchscreen. Something is different between the krogoth and sumo version, but I didn't find what is changed... Xrandr show that problem is maybe around the screen resolution. It's show the next message : "Size 1024x768 not found in available modes" Maybe it was changed between krogoth and sumo version...but I don't know where it is indicated if sources files... What do you think ? problem can be around the screen resolution, screen frequency and adc touchscreen ? Nikola -Message d'origine- De : Zoran Stojsavljevic Envoyé : lundi 4 février 2019 17:08 À : Stanisavljevic Cc : Yocto Project Objet : Re: [yocto] yocto touchscreen > I built a first version of this os with version krogoth and it works fine. > > Now I build a second version of this os with version sumo and the > touch screen works fine during boot process but when kernel is loaded, > touchscreen freeze / lock and impossible to use it. Did you compare Krogoth kernel defconfig with Sumo kernel defconfig? May there are some mismatches in drivers' setup between these two? Zoran ___ On Mon, Feb 4, 2019 at 12:24 PM Stanisavljevic wrote: > > Hy Team, > > > > I have a problem > > > > I buid a custom os for AM335x processor and I used yocto to do it. > > > > I build a first version of this os with version krogoth and it work fine. > > > > Now I build a second version of this os with version sumo and the touchscreen > work fine during boot process but when kernel is loaded, touchscreen freeze / > lock and impossible to use it. > > The terminal is printed on the touchscreen but the screen is locked, > impossible to write a command or to move the mouse to select, …. > > > > Here is the log of boot to the user session (log got with serial > communication between PC and board) : > > > > U-Boot SPL 2017.05-1-g041a398 (May 02 2018 - 18:36:57) > > Trying to boot from MMC1 > > reading uboot.env > > reading u-boot.img > > reading u-boot.img > > reading u-boot.img > > reading u-boot.img > > > > > > U-Boot 2017.05-1-g041a398 (May 02 2018 - 18:36:57 +0200) > > > > CPU : AM335X-GP rev 2.1 > > Model: TI AM335x EVM-SK > > DRAM: 256 MiB > > NAND: 0 MiB > > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > reading uboot.env > > ERROR: No USB device found > > > > at drivers/usb/gadget/ether.c:2709/usb_ether_init() > > Net: CACHE: Misaligned operation at range [8df323c0, 8df32464] > > > > Warning: ethernet@4a10 using MAC address from ROM > > eth0: ethernet@4a10 > > Hit any key to stop autoboot: 0 > > reading zImage > > 3412752 bytes read in 251 ms (13 MiB/s) > > reading dtb > > 39733 bytes read in 12 ms (3.2 MiB/s) > > ## Flattened Device Tree blob at 8200 > >Booting using the fdt blob at 0x8200 > >Loading Device Tree to 8df19000, end 8df25b34 ... OK > > > > Starting kernel ... > > > > [0.00] Booting Linux on physical CPU 0x0 > > [0.00] Initializing cgroup subsys cpu > > [0.00] Initializing cgroup subsys cpuacct > > [0.00] Linux version 4.4.19-ge581bb1cac > (polycaptil@polycaptil-HP-Notebook) (gcc version 5.3.0 (GCC) ) #1 PREEMPT Thu > May 24 11:42:17 CEST 2018 > > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d > > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > > [0.00] Machine model: TI AM335x EVM-SK > > [0.00] cma: Reserved 48 MiB at 0x8a80 > > [0.00] Memory policy: Data cache writeback > > [0.00] CPU: All CPU(s) started in SVC mode. > > [0.00] AM335X ES2.1 (sgx neon ) > > [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total > pages: 64960 > > [0.00] Kernel command line: console=ttyO0,115200 root=/dev/mmcblk0p3 > rw > > [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) > > [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) > > [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) > > [0.00] Memory: 200444K/262144K available (6495K kernel code, 313K > rwdata, 2368K rodata, 260K init, 265K bss, 12548K reserved, 49152K > cma-reserved, 0
[yocto] yocto touchscreen
Hy Team, I have a problem I buid a custom os for AM335x processor and I used yocto to do it. I build a first version of this os with version krogoth and it work fine. Now I build a second version of this os with version sumo and the touchscreen work fine during boot process but when kernel is loaded, touchscreen freeze / lock and impossible to use it. The terminal is printed on the touchscreen but the screen is locked, impossible to write a command or to move the mouse to select, .. Here is the log of boot to the user session (log got with serial communication between PC and board) : U-Boot SPL 2017.05-1-g041a398 (May 02 2018 - 18:36:57) Trying to boot from MMC1 reading uboot.env reading u-boot.img reading u-boot.img reading u-boot.img reading u-boot.img U-Boot 2017.05-1-g041a398 (May 02 2018 - 18:36:57 +0200) CPU : AM335X-GP rev 2.1 Model: TI AM335x EVM-SK DRAM: 256 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 reading uboot.env ERROR: No USB device found at drivers/usb/gadget/ether.c:2709/usb_ether_init() Net: CACHE: Misaligned operation at range [8df323c0, 8df32464] Warning: ethernet@4a10 using MAC address from ROM eth0: ethernet@4a10 Hit any key to stop autoboot: 0 reading zImage 3412752 bytes read in 251 ms (13 MiB/s) reading dtb 39733 bytes read in 12 ms (3.2 MiB/s) ## Flattened Device Tree blob at 8200 Booting using the fdt blob at 0x8200 Loading Device Tree to 8df19000, end 8df25b34 ... OK Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.19-ge581bb1cac (polycaptil@polycaptil-HP-Notebook) (gcc version 5.3.0 (GCC) ) #1 PREEMPT Thu May 24 11:42:17 CEST 2018 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: TI AM335x EVM-SK [0.00] cma: Reserved 48 MiB at 0x8a80 [0.00] Memory policy: Data cache writeback [0.00] CPU: All CPU(s) started in SVC mode. [0.00] AM335X ES2.1 (sgx neon ) [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64960 [0.00] Kernel command line: console=ttyO0,115200 root=/dev/mmcblk0p3 rw [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Memory: 200444K/262144K available (6495K kernel code, 313K rwdata, 2368K rodata, 260K init, 265K bss, 12548K reserved, 49152K cma-reserved, 0K highmem) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xffc0 - 0xfff0 (3072 kB) [0.00] vmalloc : 0xd080 - 0xff80 ( 752 MB) [0.00] lowmem : 0xc000 - 0xd000 ( 256 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc08b0034 (8865 kB) [0.00] .init : 0xc08b1000 - 0xc08f2000 ( 260 kB) [0.00] .data : 0xc08f2000 - 0xc09407f0 ( 314 kB) [0.00].bss : 0xc09407f0 - 0xc0982d58 ( 266 kB) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Preemptible hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 32. [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 interrupts [0.00] OMAP clockevent source: timer2 at 2400 Hz [0.15] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [0.36] clocksource: timer1: mask: 0x max_cycles: 0x, max_idle_ns: 79635851949 ns [0.47] OMAP clocksource: timer1 at 2400 Hz [0.000222] clocksource_probe: no matching clocksources found [0.000415] Console: colour dummy device 80x30 [0.000442] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' [0.000448] This ensures that you still see kernel messages. Please [0.000454] update your kernel commandline. [0.000473] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216) [0.089064] pid_max: default: 32768 minimum: 301 [0.089193] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.089205] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.089932] Initializing cgroup subsys io [0.089964] Initializing cgroup subsys memory [0.090005] Initializing cgroup subsys devices [0.090021] Initializing cgroup subsys freezer [0.090036]
[yocto] xrandr / xinput calibrator
Hy team, I tried to migrate from krogoth to sumo version of yocto project, to compile a custom OS for a custom board based on TI AM335x EVMSK Starter Kit. On this custom board there is a touchscreen panel (same like the AM335x EVMSK starter Kit) whitch worked fine with krogoth version. When I migrated to sumo version, while the OS boot the touchscreen work fine, but when the screen display to log the user and when it display the mouse, the touschreen panel is completely locked. I think that this append during the boot of the OS : Xrandr is called and try to do something to configure/set the touschscreen panel. But xrandr return the following message : polycaptil-machine-am335x-evmsk login: Size 1024x768 not found in available mode (screen resolution is 480x272) Later xinput_calibrator pring this message : Error: No calibratable devices found. But when I log to the user session (with putty) and I execute xrandr -listmonitors I get : xrandr: Failed to get size of gamma for output default Monitors: 1 0: +default 480/127x272/72+0+0 default It means that touschscreen panel is recognized with the right resolution but somewhere it's not correctly defined in the OS. I exported 0 in DISPLAY environnement variable and tried to use xininput_calibrator but without success. What can I do to solve this problem ? I don't know if I need to configure something when I compile the OS with yocto, or, if the configuration need to be done when the OS is booted and user is logged in ? I don't understand, because, I have not this problem (touschscreen panel locked and unusable) with krogoth version. Thank's to taking your time to read my problem and to trying to help me to solve it. STANISAVLJEVIC Nikola -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] xrandr / xinput calibrator
Hy everybody, I tried to migrate from krogoth to sumo version of yocto project, to compile a custom OS for a custom board based on TI AM335x EVMSK Starter Kit. On this custom board there is a touchscreen panel (same like the AM335x EVMSK starter Kit) whitch worked fine with krogoth version. When I migrated to sumo version, while the OS boot the touchscreen work fine, but when the screen display to log the user and when it display the mouse, the touschreen panel is completely locked. I think that this append during the boot of the OS : Xrandr is called and try to do something to configure/set the touschscreen panel. But xrandr return the following message : polycaptil-machine-am335x-evmsk login: Size 1024x768 not found in available mode (screen resolution is 480x272) Later xinput_calibrator pring this message : Error: No calibratable devices found. But when I log to the user session (with putty) and I execute xrandr -listmonitors I get : xrandr: Failed to get size of gamma for output default Monitors: 1 0: +default 480/127x272/72+0+0 default It means that touschscreen panel is recognized with the right resolution but somewhere it's not correctly defined in the OS. I exported 0 in DISPLAY environnement variable and tried to use xininput_calibrator but without success. What can I do to solve this problem ? I don't know if I need to configure something when I compile the OS with yocto, or, if the configuration need to be done when the OS is booted and user is logged in ? I don't understand, because, I have not this problem (touschscreen panel locked and unusable) with krogoth version. Thank's to taking your time to read my problem and to trying to help me to solve it. STANISAVLJEVIC Nikola -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] am335x evmsk screen init:id"00" respawning too fast disabled for 5 minutes yocto sumo
Hi Holzmayr and Heiko, My problem was solved with your advices. I edited the serial console variable on the machine conf file of my custom machine. It's work fine. Thank's n.stanisavljevic -Message d'origine- De : Heiko Schocher Envoyé : lundi 3 décembre 2018 05:42 À : n.stanisavlje...@polycaptil.fr Cc : Josef Holzmayr ; yocto@yoctoproject.org Objet : Re: [yocto] am335x evmsk screen init:id"00" respawning too fast disabled for 5 minutes yocto sumo Hi n.stanisavljevic, Am 28.11.2018 um 20:55 schrieb Josef Holzmayr: > Howdy! > > On Wed, Nov 28, 2018 at 03:50:02PM +, n.stanisavlje...@polycaptil.fr > wrote: >> Hello everybody >> >> here is an introduction of my situation : >> >> I build a custom board from schematic of sitara AM335x-evmsk starter kit. >> I succeed to make a custom OS with yocto (krogoth version) and to boot this >> OS (embedded Linux) on my custom board. >> >> This custom board contain a touchscreen (same touchscreen like in the >> AM335x-evmsk starter kit). >> >> All worked fine on this board while I used krogoth version on yocto. >> >> my problem : >> >> Few time ago, I decided to migrate to sumo version of yocto. >> I build with success the OS (embedded Linux) with yocto sumo version for my >> custom board, but when I try to boot this OS, it's stop/lock and print the >> following message : >> >> "INIT:Id'00' respawning too fast : disabled for 5 minutes" (I put a >> screenshot of this message ridden on putty). >> Every 5 minutes I got this message and I can't acces to the user session on >> putty and on the touchscreen, all board is locked. > > This is probably because you are basing off something that sets > SERIAL_CONSOLES for the yocto-kernel, like > http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/tree/meta-yocto-b > sp/conf/machine/beaglebone-yocto.conf?h=master#n23 > > If you are using a custom tree which does not use the special driver > for the uart, then you should be fine by setting SERIAL_CONSOLES ?= > "115200;ttyS0" > in your MACHINE config Yep, see also my patch: https://www.mail-archive.com/yocto@yoctoproject.org/msg42383.html may it help you ... bye, Heiko > >> >> I don't understand why this problem appear when I build a OS with the sumo >> version on Yocto. >> I have not this problem when I build a OS with the krogoth version on yocto. >> >> Somebody can help me to solve this problem ? >> what can I do ? >> > > Greetz > -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-52 Fax: +49-8142-66989-80 Email: h...@denx.de -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
