Re: On including 64-bit libs in 32-bit packages (see #344104)
On Tue, Oct 24, 2006 at 01:52:05AM +0100, Matthew Garrett wrote:
> Hamish Moffatt <firstname.lastname@example.org> wrote:
> > On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote:
> >> Bear in mind that the 64-bit kernel doesn't offer all the functionality
> >> that the 32-bit one does. vm86 is the most obvious thing missing.
> > [8:23am] hamish@noddy:~> grep VM86 /boot/config-2.6.17-2-amd64
> > CONFIG_VM86=y
> In arch/x86_64/ia32/ia32entry.S, both the vm86 calls (vm86 and vm86old)
> are stubbed to sys32_vm86_warning, which just printks "vm86 mode not
> supported on 64 bit kernel" and then returns -ENOSYS.
> This is moderately likely to bite people on X - the 32 bit packages will
> use vm86 to make VESA calls, and a surprising number of drivers use VESA
That might explain some trouble with X on obscure video chipsets
recently reported on debian-amd64 then.
I wonder if it wouldn't be better to set CONFIG_VM86=n in the kernel
rather than pretend it works.
Hamish Moffatt VK3SB <email@example.com> <firstname.lastname@example.org>