Opened 7 weeks ago

Last modified 5 weeks ago

#19272 new bug

Regression: Creative Sound Blaster Live does not work anymore

Reported by: bruno Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Audio/emuxki Version: R1/beta5
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by korli)

Maybe starting with hrev57101 the media_add_on server will crash imediatelly on boot or start! So no Sound! No media add ons in Cortex shown

It was working before Beta 5!

I tried with UEFI/Framebuffer and VESA (maybe not important!)

Attachments (14)

media_addon_server-840-debug-30-11-2024-18-42-21.report (17.7 KB ) - added by bruno 7 weeks ago.
First media add on crash report
syslog.old (512.0 KB ) - added by bruno 7 weeks ago.
syslog of hrev 57101
syslog hrev57114 (466.4 KB ) - added by bruno 7 weeks ago.
Syslog hrev57114 sound works!
syslog58371_8637_1 (431.7 KB ) - added by bruno 7 weeks ago.
media_addon_server-200-debug-03-12-2024-15-51-37.report (13.6 KB ) - added by bruno 7 weeks ago.
Walter media_adon_server crash report
walter.png (83.6 KB ) - added by bruno 7 weeks ago.
cortex
cortex.png (50.6 KB ) - added by bruno 7 weeks ago.
Cortex app
syslog57704 (175.0 KB ) - added by bruno 7 weeks ago.
syslog from blank fresh working(audio) install 57704
syslogBETA5 (198.3 KB ) - added by bruno 7 weeks ago.
syslog after working (audio) 57704 upgrade to 58375 with working audio!?
syslog58375 (147.3 KB ) - added by bruno 7 weeks ago.
syslog from 58375 audio suddently not working anymore (I booted in meantime to another HAIKU install on Hardware
media_addon_server-206-debug-04-12-2024-16-28-06.report (13.2 KB ) - added by bruno 7 weeks ago.
again meeting the media crash file
media (453.7 KB ) - added by bruno 6 weeks ago.
Non-packed used folders (correct use?)
non_packaged.png (165.6 KB ) - added by bruno 6 weeks ago.
Files and media folder copied to non-packaged folders from new hrev58385!
volume.png (1.9 KB ) - added by bruno 5 weeks ago.
reversed volume-meter red to green negative values!

Change History (46)

by bruno, 7 weeks ago

First media add on crash report

by bruno, 7 weeks ago

Attachment: syslog.old added

syslog of hrev 57101

comment:1 by bruno, 7 weeks ago

Description: modified (diff)

comment:2 by bruno, 7 weeks ago

Description: modified (diff)

comment:3 by waddlesplash, 7 weeks ago

Did you test with a recent nightly?

comment:4 by korli, 7 weeks ago

Description: modified (diff)

in reply to:  3 comment:5 by bruno, 7 weeks ago

Replying to waddlesplash:

Did you test with a recent nightly?

yes, I always use the latest nightly! Now hrev58357

comment:6 by bruno, 7 weeks ago

Today I tried hrev57114 and it worked!

by bruno, 7 weeks ago

Attachment: syslog hrev57114 added

Syslog hrev57114 sound works!

comment:7 by waddlesplash, 7 weeks ago

Component: Audio & VideoDrivers/Audio/emuxki

comment:9 by bruno, 7 weeks ago

Still with Walterhrev58371_8637_1 it will crash media_add_on server immediatelly at first boot and at every start ! However if I use Cortex and try to plug into the second input au1 it will crash? Maybe related, maybe not!

Do you need the syslog the media_addon_server crash report or something else? Should I try hrev57704 now?

Last edited 7 weeks ago by bruno (previous) (diff)

by bruno, 7 weeks ago

Attachment: syslog58371_8637_1 added

by bruno, 7 weeks ago

Walter media_adon_server crash report

by bruno, 7 weeks ago

Attachment: walter.png added

cortex

by bruno, 7 weeks ago

Attachment: cortex.png added

Cortex app

comment:10 by bruno, 7 weeks ago

Walter Desktop with Media preferences window 2.0 4.0 and 5.1 audio mode cortex Cortex app with crash trying to attach to au1 Cortex app

comment:12 by bruno, 7 weeks ago

Just tried it... At first boot the media_addon_server did not crash! After switching to Emuxki SB Live it was crashing at second boot up, and still no sound or audio.

Last working was still hrev57114

Need Syslog or media_addon_server crash report?

comment:13 by bruno, 7 weeks ago

just tried hrev57704 and it worked just fine! syslog?

comment:14 by bruno, 7 weeks ago

I just tried to upgrade from hrev57704 to hrev58375 and it is working! What happened here? It is working now! So how to get my other beta5 install to work too? Use installer only?

I will try to boot in some more time to be sure...

Last edited 7 weeks ago by bruno (previous) (diff)

comment:15 by bruno, 7 weeks ago

After booting into another Haiku install on hardware. I started the upgrade again and it is not working as before! So strange! At least I have the syslogs to compare. But which one might be most important?

by bruno, 7 weeks ago

Attachment: syslog57704 added

syslog from blank fresh working(audio) install 57704

by bruno, 7 weeks ago

Attachment: syslogBETA5 added

syslog after working (audio) 57704 upgrade to 58375 with working audio!?

by bruno, 7 weeks ago

Attachment: syslog58375 added

syslog from 58375 audio suddently not working anymore (I booted in meantime to another HAIKU install on Hardware

by bruno, 7 weeks ago

again meeting the media crash file

comment:16 by bruno, 7 weeks ago

Fresh hrev57705 USB-Stick (audio) works too!

comment:17 by korli, 7 weeks ago

You could try to copy a working driver on a current nightly to see whether it still works.

comment:18 by bruno, 7 weeks ago

That would be too easy.

I cannot copy to the system folder so it is (Emuxki) now in: /boot/home/config/non-packaged/add-ons/kernel/drivers/bin

It does not help!

Edit: Maybe I missed some settings file or that kind? Edit 2: I copied the one too: /boot/home/config/non-packaged/add-ons/kernel/drivers/dev/audio/hmulti

It is not the driver, it could be something else?

Last edited 7 weeks ago by bruno (previous) (diff)

comment:19 by korli, 7 weeks ago

/boot/system/non-packaged/add-ons/kernel/drivers/bin would be preferred. You mean old and new driver behave the same on a nightly? Some asserts have been added in the media add-on, which might trigger the behavior.

comment:20 by bruno, 6 weeks ago

The driver looks and feels as nothing has changed, yes The problem is with media add-on I think!

If there is no media add-on crash the sound will work! If there is a crash at boot the sound will not work!

Strange that the hrev57704 worked in live mode and even after installing it to the bigger partition on the USB-Stick and it worked even two times after updating with SoftwareUpdater! Then suddenly no more! Restarting the Audio preferences showed no effect at all! The sound bars working but no audio!

comment:21 by korli, 6 weeks ago

You could try to copy a working multiaudio.media-addon on a current nightly to see whether it still works.

comment:22 by bruno, 6 weeks ago

I tried to copy some media-addons and even the media_addon_server to the non-packaged/server but I am not sure I am doing it right! I need your guidance there which file to move to which location! The system non-packaged folder or the home non-packaged folder? I think it does not matter which!? But which files? If I restart media, the system will boot the one found in system it seems!? boot/system/servers/media_addon_server that is where I got the crash report from! I do not need to blacklist the audio driver in system folder! Sorry I am very confused now, but I think it is a good way you found here!

by bruno, 6 weeks ago

Attachment: media added

Non-packed used folders (correct use?)

comment:23 by bruno, 6 weeks ago

I tried to make use of the non-packaged folders! Is it correct? Should it work that way? Thanks. Non-packed used folders (correct use?)

comment:24 by bruno, 6 weeks ago

I just tried to install "Telegram" on the audio-working hrev57704 and after restart I have no sound there now!° So Telegram or its dependencies are the problem here! But which one?

Edit: Do you agree?

Last edited 6 weeks ago by bruno (previous) (diff)

comment:25 by bruno, 6 weeks ago

hrev57704 Sound working! I installed "Telegram" sound stopped working!

I copied the emuxki driver from (newest nightly) to non-packaged/add-ons/kernel/driver/bin

I copied the whole media folder from hrev58385 (newest nightly)to boot/home/config/non-packaged/add-ons/media

I copied the whole server folder to /boot/system/non-packaged/servers

Sound works again**

But WebPositive not! Anyway... hrev shows hrev58385 but still not upgraded to newest hrev!

I deinstalled ffmpeg6 Sound works I deinstalled ffmpeg5 Sound works I deinstalled ffmpeg Sound stopped working

I reinstalled all ffmpeg,5,6 sound does not work But sound works in Telegram! Then I tried a pkgman full! Sound works!

by bruno, 6 weeks ago

Attachment: non_packaged.png added

Files and media folder copied to non-packaged folders from new hrev58385!

comment:26 by bruno, 6 weeks ago

Copying media_addon files from new hrev Sound works again! About Haiku shows wrong hrev58385 (still 57704)

Files and media folder copied to non-packaged folders from new hrev58385!

comment:27 by bruno, 6 weeks ago

I did pkgman full

Now the system is fully working with the non-packaged add-ons still installed!

comment:28 by bruno, 6 weeks ago

I even got the newest nightly to play sound again. but I am not sure how!

Suspects: haiku_datatranslator ffmpeg ffmpeg5 ffmpeg6

Somehow involved: WebPositive telegram Qmplay2

Deleting haiku_datatranslators makes no more crash at boot! Installing haiku_datatranslations from Terminal works somehow! It is still very confusing!

But I got it working, so there is some way to make it constant!

comment:29 by bruno, 6 weeks ago

Restarting the media-server will result in mute, no audio! But no crash! After restart audio works!

Last edited 6 weeks ago by bruno (previous) (diff)

comment:30 by bruno, 6 weeks ago

If you disable haiku_datatranslators, media_addon_server will not crash anymore! If you then install the haiku_datatranslators by terminal, audio will work! But if you restart media-server in media preferences audio will be mute! At restart sound will work! Haiku nightly!

comment:31 by bruno, 5 weeks ago

Copying the media_addon files from new hrev to older one was working! I copied the whole media folder, so I am not sure which one was the responsible one!

comment:32 by bruno, 5 weeks ago

I just found out some strange thing I did not see until now! The volume bar is reversed and working! Left it is red and in the critical right side green! Which is reversed! If I slide the slider to the far right I get no more sound! If I move it to the left volume side, I can hear some cracklings but it works!

So that means the sound channels are somewhat reversed and maight not work correct because of this in first hand!

reversed volume-meter red to green negative values!

by bruno, 5 weeks ago

Attachment: volume.png added

reversed volume-meter red to green negative values!

Note: See TracTickets for help on using tickets.