[Bug 437871] [NEW] (regression) uvesafb needs missing /dev/mem, /dev/zero

[a7x]

Public bug reported:

Binary package hint: initramfs-tools

initramfs-tools version 0.92bubuntu50 removed mknods for /dev/mem and
/dev/zero, but they are not created by the time the framebuffer script
runs.  uvesafb (actually v86d) requires these devices (see bug #285970).

To verify, I modified /usr/share/initramfs-tools/scripts/init-
top/framebuffer as follows:

--- /usr/share/initramfs-tools/scripts/init-top/framebuffer~	2009-09-22 21:47:10.000000000 -0400
+++ /usr/share/initramfs-tools/scripts/init-top/framebuffer	2009-09-27 18:04:57.936614976 -0400
@@ -81,7 +81,17 @@
 esac
 
 if [ -n "${FB}" ]; then
+	echo "checking if /dev/mem and /dev/zero are present" >&2
+	for i in /dev/mem /dev/zero; do
+		if [ -e $i ]; then
+			echo "  $i is present" >&2
+		else
+			echo "  $i MISSING" >&2
+		fi
+	done
+	echo "about to run modprobe -q ${FB} ${OPTS}" >&2
 	MODPROBE_OPTIONS=-q modprobe ${FB} ${OPTS}
+	echo "done running modprobe -q ${FB} ${OPTS}" >&2
 else
 	# If we have no graphics devices, wait for udev to settle;
 	# if we still don't have a graphics device, load vesafb

The following is the output I saw after running sudo update-initramfs -u
and rebooting:

checking if /dev/mem and /dev/zero are present
  /dev/mem MISSING
  /dev/zero MISSING
about to run modprobe -q uvesafb mode_option=1400x1050
[    1.474357] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[    1.474408] uvesafb: vbe_init() failed with -22
done running modprobe -q uvesafb mode_option=1400x1050

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New

-- 
(regression) uvesafb needs missing /dev/mem, /dev/zero
https://bugs.launchpad.net/bugs/437871
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to initramfs-tools in ubuntu.