I tried the patch and it works great (though I can't seem to get the
other patch to work to increase the limit to 2gb for soundfonts), it's
just really inconvenient to recompile the kernel and now after initially
compiling it, it doesn't want to compile again and complains about a
signing key.
Look, what else to say? The patch is there, it has been confirmed to
work, and it still works here. See #10 on this list.
If the Ubuntu team does not want to pick it up, nor the kernel team
wants to pick it up, nothing will happen. If anyone is having a better
fix, also go along. Until then, see
More than ten years and this bug is still around and biting me.
Those SoundBlaster cards are really made to last.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2
This bug still exists and is easily reproducible in the latest version
of Ubuntu. I have a PC with 32GB of RAM and I can't load a Soundfont
bigger than 16mb with asfxload, on my PC with 2GB of RAM I can load a
600mb Soundfont without issue, this really needs to be fixed as using a
sofsynth causes
It's 2018 and this bug is still here; running 4GB ram 64bit + Live 5.1
and the effect is just like here.
I have an onboard builtin "soundcard" but the sound it produces is way
flatter and less full than the one I hear via the SB Live; may be just a
case of config; maybe there is a difference in
If you have an idea how to activate the 16MB mode for the emu10k1, then
this would be pretty helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with
Looks like audigy (and probably emu10k1 too) supports 32 bits DMA. There
are two addressing modes, where first supports 32 MB space in 2 GB
memory and 8192 pages (this is default mode). Second is 16 MB space in 4
GB and 4096 pages. I tested second one an looks like it is working
(audigy 8GB ram,
I have tried the small 2L change by Thomas Richter and it works fine,
no negative side effects so far. Apparently, the 4GB barrier was a bit
of an arbitrary value anyway, you can read about that here:
https://lwn.net/Articles/152337/
I found the memmap=2048M\\$6144M workaround proposed on
My patch will not compile and fails with:
include/linux/mmzone.h:335:2: error: #error ZONES_SHIFT -- too many
zones configured adjust calculation
Looking into this, I found in include/linux/gfp.h:
* GFP_ZONE_TABLE is a word size bitstring that is used for looking up the
* zone to use given
Another approach...
I set out to target the 2GB limit workaround to only affect the emu10k1,
and at the same time make some placeholders for code to create an
additional 31bit DMA region. Then I spent hours trying to set the right
kernel configuration for my system and gave up.
This patch is
An alternative solution to patching the kernel is to add a line to the
bootloader excluding all but 2GB of RAM whenever you're going to be using MIDI.
I got this idea from reading the forum at
http://ubuntuforums.org/showthread.php?t=1340309
and have confirmed that it works. I have 8GB of
ohhh...
this is a bit deeper than my knowledge of the linux kernel but i'm
starting to get the picture.
perhaps there is another way to get this done, without proposing major
changes to the kernel.
is it possible to add code to either the emu10k1 module or asfxload to
buffer large soundfonts?
Sorry, but I don't waste my time there. I believe I reported this
problem already several years ago, and it was basically ignored or the
patch wasn't accepted. To some degree, I understand this because it
doesn't address the *real* problem (which is the unflexibility of the
kernel memory
you better follow up this thread
http://thread.gmane.org/gmane.linux.alsa.devel/97927
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns
Raymond
I didn't understand what your post was about at first.
After looking into it, this does seem like the single line of code to
change.
From OSS (via a page so outdated it exists only in google cache):
linux/sound/oss/emu10k1/main.c
...
121 /* the emu10k1 _seems_ to only supports 29 bit
The problem is not which DMA mask the kernel assigns to the module. The
problem is what the kernel does if the memory to be accessed via the
emu10k1 DMA is *not* in range of the DMA mask. The emu10k1 reaches the
30 bit address space just fine, as my all-day experience tells me.
What the kernel
Hi Thomas,
You've previously said that the kernel hackers aren't overly willing to
put in a proper fix for this issue. I don't see an entry for this bug in
the Linux kernel bugzilla, however (https://bugzilla.kernel.org/), so
it's possible they aren't even aware of it.
Regardless of whether or
Wrote a small tutorial HOWTO setup EMU10k soundfont DSP on Ubuntu
11.10 see here: https://github.com/koppi/renoise-refcards/wiki/Howto-
setup-EMU10k-soundfont-DSP-on-Ubuntu-11.10 Feel free to edit the Wiki
page at GitHub or send me your commends.
--
You received this bug notification because you
Anyone know which file to patch for kernel 3.0.x?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns sfxload: no memory
left
To manage
refer to alsa-kernel/include/emu10k1.h
/* FIXME? - according to the OSS driver the EMU10K1 needs a 29 bit DMA mask */
#define EMU10K1_DMA_MASK0x7fffUL/* 31bit */
#define AUDIGY_DMA_MASK 0x7fffUL/* 31bit FIXME - 32 should
work? */
--
You received this bug
It most certainly does. However:
Current kernel hackers seem to prefer to work around the situation by
reverting to a timidity based software emulation of midi. It is not
exactly the same as the emu10k1 midi, and - if you ask me - is of lower
quality. Thus, at least kernel developers have a
Thomas,
In the dma.h header you've cited, I see that the MAX_DMA32_PFN
definition is commented thusly:
/* 4GB broken PCI/AGP hardware bus master zone */
#define MAX_DMA32_PFN ((4UL * 1024 * 1024 * 1024) PAGE_SHIFT)
Given that this value is intended for broken (PCI) hardware, and the
I would say so, yes. I just don't have any other concrete examples where
this might be the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload
** Changed in: awesfx (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns sfxload: no memory
left
This bug must be affecting far more than 9 people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns sfxload: no memory
left
To manage
Daniel Richard G. wrote:
Thomas, thank you for your clear description of the issue.
Given that the problem is memory beyond the 2GB barrier, something I
wanted to try was mmap()'s MAP_32BIT flag. You can sort-of do a malloc()
by making an anonymous mapping, and so I hacked up safe_malloc()
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns sfxload: no memory left
--
ubuntu-bugs mailing list
Hm, I was under the impression that the driver/emu10k1 simply read the
sound font data from user memory, and saved it to dedicated memory
belonging to the emu10k1.
Ah well, at least that answers that. Thanks for writing.
--
You received this bug notification because you are a member of Ubuntu
Thomas, thank you for your clear description of the issue.
Given that the problem is memory beyond the 2GB barrier, something I
wanted to try was mmap()'s MAP_32BIT flag. You can sort-of do a malloc()
by making an anonymous mapping, and so I hacked up safe_malloc() and
safe_free() (in
Raymond wrote:
I can load more than 16Mb soundfont into my sb live! platinum ct4760p on
my 32bits machines, so Is this bug specific to 64bits machine only
No, it is specific to machines with more than 2GB memory. Please see my
report.
Merry Christmas
Thomas
--
You received this bug
I can load more than 16Mb soundfont into my sb live! platinum ct4760p on
my 32bits machines, so Is this bug specific to 64bits machine only
asfxload -M
DRAM memory left = 131068 kB
asfxload -M PCLite.sf2
DRAM memory left = 100523 kB
--
You received this bug notification because you are a
As mentioned in the original ticket and the first comment
(https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/comments/1)
changing max_buffer_size does not help.
The soundfonts that fail to load are not even close to the 128MB default
(at least in file size), e.g.
~30MB file fails to
Using 64bit and 4GB of RAM, Audigy 4 (non-pro).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns sfxload: no memory left
--
ubuntu-bugs
Raymond wrote:
you have to change max_buffer_size if you want to load a larger
soundfont as default value is 128Mb
The issue is not with the size of the soundfont. The issue is that the
kernel tries to put them into the 16MB ISA
DMA zone, being short of memory below 2GB.
Here's the technical
you have to change max_buffer_size if you want to load a larger
soundfont as default value is 128Mb
http://git.alsa-project.org/?p=alsa-kernel.git;a=blob_plain;f=Documentation/sound/alsa/ALSA-Configuration.txt
Module snd-emu10k1
--
Module for EMU10K1/EMU10k2 based PCI
SnEptUne wrote:
Using gentoo-sources-2.6.36-r3.
Changing arch/x86/include/asm/dma.h fixed it for me, but I don't know if
this change would affect system stability.
Not for me, at least. I'm working with this configuration for more than
a year now without any bad side effects. What will
Using gentoo-sources-2.6.36-r3.
Changing arch/x86/include/asm/dma.h fixed it for me, but I don't know if
this change would affect system stability.
--
Trying to load a sf2 file with asfxload returns sfxload: no memory left
https://bugs.launchpad.net/bugs/183456
You received this bug
I don't quite understand your comment. The above fix applies to the
AMD64 platform. There is no such thing as a 32bit DMA zone on x86, but
still the kernel might want to allocate physical addresses for the
buffer memory beyond the 2GB barrier (bit 31 set), thus it is prone to
failure in any system
Yes, indeed. As in windows x86 the driver leads a bluescreen but in x64
it doesn't, I thought there's a solution in x64 and it could do the same
as windows, then tried yesterday to use iommu=force (soft no effect)
parameter, however, instead of no memory left, asfxload crashed with
some
Seems a different cause in amd64 platform.
In that a small sf2 file can be loaded successfully, (very few megabytes) it is
said about the IOMMU
--
Trying to load a sf2 file with asfxload returns sfxload: no memory left
https://bugs.launchpad.net/bugs/183456
You received this bug notification
Thanks, this helps a lot.
But what if the driver just makes repeated requests until it gets the
memory in the range it needs, by chance? Not likely?
-Original Message-
From: Thomas Richter t...@math.tu-berlin.de
Sent: Sunday, March 29, 2009 6:38 PM
To: j...@mojolink.com
Subject: [Bug
Well, simply re-allocating doesn't help since this will get it exactly
the same memory as before - so it had to fetch memory over and over
again until it succeeds, and then had to release all the unusable memory
again. Possible, but would require it to fetch at most 2GB of memory
(urgh!) just for
The problem with this goes a bit deeper. The reason for all this trouble
is that the emu10k1 chipset requires DMA from main memory to pick up the
samples, and - unfortunately - the DMA engine of the chip is broken.
Instead of using the full range of 32 bit DMA available on the PCI bus,
it only
Can't anyone pick this up? Please? I have had this problem for years
now, ever since I upped my RAM. I would love to use my emu10k1 synth
chip again since it is less laggy than any software synth.
I was told that this problem is due to the EMU10k1 being unable to
address more than 2G of
Is incomplete still appropriate for this bug? It is still present in
current distributions, does not appear to be a duplicate, and should not
be allowed to expire.
** Changed in: awesfx (Ubuntu)
Status: Incomplete = New
--
Trying to load a sf2 file with asfxload returns sfxload: no
Someone sent me an e-mail explaining that maybe the problem can be related to
iommu and a failure in the dma_alloc_coherent() call, and told me to include
iommu=force in the kernel's boot parameters. It didn't work with my computer,
but nevertheless it may work on your specific setup, so please
Same here, identical setup to Marcus.
--
Trying to load a sf2 file with asfxload returns sfxload: no memory left
https://bugs.launchpad.net/bugs/183456
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes - it is reproducable in 8.10.
Am Mittwoch, den 26.11.2008, 05:59 + schrieb Daniel T Chen:
Is this symptom still reproducible in 8.10 or 9.04?
** Changed in: awesfx (Ubuntu)
Status: New = Incomplete
--
Trying to load a sf2 file with asfxload returns sfxload: no memory left
Same here with Ubuntu 8.10 amd64 and 4GB Ram. Worked fine with Ubuntu
8.04 32bit on the same hardware (assumingly because then only 3.5 GB RAM
are available).
I debugged asfxload and traced it down to an error code from the
SNDRV_EMUX_IOCTL_LOAD_PATCH ioctl in seq_load_patch. Curiously,
Is this symptom still reproducible in 8.10 or 9.04?
** Changed in: awesfx (Ubuntu)
Status: New = Incomplete
--
Trying to load a sf2 file with asfxload returns sfxload: no memory left
https://bugs.launchpad.net/bugs/183456
You received this bug notification because you are a member of
I found something funny about it:
With 4GB DDR RAM (four 1GB banks):
asfxload succeeds loading an 8MB Piano SoundFont
asfxload fails with no memory left when loading a 103MB General MIDI SoundFornt
With 2GB DDR RAM (two 1GB banks):
asfxload succeeds loading an 8MB Piano SoundFont
asfxload
Just to add a bit of infrormation, I changed snd-emu10k1 module parameter to
include max_buffer_size=1024 (supposedly allowing 1GB of ram for samples)
_after_ I got the error. I increased it in steps (and rebooted after changing
it to be sure the changes were applied) and tested again, same
52 matches
Mail list logo
