Re: STABLE-11/amd64 and X

2017-01-05 Thread Schaich Alonso 
On Thu, Jan 5, 2017, at 12:12, Jonathan Chen wrote:
> Hi,
> 
> I've just moved onto STABLE-11/amd64 today, and after rebuilding all
> my ports, I find that switching from X back to the console using
> Ctrl-Alt-F1 results in a screen filled with random coloured blocks.
> Does anyone here know how I can get a decent console?
> 
> Cheers.

Hi,

This is likely caused by changes in vt(4) introduced in FreeBSD-11. Most
importantly, the new default is to use kernel mode setting which works
only limitedly well with nvidia's drivers. The default vt mode of
FreeBSD-10 can be restored by setting

hw.vga.textmode=1

in /boot/loader.conf. 

Yours,
Alonso
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildwotrld can not find zlib,h

2016-10-18 Thread Schaich Alonso 
On Fri, 14 Oct 2016 11:06:55 -0700
Kevin Oberman  wrote:

> On Fri, Oct 14, 2016 at 6:10 AM, Dmitry Luhtionov  > wrote:
> 
> > c++  -O2 -pipe
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/
> > include
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/
> > include
> > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> > -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing
> > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -MD -MF.depend.Compression.o
> > -MTCompression.o -Qunused-arguments
> > -I/usr/obj/usr/src/tmp/legacy/usr/include  -std=c++11 -fno-exceptions
> > -fno-rtti -stdlib=libc++ -Wno-c++11-extensions  -c
> > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > Compression.cpp
> > -o Compression.o
> > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > Compression.cpp:21:10:
> > fatal error: 'zlib.h' file not found
> > #include 
> >  ^
> > 1 error generated.
> >
> 
> Very odd. /usr/include/zlib.h is and long has been a standard component of
> FreeBSD and should be present on your system. Can you confirm its absence?
> Anything that could be in /etc/src.conf that might trigger this? (I can't
> see anything obvious, but src.conf(5) is very long.)
> 
> I'm also not sure whether, at this point in the build, you should be using
> the system's include files or those in /usr/obj/usr/src/tmp/usr/include/ or
> /usr/src/lib/libz/zlib.h, which is what should be copied to
> /usr/obj/usr/src/tmp/usr/include. Normally the system's files are not used
> during the build.
> 
> Have you tried completely removing /usr/obj (rm -r /usr/obj/*) before
> starting the build with -DNO_CLEAN?
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Hi,

I'm having an issue with libarchive that might or might not be related:

> [...]
> (cd /usr/src/lib/libarchive/tests &&  DEPENDFILE=.depend.libarchive_test  
> NO_SUBDIR=1 make -f /usr/src/lib/libarchive/tests/Makefile _RECURSING_PROGS=t 
>  PROG=libarchive_test )
> cc -O2 -pipe -I/usr/src/lib/libarchive 
> -I/usr/obj/usr/src/lib/libarchive/tests 
> -I/usr/src/contrib/libarchive/libarchive 
> -I/usr/src/contrib/libarchive/test_utils -DHAVE_LIBLZMA=1 -DHAVE_LZMA_H=1   
> -g -MD  -MF.depend.libarchive_test.main.o -MTmain.o -std=gnu99 
> -fstack-protector-strong-Qunused-arguments  -c 
> /usr/src/contrib/libarchive/libarchive/test/main.c -o main.o
> /usr/src/contrib/libarchive/libarchive/test/main.c:2400:10: fatal error: 
> 'list.h' file not found
> #include "list.h"
>  ^
> 1 error generated.
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/src/lib/libarchive/tests
> *** Error code 1
> [...]

list.h is perfectly there, but it's in /usr/src/lib/libarchive/tests rather 
than /usr/obj/usr/src/lib/libarchive/tests (the second -I is wrong), so either 
some copy-to-builddir target was skipped or the build process should include 
the source path instead of the build path.

I removed anything from /usr/obj/ and also commented-away anything I had in 
make.conf and src.conf prior to attempting to compile it (11-STABLE r307550).

Alonso


pgp6cLK2i33NF.pgp
Description: PGP signature

Re: Stuck processes in unkillable (STOP) state, listen queue overflow

2015-10-29 Thread Schaich Alonso 
On Thu, Oct 29, 2015, at 16:46, Zara Kanaeva wrote:
> Hello Дмитрий,
> 
> thank you very much for your message.
> 
> First of all: I like FreeBSD (the installation logic, the good  
> documentation etc.), this is why I use FreeBSD as Server OS. But in my  
> case I must desagree your strong theoretical probability  
> consideration. In my case I have one machine (7 years old), that had  
> 1-2 spontaneous rebootes in a year. In my case I got a lot of "already  
> in queue awaiting acceptance"-Errors and the machine rebootes  
> immediately after this.
> 
> I will get soon a new replacement for this old machine with at least  
> 32 GB RAM and (of course) new power supply. So I will see if my  
> problem (perhaps it is only my problem) still persist.
> 
> Greetings, Z. Kanaeva.
> 

I've had resetting network interfaces combined with the queue overflow
warnings on 3 different machines with 5 different NICs and 3 differnt
PSUs.

It disappeared when I updated to FreeBSD-10 two years ago, so I assumed
the cause of this to have either been fixed or workarounded.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: RELENG_9 build error

2013-08-26 Thread Schaich Alonso 
On Mon, 26 Aug 2013 15:07:42 -0400
Mike Tancsa m...@sentex.net wrote:

 
 Does anyone have any idea how to correct this issue ?  Already blew away
 /usr/src and /usr/obj in case something got corrupted.
 
 

Taking it you mean stable/9 by RELENG_9, it can be ``fixed'' by updating your
sources, to any revision more recent than r254669 (which reverted the breaking
commit)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FBSD 9.2 RC crashes running as virtualbox host

2013-08-17 Thread Schaich Alonso 
On Sat, 17 Aug 2013 00:38:48 -0700
Kevin Oberman rkober...@gmail.com wrote:

 On Fri, Aug 16, 2013 at 11:34 PM, Kevin Oberman rkober...@gmail.com wrote:
 
  On Fri, Aug 16, 2013 at 10:44 PM, Kevin Oberman
  rkober...@gmail.comwrote:
 
  On Fri, Aug 16, 2013 at 2:01 PM, Warren Block wbl...@wonkity.com wrote:
 
  On Fri, 16 Aug 2013, Thomas Zenker wrote:
 
   On 08/16/13 15:41, Mikhail Tsatsenko wrote:
 
  2013/8/16 Thomas Zenker t...@zenker.tk:
 
  Hi,
 
  after updating my freebsd amd64 box from 9.1 (r250841) to 9.2-RC
  (r254276) virtualbox crashes the machine. Seconds after starting VBOX
 
  After starting VBOX gui or guest machine? If first, try to rebuild
  userland portion of vbox too.
 
 
  After starting a virtual guest machine in the GUI or directly
  from cli
  leads to the crash. The userland has been rebuild w/ 9.2 also. The same
  binaries of the userland portion built with 9.2 work w/o problems in
  9.1.
 
 
  Updated to 9.2-PRERELEASE #0 r254408 amd64 today, rebuilt and reloaded
  the VirtualBox kernel module, and just started a couple of guests from
  the GUI with no problems.
 
 
  Updated to r254416 today.Two crashes when I tried starting VirtualBox
  4.16_2. I have both dumps and they ere very different. The first was a
  spin lock held too long and the second was a general protection fault.
  Both occurred when I attempted to start a saved Windows 7 VM.
 
  FreeBSD rogue.local 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254416M:
  Fri Aug 16 11:27:20 PDT 2013
  root@rogue.local:/usr/obj/usr/src/sys/GENERIC amd64
 
  #0  doadump (textdump=value optimized out) at pcpu.h:234
  234 pcpu.h: No such file or directory.
  in pcpu.h
  (kgdb) #0  doadump (textdump=value optimized out) at pcpu.h:234
  #1  0x80915c66 in kern_reboot (howto=260)
  at /usr/src/sys/kern/kern_shutdown.c:449
  #2  0x80916167 in panic (fmt=0x1 Address 0x1 out of bounds)
  at /usr/src/sys/kern/kern_shutdown.c:637
  #3  0x80cfae80 in trap_fatal (frame=0x9, eva=value optimized
  out)
  at /usr/src/sys/amd64/amd64/trap.c:879
  #4  0x80cfb691 in trap (frame=0xff8124900830)
  at /usr/src/sys/amd64/amd64/trap.c:605
  #5  0x80ce4ac3 in calltrap ()
  at /usr/src/sys/amd64/amd64/exception.S:232
  #6  0x80b86015 in vm_map_entry_splay (addr=984915968,
  root=0xfe002c9af200) at /usr/src/sys/vm/vm_map.c:832
  #7  0x80b870f7 in vm_map_lookup_entry (map=0xfe007535b640,
  address=984915968, entry=0xff8124900970)
  at /usr/src/sys/vm/vm_map.c:1080
  #8  0x80b8a5cc in vm_map_madvise (map=0xfe007535b640,
 start=984915968, end=985440256, behav=5) at
  /usr/src/sys/vm/vm_map.c:2050
  #9  0x80b8d9e3 in sys_madvise (td=0xfe000549e920,
  uap=value optimized out) at /usr/src/sys/vm/vm_mmap.c:760
  #10 0x80cfa62a in amd64_syscall (td=0xfe000549e920, traced=0)
  at subr_syscall.c:135
  #11 0x80ce4da7 in Xfast_syscall ()
  at /usr/src/sys/amd64/amd64/exception.S:391
  #12 0x2ce13dcc in ?? ()
  Previous frame inner to this frame (corrupt stack?)
 
   I can make the cores and text dumps available. kmod was rebuilt after
  the upgrade.
 
 
  Just confirmed that 254050 works fine. Trying 354162 and will continue
  binary hunt till I find it.
 
  I am now up to 254270, at the point of the original failure report. I now
 suspect I may have botched the kmod re-install on my original failure. I am
 calling it quits of the night now, but will finish tests tomorrow morning.
 The updates are pretty few and far between between 270 and the present.

Hi,

I am using r254095 and my system also resets when trying to start a Guest in
VirtualBox, so the breaking update is probably between 254050 and 254270.

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FBSD 9.2 RC crashes running as virtualbox host

2013-08-17 Thread Schaich Alonso 
On Sat, 17 Aug 2013 10:00:38 +0200
Schaich Alonso alonsoscha...@fastmail.fm wrote:

 On Sat, 17 Aug 2013 00:38:48 -0700
 Kevin Oberman rkober...@gmail.com wrote:
 
  On Fri, Aug 16, 2013 at 11:34 PM, Kevin Oberman rkober...@gmail.com
  wrote:
  
   On Fri, Aug 16, 2013 at 10:44 PM, Kevin Oberman
   rkober...@gmail.comwrote:
  
   On Fri, Aug 16, 2013 at 2:01 PM, Warren Block wbl...@wonkity.com
   wrote:
  
   On Fri, 16 Aug 2013, Thomas Zenker wrote:
  
On 08/16/13 15:41, Mikhail Tsatsenko wrote:
  
   2013/8/16 Thomas Zenker t...@zenker.tk:
  
   Hi,
  
   after updating my freebsd amd64 box from 9.1 (r250841) to 9.2-RC
   (r254276) virtualbox crashes the machine. Seconds after starting
   VBOX
  
   After starting VBOX gui or guest machine? If first, try to rebuild
   userland portion of vbox too.
  
  
   After starting a virtual guest machine in the GUI or directly
   from cli
   leads to the crash. The userland has been rebuild w/ 9.2 also. The
   same binaries of the userland portion built with 9.2 work w/o
   problems in 9.1.
  
  
   Updated to 9.2-PRERELEASE #0 r254408 amd64 today, rebuilt and reloaded
   the VirtualBox kernel module, and just started a couple of guests from
   the GUI with no problems.
  
  
   Updated to r254416 today.Two crashes when I tried starting VirtualBox
   4.16_2. I have both dumps and they ere very different. The first was a
   spin lock held too long and the second was a general protection
   fault. Both occurred when I attempted to start a saved Windows 7 VM.
  
   FreeBSD rogue.local 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254416M:
   Fri Aug 16 11:27:20 PDT 2013
   root@rogue.local:/usr/obj/usr/src/sys/GENERIC amd64
  
   #0  doadump (textdump=value optimized out) at pcpu.h:234
   234 pcpu.h: No such file or directory.
   in pcpu.h
   (kgdb) #0  doadump (textdump=value optimized out) at pcpu.h:234
   #1  0x80915c66 in kern_reboot (howto=260)
   at /usr/src/sys/kern/kern_shutdown.c:449
   #2  0x80916167 in panic (fmt=0x1 Address 0x1 out of bounds)
   at /usr/src/sys/kern/kern_shutdown.c:637
   #3  0x80cfae80 in trap_fatal (frame=0x9, eva=value optimized
   out)
   at /usr/src/sys/amd64/amd64/trap.c:879
   #4  0x80cfb691 in trap (frame=0xff8124900830)
   at /usr/src/sys/amd64/amd64/trap.c:605
   #5  0x80ce4ac3 in calltrap ()
   at /usr/src/sys/amd64/amd64/exception.S:232
   #6  0x80b86015 in vm_map_entry_splay (addr=984915968,
   root=0xfe002c9af200) at /usr/src/sys/vm/vm_map.c:832
   #7  0x80b870f7 in vm_map_lookup_entry (map=0xfe007535b640,
   address=984915968, entry=0xff8124900970)
   at /usr/src/sys/vm/vm_map.c:1080
   #8  0x80b8a5cc in vm_map_madvise (map=0xfe007535b640,
  start=984915968, end=985440256, behav=5) at
   /usr/src/sys/vm/vm_map.c:2050
   #9  0x80b8d9e3 in sys_madvise (td=0xfe000549e920,
   uap=value optimized out) at /usr/src/sys/vm/vm_mmap.c:760
   #10 0x80cfa62a in amd64_syscall (td=0xfe000549e920,
   #traced=0)
   at subr_syscall.c:135
   #11 0x80ce4da7 in Xfast_syscall ()
   at /usr/src/sys/amd64/amd64/exception.S:391
   #12 0x2ce13dcc in ?? ()
   Previous frame inner to this frame (corrupt stack?)
  
I can make the cores and text dumps available. kmod was rebuilt after
   the upgrade.
  
  
   Just confirmed that 254050 works fine. Trying 354162 and will continue
   binary hunt till I find it.
  
   I am now up to 254270, at the point of the original failure report. I
   now
  suspect I may have botched the kmod re-install on my original failure. I
  am calling it quits of the night now, but will finish tests tomorrow
  morning. The updates are pretty few and far between between 270 and the
  present.
 
 Hi,
 
 I am using r254095 and my system also resets when trying to start a Guest in
 VirtualBox, so the breaking update is probably between 254050 and 254270.
 
 Alonso

I meant between 254050 and 254095.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: buildkernel error ...

2012-12-17 Thread Schaich Alonso 
On 2012-12-17 (Monday) 17:02:06 Chris H wrote:
  On 12/17/2012 1:35 AM, Chris H wrote:
  hi all,
  
  I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
  
  yesterday I have cvsup-ed src and was trying to buildkernel
  bellow is error I receive:
  --- [ cut ]
  
  - ...
  cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g
  -Wall
  -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
  -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign
  -fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option  
  -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL
  -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
  -finline-limit=8000
  --param inline-unit-growth=100 --param large-function-growth=1000
  -fno-omit-frame-pointer
  -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
  /usr/src/sys/xdr/xdr_reference.c
  cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g
  -Wall
  -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
  -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign
  -fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option  
  -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL
  -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
  -finline-limit=8000
  --param inline-unit-growth=100 --param large-function-growth=1000
  -fno-omit-frame-pointer
  -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
  /usr/src/sys/xdr/xdr_sizeof.c
  cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g
  -Wall
  -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
  -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign
  -fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option  
  -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL
  -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
  -finline-limit=8000
  --param inline-unit-growth=100 --param large-function-growth=1000
  -fno-omit-frame-pointer
  -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
  /usr/src/sys/amd64/acpica/acpi_machdep.c
  cc -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe
  -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
  -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign
  -fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option  
  -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL
  -DHAVE_KERNEL_OPTION_HEADERS -include
  opt_global.h -fno-common -finline-limit=8000 --param
  inline-unit-growth=100 --param large-function-growth=1000 
  -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx
  -mno-sse -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding
  -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S
  /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages:
  /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction:
  `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such
  instruction: `xrstor (%rbx)' *** Error code 1
  
  Stop in /usr/obj/usr/src/sys/ZEUS_HOME.
  *** Error code 1
  
  Stop in /usr/src.
  *** Error code 1
  
  Stop in /usr/src.
  --- [ cut ]
  
  -
  
  
  nothing is changed in my kernel configuration file ...
  
  Greetings,
  
I too attempted a buildworld, and a kernel yesterday (also synced
yesterday). 
  It failed with a similar message to yours. I have _never_ experianced
  world, or kernel issues in the 25yrs I've been using BSD exclusively.
  Given that the only thing that has changed is the addition of clang, I'd
  recommend performing a: make clean
  then try again with:
  make  -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here
  replacing your_kernel_name_here with the actual name of your KERNCONF
  file.
  
  I'm in the middle of a buildworld as I write this, that I believe will
  conclusively prove that clang was the reason my last attempt failed.
  
  HTH, and best wishes.
  
  --Chris
  
  P.S. This was also 9.1
  
  --
  Zeus V. Panchenko jid:z...@im.ibs.dn.ua
  IT Dpt., I.B.S. LLC GMT+2 (EET)
  ___
  freebsd-stable@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-stable
  To unsubscribe, send any mail to

Re: Help review the FAQ

2012-11-26 Thread Schaich Alonso 
On 2012-11-26 (Monday) 22:15:27 Miroslav Lachman wrote:
 [...]
 
 So a kernel alone has 12MB, with debug symbols 62MB (12+50).
 And all *.symbols files can be deleted (if more space on /boot is needed)
 I don't know how it should be mentioned in FAQ.
 
 Miroslav Lachman

Specifying WITHOUT_KERNEL_SYMBOLS=YES in src.conf to not generate debug 
information IMO is a cleaner and more preferable solution then deleting the 
files, and it also reduces the amount of storage space needed for /usr/obj (or 
whereever else the kernel's built) by about 1GB on STABLE-9.

Schaich Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 and intel graphics

2012-10-20 Thread Schaich Alonso 
On 2012-10-20 (Saturday) 11:12:45 Thomas Mueller wrote:
  Full support for the HD3000 is in 9-stable and 9.1-Beta and all RCs.
  To use it you need to build X drivers and drm and the kernel with:
  WITH_NEW_XORG=YES
  WITH_KMS=YES
  in /etc/make.conf.
  
  Specifically, the kernel and a few ports. graphics/drm and your
  org-drivers: xf86-video-intel, xf86-input-synaptics, xf86-input-mouse,
  and xf86-input-keyboard. Then just start X. Don't try loading the
  kernel module. It will be loaded by the startx.
  
   Finally, what happens when I leave x and want to go back to
   console mode?
  
  You don't If you try, your system will lock up. You need to shutdown
  from a window in X. Hopefully someone will implement switching back to
  console mode some day, but it has not happened, yet.
 
 How do you shutdown from a window in X if you're nonroot?  Can you have
 both root and nonroot windows simultaneously in X?
 
 Tom
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Hello,

While you are not able to see anything on the screen, the system is still 
operational after X11 shutdown (or tty switch). Therefore you can still type 
input to the (invisible) command line or connect to that system via 
telnet/ssh/rlogin ...

By default the system shuts down gracefully if you hit it's power button. If 
you're using GDM/KDM you can also use their shutdown options. Eventually it 
might crash during shutdown though (at least over here). 

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Clang as default compiler

2012-09-11 Thread Schaich Alonso 
On 2012-09-11 (Tuesday) 23:49:24 Andreas Nilsson wrote:
 Today I decided to take the plunge and make clang the default compiler, ie
 I set
 
 WITH_CLANG=yes
 WITH_CLANG_IS_CC=yes
 WITH_CLANG_EXTRAS=yes
 
 in src.conf. No problem so far. However I wanted to avoid building base gcc
 ( the whole collection ). Is  WITHOUT_GCC what I'm looking for?
 

It probably is. However, WITHOUT_GCC is not supported yet.

 On another clang note: Is there a page specifying valid settings for
 -march, my google-foo is failing me. Ie, I'm looking for the equivalent of
 http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.htm
 l#i386-and-x86_002d64-Options
 

Take a look at lines 120 and below of contrib/llvm/lib/Target/X86/X86.td in 
the FreeBSD source directory for supported march switches.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: video issue - Intel Atom based motherboard D2500HN

2012-07-14 Thread Schaich Alonso 
On 2012-07-14 (Saturday) 13:28:32 Marek Salwerowicz wrote:
 Hi all,
 
 I recently bought a Intel D2500HN motherboard with Intel GMA 3600 video
 card.
 I want to install FreeBSD 9-Release on it via PXE, but after booting the
 system, it seems that video card driver doesn't work properly.
 
 Have a look at this picture:
 http://img703.imageshack.us/img703/5648/20120714393.jpg
 
 I've tried the
 # vidcontrol 80x25
 
 but unfortunately it doesn't help.
 
 Do you have any idea how to deal with taht graphics?
 
 Regards,

That is probably a broken BIOS, firmware or hardware. Can you try booting a 
different operating system? (USB rescue discs or so)

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: em interfaces supermicro X9SCM-F board

2012-06-05 Thread Schaich Alonso 
On 2012-06-05 (Tuesday) 19:31:44 Sebastian Stach wrote:
 I have an X9SCA-F board and recently updated the BIOS to version 2.0 (the
 .508 BIOS file). Its not the same board as yours but maybe the you have
 the same problem. When i downloaded the BIOS from the Supermicro website
 on May 23 the included AMI.BAT only updated the BIOS and not the Intel ME
 BIOS extension.
 
 When i downloaded the file again 2 days ago the AMI.BAT was updated to also
 flash the Intel ME. Too bad the version number and the filename are still
 the same. I only got to know this after contacting their support.
 
 My problems were different though. Both of my nics were usable but were
 hanging after about 2 hours of heavy load but maybe your problem can be
 fixed with a new BIOS update.
 
 Sebastian
 

Hello

I never have updated the BIOS on my X9SCM-F, yet the interfaces are also going 
down after some time of full load.
Was the NIC issue fixed for you by updating the BIOS?

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: What ZFS version will be in 8.3?

2012-03-11 Thread Schaich Alonso 
ZFS v28. It was merged into RELENG_8 from current in may last year.

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Problem with USB keyboard during boot screen

2012-01-26 Thread Schaich Alonso 
On 2012-01-26 (Thursday) 23:00:32 Garance A Drosihn wrote:
 Hi.
 
 I recently installed 9.0-release on a brand new PC which has an i3 chip.
 During the initial install I happened to use a USB keyboard from Apple.
 I installed freebsd/amd64.  Everything that I tried worked okay with it.
 
 After testing a variety of things, I put the machine in a small rack I
 have, and hooked up a different USB keyboard to it.  Once the machine
 has booted all the way up to a login: prompt, the newer USB keyboard
 also works fine.  It's from Logitech, and has illuminated keys (if that
 makes any difference).
 
 The thing is, the newer keyboard will not work during the initial boot
 screen.  I see the menu fine, but everything I type using the logitech
 keyboard is ignored.  If I plug in the Apple keyboard, that works fine
 during the bootup screen.
 
 Is there something I could configure to make the Logitech keyboard work
 during that bootup screen?  The thing is that the Apple keyboard has a
 pretty short USB cable, while the Logitech one has a much longer cable.
 
 When I plug in the Logitech keyboard, I get /var/log/messages of:
 
Jan 26 16:54:20 santropez kernel: ugen1.3: Logitech at usbus1
Jan 26 16:54:20 santropez kernel: ukbd0: Logitech Logitech
 Illuminated Keyboard, class 0/0, rev 2.00/55.01, addr 3 on usbus1
Jan 26 16:54:20 santropez kernel: kbd2 at ukbd0
Jan 26 16:54:20 santropez kernel: uhid0: Logitech Logitech
 Illuminated Keyboard, class 0/0, rev 2.00/55.01, addr 3 on usbus1
 
 When I plug in the Apple keyboard, I get messages of:
 
Jan 26 16:54:37 santropez kernel: ugen1.4: Apple, Inc. at usbus1
Jan 26 16:54:37 santropez kernel: uhub4: Apple, Inc. Keyboard Hub,
 class 9/0, rev 2.00/94.15, addr 4 on usbus1
Jan 26 16:54:38 santropez kernel: uhub4: 3 ports with 2 removable,
 bus powered
Jan 26 16:54:39 santropez kernel: ugen1.5: Apple, Inc at usbus1
Jan 26 16:54:39 santropez kernel: ukbd1: Apple, Inc Apple Keyboard,
 class 0/0, rev 2.00/0.69, addr 5 on usbus1
Jan 26 16:54:39 santropez kernel: kbd3 at ukbd1
Jan 26 16:54:39 santropez kernel: uhid1: Apple, Inc Apple Keyboard,
 class 0/0, rev 2.00/0.69, addr 5 on usbus1
 
 This is not particularly critical to me, but it'd be nice if I could
 get the logitech one to work during the bootup screen.

The illuminated keyboard is most probably an usb-2 device, while the 
nonilluminated one is usb-1. USB-1 is supported by BIOS and USB-2 is not I 
would guess, and it's also the bios where you could eventually change this 
(notice that you will probably not be able to enter BIOS with the illuminated 
keyboard either)

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Upgrade to 9.0 and Fan kick to high speed

2012-01-14 Thread Schaich Alonso 
On 2012-01-14 (Saturday) 04:35:31 Jeremy Chadwick wrote:
 On Fri, Jan 13, 2012 at 07:44:17PM -0500, benjamin adams wrote:
  I just upgraded from RC3 to release and now my pc fans are doing an high
  to low every two seconds.  Ideas on why??
 
 Lots of ideas on why, but whether or not any of them are applicable is a
 separate topic.  :-)  For starters:
 
 sysctl -a | grep freq
 sysctl -a | grep acpi
 
 And are you using powerd(8) at all?

Hi

This is happening to me, too. It starts occuring after about two hours of 
uptime here, and I haven't managed to get any of the sysctl data under this 
effect, as the system will start booting when I run sysctl. sysctl 
dev.cpu.x.freq runs however, showing 400-1200 MHz (with coretemp module 
dev.cpu.0.temperature is 30-35 C) so it's a sensor issue somewhere else - also 
the overheat indicator light of the affected box turns on here every ~20 
seconds, causing the fans to run faster.

I've attached the sysctl outputs of the system while it's is running stable. 
powerd is running, with performance_cx_lowest and economy_cx_lowest set to C2.

Also, I've been running 9-STABLE for months (i.e. before and after RELEASE) 
without this issue, but enabled speedstepping only a few days ago, so I think 
this issue might be related to speedsteping. I'll disable it now and report 
back in a few hours if it helped ;)

Alonso
device  acpi
debug.acpi.acpi_ca_version: 20110527
debug.acpi.enable_debug_objects: 0
debug.acpi.interpreter_slack: 1
debug.acpi.reset_clock: 1
debug.acpi.suspend_bounce: 0
debug.acpi.ec.burst: 0
debug.acpi.ec.polled: 0
debug.acpi.ec.timeout: 750
debug.acpi.batt.batt_sleep_ms: 0
debug.acpi.resume_beep: 0
hw.acpi.supported_sleep_state: S1 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S1
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: NONE
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 1
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C2
machdep.acpi_timer_freq: 3579545
machdep.idle_available: spin, mwait, hlt, acpi
machdep.idle: acpi
machdep.acpi_root: 984144
dev.acpi.0.%desc: SUPERM SMCI--MB
dev.acpi.0.%driver: acpi
dev.acpi.0.%parent: nexus0
dev.acpi_sysresource.0.%desc: System Resource
dev.acpi_sysresource.0.%driver: acpi_sysresource
dev.acpi_sysresource.0.%location: handle=\_SB_.PCI0.MCH_
dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C01 _UID=10
dev.acpi_sysresource.0.%parent: acpi0
dev.acpi_sysresource.1.%desc: System Resource
dev.acpi_sysresource.1.%driver: acpi_sysresource
dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.SBRG.RMSC
dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=16
dev.acpi_sysresource.1.%parent: acpi0
dev.acpi_sysresource.2.%desc: System Resource
dev.acpi_sysresource.2.%driver: acpi_sysresource
dev.acpi_sysresource.2.%location: handle=\_SB_.PCI0.SBRG.SIO1
dev.acpi_sysresource.2.%pnpinfo: _HID=PNP0C02 _UID=273
dev.acpi_sysresource.2.%parent: acpi0
dev.acpi_sysresource.3.%desc: System Resource
dev.acpi_sysresource.3.%driver: acpi_sysresource
dev.acpi_sysresource.3.%location: handle=\_SB_.PCI0.SBRG.SIO2
dev.acpi_sysresource.3.%pnpinfo: _HID=PNP0C02 _UID=5710
dev.acpi_sysresource.3.%parent: acpi0
dev.acpi_sysresource.4.%desc: System Resource
dev.acpi_sysresource.4.%driver: acpi_sysresource
dev.acpi_sysresource.4.%location: handle=\_SB_.PCI0.PCH_
dev.acpi_sysresource.4.%pnpinfo: _HID=PNP0C01 _UID=455
dev.acpi_sysresource.4.%parent: acpi0
dev.acpi_sysresource.5.%desc: System Resource
dev.acpi_sysresource.5.%driver: acpi_sysresource
dev.acpi_sysresource.5.%location: handle=\_SB_.PCI0.CWDT
dev.acpi_sysresource.5.%pnpinfo: _HID=INT3F0D _UID=0
dev.acpi_sysresource.5.%parent: acpi0
dev.acpi_sysresource.6.%desc: System Resource
dev.acpi_sysresource.6.%driver: acpi_sysresource
dev.acpi_sysresource.6.%location: handle=\_SB_.RMEM
dev.acpi_sysresource.6.%pnpinfo: _HID=PNP0C01 _UID=1
dev.acpi_sysresource.6.%parent: acpi0
dev.acpi_sysresource.7.%desc: System Resource
dev.acpi_sysresource.7.%driver: acpi_sysresource
dev.acpi_sysresource.7.%location: handle=\OMSC
dev.acpi_sysresource.7.%pnpinfo: _HID=PNP0C02 _UID=3601
dev.acpi_sysresource.7.%parent: acpi0
dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz
dev.acpi_timer.0.%driver: acpi_timer
dev.acpi_timer.0.%location: unknown
dev.acpi_timer.0.%pnpinfo: unknown
dev.acpi_timer.0.%parent: acpi0
dev.cpu.0.%parent: acpi0
dev.cpu.1.%parent: acpi0
dev.cpu.2.%parent: acpi0
dev.cpu.3.%parent: acpi0
dev.cpu.4.%parent: acpi0
dev.cpu.5.%parent: acpi0
dev.cpu.6.%parent: acpi0
dev.cpu.7.%parent: acpi0
dev.pci_link.0.%parent: acpi0
dev.pci_link.1.%parent: acpi0
dev.pci_link.2.%parent: acpi0
dev.pci_link.3.%parent: acpi0
dev.pci_link.4.%parent: acpi0
dev.pci_link.5.%parent: acpi0
dev.pci_link.6.%parent: acpi0
dev.pci_link.7.%parent: acpi0
dev.pcib.0.%parent: acpi0
dev.acpi_button.0.%desc: Power Button
dev.acpi_button.0.%driver: acpi_button
dev.acpi_button.0.%location: handle=\_SB_.PWRB

Re: Upgrade to 9.0 and Fan kick to high speed

2012-01-14 Thread Schaich Alonso 
System is running well for 6 hours now. Seems like disabling speedsteping 
solved it (for me).

Alonso
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org