tags 559364 + pending
Bug #559364 [kfreebsd-image-8.0-1-686] regression: console text is red
Added tag(s) pending.
I'm not sure if this is the same issue, but I get orange text on
startup with the 8.1 kernel:
http://v.nix.is/~avar/fbsd-boot.png
It is, the "tput op" have not done what have
On Sat, Aug 7, 2010 at 11:24, Debian Bug Tracking System
wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> tags 559364 + pending
> Bug #559364 [kfreebsd-image-8.0-1-686] regression: console text is red
> Added tag(s) pending.
I'm not sure if this is the same issue, but I get orange t
Processing commands for cont...@bugs.debian.org:
> tags 559364 + pending
Bug #559364 [kfreebsd-image-8.0-1-686] regression: console text is red
Added tag(s) pending.
> --
Stopping processing here.
Please contact me if you need assistance.
--
559364: http://bugs.debian.org/cgi-bin/bugreport.cgi?b
Given squeeze is frozen, we should now go the conservative way, that is
reverting back to cons25. We will try to have another way to get
debian-installer display UTF-8 (maybe defaulting to the graphical
installer, not yet tested on GNU/kFreeBSD), and it is possible to do
that far later in the free
On Tue, Aug 03, 2010 at 10:38:25AM +0200, Petr Salinger wrote:
> I dig into. The "tput op" does not do what is expected.
>
> The our 8.x kernel series have added following options:
>
> # UTF-8 console support
> options VESA
> options SC_PIXEL_MODE # add
On Tue, Aug 03, 2010 at 01:05:39PM -0400, Tuco wrote:
> On 8/2/10, Aurelien Jarno wrote:
> > I confirm the issue here, so it seems we have to revert the options in
> > the kernel. That's a pitty because the goal was to use the UTF-8
> > terminal to be able to have non-english language in debian-in
On 8/2/10, Aurelien Jarno wrote:
> I confirm the issue here, so it seems we have to revert the options in
> the kernel. That's a pitty because the goal was to use the UTF-8
> terminal to be able to have non-english language in debian-installer.
Maybe this sounds crazy, but what if you put this in
I dig into. The "tput op" does not do what is expected.
The our 8.x kernel series have added following options:
# UTF-8 console support
options VESA
options SC_PIXEL_MODE # add support for the raster text mode
options TEKEN_UTF8 # UTF-8 output handling
options
On Sat, Jul 31, 2010 at 04:41:39PM +0200, Guillem Jover wrote:
> Hi!
>
> On Tue, 2010-07-27 at 20:42:04 +0200, Aurelien Jarno wrote:
> > On Tue, Jul 27, 2010 at 07:17:18PM +0200, Petr Salinger wrote:
> > > I dig into. The "tput op" does not do what is expected.
> > >
> > > The our 8.x kernel seri
Hi!
On Tue, 2010-07-27 at 20:42:04 +0200, Aurelien Jarno wrote:
> On Tue, Jul 27, 2010 at 07:17:18PM +0200, Petr Salinger wrote:
> > I dig into. The "tput op" does not do what is expected.
> >
> > The our 8.x kernel series have added following options:
> >
> > # UTF-8 console support
> > options
On Tue, Jul 27, 2010 at 07:17:18PM +0200, Petr Salinger wrote:
> Hi,
Hi,
> I dig into. The "tput op" does not do what is expected.
>
> The our 8.x kernel series have added following options:
>
> # UTF-8 console support
> options VESA
> options SC_PIXEL_MODE # add support for th
Hi,
I dig into. The "tput op" does not do what is expected.
The our 8.x kernel series have added following options:
# UTF-8 console support
options VESA
options SC_PIXEL_MODE # add support for the raster text mode
options TEKEN_UTF8 # UTF-8 output handling
options
Cyril Brulebois (10/12/2009):
> I'll have to retry later on.
So first, to help debugging, “dmesg -a” is our friend.
Now, I've tweaked the checkroot.sh init script (see attached patch)
and I'm getting this:
| Activating swap...
| log_action_end_msg 139
which shows that we're taking the “then” br
On Thu, Dec 10, 2009 at 04:33:20PM +0100, Cyril Brulebois wrote:
> > This is actually most probably due to an initscript. Does the boot
> > start in red, or does it switches to red at some point?
The latter.
> on a kfreebsd-amd64 machine, I can reproduce this. Booting with 7.2 is
> alright while
Aurelien Jarno (04/12/2009):
> This is actually most probably due to an initscript. Does the boot
> start in red, or does it switches to red at some point?
Hi,
on a kfreebsd-amd64 machine, I can reproduce this. Booting with 7.2 is
alright while booting with 8.0 triggers this bug. It appears the
The kernel messages are still bright yellow. Then the init scripts turn
green, then red.
A.
--
We should act only in such away that if everyone
else acted as we do, we would accept the results.
- Kant
signature.asc
Description: Digital signature
On Thu, Dec 03, 2009 at 05:03:28PM -0500, anar...@anarcat.ath.cx wrote:
> Package: kfreebsd-image-8.0-1-686
> Version: 8.0-1
> Severity: minor
>
> After installing this package and rebooting, the console text is all red
> instead of the regular gray. 7.2 didn't have that behavior.
>
> Not a big d
Package: kfreebsd-image-8.0-1-686
Version: 8.0-1
Severity: minor
After installing this package and rebooting, the console text is all red
instead of the regular gray. 7.2 didn't have that behavior.
Not a big deal, but just something that should be mentionned I guess.
-- System Information:
Debia
18 matches
Mail list logo
