swift 05/06/02 17:18:54
Modified: xml/htdocs/doc/en/handbook hb-install-alpha-kernel.xml
hb-install-amd64-kernel.xml
hb-install-hppa-kernel.xml
hb-install-ppc-kernel.xml
hb-install-ppc64-kernel.xml
hb-install-sparc-kernel.xml
Log:
#90367 - Apply lspci fix to other architectures as well
Revision Changes Path
1.24 +11 -7 xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml?rev=1.24&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml?rev=1.24&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml.diff?r1=1.23&r2=1.24&cvsroot=gentoo
Index: hb-install-alpha-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-alpha-kernel.xml 16 Apr 2005 21:47:06 -0000 1.23
+++ hb-install-alpha-kernel.xml 2 Jun 2005 17:18:54 -0000 1.24
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v
1.23 2005/04/16 21:47:06 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v
1.24 2005/06/02 17:18:54 swift Exp $ -->
<sections>
-<version>2.2</version>
-<date>2005-04-16</date>
+<version>2.3</version>
+<date>2005-06-02</date>
<section>
<title>Timezone</title>
@@ -112,10 +112,14 @@
<p>
However, one thing <e>is</e> true: you must know your system when you start
-configuring a kernel manually. Most information can be gathered by viewing the
-contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
-can also run <c>lsmod</c> to see what kernel modules the Installation CD uses
(it might
-provide you with a nice hint on what to enable).
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
+be able to use <c>lspci</c> within the chrooted environment. You may safely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
+<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD
+uses (it might provide you with a nice hint on what to enable).
</p>
<p>
1.24 +11 -7 xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml?rev=1.24&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml?rev=1.24&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml.diff?r1=1.23&r2=1.24&cvsroot=gentoo
Index: hb-install-amd64-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-amd64-kernel.xml 16 Apr 2005 21:47:06 -0000 1.23
+++ hb-install-amd64-kernel.xml 2 Jun 2005 17:18:54 -0000 1.24
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v
1.23 2005/04/16 21:47:06 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v
1.24 2005/06/02 17:18:54 swift Exp $ -->
<sections>
-<version>2.1</version>
-<date>2005-04-16</date>
+<version>2.2</version>
+<date>2005-06-02</date>
<section>
<title>Timezone</title>
@@ -109,10 +109,14 @@
<p>
However, one thing <e>is</e> true: you must know your system when you start
-configuring a kernel manually. Most information can be gathered by viewing the
-contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
-can also run <c>lsmod</c> to see what kernel modules the Installation CD uses
-(it might provide you with a nice hint on what to enable).
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
+be able to use <c>lspci</c> within the chrooted environment. You may safely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
+<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD
+uses (it might provide you with a nice hint on what to enable).
</p>
<p>
1.20 +11 -7 xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml?rev=1.20&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml?rev=1.20&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml.diff?r1=1.19&r2=1.20&cvsroot=gentoo
Index: hb-install-hppa-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-install-hppa-kernel.xml 16 Apr 2005 21:47:06 -0000 1.19
+++ hb-install-hppa-kernel.xml 2 Jun 2005 17:18:54 -0000 1.20
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v
1.19 2005/04/16 21:47:06 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v
1.20 2005/06/02 17:18:54 swift Exp $ -->
<sections>
-<version>1.13</version>
-<date>2005-04-16</date>
+<version>1.14</version>
+<date>2005-06-02</date>
<section>
<title>Timezone</title>
@@ -103,10 +103,14 @@
<p>
However, one thing <e>is</e> true: you must know your system when you start
-configuring a kernel manually. Most information can be gathered by viewing the
-contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
-can also run <c>lsmod</c> to see what kernel modules the LiveCD uses (it might
-provide you with a nice hint on what to enable).
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
+be able to use <c>lspci</c> within the chrooted environment. You may safely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
+<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD
+uses (it might provide you with a nice hint on what to enable).
</p>
<p>
1.26 +11 -7 xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.26&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.26&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml.diff?r1=1.25&r2=1.26&cvsroot=gentoo
Index: hb-install-ppc-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-install-ppc-kernel.xml 29 May 2005 19:23:30 -0000 1.25
+++ hb-install-ppc-kernel.xml 2 Jun 2005 17:18:54 -0000 1.26
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.25
2005/05/29 19:23:30 josejx Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.26
2005/06/02 17:18:54 swift Exp $ -->
<sections>
-<version>2.5</version>
-<date>2005-05-29</date>
+<version>2.6</version>
+<date>2005-06-02</date>
<section>
<title>Timezone</title>
@@ -115,10 +115,14 @@
<p>
However, one thing <e>is</e> true: you must know your system when you start
-configuring a kernel manually. Most information can be gathered by viewing the
-contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
-can also run <c>lsmod</c> to see what kernel modules the Installation CD uses
-(it might provide you with a nice hint on what to enable).
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
+be able to use <c>lspci</c> within the chrooted environment. You may safely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
+<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD
+uses (it might provide you with a nice hint on what to enable).
</p>
<p>
1.13 +11 -8 xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml?rev=1.13&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml?rev=1.13&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml.diff?r1=1.12&r2=1.13&cvsroot=gentoo
Index: hb-install-ppc64-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- hb-install-ppc64-kernel.xml 26 Apr 2005 03:12:56 -0000 1.12
+++ hb-install-ppc64-kernel.xml 2 Jun 2005 17:18:54 -0000 1.13
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v
1.12 2005/04/26 03:12:56 vapier Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v
1.13 2005/06/02 17:18:54 swift Exp $ -->
<sections>
-<version>2.2</version>
-<date>2005-04-25</date>
+<version>2.3</version>
+<date>2005-06-02</date>
<section>
<title>Timezone</title>
@@ -103,11 +103,14 @@
<p>
However, one thing <e>is</e> true: you must know your system when you
-start configuring a kernel manually. Most information can be gathered by
-viewing the contents of <path>/proc/pci</path> (or by using <c>lspci</c>
-if available). You can also run <c>lsmod</c> to see what kernel modules
-the Installation CD uses (it might provide you with a nice hint on what to
-enable).
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
+be able to use <c>lspci</c> within the chrooted environment. You may safely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
+<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD
+uses (it might provide you with a nice hint on what to enable).
</p>
<p>
1.16 +11 -7 xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml?rev=1.16&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml?rev=1.16&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml.diff?r1=1.15&r2=1.16&cvsroot=gentoo
Index: hb-install-sparc-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- hb-install-sparc-kernel.xml 16 Apr 2005 21:47:06 -0000 1.15
+++ hb-install-sparc-kernel.xml 2 Jun 2005 17:18:54 -0000 1.16
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v
1.15 2005/04/16 21:47:06 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v
1.16 2005/06/02 17:18:54 swift Exp $ -->
<sections>
-<version>2.1</version>
-<date>2005-04-16</date>
+<version>2.2</version>
+<date>2005-06-02</date>
<section>
<title>Timezone</title>
@@ -104,10 +104,14 @@
<p>
However, one thing <e>is</e> true: you must know your system when you start
-configuring a kernel manually. Most information can be gathered by viewing the
-contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
-can also run <c>lsmod</c> to see what kernel modules the Installation CD uses
-(it might provide you with a nice hint on what to enable).
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
+be able to use <c>lspci</c> within the chrooted environment. You may safely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
+<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD
+uses (it might provide you with a nice hint on what to enable).
</p>
<p>
--
[email protected] mailing list
