I can confirm that I should have paid greater attention to detail. I apologize to any I may have inconvenienced by communicating BAD information. On another hunch last night, I checked /etc/apt/sources.list to confirm that I was indeed using amd64, and not i386. To my horror and deep embarrassment, i386 was installed. i386 never had a problem with my hardware configuration, only amd64. I apparently burned the i386 ISO to disk twice, thinking one of them was amd64. So I went back and retrieved the correct amd64 ISO which is dated 16 October.
To make amends for my error, I performed deeper testing of both ISO architectures, and resolved the usplash problem with amd64 on the Inspiron 1420. The solution is similar to orange2k's:
1024x748 16-bit resolution set using startupmanager
fbcon and vesafb added to /etc/initramfs-tools/modules (vga16fb not needed in my case)
"blacklist vesafb" commented out in /etc/modprobe.d/blacklist-framebuffer
Rene,
I can confirm that I should have paid greater attention to detail. I apologize to any I may have inconvenienced by communicating BAD information. On another hunch last night, I checked /etc/apt/ sources. list to confirm that I was indeed using amd64, and not i386. To my horror and deep embarrassment, i386 was installed. i386 never had a problem with my hardware configuration, only amd64. I apparently burned the i386 ISO to disk twice, thinking one of them was amd64. So I went back and retrieved the correct amd64 ISO which is dated 16 October.
To make amends for my error, I performed deeper testing of both ISO architectures, and resolved the usplash problem with amd64 on the Inspiron 1420. The solution is similar to orange2k's:
1024x748 16-bit resolution set using startupmanager tools/modules (vga16fb not needed in my case) d/blacklist- framebuffer
fbcon and vesafb added to /etc/initramfs-
"blacklist vesafb" commented out in /etc/modprobe.
Harvey