1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
-*- outline -*-
* Harddrake TODO:
** fixes
*** non needed stuff to run X must be posponed after X11 startup
**** eg: scanner/audio/printer/floppy/cdrom/tape/tv/webcam/joystick/ ...
*** add updfstab as in kudzu
*** enable the user to force a module (isa, isapnp, ...)
*** timeout on dialogs in service
*** text:
**** bold fields name
**** red unknown modules
*** pci freeze
*** 2detect/look 4
**** pcmcia devices
**** isapnp devices
*** print "NOT LOADED" if module isn't loaded
** validation:
*** see dadou (GUI)
*** qa team (test cases)
* Postponed
** more use of my_gtk/ugtk
** use fbgtk+2 when booting on fbcon for smoother GUI => interactive::fbgtk
*** fpons, convert perl-GTK to gtk+2 :-)
** move all drakx tools into just a small one-liner that uses real <tool>.pm
so that harddrake and mcc reduces their memory usage pattern and
be faster (the next fast step will be to use perl6/parrot)
** check there're enough parameters in module config
** for to send a message for unknown hardware to install@mandrakesoft.com
*** use drakbugreport ?
Subject: [UNKNOW HARDWARE] or a new other ml
-> do you konw how to configure it under linux ?
-> description
* ####################################################################
* ####################################################################
sub disconnect($$) {
my ($button, $sig) = @_;
if ($sig) {
$button->signal_disconnect($sig);
undef $sig;
}
}
* / no hope / useless :
** enable a string to be passed as detector; in that case, do ourself the =~
** alter detect_devices in order to only probe one time
** detect *ALL* mouses if more than one (mousedrake?)
** deeper data structure in Mandrake 9.1 :
"Mass storage" => (Floppy,
Disk,
Cdrom,
Tape)
"Network" => (Ethernetcard,
Modem,
Isdn)
"Multimedia" => (Videocard,
Tvcard,
Soundcard,
Webcam)
"System" => (Bridge,
Cpu,
Memory)
"Publishing" => (Printer,
Scanner)
"Pointing" => (Mouse,
Joystick)
"Buses" => (Ideinterface,
Scsiinterface,
Usbinterface,
);
"Unknown/Others",
* ####################################################################
* Suggestions
** a dialog in harddrake to select the driver of choice.
easy way: greping pcitable for all known oss modules and alsa' snd-*
ones, then build a hand hash (oss<->alsa modules names) that enable to
get alsa or (respectively oss) module from oss (respectively alsa)
module.
then offering a window to switch from alsa to oss.
** various
Subject: Re: [Cooker] Optional ALSA Support for SB Live!
From: Fabrice FACORAT <f.faber@netcourrier.com>
To: cooker@linux-mandrake.com
In-Reply-To: <m2ofhvtpaq.fsf@vador.mandrakesoft.com>
References: <20020311051222.47DC087CA5@yavin.mandrax.org>
<m2ofhvtpaq.fsf@vador.mandrakesoft.com>
Date: 11 Mar 2002 11:12:31 +0100
Message-Id: <1015841551.3895.31.camel@bastard.localdomain>
Le lun 11/03/2002 à 10:41, Thierry Vignaud a écrit :
> > In Mandrake 8.1 rerunning Harddrake post-setup would switch over
> > to ALSA (which supports MIDI synth), however in 8.2 the only way to
> > get ALSA support is to manually edit the modules.conf file. This
> > would be disasterous for someone who isn't familar with
> > modules.conf, but had been instructed on the mandrake-expert/newbie
> > lists (as many had been) to simply rerun Harddrake on the sound card
> > to get ALSA (and hence MIDI synth support).
>
> give me the result of lspcidrake -f -v so that i switch your card
> from oss to alsa.
no please.
just one month ago you switch SBLive from Alsa to OSS ( cause drakX
set it as OSS and harddrake as Alsa ).
There were also a discussion concerning the fact that Alsa doesn't
support emu-tools and so all available options.
Last but not least, several peoples report pbs with Alsa ( is sound is
too high you have disturbances ). So someone is going to ask you for
OSS as it want to use some features os SBLive, etc ...
To my mind the best way for this ( but too late for 8.2 ) will be to
have a tool called soundrake. Thanks to this tools, you choose at the
beginning if you want to use OSS or alsa and then try to correctly
configure your sound card. This tool should be able to work in
embended mo in harddrake or harddrake2 ( infos concerning this so long
awaiting harddrake 2 ? ).
In order to make this tool be a perfect tool, it should be able to
advice user concerning the advantage and the disadvantage of each
driver ( indeed alsa sometimes is better than OSS as it support full
duplex and wave mixing on more sound cards ).
It's also disturbing is harddrake set alsa by default and XrakX set
OSS by default as sometimes by lanching harddrake ( just to see what
happen ) you lose ( or seems to lose ) your sound card ( mute mixer )
For example :
+ launch harddrake
+ use autodetection : yes/no
+ if auto detects enable, it detects a SBLive.
+ explanations text concerning the fact that :
if I use OSS I will be able to use sounds effects, live drive and
others things ( AC-3 passthrough ) thanks to the emu10k1-tools packages
( available on CD sets and installable via Software Manager )
if I use Alsa, I won't be able to use emu10k1-tools but at the
contrary I will be able to use midi software as alsa module support midi
+ ask user which one he wants to use : OSS / Alsa ?
+ set the sound card drivers and modules.conf according to user wishes
+ <mode= dream> if I select OSS, installed emu10k1-tools and provide a
GUI to configure them </mode = dream>
+ <mode= dream> if I select Alsa unmute at least PCM and Vol or display
a warning saying that by default Alsa mute everything ( configure alsa
service so that it save mixer settings )
+ test the sound ( mandrake sound theme )
+ do you hear something ?
+ yes -> your sound card have been properly set.
+ if no -> try the others drivers set or send lspcidrake -v to
somebody@somewhere.org to check for support for your sound card
+ Do you ahave another sound card ?
|
