Re: em, bge, network problems survey.
All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know: No apparent problem here. %vmstat -i interrupt total rate irq1: atkbd02416 0 irq4: sio0 1 0 irq14: ata0 47 0 irq16: uhci0 277 0 irq18: em0 atapci1 437511791329 irq21: pcm0 69483666 52 irq23: ehci0 1 0 irq24: twa0 9503153 7 irq25: twa1 2115898 1 irq26: ahc0 125 0 irq27: ahc1 15 0 cpu0: timer 2653958853 2000 Total 3172576243 2391 % %uname -a FreeBSD v2.netoldies.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 17 15:37:40 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/V2KERNEL i386 --Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: snd_emu10k1 driver
On Wed, 27 Sep 2006 01:42:03 -0700, Josh Paetzel [EMAIL PROTECTED] wrote: On Wednesday 27 September 2006 11:55, Bill Blue wrote: Hi, Is this driver known to be 100% working? I'm running stable 6.2 p6 right now and have this device driver installed (device sound and device snd_emu10k1 compiled into the kernel) for use with a Creative Live! card. Audio outputs work correctly, and the various players will produce audio as expected via the PCM control. Line input works as well. 'mixer' works as does KDE's kmix (they track each other). I've also installed the driver via kldload at boot, but it makes no difference. I'm unable to successfully record audio from the line input of this Creative Live! card. Either using the generic /dev/dsp as the recording source, or individual devices /dev/dsp0.0 and up, dspW0.0 and up, or dspr0.4/5. There's just no audio there. For the recording software I've used Krec, ffmpeg, darkice and streamTranscoder (the latter two feeding an icecast server). 'mixer' has its recording device (=rec) set to line in, and I'm feeding audio to line in (analog) and spdif in (digital). There's no problem monitoring the 'line in' buss on the outputs, but there's no audio on the record output device. dmesg shows the driver being installed, and cat /dev/sndstat shows it is active on pcm0. If I cat /dev/sndstat with a higher verbosity (set with sysctrl) it shows that the record devices should be dsp0.4 and dsp0.5, line and mic in respectively. The man page for snd_emu10k1 says the recording devices should be dspr0.4 and dspr0.5 but only if they're driving a codec directly -- I'm not sure what that means exactly. There's no sound daemons like esound or artsd running during these tests. The ports being tested as an input device seem to open correctly and show up as read devices in fstat. I've also tried the snd_emu10kx driver to no avail. Has anyone had experience using the Live! sound card and these drivers? And if so, is recording correctly supported? I have other sound cards available, but none of them seem to have driver support in FreeBSD. One is a Delta (Midiman) 410 with an ICE1712 chip, and the other is a Turtle Beach TB400 (not a Santa Cruz) with Vortex AU8830A2 chip. Both cards have analog and digital ins and outs. Anyone with insight on any of this? --Bill I thought I'd try this out since I have a SB Live! 5.1, use the snd_emu10k1 driver and don't run artsd or esound but when I start krec the record button is greyed out! Using ffmpeg and the /dev/dsp device I was able to record just fine from the mic port on the card. I'm running 6.1-R-p6 Here's my various outputs: Sep 20 19:18:12 v2 kernel: pcm0: Creative EMU10K1 port 0xd000-0xd01f irq 21 at device 2.0 on pci4 Sep 20 19:18:12 v2 kernel: pcm0: TriTech TR28023 AC97 Codec FreeBSD v2.netoldies.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 17 15:37:40 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/V2KERNEL i386 FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Creative EMU10K1 at io 0xd000 irq 21 kld snd_emu10k1 (4p/2r/4v channels duplex default) [EMAIL PROTECTED]:2:0: class=0x040100 card=0x00211102 chip=0x00021102 rev=0x04 hdr=0x00 vendor = 'Creative Labs' device = 'EMU1 Sound Blaster Live! (Also Live! 5.1) - OEM from DELL - CT4780' class= multimedia subclass = audio [EMAIL PROTECTED]:2:1: class=0x098000 card=0x00201102 chip=0x70021102 rev=0x01 hdr=0x00 vendor = 'Creative Labs' device = 'EMU1 Game Port' class= input device I have found the problem, which turned out to be mostly that of (lack of good) documentation and user interpretation. The mixer man page doesn't really talk at all about signal routing, and the kmix man page says almost nothing useful, with examples that address only one card type. snd_emu10k1's man page says less than all the others combined. 'mixer -?' gives a list of input devices and record devices: devices: vol, pcm, speaker, line, mic, cd, rec, igain, line1, phin, phout, video rec devices: vol, line, mic, cd, line1, phin, phout, video and 'mixer' gives a list of all devices and slider settings with no regard to what they do or how they interrelate, and the default record device (=rec). At least in this driver, the devices pcm, line, mic, cd, line1, phin, phout, and video, seem to be strictly inputs -- a mix of internal system and external jack inputs. pcm is an input from software media players, line and mic are external inputs, cd and possibly line1 are 4 pin connectors on the card itself, but I don't know the role of phin, phout and video. vol is master playback volume. The spdif input on the Live! card doesn't seem to be supported. The rec devices are mostly self explanatory, except for two issues. First, on this driver there's only a single device selectable for record at one time (i.e. no record mixer). That devices
snd_emu10k1 driver
Hi, Is this driver known to be 100% working? I'm running stable 6.2 p6 right now and have this device driver installed (device sound and device snd_emu10k1 compiled into the kernel) for use with a Creative Live! card. Audio outputs work correctly, and the various players will produce audio as expected via the PCM control. Line input works as well. 'mixer' works as does KDE's kmix (they track each other). I've also installed the driver via kldload at boot, but it makes no difference. I'm unable to successfully record audio from the line input of this Creative Live! card. Either using the generic /dev/dsp as the recording source, or individual devices /dev/dsp0.0 and up, dspW0.0 and up, or dspr0.4/5. There's just no audio there. For the recording software I've used Krec, ffmpeg, darkice and streamTranscoder (the latter two feeding an icecast server). 'mixer' has its recording device (=rec) set to line in, and I'm feeding audio to line in (analog) and spdif in (digital). There's no problem monitoring the 'line in' buss on the outputs, but there's no audio on the record output device. dmesg shows the driver being installed, and cat /dev/sndstat shows it is active on pcm0. If I cat /dev/sndstat with a higher verbosity (set with sysctrl) it shows that the record devices should be dsp0.4 and dsp0.5, line and mic in respectively. The man page for snd_emu10k1 says the recording devices should be dspr0.4 and dspr0.5 but only if they're driving a codec directly -- I'm not sure what that means exactly. There's no sound daemons like esound or artsd running during these tests. The ports being tested as an input device seem to open correctly and show up as read devices in fstat. I've also tried the snd_emu10kx driver to no avail. Has anyone had experience using the Live! sound card and these drivers? And if so, is recording correctly supported? I have other sound cards available, but none of them seem to have driver support in FreeBSD. One is a Delta (Midiman) 410 with an ICE1712 chip, and the other is a Turtle Beach TB400 (not a Santa Cruz) with Vortex AU8830A2 chip. Both cards have analog and digital ins and outs. Anyone with insight on any of this? --Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Polling and em0
polling(4) says that supported devices include em(4) and that polling support is turned on and off with ifconfig's 'polling' option. But ifconfig doesn't seem to recognize that option either as a standalone request or with the initial em0 setup at boot. This is after a source cvsup (releng=6 for the frozen for 6.2 sources) yesterday and buildworld + buildkernel. em support is compiled in the kernel rather than loaded. Mobo is a Supermicro P4SCT-0 with Intel 875 chipset. Is this a known issue that I haven't found references to, or perhaps something related to my specific configuration? FreeBSD v2.netoldies.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 15 15:14:07 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/V2KERNEL i386 Thanks --Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Motherboard RAID problem
I'm not sure if I'm expecting too much, or this is a real bug. Using FreeBSD 6.1 release, CVSup'd to current. The motherboard is a Supermicro P4SCT0 with a 3.2Ghz P4 and 2 DDR400 1G sticks of RAM. On the MB is a built-in RAID controller (Adaptec chip) for the SATA drives. You set it for discrete SATA or RAID. If RAID is set, on the next boot you have essentially a BIOS configuration for that 'device' consisting of the two SATA devices in either RAID 0 (striped) or RAID 1 (mirrored). I already had a functional SATA boot drive (first SATA device) which shows up on the OS as device ad4s1a-f. I added a second identical drive as the second SATA device, configured the BIOS setting for SATA RAID, rebooted, set up an array of RAID 1 with the first drive as the master. The second device was then built up as a mirror of the first and everything looked normal. Boot the OS now and all goes well with the device still showing up on /dev/ad4* but I couldn't tell if the mirroring was really working since the drives have no individual led indications. I then noticed that there was a new ad6* device, and guess what -- it was the second SATA drive and a mirror image of the *original* first drive. Watching it with DF for size changes when copying a large file to my home directory, it didn't change at all. ad6* were the only new devices seen in the OS. Went back to the BIOS which displayed that instead of two SATA drives there was one RAID unit as far as it's concerned. So it appears as though FreeBSD doesn't have the right drivers to actually see the RAID volume built by the BIOS and considers its members to be individual devices. Does this ring any bells with anyone? Suggestions? A separate and semi-related question, this system also has 16 other drives with two 3Ware 9500SML controllers and 8x500 and 8x750GB arrays. It's managed remotely with X. In this type of application, is Hyperthreading best on or off? Of course for just reading files it's not a big issue, but receiving large files seems to be largely limited by processing interrupts from the 1G ether. They shoot up to 50% and stay pretty consistent regardless of variations in the incoming stream. If Hyperthreading was off, wouldn't there be better performance inbound? Or would that be a tradeoff when the entire picture is taken into account? Thanks for any insights. --Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Motherboard RAID problem
On Sun, 20 Aug 2006 11:22:48 -0700, Roland Smith [EMAIL PROTECTED] wrote: On Sun, Aug 20, 2006 at 07:55:47PM +0200, Greg Byshenk wrote: On Sun, Aug 20, 2006 at 07:38:28PM +0200, Roland Smith wrote: On Sun, Aug 20, 2006 at 10:02:05AM -0700, Bill Blue wrote: I'm not sure if I'm expecting too much, or this is a real bug. Using FreeBSD 6.1 release, CVSup'd to current. The motherboard is a Supermicro P4SCT0 with a 3.2Ghz P4 and 2 DDR400 1G sticks of RAM. On the MB is a built-in RAID controller (Adaptec chip) for the SATA drives. You set it for discrete SATA or RAID. If RAID is set, on the next boot you have essentially a BIOS configuration for that 'device' consisting of the two SATA devices in either RAID 0 (striped) or RAID 1 (mirrored). The ataraid(4) driver supports the Adaptec HostRAID. snip Boot the OS now and all goes well with the device still showing up on /dev/ad4* but I couldn't tell if the mirroring was really working since the drives have no individual led indications. I then noticed that there was a new ad6* device, and guess what -- it was the second SATA drive and a mirror image of the *original* first drive. Watching it with DF for size changes when copying a large file to my home directory, it didn't change at all. ad6* were the only new devices seen in the OS. If FreeBSD supports the device, you should see an ar0 device. Do you have the ataraid(4) driver loaded, or built into your kernel? Alternatively, are you sure you have identified your hardware correctly? According to Supermicro here http://www.supermicro.com/products/motherboard/P4/875/P4SCT.cfm the P4SCT has an Intel 6300ESB onboard RAID controller, which according to this page http://www.gamepc.com/labs/view_content.asp?id=eoyraidpage=2cookie%5Ftest=1 is based upon the ICH4, and not Adaptec controller. And, unless I've missed it, this controller is not supported. The ata(4) manual page lists the 6300ESB as supported. The ataraid(4) manual only lists the Intel MatrixRAID metadata format as supported. Roland Roland, Greg, Thanks for the replies. The Intel 6300ESB (aka Hance Rapids I/O Controller Hub) serves as a controller for USB 2.0, UDMA100 and SATA150 devices. Separately of that, there's the Adaptec embedded SATA with Hostraid controller driver which comes into play if you activate RAID in the BIOS. Since they refer to it as Adaptec's Hostraid controller, it looks like ataraid(4) should support it. And No, I didn't have ataraid defined in my kernel. It was, but for some reason it isn't now. I'll uh, have to add and rebuild. Thanks for pointing out my error. Now, when the ar0s1a-f devices do show up, does the boot device actually get changed from ad4* to ar0* or do I need to boot single user while it's talking to ad4* and change the mount points and reboot? I've never played much with changing boot devices. --Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
