Re: SVN r296272 breaks virtualbox

2016-03-01 Thread Howard Su
On Tue, Mar 1, 2016 at 10:28 PM Kurt Jaeger wrote: > Hi! > > > > > The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods: > [...] > > Then the port needs to be patched? It's been using an API deprecated > > for the last 15 years. A simple >

Re: SVN r296272 breaks virtualbox

2016-03-01 Thread Kurt Jaeger
Hi! > > > The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods: [...] > Then the port needs to be patched? It's been using an API deprecated > for the last 15 years. A simple s/taskqueue_enqueue_fast/taskqueue_enqueue/ > will fix it. A patch is possible if a new

mounting CIFS share (tcp/445) with FreeBSD and mount_smbfs(8)

2016-03-01 Thread O. Hartmann
Hello list. I need to mount a CIFS share from windows server 2012 r2 via CIFS, tcp/445 as NetBIOS service (tcp/139) has been deprecated due to serious vulnerability issues. Until the disabling of NetBIOS and tcp/139 we used successfully autofs and mount_smbfs. this is no longer working. I

Re: CAM Shingled Disk support patches available

2016-03-01 Thread Scott Long
Hi Ken, I’m against changing the function signature of scsi_ata_pass_16(). Even if you manage to get things right with symbol versioning, it still leads to problems of code compatibility. Maybe pre-existing binaries will work, but source code will forever have to include an #if

Re: SVN r296272 breaks virtualbox

2016-03-01 Thread Kubilay Kocak
On 2/03/2016 9:29 AM, Michael Butler wrote: > The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods: > > Mar 1 16:54:36 toshi kernel: vboxdrv: fAsync=0 offMin=0x914 offMax=0x151c > Mar 1 16:54:36 toshi kernel: link_elf_obj: symbol > taskqueue_enqueue_fast undefined > Mar 1

Re: Bay Trail 32bit UEFI

2016-03-01 Thread Lundberg, Johannes
CherryTrail devices/boards with 64bit UEFI are already out. Upgrading the hardware is one solution (I did). I never did try FreeBSD on BayTrail but for running Linux on BayTrail I used special built Grub that was 32bit but could load 64bit OS. Could this kind of Grub boot a 64bit FreeBSD, I

Re: Bay Trail 32bit UEFI

2016-03-01 Thread John Baldwin
On Sunday, February 28, 2016 07:00:06 AM Joe Holden wrote: > Hi all, > > Apologies if this is the wrong list... > > Is there any plan to support booting FreeBSD on 32bit UEFI systems (with > or without 64bit kernel/userland)? Obviously there is no i386 efi loader > currently so neither is

Re: SVN r296272 breaks virtualbox

2016-03-01 Thread John Baldwin
On Wednesday, March 02, 2016 12:42:05 AM Ivan Klymenko wrote: > On Tue, 1 Mar 2016 17:29:37 -0500 > Michael Butler wrote: > > > The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods: > > > > Mar 1 16:54:36 toshi kernel: vboxdrv: fAsync=0 offMin=0x914

Re: hint.uart.1 in device.hints causes freeze at boot

2016-03-01 Thread John Baldwin
On Friday, February 26, 2016 11:08:37 PM Warner Losh wrote: > On Fri, Feb 26, 2016 at 6:49 PM, Marcel Moolenaar wrote: > > Any reason not to add .disabled=1 to all the entries that are there, > with the possible exception of uart.0? At least for i386 and amd64? > Bonus points

Re: WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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: CAM Shingled Disk support patches available

2016-03-01 Thread Kenneth D. Merry
I have a new set of SMR patches available. (See the original message below for a more detailed description of what these patches do.) The primary change is to add library versioning to libcam so that we can change the function prototype of scsi_ata_pass_16() in a way that won't break existing

Re: SVN r296272 breaks virtualbox

2016-03-01 Thread Ivan Klymenko
On Tue, 1 Mar 2016 17:29:37 -0500 Michael Butler wrote: > The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods: > > Mar 1 16:54:36 toshi kernel: vboxdrv: fAsync=0 offMin=0x914 > offMax=0x151c Mar 1 16:54:36 toshi kernel: link_elf_obj: symbol >

