Build failed in Jenkins: FreeBSD_HEAD #1537

2014-09-27 Thread jenkins-admin 
See 

Changes:

[cperciva] Switch primes(6) from using unsigned long to using uint64_t.  This 
fixes
'limited range of type' warnings about comparisons on 32-bit systems, and
allows 32-bit systems to compute the full range of primes.

[sbruno] Add kernel support for the TP-LINK MR3020 Atheros MIPS 24k router.

AR9331 based system.

Phabric:https://reviews.freebsd.org/D780
Reviewed by:adrian

[melifaro] * Split tcp_signature_compute() into 2 pieces:
 - tcp_get_sav() - SADB key lookup
 - tcp_signature_do_compute() - actual computation
* Fix TCP signature case for listening socket:
  do not assume EVERY connection coming to socket
  with TCP_SIGNATURE set to be md5 signed regardless
  of SADB key existance for particular address. This
  fixes the case for routing software having _some_
  BGP sessions secured by md5.
* Simplify TCP_SIGNATURE handling in tcp_input()

MFC after:  2 weeks

--
[...truncated 87458 lines...]
%lu
:2578:52:
 warning: format specifies type 'unsigned long long' but the argument has type 
'uint64_t' (aka 'unsigned long') [-Wformat]
dgettext(TEXT_DOMAIN, "cannot degrade %llu"), guid);
  ^~~~
  %lu
:3247:6:
 warning: format specifies type 'unsigned long long' but the argument has type 
'uint64_t' (aka 'unsigned long') [-Wformat]
guid);
^~~~
:3841:57:
 warning: format specifies type 'unsigned long long' but the argument has type 
'uint64_t' (aka 'unsigned long') [-Wformat]
(void) snprintf(pathname, len, ":<0x%llx>", obj);
  ^~~
  %lx
:3852:7:
 warning: format specifies type 'unsigned long long' but the argument has type 
'uint64_t' (aka 'unsigned long') [-Wformat]
dsobj, obj);
^
:3852:14:
 warning: format specifies type 'unsigned long long' but the argument has type 
'uint64_t' (aka 'unsigned long') [-Wformat]
dsobj, obj);
   ^~~
:3873:57:
 warning: format specifies type 'unsigned long long' but the argument has type 
'uint64_t' (aka 'unsigned long') [-Wformat]
(void) snprintf(pathname, len, "%s:<0x%llx>", dsname, obj);
  ^~~
  %lx
--- kerberos5/lib__L ---
--- crypto.o ---
cc   -O2 -pipe   
-I
 
-I
 
-I
 
-I
 
-I
 -DHAVE_CONFIG_H 
-I
 -std=gnu99 -fstack-protector   -Qunused-arguments -c 

 -o crypto.o
--- delete_sec_context.o ---
cc   -O2 -pipe   
-I
 
-I
 
-I
 
-I

WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread O. Hartmann 

I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to 
replace it
with an 802.11ac adaptor.

