headers
FreeBSD Tinderbox | 1 Apr 2010 01:01
Picon
Favicon

[head tinderbox] failure on i386/i386

TB --- 2010-03-31 21:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-31 21:55:00 - starting HEAD tinderbox run for i386/i386
TB --- 2010-03-31 21:55:00 - cleaning the object tree
TB --- 2010-03-31 21:55:21 - cvsupping the source tree
TB --- 2010-03-31 21:55:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile
TB --- 2010-03-31 21:55:52 - building world
TB --- 2010-03-31 21:55:52 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-31 21:55:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-31 21:55:52 - TARGET=i386
TB --- 2010-03-31 21:55:52 - TARGET_ARCH=i386
TB --- 2010-03-31 21:55:52 - TZ=UTC
TB --- 2010-03-31 21:55:52 - __MAKE_CONF=/dev/null
TB --- 2010-03-31 21:55:52 - cd /src
TB --- 2010-03-31 21:55:52 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 31 21:55:52 UTC 2010
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
>>> World build completed on Wed Mar 31 22:54:58 UTC 2010
TB --- 2010-03-31 22:54:58 - generating LINT kernel config
TB --- 2010-03-31 22:54:58 - cd /src/sys/i386/conf
TB --- 2010-03-31 22:54:58 - /usr/bin/make -B LINT
(Continue reading)

Permalink | Reply | 0 comments |
headers
FreeBSD Tinderbox | 1 Apr 2010 01:27
Picon
Favicon

[head tinderbox] failure on amd64/amd64

TB --- 2010-03-31 21:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-31 21:55:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-03-31 21:55:00 - cleaning the object tree
TB --- 2010-03-31 21:55:26 - cvsupping the source tree
TB --- 2010-03-31 21:55:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2010-03-31 21:55:52 - building world
TB --- 2010-03-31 21:55:52 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-31 21:55:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-31 21:55:52 - TARGET=amd64
TB --- 2010-03-31 21:55:52 - TARGET_ARCH=amd64
TB --- 2010-03-31 21:55:52 - TZ=UTC
TB --- 2010-03-31 21:55:52 - __MAKE_CONF=/dev/null
TB --- 2010-03-31 21:55:52 - cd /src
TB --- 2010-03-31 21:55:52 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 31 21:55:52 UTC 2010
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
>>> stage 5.1: building 32 bit shim libraries
>>> World build completed on Wed Mar 31 23:21:18 UTC 2010
TB --- 2010-03-31 23:21:18 - generating LINT kernel config
TB --- 2010-03-31 23:21:18 - cd /src/sys/amd64/conf
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tom Uffner | 1 Apr 2010 03:56
Favicon

Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]

Michael Butler wrote:

> This breaks most (if not all) of the QT4-dependent ports for the lack of
> a definition of "off64_t".

it also breaks multimedia/mplayer, graphics/ImageMagick, and
print/ghostscript8 & everything that depends on it.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 11 comments |
headers
Xin LI | 1 Apr 2010 05:51
Picon

Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]

On Wed, Mar 31, 2010 at 6:56 PM, Tom Uffner <tom <at> uffner.com> wrote:
> Michael Butler wrote:
>
>> This breaks most (if not all) of the QT4-dependent ports for the lack of
>> a definition of "off64_t".
>
> it also breaks multimedia/mplayer, graphics/ImageMagick, and
> print/ghostscript8 & everything that depends on it.

Just because they used to compile DOES NOT mean they were right.  It's
NOT right to define _LARGEFILE64_SOURCE on FreeBSD, see:

http://www.delorie.com/gnu/docs/glibc/libc_13.html

Cheers,
--

-- 
Xin LI <delphij <at> delphij.net> http://www.delphij.net
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 10 comments |
headers
David Ehrmann | 1 Apr 2010 08:29
Picon

Intel H55 and em0

I recently picked up a H55-based motherboard, and the ethernet interface 
isn't autodetected.  dmesg lists it as the following:

pci0: <network, ethernet> at device 25.0 (no driver attached)

And pciconf lists this:

none1 <at> pci0:0:25:0:      class=0x020000 card=0x00008086 chip=0x10ef8086 
rev=0x06 hdr=0x00
    vendor     = 'Intel Corporation'
    class      = network
    subclass   = ethernet

I'm actually not sure it's an em device, but it's definitely gigabit, 
and googling suggests that others have recently run into the same issue.

Since I'll probably have to recompile, is this currently working in 
recent builds of 8.0?  This was just a vanilla 8.0 release image.  Would 
some simple change tell the driver to recognize this card?

Thanks in advance.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 7 comments |
headers
Jack Vogel | 1 Apr 2010 08:39
Picon

Re: Intel H55 and em0

The device subfamily on those motherboards is called PCH, and its only in
the em driver as of
last December, The CVS delta of if_em is 1.27. You can either update to
STABLE/8 or CURRENT.
If you wish to just pull the e1000 driver directory it should work fine in
8.0 RELEASE also.

