Re: Sound Blaster Audigy Series only working in 50% of the boots

Hey,
sorry I did not mentioned it, but I tested a lot of boot parameters. Like disable acpi, pci noroute, but your option I didn't test, I will do.

Micha 

Am 14. November 2020 19:58:31 MEZ schrieb Patrick May <[email protected]>:
>Hello,
>
>I don't think this is likely to help your issue, but if you haven't 
>already, you should try booting linux with the option iommu=soft
>
>That was necessary for an issue I had with another card that uses the 
>snd-emu10k1 driver.
>
>Sorry if it doesn't help.
>
>PM
>
>On 14/11/2020 14:01, Micha wrote:
>> Hi there,
>> 
>> my soundcard works only in 50% of the boots.
>> 
>> 
>> ❯ hwinfo --sound
>> 19: PCI a00.0: 0401 Multimedia audio controller
>>    [Created at pci.386]
>>    Unique ID: cuhJ.Rgto84+swI4
>>    Parent ID: x1VA.RTygCxq_rO0
>>    SysFS ID:
>/devices/pci0000:00/0000:00:1c.6/0000:09:00.0/0000:0a:00.0
>>    SysFS BusID: 0000:0a:00.0
>>    Hardware Class: sound
>>    Model: "Creative SB1550 Audigy 5/Rx"
>>    Vendor: pci 0x1102 "Creative Labs"
>>    Device: pci 0x0008 "CA0108/CA10300 [Sound Blaster Audigy Series]"
>>    SubVendor: pci 0x1102 "Creative Labs"
>>    SubDevice: pci 0x1024 "SB1550 Audigy 5/Rx"
>>    I/O Ports: 0xd000-0xd03f (rw)
>>    IRQ: 18 (no events)
>>    Module Alias:
>"pci:v00001102d00000008sv00001102sd00001024bc04sc01i00"
>>    Driver Info #0:
>>      Driver Status: snd_emu10k1 is active
>>      Driver Activation Cmd: "modprobe snd_emu10k1"
>>    Config Status: cfg=new, avail=yes, need=no, active=unknown
>>    Attached to: #10 (PCI bridge)
>> 
>> If the card is recognised well the card works out of the box, but in
>> half of all boots the card is not recognised. For some reasons the
>card
>> didn't get an interrupt and then the card is not available in
>> /proc/asound/cards
>> 
>> 
>> working state:
>> 
>> File: /proc/interrupts
>>
>───────┼───────────────────────────────────────────────────────────────
>>
>───────────────────────────────────────────────────────────────────────
>> ────────────────────────────
>> 1 │ CPU0 CPU1 CPU2 CPU3
>> 2 │ 0: 8 0 0 0 IO-APIC 2-edge timer
>> 3 │ 8: 0 0 0 1 IO-APIC 8-edge rtc0
>> 4 │ 9: 0 0 0 0 IO-APIC 9-fasteoi acpi
>> 5 │ 16: 0 0 4 0 IO-APIC 16-fasteoi i801_smbus
>> 6 │ 18: 0 21 0 0 IO-APIC 18-fasteoi snd_emu10k1
>> 
>> 
>> In the not working state the cards get no interrupt, but the
>interrupt
>> above ( 18) in not given to another card or something
>> 
>> 
>> 442368-edge      aerdrv
>> journald meldet dann:
>> ✦ ❯ journalctl -b -g snd_emu10k1
>> -- Logs begin at Mon 2020-06-29 17:38:04 CEST, end at Mon 2020-11-02
>> 20:30:00 CET. --
>> Nov 02 18:03:14 sysiphus kernel: snd_emu10k1 0000:0a:00.0: enabling
>> device (0000 -> 0001)
>> Nov 02 18:03:14 sysiphus kernel: snd_emu10k1 0000:0a:00.0: Audigy2
>> value: Special config.
>> Nov 02 18:03:15 sysiphus kernel: snd_emu10k1 0000:0a:00.0: AC'97 0
>does
>> not respond - RESET
>> Nov 02 18:03:15 sysiphus kernel: snd_emu10k1 0000:0a:00.0: AC'97 0
>> access is not valid [0x0], removing mixer.
>> Nov 02 18:03:15 sysiphus kernel: snd_emu10k1: probe of 0000:0a:00.0
>> failed with error -5
>> 
>> Debian Sid
>> ✦ ❯ uname -a
>> Linux sysiphus 5.9.0-2-amd64 #1 SMP Debian 5.9.6-1 (2020-11-08)
>x86_64
>> GNU/Linux
>> 
>> Board is an Asus PRIME Z270-K with bios 1207.
>> 
>> I have tested the card in another pci port and also have changed the
>> card to a new one, both without success.
>> 
>> Can you please help me to debug this further? When you need
>additional
>> information, please ask and I will provide it.
>> 
>> 
>> Grüße/ regards Micha
>> 
>> 
>> _______________________________________________
>> Alsa-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/alsa-user
>> 
>
>
>_______________________________________________
>Alsa-user mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/alsa-user

_______________________________________________
Alsa-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-user