Re: device otus unknown

On 12 Nov 2018, at 22:03, Adrian Chadd wrote: > yeah, that we'll have to look into.. I was going to say that might be easy: Index: sys/conf/files === --- sys/conf/files (revision 340282) +++ sys/conf/files (working copy) @

Re: Just updated to 12 from11 - did ld change ?

On 12/11/2018 22:12, Dimitry Andric wrote: If you are on amd64, ld is now LLVM's lld. You can check this with "ld -v": $ ld -v LLD 6.0.1 (FreeBSD 335540-125) (compatible with GNU linkers) Ah, yes, I am on amd64 - that would be it then, thanks! Worth menioning in the release notes mayb

Re: Just updated to 12 from11 - did ld change ?

On 12 Nov 2018, at 23:06, Pete French wrote: > > Just trying out the BETA4 version of 12, updating from 11-STABLE. All went > nice and smoothly, but when compiing coe I had to make some tweaks to the > arhuments I am passing to 'ld' when part-linking objects against static > libraries. Did someth

Just updated to 12 from11 - did ld change ?

Just trying out the BETA4 version of 12, updating from 11-STABLE. All went nice and smoothly, but when compiing coe I had to make some tweaks to the arhuments I am passing to 'ld' when part-linking objects against static libraries. Did something chnage here ? Its not on the release notes that I can

Re: device otus unknown

On Mon, Nov 12, 2018 at 09:33:01PM +, tech-lists wrote: On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote: If it's showing up like that then it's not an AR9170 device; it's a broadcom firmware device. :( yeah. In tiny lettering it has "v2" next to the WNDA3100 so this seems to b

Re: device otus unknown

yeah, that we'll have to look into.. -a On Mon, 12 Nov 2018 at 13:33, tech-lists wrote: > On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote: > >If it's showing up like that then it's not an AR9170 device; it's a > >broadcom firmware device. :( > > yeah. In tiny lettering it has "v2

Re: device otus unknown

On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote: If it's showing up like that then it's not an AR9170 device; it's a broadcom firmware device. :( yeah. In tiny lettering it has "v2" next to the WNDA3100 so this seems to be a completely different chipset But what about the otus(4)

emac g4 1.25 GHz retail model won't boot FreeBSD 12 at all.

The CD or DVD show up fine in the device selection screen, but it won’t even boot the disc. What changed from 11.2 to 12.0 in regards to PowerPC Macs that are 32 bit? A much needed answer would be appreciated. Sent from Mail for Windows 10 ___ freebs

Re: Upgrade from 10.4 stable to 11.0 releng fails

COMPAT_FREEBSD10 was indeed missing in my custom kernel config. Now after a reboot the system continues, but then natd failed to start: # /etc/rc.d/natd start Starting natd. natd: unknown interface name xl0 /etc/rc.d/natd: WARNING: failed to start natd While xl0 is up and running: # ifconfig x

Re: device otus unknown

If it's showing up like that then it's not an AR9170 device; it's a broadcom firmware device. :( -a On Mon, 12 Nov 2018 at 12:08, tech-lists wrote: > Hi, > > context: > freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now > with amd64 r340354. > > I have a Netgear WNDA3100

device otus unknown

Hi, context: freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now with amd64 r340354. I have a Netgear WNDA3100 USB wireless key. Its man page has the following: SYNOPSIS To compile this driver into the kernel, place the following lines in your kernel configuration

Re: Upgrade from 10.4 stable to 11.0 releng fails

On Mon, Nov 12, 2018 at 11:39 AM Sven Vermeulen wrote: > 4) make installkernel (using a custom kernel config) > > installkernel gives some warnings with kldxref: > > kldxref /boot/kernel > kldxref: unknown metadata record 4 in file aic.ko > kldxref: unknown metadata record 4 in file atacard.ko >

Re: Upgrade from 10.4 stable to 11.0 releng fails

13.11.2018 1:36, Sven Vermeulen wrote: > I am busy trying to upgrade FreeBSD from 10.4 stable to 11.0 releng with make > world. > > I did the following steps: > > 1) svn update (for /base/releng/11.0) > 2) make buildworld > 3) make buildkernel (using a custom kernel config) > 4) make installker

Upgrade from 10.4 stable to 11.0 releng fails

Hi, I am busy trying to upgrade FreeBSD from 10.4 stable to 11.0 releng with make world. I did the following steps: 1) svn update (for /base/releng/11.0) 2) make buildworld 3) make buildkernel (using a custom kernel config) 4) make installkernel (using a custom kernel config) installkernel g

MSI allocation regression, still to be corrected in HEAD and please MFC before release/12.0 gets branched

Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer: Am 05.06.2018 um 19:54 schrieb Scott Long: … Late in the 11.2 phase, I identified this commit as a regression for MSI (non-x) alloctaion. I have an idea what probably causes the problem here (INTx allocation, although MSI (and MSI-x) capability

Re: Panic (gpf) in early boot after upgrading FreeBSD 10.4 -> 11.2 on Ganeti

On Mon, 12 Nov 2018 01:58:12 -0500, Konstantin Belousov wrote: > On Sun, Nov 11, 2018 at 11:24:48PM -0500, Rob Austein wrote: > > > > panic: general protection fault > > cpuid = 0 > > KDB: stack backtrace: > > #0 0x80b3d587 at kdb_backtrace+0x67 > > #1 0x80af6b2

Re: sendmail blacklistd on 12.0

> I'm using ports/mail/sendmail with blacklistd. > > In 11.2R, it is working good without UseBlacklist option in > sendmail.cf. > After upgrading from 11.2R to 12.0-BETA[34], blacklistd for > sendmail is not working without UseBlacklist option in sendmail.cf. > > Is there any change of be

AN INVESTMENT OFFER.

Greetings, We are international project financiers and we specialize in both start up projects and existing businesses needing funding or Loan for expansion. We are committed to helping businesses develop and succeed. We will like to partner with you/your company should you be interested or may