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

Bug#485510: marked as done ([sparc] Enabling FRAMEBUFFER_CONSOLE_DETECT_PRIMARY)

Your message dated Wed, 10 Jul 2013 20:09:13 +0200
with message-id <20130710180913.GB6890@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #485510,
regarding [sparc] Enabling FRAMEBUFFER_CONSOLE_DETECT_PRIMARY
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.)


-- 
485510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485510
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.25-4
Severity: wishlist

Sparc systems by default use the framebuffer and often have two video 
cards, e.g. for my Ultra 10: a "standard" ATI and a "professional" 
Creator 3D card.

Problem always has been detecting which card was "active". Getting it 
right frequently required users disabling one or the other.

IIUC the FRAMEBUFFER_CONSOLE_DETECT_PRIMARY config option was designed to 
solve this problem and take the correct framebuffer based on firmware 
settings.
However, I see that in current kernels this option is not enabled. Please 
consider enabling it, at least for Sparc but possibly for other 
architectures as well.

Cheers,
FJP

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: