On Tue, Mar 30, 2004 at 09:22:11PM +0200, Thomas Poindessous wrote: > can you try with disabling framebuffer : > > debian-installer/framebuffer=false > > If it doesn't help, it will need some debugging on bterm ...
I found out how to pass boot parameters to the kernel -- or at least, I think I did. When I added this one, it produced no visible difference in the results. I still get a Frame Buffer after the first few seconds of booting (Tux with the PA-RISC log on his stomach, and an fb0: line in the kernel's output). Then I get the same "Segmentation fault" lines at the end. Here's how I added the boot parameters: 1) Hit ESC at power-on time to get to the BOOT_ADMIN prompt. 2) At the BOOT_ADMIN prompt, type "boot scsi.2.0 isl" to get to the list of boot parameters. 3) Edit parameter number 0 (or any of them, actually) and add " debian-installer/framebuffer=false" (with a space) to it. This adds a new parameter to the list. 4) When the new list is displayed, press Backspace, b, Enter to boot. The list seems to be the correct one, since it includes "DEBCONF_PRIORITY=high" by default. (Changing that to low made no difference, either.) P.S.: Whatever you do, don't boot with "video=stifb:off", because that *does* disable the FB in the kernel, and the result is an endless scrolling of errors full of numbers that I can't read (because the whole screen jerks too much), and the only way to stop it is to pull the power cord. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
