From bugmaster at FreeBSD.org Mon Aug 3 11:07:09 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 3 11:09:58 2009 Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org Message-ID: <200908031107.n73B77SB088787@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/113556 sparc64 [panic] trap: memory address not aligned; Rebooting... f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 [hang] system is hung during boot from CD o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 12 problems total. From rc at networkz.ch Fri Aug 7 18:18:01 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Fri Aug 7 18:18:10 2009 Subject: Audio on Sunblade 100 Message-ID: <4A7C6B50.3070503@networkz.ch> Hi I'm trying to get sound on a Sunblade 100 with 7.2R. I've added device sound device snd_t4dwave to the kernel and recompiled. pciconf shows an attached driver: pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 rev=0x01 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M5451 PCI AC-Link Controller Audio Device' class = multimedia subclass = audio However, there are errors in dmesg: pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed I've also found this message from 2006: http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html So, am I just doing something wrong or are there problems with 5451 audio on SPARC? I see that the release notes only list i386 and amd64 as architectures for the t4dwave driver. By the way, thanks a lot for all the work your guys are doing in general and for the SPARC port in particular. I'm currently trying BSD for the first time in my life and I like it a lot. It runs surprisingly well on this outdated platform. Christian -- rc at networkz dot ch From bugmaster at FreeBSD.org Mon Aug 10 11:07:05 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 10 11:09:26 2009 Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org Message-ID: <200908101107.n7AB74ST025306@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/113556 sparc64 [panic] trap: memory address not aligned; Rebooting... f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 [hang] system is hung during boot from CD o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 12 problems total. From naddy at mips.inka.de Tue Aug 11 22:40:12 2009 From: naddy at mips.inka.de (Christian Weisgerber) Date: Tue Aug 11 22:40:44 2009 Subject: Audio on Sunblade 100 References: <4A7C6B50.3070503@networkz.ch> Message-ID: Christian Ramseyer wrote: > I've also found this message from 2006: > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html "However AFAIK the hardware can't handle DMA addresses located above 1GB. Since sparc64 uses DVMA and if the DVMA address is higher than 1GB it wouldn't work at all." FWIW, I have a Blade 100 running OpenBSD and sound works fine there with OpenBSD's autri(4) driver. I don't see any provisions for dealing with such an address limit in the driver, so I doubt the claim above. -- Christian "naddy" Weisgerber naddy@mips.inka.de From gavin at FreeBSD.org Sat Aug 15 20:51:06 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Sat Aug 15 20:51:13 2009 Subject: sparc64/137800: -CURRENT on sparc64 immediate "panic: mtx_init: mtx_lock not aligned for turnstile chain: 0xc06489f8" Message-ID: <200908152051.n7FKp6sM029572@freefall.freebsd.org> Synopsis: -CURRENT on sparc64 immediate "panic: mtx_init: mtx_lock not aligned for turnstile chain: 0xc06489f8" Responsible-Changed-From-To: freebsd-bugs->freebsd-sparc64 Responsible-Changed-By: gavin Responsible-Changed-When: Sat Aug 15 20:49:56 UTC 2009 Responsible-Changed-Why: I suspect that this is some MD problem on sparc64, and not directly related to the commit that triggers the problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=137800 From bz at FreeBSD.org Sat Aug 15 21:47:15 2009 From: bz at FreeBSD.org (bz@FreeBSD.org) Date: Sat Aug 15 21:47:21 2009 Subject: sparc64/137800: -CURRENT on sparc64 immediate "panic: mtx_init: mtx_lock not aligned for turnstile chain: 0xc06489f8" Message-ID: <200908152147.n7FLlFWY070518@freefall.freebsd.org> Synopsis: -CURRENT on sparc64 immediate "panic: mtx_init: mtx_lock not aligned for turnstile chain: 0xc06489f8" Responsible-Changed-From-To: freebsd-sparc64->bz Responsible-Changed-By: bz Responsible-Changed-When: Sat Aug 15 21:46:12 UTC 2009 Responsible-Changed-Why: Mine. I got input form kib on why it's an issue for sparc64 and I think ia64 might have the same problem. We'll either disable the check or find something better that actually works on all platforms. http://www.freebsd.org/cgi/query-pr.cgi?pr=137800 From bugmaster at FreeBSD.org Mon Aug 17 11:07:04 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 17 11:09:45 2009 Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org Message-ID: <200908171107.n7HB73fN075946@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/113556 sparc64 [panic] trap: memory address not aligned; Rebooting... f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 [hang] system is hung during boot from CD o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 12 problems total. From marius at alchemy.franken.de Mon Aug 17 20:53:45 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Mon Aug 17 20:53:51 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A7C6B50.3070503@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> Message-ID: <20090817205340.GA75477@alchemy.franken.de> On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > Hi > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > device sound > device snd_t4dwave > > to the kernel and recompiled. pciconf shows an attached driver: > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > rev=0x01 hdr=0x00 > vendor = 'Acer Labs Incorporated (ALi/ULi)' > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > class = multimedia > subclass = audio > > However, there are errors in dmesg: > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > 8.0 on pci0 > pcm0: > pcm0: [GIANT-LOCKED] > pcm0: [ITHREAD] > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > I've also found this message from 2006: > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > So, am I just doing something wrong or are there problems with 5451 > audio on SPARC? I see that the release notes only list i386 and amd64 as > architectures for the t4dwave driver. > > By the way, thanks a lot for all the work your guys are doing in general > and for the SPARC port in particular. I'm currently trying BSD for the > first time in my life and I like it a lot. It runs surprisingly well on > this outdated platform. > Could you (or any other Blade 100 user) please give the following patch at try? http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff This gets at least the line-out of the M5451 in my Blade 1500 working (I've no idea whether its internal speaker is also connected to the sound chip like for example in a Blade 1000 and thus supposed to also work or just to a PC-style beeper, the firmware at least makes it beep that way...), but which also has a newer revision of this chip. Marius From marius at alchemy.franken.de Mon Aug 17 21:56:15 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Mon Aug 17 21:56:22 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090817205340.GA75477@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> Message-ID: <20090817215612.GB75477@alchemy.franken.de> On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > Hi > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > device sound > > device snd_t4dwave > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > rev=0x01 hdr=0x00 > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > class = multimedia > > subclass = audio > > > > However, there are errors in dmesg: > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > 8.0 on pci0 > > pcm0: > > pcm0: [GIANT-LOCKED] > > pcm0: [ITHREAD] > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > I've also found this message from 2006: > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > So, am I just doing something wrong or are there problems with 5451 > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > architectures for the t4dwave driver. > > > > By the way, thanks a lot for all the work your guys are doing in general > > and for the SPARC port in particular. I'm currently trying BSD for the > > first time in my life and I like it a lot. It runs surprisingly well on > > this outdated platform. > > > > Could you (or any other Blade 100 user) please give the following > patch at try? > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > This gets at least the line-out of the M5451 in my Blade 1500 > working (I've no idea whether its internal speaker is also > connected to the sound chip like for example in a Blade 1000 > and thus supposed to also work or just to a PC-style beeper, > the firmware at least makes it beep that way...), but which > also has a newer revision of this chip. > Looks like I've spoken to soon; it only works when it happens to get certain buffer addresses, otherwise nothing is played and the interrupt times out (which according to google isn't a sparc64 specific problem). This probably means that some bus_dma(9) parameters are incorrect... Marius From pyunyh at gmail.com Mon Aug 17 22:54:13 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Mon Aug 17 22:54:20 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090817215612.GB75477@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> Message-ID: <20090817223051.GB1369@michelle.cdnetworks.com> On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > Hi > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > device sound > > > device snd_t4dwave > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > rev=0x01 hdr=0x00 > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > class = multimedia > > > subclass = audio > > > > > > However, there are errors in dmesg: > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > 8.0 on pci0 > > > pcm0: > > > pcm0: [GIANT-LOCKED] > > > pcm0: [ITHREAD] > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > I've also found this message from 2006: > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > architectures for the t4dwave driver. > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > first time in my life and I like it a lot. It runs surprisingly well on > > > this outdated platform. > > > > > > > Could you (or any other Blade 100 user) please give the following > > patch at try? > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff 404 > > This gets at least the line-out of the M5451 in my Blade 1500 > > working (I've no idea whether its internal speaker is also > > connected to the sound chip like for example in a Blade 1000 > > and thus supposed to also work or just to a PC-style beeper, > > the firmware at least makes it beep that way...), but which > > also has a newer revision of this chip. > > > > Looks like I've spoken to soon; it only works when it happens > to get certain buffer addresses, otherwise nothing is played > and the interrupt times out (which according to google isn't > a sparc64 specific problem). This probably means that some > bus_dma(9) parameters are incorrect... > Since I couldn't get the patch I don't know what it does, but the PCI trident 4D wave NX hardware I had surely had DMA address limitations where MSB 2bits of LBA register are used as other purposes. I don't know 4D wave compatible controller on Blade 100 removed this limitation. Marius, does the DVMA base address of blade 100 is lower than 1GB? From marius at alchemy.franken.de Tue Aug 18 06:51:49 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Tue Aug 18 06:51:56 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090817223051.GB1369@michelle.cdnetworks.com> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090817223051.GB1369@michelle.cdnetworks.com> Message-ID: <20090818065147.GI25891@alchemy.franken.de> On Mon, Aug 17, 2009 at 03:30:51PM -0700, Pyun YongHyeon wrote: > On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > > Hi > > > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > > > device sound > > > > device snd_t4dwave > > > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > > rev=0x01 hdr=0x00 > > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > > class = multimedia > > > > subclass = audio > > > > > > > > However, there are errors in dmesg: > > > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > > 8.0 on pci0 > > > > pcm0: > > > > pcm0: [GIANT-LOCKED] > > > > pcm0: [ITHREAD] > > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > > > I've also found this message from 2006: > > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > > architectures for the t4dwave driver. > > > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > > first time in my life and I like it a lot. It runs surprisingly well on > > > > this outdated platform. > > > > > > > > > > Could you (or any other Blade 100 user) please give the following > > > patch at try? > > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > > 404 > > > > This gets at least the line-out of the M5451 in my Blade 1500 > > > working (I've no idea whether its internal speaker is also > > > connected to the sound chip like for example in a Blade 1000 > > > and thus supposed to also work or just to a PC-style beeper, > > > the firmware at least makes it beep that way...), but which > > > also has a newer revision of this chip. > > > > > > > Looks like I've spoken to soon; it only works when it happens > > to get certain buffer addresses, otherwise nothing is played > > and the interrupt times out (which according to google isn't > > a sparc64 specific problem). This probably means that some > > bus_dma(9) parameters are incorrect... > > > > Since I couldn't get the patch I don't know what it does, but > the PCI trident 4D wave NX hardware I had surely had DMA address > limitations where MSB 2bits of LBA register are used as other > purposes. I don't know 4D wave compatible controller on Blade 100 > removed this limitation. > Marius, does the DVMA base address of blade 100 is lower than 1GB? No, but the M5451 actually does 31-bit DMA and in order to generate 32-bit DMA the 31st bit can be set via its accompanying ISA bridge. Marius From marius at alchemy.franken.de Tue Aug 18 19:27:52 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Tue Aug 18 19:27:59 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090817215612.GB75477@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> Message-ID: <20090818192748.GA6585@alchemy.franken.de> On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > Hi > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > device sound > > > device snd_t4dwave > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > rev=0x01 hdr=0x00 > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > class = multimedia > > > subclass = audio > > > > > > However, there are errors in dmesg: > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > 8.0 on pci0 > > > pcm0: > > > pcm0: [GIANT-LOCKED] > > > pcm0: [ITHREAD] > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > I've also found this message from 2006: > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > architectures for the t4dwave driver. > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > first time in my life and I like it a lot. It runs surprisingly well on > > > this outdated platform. > > > > > > > Could you (or any other Blade 100 user) please give the following > > patch at try? > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > > This gets at least the line-out of the M5451 in my Blade 1500 > > working (I've no idea whether its internal speaker is also > > connected to the sound chip like for example in a Blade 1000 > > and thus supposed to also work or just to a PC-style beeper, > > the firmware at least makes it beep that way...), but which > > also has a newer revision of this chip. > > > > Looks like I've spoken to soon; it only works when it happens > to get certain buffer addresses, otherwise nothing is played > and the interrupt times out (which according to google isn't > a sparc64 specific problem). This probably means that some > bus_dma(9) parameters are incorrect... > Ok, I think I've identified the incorrect bus_dma(9) settings with the help of Tatsuo YOKOGAWA's ali(4) (which as least for the alignment requirement also matches the NetBSD autri(4). A new patch is at: http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff This version now also basically works with the GENIALstation 777s, but there seems to be a problem with ac94(4) on that machine or it's wired strangely as I've to turn on the "PhoneOut" output in the mixer in order to get sound and its quality is likewise, though with the Blade 1500 all seems fine. If someone could test how far this patch gets things into working with Blade 100 that would be great. Marius From rc at networkz.ch Wed Aug 19 10:56:36 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Wed Aug 19 10:56:43 2009 Subject: Audio on Sunlade 100 Message-ID: <4A8BDA5F.4060703@networkz.ch> > Ok, I think I've identified the incorrect bus_dma(9) settings > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > the alignment requirement also matches the NetBSD autri(4). A > new patch is at: > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff Thanks, I'll give it a try and report back. Christian From ardelean at ww.uni-erlangen.de Wed Aug 19 12:47:46 2009 From: ardelean at ww.uni-erlangen.de (Gheorghe Ardelean) Date: Wed Aug 19 12:47:53 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090818192748.GA6585@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> Message-ID: On Tue, 18 Aug 2009, Marius Strobl wrote: > On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: >> On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: >>> On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: >>>> Hi >>>> >>>> I'm trying to get sound on a Sunblade 100 with 7.2R. I've added >>>> >>>> device sound >>>> device snd_t4dwave >>>> >>>> to the kernel and recompiled. pciconf shows an attached driver: >>>> >>>> pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 >>>> rev=0x01 hdr=0x00 >>>> vendor = 'Acer Labs Incorporated (ALi/ULi)' >>>> device = 'ALI M5451 PCI AC-Link Controller Audio Device' >>>> class = multimedia >>>> subclass = audio >>>> >>>> However, there are errors in dmesg: >>>> >>>> pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device >>>> 8.0 on pci0 >>>> pcm0: >>>> pcm0: [GIANT-LOCKED] >>>> pcm0: [ITHREAD] >>>> pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 >>>> pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed >>>> pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 >>>> pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed >>>> >>>> I've also found this message from 2006: >>>> http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html >>>> >>>> So, am I just doing something wrong or are there problems with 5451 >>>> audio on SPARC? I see that the release notes only list i386 and amd64 as >>>> architectures for the t4dwave driver. >>>> >>>> By the way, thanks a lot for all the work your guys are doing in general >>>> and for the SPARC port in particular. I'm currently trying BSD for the >>>> first time in my life and I like it a lot. It runs surprisingly well on >>>> this outdated platform. >>>> >>> >>> Could you (or any other Blade 100 user) please give the following >>> patch at try? >>> http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff >>> This gets at least the line-out of the M5451 in my Blade 1500 >>> working (I've no idea whether its internal speaker is also >>> connected to the sound chip like for example in a Blade 1000 >>> and thus supposed to also work or just to a PC-style beeper, >>> the firmware at least makes it beep that way...), but which >>> also has a newer revision of this chip. >>> >> >> Looks like I've spoken to soon; it only works when it happens >> to get certain buffer addresses, otherwise nothing is played >> and the interrupt times out (which according to google isn't >> a sparc64 specific problem). This probably means that some >> bus_dma(9) parameters are incorrect... >> > > Ok, I think I've identified the incorrect bus_dma(9) settings > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > the alignment requirement also matches the NetBSD autri(4). A > new patch is at: > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff > This version now also basically works with the GENIALstation > 777s, but there seems to be a problem with ac94(4) on that > machine or it's wired strangely as I've to turn on the > "PhoneOut" output in the mixer in order to get sound and its > quality is likewise, though with the Blade 1500 all seems > fine. If someone could test how far this patch gets things > into working with Blade 100 that would be great. > > Marius > > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org" > Hi Marius, Thank you! It works on my Blade 100. Tested with mpg123! The sound is not routed to the internal speaker if no headphones are pluged in (as is the case for Ultra 1 etc) but this is not a problem. Attached please find the dmesg! Could somebody add the dmesg to my list of dmesgs on the wiki page? Best regards, Gheorghe Ardelean. -------------- next part -------------- Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE #0: Wed Aug 19 14:14:19 CEST 2009 root@blade100.ganet.de:/usr/src/sys/sparc64/compile/GENERIC real memory = 536870912 (512 MB) avail memory = 505315328 (481 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (502.00 MHz CPU) registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set kbd0 at kbdmux0 nexus0: pcib0: mem 0x1fe00000000-0x1fe0000ffff,0x1fe01000000-0x1fe010000ff irq 2032,2030,2031,2021 on nexus0 pcib0: Hummingbird compatible, impl 0, version 0, IGN 0x1f, bus A, 33MHz pcib0: DVMA map: 0xc0000000 to 0xc3ffffff pcib0: [FILTER] pcib0: [FILTER] pcib0: [GIANT-LOCKED] pcib0: [ITHREAD] pcib0: [FILTER] pci0: on pcib0 ebus0: mem 0xf0000000-0xf0ffffff,0xf1000000-0xf17fffff at device 12.0 on pci0 ebus0: : incomplete ebus0: addr 0-0xfffff (no driver attached) eeprom0: addr 0x100000000-0x100001fff on ebus0 eeprom0: model mk48t59 isab0: at device 7.0 on pci0 isa0: on isab0 gem0: mem 0x400000-0x41ffff at device 12.1 on pci0 miibus0: on gem0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 2kB RX FIFO, 2kB TX FIFO gem0: Ethernet address: 00:03:ba:08:xy:xz gem0: [ITHREAD] fwohci0: mem 0x420000-0x4207ff,0x422000-0x4227ff at device 12.2 on pci0 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:03:ba:ff:fe:08:0b:a1 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:03:ba:08:0b:a1 fwe0: Ethernet address: 02:03:ba:08:0b:a1 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xc1128000 fwip0: on firewire0 fwip0: Firewire address: 00:03:ba:ff:fe:08:0b:a1 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode ohci0: mem 0x2000000-0x2007fff at device 12.3 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: <(0x108e) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 4 ports with 4 removable, self powered pci0: at device 3.0 (no driver attached) pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] atapci0: port 0xa00-0xa07,0xa18-0xa1b,0xa10-0xa17,0xa08-0xa0b,0xa20-0xa2f at device 13.0 on pci0 atapci0: [ITHREAD] atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] machfb0: port 0xb00-0xbff mem 0x3000000-0x3ffffff,0x426000-0x426fff at device 19.0 on pci0 machfb0: console machfb0: 16 MB aperture at 0xfde00000 not swapped machfb0: 8188 KB SDRAM 114.992 MHz, maximum RAMDAC clock 230 MHz, DSP machfb0: resolution 1280x1024 at 8 bpp pcib1: at device 5.0 on pci0 pci1: on pcib1 sym0: <875> port 0x1000-0x10ff mem 0x4000000-0x40000ff,0x4002000-0x4002fff at device 2.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: [ITHREAD] syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x300> uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 43 on isa0 uart0: [FILTER] uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 43 on isa0 uart1: [FILTER] ums0: on uhub0 ums0: 3 buttons and Z dir. ukbd0: on uhub0 kbd1 at ukbd0 Timecounter "tick" frequency 502000000 Hz quality 1000 Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad0: 38166MB at ata2-master UDMA66 acd0: CDRW at ata2-slave PIO4 GEOM_LABEL: Label for provider ad0a is ufsid/4a8bdf49852bb47a. Trying to mount root from ufs:/dev/ad0a GEOM_LABEL: Label ufsid/4a8bdf49852bb47a removed. GEOM_LABEL: Label for provider ad0a is ufsid/4a8bdf49852bb47a. GEOM_LABEL: Label ufsid/4a8bdf49852bb47a removed. From marius at alchemy.franken.de Wed Aug 19 16:14:13 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Wed Aug 19 16:14:20 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090818192748.GA6585@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> Message-ID: <20090819161410.GA19351@alchemy.franken.de> On Tue, Aug 18, 2009 at 09:27:48PM +0200, Marius Strobl wrote: > On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > > Hi > > > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > > > device sound > > > > device snd_t4dwave > > > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > > rev=0x01 hdr=0x00 > > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > > class = multimedia > > > > subclass = audio > > > > > > > > However, there are errors in dmesg: > > > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > > 8.0 on pci0 > > > > pcm0: > > > > pcm0: [GIANT-LOCKED] > > > > pcm0: [ITHREAD] > > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > > > I've also found this message from 2006: > > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > > architectures for the t4dwave driver. > > > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > > first time in my life and I like it a lot. It runs surprisingly well on > > > > this outdated platform. > > > > > > > > > > Could you (or any other Blade 100 user) please give the following > > > patch at try? > > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > > > This gets at least the line-out of the M5451 in my Blade 1500 > > > working (I've no idea whether its internal speaker is also > > > connected to the sound chip like for example in a Blade 1000 > > > and thus supposed to also work or just to a PC-style beeper, > > > the firmware at least makes it beep that way...), but which > > > also has a newer revision of this chip. > > > > > > > Looks like I've spoken to soon; it only works when it happens > > to get certain buffer addresses, otherwise nothing is played > > and the interrupt times out (which according to google isn't > > a sparc64 specific problem). This probably means that some > > bus_dma(9) parameters are incorrect... > > > > Ok, I think I've identified the incorrect bus_dma(9) settings > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > the alignment requirement also matches the NetBSD autri(4). A > new patch is at: > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff > This version now also basically works with the GENIALstation > 777s, but there seems to be a problem with ac94(4) on that > machine or it's wired strangely as I've to turn on the > "PhoneOut" output in the mixer in order to get sound and its > quality is likewise, though with the Blade 1500 all seems > fine. If someone could test how far this patch gets things > into working with Blade 100 that would be great. > FYI, according to the OpenSolaris source, SPARC machines with AC97-based on-board audio use the AC97 MONO_OUT for the internal speaker, which in FreeBSD is mapped to PhoneOut. Turning the latter on in the Blade 1500 indeed gets its internal speaker going with a decent quality. This also means that in the GENIALstation 777s the "stereo" jack is wired to a mono output, which probably explains the lousy sound quality. Marius From pyunyh at gmail.com Wed Aug 19 17:56:54 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Aug 19 17:57:01 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090818192748.GA6585@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> Message-ID: <20090819175610.GA20481@michelle.cdnetworks.com> On Tue, Aug 18, 2009 at 09:27:48PM +0200, Marius Strobl wrote: > On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > > Hi > > > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > > > device sound > > > > device snd_t4dwave > > > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > > rev=0x01 hdr=0x00 > > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > > class = multimedia > > > > subclass = audio > > > > > > > > However, there are errors in dmesg: > > > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > > 8.0 on pci0 > > > > pcm0: > > > > pcm0: [GIANT-LOCKED] > > > > pcm0: [ITHREAD] > > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > > > I've also found this message from 2006: > > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > > architectures for the t4dwave driver. > > > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > > first time in my life and I like it a lot. It runs surprisingly well on > > > > this outdated platform. > > > > > > > > > > Could you (or any other Blade 100 user) please give the following > > > patch at try? > > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > > > This gets at least the line-out of the M5451 in my Blade 1500 > > > working (I've no idea whether its internal speaker is also > > > connected to the sound chip like for example in a Blade 1000 > > > and thus supposed to also work or just to a PC-style beeper, > > > the firmware at least makes it beep that way...), but which > > > also has a newer revision of this chip. > > > > > > > Looks like I've spoken to soon; it only works when it happens > > to get certain buffer addresses, otherwise nothing is played > > and the interrupt times out (which according to google isn't > > a sparc64 specific problem). This probably means that some > > bus_dma(9) parameters are incorrect... > > > > Ok, I think I've identified the incorrect bus_dma(9) settings > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > the alignment requirement also matches the NetBSD autri(4). A > new patch is at: > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff The patch looks good to me but I have two questions. The alignment restriction specified in bus_dma_tag_create(9) really works even if the alignment is greater than PAGE_SIZE? I vaguely remember the alignment was not satisfied last time I tried it on i386 if I specified 256K. The second question is number of channels supported for M5451. If I remember correctly there are some differences among 4D wave compatible chips and M5451 may have 32 channels instead of 64. > This version now also basically works with the GENIALstation > 777s, but there seems to be a problem with ac94(4) on that > machine or it's wired strangely as I've to turn on the > "PhoneOut" output in the mixer in order to get sound and its > quality is likewise, though with the Blade 1500 all seems > fine. If someone could test how far this patch gets things > into working with Blade 100 that would be great. > > Marius From marius at alchemy.franken.de Wed Aug 19 20:46:05 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Wed Aug 19 20:46:11 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090819175610.GA20481@michelle.cdnetworks.com> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819175610.GA20481@michelle.cdnetworks.com> Message-ID: <20090819204603.GL25891@alchemy.franken.de> On Wed, Aug 19, 2009 at 10:56:10AM -0700, Pyun YongHyeon wrote: > On Tue, Aug 18, 2009 at 09:27:48PM +0200, Marius Strobl wrote: > > On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > > > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > > > Hi > > > > > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > > > > > device sound > > > > > device snd_t4dwave > > > > > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > > > rev=0x01 hdr=0x00 > > > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > > > class = multimedia > > > > > subclass = audio > > > > > > > > > > However, there are errors in dmesg: > > > > > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > > > 8.0 on pci0 > > > > > pcm0: > > > > > pcm0: [GIANT-LOCKED] > > > > > pcm0: [ITHREAD] > > > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > > > > > I've also found this message from 2006: > > > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > > > architectures for the t4dwave driver. > > > > > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > > > first time in my life and I like it a lot. It runs surprisingly well on > > > > > this outdated platform. > > > > > > > > > > > > > Could you (or any other Blade 100 user) please give the following > > > > patch at try? > > > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > > > > This gets at least the line-out of the M5451 in my Blade 1500 > > > > working (I've no idea whether its internal speaker is also > > > > connected to the sound chip like for example in a Blade 1000 > > > > and thus supposed to also work or just to a PC-style beeper, > > > > the firmware at least makes it beep that way...), but which > > > > also has a newer revision of this chip. > > > > > > > > > > Looks like I've spoken to soon; it only works when it happens > > > to get certain buffer addresses, otherwise nothing is played > > > and the interrupt times out (which according to google isn't > > > a sparc64 specific problem). This probably means that some > > > bus_dma(9) parameters are incorrect... > > > > > > > Ok, I think I've identified the incorrect bus_dma(9) settings > > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > > the alignment requirement also matches the NetBSD autri(4). A > > new patch is at: > > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff > > The patch looks good to me but I have two questions. The alignment > restriction specified in bus_dma_tag_create(9) really works even > if the alignment is greater than PAGE_SIZE? I vaguely remember > the alignment was not satisfied last time I tried it on i386 if I > specified 256K. Hrm, from a quick check of the i386 busdma and the sparc64 busdma and IOMMU code I see no indication why such an alignment shouldn't work as expected, neither do relevant man pages like bus_dma(9) and contigmalloc(9) indicate a restriction to PAGE_SIZE. Based on the addresses of the buffers I get on sparc64 (f.e. 0xc0000000 and 0xc0020000) I'd also say it just works. But before possibly commiting this change I've to also run-time check it on i386 anyway. > The second question is number of channels > supported for M5451. If I remember correctly there are some > differences among 4D wave compatible chips and M5451 may have 32 > channels instead of 64. Well, r173511 limited the driver to effectively only use one channel with M5451 and given that the same change added a knob I suspect that it was also actually tested with more than one channel but that also failed. Do you mean that the interation in the interrupt handler should be limited to 32 (according to the M1535 datasheet [1] that number is correct) for M5451 or maybe also to the number of channels registered? Marius [1]: www.nvidia.com/docs/CP/29993/m1535dm_web.pdf From pyunyh at gmail.com Wed Aug 19 21:08:43 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Aug 19 21:08:50 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090819204603.GL25891@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819175610.GA20481@michelle.cdnetworks.com> <20090819204603.GL25891@alchemy.franken.de> Message-ID: <20090819210804.GC20481@michelle.cdnetworks.com> On Wed, Aug 19, 2009 at 10:46:03PM +0200, Marius Strobl wrote: > On Wed, Aug 19, 2009 at 10:56:10AM -0700, Pyun YongHyeon wrote: > > On Tue, Aug 18, 2009 at 09:27:48PM +0200, Marius Strobl wrote: > > > On Mon, Aug 17, 2009 at 11:56:12PM +0200, Marius Strobl wrote: > > > > On Mon, Aug 17, 2009 at 10:53:40PM +0200, Marius Strobl wrote: > > > > > On Fri, Aug 07, 2009 at 07:58:40PM +0200, Christian Ramseyer wrote: > > > > > > Hi > > > > > > > > > > > > I'm trying to get sound on a Sunblade 100 with 7.2R. I've added > > > > > > > > > > > > device sound > > > > > > device snd_t4dwave > > > > > > > > > > > > to the kernel and recompiled. pciconf shows an attached driver: > > > > > > > > > > > > pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 > > > > > > rev=0x01 hdr=0x00 > > > > > > vendor = 'Acer Labs Incorporated (ALi/ULi)' > > > > > > device = 'ALI M5451 PCI AC-Link Controller Audio Device' > > > > > > class = multimedia > > > > > > subclass = audio > > > > > > > > > > > > However, there are errors in dmesg: > > > > > > > > > > > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > > > > > > 8.0 on pci0 > > > > > > pcm0: > > > > > > pcm0: [GIANT-LOCKED] > > > > > > pcm0: [ITHREAD] > > > > > > pcm0: chn_init(pcm0:record:dsp0.r0) failed: err = 19 > > > > > > pcm0: pcm_chn_create(trrchan, -1, 0xfffff80001370800) failed > > > > > > pcm0: chn_init(pcm0:play:dsp0.p0) failed: err = 19 > > > > > > pcm0: pcm_chn_create(trpchan, 1, 0xfffff80001370800) failed > > > > > > > > > > > > I've also found this message from 2006: > > > > > > http://lists.freebsd.org/mailman/htdig/freebsd-sparc64/2006-June/004168.html > > > > > > > > > > > > So, am I just doing something wrong or are there problems with 5451 > > > > > > audio on SPARC? I see that the release notes only list i386 and amd64 as > > > > > > architectures for the t4dwave driver. > > > > > > > > > > > > By the way, thanks a lot for all the work your guys are doing in general > > > > > > and for the SPARC port in particular. I'm currently trying BSD for the > > > > > > first time in my life and I like it a lot. It runs surprisingly well on > > > > > > this outdated platform. > > > > > > > > > > > > > > > > Could you (or any other Blade 100 user) please give the following > > > > > patch at try? > > > > > http://people.freebsd.org/~marius/t4dwave_sparc64_32-bit.diff > > > > > This gets at least the line-out of the M5451 in my Blade 1500 > > > > > working (I've no idea whether its internal speaker is also > > > > > connected to the sound chip like for example in a Blade 1000 > > > > > and thus supposed to also work or just to a PC-style beeper, > > > > > the firmware at least makes it beep that way...), but which > > > > > also has a newer revision of this chip. > > > > > > > > > > > > > Looks like I've spoken to soon; it only works when it happens > > > > to get certain buffer addresses, otherwise nothing is played > > > > and the interrupt times out (which according to google isn't > > > > a sparc64 specific problem). This probably means that some > > > > bus_dma(9) parameters are incorrect... > > > > > > > > > > Ok, I think I've identified the incorrect bus_dma(9) settings > > > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > > > the alignment requirement also matches the NetBSD autri(4). A > > > new patch is at: > > > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff > > > > The patch looks good to me but I have two questions. The alignment > > restriction specified in bus_dma_tag_create(9) really works even > > if the alignment is greater than PAGE_SIZE? I vaguely remember > > the alignment was not satisfied last time I tried it on i386 if I > > specified 256K. > > Hrm, from a quick check of the i386 busdma and the sparc64 > busdma and IOMMU code I see no indication why such an > alignment shouldn't work as expected, neither do relevant > man pages like bus_dma(9) and contigmalloc(9) indicate a > restriction to PAGE_SIZE. Based on the addresses of the > buffers I get on sparc64 (f.e. 0xc0000000 and 0xc0020000) > I'd also say it just works. But before possibly commiting > this change I've to also run-time check it on i386 anyway. > Hmm, I also have to check it again. But I guess there was an alignment issue for iwn(4) so the driver had to add a ugly workaround for it. > > The second question is number of channels > > supported for M5451. If I remember correctly there are some > > differences among 4D wave compatible chips and M5451 may have 32 > > channels instead of 64. > > Well, r173511 limited the driver to effectively only use > one channel with M5451 and given that the same change added > a knob I suspect that it was also actually tested with more > than one channel but that also failed. Do you mean that the I know t4dwave(4) uses 1p/1r for M5451, I meant wavetable/digital channel used in the hardware. I think original Trident 4Dwave supports 64 channels but [1] surely indicates it just supports up to 32 channels(32-voices directsound channels). > interation in the interrupt handler should be limited to 32 > (according to the M1535 datasheet [1] that number is correct) Yes, I think tr_intr() shuld not touch more than 32 channels for M5451. > for M5451 or maybe also to the number of channels registered? > > Marius > > [1]: www.nvidia.com/docs/CP/29993/m1535dm_web.pdf > From gahr at gahr.ch Thu Aug 20 09:02:54 2009 From: gahr at gahr.ch (Pietro Cerutti) Date: Thu Aug 20 09:03:01 2009 Subject: Audio on Sunblade 100 In-Reply-To: References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> Message-ID: <20090820082543.GM30947@gahrfit.gahr.ch> On 2009-Aug-19, 14:30, Gheorghe Ardelean wrote: [snip] > Attached please find the dmesg! Could somebody add the dmesg to my list of > dmesgs on the wiki page? Done, thanks! > Best regards, > > Gheorghe Ardelean. -- Pietro Cerutti The FreeBSD Project gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20090820/77bfd13a/attachment.pgp From rc at networkz.ch Thu Aug 20 21:32:21 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Thu Aug 20 21:32:28 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090819161410.GA19351@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> Message-ID: <4A8DC0DF.4040701@networkz.ch> Marius Strobl wrote: >> Ok, I think I've identified the incorrect bus_dma(9) settings >> with the help of Tatsuo YOKOGAWA's ali(4) (which as least for >> the alignment requirement also matches the NetBSD autri(4). A >> new patch is at: >> http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff Hi Thanks for the patch, I've applied it and the driver seems to load properly: pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] Unfortunately, the actual "playing sound part" is not going too well. When I do e.g. : rc@ds9000:~ $ mpg321 03\ Wonderful\ Night\ \(feat\ Lateef\).mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. ... Playing MPEG stream from 03 Wonderful Night (feat Lateef).mp3 ... MPEG 1.0 layer III, 192 kbit/s, 44100 Hz stereo I sometimes get some seconds of sound, but most of the time only silence or a short burst of static, and then pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead appears on the console. I tried to evade some layers of complexity by trying: rc@ds9000:~ $ sox 10-the_white_stripes-take_take_take.mp3 10-the_white_stripes-take_take_take.raw rc@ds9000:~ $ cat 10-the_white_stripes-take_take_take.raw > /dev/dsp0.0 cat: stdout: Invalid argument This didn't output anything audible, though I'm not even sure if it should work. As it worked for Gheorghe, chances are that I'm doing something wrong/different: - the driver is built directly into the kernel, I'm using sparc64/conf/GENERIC with minimal modifications: [root@ds9000 /usr/src/sys/sparc64/conf]# diff GENERIC SNOOSNOO 24c24 < ident GENERIC --- > ident SNOOSNOO 242a243,245 > > device sound > device snd_t4dwave - kernel built like this: 102 make buildkernel KERNCONF=SNOOSNOO 103 make installkernel KERNCONF=SNOOSNOO Thanks for your time & best regards Christian From pyunyh at gmail.com Thu Aug 20 21:50:19 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Thu Aug 20 21:50:25 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A8DC0DF.4040701@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> Message-ID: <20090820214938.GC1262@michelle.cdnetworks.com> On Thu, Aug 20, 2009 at 11:32:15PM +0200, Christian Ramseyer wrote: > Marius Strobl wrote: > >> Ok, I think I've identified the incorrect bus_dma(9) settings > >> with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > >> the alignment requirement also matches the NetBSD autri(4). A > >> new patch is at: > >> http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff > > Hi > > Thanks for the patch, I've applied it and the driver seems to load properly: > > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device > 8.0 on pci0 > pcm0: > pcm0: [GIANT-LOCKED] > pcm0: [ITHREAD] > > Unfortunately, the actual "playing sound part" is not going too well. > When I do e.g. : > > rc@ds9000:~ $ mpg321 03\ Wonderful\ Night\ \(feat\ Lateef\).mp3 > High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. > ... > Playing MPEG stream from 03 Wonderful Night (feat Lateef).mp3 ... > MPEG 1.0 layer III, 192 kbit/s, 44100 Hz stereo > > I sometimes get some seconds of sound, but most of the time only silence > or a short burst of static, and then > > pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead > > appears on the console. > How about disabling vchans in /boot/loader.conf? (dev.pcm.0.play.vchans="0") From rc at networkz.ch Thu Aug 20 22:13:56 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Thu Aug 20 22:14:03 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090820214938.GC1262@michelle.cdnetworks.com> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <20090820214938.GC1262@michelle.cdnetworks.com> Message-ID: <4A8DCA9F.80902@networkz.ch> >> >> Unfortunately, the actual "playing sound part" is not going too well. >> When I do e.g. : >> >> rc@ds9000:~ $ mpg321 03\ Wonderful\ Night\ \(feat\ Lateef\).mp3 >> High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. >> >> I sometimes get some seconds of sound, but most of the time only silence >> or a short burst of static, and then >> >> pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead >> >> appears on the console. >> > > How about disabling vchans in /boot/loader.conf? > (dev.pcm.0.play.vchans="0") Setting this in /boot/loader.conf didn't seem to have any effect: [root@ds9000 ~]# cat /boot/loader.conf dev.pcm.0.play.vchans="0" (reboot) [root@ds9000 ~]# sysctl dev.pcm.0.play dev.pcm.0.play.vchans: 1 However, I was able to set it via sysctl (is this the same?): [root@ds9000 ~]# sysctl dev.pcm.0.play.vchans="0" dev.pcm.0.play.vchans: 1 -> 0 There isn't any sound either, but the logged message changes: pcm0:play:dsp0.p0: play interrupt timeout, channel dead Thanks Christian From pyunyh at gmail.com Thu Aug 20 22:31:14 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Thu Aug 20 22:31:20 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A8DCA9F.80902@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <20090820214938.GC1262@michelle.cdnetworks.com> <4A8DCA9F.80902@networkz.ch> Message-ID: <20090820223034.GD1262@michelle.cdnetworks.com> On Fri, Aug 21, 2009 at 12:13:51AM +0200, Christian Ramseyer wrote: > > >> > >> Unfortunately, the actual "playing sound part" is not going too well. > >> When I do e.g. : > >> > >> rc@ds9000:~ $ mpg321 03\ Wonderful\ Night\ \(feat\ Lateef\).mp3 > >> High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. > >> > >> I sometimes get some seconds of sound, but most of the time only silence > >> or a short burst of static, and then > >> > >> pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead > >> > >> appears on the console. > >> > > > > How about disabling vchans in /boot/loader.conf? > > (dev.pcm.0.play.vchans="0") > > Setting this in /boot/loader.conf didn't seem to have any effect: > > [root@ds9000 ~]# cat /boot/loader.conf > dev.pcm.0.play.vchans="0" > > (reboot) > > [root@ds9000 ~]# sysctl dev.pcm.0.play > dev.pcm.0.play.vchans: 1 > > However, I was able to set it via sysctl (is this the same?): > > [root@ds9000 ~]# sysctl dev.pcm.0.play.vchans="0" > dev.pcm.0.play.vchans: 1 -> 0 > > There isn't any sound either, but the logged message changes: > > pcm0:play:dsp0.p0: play interrupt timeout, channel dead > Hmm, I think this rules out vchans, so let's see marious' opinion. From ardelean at ww.uni-erlangen.de Fri Aug 21 08:45:23 2009 From: ardelean at ww.uni-erlangen.de (Gheorghe Ardelean) Date: Fri Aug 21 08:45:29 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A8DC0DF.4040701@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> Message-ID: On Thu, 20 Aug 2009, Christian Ramseyer wrote: [...] > As it worked for Gheorghe, chances are that I'm doing something > wrong/different: Now I have tested also mpg321 and it has a not that good sound quality. A lot of noise is coming out but the sound is there all the time. The noise is coming always on the bass (maybe drums?) parts. blade100# mpg321 Baltimora\ -\ Tarzan\ Boy.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.59q (2002/03/23). Written and copyrights by Joe Drew. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Playing MPEG stream from Baltimora - Tarzan Boy.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 48000 Hz joint-stereo mpg123 is still ok: blade100# mpg123 Baltimora\ -\ Tarzan\ Boy.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3 version 1.6.4; written and copyright by Michael Hipp and others free software (LGPL/GPL) without any warranty but with best wishes Playing MPEG stream 1 of 1: Baltimora - Tarzan Boy.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 48000 Hz joint-stereo So this is some kind of strange to me. I have tested also xmms with the result of only noise comming out. And x11amp dies when loading. So up to now the only viable solution is mpg123 (at least for me). All I can see is mpgs321 is using different libraries from mpg123: blade100# ldd /usr/local/bin/mpg123 /usr/local/bin/mpg123: libltdl.so.4 => /usr/local/lib/libltdl.so.4 (0x4035a000) libmpg123.so.11 => /usr/local/lib/libmpg123.so.11 (0x40464000) libm.so.5 => /lib/libm.so.5 (0x405aa000) libc.so.7 => /lib/libc.so.7 (0x406d4000) blade100# ldd /usr/local/bin/mpg321 /usr/local/bin/mpg321: libid3tag.so.0 => /usr/local/lib/libid3tag.so.0 (0x40346000) libmad.so.2 => /usr/local/lib/libmad.so.2 (0x40466000) libz.so.4 => /lib/libz.so.4 (0x40588000) libao.so.3 => /usr/local/lib/libao.so.3 (0x4069e000) libc.so.7 => /lib/libc.so.7 (0x407a4000) libthr.so.3 => /lib/libthr.so.3 (0x409e2000) Christian, could please also test mpg123 and let us know if you get different results? > - the driver is built directly into the kernel, I'm using > sparc64/conf/GENERIC with minimal modifications: I included the driver also in the kernel. blade100# diff -u GENERIC GENERIC.orig --- GENERIC 2009-08-19 12:51:27.000000000 +0200 +++ GENERIC.orig 2009-08-21 10:26:47.000000000 +0200 @@ -241,6 +241,3 @@ device dcons # Dumb console driver device dcons_crom # Configuration ROM for dcons -device sound -device snd_t4dwave - in /etc/make.conf I have this line: MODULES_OVERRIDE= ipfw and the kernel was build this way: cd /usr/src/sys/sparc64/conf config GENERIC (I modifed the GENERIC file) cd ../compile/GENERIC make cleandepend && make depend make make install reboot Regards, Gheorghe Ardelean. From rc at networkz.ch Fri Aug 21 17:50:47 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Fri Aug 21 17:50:54 2009 Subject: Audio on Sunblade 100 In-Reply-To: References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> Message-ID: <4A8EDE72.6040703@networkz.ch> Gheorghe Ardelean wrote: > > On Thu, 20 Aug 2009, Christian Ramseyer wrote: > > [...] >> As it worked for Gheorghe, chances are that I'm doing something >> wrong/different: > > Now I have tested also mpg321 and it has a not that good sound quality. > A lot of noise is coming out but the sound is there all the time. The > noise is coming always on the bass (maybe drums?) parts. > > Christian, could please also test mpg123 and let us know if you get > different results? > I've got maybe 10 seconds of sound, then silence and these messages: [audio.c:596] error: Error in writing audio (Invalid argument?)! [mpg123.c:577] error: Deep trouble! Cannot flush to my output anymore! There was the "usual" message: pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead Also, I have the impressions that the rare events where I get some seconds of sound only occur when the box was powered down for some time before, subsequent attempts (also after reboot without power cycle) never seem to produce sound. > So this is some kind of strange to me. I have tested also xmms with > the result of only noise comming out. I tried xmms with similar results: one short burst of noise/static, then silence. Plus some complaining about ioctls: ** WARNING **: SNDCTL_DSP_SETFMT ioctl failed: Invalid argument ** WARNING **: SNDCTL_DSP_SPEED ioctl failed: Invalid argument Cheers, Christian From marius at alchemy.franken.de Fri Aug 21 19:37:42 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Fri Aug 21 19:37:49 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A8EDE72.6040703@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> Message-ID: <20090821193740.GA66639@alchemy.franken.de> On Fri, Aug 21, 2009 at 07:50:42PM +0200, Christian Ramseyer wrote: > Gheorghe Ardelean wrote: > > > > On Thu, 20 Aug 2009, Christian Ramseyer wrote: > > > > [...] > >> As it worked for Gheorghe, chances are that I'm doing something > >> wrong/different: > > > > Now I have tested also mpg321 and it has a not that good sound quality. > > A lot of noise is coming out but the sound is there all the time. The > > noise is coming always on the bass (maybe drums?) parts. > > > > Christian, could please also test mpg123 and let us know if you get > > different results? > > > > I've got maybe 10 seconds of sound, then silence and these messages: > > [audio.c:596] error: Error in writing audio (Invalid argument?)! > [mpg123.c:577] error: Deep trouble! Cannot flush to my output anymore! > > There was the "usual" message: > pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead > > Also, I have the impressions that the rare events where I get some > seconds of sound only occur when the box was powered down for some time > before, subsequent attempts (also after reboot without power cycle) > never seem to produce sound. This symptom is similar to when using non-working DMA tag parameters, except that I get no sound at all then but possibly a non-correctable DMA error panic. This also might occur due to other kinds of bugs in the driver, but without deeper insight in the sound subsystem and no programming manual for the M5451 this is kind of unfun... Given that the driver works for Gheorghe with the same hardware model I suspect an initialization issue based on different firmware revsions. Could both of you please run `pciconf -lv` and report the two lines starting with isab0 and pcm0 (just these two lines, not the whole output from that command). Then get a complete dump of the PCI configuration header by running `pciconf -rb 0:255` on the selectors contained in the isab0 and pcm0 strings, for example: `pciconf -rb isab0@pci0:1:7:0 0:255` Please also report the pcm0 parts of a verbose boot (stop the boot count-down by pressing space and issue a `set boot_verbose`, followed by `boot`, then get the pcm0 lines from for example the dmesg-output). Yongari, given that you've worked on sound drivers and snd_t4dwave(4) in particular before, can you spot something obviously wrong with the DMA programming this driver does, for example in the CSO and ESO parts? > > > So this is some kind of strange to me. I have tested also xmms with > > the result of only noise comming out. > > I tried xmms with similar results: one short burst of noise/static, then > silence. Plus some complaining about ioctls: > > ** WARNING **: SNDCTL_DSP_SETFMT ioctl failed: Invalid argument > ** WARNING **: SNDCTL_DSP_SPEED ioctl failed: Invalid argument > >From the symptoms Gheorghe reported for mpg321 I suspect it has some LP64 and/or endian bugs, while mpg123 hasn't. IIRC Yongari once also had a fix for such a bug in XMMS, which isn't necessarily the cause for the above problem though. Marius From rc at networkz.ch Fri Aug 21 23:03:58 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Fri Aug 21 23:04:04 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090821193740.GA66639@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> Message-ID: <4A8F27D7.20503@networkz.ch> Marius Strobl wrote: > but without deeper insight in the sound subsystem and > no programming manual for the M5451 this is kind of > unfun... Let me say that I really appreciate your effort, but it's not really an issue of life and dead for me so I'd also accept if you let it go and moved on :) > Given that the driver works for Gheorghe with the same > hardware model I suspect an initialization issue based > on different firmware revsions. Could both of you please > run `pciconf -lv` and report the two lines starting > with isab0 and pcm0 (just these two lines, not the > whole output from that command). isab0@pci0:0:7:0: class=0x060100 card=0x153310b9 chip=0x153310b9 rev=0x00 hdr=0x00 pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 rev=0x01 hdr=0x00 > Then get a complete > dump of the PCI configuration header by running > `pciconf -rb 0:255` on the selectors > contained in the isab0 and pcm0 strings, for example: > `pciconf -rb isab0@pci0:1:7:0 0:255` [root@ds9000 ~]# pciconf -rb isab0@pci0:0:7:0 0:255 b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 33 15 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 11 13 49 80 83 09 00 07 00 00 00 10 00 00 fd 01 00 00 00 40 00 07 02 00 6e 03 09 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 00 00 06 00 41 03 00 d3 04 02 00 02 00 00 01 10 07 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [root@ds9000 ~]# pciconf -rb pcm0@pci0:0:8:0 0:255 b9 10 51 54 07 00 90 02 01 00 01 04 00 10 00 00 01 09 00 00 00 40 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 51 54 00 00 00 00 dc 00 00 00 00 00 00 00 23 01 02 18 00 00 00 00 00 04 00 e2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > Please also report the pcm0 parts of a verbose boot > (stop the boot count-down by pressing space and > issue a `set boot_verbose`, followed by `boot`, then > get the pcm0 lines from for example the dmesg-output). > pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x900 pcm0: pcm0: Codec features headphone, 6 bit master volume, Analog Devices Phat Stereo pcm0: Primary codec extended features variable rate PCM pcm0: ac97 codec dac ready count: 0 pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "cd": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "line1": pcm0: Mixer "phin": pcm0: Mixer "phout": pcm0: Mixer "video": pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] pcm0: M1533 0x7e: 0x1 -> 0x1 pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: sndbuf_setmap c1140000, 10000; 0xc0c50000 -> c1140000 pcm0: sndbuf_setmap c1160000, 10000; 0xc0c70000 -> c1160000 If you'd like, I could also setup SSH access for you. Christian From ardelean at ww.uni-erlangen.de Sat Aug 22 13:08:37 2009 From: ardelean at ww.uni-erlangen.de (Gheorghe Ardelean) Date: Sat Aug 22 13:08:59 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090821193740.GA66639@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> Message-ID: On Fri, 21 Aug 2009, Marius Strobl wrote: > On Fri, Aug 21, 2009 at 07:50:42PM +0200, Christian Ramseyer wrote: >> Gheorghe Ardelean wrote: >>> >>> On Thu, 20 Aug 2009, Christian Ramseyer wrote: >>> >>> [...] >>>> As it worked for Gheorghe, chances are that I'm doing something >>>> wrong/different: >>> >>> Now I have tested also mpg321 and it has a not that good sound quality. >>> A lot of noise is coming out but the sound is there all the time. The >>> noise is coming always on the bass (maybe drums?) parts. >>> >>> Christian, could please also test mpg123 and let us know if you get >>> different results? >>> >> >> I've got maybe 10 seconds of sound, then silence and these messages: >> >> [audio.c:596] error: Error in writing audio (Invalid argument?)! >> [mpg123.c:577] error: Deep trouble! Cannot flush to my output anymore! >> >> There was the "usual" message: >> pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead >> >> Also, I have the impressions that the rare events where I get some >> seconds of sound only occur when the box was powered down for some time >> before, subsequent attempts (also after reboot without power cycle) >> never seem to produce sound. > > Given that the driver works for Gheorghe with the same > hardware model I suspect an initialization issue based > on different firmware revsions. Could both of you please > run `pciconf -lv` and report the two lines starting > with isab0 and pcm0 (just these two lines, not the > whole output from that command). isab0@pci0:0:7:0: class=0x060100 card=0x153310b9 chip=0x153310b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M1533 Aladdin IV ISA Bridge' class = bridge subclass = PCI-ISA pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 rev=0x01 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M5451 PCI AC-Link Controller Audio Device' class = multimedia subclass = audio > Then get a complete > dump of the PCI configuration header by running > `pciconf -rb 0:255` on the selectors > contained in the isab0 and pcm0 strings, for example: > `pciconf -rb isab0@pci0:1:7:0 0:255` blade100# pciconf -rb isab0@pci0:0:7:0 0:255 b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 33 15 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 11 13 49 80 83 09 00 07 00 00 00 10 00 00 fd 01 00 00 00 40 00 07 02 00 6e 03 09 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 00 00 06 00 41 03 00 d3 04 02 00 04 00 00 01 10 07 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 blade100# pciconf -rb pcm0@pci0:0:8:0 0:255 b9 10 51 54 07 00 90 02 01 00 01 04 00 10 00 00 01 09 00 00 00 40 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 51 54 00 00 00 00 dc 00 00 00 00 00 00 00 23 01 02 18 00 00 00 00 00 04 00 e2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > Please also report the pcm0 parts of a verbose boot > (stop the boot count-down by pressing space and > issue a `set boot_verbose`, followed by `boot`, then > get the pcm0 lines from for example the dmesg-output). blade100# dmesg | grep ^pcm pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x900 pcm0: pcm0: Codec features headphone, 6 bit master volume, Analog Devices Phat Stereo pcm0: Primary codec extended features variable rate PCM pcm0: ac97 codec dac ready count: 0 pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "cd": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "line1": pcm0: Mixer "phin": pcm0: Mixer "phout": pcm0: Mixer "video": pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] pcm0: M1533 0x7e: 0x1 -> 0x1 pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: sndbuf_setmap c1140000, 10000; 0xc0c62000 -> c1140000 pcm0: sndbuf_setmap c1160000, 10000; 0xc0c82000 -> c1160000 >> From the symptoms Gheorghe reported for mpg321 I suspect > it has some LP64 and/or endian bugs, while mpg123 hasn't. > IIRC Yongari once also had a fix for such a bug in XMMS, > which isn't necessarily the cause for the above problem > though. I have also a second blade 100. I wil test on monday on it (it's at work). Regards, Gheorghe Ardelean From pyunyh at gmail.com Sun Aug 23 22:26:45 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sun Aug 23 22:26:53 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090819204603.GL25891@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819175610.GA20481@michelle.cdnetworks.com> <20090819204603.GL25891@alchemy.franken.de> Message-ID: <20090823222606.GA1185@michelle.cdnetworks.com> On Wed, Aug 19, 2009 at 10:46:03PM +0200, Marius Strobl wrote: [...] > > > Ok, I think I've identified the incorrect bus_dma(9) settings > > > with the help of Tatsuo YOKOGAWA's ali(4) (which as least for > > > the alignment requirement also matches the NetBSD autri(4). A > > > new patch is at: > > > http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff > > > > The patch looks good to me but I have two questions. The alignment > > restriction specified in bus_dma_tag_create(9) really works even > > if the alignment is greater than PAGE_SIZE? I vaguely remember > > the alignment was not satisfied last time I tried it on i386 if I > > specified 256K. > > Hrm, from a quick check of the i386 busdma and the sparc64 > busdma and IOMMU code I see no indication why such an > alignment shouldn't work as expected, neither do relevant > man pages like bus_dma(9) and contigmalloc(9) indicate a > restriction to PAGE_SIZE. Based on the addresses of the > buffers I get on sparc64 (f.e. 0xc0000000 and 0xc0020000) > I'd also say it just works. But before possibly commiting > this change I've to also run-time check it on i386 anyway. > I tried it on amd64 CURRENT and it still fails to align if I set 16K as alignment. So I guess i386 may also have the same issue. As you said I also wonder why contigmalloc(9) does not honor the alignment. From pyunyh at gmail.com Sun Aug 23 22:48:06 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sun Aug 23 22:48:12 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090821193740.GA66639@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> Message-ID: <20090823224727.GB1185@michelle.cdnetworks.com> On Fri, Aug 21, 2009 at 09:37:40PM +0200, Marius Strobl wrote: > On Fri, Aug 21, 2009 at 07:50:42PM +0200, Christian Ramseyer wrote: > > Gheorghe Ardelean wrote: > > > > > > On Thu, 20 Aug 2009, Christian Ramseyer wrote: > > > > > > [...] > > >> As it worked for Gheorghe, chances are that I'm doing something > > >> wrong/different: > > > > > > Now I have tested also mpg321 and it has a not that good sound quality. > > > A lot of noise is coming out but the sound is there all the time. The > > > noise is coming always on the bass (maybe drums?) parts. > > > > > > Christian, could please also test mpg123 and let us know if you get > > > different results? > > > > > > > I've got maybe 10 seconds of sound, then silence and these messages: > > > > [audio.c:596] error: Error in writing audio (Invalid argument?)! > > [mpg123.c:577] error: Deep trouble! Cannot flush to my output anymore! > > > > There was the "usual" message: > > pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead > > > > Also, I have the impressions that the rare events where I get some > > seconds of sound only occur when the box was powered down for some time > > before, subsequent attempts (also after reboot without power cycle) > > never seem to produce sound. > > This symptom is similar to when using non-working DMA tag > parameters, except that I get no sound at all then but > possibly a non-correctable DMA error panic. This also > might occur due to other kinds of bugs in the driver, > but without deeper insight in the sound subsystem and > no programming manual for the M5451 this is kind of > unfun... > Given that the driver works for Gheorghe with the same > hardware model I suspect an initialization issue based > on different firmware revsions. Could both of you please > run `pciconf -lv` and report the two lines starting > with isab0 and pcm0 (just these two lines, not the > whole output from that command). Then get a complete > dump of the PCI configuration header by running > `pciconf -rb 0:255` on the selectors > contained in the isab0 and pcm0 strings, for example: > `pciconf -rb isab0@pci0:1:7:0 0:255` > Please also report the pcm0 parts of a verbose boot > (stop the boot count-down by pressing space and > issue a `set boot_verbose`, followed by `boot`, then > get the pcm0 lines from for example the dmesg-output). > > Yongari, given that you've worked on sound drivers > and snd_t4dwave(4) in particular before, can you spot > something obviously wrong with the DMA programming > this driver does, for example in the CSO and ESO parts? > Sorry, I can't remember details. I have to reread 4DWave datasheet. 4DWave was one of the best audio controller in its sound quality and wavetable support. FreeBSD's 4DWave support was very minimal(e.g. no wavetable support, using sound blaster mode for recording etc) so I wanted to implement missing features in the past but had no time to try it. As time goes, ariff also changed/enhanced a lot of sound framework so my understanding to sound subsystem is now very limited and I guess I need more time to understand sound subsystem by reading every code of the subsystem. Anyway, I'll see what I can do if time permit. > > > > > So this is some kind of strange to me. I have tested also xmms with > > > the result of only noise comming out. > > > > I tried xmms with similar results: one short burst of noise/static, then > > silence. Plus some complaining about ioctls: > > > > ** WARNING **: SNDCTL_DSP_SETFMT ioctl failed: Invalid argument > > ** WARNING **: SNDCTL_DSP_SPEED ioctl failed: Invalid argument > > > > >From the symptoms Gheorghe reported for mpg321 I suspect > it has some LP64 and/or endian bugs, while mpg123 hasn't. > IIRC Yongari once also had a fix for such a bug in XMMS, > which isn't necessarily the cause for the above problem > though. > > Marius > From ardelean at ww.uni-erlangen.de Mon Aug 24 10:07:48 2009 From: ardelean at ww.uni-erlangen.de (Gheorghe Ardelean) Date: Mon Aug 24 10:07:55 2009 Subject: Audio on Sunblade 100 In-Reply-To: References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> Message-ID: On Sat, 22 Aug 2009, Gheorghe Ardelean wrote: > On Fri, 21 Aug 2009, Marius Strobl wrote: > >> On Fri, Aug 21, 2009 at 07:50:42PM +0200, Christian Ramseyer wrote: >>> Gheorghe Ardelean wrote: >>>> >>>> On Thu, 20 Aug 2009, Christian Ramseyer wrote: >>>> >>>> [...] >>>>> As it worked for Gheorghe, chances are that I'm doing something >>>>> wrong/different: >>>> [...] >>> From the symptoms Gheorghe reported for mpg321 I suspect >> it has some LP64 and/or endian bugs, while mpg123 hasn't. >> IIRC Yongari once also had a fix for such a bug in XMMS, >> which isn't necessarily the cause for the above problem >> though. > > I have also a second blade 100. I wil test on monday on it (it's at work). I have installed also the second computer. Everything works ok. The sound quality problem that I observed with mpg321 is depending also on the files that are played. Here is the output, also for this computer, of the commands Marius sugested: blade100-2# uname -a FreeBSD blade100-2.ganet 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Wed Aug 19 14:14:19 CEST 2009 root@blade100.iisb.fraunhofer.de:/usr/src/sys/sparc64/compile/GENERIC sparc64 I use the same kernel compiled on the first machine! blade100-2# pciconf -lv isab0@pci0:0:7:0: class=0x060100 card=0x153310b9 chip=0x153310b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M1533 Aladdin IV ISA Bridge' class = bridge subclass = PCI-ISA pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 rev=0x01 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M5451 PCI AC-Link Controller Audio Device' class = multimedia subclass = audio blade100-2# pciconf -rb isab0@pci0:0:7:0 0:255 b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 33 15 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 11 13 49 80 83 09 00 07 00 00 00 10 00 00 fd 01 00 00 00 40 00 07 02 00 6e 03 09 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 00 00 06 00 41 03 00 d3 04 02 00 04 00 00 01 10 07 00 33 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 blade100-2# pciconf -rb pcm0@pci0:0:8:0 0:255 b9 10 51 54 07 00 90 02 01 00 01 04 00 10 00 00 01 09 00 00 00 40 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 51 54 00 00 00 00 dc 00 00 00 00 00 00 00 23 01 02 18 00 00 00 00 00 04 00 e2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >From all this dumps all I can see is that on my Blade100s there are some bytes in the isab0@pci... dumps which are different from what the Christian has: ardelean@ahorn:~> diff -u pciconf-myconfig1.txt pciconf-christian.txt --- pciconf-myconfig1.txt 2009-08-24 11:24:52.758524000 +0200 +++ pciconf-christian.txt 2009-08-24 11:25:30.791166000 +0200 -00 00 06 00 41 03 00 d3 04 02 00 04 00 00 01 10 +00 00 06 00 41 03 00 d3 04 02 00 02 00 00 01 10 and the boot verbose part: -pcm0: sndbuf_setmap c1140000, 10000; 0xc0c62000 -> c1140000 -pcm0: sndbuf_setmap c1160000, 10000; 0xc0c82000 -> c1160000 +pcm0: sndbuf_setmap c1140000, 10000; 0xc0c50000 -> c1140000 +pcm0: sndbuf_setmap c1160000, 10000; 0xc0c70000 -> c1160000 Now same diff for the two Blades I have: ardelean@ahorn:~> diff -u pciconf-myconfig1.txt pciconf-myconfig2.txt --- pciconf-myconfig1.txt 2009-08-24 11:40:49.803728000 +0200 +++ pciconf-myconfig2.txt 2009-08-24 11:39:20.510277000 +0200 @@ -1,5 +1,5 @@ -blade100# pciconf -lv +blade100-2# pciconf -lv isab0@pci0:0:7:0: class=0x060100 card=0x153310b9 chip=0x153310b9 rev=0x00 hdr=0x00 @@ -15,7 +15,7 @@ class = multimedia subclass = audio -blade100# pciconf -rb isab0@pci0:0:7:0 0:255 +blade100-2# pciconf -rb isab0@pci0:0:7:0 0:255 b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 33 15 @@ -24,7 +24,7 @@ 00 00 00 40 00 07 02 00 6e 03 09 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 00 00 06 00 41 03 00 d3 04 02 00 04 00 00 01 10 -07 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 +07 00 33 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 @@ -33,7 +33,7 @@ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -blade100# pciconf -rb pcm0@pci0:0:8:0 0:255 +blade100-2# pciconf -rb pcm0@pci0:0:8:0 0:255 b9 10 51 54 07 00 90 02 01 00 01 04 00 10 00 00 01 09 00 00 00 40 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 51 54 @@ -51,7 +51,7 @@ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -blade100# dmesg | grep ^pcm +blade100-2# dmesg |grep ^pcm pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x900 @@ -76,5 +76,5 @@ pcm0: [ITHREAD] pcm0: M1533 0x7e: 0x1 -> 0x1 pcm0: clone manager: deadline=750ms flags=0x8000001e -pcm0: sndbuf_setmap c1140000, 10000; 0xc0c62000 -> c1140000 -pcm0: sndbuf_setmap c1160000, 10000; 0xc0c82000 -> c1160000 +pcm0: sndbuf_setmap c1140000, 10000; 0xc0c56000 -> c1140000 +pcm0: sndbuf_setmap c1160000, 10000; 0xc0c76000 -> c1160000 So one can see that there are differences in the output of isab0@pci dump and also in the dmesg. In the case of Christian this diference is at bye offset 0x79 (one byte). In my case the difference is at byteoffset 0x82 (two bytes). I don't know what is the meaning of this bytes but maybe someone could tell us. The 1st Blade100 that I have has: UltraSPARC-IIe 500MHz, OpenBoot 4.2, 512MB RAM The 2nd one has: UltraSPARC-IIe 500MHz, OpenBoot 4.2, 256MB RAM Christian, are you running the same version of OpenBoot? Nevertheless thank you Marius! It's working (at least for me :) Best regards, Gheorghe Ardelean. From bugmaster at FreeBSD.org Mon Aug 24 11:07:04 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 24 11:09:29 2009 Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org Message-ID: <200908241107.n7OB73Tl048733@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/113556 sparc64 [panic] trap: memory address not aligned; Rebooting... f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 [hang] system is hung during boot from CD o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 12 problems total. From rc at networkz.ch Mon Aug 24 18:32:20 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Mon Aug 24 18:32:27 2009 Subject: Audio on Sunblade 100 In-Reply-To: References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> Message-ID: <4A92DCAD.6040908@networkz.ch> Gheorghe Ardelean wrote: > The 1st Blade100 that I have has: > > UltraSPARC-IIe 500MHz, OpenBoot 4.2, 512MB RAM > > The 2nd one has: > > UltraSPARC-IIe 500MHz, OpenBoot 4.2, 256MB RAM > > Christian, are you running the same version of OpenBoot? > Mine has 4.17.1 and only 128 MB of RAM. If you guys think it would help, I could try to update it, but if I'm not mistaken, that would require me to first install Solaris on it, right? Christian From ardelean at ww.uni-erlangen.de Mon Aug 24 22:12:01 2009 From: ardelean at ww.uni-erlangen.de (Gheorghe Ardelean) Date: Mon Aug 24 22:13:47 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A92DCAD.6040908@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> <4A92DCAD.6040908@networkz.ch> Message-ID: On Mon, 24 Aug 2009, Christian Ramseyer wrote: > Gheorghe Ardelean wrote: >> The 1st Blade100 that I have has: >> >> UltraSPARC-IIe 500MHz, OpenBoot 4.2, 512MB RAM >> >> The 2nd one has: >> >> UltraSPARC-IIe 500MHz, OpenBoot 4.2, 256MB RAM >> >> Christian, are you running the same version of OpenBoot? >> > > Mine has 4.17.1 and only 128 MB of RAM. If you guys think it would help, > I could try to update it, but if I'm not mistaken, that would require me > to first install Solaris on it, right? Is this not newer than mine? I think 4.17 is the latest ( I have 4.2 ) Concerning the way to do the updates, I did all my updates by netbooting the update installer. I did this for Ultra 1, 1E, 5, 10 and 30. IIRC just setup a RARP and TFTP server, and serve the flash rom updater over TFTP. The file name should be the IP address of the client in HEX written with capital letter (tcpdump is your friend here analyzing the requests) and maybe at the end you should add the architectural class (sun4u). Do not forget to set the jumpers on the motherboard also. :) Good documentation about this setup could be found here: http://www.netbsd.org/docs/network/netboot/intro.sun.ofw.html The other way round is to use the Solaris CD/DVD. Best regards, Gheorghe Ardelean From rc at networkz.ch Tue Aug 25 11:14:02 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Tue Aug 25 11:14:09 2009 Subject: Audio on Sunblade 100 In-Reply-To: References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> <4A92DCAD.6040908@networkz.ch> Message-ID: <4A93C774.9010601@networkz.ch> Gheorghe Ardelean wrote: >> >> Mine has 4.17.1 and only 128 MB of RAM. If you guys think it would help, >> I could try to update it, but if I'm not mistaken, that would require me >> to first install Solaris on it, right? > > Is this not newer than mine? I think 4.17 is the latest ( I have 4.2 ) > Concerning the way to do the updates, I did all my updates by netbooting > the update installer. I did this for Ultra 1, 1E, 5, 10 and 30. > Ah yes, netbooting would be an option. However, it seems like I actually haved the latest release: http://sunsolve.sun.com/search/document.do?assetkey=1-21-119235-01-1 Status: RELEASED Patch Id: 119235-01 Summary: Hardware/PROM: Sun Blade 100/150 Flash PROM Update Date: Apr/29/2005 Unbundled Release: OBP 4.17.1,OBDIAG 4.17.1,POST_2.0.1 Christian From ardelean at ww.uni-erlangen.de Tue Aug 25 17:00:25 2009 From: ardelean at ww.uni-erlangen.de (Gheorghe Ardelean) Date: Tue Aug 25 17:00:58 2009 Subject: Audio on Sunblade 100 In-Reply-To: <4A93C774.9010601@networkz.ch> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> <4A92DCAD.6040908@networkz.ch> <4A93C774.9010601@networkz.ch> Message-ID: On Tue, 25 Aug 2009, Christian Ramseyer wrote: > Gheorghe Ardelean wrote: >>> >>> Mine has 4.17.1 and only 128 MB of RAM. If you guys think it would help, >>> I could try to update it, but if I'm not mistaken, that would require me >>> to first install Solaris on it, right? >> >> Is this not newer than mine? I think 4.17 is the latest ( I have 4.2 ) >> Concerning the way to do the updates, I did all my updates by netbooting >> the update installer. I did this for Ultra 1, 1E, 5, 10 and 30. >> > > Ah yes, netbooting would be an option. However, it seems like I actually > haved the latest release: > > http://sunsolve.sun.com/search/document.do?assetkey=1-21-119235-01-1 > > Status: RELEASED > Patch Id: 119235-01 > Summary: Hardware/PROM: Sun Blade 100/150 Flash PROM Update > Date: Apr/29/2005 > Unbundled Release: OBP 4.17.1,OBDIAG 4.17.1,POST_2.0.1 I did the same update. Now I have the same version as yours and the sound is still working! Nice! :) Here are the new dumps: isab0@pci0:0:7:0: class=0x060100 card=0x153310b9 chip=0x153310b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M1533 Aladdin IV ISA Bridge' class = bridge subclass = PCI-ISA pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9 rev=0x01 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi/ULi)' device = 'ALI M5451 PCI AC-Link Controller Audio Device' class = multimedia subclass = audio blade100-2# pciconf -rb isab0@pci0:0:7:0 0:255 b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 33 15 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 11 13 49 80 83 09 00 07 00 00 00 10 00 00 fd 01 00 00 00 40 00 07 02 00 6e 03 09 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 00 00 06 00 41 03 00 d3 04 02 00 02 00 00 01 10 07 00 33 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 blade100-2# pciconf -rb pcm0@pci0:0:8:0 0:255 b9 10 51 54 07 00 90 02 01 00 01 04 00 10 00 00 01 09 00 00 00 40 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b9 10 51 54 00 00 00 00 dc 00 00 00 00 00 00 00 23 01 02 18 00 00 00 00 00 04 00 e2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 blade100-2# dmesg |grep ^pcm pcm0: port 0x900-0x9ff mem 0x424000-0x424fff at device 8.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x900 pcm0: pcm0: Codec features headphone, 6 bit master volume, Analog Devices Phat Stereo pcm0: Primary codec extended features variable rate PCM pcm0: ac97 codec dac ready count: 0 pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "cd": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "line1": pcm0: Mixer "phin": pcm0: Mixer "phout": pcm0: Mixer "video": pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] pcm0: M1533 0x7e: 0x1 -> 0x1 pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: sndbuf_setmap c1140000, 10000; 0xc0c56000 -> c1140000 pcm0: sndbuf_setmap c1160000, 10000; 0xc0c76000 -> c1160000 Regards, Gheorghe From marius at alchemy.franken.de Wed Aug 26 20:59:07 2009 From: marius at alchemy.franken.de (Marius Strobl) Date: Wed Aug 26 20:59:14 2009 Subject: Audio on Sunblade 100 In-Reply-To: References: <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> Message-ID: <20090826205905.GG94142@alchemy.franken.de> On Mon, Aug 24, 2009 at 12:07:44PM +0200, Gheorghe Ardelean wrote: <...> Thanks for the dumps! > > >From all this dumps all I can see is that on my Blade100s there are some > bytes in the isab0@pci... dumps which are different from what the Christian > has: > > ardelean@ahorn:~> diff -u pciconf-myconfig1.txt pciconf-christian.txt > --- pciconf-myconfig1.txt 2009-08-24 11:24:52.758524000 +0200 > +++ pciconf-christian.txt 2009-08-24 11:25:30.791166000 +0200 > > -00 00 06 00 41 03 00 d3 04 02 00 04 00 00 01 10 > +00 00 06 00 41 03 00 d3 04 02 00 02 00 00 01 10 > > and the boot verbose part: > > -pcm0: sndbuf_setmap c1140000, 10000; 0xc0c62000 -> c1140000 > -pcm0: sndbuf_setmap c1160000, 10000; 0xc0c82000 -> c1160000 > +pcm0: sndbuf_setmap c1140000, 10000; 0xc0c50000 -> c1140000 > +pcm0: sndbuf_setmap c1160000, 10000; 0xc0c70000 -> c1160000 > The interesing bits here are the leftmost and the rightmost columns which contain the DVMA addresses. Aa they are indentical on both machines, incorrect bus_dma(9) parameters can be ruled out as a cause for the problem Christian is seeing. > So one can see that there are differences in the output of isab0@pci > dump and also in the dmesg. In the case of Christian this diference is > at bye offset 0x79 (one byte). In my case the difference is at > byteoffset 0x82 (two bytes). Christian could try whether changing the value of register 0x7b (I think you got the offset of the first one wrong) to 4 via `pciconf -wb isab0@pci0:0:7:0 0x7b 4` before playing audio makes any difference, but given that with the latest firmware your machines also use 2 without problems I doubt that will make a difference. > I don't know what is the meaning of this > bytes but maybe someone could tell us. Well, the datasheet for the M1543C southbridge, which in theory contains the same ISA bridge as its successor, just lists it as reserved. Unfortunately I don't have on for the M1543D which Sun uses. > > Nevertheless thank you Marius! It's working (at least for me :) > Unfortunately, I'm currently out of ideas what could be the reason for the problem Christian is seeing. Given that what I have works fine on 2 of 3 Blade 100 and my Blade 1500, I'll commit it once I had a chance to verify it doesn't break i386 though. It would be great however if you could try a slightly updated version of the patch at http://people.freebsd.org/~marius/t4dwave_M5451_32-bit.diff (MD5 hash: 7aaee2bfeab57c21ab23c98cf1c67f23) with one of your Blade 100. Marius From sr at genyosha.net Wed Aug 26 22:42:53 2009 From: sr at genyosha.net (Steve Rikli) Date: Wed Aug 26 22:42:59 2009 Subject: free Ultra5 in Silicon Valley, CA Message-ID: <20090826223006.GA14108@dragon.genyosha.net> I have a Sun Ultra5 in Silicon Valley, CA to give away. All I ask in return is reimbursement for shipping, and local pickups are also welcome. Disclaimer: I haven't used this server in a while but I loaded NetBSD 5.0 on it to wipe the disks and generally check the hardware so I believe it's in good shape. General config: Ultra5, 440MHz CPU, 1GB RAM, 2*hme, QLogic SCSI, 20GB IDE sysdisk, 18GB SCSI disk, Ultra5 server disk sled, CDROM Also including a spare 20GB IDE disk and the original floppy drive which is unused in favor of the installed server disk sled. Full dmesg is below. Cheers, sr. -- Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz), No Keyboard OpenBoot 3.31, 1024 MB (50 ns) memory installed, Serial #13024808. Ethernet address 8:0:20:c6:be:28, Host ID: 80c6be28. Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.0 (GENERIC) #0: Mon Apr 27 08:13:38 UTC 2009 builds@b4.netbsd.org:/home/builds/ab/netbsd-5-0-RELEASE/sparc64/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/sparc64/compile/GENERIC total memory = 1024 MB avail memory = 992 MB timecounter: Timecounters tick every 10.000 msec mainbus0 (root): SUNW,Ultra-5_10 (Sun Ultra 5/10 UPA/PCI): hostid 80c6be28 cpu0 at mainbus0: SUNW,UltraSPARC-IIi @ 440 MHz, UPA id 0 cpu0: 32K instruction (32 b/l), 16K data (32 b/l), 2048K external (64 b/l) psycho0 at mainbus0 addr 0xfffc4000 psycho0: SUNW,sabre: impl 0, version 0: ign 7c0 bus range 0 to 2; PCI bus 0 DVMA map: c0000000 to e0000000 IOTSB: 11b8000 to 1238000 pci0 at psycho0 pci0: i/o space, memory space enabled ppb0 at pci0 dev 1 function 1: Sun Microsystems Simba PCI bridge (rev. 0x13) pci1 at ppb0 bus 1 pci1: i/o space, memory space enabled ebus0 at pci1 dev 1 function 0 ebus0: Sun Microsystems PCIO Ebus2, revision 0x01 auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 72c000-72c003, 72f000-72f003 power at ebus0 addr 724000-724003 ipl 37 not configured SUNW,pll at ebus0 addr 504000-504002 not configured sab0 at ebus0 addr 400000-40007f ipl 43: rev 3.2 sabtty0 at sab0 port 0: console i/o sabtty1 at sab0 port 1 com0 at ebus0 addr 3083f8-3083ff ipl 41: ns16550a, working fifo kbd0 at com0 com1 at ebus0 addr 3062f8-3062ff ipl 42: ns16550a, working fifo ms0 at com1 wsmouse0 at ms0 mux 0 lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 700000-70000f ipl 34 fdthree at ebus0 addr 3023f0-3023f7, 706000-70600f, 720000-720003 ipl 39 not configured clock0 at ebus0 addr 0-1fff: mk48t59 flashprom at ebus0 addr 0-fffff not configured audiocs0 at ebus0 addr 200000-2000ff, 702000-70200f, 704000-70400f, 722000-722003 ipl 35 ipl 36: CS4231A audio0 at audiocs0: full duplex hme0 at pci1 dev 1 function 1: Sun Happy Meal Ethernet, rev. 1 hme0: interrupting at ivec 3021 hme0: Ethernet address 08:00:20:c6:be:28 nsphy0 at hme0 phy 1: DP83840 10/100 media interface, rev. 1 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto machfb0 at pci1 dev 2 function 0: ATI Technologies 3D Rage Pro (rev. 0x5c) machfb0: 16 MB aperture at 0xe1000000, 4 KB registers at 0xe2000000 machfb0: 4096 KB SGRAM 98.924 MHz, maximum RAMDAC clock 230 MHz mach64_get_mode: 1152 5304 5432 1528 900 902 938 937 machfb0: initial resolution 1152x864 at 8 bpp machfb0: attached to /dev/fb0 machfb0: initializing the DSP wsdisplay1 at machfb0 kbdmux 1 wsmux1: connecting to wsdisplay1 wsdisplay1: screen 0-3 added (default) cmdide0 at pci1 dev 3 function 0 cmdide0: CMD Technology PCI0646 (rev. 0x03) cmdide0: bus-master DMA support present cmdide0: primary channel configured to native-PCI mode cmdide0: using ivec 1820 for native-PCI interrupt atabus0 at cmdide0 channel 0 cmdide0: secondary channel configured to native-PCI mode atabus1 at cmdide0 channel 1 ppb1 at pci0 dev 1 function 0: Sun Microsystems Simba PCI bridge (rev. 0x13) pci2 at ppb1 bus 2 pci2: i/o space, memory space enabled Sun Microsystems PCIO Ebus2 (miscellaneous bridge, revision 0x01) at pci2 dev 1 function 0 not configured hme1 at pci2 dev 1 function 1: Sun Happy Meal Ethernet, rev. 1 hme1: interrupting at ivec 3011 hme1: Ethernet address 08:00:20:c6:be:28 ukphy0 at hme1 phy 1: Generic IEEE 802.3u media interface ukphy0: OUI 0x0006b8, model 0x000c, rev. 1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isp0 at pci2 dev 2 function 0: QLogic 1020 Fast Wide SCSI HBA isp0: interrupting at ivec 14 Sun Microsystems PCIO Ebus2 (miscellaneous bridge, revision 0x01) at pci2 dev 3 function 0 not configured hme2 at pci2 dev 3 function 1: Sun Happy Meal Ethernet, rev. 1 hme2: interrupting at ivec 3019 hme2: Ethernet address 08:00:20:c6:be:28 ukphy1 at hme2 phy 1: Generic IEEE 802.3u media interface ukphy1: OUI 0x0006b8, model 0x000c, rev. 1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcons at mainbus0 not configured timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0 timecounter: Timecounter "tick-counter" frequency 440000000 Hz quality 100 No counter-timer -- using %tick at 440MHz as system clock. wskbd0 at kbd0 mux 1 scsibus0 at isp0: 16 targets, 8 luns per target scsibus0: waiting 2 seconds for devices to settle... kbd0: reset failed wskbd0: connecting to wsdisplay1 wd0 at atabus0 drive 0: wd0: drive supports 16-sector PIO transfers, LBA addressing wd0: 19092 MB, 38792 cyl, 16 head, 63 sec, 512 bytes/sect x 39102336 sectors wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) wd0(cmdide0:0:0): using PIO mode 4, DMA mode 2 (using DMA) atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 0: cdrom removable cd0: drive supports PIO mode 4, DMA mode 2 cd0(cmdide0:1:0): using PIO mode 4, DMA mode 2 (using DMA) sd0 at scsibus0 target 0 lun 0: disk fixed sd0: 17628 MB, 26866 cyl, 3 head, 447 sec, 512 bytes/sect x 36102720 sectors sd0: sync (50.00ns offset 8), 16-bit (40.000MB/s) transfers, tagged queueing Kernelized RAIDframe activated root on wd0a dumps on wd0b root file system type: ffs From rc at networkz.ch Sun Aug 30 12:04:17 2009 From: rc at networkz.ch (Christian Ramseyer) Date: Sun Aug 30 12:04:24 2009 Subject: Audio on Sunblade 100 In-Reply-To: <20090826205905.GG94142@alchemy.franken.de> References: <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de> <20090826205905.GG94142@alchemy.franken.de> Message-ID: <4A9A6ABD.4020803@networkz.ch> Marius Strobl wrote: > > Christian could try whether changing the value of register > 0x7b (I think you got the offset of the first one wrong) to > 4 via `pciconf -wb isab0@pci0:0:7:0 0x7b 4` before playing > audio makes any difference, but given that with the latest > firmware your machines also use 2 without problems I doubt > that will make a difference. > Hi Marius As you suspected, it didn't make a difference. Thanks for your effort anyways. Christian From bugmaster at FreeBSD.org Mon Aug 31 11:07:16 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 31 11:09:35 2009 Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org Message-ID: <200908311107.n7VB7FF4070713@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/113556 sparc64 [panic] trap: memory address not aligned; Rebooting... f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 [hang] system is hung during boot from CD o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 12 problems total.