Cheers,

Jack

On Wed, Mar 31, 2010 at 11:29 PM, David Ehrmann <ehrmann <at> gmail.com> wrote:

> I recently picked up a H55-based motherboard, and the ethernet interface
> isn't autodetected.  dmesg lists it as the following:
>
> pci0: <network, ethernet> at device 25.0 (no driver attached)
>
> And pciconf lists this:
>
> none1 <at> pci0:0:25:0:      class=0x020000 card=0x00008086 chip=0x10ef8086
> rev=0x06 hdr=0x00
>   vendor     = 'Intel Corporation'
>   class      = network
>   subclass   = ethernet
>
>
> I'm actually not sure it's an em device, but it's definitely gigabit, and
> googling suggests that others have recently run into the same issue.
>
(Continue reading)

Permalink | Reply | 6 comments |
headers
Jack Vogel | 1 Apr 2010 08:43
Picon

Re: Intel H55 and em0

OH, as to my last statement, the code in CURRENT will NOT work on 8.0
RELEASE,
it would require a change to sys/conf/files, and it also has a fix in the
stack that is not
in RELEASE. SO taking the latest would require you take the whole tree.

Jack

On Wed, Mar 31, 2010 at 11:39 PM, Jack Vogel <jfvogel <at> gmail.com> wrote:

> The device subfamily on those motherboards is called PCH, and its only in
> the em driver as of
> last December, The CVS delta of if_em is 1.27. You can either update to
> STABLE/8 or CURRENT.
> If you wish to just pull the e1000 driver directory it should work fine in
> 8.0 RELEASE also.
>
> Cheers,
>
> Jack
>
>
>
> On Wed, Mar 31, 2010 at 11:29 PM, David Ehrmann <ehrmann <at> gmail.com> wrote:
>
>> I recently picked up a H55-based motherboard, and the ethernet interface
>> isn't autodetected.  dmesg lists it as the following:
>>
>> pci0: <network, ethernet> at device 25.0 (no driver attached)
>>
(Continue reading)

Permalink | Reply | 3 comments |
headers
PseudoCylon | 1 Apr 2010 12:47
Picon
Favicon

Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

----- Original Message ----
> From: Ganbold <ganbold <at> gmail.com>
> To: PseudoCylon <moonlightakkiy <at> yahoo.ca>
> Cc: freebsd-current <at> freebsd.org
> Sent: Wed, March 31, 2010 8:08:29 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Does stock run(4) support hostap mode yet?

No. There were some bugs and I thought I fixed them. So, I called for test. It seems the driver is working on
x86, but not on mips. hostap mode should work on your other computer with i386.

I'm still working on patch. It panics where there wasn't any changes made. Strange...

AK

      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
http://ca.toolbar.yahoo.com.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 26 comments |
headers
David Ehrmann | 1 Apr 2010 17:02
Picon

Re: Intel H55 and em0

Thanks.  I'll give STABLE/8 a try.

Jack Vogel wrote:
> OH, as to my last statement, the code in CURRENT will NOT work on 8.0 
> RELEASE,
> it would require a change to sys/conf/files, and it also has a fix in 
> the stack that is not
> in RELEASE. SO taking the latest would require you take the whole tree.
>
> Jack
>
>
> On Wed, Mar 31, 2010 at 11:39 PM, Jack Vogel <jfvogel <at> gmail.com 
> <mailto:jfvogel <at> gmail.com>> wrote:
>
>     The device subfamily on those motherboards is called PCH, and its
>     only in the em driver as of
>     last December, The CVS delta of if_em is 1.27. You can either
>     update to STABLE/8 or CURRENT.
>     If you wish to just pull the e1000 driver directory it should work
>     fine in 8.0 RELEASE also.
>
>     Cheers,
>
>     Jack
>
>
>
>     On Wed, Mar 31, 2010 at 11:29 PM, David Ehrmann <ehrmann <at> gmail.com
>     <mailto:ehrmann <at> gmail.com>> wrote:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Gellekum | 1 Apr 2010 17:30
Picon
Picon

Re: Intel H55 and em0

Jack Vogel <jfvogel <at> gmail.com> wrote:
> The device subfamily on those motherboards is called PCH, and its only in
> the em driver as of
> last December, The CVS delta of if_em is 1.27. You can either update to
> STABLE/8 or CURRENT.
> If you wish to just pull the e1000 driver directory it should work fine in
> 8.0 RELEASE also.

8-STABLE doesn't work for me. The ethernet device is not recognized, and I get warnings about interrupt
storms on irq19 (atapci1), which I don't see with 8-RELEASE. That might be a matter of missing diagnostics
in the release kernel (the numbers from 'vmstat -i' seem to suggest this).

The board is an Intel DH55HC with an i3-530. Sources for -STABLE checked out this morning; I simply built a
GENERIC kernel.

tg
--

-- 
Sicherer, schneller und einfacher. Die aktuellen Internet-Browser -
jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |

Gmane