Package: v86d
Version: 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4
Severity: wishlist
I compile my own kernels, and rely on 'uvesafb' to allow me to use 60
Hz modes with my monitor that are not official VESA modes.
I haven't updated my kernels since September because of a kernel bug
that prevented any 2.6.2[67] kernel from working on 2 of my 3
machines. After seeking help on LKML during August, fixes to the PCI
initialization routines in the kernel were developed, but were too
late in the process to be included in 2.6.27... but now the 2.6.28
kernel is nearing release, and 2.6.28-rc3 is the first kernel that
runs on all of my machines (without hanging during boot) since kernel
2.6.25.
I am currently building kernels for all of my machines, but I always
build 'klibc' and 'v86d' from source -- as per the recommendations of
the UVESA FB author at
http://dev.gentoo.org/~spock/projects/uvesafb/
Just now, I noticed that 'apt-cache policy v86d' gives me this:
v86d:
Installed: 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4
Candidate: 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4
Version table:
*** 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4 0
100 /var/lib/dpkg/status
0.1.5.2-1 0
990 ftp://ftp.uwsg.indiana.edu unstable/main Packages
which indicates that the last version of 'v86d' available as a Debian
package is still 0.1.5.2! The UVESA FB website lists the lastest
version as 0.1.9!!
I've never had a problem with any version of 'v86d' -- though I always
home brew mine and never use the precompiled Debian binaries -- so I
consider this a wishlist request. As you can see from the 'apt-cache'
output above, the last time I built 'v86d' I hacked together DEBs by
using the 'debian' directory from the 0.1.5.2 sources with the "Spock"
upstream version of 0.1.6. I am about to try the same hack again with
0.1.9, so we'll see how that goes.
Also, I requested before that the scripts used to produce the DEBs
should include the 'misc/initramfs' file in some shared directory in
the filesystem, so that later kernel compilations could continue to
use the currently-installed 'v86d' package via the CONFIG_INITRAMFS_
SOURCE kernel option. The UVESA FB author seems to have standardized
a location for packages to install that file (see step 6 under
"uvesafb::installation instructions" at the website mentioned above):
/usr/share/v86d/initramfs
It should be simple to copy this text file to the proper location in
'debian/v86d-<version>/usr/share/v86d' when the DEB is being created.
Thanks,
Dave W.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.27-rc5+fac8f1e4-080918.desktop.uvesafb (SMP w/2 CPU cores;
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
v86d depends on no packages.
Versions of packages v86d recommends:
ii initramfs-tools 0.92l tools for generating an initramfs
v86d suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
