From owner-freebsd-hackers Mon Dec 18 6:33: 4 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 18 06:32:59 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 1A3B437B400 for ; Mon, 18 Dec 2000 06:32:58 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id OAA11277; Mon Dec 18 14:30:44 2000 Date: Mon, 18 Dec 2000 14:35:43 +0000 Subject: Re: Message-ID: <20001218143543.C593@freefire.psi-domain.co.uk> References: <78784D0E83CDD411BB580000D11ABE920C88BA@btcexc01.btc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <78784D0E83CDD411BB580000D11ABE920C88BA@btcexc01.btc.adaptec.com>; from scott_long@btc.adaptec.com on Mon, Dec 18, 2000 at 13:10:52 +0000 X-Mailer: Balsa 1.0.0 Lines: 162 From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Cc: freebsd-hackers@freebsd.org Bad-To: "\"Long, Scott\"" Apparently-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, after a cold boot. The machine is dual boot Windows ME (came with the laptop, need it for DVD!!) The output of dmesg is below - should I turn of Plug and Play in the BIOS? Dmesg ----- 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 4.2-RELEASE #2: Sun Dec 17 14:03:20 GMT 2000 jamie@freefire.psi-domain.co.uk:/usr/src/sys/compile/FREEFIRE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 134152192 (131008K bytes) avail memory = 127475712 (124488K bytes) Preloaded elf kernel "kernel" at 0xc031f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031f09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 1.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1040-0x104f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 chip1: port 0x2180-0x218f at device 7.3 on pci0 pcic-pci0: irq 0 at device 8.0 on pci0 pcic-pci1: irq 0 at device 8.1 on pci0 pci0: (vendor=0x125d, dev=0x199a) at 12.0 fxp0: port 0x1000-0x103f mem 0xe8000000-0xe80fffff,0xe8100000-0xe8100fff irq 11 at device 13.0 o n pci0 fxp0: Ethernet address 00:00:f0:65:cf:ef pci0: (vendor=0x11c1, dev=0x0444) at 13.1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> pcic0: at port 0x3e0 iomem 0xd0000 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 pccard: card inserted, slot 0 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 9590MB [19485/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a On 2000.12.18 13:10:52 +0000 "Long, Scott" wrote: > Very odd. Did this happen after a cold boot of the machine? Are you > running any other OS's? It might help if you could send the output of > dmesg. > > Scott > > -----Original Message----- > From: heckfordj@psi-domain.co.uk > Sent: 12/17/00 6:33 AM > > Hi, > > I got hold of you driver, compiled and installed it. > > After booting, I logged in as root and typed: > > # kldload snd_maestro3 > > but this returned the following error message: > > pcm0: at device 12.0 on pci0 > pcm0: Unable to map i/o space > device_probe_and_attach: pcm0 attach returned 6 > > Any ideas on what I am doing wrong?? > > Any help appreciated > > Jamie > > On 2000.12.15 16:47:16 +0000 "Long, Scott" wrote: > > Myself and Darrell Anderson are working on a driver. Check out > > http://people.freebsd.org/~scottl/maestro3 for mine or > > http://www.cs.duke.edu/~anderson/freebsd/maestro3xxx for his. The PCI > id > > mentioned by the original poster (0x199a125d) is supported by this > > driver, > > though I haven't tested it. > > > > > -----Original Message----- > > > From: Michel Talon [mailto:michel@lpthe.jussieu.fr] > > > Sent: Friday, December 15, 2000 9:42 AM > > > To: freebsd-stable@freebsd.org > > > Subject: Re: ESS Sound Driver > > > > > > > > > On Fri, Dec 15, 2000 at 04:10:09PM +0000, Jamie Heckford wrote: > > > > Hi, > > > > > > > > Could anyone offer any guidance on getting the following > > > sound card to work? > > > > > > > > It is in a Samsung GT8700 laptop - and I am using FreeBSD > > > 4.2-RELEASE. > > > > > > > > Windows identifies the card as an ESS Maestro PCI Audio > > > (WDM) - IRQ 5 > > > > > > > I have seen recently a HP laptop with a maestro 3 audio > > > card. I have been > > > able to run the sound card only with the Alsa drivers under Linux. > > > Apparently the FreeBSD drivers are able to run only the > > > maestro 2 and 2E. > > > > > > -- > > > Michel Talon > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message