Re: CURRENT: EFI boot failure

2014-09-15 Thread O. Hartmann
Am Mon, 15 Sep 2014 17:39:26 -0700 Nathan Whitehorn schrieb: > > On 09/15/14 17:36, Allan Jude wrote: > > On 2014-09-15 20:05, O. Hartmann wrote: > >> Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works > >> for UEFI > >> fine. After I updated the sources to r271649, recom

Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI

2014-09-15 Thread Adrian Chadd
Hi, Try updating to the latest -HEAD. It at least makes dhclient behave better. -a On 15 September 2014 18:19, Kevin Oberman wrote: > On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann > wrote: > >> >> Trying to install and run FreeBSD 11.0-CURRENT >> (FreeBSD-11.0-CURRENT-amd64-20140903-r270990-m

Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI

2014-09-15 Thread Kevin Oberman
On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann wrote: > > Trying to install and run FreeBSD 11.0-CURRENT > (FreeBSD-11.0-CURRENT-amd64-20140903-r270990-memstick.img) on a new Lenovo > E540 notebook > fails in activating the NIC (Realtek RTL8111/8168B, driver re[0]). The NIC > shows up as > active a

Re: CURRENT: EFI boot failure

2014-09-15 Thread Nathan Whitehorn
On 09/15/14 17:36, Allan Jude wrote: On 2014-09-15 20:05, O. Hartmann wrote: Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for UEFI fine. After I updated the sources to r271649, recompiled world and kernel (as well as installed), now I get stuck with the screen mess

Re: CURRENT: EFI boot failure

2014-09-15 Thread Allan Jude
On 2014-09-15 20:05, O. Hartmann wrote: > > Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for > UEFI fine. > After I updated the sources to r271649, recompiled world and kernel (as well > as > installed), now I get stuck with the screen message: > >>> FreeBSD EFI boo

CURRENT: EFI boot failure

2014-09-15 Thread O. Hartmann
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for UEFI fine. After I updated the sources to r271649, recompiled world and kernel (as well as installed), now I get stuck with the screen message: >> FreeBSD EFI boot block Loader path: /boot/loader.efi and nothing ha

Re: libthr and main thread stack size

2014-09-15 Thread Justin T. Gibbs
On Aug 8, 2014, at 5:22 AM, Konstantin Belousov wrote: … > Below is the patch which adds environment variable LIBPTHREAD_BIGSTACK_MAIN. > Setting it to any value results in the main thread stack left as is, and > other threads allocate stack below the area of RLIMIT_STACK. Try it. > I do not wa

11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI

2014-09-15 Thread O. Hartmann
Trying to install and run FreeBSD 11.0-CURRENT (FreeBSD-11.0-CURRENT-amd64-20140903-r270990-memstick.img) on a new Lenovo E540 notebook fails in activating the NIC (Realtek RTL8111/8168B, driver re[0]). The NIC shows up as active and with carrier when issuing "ifconfig re0". From a desktop mach

Re: Driver-specific debugging in buildkernel?

2014-09-15 Thread John Baldwin
On Sunday, September 14, 2014 07:56:16 PM Thomas Mueller wrote: > I want to build a kernel with debugging for a specific device, rather than > for everything. > > Device of interest is re (Ethernet driver), also rsu (USB wlan adapter). > > I looked in Makefiles, also NOTES files, found some D

Re: panic: resource_list_alloc: resource entry is busy

2014-09-15 Thread John Baldwin
On Friday, September 12, 2014 10:03:26 PM Marcin Cieslak wrote: > On Fri, 12 Sep 2014, John Baldwin wrote: > >> Please note I originally loaded "i915.ko", not "i915kms.ko" > > > > Oh, that is probably your problem. X loaded i915kms automatically and > > i915 and i915kms do not get along. i915 ha

Re: Xorg causes panics with "multiple" drivers (Was: panic: resource_list_alloc: resource entry is busy)

2014-09-15 Thread John Baldwin
On Saturday, September 13, 2014 10:57:53 AM d...@gmx.com wrote: > John Baldwin wrote on 09/12/2014 23:06: > > X loaded i915kms automatically and > > i915 and i915kms do not get along. i915 had already allocated the IRQ > > when i915kms tried to alloc the same IRQ causing the issue. > > Who is to