I noticed there seems to have been some kind of change in the alsa autoinstall on boot between rc1 and rc2.
With rc1 there were a number of lines on the boot screen saying something about modules loaded with warnings - on rc2 this has been replaced by something that goes by too quick to see. In both cases, the driver (snd-intel8x0) loads and works.
I tried alsa on an rc2 legacy boot with the alsa and alsa-modules dsl extensions on the same machine but the alsa autoconfig does not work. Is this because the dsl extensions (I see one has 2.4.31 modules, i.e. DSL 2.1) are older than the corresponding unc extension?There was no change in this area. Alsa auto boot and detection requires the following:
Both alsa.unc and gnu-utils.unc must be in your mydsl search path upon boot and successfully loaded at boot time.
alsa.unc requires gnu-utils.unc as specified in the alsa.unc.info
Obviously, since unc type extensions are used, it will not work with legacy option. Unionfs is required.
Do not try to use alsadebs.dsl or alsa.dsl for 2.4.31 as they both will not work.
OK - sure, but if the dsl equivalent of alsa.unc were available would things work on a legacy boot with the alsa boot option and gnu-utils.dsl?Will the finnish keymap make it for rc3?
Quote (Juanito @ Mar. 07 2007,08:51)
OK - sure, but if the dsl equivalent of alsa.unc were available would things work on a legacy boot with the alsa boot option and gnu-utils.dsl?
No. Not at boot time. Both of those .dsls are huge memory resource hogs and would likely cause the system not to boot, as ramdisk would become exhausted. Therefore would not work for many users.
In fact, it would not work for the majority of DSL machines that I use.
Our target is not only a small distro but one that works well on very small resource machines.
You can, as many have, add commands to /opt/bootlocal.sh to achieve similar results.Next Page...
original here.