Aw: recent change to vim defaults?

Julian Elischer wrote: > I noticed that suddenly vim is grabbing mouse movements, which makes > life really hard. > > Was there a specific revision that brought in this change, and can it > be removed? Of course this behavior can be disabled as suggested by others--or you

Re: WLAN hardware not recognized

Adrian Chadd wrote: > Right, you need to create the interface: > > ifconfig wlan0 create wlandev iwn0 > > then run wpa_spuplicant > > (or do it all in /etc/rc.conf .. :) That seems to work. There seems to be something configured wrong for wpa_supplicant but WLAN

Re: WLAN hardware not recognized

Conrad Meyer wrote: > "[1] iwn0: mem 0xf7b0-0xf7b01fff > irq 18 at device 0.0 on pci3" is fine; "module iwn already present!" > is fine. > > What makes you say it isn't recognized or doesn't work? ifconfig iwn0 says "interface iwn0 does not exist". Also starting

Aw: Re: WLAN hardware not recognized

Adrian Chadd wrote: > sysctl net.wlan.devices > > iwn0 no longer shows up in ifconfig -a . > > > -a Ok, "sysctl -a|grep iwn" gives quite some output. Actually I tried to start wpa_supplicant, but WLAN didn't react. Then--just for testing--I wrote "ifconfig iwn0

Re: WLAN hardware not recognized

Conrad Meyer wrote: > kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw. This or edit loader.conf doesn't help, all these things had already been in the kernel. dmesg stays the same. ___ freebsd-current@freebsd.org mailing list

Re: WLAN hardware not recognized

Larry Rosenman wrote: > Did you load the iwn firmware? How do I do this? I put "if_iwn_load="YES"" into /boot/loader.conf, now I get "module iwn already present!" in dmesg... ___ freebsd-current@freebsd.org mailing list

Aw: Re: WLAN hardware not recognized

Joe Nosay wrote: > Is the card removable? If so, have you tried plugging in one that would > have the driver already included with the base - so to speak - system? Have > you tried the card in another computer/laptop? It is an integrated card. Theoretical it is

WLAN hardware not recognized

Hello, the WLAN hardware of my Dell E6540 (intel 633ANHMW) is not recognized (or at least does not work). The only message found in dmesg is: [1] iwn0: mem 0xf7b0-0xf7b01fff irq 18 at device 0.0 on pci3 Full dmesg is: Copyright (c) 2013-2016 The HardenedBSD Project. [1] Copyright (c)

Aw: Re: Haswell graphics (i915) still not in CURRENT

Shawn Webb wrote: > We at HardenedBSD have an experimental branch that is kept up-to-date > with FreeBSD HEAD along with Jean-Sebastien's excellent work (and > HardenedBSD's awesomeness on top of that). > > The code is here: > >

Haswell graphics (i915) still not in CURRENT

Hello, Haswell graphics (i915) still seems not to be in CURRENT. There is a suggested test procedure on https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linux%203.8 but currently I'm to busy with other projects to test this. At the moment CURRENT can't be used on laptops

Re: No X on Dell E6540

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

Aw: Re: make .SUFFIXES bug?

Thomas Dickey <dic...@his.com> wrote: > On Tue, Dec 15, 2015 at 04:01:41PM +0100, Carsten Kunze wrote: > > current groff doesn't build on FreeBSD. I had noticed the same issue some > > months ago on NetBSD and cross checked on FreeBSD and it had worked on > > FreeBSD

Aw: Re: make .SUFFIXES bug?

Hello Simon, > > .SUFFIXES: > > .SUFFIXES: .roff .in .ps .mom .pdf .me .ms .ps .html .txt .texi .dvi .pdf > .xhtml .man .c .cpp .log .o .obj .sed .sin .test .test$(EXEEXT) .trs .ypp > > What is the value of EXEEXT at this point? You are right, the example is not as small as it could be for

Do keymaps need to be in /usr/...?

Hello, disk decryption works for me when I put kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd into /etc/rc.d/geli. But do the keymaps need to be in a file system which may be mounted delayed? If there is an error at boot time and something needs to be input to the console the

keymap set after file system decryption

Hello, according to the boot messages the keymap is set after decryption of file systems. I consider this as a bug. The geli decryption script asks for the passphrase which can't of course be input if the kaymap is not set. Handbook §17.12 does not mention the keymap setup. What can I do to

Aw: Re: keymap set after file system decryption

Trond Endrestøl wrote: > I guess we who live outside the US should take into account that PCs > are initialised by firmware to the US keyboard layout and the 437 code > page, courtesy of IBM, 1981. In 1981 I had accepted this. Now it's simply a bug and I

Keyboard language not set before decrypting devices?

Hello, I have encrypted /home and want to decrypt it at boot time with 'geli_devices="da2"' in /etc/rc.conf but the passphrase is not accepted. Is it possible that the keymap is set *after* the decrypting of filesystems? Carsten ___

No X on Dell E6540

Hello, X does not start. For the error message I get (Number of created screens does not match number of detected devices) there are many posts on https://forums.freebsd.org but this URL seems to not work currently. Xorg log is (for dmesg see below): [ 369.089] X.Org X Server 1.17.4

Aw: Re: No X on Dell E6540

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

Aw: Re: No X on Dell E6540

Hello David, > I had a similar issue with my Dell M4800 until I entered BIOS > configuration (vi F12 key at boot), selected "Video," then disabled > "Switchable Graphics." this option is unfortunately not available in "Video" (only display brightness can be set there in my BIOS). Regards,

make .SUFFIXES bug?

Hello, current groff doesn't build on FreeBSD. I had noticed the same issue some months ago on NetBSD and cross checked on FreeBSD and it had worked on FreeBSD. There must have somethig changed since then. How to reproduce: When there is a file "test.1.man" and a makefile: .SUFFIXES:

[Solved] Partitioning on a MBR table disk fails

Hi Rick, thank you for your help! Using gpart in the shell did work well :) Regards, Carsten ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Partitioning on a MBR table disk fails (and destroys my data...)

Hello, I had not been succesful in partitioning and MBR disk for FreeBSD. I have only one free primary partition where I had installed NetBSD and OpenBSD alternatively since many years. The free space on the disk is divided into three parts: one for NetBSD, one for OpenBSD and one left for

Aw: Re: Partitioning on a MBR table disk fails (and destroys my data...)

Rick Macklem wrote: > Did you use "Manual" when it gets to the partitioning screen? > When I've done this, after selecting "Manual MBR" (or whatever it's called, > one or two below "Auto"), it should show you the slices > (what FreeBSD calls the 4 MBR partitions): > - Then

Aw: Re: Aw: Re: Partitioning on a MBR table disk fails (and destroys my data...)

Rick Macklem wrote: > I don`t use it, but gpart is the preferred FreeBSD command. You might try > that instead. Does it work with MBR or only GPT? Anyway, I'll try it. > Well, although installing is always a bit scary, if you don`t touch the > other > slices, I`d delete

Partitioning on a MBR table disk fails (and destroys my data...)

Hello, how is it possible to install FreeBSD in an existing empty MBR partition with type "freebsd"? The installer does not allow this (for unknown reason), it returns the error "no space left". What steps would be necessary to add two freebsd-ufs and one freebsd-swap into the existing

Aw: Re: [RFC] Replace gnu groff in base by heirloom doctools

Steffen Nurpmeso sdao...@yandex.com wrote: It seems you haven't checked at all. It seems to me that e.g. mdoc(7) of n-t-r seems to require quite a bit of work in order to be at all usable. This is not completely true. It is usable, I did check it with all about 7000 manpages in the base of