Re: WLAN hardware not recognized

2016-03-01 Thread Oliver Pinter
On 3/1/16, Carsten Kunze wrote: > 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? > >

SVN r296272 breaks virtualbox

2016-03-01 Thread Michael Butler
The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods: Mar 1 16:54:36 toshi kernel: vboxdrv: fAsync=0 offMin=0x914 offMax=0x151c Mar 1 16:54:36 toshi kernel: link_elf_obj: symbol taskqueue_enqueue_fast undefined Mar 1 16:54:36 toshi kernel: linker_load_file: Unsupported file type

Re: WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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

Re: Re: WLAN hardware not recognized

2016-03-01 Thread Adrian Chadd
Right, you need to create the interface: ifconfig wlan0 create wlandev iwn0 then run wpa_spuplicant (or do it all in /etc/rc.conf .. :) -a On 1 March 2016 at 14:13, Carsten Kunze wrote: > Adrian Chadd wrote: > >> sysctl net.wlan.devices >>

Aw: Re: WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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

2016-03-01 Thread Adrian Chadd
sysctl net.wlan.devices iwn0 no longer shows up in ifconfig -a . -a On 1 March 2016 at 13:42, 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

Re: WLAN hardware not recognized

2016-03-01 Thread Conrad Meyer
"[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? On Tue, Mar 1, 2016 at 1:01 PM, Carsten Kunze wrote: > Conrad Meyer wrote: > >>

Re: mounting CIFS share (tcp/455) with FreeBSD and mount_smbfs(8)

2016-03-01 Thread Reko Turja
-Original Message- From: O. Hartmann Subject: mounting CIFS share (tcp/455) with FreeBSD and mount_smbfs(8) > > I need to mount a CIFS share from windows server 2012 r2 via CIFS, tcp/445 as > NetBIOS > service (tcp/139) has been deprecated due to serious vulnerability issues. > . > .

Re: WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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

mounting CIFS share (tcp/455) with FreeBSD and mount_smbfs(8)

2016-03-01 Thread O. Hartmann
I need to mount a CIFS share from windows server 2012 r2 via CIFS, tcp/445 as NetBIOS service (tcp/139) has been deprecated due to serious vulnerability issues. Until the disabling of NetBIOS and tcp/139 we used successfully autofs and mount_smbfs. this is no longer working. I tried to force

Re: WLAN hardware not recognized

2016-03-01 Thread Conrad Meyer
kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw. On Tue, Mar 1, 2016 at 12:48 PM, Carsten Kunze wrote: > 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 >

Re: WLAN hardware not recognized

2016-03-01 Thread Larry Rosenman
On 2016-03-01 14:48, Carsten Kunze wrote: 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... ___

Re: WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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

Re: continuous stream of writes?

2016-03-01 Thread Matthias Apitz
El día Tuesday, March 01, 2016 a las 08:50:05AM -0600, Eric van Gyzen escribió: > >> The I/O mode of "top" might be useful: > >> > >> top -m io > > > > Well that's different .. KDE konsole .. why on earth .. ? > > Now try ktrace, fstat, and procstat. See the man pages for usage. Or as

Re: Aw: Re: WLAN hardware not recognized

2016-03-01 Thread Larry Rosenman
On 2016-03-01 12:23, Carsten Kunze wrote: 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

Aw: Re: WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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

Re: Dropping some locales/encodings?

2016-03-01 Thread Andrey Chernov
On 01.03.2016 12:54, Baptiste Daroussin wrote: >> What benefit does it bring to remove an already existing locale? > > The benefit is the fact we have no source for those and collation for one are > wrong for those. (We have added proper collation support in head). Unicode mapping for CP1251

Re: WLAN hardware not recognized

2016-03-01 Thread Joe Nosay
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? On Tue, Mar 1, 2016 at 10:47 AM, Carsten Kunze wrote: > Hello, > > the WLAN

FreeBSD_HEAD_i386 - Build #2480 - Fixed

2016-03-01 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #2480 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2480/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2480/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2480/console Change summaries: No

WLAN hardware not recognized

