From: Peter Seiderer <ps.report@gmx.net>
To: Rafal Gorczynski <rafal.gorczynski@ecosystems-group.co.uk>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] A problem with running Xorg 2021.08.x
Date: Wed, 15 Sep 2021 22:32:06 +0200 [thread overview]
Message-ID: <20210915223206.43a7bda0@gmx.net> (raw)
In-Reply-To: <20210915190617.5d64460f@gmx.net>
On Wed, 15 Sep 2021 19:06:17 +0200, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Rafal,
>
> On Wed, 15 Sep 2021 12:47:56 +0000, Rafal Gorczynski <rafal.gorczynski@ecosystems-group.co.uk> wrote:
>
> > Hi,
> > I'm looking for help with running Xorg in my image, tried multiple branches such as 2021.08, 2021.05, 2021.02 with no luck.
> >
> > This is what I've received from Xorg
> >
> > [ 353.565] (II) LoadModule: "intel"
> > [ 353.565] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
> > [ 353.565] (EE) Failed to load /usr/lib/xorg/modules/drivers/intel_drv.so: /usr/lib/xorg/modules/drivers/intel_drv.so: undefined symbol: vgaHWFreeHWRec
> > [ 353.565] (EE) Failed to load module "intel" (loader failed, 0)
> > [ 353.565] (II) LoadModule: "modesetting"
> > [ 353.565] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> > [ 353.565] (EE) Failed to load /usr/lib/xorg/modules/drivers/modesetting_drv.so: /usr/lib/xorg/modules/drivers/modesetting_drv.so: undefined symbol: shadowRemove
> > [ 353.565] (EE) Failed to load module "modesetting" (loader failed, 0)
> > [ 353.565] (II) LoadModule: "fbdev"
> > [ 353.565] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
> > [ 353.565] (EE) Failed to load /usr/lib/xorg/modules/drivers/fbdev_drv.so: /usr/lib/xorg/modules/drivers/fbdev_drv.so: undefined symbol: fbdevHWSave
> > [ 353.565] (EE) Failed to load module "fbdev" (loader failed, 0)
> > [ 353.565] (II) LoadModule: "vesa"
> > [ 353.565] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
> > [ 353.565] (EE) Failed to load /usr/lib/xorg/modules/drivers/vesa_drv.so: /usr/lib/xorg/modules/drivers/vesa_drv.so: undefined symbol: VBESetModeParameters
> >
> > Full Xorg.log https://pastebin.com/nu5wpHex
> > Full defconfig https://pastebin.com/RLJRwMES
> >
> >
> > I don't have problems with branch 2020.08.x with the same defconfig.
> >
> > Any idea?
>
> Seems similar to the problem fixed by commit [1] (for the fbdev use case), but take a look
s/fbdev/fbturbo/
Regards,
Peter
> at the linked bug report/mailing list report for hints about the module loading order in
> xorg.conf file and/or needed patches...
>
> Regards,
> Peter
>
> [1] https://git.buildroot.net/buildroot/commit/?id=9dc2b4a4eee557d3d9e7df31e9d2e96f364a2f03
>
> >
> > Rafal
> >
>
> _______________________________________________
> buildroot mailing list
> buildroot@lists.buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-15 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:47 [Buildroot] A problem with running Xorg 2021.08.x Rafal Gorczynski
2021-09-15 17:06 ` Peter Seiderer
2021-09-15 20:32 ` Peter Seiderer [this message]
2021-09-16 11:39 ` Rafal Gorczynski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210915223206.43a7bda0@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=rafal.gorczynski@ecosystems-group.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox