On 14/02/2014 13:04, Aleksandr Rybalko wrote:
> On 14 лютого 2014 р. 14:31:45 GMT+02:00, Robert Millan
> wrote:
>> On 14/02/2014 11:00, Aleksandr Rybalko wrote:
> Strange. What I get now is black screen during 3 seconds every
>> time I switch VT.
>>> 3 seconds is for VirtualBox, right?
>>
>>
On 14 лютого 2014 р. 14:31:45 GMT+02:00, Robert Millan wrote:
>On 14/02/2014 11:00, Aleksandr Rybalko wrote:
>>> > Strange. What I get now is black screen during 3 seconds every
>time I switch VT.
>> 3 seconds is for VirtualBox, right?
>
>No, real hardware (Radeon HD 2400 PRO).
>
>This black scree
On 14/02/2014 11:00, Aleksandr Rybalko wrote:
>> > Strange. What I get now is black screen during 3 seconds every time I
>> > switch VT.
> 3 seconds is for VirtualBox, right?
No, real hardware (Radeon HD 2400 PRO).
This black screen is not just black pixels, it looks a lot like the usual "mode
On Fri, 14 Feb 2014 00:01:56 +
Robert Millan wrote:
> On 12/02/2014 18:36, Ed Maste wrote:
> > On 12 February 2014 09:05, Robert Millan wrote:
> >> There's a small glitch during VT switch: immediately after pressing the
> >> keys, screen is redrawn, but where you'd normally see the login pro
On 12/02/2014 18:36, Ed Maste wrote:
> On 12 February 2014 09:05, Robert Millan wrote:
>> There's a small glitch during VT switch: immediately after pressing the
>> keys, screen is redrawn, but where you'd normally see the login prompt,
>> blurry characers are drawn. After a fraction of a second,
On 12.02.2014 14:59, Robert Millan wrote:
> On 09/02/2014 12:56, Markus Koschany wrote:
>> Switching between virtual terminals and X works flawlessly after I
>> loaded the intel drivers manually.
>
> What about switching from one VT to another? (no X involved)
Works perfectly.
signature.asc
D
On 12 February 2014 09:05, Robert Millan wrote:
> There's a small glitch during VT switch: immediately after pressing the
> keys, screen is redrawn, but where you'd normally see the login prompt,
> blurry characers are drawn. After a fraction of a second, these are replaced
> with proper glyphs. S
Processing control commands:
> retitle -1 VGA Newcons is awfully slow
Bug #738188 [kfreebsd-image-11.0-0-amd64] VESA Newcons is awfully slow
Changed Bug title to 'VGA Newcons is awfully slow' from 'VESA Newcons is
awfully slow'
--
738188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738188
Control: retitle -1 VGA Newcons is awfully slow
Hi Ed,
On 09/02/2014 19:47, Ed Maste wrote:
> On what hardware (or VM) do you experience this? On my Thinkpad X220
> the console is acceptably performant in both VGA-mode (at boot) and
> i915 (after starting X), with a FreeBSD-CURRENT kernel from t
On 09/02/2014 12:56, Markus Koschany wrote:
> Switching between virtual terminals and X works flawlessly after I
> loaded the intel drivers manually.
What about switching from one VT to another? (no X involved)
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
w
On 8 February 2014 08:49, Robert Millan wrote:
> Package: kfreebsd-image-11.0-0-amd64
> Version: 11.0~svn260666-1
> Severity: important
>
> With Newcons it becomes practically impossible to use the console. When
> using the default VESA driver, both VT switching and text scrolling
> become terribl
On Sat, 08. Feb 13:49 Robert Millan wrote:
[...]
> Has anyone else tried Newcons? It is currently the default in kfreebsd-11
> packages. Do you also experience this problem?
I tried it with kfreebsd-11 on my lenovo X200 laptop with Intel GM45
integrated graphic chipset.
Switching between virtual
Package: kfreebsd-image-11.0-0-amd64
Version: 11.0~svn260666-1
Severity: important
With Newcons it becomes practically impossible to use the console. When
using the default VESA driver, both VT switching and text scrolling
become terribly slow. Either of these operations takes almost 1 s!
Newcons
13 matches
Mail list logo