On 11/15/12 5:40 AM, Ivan Voras wrote:
> On 15/11/2012 11:16, Andriy Gapon wrote:
>> on 14/11/2012 23:56 Russell Cattelan said the following:
>>> This has been sitting on my plate for a while and I would like to get some
>>> more feedback / testing on this feature.
&
On 7/2/12 10:03 AM, Alexander Kabaev wrote:
> On Mon, Jul 02, 2012 at 02:12:20AM -0400, Christoph Hellwig wrote:
>> On Sun, Jul 01, 2012 at 03:52:05PM +0200, Attilio Rao wrote:
>>> anything by SoC involved people about NTFS and certainly I don't see a
>>> plan to get XFS locked.
>>
>> Stupid questi
On 7/2/12 1:12 AM, Christoph Hellwig wrote:
> On Sun, Jul 01, 2012 at 03:52:05PM +0200, Attilio Rao wrote:
>> anything by SoC involved people about NTFS and certainly I don't see a
>> plan to get XFS locked.
>
> Stupid question, but what amount of locking does XFS in FreeBSD still
> need? I'm one
p=0x71138086 rev=0x02
hdr=0x00
ahc0@pci0:11:0: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00
hdr=0x00
ahc1@pci0:11:1: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00
hdr=0x00
fxp0@pci0:13:0: class=0x02 card=0x000c8086 chip=0x12298086 rev=0x08
hdr=0x00
--
Russell Cattelan
[EMAI
Ollivier Robert wrote:
> According to Kenneth Wayne Culver:
> > This is the patch to make my soundcard, a Creative Ensoniq AudioPCI (an
> > es1371 chip, device id 0x58801274 rev 0x02). Can someone commit it please?
>
> Done.
There is a problem with that patch.
I'm not sure if there are older 137
n as to when the kernel stopped booting.
Any suggestions as to which pieces of code to go look at would be appreciated.
>
>
> --
> -- David ([EMAIL PROTECTED])
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body
/kernel: wi0: tx buffer allocation failed
Mar 30 23:54:19 lupo /kernel: pid 85 (routed), uid 0: exited on signal
11 (co
re dumped)
Mar 30 23:54:19 lupo /kernel: wi0: xmit failed
Mar 30 23:54:24 lupo /kernel: wi0: device timeout
Mar 30 23:54:24 lupo /kernel: wi0: tx buffer allocation failed
--
Russell
nse about this is I have tried forcing mono on mpg123 and
> xmms and they both still work fine.
>
> So if anyone has any ideas, please shoot them to me. Otherwise I will
> continue my quest to figure out why this is broke.
>
> Greg
>
> --
> Greg Rumple
> [EMAIL PR
This started sometime after Jan06.
I have build a current kernel but Jan06 aic7xxx directory.
panic: ahc0: brkadrint, Scratch or SCB Memory Parity Error at seqaddr = 0x0
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
0
> iicbb0: on bti2c0
> iicbus0: on iicbb0 master-only
> smbus0: on bti2c0
> bktr0: Hauppauge Model 6 A M
> bktr0: Detected a MSP3430G-A1 at 0x80
> Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo.
> pci0: unknown card (vendor=0x109e, d
Thomas Veldhouse wrote:
> Does the newpcm system support the Sound Blaster 128 PCI card (ESS1371
> chipset)? I am aware of a pcm dirver for it in STABLE, but I have not
> tried it.
The only major problems have been with certain ASUS motherboards and
some of the newer PCI128's. (the card freezes
Jeroen Ruigrok/Asmodai wrote:
> -On [19991201 20:01], Russell Cattelan ([EMAIL PROTECTED]) wrote:
> >Dag-Erling Smorgrav wrote:
> >> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
> >> get to work with newpcm.
>
> >What
Dag-Erling Smorgrav wrote:
> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
> get to work with newpcm. It shows up like this in dmesg:
>
> pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5
>
> and in 'pciconf -l':
>
> none0@pci0:10:0:class=0x040100 card=0x
Mark Hittinger wrote:
> Hey per request I'm reporting some ep0 breakage in today's -current. I have
> an etherlink III 3c509B and the probing appears correct.
>
> Sequence of events boot -s
> # ifconfig ep0 inet 192.168.18.200
> (PC hangs)
>
> More lat
.src4.patch
Thomas Stromberg wrote:
> I've been using the Esoniq 1371 Driver from
> http://www.freebsd.org/~ghelmer/es1371/ (written by Russell Cattelan?)
> on my 4.0-CURRENT box for a few weeks now. It's just a hack replacement
> for es1370.c/es1370_reg.h, but it worked fin
en I'm done it won't be a "hack" and it can be committed.
--
Russell Cattelan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Russell Cattelan wrote:
> I haven't been able to track down exactly where this
> is occuring, but disabling pcm allows eliminates the crash.
>
> The build is current as of Sun 18th.
>
> The one strange thing about this box, it has
> two sounds cards. A build in Yamaha O
I haven't been able to track down exactly where this
is occuring, but disabling pcm allows eliminates the crash.
The build is current as of Sun 18th.
The one strange thing about this box, it has
two sounds cards. A build in Yamaha OPL-3 (really really crappy)
and Ensoniq AudioPCI 1371 (very hack
18 matches
Mail list logo