The OSS version 4.0 has been available under GPL 2 since last month.
It's not restrictive anymore and, actually, considering to replace ALSA
with OSS is a fine idea.
--
restricted-manager shows all unused OSS modules as "needs computer restart"
https://bugs.launchpad.net/bugs/102468
You received
Ah -- thanks for the clarification. The fix sounds great. I look
forward to trying it.
As for Feisty+1, the developers of OSS have indicated a willingness to
collaborate with Ubuntu on how restricted-manager works with OSS. You
may contact Dev Mazumdar ([EMAIL PROTECTED]) or Hannu Savolainen
([
restricted-manager (0.19) feisty; urgency=low
.
[ Martin Pitt ]
* debian/control: Add X-Vcs-Bzr.
* autostart/restricted-manager.desktop.in: Fix capitalization. (LP: #103248)
* RestrictedManager/core.py: Keep track of whether a module's enable status
has changed throughout program
> - initially, state is never 'needs restart'. for enabled and not
loaded -> 'not used'
I implemented this rule in bzr head now. This is unintrusive enough for
Feisty.
Messing with modprobe etc. is Feisty+1 material, but actually we should
not even need it at all, since new modules default to bei
No, of course I do not want to modprobe all modules which are enabled.
Just one which *gets* enabled in the UI ('enabling' vs. 'enabled').
--
restricted-manager shows all unused OSS modules as "needs computer restart"
https://bugs.launchpad.net/bugs/102468
You received this bug notification becau
Confirmed.
The ALSA ice1712 module exports an alias of
pci:v1412d1712sv*sd*bc*sc*i* -- exactly the correct scope.
The comparable OSS envy24 module exports no alias whatsoever, and I
don't know why. That is the case for each of the OSS modules I spot-
checked (I didn't look at all of them
I'll do a little thinking-out-loud here myself:
I agree an overly-generous modalias might potentially cause this -- I'm
curious and will follow up on that tonight to see what modinfo has to
say on the OSS modules. If it is the case, I will email 4Front myself
and ask them to consider changing tha
Thanks for the additional information, I have everything I need now.
The best solution would of course be to change the OSS modules to ship
proper modaliases, so that they don't appear in the first place, but we
cannot have that easily.
Some loud thinking/taking notes:
Currently, state 'needs co
Screenshot attached. The only modules actually "in use" (and
appropriately so) are the NVIDIA accelerated graphics driver (not seen
in this shot), the Open Sound System 'envy24' driver module (not seen),
the OSS 'hdaudio' driver module (not seen), the OSS 'ossusb' driver
module (not seen), and the
Attached is a single file containing output from both "restricted-
modules --list" and "lsmod".
** Attachment added: "module-listings.txt"
http://librarian.launchpad.net/7150143/module-listings.txt
--
restricted-manager shows all unused OSS modules as "needs computer restart"
https://bugs.lau
Right, I'm talking about installing non-free OSS after installing
Ubuntu, and then looking in restricted-manager. I am using OSS because
ALSA doesn't support one of my audio interfaces. And the kernel is
stock from the installation CD image.
OSS seems to install a module for *every* known sound
The default Ubuntu kernel does not ship any non-free OSS modules. I
assume you are using a custom kernel? Please give me the output of
restricted-manager --list
lsmod
** Changed in: restricted-manager (Ubuntu)
Importance: Undecided => Low
Status: Unconfirmed => Needs Info
--
restr
12 matches
Mail list logo
