From owner-freebsd-multimedia Tue Feb 13 23: 0:14 2001 Delivered-To: freebsd-multimedia@freebsd.org Received: from mukappa.home.com (c576194-a.saltlk1.ut.home.com [65.5.60.246]) by hub.freebsd.org (Postfix) with ESMTP id 8F30437B491 for ; Tue, 13 Feb 2001 23:00:08 -0800 (PST) Received: from mukappa.home.com (tmlifo@localhost.home.com [127.0.0.1]) by mukappa.home.com (8.11.1/8.11.1) with SMTP id f1DGAXS70462 for ; Tue, 13 Feb 2001 09:10:33 -0700 (MST) (envelope-from mupi@mknet.org) From: Mike Porter Reply-To: mupi@mknet.org To: freebsd-multimedia@freebsd.org Subject: Fwd: BSD not finding ESS 1878 sound chip... Date: Tue, 13 Feb 2001 09:10:30 -0700 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01021309103000.66888@mukappa.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Having originally posted this to -questions, becuase I don't think it is directly multi-media related, and gotten a grand total of 0 responses, I thought I would try it over here, maybe somone else has run into this before? mike - ---------- Forwarded Message ---------- Subject: BSD not finding ESS 1878 sound chip... Date: Sat, 10 Feb 2001 15:17:04 -0700 From: Mike Porter To: freebsd-questions@freebsd.org - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an older ARM laptop that I have been beating my head against the wall trying to install BSD. Most everything works, including I finally got Xwindows to run after tweaking about 19 different settings, however I have as yet had no luck with the built-in ESS sound. I have built several kernels, finally resorting to using a kernel with userconfig, intro_userconfig, and visual_userconfig defined to I could verify the presence of the pcm driver, which according to HARDWARE.TXT /should/ support the ESS 1878 which is what this laptop claims to have. Userconfig does show the pcm driver in memory, but that's it. there is no "pcm0:" line while booting, (or in dmesg afterwards, either). The only clue I can come up with is the following lines from dmesg: Copyright (c) 1992-2001 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-STABLE #2: Wed Feb 7 19:19:47 MST 2001 mupi@xxx.yyy.zzz:/usr/obj/usr/src/sys/AUDIO2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (199.31-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 33554432 (32768K bytes) avail memory = 29417472 (28728K bytes) pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "kernel" at 0xc0355000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip1: at device 1.0 on pci0 pnpbios: bad pnpbios checksum? That shouldn't affect the multimedia stuff, should it? but the real interesting line is the chip1 line.... isn't 8086 intel? but what is device 1234? anybody? My best guess is that the ESS chip is somehow "hiding" behind this chip, and since nothing is loading for it, pcm never has a chance to see it. (unless it is related to the bad pnpbios checksum?) I know it isn't the ISA insterface, because 1) I get the following output 7 lines further down: isa0: on motherboard fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 (followed by several typically ISA-mounted things like keyboard, mouse, generic vga interface, all stuff I get on my desktop machine.) am I missing something obvious? My first thought was a pci-isa bridge, but it seems to be finding that OK, or at least, otherwise working it OK. Is it possible that the ESS is really an "ESS compatible" sound card built into the Intel chipset, and that's why it isn't finding it ( i guess in that case I could add the appropriate ID string to the appropriate place in the pcm files, and it might work?) have I asked enough questions yet for one email? <(}: At least they are all related to the same issue. TIA, mike - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqFveAACgkQZ7GovTQbIm5KnwCfXYBZlcmMkEXklw2F3jiaRpZ8 ctgAoIzKY53Oywt6aLrEf3G0J7qh4DtQ =Xvsc - -----END PGP SIGNATURE----- - ------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqJXHkACgkQZ7GovTQbIm5jGgCcCrJ3zkrGkD0BNdKlYjUWF7KH zbQAn0ewmZL861JeMAOQfxoSUXWXYCVv =8I75 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message