Bug#216048: linux-kernel-di: Cycles on vesafb.o module loading

[stappers@stappers.nl (Geert Stappers)]

On Thu, Oct 16, 2003 at 07:19:43AM +0200, Christian Perrier wrote:
> 
> While trying the daily-generated netinst image grabbed from gluck on Oct
> 15th (dated Oct 15th, 00:16), the following happens :
> 
> info: Trying to  nable linux fram buffer
> Using /lib/modul s/2.4.22-1-386/k rnel/drivers/video/vesafb.o
> modprobe: failed to load module vesafb
> info: Trying to  nable linux fram buffer
> Using /lib/modul s/2.4.22-1-386/k rnel/drivers/video/vesafb.o
> modprobe: failed to load module vesafb
> info: Trying to  nable linux fram buffer
> Using /lib/modul s/2.4.22-1-386/k rnel/drivers/video/vesafb.o
> modprobe: failed to load module vesafb
> 

This bahaviour was also encountered by me.
IMO it was due the main-menu issues.  ( main-menu is working ATM )

The modprobe for vesafb.o is done in 
$ cat debian-installer/rootskel/src/lib/debian-installer.d/S33framebuffer-module-linux-i386
echo "info: Trying to enable linux framebuffer."
modprobe -q vesafb || modprobe -q vga16fb || true
 

Helping to avoid bugreports on the wrong components in d-i,
I recomment this (unverified) patch:
diff -u -r1.33 debian-installer
--- rootskel/src/sbin/debian-installer  13 Oct 2003 14:36:21 -0000      1.33
+++ rootskel/src/sbin/debian-installer  16 Oct 2003 08:12:41 -0000
@@ -4,6 +4,7 @@
  
 for script in /lib/debian-installer.d/S[0-9][0-9]*; do
     . $script
+    echo back from ${script} in ${0}
 done
  
 # Allow error messages to be seen if we're in a crash-loop.


HTH


Geert Stappers