isisalsa-devel Mailing List for Guillemot Maxisound ISIS ALSA driver (Page 4)
Status: Inactive
Brought to you by:
jeanseb
Menu
▾
▴
isisalsa-devel — Developers mailing list
You can subscribe to this list here.
| 2003 |
Jan
(7) |
Feb
(1) |
Mar
(8) |
Apr
|
May
(7) |
Jun
(3) |
Jul
(16) |
Aug
(12) |
Sep
(3) |
Oct
|
Nov
(11) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
(4) |
Apr
(6) |
May
|
Jun
(8) |
Jul
(4) |
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(2) |
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(4) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: V. <jea...@fr...> - 2003-09-06 13:30:19
|
good holiday ;) Please when you'll be back join #isisalsa channel on irc.freenode.net to talk online about coding the driver. On Tue, 02 Sep 2003 18:24:06 +0200 "Pieter Palmers" <ppa...@es...> nous a dis: > Hi all, > > I won't be able to answer to support requests for the next 3 weeks. Not > that you can't send them to this list... maybe someone else can help you > in the mean time. I will answer everything when I get back. > > Pieter > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Isisalsa-devel mailing list > Isi...@li... > https://lists.sourceforge.net/lists/listinfo/isisalsa-devel |
|
From: Pieter P. <ppa...@es...> - 2003-09-02 16:25:47
|
Hi all, I won't be able to answer to support requests for the next 3 weeks. Not that you can't send them to this list... maybe someone else can help you in the mean time. I will answer everything when I get back. Pieter |
|
From: Pieter P. <pie...@st...> - 2003-08-23 05:33:36
|
Anthony wrote: >* Pieter Palmers <ppa...@es...> [Aug 18 03 05:42]: > > >>Hi, >> >>You can find most info about the alsa driver for the ISIS at >>http://isisalsa.sourceforge.net/ >> >> > >Excellent news. We picked up this card for dirt cheap, so I'm glad >there is some hope of using it. > > > >>A few weeks ago there was a first driver release, based upon alsa 0.9.5. >> >>There are two utils available to make the ISIS work: >>* maxiinit: a firmware load/card config utility that enables the card >>* an alsa driver (beta release) for the isis in 'multimedia' mode. >> >>after using the maxiinit tool, you can choose which driver you want to >>use: the isis driver or the generic maestro2E driver. The latter offers >>only es1968 support, but is of higher quality than the isis driver, >>which is a beta release. >> >> > >To be clear, we have the Maxi Studio card. I know almost nothing about >it, but I see there is some good reading material for me. The goal is to >get the breakout box 8 channels working for recording. Has anybody had >any success doing this? > > The recording functionallity isn't implemented yet. Playback only. > > >>Should you have some time available for this project, it would be very >>welcome. For the moment I'm the only one working on it, and I don't have >>that much spare time. >> >> > >I will try out the existing driver this week hopefully. Unfortunately, I >don't have access to the machine often other than through ssh, which makes >devloping difficult. Not to mention I have little expierence doing such >things. But, I do hope to eventually invest some time. Thanks for the reply. > no problem. Pieter |
|
From: Anthony <av...@uw...> - 2003-08-22 21:34:07
|
Hi, I've succesfully compiled the drivers and maxiinit. For the later I had to manually compile the lib directory, but no big deal. I loaded the PCI64.BIN firmware and loaded the module and it all looks good so far. Can't really test it till I get into the studio but aplay -l arecord -l and alsamixer all seem reasonable. * Pieter Palmers <pie...@st...> [Aug 22 03 16:29]: > The recording functionallity isn't implemented yet. Playback only. Well this is a must do for me. Do you have any plans, thoughts, suggestions on how to proceed? Thanks. --ant |
|
From: Pieter P. <pie...@st...> - 2003-08-21 17:32:27
|
Felipe Sologuren wrote:
> Pieter Palmers wrote:
>
>> Felipe Sologuren wrote:
>>
>>> -------- Original Message --------
>>> Subject: Re: isis driver
>>> Date: Sat, 16 Aug 2003 13:11:32 -0400
>>> From: Felipe Sologuren <sol...@es...>
>>> To: ppalmers <Pie...@es...>
>>> References: <3F3...@es...>
>>> <3F3...@es...>
>>> <106...@we...>
>>>
>>> ppalmers wrote:
>>>
>>>>> Cold reboot from windows is still necessary for maxiinit not?
>>>>>
>>>>
>>>>
>>>> windows boot is not nescessary. On my system, everything works
>>>> without windows boot.
>>>>
>>>>
>>>>
>>> Pieter:
>>> Yesterday, I could listen audio in XMMS with snd-es1968 (the
>>> sound was good) but with snd-isis module the error is the same
>>> ('ALSA sam_io.c:345: sam9407: command 0x3 ack timeout...').
>>> I don't know if it could be an irq problem.
>>> It could be a problem with my chipset VIA KT333 & VT8235 yet?
>>> The card is in the slot 5 of pci bus and the onboard sound is disabled.
>>> In bios, for settings, this slot have the same irq (5) with slot 2
>>> (empty).
>>> I have RH7.3 again with kernel 2.4.18-3 and gcc 2.96.
>>> I think that in RH9 (not upgraded and in other partition) with
>>> kernel 2.4.20-8 and gcc 3.2 the result will be the same, I'll do the
>>> test tomorrow.
>>>
>>> In Via website exist a patch for ide timings. For 'time.h' of kernel
>>> sources. It could help?
>>>
>>> Thank you one more time,
>>> Felipe
>>
>>
>>
>>
>> Could you send me the output of the maxiinit script?
>
>
> I was probing several times...
> After login:
> - alsasound status: drivers loaded. But snd-isis isn't loaded.
> - lsmod only shows oss modules (I don't know why (/etc/hwconf?))
> 1) maxinit -> reports maxiinit-RH9-before
> 2) modprobe snd-isis -> fails like ever and sounds ugly.
> 3) maxiinit -> maxiinit-RH9-before
> 4) modprobe snd-es1968 -> good
> 5) maxiinit -> maxiinit-RH9-before
> 6) I can do aplay succesfully (after alsamixer)
> 7) modprobe -r snd-es1968 or alsasound stop -> sounds ugly
> 8) maxiinit -> maxiinit-RH9-after (this error doesn't resolve until
> step 4 or 9)
> 9) modprobe snd-isis -> fails and sounds ugly -> dmesg-RH9-after
> 10) I could do 3) again (in a loop)
>
> Only when snd-es1968 is loaded cat /proc/interrupts shows 5:Maestro...
>
> In RH7.3 the responses are the same except that in dmesg-RH9 exist a
> line with 'snd-malloc...' and lsmod in RH7.3 after step 7) with a
> module snd-page-alloc-... (I suppose it means the same not?)
>
> Today, after several hours (more than 20) of my pc connected to
> Internet without me, I could to load snd-isis but I don't know how nor
> why. Only know that es1968 were loaded all those time.
> Aplay were locked, and I couldn't do alsasound stop. cat
> /proc/interrupts shows 5:Isis..., and dmesg several lines with hexas.
>
> I know it could do but I don't know how! :(
>
>> How many errors does it generate?
>
>
> 2 unexpected responses.
> One time I haved maxiinit-RH9-2 but I don't remember the secuency of
> commands.
>
can you try using the attached firmware?
Pieter
|
|
From: Anthony <av...@uw...> - 2003-08-21 17:09:24
|
* Pieter Palmers <ppa...@es...> [Aug 18 03 05:42]: > Hi, > > You can find most info about the alsa driver for the ISIS at > http://isisalsa.sourceforge.net/ Excellent news. We picked up this card for dirt cheap, so I'm glad there is some hope of using it. > A few weeks ago there was a first driver release, based upon alsa 0.9.5. > > There are two utils available to make the ISIS work: > * maxiinit: a firmware load/card config utility that enables the card > * an alsa driver (beta release) for the isis in 'multimedia' mode. > > after using the maxiinit tool, you can choose which driver you want to > use: the isis driver or the generic maestro2E driver. The latter offers > only es1968 support, but is of higher quality than the isis driver, > which is a beta release. To be clear, we have the Maxi Studio card. I know almost nothing about it, but I see there is some good reading material for me. The goal is to get the breakout box 8 channels working for recording. Has anybody had any success doing this? > Should you have some time available for this project, it would be very > welcome. For the moment I'm the only one working on it, and I don't have > that much spare time. I will try out the existing driver this week hopefully. Unfortunately, I don't have access to the machine often other than through ssh, which makes devloping difficult. Not to mention I have little expierence doing such things. But, I do hope to eventually invest some time. Thanks for the reply. --ant |
|
From: Felipe S. <sol...@es...> - 2003-08-19 07:58:00
|
Pieter Palmers wrote:
> Felipe Sologuren wrote:
>
>> -------- Original Message --------
>> Subject: Re: isis driver
>> Date: Sat, 16 Aug 2003 13:11:32 -0400
>> From: Felipe Sologuren <sol...@es...>
>> To: ppalmers <Pie...@es...>
>> References: <3F3...@es...>
>> <3F3...@es...>
>> <106...@we...>
>>
>> ppalmers wrote:
>>
>>>> Cold reboot from windows is still necessary for maxiinit not?
>>>>
>>>
>>>
>>> windows boot is not nescessary. On my system, everything works
>>> without windows boot.
>>>
>>>
>>>
>> Pieter:
>> Yesterday, I could listen audio in XMMS with snd-es1968 (the sound
>> was good) but with snd-isis module the error is the same ('ALSA
>> sam_io.c:345: sam9407: command 0x3 ack timeout...').
>> I don't know if it could be an irq problem.
>> It could be a problem with my chipset VIA KT333 & VT8235 yet?
>> The card is in the slot 5 of pci bus and the onboard sound is disabled.
>> In bios, for settings, this slot have the same irq (5) with slot 2
>> (empty).
>> I have RH7.3 again with kernel 2.4.18-3 and gcc 2.96.
>> I think that in RH9 (not upgraded and in other partition) with kernel
>> 2.4.20-8 and gcc 3.2 the result will be the same, I'll do the test
>> tomorrow.
>>
>> In Via website exist a patch for ide timings. For 'time.h' of kernel
>> sources. It could help?
>>
>> Thank you one more time,
>> Felipe
>
>
>
> Could you send me the output of the maxiinit script?
I was probing several times...
After login:
- alsasound status: drivers loaded. But snd-isis isn't loaded.
- lsmod only shows oss modules (I don't know why (/etc/hwconf?))
1) maxinit -> reports maxiinit-RH9-before
2) modprobe snd-isis -> fails like ever and sounds ugly.
3) maxiinit -> maxiinit-RH9-before
4) modprobe snd-es1968 -> good
5) maxiinit -> maxiinit-RH9-before
6) I can do aplay succesfully (after alsamixer)
7) modprobe -r snd-es1968 or alsasound stop -> sounds ugly
8) maxiinit -> maxiinit-RH9-after (this error doesn't resolve until step
4 or 9)
9) modprobe snd-isis -> fails and sounds ugly -> dmesg-RH9-after
10) I could do 3) again (in a loop)
Only when snd-es1968 is loaded cat /proc/interrupts shows 5:Maestro...
In RH7.3 the responses are the same except that in dmesg-RH9 exist a
line with 'snd-malloc...' and lsmod in RH7.3 after step 7) with a module
snd-page-alloc-... (I suppose it means the same not?)
Today, after several hours (more than 20) of my pc connected to Internet
without me, I could to load snd-isis but I don't know how nor why. Only
know that es1968 were loaded all those time.
Aplay were locked, and I couldn't do alsasound stop. cat
/proc/interrupts shows 5:Isis..., and dmesg several lines with hexas.
I know it could do but I don't know how! :(
> How many errors does it generate?
2 unexpected responses.
One time I haved maxiinit-RH9-2 but I don't remember the secuency of
commands.
>
> Pieter
>
>
Regards,
Felipe
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Isisalsa-devel mailing list
> Isi...@li...
> https://lists.sourceforge.net/lists/listinfo/isisalsa-devel
>
>
|
|
From: Pieter P. <pie...@st...> - 2003-08-18 10:06:36
|
Felipe Sologuren wrote:
> -------- Original Message --------
> Subject: Re: isis driver
> Date: Sat, 16 Aug 2003 13:11:32 -0400
> From: Felipe Sologuren <sol...@es...>
> To: ppalmers <Pie...@es...>
> References: <3F3...@es...>
> <3F3...@es...>
> <106...@we...>
>
> ppalmers wrote:
>
>>> Cold reboot from windows is still necessary for maxiinit not?
>>>
>>
>>
>> windows boot is not nescessary. On my system, everything works
>> without windows boot.
>>
>>
>>
> Pieter:
> Yesterday, I could listen audio in XMMS with snd-es1968 (the sound
> was good) but with snd-isis module the error is the same ('ALSA
> sam_io.c:345: sam9407: command 0x3 ack timeout...').
> I don't know if it could be an irq problem.
> It could be a problem with my chipset VIA KT333 & VT8235 yet?
> The card is in the slot 5 of pci bus and the onboard sound is disabled.
> In bios, for settings, this slot have the same irq (5) with slot 2
> (empty).
> I have RH7.3 again with kernel 2.4.18-3 and gcc 2.96.
> I think that in RH9 (not upgraded and in other partition) with kernel
> 2.4.20-8 and gcc 3.2 the result will be the same, I'll do the test
> tomorrow.
>
> In Via website exist a patch for ide timings. For 'time.h' of kernel
> sources. It could help?
>
> Thank you one more time,
> Felipe
Could you send me the output of the maxiinit script?
How many errors does it generate?
Pieter
|
|
From: Felipe S. <sol...@es...> - 2003-08-18 05:08:39
|
Felipe Sologuren wrote:
> -------- Original Message --------
> Subject: Re: isis driver
> Date: Sat, 16 Aug 2003 13:11:32 -0400
> From: Felipe Sologuren <sol...@es...>
> To: ppalmers <Pie...@es...>
> References: <3F3...@es...>
> <3F3...@es...>
> <106...@we...>
>
> ppalmers wrote:
>
>>> Cold reboot from windows is still necessary for maxiinit not?
>>>
>>
>>
>> windows boot is not nescessary. On my system, everything works without
>> windows boot.
>>
>>
>>
> Pieter:
> Yesterday, I could listen audio in XMMS with snd-es1968 (the sound
> was good) but with snd-isis module the error is the same ('ALSA
> sam_io.c:345: sam9407: command 0x3 ack timeout...').
> I don't know if it could be an irq problem.
> It could be a problem with my chipset VIA KT333 & VT8235 yet?
> The card is in the slot 5 of pci bus and the onboard sound is disabled.
> In bios, for settings, this slot have the same irq (5) with slot 2 (empty).
> I have RH7.3 again with kernel 2.4.18-3 and gcc 2.96.
> I think that in RH9 (not upgraded and in other partition) with kernel
> 2.4.20-8 and gcc 3.2 the result will be the same, I'll do the test
> tomorrow.
Effectively snd-es1968 works in RH9 and snd-isis doesn't load.
Somebody have an idea about this?
>
> In Via website exist a patch for ide timings. For 'time.h' of kernel
> sources. It could help?
>
> Thank you one more time,
> Felipe
>
>
> ------------------------------------------------------------------------
>
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8367 [KT266]
> Subsystem: VIA Technologies, Inc.: Unknown device 0000
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> Latency: 8
> Region 0: Memory at e0000000 (32-bit, prefetchable) [size=32M]
> Capabilities: [a0] AGP version 2.0
> Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2
> Command: RQ=31 SBA- AGP+ 64bit- FW- Rate=<none>
> Capabilities: [c0] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8367 [KT266 AGP] (prog-if 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> Latency: 0
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> Memory behind bridge: dde00000-dfefffff
> Prefetchable memory behind bridge: d9d00000-ddcfffff
> BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
> Capabilities: [80] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
> Subsystem: Guillemot Corporation: Unknown device 0010
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (500ns min, 6000ns max)
> Interrupt: pin A routed to IRQ 5
> Region 0: I/O ports at ec00 [size=256]
> Capabilities: [c0] Power Management version 2
> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:0a.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 31)
> Subsystem: Unknown device 3030:5032
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (5000ns min, 10000ns max)
> Interrupt: pin A routed to IRQ 10
> Region 0: I/O ports at e800 [size=256]
> Region 1: Memory at dfffff00 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at dff80000 [disabled] [size=256K]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=220mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3177
> Subsystem: VIA Technologies, Inc.: Unknown device 0000
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Capabilities: [c0] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
> Subsystem: Micro-star International Co Ltd: Unknown device 7120
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32
> Interrupt: pin A routed to IRQ 14
> Region 4: I/O ports at fc00 [size=16]
> Capabilities: [c0] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta] (rev 15) (prog-if 00 [VGA])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 248 (1250ns min, 250ns max)
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
> Region 1: Memory at da000000 (32-bit, prefetchable) [size=32M]
> Expansion ROM at dfef0000 [disabled] [size=64K]
> Capabilities: [60] Power Management version 1
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [44] AGP version 2.0
> Status: RQ=31 SBA- 64bit- FW- Rate=x1,x2
> Command: RQ=31 SBA- AGP+ 64bit- FW- Rate=<none>
>
>
> ------------------------------------------------------------------------
>
> Linux version 2.4.18-3 (bhc...@po...) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 Thu Apr 18 07:32:41 EDT 2002
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
> BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> found SMP MP-table at 000fb930
> hm, page 000fb000 reserved twice.
> hm, page 000fc000 reserved twice.
> hm, page 000f6000 reserved twice.
> hm, page 000f7000 reserved twice.
> On node 0 totalpages: 65536
> zone(0): 4096 pages.
> zone(1): 61440 pages.
> zone(2): 0 pages.
> Intel MultiProcessor Specification v1.1
> Virtual Wire compatibility mode.
> OEM ID: VIA Product ID: VT5440B APIC at: 0xFEE00000
> Processor #0 Pentium(tm) Pro APIC version 17
> I/O APIC #2 Version 3 at 0xFEC00000.
> Processors: 1
> Kernel command line: ro root=/dev/hda4 hdd=ide-scsi
> ide_setup: hdd=ide-scsi
> Initializing CPU#0
> Detected 950.043 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 1893.99 BogoMIPS
> Memory: 255384k/262144k available (1125k kernel code, 6372k reserved, 802k data, 296k init, 0k highmem)
> Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
> Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
> Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
> Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
> Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> CPU: Before vendor init, caps: 0183fbff c1c7fbff 00000000, vendor = 2
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 256K (64 bytes/line)
> CPU: After vendor init, caps: 0183fbff c1c7fbff 00000000 00000000
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
> CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
> CPU: AMD Athlon(tm) Processor stepping 02
> Enabling fast FPU save and restore... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch (rg...@at...)
> mtrr: detected mtrr type: Intel
> PCI: PCI BIOS revision 2.10 entry at 0xfdaf1, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Unknown bridge resource 0: assuming transparent
> PCI: Using IRQ router default [1106/3177] at 00:11.0
> PCI: Hardcoded IRQ 14 for device 00:11.1
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
> Starting kswapd
> VFS: Diskquotas version dquot_6.5.0 initialized
> pty: 2048 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
> Real Time Clock Driver v1.10e
> block: 496 slots per queue, batch=124
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> VP_IDE: IDE controller on PCI bus 00 dev 89
> PCI: Hardcoded IRQ 14 for device 00:11.1
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: Unknown VIA SouthBridge, contact Vojtech Pavlik <vo...@su...>
> hda: MAXTOR 6L040J2, ATA DISK drive
> hdc: QUANTUM FIREBALLlct10 10, ATA DISK drive
> hdd: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide0: probed IRQ 14 failed, using default.
> ide1 at 0x170-0x177,0x376 on irq 15
> ide1: probed IRQ 15 failed, using default.
> hda: 78177792 sectors (40027 MB) w/1818KiB Cache, CHS=4866/255/63
> hdc: 20044080 sectors (10263 MB) w/418KiB Cache, CHS=19885/16/63
> ide-floppy driver 0.99.newide
> Partition check:
> hda: hda1 hda2 hda3 hda4
> hdc: [PTBL] [1247/255/63] hdc1 hdc2
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> ide-floppy driver 0.99.newide
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 2048 buckets, 16Kbytes
> TCP: Hash tables configured (established 16384 bind 16384)
> Linux IP multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 152k freed
> VFS: Mounted root (ext2 filesystem).
> reiserfs: checking transaction log (device 03:04) ...
> Using r5 hash to sort names
> ReiserFS version 3.6.25
> Freeing unused kernel memory: 296k freed
> Adding Swap: 506036k swap-space (priority -1)
> Adding Swap: 522104k swap-space (priority -2)
> SCSI subsystem driver Revision: 1.00
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: HL-DT-ST Model: CD-RW GCE-8400B Rev: 1.01
> Type: CD-ROM ANSI SCSI revision: 02
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
> parport0: irq 7 detected
> ip_conntrack (2048 buckets, 16384 max)
> 0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4363 Sat Apr 19 17:46:46 PDT 2003
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 204M
> agpgart: Detected Via Apollo Pro KT266 chipset
> agpgart: AGP aperture is 32M @ 0xe0000000
> Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
> sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.12
> isis: loading driver built on 01:56:25 Aug 14 2003
> ALSA isis.c:2632: Entering ISIS create
> ALSA isis.c:2822: isis: loading SAM driver
> ALSA sam9407.c:27: sam9407: Creating chip
> ALSA sam_pcm.c:937: creating 1/2 controls
> ALSA sam_pcm.c:975: creating 3/4 controls
> ALSA sam_ucode.c:324: new HWDEP
> ALSA sam_mpu401.c:305: creating MIDI controls
> ALSA sam9407.c:121: sam9407: Creating chip done
> ALSA sam9407.c:154: sam9407: Init chip
> ALSA sam_io.c:345: sam9407: command 0x3 ack timeout
> ALSA sam_io.c:345: sam9407: command 0x2 ack timeout
> ALSA sam_mem.c:128: sam9407: transfer 192 words from address 0x0 failed
> ALSA isis.c:2215: isis: Error creating SAM chip
> ALSA sam9407.c:327: sam9407: devfree chip
> ALSA sam9407.c:285: sam9407: free chip
> ALSA sam9407.c:268: sam9407: cleanup shadows
> Maxi Studio ISIS soundcard not found or device busy
> isis: loading driver built on 01:56:25 Aug 14 2003
> ALSA isis.c:2632: Entering ISIS create
> ALSA isis.c:2822: isis: loading SAM driver
> ALSA sam9407.c:27: sam9407: Creating chip
> ALSA sam_pcm.c:937: creating 1/2 controls
> ALSA sam_pcm.c:975: creating 3/4 controls
> ALSA sam_ucode.c:324: new HWDEP
> ALSA sam_mpu401.c:305: creating MIDI controls
> ALSA sam9407.c:121: sam9407: Creating chip done
> ALSA sam9407.c:154: sam9407: Init chip
> ALSA sam_io.c:345: sam9407: command 0x3 ack timeout
> ALSA sam_io.c:345: sam9407: command 0x2 ack timeout
> ALSA sam_mem.c:128: sam9407: transfer 192 words from address 0x0 failed
> ALSA isis.c:2215: isis: Error creating SAM chip
> ALSA sam9407.c:327: sam9407: devfree chip
> ALSA sam9407.c:285: sam9407: free chip
> ALSA sam9407.c:268: sam9407: cleanup shadows
> Maxi Studio ISIS soundcard not found or device busy
> isis: loading driver built on 01:56:25 Aug 14 2003
> ALSA isis.c:2632: Entering ISIS create
> ALSA isis.c:2822: isis: loading SAM driver
> ALSA sam9407.c:27: sam9407: Creating chip
> ALSA sam_pcm.c:937: creating 1/2 controls
> ALSA sam_pcm.c:975: creating 3/4 controls
> ALSA sam_ucode.c:324: new HWDEP
> ALSA sam_mpu401.c:305: creating MIDI controls
> ALSA sam9407.c:121: sam9407: Creating chip done
> ALSA sam9407.c:154: sam9407: Init chip
> ALSA sam_io.c:345: sam9407: command 0x3 ack timeout
> ALSA sam_io.c:345: sam9407: command 0x2 ack timeout
> ALSA sam_mem.c:128: sam9407: transfer 192 words from address 0x0 failed
> ALSA isis.c:2215: isis: Error creating SAM chip
> ALSA sam9407.c:327: sam9407: devfree chip
> ALSA sam9407.c:285: sam9407: free chip
> ALSA sam9407.c:268: sam9407: cleanup shadows
> Maxi Studio ISIS soundcard not found or device busy
|
|
From: Felipe S. <sol...@es...> - 2003-08-17 18:26:33
|
-------- Original Message --------
Subject: Re: isis driver
Date: Sat, 16 Aug 2003 13:11:32 -0400
From: Felipe Sologuren <sol...@es...>
To: ppalmers <Pie...@es...>
References: <3F3...@es...>
<3F3...@es...>
<106...@we...>
ppalmers wrote:
>>Cold reboot from windows is still necessary for maxiinit not?
>>
>
>
> windows boot is not nescessary. On my system, everything works without windows
> boot.
>
>
>
Pieter:
Yesterday, I could listen audio in XMMS with snd-es1968 (the sound was
good) but with snd-isis module the error is the same ('ALSA
sam_io.c:345: sam9407: command 0x3 ack timeout...').
I don't know if it could be an irq problem.
It could be a problem with my chipset VIA KT333 & VT8235 yet?
The card is in the slot 5 of pci bus and the onboard sound is disabled.
In bios, for settings, this slot have the same irq (5) with slot 2 (empty).
I have RH7.3 again with kernel 2.4.18-3 and gcc 2.96.
I think that in RH9 (not upgraded and in other partition) with kernel
2.4.20-8 and gcc 3.2 the result will be the same, I'll do the test tomorrow.
In Via website exist a patch for ide timings. For 'time.h' of kernel
sources. It could help?
Thank you one more time,
Felipe
|
|
From: V. <jea...@fr...> - 2003-08-13 20:23:28
|
Lots of stuf to compile (full alsa ?) but it work. The only thing that I had to search was the mixer to unmute voice when i realise why I didn't hear any sound. I need to run the init prog before pluging the module but the go script do that so i guess it is the right way. On Mon, 11 Aug 2003 19:19:18 +0200 "Pieter Palmers" <ppa...@es...> nous a dis: > Hi all, > > I'd like some reports on the driver... is it possible for all people who > installed the driver to report their experiences? > > Thanks, > > > Pieter > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Isisalsa-devel mailing list > Isi...@li... > https://lists.sourceforge.net/lists/listinfo/isisalsa-devel |
|
From: Pieter P. <ppa...@es...> - 2003-08-11 17:19:17
|
Hi all, I'd like some reports on the driver... is it possible for all people who installed the driver to report their experiences? Thanks, Pieter |
|
From: Pieter P. <ppa...@es...> - 2003-08-11 16:19:45
|
Jean-Sébastien Valette wrote: > I'm a french coder who were working in a same project like you. >I'm looking at the code and it seem to me that the cvs contain lot's of stuff that isn't part of the useful code. >I'm thinking useful code is only in the mai dir (the one containing isis.c) am i right ? > >By looking at the code I see that there is 2 spin lock for the dream chip (with and whitout irq). >are they still both used and if so are they locking the same thing or different part ? > > The driver, in it's current state, is of rather poor quality. It is therefore possible that there are some spinlocks that are defined but not used, or other issues. I don't even think that this driver would work on multiprocessor machines because the spinlocks aren't used correctly. To summarize: I don't know... the driver works acceptably good for the moment. I intend to do a complete rewrite of the driver. The current driver is the result of a lot of experimenting with the ISIS to get it working (hence the tons of commented code). On top of that, it's my first expierence with ALSA driver writing, and (linux) driver developement in general. No wonder it's messy. >I've also created an irc channel on irc.freenode.net named isisalsa. >Please join it as it is a good way to talk about driver code ans to do support for end user. > > > Nice idea. Pieter >------- >jeanseb >I know it look like I'm insane >Take a closer look I'm not to blame. >If love is blind I guess I'll buy myself a cane > (slash / axl rose ) > > >------------------------------------------------------- >This SF.Net email sponsored by: Free pre-built ASP.NET sites including >Data Reports, E-commerce, Portals, and Forums are available now. >Download today and enter to win an XBOX or Visual Studio .NET. >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 >_______________________________________________ >Isisalsa-devel mailing list >Isi...@li... >https://lists.sourceforge.net/lists/listinfo/isisalsa-devel > > > |
|
From: V. <jea...@fr...> - 2003-08-04 17:28:37
|
I'm a french coder who were working in a same project like you. I'm looking at the code and it seem to me that the cvs contain lot's of stuff that isn't part of the useful code. I'm thinking useful code is only in the mai dir (the one containing isis.c) am i right ? By looking at the code I see that there is 2 spin lock for the dream chip (with and whitout irq). are they still both used and if so are they locking the same thing or different part ? I've also created an irc channel on irc.freenode.net named isisalsa. Please join it as it is a good way to talk about driver code ans to do support for end user. ------- jeanseb I know it look like I'm insane Take a closer look I'm not to blame. If love is blind I guess I'll buy myself a cane (slash / axl rose ) |
|
From: Pieter P. <pie...@st...> - 2003-07-30 08:52:11
|
Felipe Sologuren wrote:
> Pieter Palmers wrote:
>
>> Please don't install gcc 3.1! Upgrading to gcc 3 is something you can
>> easily spend a few days on.
>> Besides, this isn't the problem in this case.
>
>
> You are right, the problem isn't resolve.
> Now I have RH9 (upgraded) with same kernel and gcc 3.2. (I have some
> time thinking in upgrade, isn't a problem, BTW :)
>
>>
>> Did you load the pci64.bin firmware with maxiinit?
>
>
> Maxinit don't have problems. When you release the firmware loader, I
> haved 2 strange responses, but isis works. Now I have 0 strange
> responses.
I assume this means that the driver now works for you?
If it doesn't I have the following suggestions:
1) Your card seems to be running on IRQ 9. It might work better when
forced to use IRQ5. You can do this by assigning IRQ5 to the PCI slot
the isis is in, in the bios.
>00:07.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E
(rev 10)
> Subsystem: Guillemot Corporation: Unknown device 0010
> Flags: bus master, medium devsel, latency 128, IRQ 9
2) I also notice that you are using another soundcard that is also on
IRQ9. The isis driver doesn't support IRQ sharing (yet). Forcing the IRQ
of the isis to 5, like suggested above, could solve this problem. Or, as
I suspect that this is the on-board soundcard of the mainboard, you
could disable this on-bord sound.
>00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233
AC97 Audio Controller (rev 10)
> Subsystem: Avance Logic Inc.: Unknown device 4710
> Flags: medium devsel, IRQ 9
The dmesg log tells me that it is definately an IRQ problem. Maxiinit
doesn't use interrupts to communicate with the ISIS, therefore it
doesn't report any errors. The first error statement in the dmesg log
('ALSA sam_io.c:345: sam9407: command 0x3 ack timeout') corresponds with
the first time the driver expects a response from the sam chip (for
which it needs to receive an interrupt).
>
>
> Thank you again, Pieter.
No problem
>
> Felipe.
>
> PD: Other question: capture from your driver don't work because
> Maestro driver from Alsa don't do it?
> (Is this an extra problem for you?)
>
The only capture that is implemented is the one from the maestro driver,
and as I based on the standard es1968 driver of the ALSA package, it
suffers from the same problems as this driver. And indeed, I saw some
posts on the alsa-devel mailing list about the capture part of the
es1968 not working with the maestro2E. I haven't tried myself, but I
assume this applies to the isis maestro driver as well.
I don't intend to correct this problem myself, I'll leave it up to the
es1968 maintainers. I don't know how the maestro PCM stuff works.
Besides: all capture with the isis should be done through the SAM part
anyway. The maestro recording is lousy compared to the SAM recording.
I should also mention that I suspect that this linux driver lowers the
card's latency by a factor 2 or more, as compared to the windows driver.
Havent been able to test this statement though.
There are two reasons for this lower latency:
1) the ALSA framework provides far better latency specs than the
equivalent windows framework. (if you use a low latency kernel)
2) My driver uses a variable hardware buffer size, whereas the windows
driver uses a fixed buffer size of 4096 stereo samples. When
applications use the "default" alsa settings, this results in a buffer
size of 2048 stereo samples, which corresponds to 4.2ms.
But this is theory, let's wait & see if it's really true.
Ciao,
Pieter
|
|
From: Felipe S. <sol...@es...> - 2003-07-29 21:01:53
|
Pieter Palmers wrote:
> Please don't install gcc 3.1! Upgrading to gcc 3 is something you can
> easily spend a few days on.
> Besides, this isn't the problem in this case.
You are right, the problem isn't resolve.
Now I have RH9 (upgraded) with same kernel and gcc 3.2. (I have some
time thinking in upgrade, isn't a problem, BTW :)
>
> Did you load the pci64.bin firmware with maxiinit?
Maxinit don't have problems. When you release the firmware loader, I
haved 2 strange responses, but isis works. Now I have 0 strange responses.
Thank you again, Pieter.
Felipe.
PD: Other question: capture from your driver don't work because Maestro
driver from Alsa don't do it?
(Is this an extra problem for you?)
>
> Pieter
>
>
>
> Felipe Sologuren wrote:
>
> > I tried with both kernels and alsa recompiled.
> > I'll try tomorrow to install gcc 3.1 for testing.
> >
> > Thank you Pieter, your work is very usefull and important.
> >
> > Felipe
> >
> >------------------------------------------------------------------------
> >
> >Linux version 2.4.20-18.1.caps (ro...@cm...) (gcc version
> 2.96 20000731 (Red Hat Linux 7.2 2.96-112.7.2)) #1 Wed Jun 4 17:29:20
> PDT 2003
> >BIOS-provided physical RAM map:
> > BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> > BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> > BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> > BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
> > BIOS-e820: 000000000fff0000 - 000000000fff8000 (ACPI data)
> > BIOS-e820: 000000000fff8000 - 0000000010000000 (ACPI NVS)
> > BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
> > BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> > BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> >0MB HIGHMEM available.
> >255MB LOWMEM available.
> >On node 0 totalpages: 65520
> >zone(0): 4096 pages.
> >zone(1): 61424 pages.
> >zone(2): 0 pages.
> >Kernel command line: ro root=/dev/hda2 hdd=ide-scsi
> >ide_setup: hdd=ide-scsi
> >Initializing CPU#0
> >Detected 950.024 MHz processor.
> >Console: colour VGA+ 80x25
> >Calibrating delay loop... 1893.99 BogoMIPS
> >Memory: 253312k/262080k available (1160k kernel code, 6336k reserved,
> 983k data, 120k init, 0k highmem)
> >Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
> >Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
> >Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> >Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
> >Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> >CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> >CPU: L2 Cache: 256K (64 bytes/line)
> >Intel machine check architecture supported.
> >Intel machine check reporting enabled on CPU#0.
> >CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
> >CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
> >CPU: AMD Athlon(tm) Processor stepping 02
> >Enabling fast FPU save and restore... done.
> >Checking 'hlt' instruction... OK.
> >POSIX conformance testing by UNIFIX
> >mtrr: v1.40 (20010327) Richard Gooch (rg...@at...)
> >mtrr: detected mtrr type: Intel
> >PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
> >PCI: Using configuration type 1
> >PCI: Probing PCI hardware
> >PCI: Using IRQ router default [1106/3074] at 00:11.0
> >isapnp: Scanning for PnP cards...
> >isapnp: No Plug & Play device found
> >Linux NET4.0 for Linux 2.4
> >Based upon Swansea University Computer Society NET3.039
> >Initializing RT netlink socket
> >apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
> >Starting kswapd
> >VFS: Disk quotas vdquot_6.5.1
> >pty: 2048 Unix98 ptys configured
> >Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT
> SHARE_IRQ SERIAL_PCI ISAPNP enabled
> >Real Time Clock Driver v1.10e
> >Floppy drive(s): fd0 is 1.44M
> >FDC 0 is a post-1991 82077
> >NET4: Frame Diverter 0.46
> >RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> >Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4
> >ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> >VP_IDE: IDE controller at PCI slot 00:11.1
> >VP_IDE: chipset revision 6
> >VP_IDE: not 100% native mode: will probe irqs later
> >VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
> > ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
> > ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
> >hda: MAXTOR 6L040J2, ATA DISK drive
> >blk: queue c0373d00, I/O limit 4095Mb (mask 0xffffffff)
> >hdc: QUANTUM FIREBALLlct10 10, ATA DISK drive
> >hdd: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive
> >blk: queue c0374164, I/O limit 4095Mb (mask 0xffffffff)
> >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >ide1 at 0x170-0x177,0x376 on irq 15
> >hda: attached ide-disk driver.
> >hda: host protected area => 1
> >hda: 78177792 sectors (40027 MB) w/1818KiB Cache, CHS=4866/255/63,
> UDMA(100)
> >hdc: attached ide-disk driver.
> >hdc: host protected area => 1
> >hdc: 20044080 sectors (10263 MB) w/418KiB Cache, CHS=19885/16/63
> >ide-floppy driver 0.99.newide
> >Partition check:
> > hda: hda1 hda2 hda3 hda4
> > hdc: [PTBL] [1247/255/63] hdc1
> >ide-floppy driver 0.99.newide
> >md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> >md: Autodetecting RAID arrays.
> >md: autorun ...
> >md: ... autorun DONE.
> >NET4: Linux TCP/IP 1.0 for NET4.0
> >IP Protocols: ICMP, UDP, TCP, IGMP
> >IP: routing cache hash table of 2048 buckets, 16Kbytes
> >TCP: Hash tables configured (established 16384 bind 32768)
> >Linux IP multicast router 0.06 plus PIM-SM
> >NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> >RAMDISK: Compressed image found at block 0
> >Freeing initrd memory: 120k freed
> >VFS: Mounted root (ext2 filesystem).
> >Journalled Block Device driver loaded
> >kjournald starting. Commit interval 5 seconds
> >EXT3-fs: mounted filesystem with ordered data mode.
> >Freeing unused kernel memory: 120k freed
> >Adding Swap: 522104k swap-space (priority -1)
> >EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
> >kjournald starting. Commit interval 5 seconds
> >EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,4), internal journal
> >EXT3-fs: mounted filesystem with ordered data mode.
> >SCSI subsystem driver Revision: 1.00
> >hdd: attached ide-scsi driver.
> >scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> > Vendor: HL-DT-ST Model: CD-RW GCE-8400B Rev: 1.01
> > Type: CD-ROM ANSI SCSI revision: 02
> >hdd: DMA disabled
> >hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> >hdd: drive_cmd: error=0x04
> >parport0: PC-style at 0x278 [PCSPP,TRISTATE,EPP]
> >dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
> >divert: allocating divert_blk for eth0
> >eth0: Davicom DM9102 at pci00:06.0, 00:80:ad:7a:03:17, irq 10.
> > isis: loading driver built on 21:04:13 Jul 27 2003
> >ALSA isis.c:2632: Entering ISIS create
> >ALSA isis.c:2822: isis: loading SAM driver
> >ALSA sam9407.c:27: sam9407: Creating chip
> >ALSA sam_pcm.c:937: creating 1/2 controls
> >ALSA sam_pcm.c:975: creating 3/4 controls
> >ALSA sam_ucode.c:324: new HWDEP
> >ALSA sam_mpu401.c:305: creating MIDI controls
> >ALSA sam9407.c:121: sam9407: Creating chip done
> >ALSA sam9407.c:154: sam9407: Init chip
> >ALSA sam_io.c:345: sam9407: command 0x3 ack timeout
> >ALSA sam_io.c:345: sam9407: command 0x2 ack timeout
> >ALSA sam_mem.c:128: sam9407: transfer 192 words from address 0x0 failed
> >ALSA isis.c:2215: isis: Error creating SAM chip
> >ALSA sam9407.c:327: sam9407: devfree chip
> >ALSA sam9407.c:285: sam9407: free chip
> >ALSA sam9407.c:268: sam9407: cleanup shadows
> >Maxi Studio ISIS soundcard not found or device busy
> >PCI: Setting latency timer of device 00:11.5 to 64
> >0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4363
> Sat Apr 19 17:46:46 PDT 2003
> >Linux agpgart interface v0.99 (c) Jeff Hartmann
> >agpgart: Maximum main memory to use for agp memory: 203M
> >agpgart: Detected Via Apollo Pro KT266 chipset
> >agpgart: AGP aperture is 32M @ 0xe0000000
> >Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
> >sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
> >Uniform CD-ROM driver Revision: 3.12
> >
> >
> >------------------------------------------------------------------------
> >
> >00:00.0 Host bridge: VIA Technologies, Inc. VT8367 [KT266]
> > Subsystem: VIA Technologies, Inc.: Unknown device 0000
> > Flags: bus master, medium devsel, latency 0
> > Memory at e0000000 (32-bit, prefetchable) [size=32M]
> > Capabilities: [a0] AGP version 2.0
> > Capabilities: [c0] Power Management version 2
> >
> >00:01.0 PCI bridge: VIA Technologies, Inc. VT8367 [KT333 AGP] (prog-if
> 00 [Normal decode])
> > Flags: bus master, 66Mhz, medium devsel, latency 0
> > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> > Memory behind bridge: dde00000-dfefffff
> > Prefetchable memory behind bridge: d9c00000-ddcfffff
> > Capabilities: [80] Power Management version 2
> >
> >00:06.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet
> 100/10 MBit (rev 31)
> > Subsystem: Unknown device 3030:5032
> > Flags: bus master, medium devsel, latency 128, IRQ 10
> > I/O ports at ec00 [size=256]
> > Memory at dfffff00 (32-bit, non-prefetchable) [size=256]
> > Expansion ROM at dff80000 [disabled] [size=256K]
> > Capabilities: [50] Power Management version 2
> >
> >00:07.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E
> (rev 10)
> > Subsystem: Guillemot Corporation: Unknown device 0010
> > Flags: bus master, medium devsel, latency 128, IRQ 9
> > I/O ports at e800 [size=256]
> > Capabilities: [c0] Power Management version 2
> >
> >00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
> > Subsystem: VIA Technologies, Inc.: Unknown device 0000
> > Flags: bus master, stepping, medium devsel, latency 0
> > Capabilities: [c0] Power Management version 2
> >
> >00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus
> Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
> > Subsystem: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE
> > Flags: bus master, medium devsel, latency 32
> > I/O ports at fc00 [size=16]
> > Capabilities: [c0] Power Management version 2
> >
> >00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233
> AC97 Audio Controller (rev 10)
> > Subsystem: Avance Logic Inc.: Unknown device 4710
> > Flags: medium devsel, IRQ 9
> > I/O ports at e400 [size=256]
> > Capabilities: [c0] Power Management version 2
> >
> >01:00.0 VGA compatible controller: nVidia Corporation RIVA TNT2 Model
> 64 (rev 15) (prog-if 00 [VGA])
> > Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 11
> > Memory at de000000 (32-bit, non-prefetchable) [size=16M]
> > Memory at da000000 (32-bit, prefetchable) [size=32M]
> > Expansion ROM at dfef0000 [disabled] [size=64K]
> > Capabilities: [60] Power Management version 1
> > Capabilities: [44] AGP version 2.0
> >
> >
> >
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Isisalsa-devel mailing list
> Isi...@li...
> https://lists.sourceforge.net/lists/listinfo/isisalsa-devel
>
>
|
|
From: Pieter P. <pie...@st...> - 2003-07-29 10:12:11
|
Please don't install gcc 3.1! Upgrading to gcc 3 is something you can
easily spend a few days on.
Besides, this isn't the problem in this case.
Did you load the pci64.bin firmware with maxiinit?
Pieter
Felipe Sologuren wrote:
> I tried with both kernels and alsa recompiled.
> I'll try tomorrow to install gcc 3.1 for testing.
>
> Thank you Pieter, your work is very usefull and important.
>
> Felipe
>
>------------------------------------------------------------------------
>
>Linux version 2.4.20-18.1.caps (ro...@cm...) (gcc version
2.96 20000731 (Red Hat Linux 7.2 2.96-112.7.2)) #1 Wed Jun 4 17:29:20
PDT 2003
>BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
> BIOS-e820: 000000000fff0000 - 000000000fff8000 (ACPI data)
> BIOS-e820: 000000000fff8000 - 0000000010000000 (ACPI NVS)
> BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
>0MB HIGHMEM available.
>255MB LOWMEM available.
>On node 0 totalpages: 65520
>zone(0): 4096 pages.
>zone(1): 61424 pages.
>zone(2): 0 pages.
>Kernel command line: ro root=/dev/hda2 hdd=ide-scsi
>ide_setup: hdd=ide-scsi
>Initializing CPU#0
>Detected 950.024 MHz processor.
>Console: colour VGA+ 80x25
>Calibrating delay loop... 1893.99 BogoMIPS
>Memory: 253312k/262080k available (1160k kernel code, 6336k reserved,
983k data, 120k init, 0k highmem)
>Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
>Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
>Mount cache hash table entries: 512 (order: 0, 4096 bytes)
>Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
>Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
>CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>CPU: L2 Cache: 256K (64 bytes/line)
>Intel machine check architecture supported.
>Intel machine check reporting enabled on CPU#0.
>CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
>CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
>CPU: AMD Athlon(tm) Processor stepping 02
>Enabling fast FPU save and restore... done.
>Checking 'hlt' instruction... OK.
>POSIX conformance testing by UNIFIX
>mtrr: v1.40 (20010327) Richard Gooch (rg...@at...)
>mtrr: detected mtrr type: Intel
>PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
>PCI: Using configuration type 1
>PCI: Probing PCI hardware
>PCI: Using IRQ router default [1106/3074] at 00:11.0
>isapnp: Scanning for PnP cards...
>isapnp: No Plug & Play device found
>Linux NET4.0 for Linux 2.4
>Based upon Swansea University Computer Society NET3.039
>Initializing RT netlink socket
>apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
>Starting kswapd
>VFS: Disk quotas vdquot_6.5.1
>pty: 2048 Unix98 ptys configured
>Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI ISAPNP enabled
>Real Time Clock Driver v1.10e
>Floppy drive(s): fd0 is 1.44M
>FDC 0 is a post-1991 82077
>NET4: Frame Diverter 0.46
>RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
>Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4
>ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
>VP_IDE: IDE controller at PCI slot 00:11.1
>VP_IDE: chipset revision 6
>VP_IDE: not 100% native mode: will probe irqs later
>VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
> ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
>hda: MAXTOR 6L040J2, ATA DISK drive
>blk: queue c0373d00, I/O limit 4095Mb (mask 0xffffffff)
>hdc: QUANTUM FIREBALLlct10 10, ATA DISK drive
>hdd: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive
>blk: queue c0374164, I/O limit 4095Mb (mask 0xffffffff)
>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>ide1 at 0x170-0x177,0x376 on irq 15
>hda: attached ide-disk driver.
>hda: host protected area => 1
>hda: 78177792 sectors (40027 MB) w/1818KiB Cache, CHS=4866/255/63,
UDMA(100)
>hdc: attached ide-disk driver.
>hdc: host protected area => 1
>hdc: 20044080 sectors (10263 MB) w/418KiB Cache, CHS=19885/16/63
>ide-floppy driver 0.99.newide
>Partition check:
> hda: hda1 hda2 hda3 hda4
> hdc: [PTBL] [1247/255/63] hdc1
>ide-floppy driver 0.99.newide
>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
>md: Autodetecting RAID arrays.
>md: autorun ...
>md: ... autorun DONE.
>NET4: Linux TCP/IP 1.0 for NET4.0
>IP Protocols: ICMP, UDP, TCP, IGMP
>IP: routing cache hash table of 2048 buckets, 16Kbytes
>TCP: Hash tables configured (established 16384 bind 32768)
>Linux IP multicast router 0.06 plus PIM-SM
>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>RAMDISK: Compressed image found at block 0
>Freeing initrd memory: 120k freed
>VFS: Mounted root (ext2 filesystem).
>Journalled Block Device driver loaded
>kjournald starting. Commit interval 5 seconds
>EXT3-fs: mounted filesystem with ordered data mode.
>Freeing unused kernel memory: 120k freed
>Adding Swap: 522104k swap-space (priority -1)
>EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
>kjournald starting. Commit interval 5 seconds
>EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,4), internal journal
>EXT3-fs: mounted filesystem with ordered data mode.
>SCSI subsystem driver Revision: 1.00
>hdd: attached ide-scsi driver.
>scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: HL-DT-ST Model: CD-RW GCE-8400B Rev: 1.01
> Type: CD-ROM ANSI SCSI revision: 02
>hdd: DMA disabled
>hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>hdd: drive_cmd: error=0x04
>parport0: PC-style at 0x278 [PCSPP,TRISTATE,EPP]
>dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
>divert: allocating divert_blk for eth0
>eth0: Davicom DM9102 at pci00:06.0, 00:80:ad:7a:03:17, irq 10.
> isis: loading driver built on 21:04:13 Jul 27 2003
>ALSA isis.c:2632: Entering ISIS create
>ALSA isis.c:2822: isis: loading SAM driver
>ALSA sam9407.c:27: sam9407: Creating chip
>ALSA sam_pcm.c:937: creating 1/2 controls
>ALSA sam_pcm.c:975: creating 3/4 controls
>ALSA sam_ucode.c:324: new HWDEP
>ALSA sam_mpu401.c:305: creating MIDI controls
>ALSA sam9407.c:121: sam9407: Creating chip done
>ALSA sam9407.c:154: sam9407: Init chip
>ALSA sam_io.c:345: sam9407: command 0x3 ack timeout
>ALSA sam_io.c:345: sam9407: command 0x2 ack timeout
>ALSA sam_mem.c:128: sam9407: transfer 192 words from address 0x0 failed
>ALSA isis.c:2215: isis: Error creating SAM chip
>ALSA sam9407.c:327: sam9407: devfree chip
>ALSA sam9407.c:285: sam9407: free chip
>ALSA sam9407.c:268: sam9407: cleanup shadows
>Maxi Studio ISIS soundcard not found or device busy
>PCI: Setting latency timer of device 00:11.5 to 64
>0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4363
Sat Apr 19 17:46:46 PDT 2003
>Linux agpgart interface v0.99 (c) Jeff Hartmann
>agpgart: Maximum main memory to use for agp memory: 203M
>agpgart: Detected Via Apollo Pro KT266 chipset
>agpgart: AGP aperture is 32M @ 0xe0000000
>Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
>sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
>Uniform CD-ROM driver Revision: 3.12
>
>
>------------------------------------------------------------------------
>
>00:00.0 Host bridge: VIA Technologies, Inc. VT8367 [KT266]
> Subsystem: VIA Technologies, Inc.: Unknown device 0000
> Flags: bus master, medium devsel, latency 0
> Memory at e0000000 (32-bit, prefetchable) [size=32M]
> Capabilities: [a0] AGP version 2.0
> Capabilities: [c0] Power Management version 2
>
>00:01.0 PCI bridge: VIA Technologies, Inc. VT8367 [KT333 AGP] (prog-if
00 [Normal decode])
> Flags: bus master, 66Mhz, medium devsel, latency 0
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> Memory behind bridge: dde00000-dfefffff
> Prefetchable memory behind bridge: d9c00000-ddcfffff
> Capabilities: [80] Power Management version 2
>
>00:06.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet
100/10 MBit (rev 31)
> Subsystem: Unknown device 3030:5032
> Flags: bus master, medium devsel, latency 128, IRQ 10
> I/O ports at ec00 [size=256]
> Memory at dfffff00 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at dff80000 [disabled] [size=256K]
> Capabilities: [50] Power Management version 2
>
>00:07.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E
(rev 10)
> Subsystem: Guillemot Corporation: Unknown device 0010
> Flags: bus master, medium devsel, latency 128, IRQ 9
> I/O ports at e800 [size=256]
> Capabilities: [c0] Power Management version 2
>
>00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
> Subsystem: VIA Technologies, Inc.: Unknown device 0000
> Flags: bus master, stepping, medium devsel, latency 0
> Capabilities: [c0] Power Management version 2
>
>00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus
Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
> Subsystem: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE
> Flags: bus master, medium devsel, latency 32
> I/O ports at fc00 [size=16]
> Capabilities: [c0] Power Management version 2
>
>00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233
AC97 Audio Controller (rev 10)
> Subsystem: Avance Logic Inc.: Unknown device 4710
> Flags: medium devsel, IRQ 9
> I/O ports at e400 [size=256]
> Capabilities: [c0] Power Management version 2
>
>01:00.0 VGA compatible controller: nVidia Corporation RIVA TNT2 Model
64 (rev 15) (prog-if 00 [VGA])
> Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 11
> Memory at de000000 (32-bit, non-prefetchable) [size=16M]
> Memory at da000000 (32-bit, prefetchable) [size=32M]
> Expansion ROM at dfef0000 [disabled] [size=64K]
> Capabilities: [60] Power Management version 1
> Capabilities: [44] AGP version 2.0
>
>
>
|
|
From: Felipe S. <sol...@es...> - 2003-07-28 01:34:13
|
I tried with both kernels and alsa recompiled. I'll try tomorrow to install gcc 3.1 for testing. Thank you Pieter, your work is very usefull and important. Felipe |
|
From: Pieter P. <pie...@st...> - 2003-07-27 21:16:47
|
Hi all, I have corrected the compilation problems of Felipe. The new version at sourceforge.net should compile with gcc2.96. I have also added preliminary MIDI support to the driver: - The MIDI connectors on the breakout box are (by hardware) connected to the Maestro MIDI port. This port is also available on the joystick connector. The ALSA device name for the maestro MIDI device is "Maxi Studio ISIS MPU-401 (Maestro)". This midi port was already supported in the previous driver release. - The SAM device contains two MIDI devices: "Maxi Studio ISIS SAM Synth" and "Maxi Studio ISIS SAM MIDI". The first is the internal wavetable synthesiser of the SAM chip. The second is the MIDI port of the SAM chip. Note that these new midi devices aren't very usefull for now: - I still have to write a method to upload soundbanks into the SAM memory, so the synth is pretty much useless (for now). But the soundbank stuff is so damn complicated... - The SAM midi port isn't connected to anything on the ISIS PCB. So why support it you may ask... well: first of all it wasn't difficult to support it, because it's usage almost identical to the internal synth usage. And second, I plan to modify my ISIS PCB to connect the SAM midi port to the breakout box connectors. That way I'll have two midi ports available on the ISIS: one on the breakout box (=SAM midi port) and one on the joystick port (=maestro midi port). The modification is pretty simple... I wonder why the guys at guillemot didn't do it this way... probably because writing a driver would be more difficult. Don't expect these things to work yet, because I can't test them for the moment. I won't be able to work on the driver from July 30 to Aug 20 because I'm working (actually earning some money). After that, I'll have to apply for a PhD scolarship, and I don't know how much time that is going to consume. Probably a lot. From 3sept to 26sept I'm off to Mexico... So I guess the project is pretty much suspended until end september. I'm sorry. Maybe there is someone else who has some basic expierience with ALSA & linux drivers that can help me out? Anyway, try the new driver, http://prdownloads.sourceforge.net/isisalsa/alsa-driver-0.9.5-isis-1.tar.bz2?download Pieter Pieter Palmers wrote: > Felipe Sologuren wrote: > >> Pieter Palmers wrote: >> > Hi Felipe, >> > >> > This looks like a compiler problem. Or an include file that isn't >> present. >> > >> > First of all: what distribution do you use? and what version of gcc? >> >> I'm using RH 7.3 and gcc 2.96 >> I have alsa-kernel from planet-ccrma 2.4.21.1-II.acpi, but yesterday I >> tried with 2.4.20-18.1.caps too and results was the same. >> Before your release I was using alsa 0.9.4 from planet and the >> via card >> for trying with jack-ardour. It was uninstalling with synaptic. >> Today, I'am trying without via82xx onboard from bios. I don't >> know if >> that is important, but maybe a hardware conflict... acpi yet... > > > > Possibly the problem arises from the gcc version you use. I use Redhat > 8.0 which comes with gcc version >3. There are some differences > between the 2.x and 3.x versions of gcc. I haven't tested with gcc 2.96. > I'll try and figure out the problems (& solutions) as soon as possible. > > Pieter > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > > _______________________________________________ > Isisalsa-devel mailing list > Isi...@li... > https://lists.sourceforge.net/lists/listinfo/isisalsa-devel > |
|
From: Pieter P. <pie...@st...> - 2003-07-27 19:57:47
|
Felipe Sologuren wrote: > Pieter Palmers wrote: > > Hi Felipe, > > > > This looks like a compiler problem. Or an include file that isn't > present. > > > > First of all: what distribution do you use? and what version of gcc? > > I'm using RH 7.3 and gcc 2.96 > I have alsa-kernel from planet-ccrma 2.4.21.1-II.acpi, but yesterday I > tried with 2.4.20-18.1.caps too and results was the same. > Before your release I was using alsa 0.9.4 from planet and the via > card > for trying with jack-ardour. It was uninstalling with synaptic. > Today, I'am trying without via82xx onboard from bios. I don't know if > that is important, but maybe a hardware conflict... acpi yet... Possibly the problem arises from the gcc version you use. I use Redhat 8.0 which comes with gcc version >3. There are some differences between the 2.x and 3.x versions of gcc. I haven't tested with gcc 2.96. I'll try and figure out the problems (& solutions) as soon as possible. Pieter |
|
From: Felipe S. <sol...@es...> - 2003-07-27 19:34:35
|
Pieter Palmers wrote: > Hi Felipe, > > This looks like a compiler problem. Or an include file that isn't present. > > First of all: what distribution do you use? and what version of gcc? I'm using RH 7.3 and gcc 2.96 I have alsa-kernel from planet-ccrma 2.4.21.1-II.acpi, but yesterday I tried with 2.4.20-18.1.caps too and results was the same. Before your release I was using alsa 0.9.4 from planet and the via card for trying with jack-ardour. It was uninstalling with synaptic. Today, I'am trying without via82xx onboard from bios. I don't know if that is important, but maybe a hardware conflict... acpi yet... > > Second: make sure that the directory alsa-driver-0.9.5-isis/include > contains a symbolic link named sam9407.h that points to the file > alsa-driver-0.9.5-isis/pci/isisalsa/sam9407.h > This link should be present in the package, but it could be lost during > untarring. The file is ok. After untarring again and looks the symbolic link both archives looks fine. > > I do find it a very strange error. I'll look into it. > > Pieter > >> >> Pieter: >> I can't compile the driver. >> I can do './configure' but with 'make' in the 'pci/isisalsa' > > >> subdirectory report an error: >> >> make[2]: Cambiando a directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' >> make[2]: Saliendo directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' >> make -C isisalsa modules >> make[2]: Cambiando a directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' >> gcc -D__KERNEL__ -DMODULE=1 >> -I/installers/AUDIO/alsa-driver-0.9.5-isis/include >> -I/usr/src/linux-2.4.20-18.1.caps/include -O2 >> -mpreferred-stack-boundary=2 -march=athlon -DLINUX -Wall >> -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 >> -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD >> -DKBUILD_BASENAME=isis -c -o isis.o isis.c >> isis.c: In function `isis_sam_read_control': >> isis.c:611: parse error before `data' >> isis.c:615: `data' undeclared (first use in this function) >> isis.c:615: (Each undeclared identifier is reported only once >> isis.c:615: for each function it appears in.) >> isis.c:616: warning: control reaches end of non-void function >> isis.c: In function `isis_sam_read_data8': >> isis.c:640: parse error before `data' >> isis.c:644: `data' undeclared (first use in this function) >> isis.c:645: warning: control reaches end of non-void function >> isis.c: In function `isis_sam_read_data16': >> isis.c:668: parse error before `data' >> isis.c:672: `data' undeclared (first use in this function) >> isis.c:673: warning: control reaches end of non-void function >> isis.c: In function `isis_sam_init': >> isis.c:728: parse error before `*' >> isis.c:731: `isis' undeclared (first use in this function) >> isis.c: In function `snd_isis_init_dmabuf': >> isis.c:1678: warning: passing arg 4 of >> `snd_malloc_pci_pages_fallback_R9e9124ec' from incompatible pointer type >> isis.c: In function `snd_isis_interrupt': >> isis.c:2131: parse error before `unsigned' >> isis.c:2151: `flags' undeclared (first use in this function) >> isis.c: In function `snd_isis_mixer': >> isis.c:2241: warning: passing arg 1 of `snd_ctl_new1_R11a21821' discards >> qualifiers from pointer target type >> isis.c: At top level: >> isis_mixer.h:60: warning: `isis_set_volume_monitor' defined but not used >> make[2]: *** [isis.o] Error 1 >> make[2]: Saliendo directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' >> make[1]: *** [_modsubdir_isisalsa] Error 2 >> make[1]: Saliendo directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci' >> make: *** [compile] Error 1 >> >> I don't know if this error is a problem of the driver but I search >> the >> line of isis.c where 'isis_sam_read_data' appears and it is in a >> section called 'no spinlock' :( >> > > > > |
|
From: Felipe S. <sol...@es...> - 2003-07-27 18:23:23
|
Pieter Palmers wrote: > Hi Felipe, > > This looks like a compiler problem. Or an include file that isn't present. > > First of all: what distribution do you use? and what version of gcc? I'm using RH 7.3 and gcc 2.96 I have alsa-kernel from planet-ccrma 2.4.21.1-II.acpi, but yesterday I tried with 2.4.20-18.1.caps too and results was the same. Before your release I was using alsa 0.9.4 from planet and the via card for trying with jack-ardour. It was uninstalling with synaptic. Today, I'am trying without via82xx onboard from bios. I don't know if that is important, but maybe a hardware conflict... acpi yet... > > Second: make sure that the directory alsa-driver-0.9.5-isis/include > contains a symbolic link named sam9407.h that points to the file > alsa-driver-0.9.5-isis/pci/isisalsa/sam9407.h > This link should be present in the package, but it could be lost during > untarring. The file is ok. After downloading, untarring again and looks the symbolic link both archives looks fine. > > I do find it a very strange error. I'll look into it. > > Pieter > >> >> Pieter: >> I can't compile the driver. >> I can do './configure' but with 'make' in the 'pci/isisalsa' > > >> subdirectory report an error: >> >> make[2]: Cambiando a directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' >> make[2]: Saliendo directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' >> make -C isisalsa modules >> make[2]: Cambiando a directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' >> gcc -D__KERNEL__ -DMODULE=1 >> -I/installers/AUDIO/alsa-driver-0.9.5-isis/include >> -I/usr/src/linux-2.4.20-18.1.caps/include -O2 >> -mpreferred-stack-boundary=2 -march=athlon -DLINUX -Wall >> -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 >> -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD >> -DKBUILD_BASENAME=isis -c -o isis.o isis.c >> isis.c: In function `isis_sam_read_control': >> isis.c:611: parse error before `data' >> isis.c:615: `data' undeclared (first use in this function) >> isis.c:615: (Each undeclared identifier is reported only once >> isis.c:615: for each function it appears in.) >> isis.c:616: warning: control reaches end of non-void function >> isis.c: In function `isis_sam_read_data8': >> isis.c:640: parse error before `data' >> isis.c:644: `data' undeclared (first use in this function) >> isis.c:645: warning: control reaches end of non-void function >> isis.c: In function `isis_sam_read_data16': >> isis.c:668: parse error before `data' >> isis.c:672: `data' undeclared (first use in this function) >> isis.c:673: warning: control reaches end of non-void function >> isis.c: In function `isis_sam_init': >> isis.c:728: parse error before `*' >> isis.c:731: `isis' undeclared (first use in this function) >> isis.c: In function `snd_isis_init_dmabuf': >> isis.c:1678: warning: passing arg 4 of >> `snd_malloc_pci_pages_fallback_R9e9124ec' from incompatible pointer type >> isis.c: In function `snd_isis_interrupt': >> isis.c:2131: parse error before `unsigned' >> isis.c:2151: `flags' undeclared (first use in this function) >> isis.c: In function `snd_isis_mixer': >> isis.c:2241: warning: passing arg 1 of `snd_ctl_new1_R11a21821' discards >> qualifiers from pointer target type >> isis.c: At top level: >> isis_mixer.h:60: warning: `isis_set_volume_monitor' defined but not used >> make[2]: *** [isis.o] Error 1 >> make[2]: Saliendo directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' >> make[1]: *** [_modsubdir_isisalsa] Error 2 >> make[1]: Saliendo directorio >> `/installers/AUDIO/alsa-driver-0.9.5-isis/pci' >> make: *** [compile] Error 1 >> >> I don't know if this error is a problem of the driver but I search >> the >> line of isis.c where 'isis_sam_read_data' appears and it is in a >> section called 'no spinlock' :( >> > > > > |
|
From: Pieter P. <pie...@st...> - 2003-07-27 09:27:32
|
Hi Felipe, This looks like a compiler problem. Or an include file that isn't present. First of all: what distribution do you use? and what version of gcc? Second: make sure that the directory alsa-driver-0.9.5-isis/include contains a symbolic link named sam9407.h that points to the file alsa-driver-0.9.5-isis/pci/isisalsa/sam9407.h This link should be present in the package, but it could be lost during untarring. I do find it a very strange error. I'll look into it. Pieter > > Pieter: > I can't compile the driver. > I can do './configure' but with 'make' in the 'pci/isisalsa' > subdirectory report an error: > > make[2]: Cambiando a directorio > `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' > make[2]: Saliendo directorio > `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' > make -C isisalsa modules > make[2]: Cambiando a directorio > `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' > gcc -D__KERNEL__ -DMODULE=1 > -I/installers/AUDIO/alsa-driver-0.9.5-isis/include > -I/usr/src/linux-2.4.20-18.1.caps/include -O2 > -mpreferred-stack-boundary=2 -march=athlon -DLINUX -Wall > -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 > -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD > -DKBUILD_BASENAME=isis -c -o isis.o isis.c > isis.c: In function `isis_sam_read_control': > isis.c:611: parse error before `data' > isis.c:615: `data' undeclared (first use in this function) > isis.c:615: (Each undeclared identifier is reported only once > isis.c:615: for each function it appears in.) > isis.c:616: warning: control reaches end of non-void function > isis.c: In function `isis_sam_read_data8': > isis.c:640: parse error before `data' > isis.c:644: `data' undeclared (first use in this function) > isis.c:645: warning: control reaches end of non-void function > isis.c: In function `isis_sam_read_data16': > isis.c:668: parse error before `data' > isis.c:672: `data' undeclared (first use in this function) > isis.c:673: warning: control reaches end of non-void function > isis.c: In function `isis_sam_init': > isis.c:728: parse error before `*' > isis.c:731: `isis' undeclared (first use in this function) > isis.c: In function `snd_isis_init_dmabuf': > isis.c:1678: warning: passing arg 4 of > `snd_malloc_pci_pages_fallback_R9e9124ec' from incompatible pointer type > isis.c: In function `snd_isis_interrupt': > isis.c:2131: parse error before `unsigned' > isis.c:2151: `flags' undeclared (first use in this function) > isis.c: In function `snd_isis_mixer': > isis.c:2241: warning: passing arg 1 of `snd_ctl_new1_R11a21821' discards > qualifiers from pointer target type > isis.c: At top level: > isis_mixer.h:60: warning: `isis_set_volume_monitor' defined but not used > make[2]: *** [isis.o] Error 1 > make[2]: Saliendo directorio > `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' > make[1]: *** [_modsubdir_isisalsa] Error 2 > make[1]: Saliendo directorio > `/installers/AUDIO/alsa-driver-0.9.5-isis/pci' > make: *** [compile] Error 1 > > I don't know if this error is a problem of the driver but I search > the > line of isis.c where 'isis_sam_read_data' appears and it is in a > section called 'no spinlock' :( > |
|
From: Pieter P. <pie...@st...> - 2003-07-27 09:14:49
|
Adrian Prantl wrote:
>On Saturday 26 July 2003 15:28, Pieter Palmers wrote:
>
>
>>I personally experience some problems which I cannot pinpoint an origin
>>for. I guess they originate in a spinlock problem.
>>
>>The major tests you should perform are:
>>1) try using both SAM pcm channels (hw:?,1 & hw:?,2) at the same time,
>>for a longer duration (e.g. 2 alsaplayers with a long playlist)
>>
>>
>that seems to work fine.
>
>
>
OK
>>2) try using the maestro pcm (hw:?,0) in addition to point 1. This
>>should mess things up
>>
>>
>it certainly does.. the current buffer seems to be played in an endless loop
>even if I kill all alsaplayers.
>hmm. when I then try to find the ill-behaving channel with alsamixer my whole
>system responds really slow, too.
>
>
That's what I thought... This will be solved in the rewrite.
>
>
>>3) try starting & stopping a program several times, while other pcm
>>channels are playing, with different fragment sizes, etc... I have the
>>impression that once you open a channel with a specified fragment size,
>>and then close it, you can't use another fragment size on a subsequent
>>open of the channel.
>>
>>
>see above.
>
where?
>>jackd should be a nice test too.
>>
>>
>
>For "isis" beeing defined as
>pcm.isis {
> type hw
> card 1
>}
>ctl.isis {
> type hw
> card 1
>}
>
>-------------------------
>adrian@vicviper:~$ /usr/local/bin/jackd -d alsa -d isis
>jackd 0.74.1
>Copyright 2001-2003 Paul Davis and others.
>jackd comes with ABSOLUTELY NO WARRANTY
>This is free software, and you are welcome to redistribute it
>under certain conditions; see the file COPYING for details
>
>JACK compiled with System V SHM support
>loading driver ..
>creating alsa driver ... isis|isis|1024|2|48000|nomon|swmeter|rt
>open
>ALSA: the playback and capture components for this PCM device differ in their
>use of channel interleaving. We cannot use this PCM device.
>starting engine
>engine driver not set; cannot start
>cannot start main JACK thread
>jack main caught signal 15
>-------------------------
>hmmm..
>
This is because Jack needs capture as well as playback, and the current
ISIS driver doesn't implement capture yet. But I think there is an
option to jack to force it not to use the capture port:
" -P, --playback
Provide only playback ports."
This seems to work, provided you use only SAM pcm devices in .asoundrc
Pieter
|
|
From: Felipe S. <sol...@es...> - 2003-07-27 03:48:58
|
-------- Original Message -------- Subject: Re: [Isisalsa-devel] First driver release Date: Sat, 26 Jul 2003 20:50:17 -0400 From: Felipe Sologuren <sol...@es...> To: Pieter Palmers <pie...@st...> References: <3F2...@st...> Pieter Palmers wrote: > Good news: I've finally succeeded in completing a beta version of the > ISIS driver. It's only functional with the pci64.bin firmware (i.e. > multimedia mode, not studio). > Everything works, except recording from the rack (not possible with > windows drivers either in MM mode) and the MIDI synthesizer doesn't work > either. > > There are some bugs in the driver, for sure. Please let me know what & > how it occurred. > > Installation: > 1) download the file alsa-driver-0.9.5-isis.tar.bz2 from the sourceforge > project page (http://www.sourceforge.net/projects/isisalsa) > this file is a modified version of the ALSA 0.9.5 driver package. You'll > also need the other ALSA driver files, available at www.alsa-project.org. > 2) unpack it, and follow the procedure outlined in the ALSA docs for > installation > 3) use maxiinit to load the pci64.bin firmware to the card (e.g. > maxiinit /etc/isis/pci64.bin) > 4) load the isis driver: (as root) "modprobe snd-isis" > > it should work. If it doesnt, please send me the output of the kernel > log ("dmesg") and the PCI configuration ("lspci -v"), and a description > of the problem, so I can try and figure out the problem. > > Device info: > pcm device 0 = ESS Maestro PCM (Playback & Capture) > pcm device 1 = SAM 1/2 PCM (mixed with Maestro PCM by firmware) > (Playback only) > pcm device 2 = SAM 3/4 PCM (Playback only) > > Midi should also work > Joystick also > > Enjoy, > > Pieter > > PS: I'm working on the Studio mode driver, but that mode is even less > documented. Could be a while before I get this straigt. > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Isisalsa-devel mailing list > Isi...@li... > https://lists.sourceforge.net/lists/listinfo/isisalsa-devel > > Pieter: I can't compile the driver. I can do './configure' but with 'make' in the 'pci/isisalsa' subdirectory report an error: make[2]: Cambiando a directorio `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' make[2]: Saliendo directorio `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/ice1712' make -C isisalsa modules make[2]: Cambiando a directorio `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' gcc -D__KERNEL__ -DMODULE=1 -I/installers/AUDIO/alsa-driver-0.9.5-isis/include -I/usr/src/linux-2.4.20-18.1.caps/include -O2 -mpreferred-stack-boundary=2 -march=athlon -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -DKBUILD_BASENAME=isis -c -o isis.o isis.c isis.c: In function `isis_sam_read_control': isis.c:611: parse error before `data' isis.c:615: `data' undeclared (first use in this function) isis.c:615: (Each undeclared identifier is reported only once isis.c:615: for each function it appears in.) isis.c:616: warning: control reaches end of non-void function isis.c: In function `isis_sam_read_data8': isis.c:640: parse error before `data' isis.c:644: `data' undeclared (first use in this function) isis.c:645: warning: control reaches end of non-void function isis.c: In function `isis_sam_read_data16': isis.c:668: parse error before `data' isis.c:672: `data' undeclared (first use in this function) isis.c:673: warning: control reaches end of non-void function isis.c: In function `isis_sam_init': isis.c:728: parse error before `*' isis.c:731: `isis' undeclared (first use in this function) isis.c: In function `snd_isis_init_dmabuf': isis.c:1678: warning: passing arg 4 of `snd_malloc_pci_pages_fallback_R9e9124ec' from incompatible pointer type isis.c: In function `snd_isis_interrupt': isis.c:2131: parse error before `unsigned' isis.c:2151: `flags' undeclared (first use in this function) isis.c: In function `snd_isis_mixer': isis.c:2241: warning: passing arg 1 of `snd_ctl_new1_R11a21821' discards qualifiers from pointer target type isis.c: At top level: isis_mixer.h:60: warning: `isis_set_volume_monitor' defined but not used make[2]: *** [isis.o] Error 1 make[2]: Saliendo directorio `/installers/AUDIO/alsa-driver-0.9.5-isis/pci/isisalsa' make[1]: *** [_modsubdir_isisalsa] Error 2 make[1]: Saliendo directorio `/installers/AUDIO/alsa-driver-0.9.5-isis/pci' make: *** [compile] Error 1 I don't know if this error is a problem of the driver but I search the line of isis.c where 'isis_sam_read_data' appears and it is in a section called 'no spinlock' :( |
3 messages has been excluded from this view by a project administrator.
