[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#395147: marked as done (linux-image-2.6.17-2-sparc64: [sparc64] No display on ultra10 creator3d)



Your message dated Sat, 13 Dec 2008 12:40:57 +0100
with message-id <20081213114057.GG3542@galadriel.inutil.org>
and subject line Re: linux-image-2.6.18-3-sparc64: framebuffer broken in 2.6 since 2.6.8
has caused the Debian Bug report #405285,
regarding linux-image-2.6.17-2-sparc64: [sparc64] No display on ultra10 creator3d
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
405285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405285
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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.


--- End Message ---
--- Begin Message ---
On Sat, Nov 29, 2008 at 02:09:22PM +1100, Tim Connors wrote:
> On Fri, 28 Nov 2008, Moritz Muehlenhoff wrote:
> 
> > On Tue, Jan 02, 2007 at 09:50:28PM +1100, Tim Connors wrote:
> > > Package: linux-image-2.6.18-3-sparc64
> > > Version: 2.6.18-8
> > > Severity: important
> > >
> > > Upon installing either of the sarge 2.6.8 or sid 2.6.18 kernels on my
> > > Sun Ultra10 with a Creator 3D card (as well as onboard ati rage 128,
> > > from my understanding), I get get a kernel that boots up without a
> > > console.  It seems to be a well known problem with a solution of
> > > appending "video=atyfb:off" to silo; perhaps this should be done by
> > > default?
> > >
> > > Furthermore (probably related?), apparently the ffb driver is
> > > completely dead anyway from 2.6.8, and as such has been removed from
> > > the kernel: http://lkml.org/lkml/2005/1/5/33
> > >
> > > If they are the same problems, is there any chance of getting this
> > > looked into?  Presumably not being able to modprobe ffb (because it
> > > doesn't exist) is the reason why we also don't have working DRM under
> > > Xorg?
> >
> > Does this error still occur with more recent kernel versions?
> >
> > If you're running Etch, could you try to reproduce this bug
> > with the 2.6.24 based kernel added in 4.0r4?
> > http://packages.qa.debian.org/l/linux-2.6.24.html
> 
> That machine has been decommisioned, so I am unable to test at this time.

Thanks, closing the bug then.

Cheers,
        Moritz


--- End Message ---

Reply to: