Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, May 30, 2010 at 02:48:13AM +0800, datastream datastream.freecity wrote: > > http://www.nvnews.net/vbulletin/showthread.php?t=150719 > NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. Hi, I did the following: - updated r208649 - applied following patch to nvidia-

Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

>Hi, with yesterday's CURRENT my bwn works partially. > >this is my hardware >siba_bwn0 at pci0:4:0:0:class=0x028000 card=0x04b514e4 chip=0x431514e4 >rev=0x01 hdr=0x00 >vendor = 'Broadcom Corporation' >device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' >class =

Re: clangBSD build error on r208621

On Sat, May 29, 2010 at 11:31:52PM +0900, Norikatsu Shigemura wrote: > Hi rdivacky. > > On Sat, 29 May 2010 02:17:41 +0900 > Norikatsu Shigemura wrote: > > error: unknown argument: '-ferror-limit' > > mkdep: compile failed > > Do you have any idea? Of cause I set following environment: > > -

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity wrote: > > On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: >> >> On 05/26/10 09:51, Kostik Belousov wrote: >>> >>> I did a quick glance over the driver, try this: >>> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.pat

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >> >> I did a quick glance over the driver, try this: >> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch >> I did no

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I

Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))

On 05/29/10 03:54, b. f. wrote: On 5/29/10, Rui Paulo wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 toni

Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

Hi, with yesterday's CURRENT my bwn works partially. this is my hardware siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network it work

Re: clangBSD build error on r208621

Hi rdivacky. On Sat, 29 May 2010 02:17:41 +0900 Norikatsu Shigemura wrote: > error: unknown argument: '-ferror-limit' > mkdep: compile failed > Do you have any idea? Of cause I set following environment: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > - -

[TESTING]: ClangBSD branch needs testing before the import to HEAD

hi, ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to import into HEAD in roughly a week. We would like the initial import to be as painless as possible and therefore we ask you to test ClangBSD to assure that the revision we are importing does not have some really embar

Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))

On 5/29/10, Rui Paulo wrote: > > On 29 May 2010, at 05:39, b. f. wrote: > >> On 5/28/10, Doug Barton wrote: >>> On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I

Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))

On 29 May 2010, at 05:39, b. f. wrote: > On 5/28/10, Doug Barton wrote: >> On 5/28/2010 4:50 PM, b. f. wrote: >>> >>> I can't see any problems when using WPA2 with AES on r208606 i386 with >>> uath(4). I'm updating this machine to r208630 tonight, and if I >>> encounter problems with the later

Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.

Just to prefix with my config: FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #7: Sat May 29 11:20:54 EST 2010 r...@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64 Current source tree was csupped about half an hour ago. I don't think that my hardware has gone dodgy: everything