Since I made very bad experiences with CURRENT and support of modest modern 
hardware
(Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.

I found this PCIe adaptor card attractive:

GigaByte Gigabyte GC-WB867D-I

I can not find ad hoc the WLAN chip used on that specific card, but maybe 
someone has
experiences with that litte board.

Thanks in advance,
Oliver


signature.asc
Description: PGP signature

Jenkins build is back to normal : FreeBSD_HEAD #1538

2014-09-27 Thread jenkins-admin 
See 

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

Re: WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread Warren Block 

On Sat, 27 Sep 2014, O. Hartmann wrote:



I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to 
replace it
with an 802.11ac adaptor.

Since I made very bad experiences with CURRENT and support of modest modern 
hardware
(Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.

I found this PCIe adaptor card attractive:

GigaByte Gigabyte GC-WB867D-I

I can not find ad hoc the WLAN chip used on that specific card, but maybe 
someone has
experiences with that litte board.


Newegg reviews say this is an Intel 7260HMW:
http://www.newegg.com/Product/Product.aspx?Item=N82E16813995032&Tpk=N82E16813995032

I don't know if that is supported on FreeBSD yet.

PCIe to mini-PCIe adapters like that can be found separately, allowing 
the use of any mini-PCIe card.  I've successfully tested an Atheros 
AR9280 card in one.

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

Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT

2014-09-27 Thread O. Hartmann 
Am Sat, 20 Sep 2014 09:21:34 -0500
Larry Rosenman  schrieb:

> On 2014-09-20 09:10, O. Hartmann wrote:
> > Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
> > Warren Block  schrieb:
> > 
> >> On Fri, 19 Sep 2014, O. Hartmann wrote:
> >> 
> >> > nVidia's BLOB from port x11/nvidia-driver seems to have problems in 
> >> > FreeBSD
> >> > 11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on Lenovo 
> >> > ThinkPad
> >> > Edge E540 laptop with CPU i5-4200M (Haswell) with integrated HD4600 
> >> > Intel iGPU and
> >> > dedicated nVidia GT 740M (Optimus) working correctly.
> >> 
> >> Optimus is supposed to be full Intel graphics plus an Nvidia GPU.  The
> >> extra GPU uses the same display memory and can be enabled to speed up
> >> the Intel graphics or disabled for power saving.  I don't know if
> >> versions where the Nvidia section is a full discrete video adapter 
> >> that
> >> can be used alone are still called "Optimus".
> >> 
> >> Some Optimus owners have reported being able to use the Intel drivers
> >> after disabling the Nvidia GPU in the BIOS or UEFI.  If an option to
> >> disable the Nvidia GPU is not present, some people have reported 
> >> success
> >> with an xorg.conf that uses only the intel driver and ignores the 
> >> Nvidia
> >> hardware.
> > 
> > Thanks Warren.
> > 
> > But this sounds even more frustrating now. I look around the web even
> > at Lenovo's support
> > forum. Many people report the GT 740M nVidia adaptor as a discrete
> > adaptor with Optimus
> > technology and everything sounds to me like it can be selected
> > exclusively. What you
> > describes is that I definitely need to use the HD4600 iGPU on FreeBSD
> > in the first place
> > since the nVidia hardware is a kind of "appendix" to the HD4600.
> > 
> > Anyway, I also tried to configure X11 as HD4600 only and X11 doesn't
> > work properly: it
> > doesn't even start up and loading the "intel" driver complains about a
> > missing device -
> > preceeded by a lot of /dev/dri errors. This indicates to me, in a naiv
> > manner, that this
> > HD4600 isn't recodnized by the kernel, either. I do not see any kind
> > of vga0: entry in
> > the kernel log when enabling "Integrated Graphics" only in the
> > laptop's UEFI/Firmware.
> > When enabling "nVidia Optimus", a recognized vga0: device shows up.
> > 
> > From my server, equipted with a IvyBridge i3-class CPU with integrated
> > iGPU, I even get
> > this message from 11.0-CURRENT:
> > 
> > vgapci0@pci0:0:2:0: class=0x03 card=0x01521849 chip=0x01528086
> > rev=0x09 hdr=0x00
> > vendor = 'Intel Corporation'
> > device = 'Xeon E3-1200 v2/3rd Gen Core processor Graphics 
> > Controller'
> > class  = display
> > subclass   = VGA
> > bar   [10] = type Memory, range 64, base 0xf780, size 4194304, 
> > enabled
> > bar   [18] = type Prefetchable Memory, range 64, base 0xe000,
> > size 268435456,
> > enabled bar   [20] = type I/O Port, range 32, base 0xf000, size 64, 
> > enabled
> > cap 05[90] = MSI supports 1 message
> > cap 01[d0] = powerspec 2  supports D0 D3  current D0
> > cap 13[a4] = PCI Advanced Features: FLR TP
> > 
> > 
> > The very same CURRENT (most recent as I built world on all system 
> > today) doesn't
> > recognize the Haswell's HD4600 iGPU (i5-4200M). So, it seems
> > impossible to me that people
> > can report having this GPU working if even the most recent FreeBSD
> > CURRENT doesn't
> > recognize it.
> for the record, on my Thinkpad W520+Docking Station, I get two HDMI / 
> DVI outputs off the Nvidia GPU, in addition to the
> Intel graphics on the local LCD.   This is under Windows, but.
> 
> 

Just for the record.

Another box, running as a server with CURRENT on-top of a Intel(R) Core(TM) 
i3-3220 CPU
with Ivy-Bridge HD2500 graphics, crashes/blanks screen when going into graphics 
mode with
vt() (having kernel modules drm2 and i915kms already loaded via loader.conf).

This hardware is now for two years in use and the CPU is much older.

The CPU is about to be replaced by a XEON E3-1245 v2 with P4000 iGPU graphics 
(only). At
this moment, I'm highly afraid of having hardware that is not working even with 
CURRENT.


signature.asc
Description: PGP signature

Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT

2014-09-27 Thread Marcin Cieslak 



On Sat, 27 Sep 2014, O. Hartmann wrote:


Am Sat, 20 Sep 2014 09:21:34 -0500
Just for the record.

Another box, running as a server with CURRENT on-top of a Intel(R) Core(TM) 
i3-3220 CPU
with Ivy-Bridge HD2500 graphics, crashes/blanks screen when going into graphics 
mode with
vt() (having kernel modules drm2 and i915kms already loaded via loader.conf).


Seems to be a known problem. Can you try to start X without having i915kms 
loaded by
the third stage loader? This workaround works for me (i915kms gets loaded by X)

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

Re: WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread O. Hartmann 
Am Sat, 27 Sep 2014 08:41:56 -0600 (MDT)
Warren Block  schrieb:

> On Sat, 27 Sep 2014, O. Hartmann wrote:
> 
> >
> > I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want 
> > to
> > replace it with an 802.11ac adaptor.
> >
> > Since I made very bad experiences with CURRENT and support of modest modern 
> > hardware
> > (Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.
> >
> > I found this PCIe adaptor card attractive:
> >
> > GigaByte Gigabyte GC-WB867D-I
> >
> > I can not find ad hoc the WLAN chip used on that specific card, but maybe 
> > someone has
> > experiences with that litte board.
> 
> Newegg reviews say this is an Intel 7260HMW:
> http://www.newegg.com/Product/Product.aspx?Item=N82E16813995032&Tpk=N82E16813995032
> 
> I don't know if that is supported on FreeBSD yet.
> 
> PCIe to mini-PCIe adapters like that can be found separately, allowing 
> the use of any mini-PCIe card.  I've successfully tested an Atheros 
> AR9280 card in one.

Thats a pity. I have already this WiFi adaptor in a Lenovo E540 laptop and it 
isn't
supported by CURRENT. Some rumours say it is supposed to be supported by iwl() 
in the
future. 


signature.asc
Description: PGP signature

Re: WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread Lars Engels 
On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote:
> 
> I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want 
> to replace it
> with an 802.11ac adaptor.
> 
> Since I made very bad experiences with CURRENT and support of modest modern 
> hardware
> (Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.
> 
> I found this PCIe adaptor card attractive:
> 
> GigaByte Gigabyte GC-WB867D-I
> 
> I can not find ad hoc the WLAN chip used on that specific card, but maybe 
> someone has
> experiences with that litte board.

FreeBSD doensn't support 802.11ac, yet.


pgpUz4vndmrSY.pgp
Description: PGP signature

dmesg seems broken

2014-09-27 Thread Chris H 
Greetings,
 I'm building RELENG_9 recently. I installed, and updated source,
last night. I've just built world, and kernel. After (and before)
kernel install. I've found I'm missing from 14 to 40 lines from
the top of the dmesg(8) output. In either /var/log/messages, and
in /var/run/dmesg.boot.
Where can I get that information? Where was it sent? Why am I
not allowed to view it?

Thank you for all your time, and consideration.

--Chris

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

Re: dmesg seems broken

2014-09-27 Thread Chris H 
> On Sat, Sep 27, 2014 at 7:22 PM, Chris H  wrote:
>
>> Where can I get that information? Where was it sent? Why am I
>> not allowed to view it?
>>
>
> Sounds to me like the kernel ring buffer is now too small for all the early
> boot messages?
Odd. I'm only using GENERIC modified to not contain any
hardware I'm not using. I've made zero changes to alter
buffer(s).
As I also mentioned; this too was the case from GENERIC
that came on the install media.

Thanks for the reply, Brandon.

--Chris

>
> --
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
> ___
> freebsd-sta...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>

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

Re: dmesg seems broken

2014-09-27 Thread Brandon Allbery 
On Sat, Sep 27, 2014 at 7:22 PM, Chris H  wrote:

> Where can I get that information? Where was it sent? Why am I
> not allowed to view it?
>

Sounds to me like the kernel ring buffer is now too small for all the early
boot messages?

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

SOEKRIS kernel config

2014-09-27 Thread Tom Everett 
I see there is no SOEKRIS config on the tree, here

https://svnweb.freebsd.org/base/head/sys/i386/conf/

I have attached one for addition to the tree.


-- 
A better world shall emerge based on faith and understanding  - Douglas
MacArthur
#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: head/sys/i386/conf/GENERIC 271137 2014-09-04 21:06:33Z markj $

cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
ident   SOEKRIS

makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols
makeoptions WITH_CTF=1  # Run ctfconvert(1) for DTrace support

options SCHED_ULE   # ULE scheduler
options PREEMPTION  # Enable kernel thread preemption
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options TCP_OFFLOAD # TCP offload
options SCTP# Stream Control Transmission Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options UFS_GJOURNAL# Enable gjournal-based UFS journaling
options QUOTA   # Enable disk quotas for UFS
options MD_ROOT # MD is a potential root device
options NFSCL   # New Network Filesystem Client
options NFSD# New Network Filesystem Server
options NFSLOCKD# Network Lock Manager
options NFS_ROOT# NFS usable as /, requires NFSCL
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT   # GUID Partition Tables.
options GEOM_RAID   # Soft RAID functionality.
options GEOM_LABEL  # Provides labelization
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options COMPAT_FREEBSD7 # Compatible with FreeBSD7
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options STACK   # stack(9) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time 
extensions
options PRINTF_BUFR_SIZE=128# Prevent printf output being 
interspersed.
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4)
options AUDIT   # Security event auditing
options CAPABILITY_MODE # Capsicum capability mode
options CAPABILITIES# Capsicum capabilities
options MAC # TrustedBSD MAC Framework
options KDTRACE_HOOKS   # Kernel DTrace hooks
options DDB_CTF # Kernel ELF linker loads CTF data
options INCLUDE_CONFIG_FILE # Include this file in kernel

# Debugging support.  Always need this:
options KDB # Enable kernel debugger support.
options KDB_TRACE   # Print a stack trace for a panic.
# For full debugger support use (turn off in stable branch):
options DDB # Support DDB.
options GDB # Support remote GDB.
options DEADLKRES   # Enable the deadlock resolver
options INVARIANTS  # Enable calls of extra sanity checking
options INVARIANT_SUPPORT

Re: SOEKRIS kernel config

2014-09-27 Thread Kubilay Kocak 
On 28/09/2014 12:47 PM, Tom Everett wrote:
> I see there is no SOEKRIS config on the tree, here
> 
> https://svnweb.freebsd.org/base/head/sys/i386/conf/
> 
> I have attached one for addition to the tree.
> 
> 
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

Thanks Tom

This is a good candidate for a Bugzilla Issue, under Base System -> conf
so it doesn't get lost in the mail :)

--

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

Re: WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread O. Hartmann 
Am Sun, 28 Sep 2014 00:22:09 +0200
Lars Engels  schrieb:

> On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote:
> > 
> > I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want 
> > to
> > replace it with an 802.11ac adaptor.
> > 
> > Since I made very bad experiences with CURRENT and support of modest modern 
> > hardware
> > (Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.
> > 
> > I found this PCIe adaptor card attractive:
> > 
> > GigaByte Gigabyte GC-WB867D-I
> > 
> > I can not find ad hoc the WLAN chip used on that specific card, but maybe 
> > someone has
> > experiences with that litte board.
> 
> FreeBSD doensn't support 802.11ac, yet.

I'm bitter aware of that. This OS doesn't support the chipsets, even if they 
provide also
11a/g/n.

We have at our department now a bunch of Lenovo hardware, with Intels 7260 
chipset. The
laptops are now runninmg Ubuntu 14.0X something which obviously supports the 
WiFi chip.
I'm the last man standing with FreeBSD on my private Lenovo :-(


signature.asc
Description: PGP signature

Re: WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread Nathan Whitehorn 


On 09/27/14 23:06, O. Hartmann wrote:

Am Sun, 28 Sep 2014 00:22:09 +0200
Lars Engels  schrieb:


On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote:

I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to
replace it with an 802.11ac adaptor.

Since I made very bad experiences with CURRENT and support of modest modern 
hardware
(Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.

I found this PCIe adaptor card attractive:

GigaByte Gigabyte GC-WB867D-I

I can not find ad hoc the WLAN chip used on that specific card, but maybe 
someone has
experiences with that litte board.

FreeBSD doensn't support 802.11ac, yet.

I'm bitter aware of that. This OS doesn't support the chipsets, even if they 
provide also
11a/g/n.

We have at our department now a bunch of Lenovo hardware, with Intels 7260 
chipset. The
laptops are now runninmg Ubuntu 14.0X something which obviously supports the 
WiFi chip.
I'm the last man standing with FreeBSD on my private Lenovo :-(


This is a serious problem. I'm about ready to install Linux on my laptop 
as well just to get a usable system. Some kind of funding directed to a 
willing developer would be hugely valuable for the usability of the 
operating system on recent hardware. This is probably more important 
even than Haswell graphics since without a driver, Haswell is merely 
slow, whereas networking is completely broken.

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

Re: SOEKRIS kernel config

2014-09-27 Thread Scot Hetzel 
On Sat, Sep 27, 2014 at 9:47 PM, Tom Everett  wrote:
> I see there is no SOEKRIS config on the tree, here
>
> https://svnweb.freebsd.org/base/head/sys/i386/conf/
>
> I have attached one for addition to the tree.
>
>

Since you only appended a few configuration options to the end of the
GENERIC configuration, it would be better to use the include directive
in the SOEKRIS config file.  This allows changes to be made to the
GENERIC configuration, and the SOEKRIS kernel would automatically get
those changes.  Here's a shorter version of that configuration file:


#
# SOEKRIS -- Generic Kernel configuration file for FreeBSD/i386 on SOEKRIS
#
# $FREEBSD

include GENERIC

ident SOEKRIS

# To Make a SOEKRIS Kernel, the next options are needed
options  CPU_SOEKRIS
options  CPU_ELAN
#options  CPU_ELAN_PPS
#options  CPU_ELAN_XTAL=32768000
options  CPU_GEODE

# Include TMPFS
options  TMPFS


-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: WiFi 802.11/ac PCIe supported adaptor

2014-09-27 Thread Kevin Oberman 
On Sat, Sep 27, 2014 at 11:20 PM, Nathan Whitehorn 
wrote:

>
> On 09/27/14 23:06, O. Hartmann wrote:
>
>> Am Sun, 28 Sep 2014 00:22:09 +0200
>> Lars Engels  schrieb:
>>
>>  On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote:
>>>
 I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and
 want to
 replace it with an 802.11ac adaptor.

 Since I made very bad experiences with CURRENT and support of modest
 modern hardware
 (Haswell CPU/Intel  7260 DualBand WiFi NIC), I'd like to ask here first.

 I found this PCIe adaptor card attractive:

 GigaByte Gigabyte GC-WB867D-I

 I can not find ad hoc the WLAN chip used on that specific card, but
 maybe someone has
 experiences with that litte board.

>>> FreeBSD doensn't support 802.11ac, yet.
>>>
>> I'm bitter aware of that. This OS doesn't support the chipsets, even if
>> they provide also
>> 11a/g/n.
>>
>> We have at our department now a bunch of Lenovo hardware, with Intels
>> 7260 chipset. The
>> laptops are now runninmg Ubuntu 14.0X something which obviously supports
>> the WiFi chip.
>> I'm the last man standing with FreeBSD on my private Lenovo :-(
>>
>
> This is a serious problem. I'm about ready to install Linux on my laptop
> as well just to get a usable system. Some kind of funding directed to a
> willing developer would be hugely valuable for the usability of the
> operating system on recent hardware. This is probably more important even
> than Haswell graphics since without a driver, Haswell is merely slow,
> whereas networking is completely broken.
> -Nathan


While I don't yet have need of it and probably won't any time soon,
Haswell support is becoming critical. It is getting more and more difficult
to get boards with pre-Haswell processors, especially for laptops. It is
still pretty easy to get supported WiFi cards for both desktops and
laptops. I feel Haswell is getting to be a critical issue.

VESA is available for Haswell systems, but it is very slow and too often
the BIOS support of VESA is poor. Vendors want text mode for boot and such,
but really have little interest in graphics as Intel has good native
Windows drivers for them.Still waiting for Lenovo to fix VESA for my old
Sandy Bridge laptop. I used VESA, which was badly broken, for almost a year
waiting for KMS support, though I did get a recent BIOS update and have not
tried VESA on it.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"