Bug#395147: linux-image-2.6.17-2-sparc64: [sparc64] No display on ultra10 creator3d
Package: linux-image-2.6.17-2-sparc64
Version: 2.6.17-9
Severity: important
When booting 2.6.17 on my ultra-10 with a creator3d (upa) graphics
card, no output is seen on the monitor past the "Booting Linux..."
message. The system does boot and is usable via ssh.
This did not happen with the default 2.4 kernel under sarge, or after
upgrading to etch before installing a 2.6 kernel.
There is no usable output on the onboard mach64 vga output either. My
19" vga monitor sees no signal, even with the creator card removed
from the system.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: sparc (sparc64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-sparc64
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Versions of packages linux-image-2.6.17-2-sparc64 depends on:
ii initramfs-tools [linux-initra 0.83 tools for generating an initramfs
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
linux-image-2.6.17-2-sparc64 recommends no packages.
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en_GB:en",
LC_ALL = (unset),
LANG = "en_US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.17-2-sparc64/postinst/old-system-map-link-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/postinst/kimage-is-a-directory:
linux-image-2.6.17-2-sparc64/preinst/abort-install-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/preinst/overwriting-modules-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/postinst/bootloader-error-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/preinst/lilo-has-ramdisk:
linux-image-2.6.17-2-sparc64/postinst/old-initrd-link-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/postinst/create-kimage-link-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/postinst/bootloader-test-error-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/prerm/would-invalidate-boot-loader-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/preinst/abort-overwrite-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/preinst/already-running-this-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/prerm/removing-running-kernel-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/preinst/lilo-initrd-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/preinst/initrd-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/preinst/elilo-initrd-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/preinst/failed-to-move-modules-2.6.17-2-sparc64:
linux-image-2.6.17-2-sparc64/postinst/old-dir-initrd-link-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/postinst/depmod-error-initrd-2.6.17-2-sparc64: false
linux-image-2.6.17-2-sparc64/preinst/bootloader-initrd-2.6.17-2-sparc64: true
linux-image-2.6.17-2-sparc64/postinst/depmod-error-2.6.17-2-sparc64: false
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
Reply to: