From: Jude DaShiell <jdashiel@panix.com>
To: linux-msdos@vger.kernel.org
Subject: sound for dosemu on archlinux more complex
Date: Thu, 29 Apr 2021 10:51:08 -0400 [thread overview]
Message-ID: <alpine.NEB.2.23.451.2104291039480.9452@panix1.panix.com> (raw)
The only alsa.conf file on the system is in /usr/share/alsa not
/etc/modprobe.d. In my user directory I have an .asoundrc file. These
appear different from what Dominique shared earlier.
Also I am missing an expected midi device and maybe a libao device. A
code page isn't yet present or configured either. Exit errors are:
ERROR: Can't find codepage for "C".
Please add the mapping to locales.conf and send patch.
ERROR: libao: unable to get driver id
ERROR: alsa_midi (ALSA lib): rawmidi_hw.c:235:(snd_rawmidi_hw_open) : No
such file or directory open /dev/snd/midiC0D0 failed
How can I check for a live libao driver and build both midi drivers and
libao drivers if those don't exist?
This system runs on utf-8 as most Linux systems do these days. What
should be done to cause the code page error to disappear if it is or will
be critical in future?
I had to remove a drives line from a .dosemurc I made for dosemu 1.42 and
when I did that dosemu 2 came up and surprised me. My surprise was this.
With dosemu 1, with this .dosemurc file I had a 64 line boot.log file.
With the modified .dosemurc file for dosemu 2 where that drives line got
deleted, my boot.log file was only 36 lines long. Lots of warnings with
the /etc/dosemu/dosemu.conf file which stands to reason. Good
configuration work pays.
reply other threads:[~2021-04-29 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.23.451.2104291039480.9452@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).