> Wireless support for 802.11n has been added. Wait, What?
My guess is this part: The iwn(4) driver was added, providing support for the Intel® Centrino™ Wireless-N 105 and 135 chipsets. [r266770] from: https://www.freebsd.org/releases/11.0R/relnotes.html#drivers...
FreeBSD 11.0 Now Available
91–100 of 163 posts
Re: FreeBSD 11.0 Now Available
#92> Wireless support for 802.11n has been added. Wait, What?
My guess is this part: The iwn(4) driver was added, providing support for the Intel® Centrino™ Wireless-N 105 and 135 chipsets. [r266770] from: https://www.freebsd.org/releases/11.0R/relnotes.html#drivers...
Re: FreeBSD 11.0 Now Available
#93> A kernel panic triggered when destroying a vnet(9) jail(8) configured with gif(4) has been fixed. [r271917] > A kernel panic triggered when destroying a vnet(9) jail(8) configured with gre(4) has been fixed. [r271918] I see they fixed the kernel panics when destroying vnet jails but is vnet enabled by default? Or do I have to compile a custom kernel like with FreeBSD 10.x
I started using SmartOS partly because it has really nice VNIC support and you don't have to recompile the 10.x FreeBSD kernels. :-) It'd be good to know if 11.0 changed that.
Re: FreeBSD 11.0 Now Available
#94I've got a 10.3 system that's running a "custom" kernel with VNET enabled for my iocage jails. What am I in for when I upgrade? How do I keep my ZFS pool safe through the upgrade?
If you upgrade via freebsd-update and have renamed your custom kernel (and not named it GENERIC), then freebsd-update will tell you when to build and install a new version of your kernel.
If you kept GENERIC as the name of your custom kernel, which is a really really bad idea, then freebsd-update will probably still replace it with a vanilla kernel, haven't checked that in a while. In that case either rebuild your 10.3 kernel again with a fixed name, or upgrade to 11 from source.
Re: FreeBSD 11.0 Now Available
#95How much do you think it will take until Juniper JunOS and netApp will upgrade their kernels to 11.0-p1?
NetApp does tend to be one of the higher financial contributors to the FreeBSD Foundation but this amounts to the salary of one full time engineer. I think the bhyve code drop was a fluke, but a very fortunate one, and the two developers left NetApp quickly after that happened. Outside of that, especially during the formative '90s and '00 where it could have been politically influential, continuing today there is almost no code reintegration. It's hard to find business justification because NetApp is a prime contributor to Linux, including the NFS server which could be argued has allowed companies like PureStorage to eat their lunch.
Juniper has some storied history of many many-year projects to resync their branch. They have their own TCP stack. Many of the influential FreeBSD devs I know there have fled recently. I heard something about switching to Linux. Sounds like a rudderless company, following a nice anti-pattern example set by Yahoo. It is sad because JunOS and the HW was and is for now quite nice.
I work at a small but highly traditional/bureaucratic company and was able to build a 4 person full time upstream BSD team in 2 years. I cannot fathom why NetApp and Juniper would not have a 10-40 people upstream team.
Re: FreeBSD 11.0 Now Available
#96Earlier quoted context omitted.
Really depends on your machine. Suspend (and wakeup!) works great on my Lenovo X220, no fiddling needed at all.
With X? Because the docs themselves say it doesn't work well with X [1]. Would you mind sharing your relevant config? [1] https://wiki.freebsd.org/SuspendResume
I recently got my hands on a Acer Aspire E-571 (Haswell i3-4030U) and suspend/resume in X with i915kms literally just worked installing FreeBSD 11.0-RC3 from installer and xorg/xdm/openbox from packages, no config file touched (apart from adjusting the keyboard layout and setting the lid_close_state sysctl to S3).
What does not work on it yet is the Elan trackpad, since it is the version that is connected via i2c.
Re: FreeBSD 11.0 Now Available
#97Earlier quoted context omitted.
Hi! FreeBSD wifi person here! * ath(4)'s 11n support is much, much better now. All the AR93xx/AR95xx PCIe devices are supported and STA/AP 11n should work great. * iwn(4)'s 11n is much, much better. It still has some warts, and I'd love some help in chasing them down. * urtwn(4) in -HEAD does 11n now. * rsu(4) in -HEAD does 11n now. * iwm(4) (intel 7260, etc) is getting better every day in freebsd and dragonflybsd. T…
Thanks Adrian. I am not a device drivers person. But, quick query - do you reuse the current Linux drivers work [0]. Looking at the current client device deployment, Intel owns around 80% of the Wi-Fi modem market. Is anybody from Intel working on BSD wireless drivers as well. [0] https://wireless.wiki.kernel.org/en/users/Drivers
It would be great if Intel stepped up to the plate and helped.
Re: FreeBSD 11.0 Now Available
#98> A kernel panic triggered when destroying a vnet(9) jail(8) configured with gif(4) has been fixed. [r271917] > A kernel panic triggered when destroying a vnet(9) jail(8) configured with gre(4) has been fixed. [r271918] I see they fixed the kernel panics when destroying vnet jails but is vnet enabled by default? Or do I have to compile a custom kernel like with FreeBSD 10.x
I started using SmartOS partly because it has really nice VNIC support and you don't have to recompile the 10.x FreeBSD kernels. :-) It'd be good to know if 11.0 changed that.
Re: FreeBSD 11.0 Now Available
#99Earlier quoted context omitted.
Hmph. I remember when "session management" was echo startx >> .loginrc I sure miss being able to understand and control my machine...
I reached the point of not understanding my machine when mounting a disk on Linux required udisks2/dbus and parts of Gnome. FreeBSD can be pretty spartan, but I do feel like I'm more in control.
Re: FreeBSD 11.0 Now Available
#100Earlier quoted context omitted.
I reached the point of not understanding my machine when mounting a disk on Linux required udisks2/dbus and parts of Gnome. FreeBSD can be pretty spartan, but I do feel like I'm more in control.
Is this a thing? I'm running Slackware and mounting a disk is still done with good ol' `mount`, same as it ever was.