Sound problem w/ 6.1-RC and ASUS A8V-MX (VIA VT8233X)

2006-04-14 Thread George Hartzell

I have a new ASUS A8V-MX motherboard that's running 6.1-RC cvsuped
earlier this week.  I'm running w/ ACPI enabled, I still see the
problem if I boot w/ ACPI disabled at the loader prompt.

I'm running a kernel based on the standard SMP config file with the
addition of an atapicam device.

I have:
  sound_load="YES"
  snd_via8233_load="YES"
in /etc/loader.conf

I can listen to audio cd's using cdplay, I think that's just testing
the analog cable from the back of the drive to the motherboard and out
to the headphone jacks.  At least I know that I have that much
correct.

None of the gnome apps that I've tried make any sound, either playing
a cd from the drive or an mp3.

If I use a sound app, or "cat /etc/termcap > /dev/dsp" in an attempt
to make some noise, I get nothing except the following line in
/var/log/messages:

  pcm0:play:0:dsp0.0: play interrupt timeout, channel dead

I've attached my dmesg output, my mptable output, and my pciconf -lv
output.

Can anyone help me get this going?

Thanks,

g.

-cut here-
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-RC #0: Tue Apr 11 07:26:47 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEMI
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2000.10-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x20fb1  Stepping = 1
  
Features=0x178bfbff
  Features2=0x1
  AMD Features=0xe2500800,LM,3DNow+,3DNow>
real memory  = 2147155968 (2047 MB)
avail memory = 2096119808 (1999 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
npx0: [FAST]
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0:  on acpi0
powernow0:  on cpu0
cpu1:  on acpi0
powernow1:  on cpu1
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
agp0:  mem 0xf800-0xfbff at device 0.0 on 
pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
atapci0:  port 
0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f mem 
0xfebffc00-0xfebf irq 21 at device 15.0 on pci0
ata2:  on atapci0
ata3:  on atapci0
atapci1:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0
ata0:  on atapci1
ata1:  on atapci1
uhci0:  port 0xe080-0xe09f irq 20 at device 16.0 on 
pci0
uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xe000-0xe01f irq 22 at device 16.1 on 
pci0
uhci1: [GIANT-LOCKED]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xdc00-0xdc1f irq 21 at device 16.2 on 
pci0
uhci2: [GIANT-LOCKED]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3:  port 0xd880-0xd89f irq 23 at device 16.3 on 
pci0
uhci3: [GIANT-LOCKED]
usb3:  on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0:  mem 0xfebff800-0xfebff8ff irq 22 at 
device 16.4 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4:  on ehci0
usb4: USB revision 2.0
uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
uhub4: device problem (SET_ADDR_FAILED), disabling port 7
isab0:  at device 17.0 on pci0
isa0:  on isab0
pcm0:  port 0xd400-0xd4ff irq 22 at device 17.5 on pci0
pcm0: 
pcm0: 
vr0:  port 0xd000-0xd0ff mem 
0xfebff400-0xfebff4ff irq 23 at device 18.0 on pci0
miibus0:  on vr0
rlphy0:  on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:15:f2:2c:c3:86
pcib2:  at device 19.0 on pci0
pci2:  on pcib2
pcib3:  at device 0.0 on pci2
pci3:  on pcib3
pcib4:  at device 0.1 on pci2
pci4:  on pcib4
acpi_button0:  on acpi0
acpi_button1:  on acpi0
ppc0:  port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on 
acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 

Re: powerd not behaving with an Asus A8V-MX and Athlon 64 X2 3800+

2006-04-14 Thread George Hartzell
George Hartzell writes:
 > 
 > I have an Asus A8V-MX motherboard with an AMD Athlong 64 X2 3800+ CPU
 > and I'm trying to run powerd to keep it cooler/quieter/greener.
 > [...]

[for the archives]

I now have powerd running w/out any complaints, although I still don't
understand what was causing the problem.

I've added the following entries to /boot/loader.conf

  hint.acpi_throttle.0.disabled="1"
  hint.acpi_throttle.1.disabled="1"

and then just run powerd by adding the following lines to /etc/rc.conf

  powerd_enable="YES"
  powerd_flags="-a adaptive"

and the system happily cycles between 2000, 1800, and 1000 MHz
depending on what it's doing (it actually never hangs out at 1800 for
long, just while transitioning between the extremes).

I guess that the CPU or bios or ??? was advertising support for
throttling that it didn't really implement, but I don't really
understand the why's and hows.

g.



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel build failure with bce

2006-04-14 Thread Plamen Stoev
Sean McNeil wrote:
> The following error occurs building -stable on amd64:
> 
> make -sj2 buildworld && make -sj2 buildkernel
> ...
> ===> bce (all)
> /usr/src/sys/modules/bce/../../dev/bce/if_bce.c: In function
> `bce_rx_intr':
> /usr/src/sys/modules/bce/../../dev/bce/if_bce.c:4093: error: structure
> has no member named `rxcycles'
> /usr/src/sys/modules/bce/../../dev/bce/if_bce.c: In function
> `bce_ioctl':
> /usr/src/sys/modules/bce/../../dev/bce/if_bce.c:4897: error: label
> `bce_ioctl_exit' used but not defined
> 
> I have nothing in my config file for device bce, so it would appear
> someone didn't check for building as a module.

Please re-cvsup your source tree. The problem was fixed today.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"