Re: DRM/DRI accelerated (3D) graphics?
- To: MG <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: DRM/DRI accelerated (3D) graphics?
- From: Émeric Maschino <email@example.com>
- Date: Sun, 6 Nov 2011 18:09:09 +0100
- Message-id: <[🔎] CAA9xbM4=Ldvdsg=VJOOA6UFRn0GsepiJRvnz2Y=RVKAH+2Mvww@mail.gmail.com>
- In-reply-to: <[🔎] 4EB6A068.firstname.lastname@example.org>
- References: <4E4A69B3.email@example.com> <CAA9xbM7XCHEmmsx_Lx8Fvt2gJteDr8foU+ztDdCaTvRxJd8sKQ@mail.gmail.com> <4E4C5A67.firstname.lastname@example.org> <CAA9xbM7NVTZP7OB3tT-0LdCwYEaK9YcfGkapfrs7nUb3r5UyRQ@mail.gmail.com> <CAA9xbM4VajURk2yYz+Qjb9a2jmAQg4_e-qOPaP=LFD0xoaUsbw@mail.gmail.com> <4E54465B.email@example.com> <CAA9xbM6nyWP6mu_bC73U-gnTCHADCHBGpc_uFsZr1QNa2MJWAg@mail.gmail.com> <4E56D3C6.firstname.lastname@example.org> <CAA9xbM79S3bGMs50hhWTyNjA6+cOYTMSggit7Y=9-tT+j=RVOQ@mail.gmail.com> <4E752253.email@example.com> <4E753D9C.firstname.lastname@example.org> <4E75D25C.email@example.com> <CAA9xbM60D9MWZ99LPujGaDM7sZ0GShVJp=nijDC-2+tEPX0p+A@mail.gmail.com> <4E865BEC.firstname.lastname@example.org> <CAA9xbM4n2rbGuv5LmZHhOC+jjctKKjf2CvwpZNjYJQXTCRx84A@mail.gmail.com> <[🔎] 4EB6A068.email@example.com>
> First off, excuse me for the long 'radio silence'. I have been very busy
> university and what time I spent on my IA-64 hardware was mostly with
No problem. I didn't know that there was an ia64 port of OpenVMS. Did
you get 3D hardware acceleration with this?
> About Linux IA-64 and accelerated graphics, has there been news to report
> as of late?
Tony just asked Linus to pull various fixes and I've noticed that the
patch I've adapted to allow AGP memory binding was in the list
W.r.t. 3D graphics, everything is now running fine on my side. Next
big step will probably be deeply testing forthcoming GNOME 3.0 in
Wheezy (http://www.0d.be/debian/debian-gnome-3.0-status.html). And
also report/fix unaligned accesses (e.g. Xorg, ioquake3).
But IMO, more serious issues surfaced. More below.
> I think it's perhaps best if I do a complete reinstall one of these days.
> much of the mentioned fixes included with the "testing" distribution? In
> other words, what would you recommend me?
Well, you simply cannot install Wheezy as-is on ia64 at this time :-(.
Indeed, I don't know if Debian Installer team is aware of this
problem, but Wheezy netinst CD-ROM simply cannot be booted: EFI fails
to load anything. I've noticed that the netinst CD-ROM partition
layout is quite different between Squeeze and Wheezy. Could this be
the root problem?
However, you can upgrade to Wheezy from a running Squeeze install.
Latest 6.0.3 netinst CD-ROM works fine (cmd64x driver issue has been
fixed). From there, simply modify /etc/apt/sources.list to point to
Wheezy and you're gone.
BUT! Don't upgrade the following packages:
- initramfs-tools: version 0.99 in Wheezy is totally broken and
generates unbootable initrd images. I've bisected the problem but
didn't get any feedback recently
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638068). Stay with
- since initramfs-tools 0.99 cannot be installed, you're stuck with
kernel < 2.6.39. I'm currently running kernel 2.6.38
(linux-image-2.6-mckinley 2.6.38+34 and linux-image-2.6.38-2-mckinley
- lastly, don't upgrade udev > 164 otherwise you'll get nearly empty
/dev and error message at startup making system takes ~3 min. to get
login prompt (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647825).
So, hold on udev, libudev0 and libgudev-1.0-0 164-3 (164-4 shoud also
work but never reached Wheezy).
Hope this helps,