Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130516233834.457fa3a1@newbook>
Date: Thu, 16 May 2013 23:38:34 -0700
From: Isaac Dunham <idunham@...abit.com>
To: musl@...ts.openwall.com
Subject: Re: xorg intel driver load error

On Thu, 16 May 2013 20:37:05 -0400
Rich Felker <dalias@...ifal.cx> wrote:

> > Hi,
> > 
> > i am using my own x86_64-linux-musl from bootstrap+musl cross,
> > https://plan9assembler.wordpress.com/
> > https://github.com/pikhq/bootstrap-linux/issues/8
> > https://github.com/pikhq/bootstrap-linux/issues/9
> > 
> > trying to install xorg, compilation done,(mesa, font, lib, proto,
> > xserver etc).
> > but when xserver didn't work, due to intel driver.
> > 
> > ....
> > (EE) Failed to load /usr/lib/xorg/modules/drivers/intel_drv.so:
> > Error relocating /usr/lib/xorg/modules/drivers/intel_drv.so:
> > fbPolyPoint: symbol not found
> > (II) UnloadModule: "intel"
> > (II) Unloading intel
> > (EE) Failed to load module "intel" (loader failed, 7)
> > ....
> > (EE) No drivers available.  
> 
> I believe the issue is that xorg lacks proper dependency information
> between modules, so unless they're loaded in the correct order,
> symbols will be missing. This bug gets overlooked with glibc because
> many (but not all) symbol references can be deferred until the first
> time they're used (lazy binding); musl intentionally does not support
> lazy binding.
> 
> I'm not sure if anybody has worked on a patch to fix the issue, but
> you should be able to work around it by tweaking your config file to
> load modules in dependency order. In your case, it sounds like the
> missing symbol is in some general fb module..

It's libwfb.so or libfb.so; I can't tell which one has the
symbol and which uses it. These are modules wfb and fb.
I'd suggest trying out fb first.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.