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 wr

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

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: at device 25.0 (no driver attached) And pciconf lists this: no...@pci0:0:25:0: class=0x02 card=0x8086 chip=0x10ef8086 rev=0x06 hdr=0x00 vendor

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 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

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-cur

[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

[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/c

[head tinderbox] failure on i386/pc98

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/pc98 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/c

ia64 -> panic: ffs_blkfree: freeing free frag

on r205976M ia64 with gmirror, see dmesg here: http://seis.bris.ac.uk/~mexas/freebsd/ia64/rx2600/tzav/dmesg.boot I got this panic: ) at syscall+0x3b0 epc_syscall_return() at epc_syscall_return Mar 31 19:51:51 mech-cluster241 su: mexas to root on /dev/pts/9 dev = mirror/usr, block = 15150194, fs

Re: newfs_msdos and DVD-RAM

on 30/03/2010 18:41 Andriy Gapon said the following: > on 30/03/2010 18:36 Fabian Keil said the following: >> Andriy Gapon wrote: >> >>> on 29/03/2010 23:29 Fabian Keil said the following: Andriy Gapon wrote: > Thus, clearly, it is a fault of a tool that formatted the media for FAT.

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

PseudoCylon wrote: > - Original Message > > >> From: Ganbold >> To: PseudoCylon >> Cc: freebsd-current@freebsd.org >> Sent: Sat, March 27, 2010 7:01:32 AM >> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless >> >> JFYI, I have just tested if_run and works fine on HEAD (i3

Re: [head tinderbox] failure on amd64/amd64

> cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign > -fformat-extensions -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq > -

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

PseudoCylon wrote: > - Original Message > > >> From: Ganbold >> To: PseudoCylon >> Cc: freebsd-current@freebsd.org >> Sent: Sat, March 27, 2010 7:01:32 AM >> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless >> >> JFYI, I have just tested if_run and works fine on HEAD (i3

[head tinderbox] failure on amd64/amd64

TB --- 2010-03-31 12:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-31 12:00:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2010-03-31 12:00:00 - cleaning the object tree TB --- 2010-03-31 12:00:18 - cvsupping the source tree TB --- 2010-03-31 12:00:18 - /usr/bin

[head tinderbox] failure on i386/i386

TB --- 2010-03-31 12:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-31 12:00:00 - starting HEAD tinderbox run for i386/i386 TB --- 2010-03-31 12:00:00 - cleaning the object tree TB --- 2010-03-31 12:00:14 - cvsupping the source tree TB --- 2010-03-31 12:00:14 - /usr/bin/c

[head tinderbox] failure on i386/pc98

TB --- 2010-03-31 12:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-31 12:00:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2010-03-31 12:00:00 - cleaning the object tree TB --- 2010-03-31 12:00:14 - cvsupping the source tree TB --- 2010-03-31 12:00:14 - /usr/bin/c

On fresh current zvol with org.freebsd:swap=on crashes zfs list (PR:145234)

On fresh freebsd-current automatic swap configuration on zvol with org.freebsd:swap=on by /etc/rc.d/zvol doesn't work because zfs list -H -o org.freebsd:swap,name -t volume fails with bus error. To repeat a problem try: # zfs create -V 128m rpool/test # zfs list rpool/test NAME USED AVAIL REFER MO

Re: ATA_CAM-ed mvsata(4) on OpenRD-client

Hi. Norikatsu Shigemura wrote: > I got a OpenRD-client (Marvell 88F6281 SoC), and I'm tring to > make mvsata(4) ATA_CAM, like following: > > But I got following panic, my I help you? > In this time, I attached no devices to SATA/eSATA port. > - - - - - -- - - - - - - - - -