2016-03-01 Thread Carsten Kunze
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)

Re: continuous stream of writes?

2016-03-01 Thread Eric van Gyzen
On 03/01/2016 08:45, Michael Butler wrote: > On 03/01/16 09:41, Eric van Gyzen wrote: >> On 03/01/2016 08:22, Michael Butler wrote: >>> On an otherwise idle machine, I now see a continuous stream of writes to >>> disk. I've only noted this over the last couple of weeks but this will >>> not be

Re: continuous stream of writes?

2016-03-01 Thread Michael Butler
On 03/01/16 09:41, Eric van Gyzen wrote: > On 03/01/2016 08:22, Michael Butler wrote: >> On an otherwise idle machine, I now see a continuous stream of writes to >> disk. I've only noted this over the last couple of weeks but this will >> not be welcome behaviour on an SSD .. >> >> How do I find

Re: continuous stream of writes?

2016-03-01 Thread Eric van Gyzen
On 03/01/2016 08:22, Michael Butler wrote: > On an otherwise idle machine, I now see a continuous stream of writes to > disk. I've only noted this over the last couple of weeks but this will > not be welcome behaviour on an SSD .. > > How do I find the source of these writes? > > >

Testing an importing OF PCI implementations patch

2016-03-01 Thread Marcin Mazurek
Hello, I am looking for a testers for a patch to import portions of the PowerPC and Sparc64 OF PCI implementations. This extracts common code from PPC's and Sparc64's ofw_pci and moves that to general dev/ofw_pci files. It is currently building successfully on every architecture. I tested it on

continuous stream of writes?

2016-03-01 Thread Michael Butler
On an otherwise idle machine, I now see a continuous stream of writes to disk. I've only noted this over the last couple of weeks but this will not be welcome behaviour on an SSD .. How do I find the source of these writes? imb@toshi:/home/imb> iostat 10 ttyada0

Re: Dropping some locales/encodings?

2016-03-01 Thread Baptiste Daroussin
On Tue, Mar 01, 2016 at 10:58:37AM +0200, Daniel Kalchev wrote: > > > On 1.03.2016 г., at 5:45, Sergey Manucharian wrote: > > > > Excerpts from Andrey Chernov's message from Tue 01-Mar-16 05:47: > >> On 01.03.2016 2:23, Baptiste Daroussin wrote: > >>> > >>> I can properly

Re: Dropping some locales/encodings?

2016-03-01 Thread Daniel Kalchev
> On 1.03.2016 г., at 5:45, Sergey Manucharian wrote: > > Excerpts from Andrey Chernov's message from Tue 01-Mar-16 05:47: >> On 01.03.2016 2:23, Baptiste Daroussin wrote: >>> >>> I can properly generate almost any of the said locales/encodings but a few >>> that >>> I would

Re: Dropping some locales/encodings?

2016-03-01 Thread Baptiste Daroussin
On Tue, Mar 01, 2016 at 05:47:25AM +0300, Andrey Chernov wrote: > On 01.03.2016 2:23, Baptiste Daroussin wrote: > > Hi all, > > > > I have updated few month ago the locales to cldr v27.0.1. I would like to > > simplify the generation of those locales from cldr to POSIX locales that we > > do > >

Re: Dropping some locales/encodings?

2016-03-01 Thread Baptiste Daroussin
On Mon, Feb 29, 2016 at 08:41:08PM -0700, Sergey Manucharian wrote: > Excerpts from Baptiste Daroussin's message from Tue 01-Mar-16 00:23: > > > > I would like to remove (provided that unicode version are available) > > > > Here is the list of locales/encodings: > > > > be_BY.CP1251 > >

Re: Touchscreen support (was Re: new computer, strange usb messages at boot)

2016-03-01 Thread Sergey V. Dyatko
On Mon, 22 Feb 2016 17:51:00 +0100 Hans Petter Selasky wrote: > On 02/22/16 17:39, Anthony Jenkins wrote: > > > > > > On 02/22/2016 02:11 AM, Hans Petter Selasky wrote: > >> On 02/22/16 03:16, Anthony Jenkins wrote: > >>> Yes. I have an eGalax touchscreen and it's doing