Re: Strange problems with AGP driver & sound.

2000-09-06 Thread Stephen Hocking 

Ok, here's the two dmesg listing from verbose boots, one with the agp code as 
a module, and the other built in.


Stephen




Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Wed Sep  6 17:42:22 CDT 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/bloop
Calibrating clock(s) ... TSC clock: 501156139 Hz, i8254 clock: 1193229 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
Timecounter "TSC"  frequency 501138511 Hz
CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
  Features=0x8021bf
  AMD Features=0x8800
Data TLB: 128 entries, 2-way associative
Instruction TLB: 64 entries, 1-way associative
L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative
L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative
Write Allocate Enable Limit: 128M bytes
Write Allocate 15-16M bytes: Disable
real memory  = 134152192 (131008K bytes)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x003a3000 - 0x07fe5fff, 130297856 bytes (31811 pages)
avail memory = 127025152 (124048K bytes)
bios32: Found BIOS32 Service Directory header at 0xc00fb020
bios32: Entry = 0xfb4a0 (c00fb4a0)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xb4d0
pnpbios: Found PnP BIOS data at 0xc00fc0a0
pnpbios: Entry = f:c0c8  Rev = 1.0
Other BIOS signatures found:
Preloaded elf kernel "kernel.ko" at 0xc038a000.
Preloaded elf module "mga.ko" at 0xc038a0ac.
Preloaded elf module "agp.ko" at 0xc038a148.
Preloaded elf module "drm.ko" at 0xc038a1e4.
nulldev: 
random: 
mem: 
K6-family MTRR support enabled (2 registers)
VESA: information block
56 45 53 41 00 02 ca 6c 00 c0 01 00 00 00 74 69 
00 c0 00 02 05 01 df 6c 00 c0 e6 6c 00 c0 f2 6c 
00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
VESA: 11 mode(s) found
VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974)
VESA: Matrox Graphics Inc.
VESA: Matrox Matrox G400 00
npx0:  on motherboard
npx0: INT 16 interface
i586_bzero() bandwidth = 84090144 bytes/sec
bzero() bandwidth = 119488588 bytes/sec
pcib0:  on motherboard
pci0: physical bus=0
found-> vendor=0x1106, dev=0x0598, revid=0x04
bus=0, slot=0, func=0
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[10]: type 3, range 32, base e000, size 26, enabled
found-> vendor=0x1106, dev=0x8598, revid=0x00
bus=0, slot=1, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=1secondarybus=1
found-> vendor=0x1106, dev=0x0586, revid=0x47
bus=0, slot=7, func=0
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
found-> vendor=0x1106, dev=0x0571, revid=0x06
bus=0, slot=7, func=1
class=01-01-8a, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[20]: type 4, range 32, base 6400, size  4, enabled
found-> vendor=0x1106, dev=0x3040, revid=0x10
bus=0, slot=7, func=3
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
found-> vendor=0x11ad, dev=0x0002, revid=0x20
bus=0, slot=9, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=10
map[10]: type 4, range 32, base 6c00, size  8, enabled
map[14]: type 1, range 32, base eb00, size  8, enabled
pci0:  on pcib0
pcib1:  at device 
1.0 on pci0
pci1: physical bus=1
found-> vendor=0x102b, dev=0x0525, revid=0x04
bus=1, slot=0, func=0
class=03-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=11
map[10]: type 3, range 32, base e800, size 25, enabled
map[14]: type 1, range 32, base e400, size 14, enabled
map[18]: type 1, range 32, base e500, size 23, enabled
pci1:  on pcib1
drm0:  mem 
0xe500-0xe57f,0xe400-0xe4003fff,0xe800-0xe9ff irq 11 at device 0.0 
on pci1
info: [drm] The mga drm module requires the agp module to function correctly
Please load the agp module before you load the mga module
device_probe_and_attach: drm0 attach returned 12
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port 0x6400-0x640f at device 7.1 on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x6400
ata0: mask=03 status0=50 status1=00
ata0: mask=03 status0=50 status1=00
ata0: devices = 0x1
ata0: at 0x1f0 irq 14 on atapci0
ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x6408
ata1: mask=03 status0=50 status1=00
ata1: mask=03 status0=50 status1=00
ata1: devices = 0x1
ata1: at 0x170 irq 15 on atapci0
dc0:

Re: Strange problems with AGP driver & sound.

2000-09-06 Thread Stephen Hocking 

> > 
> > With very recent current sources, the agp driver doesn't probe when loaded as 
> > a module, but works OK when compiled into the kernel.
> 
> Oh. I thought that was only a problem in 4.x. Can I see a verbose bootlog
> for a kernel where this is a problem.
> 

OK -  I'm away from the machine at the moment (it's back at home) - I'll boot 
the old kernel verbosely and send the results back. Mind you, when I start to 
fire up the X server and have it load up DRI & glx modules, it crashes the 
machine. The mga module (when I preload it) complains that it needs the agp 
module in the bootup messages.


> > 
> > However, when compiled into the kernel, it seems to mess up the sound driver 
> > (pcm, crystal cs23x) such that no sound or garbled sound at a low volume comes 
> > out. Has anyone else seen this? I'm using the mga driver from the XFree86 cvs 
> > tree to do 3D work, which is why I'm using the AGP driver.
> 
> No idea about this one.
> 

Yeah - I think there's some warts lurking in the sound code somewhere. It's odd, 
becuase the interrupts from the sound device are still coming in at the expected rate 
- just not any sound, like it's bufferring from some random chunk of clear memory.


Stephen
Stephen
-- 
  The views expressed above are not those of PGS Tensor.

"We've heard that a million monkeys at a million keyboards could produce
 the Complete Works of Shakespeare; now, thanks to the Internet, we know
 this is not true."Robert Wilensky, University of California




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Strange problems with AGP driver & sound.

2000-09-06 Thread Doug Rabson 

On Wed, 6 Sep 2000, Stephen Hocking wrote:

> 
> With very recent current sources, the agp driver doesn't probe when loaded as 
> a module, but works OK when compiled into the kernel.

Oh. I thought that was only a problem in 4.x. Can I see a verbose bootlog
for a kernel where this is a problem.


> 
> However, when compiled into the kernel, it seems to mess up the sound driver 
> (pcm, crystal cs23x) such that no sound or garbled sound at a low volume comes 
> out. Has anyone else seen this? I'm using the mga driver from the XFree86 cvs 
> tree to do 3D work, which is why I'm using the AGP driver.

No idea about this one.

-- 
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 20 8348 3944




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message