Re: Sound device reported but no devices created
On Sun, 30 Jul 2006, Peter Jeremy wrote: On Sun, 2006-Jul-30 12:10:54 +0800, Ariff Abdullah wrote: On Sun, 30 Jul 2006 13:43:52 +1000 Peter Jeremy [EMAIL PROTECTED] wrote: I've been trying to get sound working on a Compaq Armada 1580 with a recent 6-STABLE. With devices 'sound' and 'snd_sbc' built into the kernel and no hints, I get: ... I suspect the problem is that sbc0 is not triggering attachment of pcm0 but I'm uncertain why. Does anyone have any suggestions? Try to disable ACPI, or edit /usr/src/sys/dev/sound/isa/sbc.c and remove acpi module dependency (line 794) The system is too old to support ACPI. I've removed the module dependency anyway with no difference. Peter, I don't know if this is likely helpful or not, but my Compaq is a 1500c with an ESS ES1869, reporting (on 5.4-RELEASE): sbc0: ESS ES1869 (Compaq OEM) at port 0x330-0x331,0x388-0x38b,0x220-0x22f irq 5 drq 5,1 on isa0 pcm0: ESS 18xx DSP on sbc0 I too have in kernel: device sound device snd_sbc # ES1869 (Compaq OEM) but after much headscratching it only finally worked after adding: snd_ess_load=YES # this fixed it .. bridge driver for ESS to /boot/loader.conf. My soon to be built 5-STABLE kernel will include also 'device snd_ess' directly, and I'm expecting that to work too. HTH, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GIANT in arcmsr(4)
On 7/29/06, Nikolas Britton [EMAIL PROTECTED] wrote: Anyone know why the giant is in arcmsr(4) or how to kill him? I did some work on the arcmsr(4) driver: http://www.freebsd.org/cgi/query-pr.cgi?pr=101045 -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound device reported but no devices created
On Sun, 2006-Jul-30 17:52:27 +1000, Ian Smith wrote: Peter, I don't know if this is likely helpful or not, but my Compaq is a 1500c with an ESS ES1869, reporting (on 5.4-RELEASE): sbc0: ESS ES1869 (Compaq OEM) at port 0x330-0x331,0x388-0x38b,0x220-0x22f irq 5 drq 5,1 on isa0 pcm0: ESS 18xx DSP on sbc0 I too have in kernel: device sound device snd_sbc # ES1869 (Compaq OEM) but after much headscratching it only finally worked after adding: snd_ess_load=YES # this fixed it .. bridge driver for ESS That worked, thank you. The man pages are not the clearest here. snd_ess(4) implies that all three drivers are needed but snd_sbc(4) has no reference to it - which is what confused me. -- Peter Jeremy pgpmNw0jBuEPT.pgp Description: PGP signature
Re: Sound device reported but no devices created
On Sun, 30 Jul 2006, Peter Jeremy wrote: On Sun, 2006-Jul-30 17:52:27 +1000, Ian Smith wrote: device sound device snd_sbc # ES1869 (Compaq OEM) but after much headscratching it only finally worked after adding: snd_ess_load=YES # this fixed it .. bridge driver for ESS That worked, thank you. The man pages are not the clearest here. Indeed; I'd spent days googling around lists and pages, at last found: http://gerda.univie.ac.at/freebsd-laptops/index.pl?action=show_laptop_detaillaptop=496 about the 1750, which was wrong (for the 1500c) about the device hints - for unbridged devices, says sound(4) - but the needed clue for loading both snd_sbc and snd_ess. snd_ess(4) implies that all three drivers are needed but snd_sbc(4) has no reference to it - which is what confused me. snd_ess(4) has been updated then; at 5.4 it didn't mention snd_sbc. Building a 5-STABLE world right now, I'm a bit curious as to which of the more recent sound stuff has found its way into 5.5 .. hi Ariff! Cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
drawterm
Hi all! I'd like to know if someone has experience with drawterm on amd64 system. (Flags, etc...) If not, on i386? I have source and feeling that I will make the box available to the rest of the world. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound device reported but no devices created
On Sun, July 30, 2006 4:28 am, Peter Jeremy wrote: On Sun, 2006-Jul-30 17:52:27 +1000, Ian Smith wrote: Peter, I don't know if this is likely helpful or not, but my Compaq is a 1500c with an ESS ES1869, reporting (on 5.4-RELEASE): sbc0: ESS ES1869 (Compaq OEM) at port 0x330-0x331,0x388-0x38b,0x220-0x22f irq 5 drq 5,1 on isa0 pcm0: ESS 18xx DSP on sbc0 I too have in kernel: device sound device snd_sbc # ES1869 (Compaq OEM) but after much headscratching it only finally worked after adding: snd_ess_load=YES # this fixed it .. bridge driver for ESS That worked, thank you. The man pages are not the clearest here. snd_ess(4) implies that all three drivers are needed but snd_sbc(4) has no reference to it - which is what confused me. The easiest (and most reliable I've found) method to determine which sound driver(s) is needed for a particular sound card is: # kldload snd_driver # cat /dev/sndstat read the text to see what driver(s) it loaded # echo 'snd_driver_load=YES' /boot/loader.conf snd_driver will load every single sound driver available in FreeBSD, all at once, and the kernel will attempt to detect every sound chipset supported by those drivers. The contents of /dev/sndstat will show which chipset was found, and which specific driver is is being used (snd_ess in your case). Putting just that one driver into loader.conf will pull in all the needed dependecies (like sound, snd_sbc, etc). Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring temperature with acpi (sysctls)
On Jul 28, 2006, at 8:38 PM, Nikolas Britton wrote: On 7/26/06, David Duchscher [EMAIL PROTECTED] wrote: Yes, the Supermicro PDSMi supports the IPMI 2.0 module and I can confirm that it works with the IPMI ported driver from current on 6.1. The module is optional so you will have to purchase one for the system, around 0. You will also need the latest BIOS loaded on the motherboard for it to work. http://www.supermicro.com/products/accessories/addon/AOC-IPMI20-E.cfm What about their other IPMI 2.0 cards: http://www.supermicro.com/products/accessories/addon/SIM.cfm Specifically the AOC-SIMLP? and what ported IPMI driver are we talking about? Also does anyone have an IPMI primer, I've never used it before? I haven't used the cards listed there so I can really comment on how well they work or if they work. I would assume the cards with their own ethernet jack will work no matter what OS is on the system. The problems that have cropped up with the integrated or add-in modules is that the OS network driver can cut off access to the IPMI module. For example, the IPMI module with the bge driver use to do that, not sure if that has been fixed. I have also noticed today that communication to the IPMI module is lost when the em driver initializes the network device and doesn't come back until the interface is brought up by the OS. If you have no networking configured, no network access to the IPMI module. :) As for the IPMI driver, it is not necessary for the OS to have an IPMI driver unless you wish to communicate with the card outside of using the network. The IPMI driver I am using is in ports/ipmi-kmod and is a port of the driver in current. I have no idea if it supports those cards. -- DaveD
Re: Sound device reported but no devices created
in message [EMAIL PROTECTED], wrote Freddie Cash thusly... # kldload snd_driver # cat /dev/sndstat read the text to see what driver(s) it loaded # echo 'snd_driver_load=YES' /boot/loader.conf snd_driver will load every single sound driver available in FreeBSD, all at once, and the kernel will attempt to detect every sound chipset supported by those drivers. Neat. Thanks much Freddie. (No, i don't have any sound driver problems, but your method seems much easier|lazier than to explicitly search for the sound hardware related FreeBSD bits.) - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.5 (VMware) on Fedora core 5
Hello, I am running Fedroa core 5 Dual PIII 800, with VMware server. I am not sure if or should i install FreeBSD 5.5 stable +SMP kernel! I am looking at a basic web server config, Apache 1.3 PHP4 MySQL 4.1 OSCommerce ProFTP some sort of mail server also, POP, SMTP. Its all for the sake of learning it and doing it as of now. FreeBSD is intalled as a Virutal Machine now. but after thinking a bit, got stuck with the SMP kernel! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Odd PCI and ACPI messages on 'INSYDE RSDT_000' laptop
Hello, Last week I got a laptop from a few friends of mine with a broken screen. I removed the screen from the device and connected a regular CRT to it to install FreeBSD 6.1 on it for serving as a jukebox (silent, doesn't consume too much power). I first tried FreeSBIE 1.1, which just deadlocked during the bootsplash. After that I downloaded a FreeBSD 6.1 CD. When I boot FreeBSD 6.1 without the ACPI kernel module, it panics (fatal trap 12) right after probing uhci0. When I boot with ACPI, it boots like it should. Because the laptop doesn't have a serial connector, I didn't copy the kernel backtrace. If it is really needed, I'll boot the CD once again and type over the screen contents. Anyway, I installed FreeBSD 6.1 on it, with the ACPI module loaded, but I still get some really strange messages in my dmesg I thought would be useful to mention: | ... | cpu0: ACPI CPU on acpi0 | acpi_perf0: ACPI CPU Frequency Control on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... | acpi_perf0: ACPI CPU Frequency Control on cpu0 | acpi_perf0: failed in PERF_STATUS attach | device_attach: acpi_perf0 attach returned 6 | ... And these: | ... | pci_link0: BIOS IRQ 11 for 0.2.INTA is invalid | pci_link1: BIOS IRQ 5 for 0.31.INTB is invalid | ... | pci_link4: BIOS IRQ 11 for 1.0.INTA is invalid | pci_link5: BIOS IRQ 11 for 1.1.INTA is invalid | ... The device Just Works at the moment, so I can live with it, but I was wondering if these messages do any harm. I've attached the entire dmesg of the device for those who are interested. Yours, -- Ed Schouten [EMAIL PROTECTED] WWW: http://g-rave.nl/ Copyright (c) 1992-2006 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 6.1-STABLE #0: Thu Jul 27 15:07:26 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KIEBORT Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1500MHz (1498.73-MHz 686-class CPU) Origin = GenuineIntel Id = 0x695 Stepping = 5 Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE Features2=0x180EST,TM2 real memory = 520028160 (495 MB) avail memory = 503705600 (480 MB) acpi0: INSYDE RSDT_000 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_ec0: Embedded Controller: GPE 0x1c port 0x62,0x66 on acpi0 cpu0: ACPI CPU on acpi0 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_perf0: ACPI CPU Frequency Control on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci_link0: BIOS IRQ 11 for 0.2.INTA is invalid pci_link1: BIOS IRQ 5 for 0.31.INTB is invalid pci0: ACPI PCI bus on pcib0 pci0: base peripheral at device 0.1 (no driver attached) pci0: base peripheral at device 0.3 (no driver attached) pci0: display, VGA at device 2.0 (no driver attached) pci0: display at device 2.1 (no driver attached) pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: serial bus, USB at device 29.2 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci_link4: BIOS IRQ 11 for 1.0.INTA is invalid pci_link5: BIOS IRQ 11 for 1.1.INTA is invalid pci1: ACPI PCI bus on pcib1 pci1: serial bus, FireWire at device 0.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xc000-0xc0ff mem 0xe000-0xe0ff irq 9 at device 1.0 on pci1 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:02:3f:12:cd:5a pci1: bridge, PCI-CardBus at device 4.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1100-0x110f at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) pcm0: Intel ICH4 (82801DB) port 0xe100-0xe1ff,0xe200-0xe23f mem 0xf0080400-0xf00805ff,0xf0080600-0xf00806ff irq 9 at device 31.5 on pci0 pcm0: Avance Logic ALC202 AC97 Codec pci0: simple comms, generic modem at device 31.6 (no driver attached) atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 atkbd0: [GIANT-LOCKED] acpi_acad0: AC Adapter on acpi0 battery0: ACPI Control Method
Re: FreeBSD 5.5 (VMware) on Fedora core 5
Jon Holstrom wrote: I am running Fedroa core 5 Dual PIII 800, with VMware server. Its all for the sake of learning it and doing it as of now. For a new installation there is really no reason to use 5.5. Use the much improved 6.1. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Latest change of if_re.c breaks DNS resolution
The today changes of if_re.c by Bill Paul break DNS resolution on my machine. Resolution requests just time out after a while. Reverting the changes resolves the problem... -- Markus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
