/[gentoo]/xml/htdocs/doc/en/alsa-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/alsa-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.71 Revision 1.72
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.71 2007/01/31 15:54:35 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.72 2007/01/31 16:39:26 nightmorph Exp $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 5
6<guide link="/doc/en/alsa-guide.xml"> 6<guide link="/doc/en/alsa-guide.xml">
7<title>Gentoo Linux ALSA Guide</title> 7<title>Gentoo Linux ALSA Guide</title>
… …
421 421
422<impo> 422<impo>
423Please note that you will have to run <c>emerge alsa-driver</c> after every 423Please note that you will have to run <c>emerge alsa-driver</c> after every
424kernel (re)compile, as the earlier drivers are deleted. To make this task 424kernel (re)compile, as the earlier drivers are deleted. To make this task
425easier, you may want to emerge the <c>module-rebuild</c> package, which will 425easier, you may want to emerge the <c>module-rebuild</c> package, which will
426keep track of module packages and rebuild them for you. First run <c>module 426keep track of module packages and rebuild them for you. First run
427rebuild populate</c> to create the list, and then after every kernel 427<c>module-rebuild populate</c> to create the list, and then after every kernel
428(re)compile, you just run <c>module-rebuild rebuild</c>, and your external 428(re)compile, you just run <c>module-rebuild rebuild</c>, and your external
429modules will be rebuilt. 429modules will be rebuilt.
430</impo> 430</impo>
431 431
432</body> 432</body>
Legend:
Removed from v.1.71  
changed lines
  Added in v.1.72
  ViewVC Help
Powered by ViewVC 1.1.13