linux-kernel - Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 18 Mar 2008 13:00:39 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Bryce Harrington <bryce@...onical.com>
Cc:	Justin Madru <jdm64@...ab.com>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]

On Tuesday, March 18, 2008 12:07 pm Bryce Harrington wrote:
> On Sun, Mar 16, 2008 at 06:28:10PM -0700, Justin Madru wrote:
> > Jesse Barnes wrote:
> >> No problem, building X still isn't quite as easy as it should be, but
> >> it's only slightly more complicated than the typical
> >> './configure;make;make install' due to the dependencies between
> >> packages.  You can check out the X wiki (wiki.x.org), there are some
> >> hints on building things there.
>
> <jbarnes> bryce: would it be possible for you to include
>   intel_reg_dumper in your intel driver pkg?
>
> jesse - I looked into this, and in fact debian has already enabled this
> in the 2.2.1 driver, which we are carrying in Hardy.  Timo had to
> disable it though since we currently carry libpciaccess in universe, not
> main.
>
> However, I note that even after installing libpciaccess, it still fails

Ok, thanks for checking.

> to compile (see below):
> > I'm just compiling the intel_reg_dumper right? I don't have to recompile
> > all of X to use it?
> >
> > Bryce Harrington wrote:
> >> The following command will pull in all the dependencies you need for
> >> building -intel:
> >>
> >>  sudo apt-get build-dep xserver-xorg-video-intel
> >
> > Ok, got that. I tried to compile and I found out I also had to install
> > libpciaccess-dev, that's probably because I'm using the git tree and not
> > the one that Ubuntu 7.10 uses. But I still can't compile the
> > intel_reg_dumper I get the following error:
> >
> > intel-driver/src/reg_dumper$ make
> > gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Wpointer-arith -Wstrict-prototypes
> > -Wmissing-prototypes -Wmissing-declarations -Wnested-externs
> > -fno-strict-aliasing -I./.. -DREG_DUMPER -g -O2 -MT main.o -MD -MP -MF
> > .deps/main.Tpo -c -o main.o main.c
> > main.c: In function ‘main’:
> > main.c:72: warning: implicit declaration of function
> > ‘pci_device_map_range’
> > main.c:72: warning: nested extern declaration of ‘pci_device_map_range’
> > main.c:75: error: ‘PCI_DEV_MAP_FLAG_WRITABLE’ undeclared (first use in
> > this function)
> > main.c:75: error: (Each undeclared identifier is reported only once
> > main.c:75: error: for each function it appears in.)
> > make: *** [main.o] Error 1
> >
> > Justin
>
> Yes, the same error occurs with the 2.2.1 driver we have in Hardy right
> now:
>
> bryce@...deok:~/src/xserver-xorg-video-intel/xserver-xorg-video-intel-2.2.1
>-build/src/reg_dumper$ make gcc -DHAVE_CONFIG_H -I. -I../..     -Wall
> -Wpointer-arith -Wstrict-prototypes   -Wmissing-prototypes
> -Wmissing-declarations     -Wnested-externs -fno-strict-aliasing -I./..
> -DREG_DUMPER -g -O2 -MT intel_reg_dumper-main.o -MD -MP -MF
> .deps/intel_reg_dumper-main.Tpo -c -o intel_reg_dumper-main.o `test -f
> 'main.c' || echo './'`main.c main.c: In function 'main':
> main.c:72: warning: implicit declaration of function 'pci_device_map_range'
> main.c:72: warning: nested extern declaration of 'pci_device_map_range'
> main.c:75: error: 'PCI_DEV_MAP_FLAG_WRITABLE' undeclared (first use in this
> function) main.c:75: error: (Each undeclared identifier is reported only
> once main.c:75: error: for each function it appears in.)
> make: *** [intel_reg_dumper-main.o] Error 1
>
> I could get it to build by ifdefing out th pci_device_map_range call,
> and then adding -lpciaccess to the linker, however it segfaults without
> that call.
>
> Does LIBPCIACCESS require xserver 1.4?  (We have 1.3 in Hardy).

No, libpciaccess should be standalone, but the Intel driver requires 0.10 or 
better... Which version are you building against?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/