Re: How to test if sound is working?

2010-11-09 Thread James Hozier
> From: David Coppa 
> Subject: Re: How to test if sound is working?
> To: "James Hozier" 
> Date: Tuesday, November 9, 2010, 3:53 PM
> On Tue, Nov 9, 2010 at 4:43 PM, James
> Hozier 
> wrote:
> >> From: David Coppa 
> >> Subject: Re: How to test if sound is working?
> >> To: "James Hozier" 
> >> Date: Tuesday, November 9, 2010, 3:15 PM
> >> On Tue, Nov 9, 2010 at 3:51 PM, James
> >> Hozier 
> >> wrote:
> >>
> >> > It doesn't 'make' properly:
> >>
> >> Of course, because you're not using/running
> -current!
> >>
> >> Then, use the attached one with 4.8...
> >>
> >> ciao,
> >> david
> >>
> >
> > A diff from your attached file with my original file
> (with the patch modifications manually added) shows no
> difference. But nonetheless I will attempt again. Should I
> update to the -CURRENT branch?
> 
> Send me the dmesg of the new compiled kernel (the patched
> one), please.
> 
> Btw, yes, updating to -current would be better.
> 
> 
> 
> ciao,
> david
> 

Here is the most recent dmesg (-CURRENT):

OpenBSD 4.8-current (GENERIC) #0: Tue Nov  9 16:01:02 EST 2010
r...@host:/usr/src/sys/arch/i386/compile/GENERIC
RTC BIOS diagnostic error 
f7
cpu0: Intel(R) Core(TM)2 Duo CPU P7550 @ 2.26GHz ("GenuineIntel" 686-class) 
2.26 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE
real mem  = 2926321664 (2790MB)
avail mem = 2868416512 (2735MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (42 
entries)
bios0: vendor Apple Inc. version "MBP55.88Z.00AC.B03.0906151708" date 06/15/09
bios0: Apple Inc. MacBookPro5,5
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) EC__(S3) OHC1(S3) EHC1(S3) OHC2(S3) 
EHC2(S3) GIGE(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2500 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 265MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (IXVE)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "3545797981023400290" type 3545797981528607052 
oem "3545797981528673619"
bios0: ROM list: 0xc/0xe800
cpu0: Enhanced SpeedStep 2256 MHz: speeds: 2261, 2128, 1862, 1596, 798 MHz
memory map conflict 0xffc0/0x40
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
mem address conflict 0xd340/0x8
pchb0 at pci0 dev 0 function 0 "NVIDIA MCP79 Host" rev 0xb1
"NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 0 function 1 not configured
pcib0 at pci0 dev 3 function 0 "NVIDIA MCP79 ISA" rev 0xb3
"NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 3 function 1 not configured
nviic0 at pci0 dev 3 function 2 "NVIDIA MCP79 SMBus" rev 0xb1
iic0 at nviic0
sdtemp0 at iic0 addr 0x18: stts424e02
sdtemp1 at iic0 addr 0x19: stts424e02
spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-8500 SO-DIMM with thermal sensor
spdmem1 at iic0 addr 0x51: 2GB DDR3 SDRAM PC3-8500 SO-DIMM with thermal sensor
iic1 at nviic0
iic1: addr 0x2c 00=ff 02=08 03=f9 07=60 0d=73 71=06 86=47 90=71 91=61 92=a4 
93=79 94=31 95=3c 96=7c 97=92 9f=0c a0=3d a1=3d a2=7d a3=3d a4=3d a5=3d a6=3d 
a7=3d a8=3d a9=3d aa=3d ab=3d ac=3d ad=3d ae=3d af=3d b0=3d b1=3d b2=3d b3=3d 
b4=3d b5=3d b6=3d b7=3d b8=3d b9=3d ba=3d bb=3d bc=3d bd=3d be=3d bf=3d words 
00=ff00 01=0008 02=08f9 03=f900 04= 05= 06=0060 07=6000
"NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 3 function 3 not configured
vendor "NVIDIA", unknown product 0x0a98 (class memory subclass RAM, rev 0xb1) 
at pci0 dev 3 function 4 not configured
"NVIDIA MCP79 Co-processor" rev 0xb1 at pci0 dev 3 function 5 not configured
ohci0 at pci0 dev 4 function 0 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 11 (irq 
11), version 1.0, legacy support
ehci0 at pci0 dev 4 function 1 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 10 (irq 
10)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "NVIDIA EHCI root hub" rev 2.00/1.00 addr 1
ohci1 at pci0 dev 6 function 0 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 7 (irq 
7), version 1.0, legacy support
ehci1 at pci0 dev 6 function 1 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 5 (irq

Re: How to test if sound is working?

2010-11-09 Thread James Hozier
> From: David Coppa 
> Subject: Re: How to test if sound is working?
> To: "James Hozier" 
> Date: Tuesday, November 9, 2010, 3:53 PM
> On Tue, Nov 9, 2010 at 4:43 PM, James
> Hozier 
> wrote:
> >> From: David Coppa 
> >> Subject: Re: How to test if sound is working?
> >> To: "James Hozier" 
> >> Date: Tuesday, November 9, 2010, 3:15 PM
> >> On Tue, Nov 9, 2010 at 3:51 PM, James
> >> Hozier 
> >> wrote:
> >>
> >> > It doesn't 'make' properly:
> >>
> >> Of course, because you're not using/running
> -current!
> >>
> >> Then, use the attached one with 4.8...
> >>
> >> ciao,
> >> david
> >>
> >
> > A diff from your attached file with my original file
> (with the patch modifications manually added) shows no
> difference. But nonetheless I will attempt again. Should I
> update to the -CURRENT branch?
> 
> Send me the dmesg of the new compiled kernel (the patched
> one), please.
> 
> Btw, yes, updating to -current would be better.
> 
> 
> 
> ciao,
> david
> 

I will be updating to -current after I paste this dmesg:

OpenBSD 4.8-stable (GENERIC) #2: Tue Nov  9 10:53:36 EST 2010
r...@host:/usr/src/sys/arch/i386/compile/GENERIC
RTC BIOS diagnostic error 
f7
cpu0: Intel(R) Core(TM)2 Duo CPU P7550 @ 2.26GHz ("GenuineIntel" 686-class) 
2.26 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE
real mem  = 2926321664 (2790MB)
avail mem = 2868498432 (2735MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (42 
entries)
bios0: vendor Apple Inc. version "MBP55.88Z.00AC.B03.0906151708" date 06/15/09
bios0: Apple Inc. MacBookPro5,5
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) EC__(S3) OHC1(S3) EHC1(S3) OHC2(S3) 
EHC2(S3) GIGE(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2500 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 265MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (IXVE)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "3545797981023400290" type 3545797981528607052 
oem "3545797981528673619"
bios0: ROM list: 0xc/0xe800
cpu0: Enhanced SpeedStep 2256 MHz: speeds: 2261, 2128, 1862, 1596, 798 MHz
memory map conflict 0xffc0/0x40
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
mem address conflict 0xd340/0x8
pchb0 at pci0 dev 0 function 0 "NVIDIA MCP79 Host" rev 0xb1
"NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 0 function 1 not configured
pcib0 at pci0 dev 3 function 0 "NVIDIA MCP79 ISA" rev 0xb3
"NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 3 function 1 not configured
nviic0 at pci0 dev 3 function 2 "NVIDIA MCP79 SMBus" rev 0xb1
iic0 at nviic0
sdtemp0 at iic0 addr 0x18: stts424e02
sdtemp1 at iic0 addr 0x19: stts424e02
spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-8500 SO-DIMM with thermal sensor
spdmem1 at iic0 addr 0x51: 2GB DDR3 SDRAM PC3-8500 SO-DIMM with thermal sensor
iic1 at nviic0
iic1: addr 0x2c 00=ff 02=08 03=f9 07=60 0d=73 71=06 86=48 90=71 91=61 92=a4 
93=79 94=31 95=3c 96=7c 97=92 9f=0c a0=39 a1=3d a2=3d a3=3d a4=3d a5=3d a6=3d 
a7=3d a8=3d a9=3d aa=3d ab=3d ac=3d ad=3d ae=3d af=3d b0=3d b1=3d b2=3d b3=3d 
b4=3d b5=3d b6=3d b7=3d b8=3d b9=3d ba=3d bb=3d bc=3d bd=3c be=7d bf=3d words 
00=ff00 01=0008 02=08f9 03=f900 04= 05= 06=0060 07=6000
"NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 3 function 3 not configured
vendor "NVIDIA", unknown product 0x0a98 (class memory subclass RAM, rev 0xb1) 
at pci0 dev 3 function 4 not configured
"NVIDIA MCP79 Co-processor" rev 0xb1 at pci0 dev 3 function 5 not configured
ohci0 at pci0 dev 4 function 0 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 11 (irq 
11), version 1.0, legacy support
ehci0 at pci0 dev 4 function 1 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 10 (irq 
10)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "NVIDIA EHCI root hub" rev 2.00/1.00 addr 1
ohci1 at pci0 dev 6 function 0 "NVIDIA MCP79 USB" rev 0xb1: apic 1 int 7 (irq 
7), version 1.0, legacy support
ehci1 at pci0 dev 6 function 1 "NVIDIA MCP79 USB" rev 0xb1: a

Re: How to test if sound is working?

2010-11-09 Thread James Hozier
> From: David Coppa 
> Subject: Re: How to test if sound is working?
> To: "James Hozier" 
> Date: Tuesday, November 9, 2010, 3:15 PM
> On Tue, Nov 9, 2010 at 3:51 PM, James
> Hozier 
> wrote:
> 
> > It doesn't 'make' properly:
> 
> Of course, because you're not using/running -current!
> 
> Then, use the attached one with 4.8...
> 
> ciao,
> david
> 

A diff from your attached file with my original file (with the patch 
modifications manually added) shows no difference. But nonetheless I will 
attempt again. Should I update to the -CURRENT branch?



Re: How to test if sound is working?

2010-11-09 Thread Dmitrij Czarkoff
On Tue, Nov 9, 2010 at 5:53 AM, Jacob Meuser  wrote:
> judging by the formatting of your emails, the patch got mangled by
> your mailer.

Fred seems to be using Gmail webmail, which has an option of
downloading a message as is, without reformatting. Anyway, in my
browser messages seem to be formatted to keep at least 80 chars wide.

-- 
Dmitrij D. Czarkoff



Re: How to test if sound is working?

2010-11-09 Thread James Hozier
> From: Jacob Meuser 
> Subject: Re: How to test if
sound is working?
> To: misc@openbsd.org
> Date: Tuesday, November 9, 2010,
4:53 AM
> On Mon, Nov 08, 2010 at 06:55:59PM
> -0800, James Hozier wrote:
> >
> From: Fred Crowson 
> > > Subject: Re: How to test
if
> > sound is working?
> > > To: "James Hozier" 
> > >
Cc:
> > misc@openbsd.org
> > > Date: Monday, November 8, 2010, 10:55 PM
> > >
On 8 November
> > 2010 22:04, James
> > > Hozier 
> > >
wrote:
> > > >
> > > > $ cat
> > azalia_codec.c.rej
> > > > @@ -64,6 +64,13 @@
> > > >this->name = NULL;
> > > >   
> > this->qrks = AZ_QRK_NONE;
> > >
>switch (this->vid) {
> > > > +case
> > 0x10134206:
> > > > +   
this->name =
> "Cirrus
> > > Logic CS4206";
> > > > +if
> >
(this->subid ==
> > > 0x106b4d00) {/* APPLE_MBP55 */
> > > > +   
>
   
> > >
> > this->qrks |= AZ_QRK_GPIO_UNMUTE_1 |
> > > > + 
>
>
> >  
> > AZ_QRK_GPIO_UNMUTE_3;
> > > > +}
> > > > +break;
> >
> >case
> > 0x10ec0260:
> > > >this->name =
> "Realtek
> > >
ALC260";
> > > >break;
> > > >
> > > > What does this mean? It looks
like a snippet
> of code
> > > from the original
> > patch
> > > file?
> > >
> > > Hi James,
> > > 
> > > For some reason patch(1) did not insert the
> >
code into
> > > azalia_codec.c
> > > - I would guess that the reason was that
patch
> > file had
> > > some
> > > formatting that patch(1) did not like.
Have
> another go at
> > >
> > creating and
> > > patching the file, or you
can either manually add
> those 7
> > > new
> > lines to
> > > azailia_codec.c
after line 77 of azaila_codec.c
> > > 
> > > Thus when you
> > rebuilt your
kernel - it did not have this
> > > new bit of code in.
> > > 
> > > hth
> > >
> > >
> > Fred
> > > 
> > > 
> > 
> > Hmm...added those lines to
azalia_codec.c after line
> 66 (without
> > the + signs in front
> > of the
lines), re-compiled and rebooted but still
> > nothing. I guess it's something
> > else, then...but I'm curious as to why the
> > patch didn't work.
> 
> 
>
judging by the formatting of your emails, the patch got
> mangled by
> your
mailer.
> 
> inlining patches in email messages (as opposed to MIME
>
attachments)
> is part of OpenBSD culture.
> 
> -- 
> jake...@sdf.lonestar.org
> SDF Public Access UNIX System - http://sdf.lonestar.org
> 
> 

Yea, I don't
know why this formats weirdly. But in any case, I do know to at the very
least
to fix up the formatting in the patch file instead of just pasting the e-mail
into vi. For what it's worth, here's a small screenshot of what the file looks
like:
http://img442.imageshack.us/img442/8076/201011090732251280x800s.png



Re: How to test if sound is working?

2010-11-08 Thread Jacob Meuser
On Mon, Nov 08, 2010 at 06:55:59PM -0800, James Hozier wrote:
> > From: Fred Crowson 
> > Subject: Re: How to test if
> sound is working?
> > To: "James Hozier" 
> > Cc:
> misc@openbsd.org
> > Date: Monday, November 8, 2010, 10:55 PM
> > On 8 November
> 2010 22:04, James
> > Hozier 
> > wrote:
> > >
> > > $ cat
> azalia_codec.c.rej
> > > @@ -64,6 +64,13 @@
> > >this->name = NULL;
> > >   
> this->qrks = AZ_QRK_NONE;
> > >switch (this->vid) {
> > > +case
> 0x10134206:
> > > +this->name = "Cirrus
> > Logic CS4206";
> > > +if
> (this->subid ==
> > 0x106b4d00) {/* APPLE_MBP55 */
> > > +   
> >
> this->qrks |= AZ_QRK_GPIO_UNMUTE_1 |
> > > + 
> >  
> AZ_QRK_GPIO_UNMUTE_3;
> > > +}
> > > +break;
> > >case
> 0x10ec0260:
> > >this->name = "Realtek
> > ALC260";
> > >break;
> > >
> > > What does this mean? It looks like a snippet of code
> > from the original
> patch
> > file?
> > 
> > Hi James,
> > 
> > For some reason patch(1) did not insert the
> code into
> > azalia_codec.c
> > - I would guess that the reason was that patch
> file had
> > some
> > formatting that patch(1) did not like. Have another go at
> >
> creating and
> > patching the file, or you can either manually add those 7
> > new
> lines to
> > azailia_codec.c after line 77 of azaila_codec.c
> > 
> > Thus when you
> rebuilt your kernel - it did not have this
> > new bit of code in.
> > 
> > hth
> > 
> >
> Fred
> > 
> > 
> 
> Hmm...added those lines to azalia_codec.c after line 66 (without
> the + signs in front
> of the lines), re-compiled and rebooted but still
> nothing. I guess it's something
> else, then...but I'm curious as to why the
> patch didn't work.


judging by the formatting of your emails, the patch got mangled by
your mailer.

inlining patches in email messages (as opposed to MIME attachments)
is part of OpenBSD culture.

-- 
jake...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org



Re: How to test if sound is working?

2010-11-08 Thread James Hozier
> From: Fred Crowson 
> Subject: Re: How to test if
sound is working?
> To: "James Hozier" 
> Cc:
misc@openbsd.org
> Date: Monday, November 8, 2010, 10:55 PM
> On 8 November
2010 22:04, James
> Hozier 
> wrote:
> >
> > $ cat
azalia_codec.c.rej
> > @@ -64,6 +64,13 @@
> >this->name = NULL;
> >   
this->qrks = AZ_QRK_NONE;
> >switch (this->vid) {
> > +case
0x10134206:
> > +this->name = "Cirrus
> Logic CS4206";
> > +if
(this->subid ==
> 0x106b4d00) {/* APPLE_MBP55 */
> > +   
>
this->qrks |= AZ_QRK_GPIO_UNMUTE_1 |
> > + 
>  
AZ_QRK_GPIO_UNMUTE_3;
> > +}
> > +break;
> >case
0x10ec0260:
> >this->name = "Realtek
> ALC260";
> >break;
> >
> > What does this mean? It looks like a snippet of code
> from the original
patch
> file?
> 
> Hi James,
> 
> For some reason patch(1) did not insert the
code into
> azalia_codec.c
> - I would guess that the reason was that patch
file had
> some
> formatting that patch(1) did not like. Have another go at
>
creating and
> patching the file, or you can either manually add those 7
> new
lines to
> azailia_codec.c after line 77 of azaila_codec.c
> 
> Thus when you
rebuilt your kernel - it did not have this
> new bit of code in.
> 
> hth
> 
>
Fred
> 
> 

Hmm...added those lines to azalia_codec.c after line 66 (without
the + signs in front
of the lines), re-compiled and rebooted but still
nothing. I guess it's something
else, then...but I'm curious as to why the
patch didn't work.



Re: How to test if sound is working?

2010-11-08 Thread Fred Crowson
On 8 November 2010 22:55, Fred Crowson  wrote:
> For some reason patch(1) did not insert the code into azalia_codec.c
> - I would guess that the reason was that patch file had some
> formatting that patch(1) did not like. Have another go at creating and
> patching the file, or you can either manually add those 7 new lines to
> azailia_codec.c after line 77 of azaila_codec.c

Sorry the 7 new lines go in after line 66 of azailia_codec.c (version
1.151 from CVS).

Fred



Re: How to test if sound is working?

2010-11-08 Thread Fred Crowson
On 8 November 2010 22:04, James Hozier  wrote:
>
> $ cat azalia_codec.c.rej
> @@ -64,6 +64,13 @@
>this->name = NULL;
>this->qrks = AZ_QRK_NONE;
>switch (this->vid) {
> +case 0x10134206:
> +this->name = "Cirrus Logic CS4206";
> +if (this->subid == 0x106b4d00) {/* APPLE_MBP55 */
> +this->qrks |= AZ_QRK_GPIO_UNMUTE_1 |
> +AZ_QRK_GPIO_UNMUTE_3;
> +}
> +break;
>case 0x10ec0260:
>this->name = "Realtek ALC260";
>break;
>
> What does this mean? It looks like a snippet of code from the original patch
file?

Hi James,

For some reason patch(1) did not insert the code into azalia_codec.c
- I would guess that the reason was that patch file had some
formatting that patch(1) did not like. Have another go at creating and
patching the file, or you can either manually add those 7 new lines to
azailia_codec.c after line 77 of azaila_codec.c

Thus when you rebuilt your kernel - it did not have this new bit of code in.

hth

Fred



Re: How to test if sound is working?

2010-11-08 Thread James Hozier
> From: Fred Crowson 
> Subject: Re: How to test if
sound is working?
> To: "James Hozier" 
> Cc:
misc@openbsd.org
> Date: Monday, November 8, 2010, 9:26 PM
> On 8 November
2010 17:10, James
> Hozier 
> wrote:
> 
> 
> >
Patching file azalia_codec.c using Plan A...
> > Hunk
> > #1 failed at 64.
> >
1 out of 1 hunks failed--saving rejects to
> azalia_codec.c.rej
> > done
> >
>
> Dunno if that means anything.
> >
> 
> The patching of the azailia_codec.c
file failed, the code
> that could
> not be patched was saved as a hunk to a
file called
> azailia_codec.c.rej <- this file will tell what
> failed...
> 
>
If it had worked it would have given you a message like:
> 
> Patching file
azalia_codec.c using Plan A...
> Hunk #1 succeeded at 64.
> Hmm...  Ignoring
the trailing garbage.
> done
> 
> hth
> 
> Fred
> 

$ cat azalia_codec.c.rej
@@ -64,6 +64,13 @@
this->name = NULL;
this->qrks = AZ_QRK_NONE;
switch (this->vid) {
+case 0x10134206:
+this->name = "Cirrus Logic
CS4206";
+if (this->subid == 0x106b4d00) {/* APPLE_MBP55 */
+
this->qrks |= AZ_QRK_GPIO_UNMUTE_1 |
+AZ_QRK_GPIO_UNMUTE_3;
+
}
+break;
case 0x10ec0260:
this->name = "Realtek ALC260";
break;

What does this mean? It looks like a snippet of code from the original
patch file?



Re: How to test if sound is working?

2010-11-08 Thread Fred Crowson
On 8 November 2010 17:10, James Hozier  wrote:


> Patching file azalia_codec.c using Plan A...
> Hunk
> #1 failed at 64.
> 1 out of 1 hunks failed--saving rejects to azalia_codec.c.rej
> done
>
> Dunno if that means anything.
>

The patching of the azailia_codec.c file failed, the code that could
not be patched was saved as a hunk to a file called
azailia_codec.c.rej <- this file will tell what failed...

If it had worked it would have given you a message like:

Patching file azalia_codec.c using Plan A...
Hunk #1 succeeded at 64.
Hmm...  Ignoring the trailing garbage.
done

hth

Fred



Re: How to test if sound is working?

2010-11-08 Thread James Hozier
> From: Jacob Meuser 
> Subject: Re: How to test if
sound is working?
> To: misc@openbsd.org
> Date: Monday, November 8, 2010,
4:36 AM
> 
> it appears you don't get any sound because the outputs are
>
controlled
> by gpio pins.  see if the following fixes it.
> 
> 1. save this
mail as a plain text file somewhere.
> 2. make sure you have kernel sources
installed.  (see
> the faq if necessary)
> 3. cd /sys/dev/pci && patch -p 0 <
 this file>
> 4. build and install kernel. (see faq if necessary)
>
5. reboot
> 
> -- 
> jake...@sdf.lonestar.org
> SDF Public Access UNIX System
- http://sdf.lonestar.org
> 
> Index: azalia_codec.c
>
===
> RCS
file: /cvs/src/sys/dev/pci/azalia_codec.c,v
> retrieving revision 1.151
> diff
-u -p azalia_codec.c
> --- azalia_codec.c10 Sep 2010 15:11:23
> -   
1.151
> +++ azalia_codec.c8 Nov 2010 04:29:59
> -
> @@ -64,6 +64,13 @@
azalia_codec_init_vtbl(codec_t *this)
>  this->name = NULL;
> 
this->qrks = AZ_QRK_NONE;
>  switch (this->vid) {
> +case 0x10134206:
> +this->name =
> "Cirrus Logic CS4206";
> +if (this->subid
>
== 0x106b4d00) {/* APPLE_MBP55 */
> +   
> this->qrks |=
AZ_QRK_GPIO_UNMUTE_1 |
> +   
> AZ_QRK_GPIO_UNMUTE_3;
> +}
> +break;
>  case 0x10ec0260:
>  this->name =
> "Realtek
ALC260";
>  break;
> 
> 

Just rebooted, tweaked mixerctl settings
several times, and nothing. Same results as
before...

For what it's worth,
when I patched azalia_codec, this is what it said:

Hmm...  Looks like a
unified diff to me...
The text leading up to this was:
--
|Index: azalia_codec.c
|===
|RCS
file: /cvs/src/sys/dev/pci/azalia_codec.c,v
|retrieving revision 1.151
|diff
-u -p azalia_codec.c
|--- azalia_codec.c10 Sep 2010 15:11:23 -
1.151
|+++ azalia_codec.c8 Nov 2010 04:29:59 -
--
Patching file azalia_codec.c using Plan A...
Hunk
#1 failed at 64.
1 out of 1 hunks failed--saving rejects to azalia_codec.c.rej
done

Dunno if that means anything.

Here is my current mixerctl settings:

$
mixerctl -v
inputs.dac-0:1_mute=off  [ off on ]
inputs.dac-0:1=250,250
inputs.dac-2:3_mute=off  [ off on ]
inputs.dac-2:3=250,250
record.adc-0:1_source=mic  [ mic ]
record.adc-0:1_mute=off  [ off on ]
record.adc-0:1=248,248 
outputs.hp_source=dac-0:1  [ dac-0:1 ]
outputs.hp_boost=on  [ off on ]
outputs.spkr_source=  [ ]
outputs.spkr2_source=dac-2:3  [ dac-2:3 ]
inputs.mic=170,170
outputs.mic_dir=input-vr80  [ none input input-vr0 input-vr50 input-vr80 ]
outputs.SPDIF_source=dig-dac-0:1  [ dig-dac-0:1 ]
outputs.hp_sense=plugged  [
unplugged plugged ]
outputs.spkr2_muters=hp  { hp }
outputs.master=250,250
outputs.master.mute=off  [ off on ]
outputs.master.slaves=dac-0:1,dac-2:3  {
dac-0:1 dac-2:3 }
record.volume=250,250 
record.volume.mute=off  [ off on ]
record.volume.slaves=adc-0:1  { adc-0:1 mic }
outputs.mode=analog  [ analog
digital ]

I change it up with different combos and restart my music player
each time to test.



Re: How to test if sound is working?

2010-11-07 Thread Jacob Meuser
On Sun, Nov 07, 2010 at 04:18:34PM -0800, James Hozier wrote:

> Oh, I've tried a lot of different combos
> yesterday and this was one of them. Tried
> both settings with my speakers, and
> tried both settings with my headphones plugged
> in.

it appears you don't get any sound because the outputs are controlled
by gpio pins.  see if the following fixes it.

1. save this mail as a plain text file somewhere.
2. make sure you have kernel sources installed.  (see the faq if necessary)
3. cd /sys/dev/pci && patch -p 0 < 
4. build and install kernel. (see faq if necessary)
5. reboot

-- 
jake...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

Index: azalia_codec.c
===
RCS file: /cvs/src/sys/dev/pci/azalia_codec.c,v
retrieving revision 1.151
diff -u -p azalia_codec.c
--- azalia_codec.c  10 Sep 2010 15:11:23 -  1.151
+++ azalia_codec.c  8 Nov 2010 04:29:59 -
@@ -64,6 +64,13 @@ azalia_codec_init_vtbl(codec_t *this)
this->name = NULL;
this->qrks = AZ_QRK_NONE;
switch (this->vid) {
+   case 0x10134206:
+   this->name = "Cirrus Logic CS4206";
+   if (this->subid == 0x106b4d00) {/* APPLE_MBP55 */
+   this->qrks |= AZ_QRK_GPIO_UNMUTE_1 |
+   AZ_QRK_GPIO_UNMUTE_3;
+   }
+   break;
case 0x10ec0260:
this->name = "Realtek ALC260";
break;



Re: How to test if sound is working?

2010-11-07 Thread James Hozier
> From: Arnaud Bergeron 
> Subject: Re: How to test if
sound is working?
> To: "James Hozier" 
> Date: Sunday,
November 7, 2010, 4:36 PM
> >
> > mixerctl -v:
> >
> > $ mixerctl -v
> >
inputs.dac-0:1_mute=off  [ off on ]
> > inputs.dac-0:1=200,200
> >
inputs.dac-2:3_mute=off  [ off on ]
> > inputs.dac-2:3=254,254
> >
record.adc-0:1_source=mic  [ mic ]
> > record.adc-0:1_mute=off  [ off on ]
> >
record.adc-0:1=0,0
> > outputs.hp_source=dac-0:1  [ dac-0:1 ]
> >
outputs.hp_boost=off  [ off on ]
> > outputs.spkr_source=  [ ]
> >
outputs.spkr2_source=dac-2:3  [ dac-2:3 ]
> > inputs.mic=85,85
> >
outputs.mic_dir=input-vr80  [ none input input-vr0
> input-vr50 input-vr80 ]
>
> outputs.SPDIF_source=dig-dac-0:1  [ dig-dac-0:1 ]
> 
> >
outputs.hp_sense=plugged  [ unplugged plugged ]
> 
> Could it be because of
this?  Do you have headphones
> plugged in?  If
> you don't it is possible the
headphones sensor is stuck in
> the
> 'plugged' position.  It happened to me
in the past.
> 
> > outputs.spkr2_muters=hp  { hp }
> > outputs.master=200,200
> > outputs.master.mute=off  [ off on ]
> >
outputs.master.slaves=dac-0:1,dac-2:3  { dac-0:1
> dac-2:3 }
> >
record.volume=0,0
> > record.volume.mute=on  [ off on ]
> >
record.volume.slaves=adc-0:1  { adc-0:1 mic }
> > outputs.mode=analog  [
analog digital ]
> 
> -- 
> La brigade SnW veut vous recruter -
http://www.brigadesnw.com
> 

Oh, I've tried a lot of different combos
yesterday and this was one of them. Tried
both settings with my speakers, and
tried both settings with my headphones plugged
in.



Re: How to test if sound is working?

2010-11-06 Thread Jacob Meuser
On Sat, Nov 06, 2010 at 01:08:40PM -0700, James Hozier wrote:
> > From: Jacob Meuser 
> > Subject: Re: How to test if sound is working?
> > To: misc@openbsd.org
> > Date: Saturday, November 6, 2010, 7:14 PM
> > On Sat, Nov 06, 2010 at 10:48:52AM
> > -0700, James Hozier wrote:
> > > I've been trying to get my sound working and tried
> > playing an audio file with mplayer,
> > > xmms, and vlc, and it seems like it's playing fine (I
> > can even see the visual bars
> > > moving in xmms) but I get no sound at all with my
> > speakers up all the way. Here is
> > > what I have done so far:
> > > 
> > > As per the FAQ's instructions:
> > > 
> > > $ cat > /dev/audio < /dev/zero &
> > > [1] 6310
> > > $ audioctl play.{seek,samples,errors}
> > > play.seek=48000
> > > play.samples=1833600
> > > play.errors=0
> > > $ audioctl play.{seek,samples,errors}
> > > play.seek=57600
> > > play.samples=4089600
> > > play.errors=0
> > > $ audioctl play.{seek,samples,errors}
> > > play.seek=57600
> > > play.samples=5299200
> > > play.errors=0
> > > $ kill %1
> > > $ fg %1
> > > cat > /dev/audio < /dev/zero 
> > > Terminated
> > > 
> > > It seems as if it's okay with the samples increasing
> > each time,
> > > 
> > > mixer settings:
> > > 
> > > $ mixerctl
> > > inputs.dac-0:1_mute=off
> > > inputs.dac-0:1=200,200
> > > inputs.dac-2:3_mute=off
> > > inputs.dac-2:3=126,126
> > > record.adc-0:1_source=mic
> > > record.adc-0:1_mute=off
> > > record.adc-0:1=124,124
> > > outputs.hp_source=dac-0:1
> > > outputs.hp_boost=off
> > > outputs.spkr_source=
> > > outputs.spkr2_source=dac-2:3
> > > inputs.mic=85,85
> > > outputs.mic_dir=input-vr80
> > > outputs.SPDIF_source=dig-dac-0:1
> > > outputs.hp_sense=plugged
> > > outputs.spkr2_muters=hp
> > > outputs.master=200,200
> > > outputs.master.mute=off
> > > outputs.master.slaves=dac-0:1,dac-2:3
> > > record.volume=124,124
> > > record.volume.mute=off
> > > record.volume.slaves=adc-0:1
> > > outputs.mode=analog
> > > 
> > > Everything seems to be at a reasonable volume and
> > nothing is muted,
> > > 
> > > And I'm not sure how to figure out what kind of audio
> > hardware I have, so I just
> > > tried this:
> > > 
> > > $ dmesg | grep audio
> > > audio0 at azalia0
> > > 
> > > What else can I try?
> > 
> > full dmesg and mixerctl -v output.
> > 
> > -- 
> > jake...@sdf.lonestar.org
> > SDF Public Access UNIX System - http://sdf.lonestar.org
> > 
> > 
> 
> mixerctl -v:
> 
> $ mixerctl -v
> inputs.dac-0:1_mute=off  [ off on ]
> inputs.dac-0:1=200,200 
> inputs.dac-2:3_mute=off  [ off on ]
> inputs.dac-2:3=254,254 
> record.adc-0:1_source=mic  [ mic ]
> record.adc-0:1_mute=off  [ off on ]
> record.adc-0:1=0,0 
> outputs.hp_source=dac-0:1  [ dac-0:1 ]
> outputs.hp_boost=off  [ off on ]
> outputs.spkr_source=  [ ]
> outputs.spkr2_source=dac-2:3  [ dac-2:3 ]
> inputs.mic=85,85 
> outputs.mic_dir=input-vr80  [ none input input-vr0 input-vr50 input-vr80 ]
> outputs.SPDIF_source=dig-dac-0:1  [ dig-dac-0:1 ]
> outputs.hp_sense=plugged  [ unplugged plugged ]
> outputs.spkr2_muters=hp  { hp }
> outputs.master=200,200 
> outputs.master.mute=off  [ off on ]
> outputs.master.slaves=dac-0:1,dac-2:3  { dac-0:1 dac-2:3 }
> record.volume=0,0 
> record.volume.mute=on  [ off on ]
> record.volume.slaves=adc-0:1  { adc-0:1 mic }
> outputs.mode=analog  [ analog digital ]
> 
> full dmesg:
> 
> $ dmesg
> OpenBSD 4.8 (GENERIC.MP) #359: Mon Aug 16 09:16:26 MDT 2010
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> RTC BIOS diagnostic error 
> f7
> cpu0: Intel(R) Core(TM)2 Duo CPU P7550 @ 2.26GHz ("GenuineIntel" 686-class) 
> 2.26 GHz
> cpu0: 
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE
> real mem  = 2926321664 (2790MB)
> avail mem = 2868469760 (2735MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (42 
> entries)
> bios0: vendor Apple Inc. version "MBP55.88Z.00AC.B03.0906151708" date 06/15/09
> bios0: Apple Inc. MacBookPro5,5

a

Re: How to test if sound is working?

2010-11-06 Thread James Hozier
> From: Jacob Meuser 
> Subject: Re: How to test if sound is working?
> To: misc@openbsd.org
> Date: Saturday, November 6, 2010, 7:14 PM
> On Sat, Nov 06, 2010 at 10:48:52AM
> -0700, James Hozier wrote:
> > I've been trying to get my sound working and tried
> playing an audio file with mplayer,
> > xmms, and vlc, and it seems like it's playing fine (I
> can even see the visual bars
> > moving in xmms) but I get no sound at all with my
> speakers up all the way. Here is
> > what I have done so far:
> > 
> > As per the FAQ's instructions:
> > 
> > $ cat > /dev/audio < /dev/zero &
> > [1] 6310
> > $ audioctl play.{seek,samples,errors}
> > play.seek=48000
> > play.samples=1833600
> > play.errors=0
> > $ audioctl play.{seek,samples,errors}
> > play.seek=57600
> > play.samples=4089600
> > play.errors=0
> > $ audioctl play.{seek,samples,errors}
> > play.seek=57600
> > play.samples=5299200
> > play.errors=0
> > $ kill %1
> > $ fg %1
> > cat > /dev/audio < /dev/zero 
> > Terminated
> > 
> > It seems as if it's okay with the samples increasing
> each time,
> > 
> > mixer settings:
> > 
> > $ mixerctl
> > inputs.dac-0:1_mute=off
> > inputs.dac-0:1=200,200
> > inputs.dac-2:3_mute=off
> > inputs.dac-2:3=126,126
> > record.adc-0:1_source=mic
> > record.adc-0:1_mute=off
> > record.adc-0:1=124,124
> > outputs.hp_source=dac-0:1
> > outputs.hp_boost=off
> > outputs.spkr_source=
> > outputs.spkr2_source=dac-2:3
> > inputs.mic=85,85
> > outputs.mic_dir=input-vr80
> > outputs.SPDIF_source=dig-dac-0:1
> > outputs.hp_sense=plugged
> > outputs.spkr2_muters=hp
> > outputs.master=200,200
> > outputs.master.mute=off
> > outputs.master.slaves=dac-0:1,dac-2:3
> > record.volume=124,124
> > record.volume.mute=off
> > record.volume.slaves=adc-0:1
> > outputs.mode=analog
> > 
> > Everything seems to be at a reasonable volume and
> nothing is muted,
> > 
> > And I'm not sure how to figure out what kind of audio
> hardware I have, so I just
> > tried this:
> > 
> > $ dmesg | grep audio
> > audio0 at azalia0
> > 
> > What else can I try?
> 
> full dmesg and mixerctl -v output.
> 
> -- 
> jake...@sdf.lonestar.org
> SDF Public Access UNIX System - http://sdf.lonestar.org
> 
> 

mixerctl -v:

$ mixerctl -v
inputs.dac-0:1_mute=off  [ off on ]
inputs.dac-0:1=200,200 
inputs.dac-2:3_mute=off  [ off on ]
inputs.dac-2:3=254,254 
record.adc-0:1_source=mic  [ mic ]
record.adc-0:1_mute=off  [ off on ]
record.adc-0:1=0,0 
outputs.hp_source=dac-0:1  [ dac-0:1 ]
outputs.hp_boost=off  [ off on ]
outputs.spkr_source=  [ ]
outputs.spkr2_source=dac-2:3  [ dac-2:3 ]
inputs.mic=85,85 
outputs.mic_dir=input-vr80  [ none input input-vr0 input-vr50 input-vr80 ]
outputs.SPDIF_source=dig-dac-0:1  [ dig-dac-0:1 ]
outputs.hp_sense=plugged  [ unplugged plugged ]
outputs.spkr2_muters=hp  { hp }
outputs.master=200,200 
outputs.master.mute=off  [ off on ]
outputs.master.slaves=dac-0:1,dac-2:3  { dac-0:1 dac-2:3 }
record.volume=0,0 
record.volume.mute=on  [ off on ]
record.volume.slaves=adc-0:1  { adc-0:1 mic }
outputs.mode=analog  [ analog digital ]

full dmesg:

$ dmesg
OpenBSD 4.8 (GENERIC.MP) #359: Mon Aug 16 09:16:26 MDT 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 
f7
cpu0: Intel(R) Core(TM)2 Duo CPU P7550 @ 2.26GHz ("GenuineIntel" 686-class) 
2.26 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE
real mem  = 2926321664 (2790MB)
avail mem = 2868469760 (2735MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (42 
entries)
bios0: vendor Apple Inc. version "MBP55.88Z.00AC.B03.0906151708" date 06/15/09
bios0: Apple Inc. MacBookPro5,5
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) EC__(S3) OHC1(S3) EHC1(S3) OHC2(S3) 
EHC2(S3) GIGE(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2500 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 265MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P7550 @ 2.26GHz ("GenuineIntel" 686-class) 
2.26 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SS

Re: How to test if sound is working?

2010-11-06 Thread Jacob Meuser
On Sat, Nov 06, 2010 at 10:48:52AM -0700, James Hozier wrote:
> I've been trying to get my sound working and tried playing an audio file with 
> mplayer,
> xmms, and vlc, and it seems like it's playing fine (I can even see the visual 
> bars
> moving in xmms) but I get no sound at all with my speakers up all the way. 
> Here is
> what I have done so far:
> 
> As per the FAQ's instructions:
> 
> $ cat > /dev/audio < /dev/zero &
> [1] 6310
> $ audioctl play.{seek,samples,errors}
> play.seek=48000
> play.samples=1833600
> play.errors=0
> $ audioctl play.{seek,samples,errors}
> play.seek=57600
> play.samples=4089600
> play.errors=0
> $ audioctl play.{seek,samples,errors}
> play.seek=57600
> play.samples=5299200
> play.errors=0
> $ kill %1
> $ fg %1
> cat > /dev/audio < /dev/zero 
> Terminated
> 
> It seems as if it's okay with the samples increasing each time,
> 
> mixer settings:
> 
> $ mixerctl
> inputs.dac-0:1_mute=off
> inputs.dac-0:1=200,200
> inputs.dac-2:3_mute=off
> inputs.dac-2:3=126,126
> record.adc-0:1_source=mic
> record.adc-0:1_mute=off
> record.adc-0:1=124,124
> outputs.hp_source=dac-0:1
> outputs.hp_boost=off
> outputs.spkr_source=
> outputs.spkr2_source=dac-2:3
> inputs.mic=85,85
> outputs.mic_dir=input-vr80
> outputs.SPDIF_source=dig-dac-0:1
> outputs.hp_sense=plugged
> outputs.spkr2_muters=hp
> outputs.master=200,200
> outputs.master.mute=off
> outputs.master.slaves=dac-0:1,dac-2:3
> record.volume=124,124
> record.volume.mute=off
> record.volume.slaves=adc-0:1
> outputs.mode=analog
> 
> Everything seems to be at a reasonable volume and nothing is muted,
> 
> And I'm not sure how to figure out what kind of audio hardware I have, so I 
> just
> tried this:
> 
> $ dmesg | grep audio
> audio0 at azalia0
> 
> What else can I try?

full dmesg and mixerctl -v output.

-- 
jake...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org