Date: Mon, 17 Jan 2000 18:11:09 -0800 From: Andy Sparrow <andy@geek4food.org> To: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Integrated Vibra16 in -current Message-ID: <200001180211.SAA13312@mega.geek4food.org>
next in thread | raw e-mail | index | archive | help
Hi. I recently cvsup'd -CURRENT both so that I could run StarOffice 5.1 (it's an SMP box), and to check it out (as it will soon be a Release, and I see a lot of good stuff going on there, like the SMP locking, NFS fixes etc.). I've got a Micron W6-Li Lightning board with integrated Creative Vibra16X and Adaptec 7880, and I run a WinTV card as well. I also have the ISA Waveblaster daughter card that makes the sound setup effectively an AWE32. After upgrading, I discovered that I couldn't get the sound chip on the motherboard to get probed correctly. Given the Plug'n'Pray changes in -current, I pretty much expected to lose AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to probe the "magic" ports for the AWE32). However, I wasn't expecting to lose the ability to use VoxWare altogether. Without PNPBIOS, I got these messages (config file was the same one as used under -STABLE, just converted by the simple expedient of fixing the complaints from 'config', mostly changing 'controller' to 'device' etc.): sb_reset_dsp failed sb_reset_dsp failed awe0 at port 0x620 on isa0 AWE32: not detected unknown0: <WaveTable> at port 0x621-0x624 on isa0 unknown1: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 unknown2: <Game> at port 0x201 on isa0 I tried adding PNPBIOS to the kernel options, with little improvement: sb_reset_dsp failed sb_reset_dsp failed unknown0: <PNP0c02> at port 0x80,0x10-0x1f,0x22-0x2f,0x30-0x3f,0x50-0x5f,0x90-0x9f,0xa2-0xaf,0xb0-0xbf,0xe0-0xef iomem 0xfffc0000-0xffffffff on isa0 unknown1: <PNP0c01> at iomem 0-0x9ffff,0xe0000-0xfffff,0x100000-0x7ffffff on isa0 unknown2: <PNP0200> at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: <PNP0000> can't assign resources unknown3: <PNP0100> at port 0x40-0x43 irq 0 on isa0 unknown4: <PNP0b00> at port 0x70-0x71 irq 8 on isa0 unknown: <PNP0303> can't assign resources unknown5: <PNP0c04> at port 0xf0-0xff irq 13 on isa0 unknown: <PNP0800> can't assign resources unknown6: <PNP0a03> at port 0xcf8-0xcff on isa0 unknown7: <PNP0c02> at port 0x4d0-0x4d1 on isa0 unknown8: <PNP0c02> at iomem 0xfec00000-0xfec0ffff,0xfee00000-0xfee00fff on isa0 unknown: <PNP0f13> can't assign resources unknown: <PNP0501> can't assign resources unknown: <PNP0700> can't assign resources unknown: <PNP0400> can't assign resources unknown9: <WaveTable> at port 0x620-0x623 on isa0 unknown10: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 unknown11: <Game> at port 0x201 on isa0 Switching 'PNP OS = YES' in the BIOS setup (it's a Phoenix BIOS) didn't seem to make any difference to anything. Worse, with PNPBIOS enabled, the WinTV card would not work either: bktr0: <BrookTree 878> irq 17 at device 17.0 on pci0 bktr0: could not map memory device_probe_and_attach: bktr0 attach returned 6 pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 17 Subsequent attempts to run 'fxtv' would give '/dev/bktr0 not configured' messages. In fact, in -current, there's a few things that look odd. I always get this complaint from the BrookTree driver (which I've never seen on 3.x): pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 17 I get this even if PNPBIOS isn't an option, and the card actually works... and I always see this too devclass_alloc_unit: npx0 already exists, using next available unit number Using the 'pcm0' and 'sbc0' driver (without any 'at isa?' etc. and without PNPBIOS so the WinTV card is usable) seems to work fine, but I'm a little confused as to why the VoxWare stuff can't work anymore. Last but not least, 'xmcd' doesn't work for me under -CURRENT (integrated AIC-7880 and Plextor PX-12TSi CD-ROM), it never recognises that a CD is inserted, and an attempt to eject the CD from 'xmcd' gives a 'Inappropriate IOCTL for device' message (sorry, I didn't make a note of the tag on the front). I was running an pre-built port, which gave a different error. I 'make reinstall' the port, and it now gives the IOCTL error message, but only under -CURRENT. I was running 3.3-STABLE from some time ago (on another drive). I just upgraded that to 3.4-STABLE (as of last night), and everything works fine booted from that, VoxWare (with AWE32), WinTV, 'xmcd', etc. However, I still can't run StarOffice 5.1 without booting a UP kernel, which is kind of sub-optimal. :-/ Is this breakage of the built-in Vibra with VoxWare expected? Surprised the heck out of me... Is there anything I can do to help track this down, or does anyone have any additional suggestions? Complete 'dmesg' output available on request :=) Regards, Andy Sparrow To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001180211.SAA13312>