[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744

Ed Maste  changed:

   What|Removed |Added

 Blocks||203349

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Build from 9.3-RELEASE to 11.0-CURRENT fails for i386 (-Wsign-compare issues with gcc)

[John Baldwin]

On Saturday, December 19, 2015 01:05:36 PM NGie Cooper wrote:
> Hi John,
>   I tried bootstrapping 9.3-RELEASE to 11.0-CURRENT with i386 and ran 
> into the -Wsign-compare issue below when running make libraries with 
> buildworld, because it’s building libkvm with gcc 4.2.1 :/… I’ve tried 
> bootstrapping with clang/clang37, but haven’t been able to yet. I’ll try 
> installing 10.2-RELEASE via freebsd-update so I can use clang instead of gcc.
> Thanks!
> -NGie

We don't actually support going from 9 to 11.  However, these constants
should probably be explicitly unsigned anyway.  I haven't tested this at
all, but something like this:

Index: head/lib/libkvm/kvm_i386.h
===
--- head/lib/libkvm/kvm_i386.h  (revision 292553)
+++ head/lib/libkvm/kvm_i386.h  (working copy)
@@ -57,8 +57,8 @@
 #defineI386_PG_PS  0x080
 #defineI386_PG_FRAME_PAE   (0x000ff000ull)
 #defineI386_PG_PS_FRAME_PAE(0x000fffe0ull)
-#defineI386_PG_FRAME   (0xf000)
-#defineI386_PG_PS_FRAME(0xffc0)
+#defineI386_PG_FRAME   (0xf000u)
+#defineI386_PG_PS_FRAME(0xffc0u)
 
 #ifdef __i386__
 _Static_assert(PAGE_SHIFT == I386_PAGE_SHIFT, "PAGE_SHIFT mismatch");



-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: No X on Dell E6540

[Carsten Kunze]

Warren Block  wrote:
> The vesa driver can be run on most systems where the newer graphics are 
> not directly supported.  See the last example here:
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html#x-c
> onfig-video-cards-file

My experience from qemu is that vesa doesn't support resolution 1920x1080.  In 
this case I couldn't use it.  I'll test it.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Aw: Re: No X on Dell E6540

[Warren Block]

On Tue, 15 Dec 2015, Carsten Kunze wrote:


Hello Michael,


It looks like that is a machine with Haswell integrated graphics.
Haswell graphics has not yet landed in CURRENT but there is a
development branch availible for testing.

https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20L
inux%203.8


there is also an additional AMD graphics card in this laptop (AMD Radeon HD 
8790M).  Is this supported by CURRENT?


The vesa driver can be run on most systems where the newer graphics are 
not directly supported.  See the last example here:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html#x-config-video-cards-file
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Panic from vesa_configure()

[Jeremie Le Hen]

On Mon, Dec 21, 2015 at 12:57 AM, Adrian Chadd  wrote:
> can you copy/paste the file:line that each of those stackframes represents?
>
> I may have an idea or two..

Sure here we go:

(kgdb) list *vesa_configure+0x270
0x80b25cd0 is in vesa_configure (/usr/src-svn/sys/dev/fb/vesa.c:827).

(kgdb) list *vga_init+0x65
0x80b286e5 is in vga_init (/usr/src-svn/sys/dev/fb/vga.c:1402).

(kgdb) list *isavga_attach+0x92
0x80b9afd2 is in isavga_attach (/usr/src-svn/sys/isa/vga_isa.c:224).

-- 
Jeremie Le Hen
j...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"