On 10.12.2013 00:49, Aleksandr Rybalko wrote:
It is not fatal in syscons case. We decide to mark this message as
error, to get more attention when run with newcons. For newcons it
indicate that vt will not be able to draw into framebuffer(memory
region which contain image you see on display).
Jean-Sébastien Pédron jean-sebastien.ped...@dumbbell.fr написав(ла):
On 10.12.2013 00:49, Aleksandr Rybalko wrote:
It is not fatal in syscons case. We decide to mark this message as
error, to get more attention when run with newcons. For newcons it
indicate that vt will not be able to draw into
On Mon, 9 Dec 2013 10:59:14 +0200
Markiyan Kushnir markiyan.kush...@gmail.com wrote:
Hello,
I'm on rev. 259102 and hitting drm not being able to attach to fbd
device at X startup (X freezing).
Attaching /var/log/messages, pciconf output and kern.conftxt. Please
let me know if there is
2013/12/9 Aleksandr Rybalko r...@ddteam.net:
On Mon, 9 Dec 2013 10:59:14 +0200
Markiyan Kushnir markiyan.kush...@gmail.com wrote:
Hello,
I'm on rev. 259102 and hitting drm not being able to attach to fbd
device at X startup (X freezing).
Attaching /var/log/messages, pciconf output and
On 09.12.2013 09:59, Markiyan Kushnir wrote:
I'm on rev. 259102 and hitting drm not being able to attach to fbd
device at X startup (X freezing).
I believe those issues are unrelated: I have the Failed to attach fbd
device because I'm using syscons, however, X.Org works perfectly well.
From
On Sun, 8 Dec 2013 16:36:10 +0100
Marc UBM ubm.free...@googlemail.com wrote:
Hiho! :-)
Thanks a lot for working on this!
As soon as X is started, things work fine. Before that (as soon as vt
is initialized after the boot menu), output on all ttys is flickering,
resolution is at 640x480
On Mon, 9 Dec 2013 22:49:33 +0200
Aleksandr Rybalko r...@freebsd.org wrote:
Hi Marc,
yeah I seen same at the test board
Intel Ironlake (D) SVGA controller
vgapci0@pci0:0:2:0: class=0x03 card=0x00368086 chip=0x00428086
First thought was about firmware(BIOS) bug related to VGA
ok, now I'm at r259128 (both world and kernel), and ports at r335849
all rebuilt from scratch, the issue's gone away. Right before rebuild,
it was the window manager (I would guess) that must be freeezing (no
mouse, no feedback to keyboard, however clean shutdown of X from
within external ssh
On Mon, 9 Dec 2013 19:48:44 +0200
Markiyan Kushnir markiyan.kush...@gmail.com wrote:
2013/12/9 Aleksandr Rybalko r...@ddteam.net:
On Mon, 9 Dec 2013 10:59:14 +0200
Markiyan Kushnir markiyan.kush...@gmail.com wrote:
Hello,
I'm on rev. 259102 and hitting drm not being able to attach to
Hiho! :-)
Thanks a lot for working on this!
As soon as X is started, things work fine. Before that (as soon as vt
is initialized after the boot menu), output on all ttys is flickering,
resolution is at 640x480 (guessing here) and changing anything via
vidcontrol fails with inappropriate ioctl
Hiho! :-)
Thanks a lot for working on this!
As soon as X is started, things work fine. Before that (as soon as vt
is initialized after the boot menu), output on all ttys is flickering,
resolution is at 640x480 (guessing here) and changing anything via
vidcontrol fails with inappropriate ioctl
11 matches
Mail list logo
