On Fri, Jan 24, 2014 at 9:52 AM, Thomas Hoffmann wrote:
> On Thu, Jan 23, 2014 at 11:49 AM, Hans Petter Selasky <
> hans.petter.sela...@bitfrost.no> wrote:
>
>> Hi,
>>
>> Can you see if you can snap some keywords of the backtraces, like usb_xxx
>> usbdx_xxx cam scsi or something like that.
>>
>
TB --- 2014-01-25 02:18:18 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2014-01-25 02:18:18 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2014
On 1/24/2014 11:31 AM, Mark Felder wrote:
I agree with the rest of this thread. This is just awful. I'm basically
forced to do source based updates when jumping major versions because
freebsd-update is a nightmare to use.
I've yet to go through a freebsd-update process that didn't require a
ma
Hi John,
seems that your commit 261030 has broken installworld target when the
installation is done on 9.1-RELEASE (and, actually, all releases
before). Installing world fails with the following error:
cd
/stor0/jails/buildhost.kibab.com/usr/home/kibab/repos/freebsd-git/freebsd/etc;
install -N
/
Oh! The NDIS FPU patch is limited to the NDIS module.
Tell you what, I'll get that committed to -HEAD soon. Would you poke
the original author and see if he's willing to work with you and I on
getting this stuff into -HEAD?
-a
___
freebsd-current@free
On Friday, January 24, 2014 3:42:15 pm Ilya Bakulin wrote:
> Hi John,
>
> seems that your commit 261030 has broken installworld target when the
> installation is done on 9.1-RELEASE (and, actually, all releases
> before). Installing world fails with the following error:
>
> cd
> /stor0/jails/buil
Unfortunately, I think there is measurable penalty going to
BSD licensed tools, same system:
http://pastebin.com/BNfhevBa
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Relea
On 2014-01-24 20:31, Mark Felder wrote:
> I agree with the rest of this thread. This is just awful. I'm basically
> forced to do source based updates when jumping major versions because
> freebsd-update is a nightmare to use.
Not tested, but maybe this works.
a) use etcmerge before freebsd-upgrad
On Fri, Jan 24, 2014 at 8:16 PM, Adrian Chadd wrote:
>
> Is i kept up to date with -head changes?
>
> As far as I know it was kept up to date with -head changes.
HI,
>
> Well, someone needs to break the fork up into pieces and submit those.
> The FPU change is a good candidate - but it needs to
On 2014-01-21 15:42, Kevin Oberman wrote:
> On Tue, Jan 21, 2014 at 8:49 AM, John Baldwin wrote:
>
>> On Tuesday, January 21, 2014 10:46:37 am David Chisnall wrote:
>>> On 21 Jan 2014, at 07:13, Antonio Olivares
>> wrote:
On Tue, Jan 21, 2014 at 7:49 AM, Ivan Voras
>> wrote:
> Hi,
>
I agree with the rest of this thread. This is just awful. I'm basically
forced to do source based updates when jumping major versions because
freebsd-update is a nightmare to use.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailm
On 24 January 2014 08:47, Vlad Movchan wrote:
> NDISulator on github (and mirror on gitorious) is a FreeBSD ndis
> module+binaries forked by Paul B. Mahol in 2009 (I've sent Paul's email
> address privately to Adrian).
> Almost every change in this project was made by Paul.
> My part is small - I'
Ah.. my bad its "0x47217" not 21 :P
works:
ndis0: flags=8802 metric 0 mtu 1500
ether ac:81:12:35:79:73
nd6 options=29
media: IEEE 802.11 Wireless Ethernet autoselect
(autoselect )
status: no carrier
On Fri, Jan 24, 2014 at 4:49 PM, Miguel Clara wrote:
> NOTE
NOTE: tried NDISulator
pciconf -lv | grep -i bcm -B2
none2@pci0:13:0:0: class=0x028000 card=0x145c103c chip=0x472714e4
rev=0x01 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM4313 802.11b/g/n Wireless LAN Controller'
# ndisload -p -s /home/user/bcmWireless/bcmwl564.sy
NDISulator on github (and mirror on gitorious) is a FreeBSD ndis
module+binaries forked by Paul B. Mahol in 2009 (I've sent Paul's email
address privately to Adrian).
Almost every change in this project was made by Paul.
My part is small - I've just discovered and fixed several panic/problems.
I'v
On Thu, Jan 23, 2014 at 11:49 AM, Hans Petter Selasky <
hans.petter.sela...@bitfrost.no> wrote:
> Hi,
>
> Can you see if you can snap some keywords of the backtraces, like usb_xxx
> usbdx_xxx cam scsi or something like that.
>
> Else I believe there are some sysctl options to prevent the final r
I've made a switch early.
What gave me some bumps:
- removal of ntfs module
- vorbis-tools-1.4.0_6,3 with ogg123 missing (??)
- ports built on db42
- malloc.conf
- gcc48 entries in libmap.conf (my fault)
- subversion-static looks broken a bit, nls problems
e.g.
$ sudo svn up
Password:
Service u
... who's the author of this? Why aren't they posting updates to
FreeBSD-HEAD so it can be included in the base system?
Does anyone have a contact email for the author, Vadislav?
-a
On 24 January 2014 03:52, Thomas Mueller wrote:
> To Miguel Clara, you might try a USB wireless adapter. I use
To Miguel Clara, you might try a USB wireless adapter. I use Hiro H50191,
driver rsu.
But you would need to do good research to find what the chip is, and which
FreeBSD driver, if any, would it work with, before you buy.
NDISulator looks worth trying. FreeBSD users will want to know if it wor
With r261034, I get the error shown below on one specific box running
kernel/world
11.0-CURRENT #0 r261034: Wed Jan 22 20:14:05 CET 2014 amd64
Another box compiles the same source without any problems (running
kernel/world
11.0-CURRENT #4 r261091: Thu Jan 23 22:46:03 CET 2014 amd64
My buildwo
20 matches
Mail list logo
