nightmorph    08/03/05 09:48:24

  Modified:             hb-install-sparc-kernel.xml
  Log:
  sparc notes from armin76: qla2xxx controller users must use vanilla-sources, 
and there will be a packages CD this release.

Revision  Changes    Path
1.30                 
xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml?rev=1.30&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml?rev=1.30&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml?r1=1.29&r2=1.30

Index: hb-install-sparc-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- hb-install-sparc-kernel.xml 3 Mar 2008 08:11:13 -0000       1.29
+++ hb-install-sparc-kernel.xml 5 Mar 2008 09:48:24 -0000       1.30
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml,v
 1.29 2008/03/03 08:11:13 nightmorph Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml,v
 1.30 2008/03/05 09:48:24 nightmorph Exp $ -->
 
 <sections>
 
@@ -59,6 +59,12 @@
 # <i>emerge gentoo-sources</i>
 </pre>
 
+<note>
+If you're using a qla2xxx disk controller, you'll need to <c>emerge
+=vanilla-sources-2.6.16*</c> (<e>not</e> <c>gentoo-sources</c>), because 
kernels
+>=2.6.17 won't work with this controller.
+</note>
+
 <p>
 When you take a look in <path>/usr/src</path> you should see a symlink called
 <path>linux</path> pointing to your kernel source. In this case, the installed



-- 
[email protected] mailing list

Reply via email to