Sabayon Wiki - User contributions [en]

Talk:Sabayon

2009-03-21T22:22:05Z

Zambayoni: clear spam

Talk:Ca:Translations

2009-03-11T21:50:40Z

Zambayoni: New page: {{i18n|ca en es it}}

{{i18n|[[Talk:Ca:Translations|ca]] [[Talk:En:Translations|en]] [[Talk:Es:Translations|es]] [[Talk:It:Translations|it]]}}

Talk:Es:Translations

2009-03-11T21:50:18Z

Zambayoni: New page: {{i18n|ca en es it}} ;Discusiones sobre Traducciones

{{i18n|[[Talk:Ca:Translations|ca]] [[Talk:En:Translations|en]] [[Talk:Es:Translations|es]] [[Talk:It:Translations|it]]}}

;Discusiones sobre Traducciones

Talk:En:Translations

2009-03-11T21:49:34Z

Zambayoni:

{{i18n|[[Talk:Ca:Translations|ca]] [[Talk:En:Translations|en]] [[Talk:Es:Translations|es]] [[Talk:It:Translations|it]]}}

Wouldn't it be a good idea to put a section in the main page called "Translations" or something like that, flagging it as "work in progress" ?? This way we can have a better organization AND let know the community that doesn't check the forum, that they can give us a hand...

Talk:It:Translations

2009-03-11T21:48:49Z

Zambayoni:

{{i18n|[[Talk:Ca:Translations|ca]] [[Talk:En:Translations|en]] [[Talk:Es:Translations|es]] [[Talk:It:Translations|it]]}}

'''Discussioni sulle traduzioni'''

== Proposta di procedura ==
Al momento sto traducendo da solo e, volevo segnalarVi, che anche qualcuno che corregga gli errori di ortografia è gradito.
Purtroppo posso dedicare un'oretta al giorno e se qualcuno si offre a correggere gli eventuali errori ...

HOWTO: Install SabayonLinux x86/x86-64 RC2 on an Intel Mac

2009-03-09T01:16:55Z

Zambayoni:

This HOWTO will guide you in the installation of SabayonLinux on an Intel Mac wiping the whole hard drive and using all the available space for our beloved Operating System. You can install Mac OSX and even Windows XP on a USB drive (with GPT) if you want, but that's not covered here.
NOTE: with the current RC2 DVDs (not the miniEditions!) you have to do two extra steps.

STEP A: Starting MAC OSX Install Disk 1.
Insert your Mac OSX Install Disk 1 and keep the "C" key pressed until the system the Installer.
We are going to wipe the whole hard drive and change the partition table format to MS-DOS (MBR) instead of GPT.
When the Installer is ed, lauch the Disk Utilty, erase all the partitions and under Options, choose "MS-DOS partition table" instead of "GPT (GUID Partition Table)".
NOTE: you can do this step even on the LiveDVD/LiveCD, but that's the way I've tried

STEP B: Booting SabayonLinux CD/DVD.
Like we did for the Mac OSX Install Disk 1, keep the "C" key pressed at boot until the system s our beloved CD/DVD boot prompt.
NOTE: you can eject CDs/DVDs by pressing both right and left mouse buttons at boot until the media gets out.
Then, choose the parameters that you want (press F2,F3,F4 for more info) and then start the boot procedure.

STEP C: Updating Sabayon Linux Installer by hand (Internet connection required)
NOTE: if you are running SabayonLinux >RC2 or the RC2 miniEditions skip this step.
Once you're on your favourite Desktop Environment, open a terminal and type:

<pre>sudo su</pre>
<pre>cd /tmp</pre>
<pre>wget http://www.lxnaydesign.net/sabayon/installer/usr-lib-anaconda.tar.bz2</pre>
<pre>tar xjf usr-lib-anaconda.tar.bz2</pre>
<pre>rm -rf /opt/anaconda/usr/lib/anaconda/*</pre>
<pre>mv -f anaconda/* /opt/anaconda/usr/lib/anaconda/</pre>
<pre>rm -rf anaconda</pre>
<pre>exit</pre>

The Installer is now updated and ready to Install into your Intel Mac.

STEP C2: Updating GRUB to support Intel Mac
1000
s boot (Internet connection required).
NOTE: if you are running SabayonLinux >RC2 or the RC2 miniEditions skip this step.
<pre>sudo su</pre>
<pre>cp /mnt/livecd/boot/grub /tmp -Rp</pre>
<pre>mount -t tmpfs none /mnt/livecd/boot/grub/</pre>
<pre>mv /tmp/grub/* /mnt/livecd/boot/grub/</pre>
<pre>cd /mnt/livecd/boot/grub/</pre>
<pre>rm -rf stage2v</pre>
At this point, if you have x86 CD/DVD just do (on the same shell!):

<pre>wget http://www.lxnaydesign.net/sabayon/grub-mactel/stage2-x86</pre>

[[Category:Hardware|Install SabayonLinux x86/x86-64 RC2 on an Intel Mac]]

It:HOWTO: Partimage Guide

2009-03-09T01:11:39Z

Zambayoni:

L'oggetto di questa breve guida è come utilizzare l'utility Partition Image[http://www.partimage.org]. Partimage è uno strumento per creare o ripristinare le immagini del filesystem in modo abbastanza veloce e semplice. La guida è specifica e si riferisce al mio personalissimo caso e quindi la sua generalizzazione non può essere scontata. La versione di Sabayon utilizzata è la 3.3 dvd edition.

E' importante tenere presente che Partimage non lavora su partizioni formattate con LVM (partizionamento in volumi logici) e nemmeno l'utility Gparted per il partizionamento. Quindi se si vuole prevedere di utilizzare Partimage come utility di recovery in tutti i casi nei quali è richiesto il suo uso, è bene utilizzare altri sistemi di partizionamento.

Altra cosa importante da considerare è che Sabayon include già Partimage (entrate in console come root e digitate partimage) ma è meglio utilizzare Partimage come utility esterna alla distro che utilizziamo. Per far ciò utilizzeremo System Rescue [http://www.sysresccd.org] una mini distro con tutto il necessario per far partire il pc in caso di problemi e che contiene al suo interno Partimage.

La prima cosa che dobbiamo fare è masterizzare l'iso di Systemrescue. Inserirla nel cddrive e accendere il pc. Ad un certo punto ci verrà richiesto di inserire il codice per la tastiera italiana e noi digiteremo il numero 21. Al termine della pseudoistallazione possiamo optare di agire tramite linea di comando oppure (scelta più ovvia per utenti inesperti come il sottoscritto) digitare:

'''startx'''

ed entrare nell'interfaccia grafica del programma. Immediatamente abbiamo a disposizione una console già aperta come root pronta a ricevere comandi. Mentre sulla destra abbiamo una serie di icone per altre scelte che potrebbero servirci: alcuni programmi di scrittura, firefox, e Gparted.

Clicchiamo due volte sull'icona Gparted (o digitiamo direttamente in console gparted). Una volta aperto il programma verifichiamo che la partizione che vogliamo salvare non sia montata (no lucchetto e no punto di montaggio) e che soprattutto sia compatibile con gli standard supportati da Partimage.

Chiuso Gparted, nella shell digitiamo:

'''fdisk -l'''

per segnarci il mome della partizione sulla quale agiremo.

Nota bene: Se non si sceglie di parizionare con LVM, allora avremo bisogno almeno di tre partizioni: una root (/), una di swap e una di /home. In questa guida noi supporremo di utilizzare la partizione /home per crearne l'immagine di backup. E supporremo di volerla salvare in una partizione creata apposta per ospitare il backup di dati e che indicheremo con sda3.

Digitiamo:

'''mkdir /mnt/backup'''

e poi:

'''mount /dev/sda3 /mnt/backup'''

Fatto ciò digitiamo:

'''partimage'''

per far partire il programma.

La prima cosa che faremo è selezionare la partizione che ci interessa backuppare e la evidenzieremo con i tasti sù o giù. Poi attraverso il tasto tab ci porteremo nella riga:

'''Image file to create/use'''

e qui scriveremo:

'''/mnt/backup/nomefile.gz'''

Tralasciando di descrivere le altre opzioni dell'utility, premiamo due volte F5

A questo punto Partimage parte e comincia ad elaborare la partizione. Se non ci sono segnalazioni di errore noi confermeremo ogni sua domanda con OK. Alla fine avremo una copia della nostra partizione salvata nel disco sda3 e che potremo utilizzare a piacimento per salvarla su dvd o su altri sistemi e quindi utilizzarla per il ripristino nell'eventualità di un crash (per esempio).

Prima di chiudere partimage, possiamo fare un'ulteriore azione che ritengo importante: verificare che la partizione appena salvata sia in effetti idonea al ripristino o è stata creata con qualche errore intrinseco.

Per far ciò, chiudiamo Partimage con F6. Riapriamolo al solito digitando partimage dalla shell. Evidenziamo la partizione appena salvata e nella solita riga digitiamo esattamente il nome che abbiamo dato in precedenza e che ora è diventato:

'''/mnt/backup/nomefile.gz.000'''

Muoviamoci con il tasto TAB fino alla riga:

'''Restore partition from an image file'''

e selezioniamola con la barra spaziatrice. Con questo abbiamo in pratica detto a Partimage di recuperare il file di backup della nostra partizione precedentemente salvata.

F5 per andare avanti. Selezioniamo ora la riga che dice in pratica di simulare il ripristino e confermiamo. Se tutto è andato bene Partimage ci dirà che il ripristino è avvenuto positivamente (ovviamente nulla è stato scritto sull'hd) e così possiamo uscire da Partimage e quindi da Systemrescue.

(Spero che questa guida sia chiara e semplice: giusta per chi è alle prime armi con il mondo linux)

[[Category:Filesystems|Partimage GuideIt]]

Talk:Guida a Partimage

2009-03-09T01:10:47Z

Zambayoni: Talk:Guida a Partimage moved to Talk:It:HOWTO: Partimage Guide: see It:Translations

#REDIRECT [[Talk:It:HOWTO: Partimage Guide]]

Talk:It:HOWTO: Partimage Guide

2009-03-09T01:10:47Z

Zambayoni: Talk:Guida a Partimage moved to Talk:It:HOWTO: Partimage Guide: see It:Translations

As per cvill64's original request ...
English is prefered, however, if you choose to use a different language, you may translate it on the same page, just use "language sections" and if you write it in a foreign language first, translate it to english or requiest a translation please :)

--cvill64 07:06, 27 August 2006 (CEST)
--[[User:Appleman1234|Appleman1234]] 16:42, 7 April 2007 (PDT)

Guida a Partimage

2009-03-09T01:10:46Z

Zambayoni: Guida a Partimage moved to It:HOWTO: Partimage Guide: see It:Translations

#REDIRECT [[It:HOWTO: Partimage Guide]]

Talk:HOWTO: Automount ntfs paritions as read/write

2009-03-09T01:01:21Z

Zambayoni:

{{delete|'''Reason:''' redirection of talk page with incorrect title}}
REDIRECT [[Talk:HOWTO: Automount NTFS partitions as read/write]]

HOWTO: Automount ntfs paritions as read/write

2009-03-09T00:59:39Z

Zambayoni:

{{delete|'''Reason:''' traslated page to correct title: [[HOWTO: Automount NTFS partitions as read/write]]}}

Existing Reiser4 partitions - CAREFUL!

2009-03-09T00:52:28Z

Zambayoni:

I have an existing Gentoo install with 3 reiser4 partitions /, /home, and /media. When trying Sabayon on a spare partition, I noticed the installer thought /media was swap, but was marked as leaving the data untouched so I wasn't too worried. However, on reboot, Sabayon mounted it as swap, destroying the file system, so when I eventually booted back into Gentoo, it was gone: unrecognized and unmountable. fsck.reiser4 was not working from within Gentoo, but rebooting to the old Conrad disc I had installed from and running it happily saved tons of data by running it with --build-sb and then --build-fs as it asked for. A happy ending to a stressful few minutes - backup and keep a sharp eye on that installer.

[[Category:Filesystems]]

Category:Filesystems

2009-03-09T00:49:39Z

Zambayoni: New page: {{See also|http://www.gentoo-wiki.info/Category:Filesystems}} Filesystems

{{See also|http://www.gentoo-wiki.info/Category:Filesystems}}

[[Category:HOWTOs|Filesystems]]

Category:Candidates for deletion

2009-02-26T19:47:50Z

Zambayoni:

This category is for pages that not meet the [[En:Editing Guidelines|Editing Guidelines]].

[[Category:Sabayon Wiki]]

Tutorial index

2009-02-26T19:45:57Z

Zambayoni:

{{delete}}

Installing RC2 on the mactel platform.

Automount NTFS partitions as read/write.

Use xdelta patches

Manual installation

Work around: SDL 2.0.13-r1

Use your sabayon live disk to recover GCC.

KDM login fix for ATI and XGL

Linux

2009-02-26T19:43:18Z

Zambayoni:

{{delete}}

Linux (also known as GNU/Linux) is a Unix-like computer operating system. It is one of the most prominent examples of open source development and free software; unlike proprietary operating systems such as Windows or Mac OS, all of its underlying source code is available to the general public for anyone to freely use, modify, and redistribute.

[http://en.wikipedia.org/wiki/Linux According to wikipedia.]

Linux is the combination of the Linux kernel, the GNU set of operating system relates applications, and other FOSS (Free Open Source software) software.

Linux is the basis of Gentoo GNU Linux which is the basis of Sabayon GNU Linux or Sabayon Linux.

For more information see the Wikipedia link above.

Zh TW:Editing Guidelines

2009-02-26T19:38:10Z

Zambayoni: the same that En:Editing Guidelines

{{delete}}
''Editing Guidelines:'' A guide to making decent, working wiki articles.
{{Warning| '''Work in Progress'''}} - That is for sure lol.

== Guidelines ==

*Make decent articles; and make them worthwhile. Meaning that if you don't see any use for it; don't put it here.
*Make sure that '''ALL''' the information in your articles are correct. I don't care if you have to run through the steps yourself; if the information isn't correct then chances are that it will be edited to be corrected or even worse, deleted.
*Use the correct code for the correct type of line.

{{Code|Python|<pre class="clear">
def chklayman(pkgname):
lst = os.listdir(laymandir)
for line in lst:
if os.path.isdir(laymandir+line+"/"+pkgname):
print 'Package found in '+laymandir+line+'/'+pkgname
return 1 </pre>}}
<nowiki>{{Code|Insert Name of Code here|<pre class="clear">
(Insert code here) </pre>}}</nowiki> To get the above shown box.

{{File| /etc/X11/xorg.conf|<pre class="clear"> # **********************************************************************
# Screen sections.
# **********************************************************************

Section "Screen"

# The Identifier, Device and Monitor lines must be present

Identifier "Screen 1"
Device "VESA"
Monitor "Generic Monitor"
Option "AddARGBGLXVisuals" "true"

</pre>}}
<nowiki>{{File| (Name of File)| <pre class="clear"> (File Contents) </pre>}}</nowiki> tag for this file box. Use this box for the contents of files.

{{Console|<pre class="clear"> # emerge --sync</pre>}}
Use <nowiki>{{Console| <pre class="clear"> (console commands & info) </pre>}}</nowiki> for console input/output

And remember to close each tag with a </pre> tag. Because if you don't then all of your text will end up in one big box.

*Use the <nowiki>{{Commandgui|<highlighted word>}}</nowiki> for highlighting keywords such as things that need to be looked for in a dialog box.

*If you have warnings such as "May break your system" or "Use with caution" then use the <nowiki>{{Warning| <Insert Warning Here>}}</nowiki>

*If you have a note such as "Emerge --sync your portage before doing this step" or "May give more than what you need in packages" then use the <nowiki>{{Note| Insert Note Here}}</nowiki> template.

*Please don't spam. If you spam we will block you and your IP. No exceptions.

*Keep your articles simple. Don't include useless crap. Just what needs to be there. However if you need to post something like the output of lspci or something long use a scrollbar box by using one of the three templates shown above.

*If you could go through and cleanup useless or outdated articles by updating them. Thanks guys!

[[Category:Sabayon Wiki|Editing GuidelinesZh TW]]

Zh TW:Wiki Admins

2009-02-26T19:27:00Z

Zambayoni:

{{i18n|[[En:Wiki Admins|en]] [[It:Wiki Admins|it]] [[Zh TW:Wiki Admins|zh tw]]}}

* [[User:Lxnay|Lxnay]]
** Jabber: lxnay at sabayonlinux dot org
** Email: lxnay at sabayonlinux dot org
* [[User:Eden|Eden]]
** Jabber: eden at binstar dot org
** Email: amcgeoch at gmail dot com

[[Category:Sabayon Wiki|Wiki AdminsZh TW]]

It:Wiki Admins

2009-02-26T19:23:32Z

Zambayoni:

{{i18n|[[En:Wiki Admins|en]] [[It:Wiki Admins|it]] [[Zh TW:Wiki Admins|zh tw]]}}

* [[User:Lxnay|Lxnay]]
** Jabber: lxnay at sabayonlinux dot org
** Email: lxnay ay sabayonlinux dot org
* [[User:Eden|Eden]]
** Jabber: eden at binstar dot org
** Email: amcgeoch at gmail dot com

C'è anche un terzo componente, a cui piace giocare e trollare nella wiki a suo piacimento ..fate attenzione, c'è qualcuno sotto copertura.

[[Category:Sabayon Wiki|Wiki AdminsIt]]

En:HOWTO: Finding right network kernel driver

2009-02-26T19:19:24Z

Zambayoni:

{{i18n|[[Ca:HOWTO: Finding right network kernel driver|ca]] [[En:HOWTO: Finding right network kernel driver|en]]}}

To find out which modules you must use..
the most simple thing to do is cat log file and grep for eth entry's ..
This will work if your Sabayon linux have already recognized your ethernet card (most cases).
In this example we look for eth0 and eth1 entry's, so if you have more cards just put at the end
eth[0,1,2,3,n] n = last ethernet card.

'''cat /var/log/messages|grep eth[0,1]\:'''

<code>

 Jul 22 07:46:44 mazinga [4294688.198000] e100: eth0: e100_probe: addr 0xd4000000, irq 19, MAC addr 00:06:29:E9:77:40 Jul 22 07:46:44 mazinga [4294688.213000] eth1: VIA Rhine II at 0x17800,00:11:2f:09:fc:1f, IRQ 20. Jul 22 07:46:44 mazinga [4294688.214000] eth1: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1. Jul 22 07:46:59 mazinga [4294756.820000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
</code>

from the lines above we can see that wi need to use e100 and VIA Rhine (which uses via_rhine) 
to view all the modules your kernel support do:

'''ls /lib/modules/`uname -r`/kernel/drivers/net'''

and for detailed information about a module (for via_rhine in this case)

'''modinfo via_rhine'''

<code>
 filename:       /lib/modules/2.6.16-reiser4-r3conan/kernel/drivers/net/via-rhine.ko author:         Donald Becker <becker@scyld.com> description:    VIA Rhine PCI Fast Ethernet driver license:        GPL vermagic:       2.6.16-reiser4-r3conan preempt K7 REGPARM gcc-4.1 depends: alias:          pci:v00001106d00003043sv*sd*bc*sc*i* alias:          pci:v00001106d00003065sv*sd*bc*sc*i* alias:          pci:v00001106d00003106sv*sd*bc*sc*i* alias:          pci:v00001106d00003053sv*sd*bc*sc*i* parm:           rx_copybreak:VIA Rhine copy breakpoint for copy-only-tiny-frames (int) parm:           debug:VIA Rhine debug level (0-7) (int) parm:           max_interrupt_work:VIA Rhine maximum events handled per interrupt (int) 
</code> 
in case you don't have running modules in your distro then you could try

'''lspci | grep Ethernet'''

<code>

 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78 ) 00:13.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08 ) 
</code>

And google for modules which support your card

If you do have multiple ethernet cards, good practice is to put aliases into
/etc/modules.d/aliases ,so in this particular case it would look like
<code>
 alias eth0 e100 alias eth1 via_rhine
</code> 
This will prevent swapping eth0 and eth1 which occur because of some bugs in coldplug/udev, as
the first driver which get loaded becomes eth0, and we don't want that. We need to know exactly
which card is eth0 and eth1 to configure our network.

[[Category:Networking|Finding right network kernel driverEn]]

HOWTO: Finding right network kernel driver

2009-02-26T19:17:22Z

Zambayoni: HOWTO: Finding right network kernel driver moved to En:HOWTO: Finding right network kernel driver

#REDIRECT [[En:HOWTO: Finding right network kernel driver]]

En:HOWTO: 3.5 Pod adding portage

2009-02-26T19:12:06Z

Zambayoni:

{{I18n| [[Ca:HOWTO: 3.5 Pod adding portage|ca]] [[En:HOWTO: 3.5 Pod adding portage|en]] [[Es:HOWTO: 3.5 Pod adding portage|es]] [[Fr:HOWTO: 3.5 Pod adding portage|fr]]}}

== Introduction ==
First, it is entirely possible to happily run Sabayon 3.5 Pod (the 700 meg mini edition) without any of the following steps. If you have no interest in compiling your own applications or maintaining 100% Gentoo compatability then you are already good to go. Sabayon 3.5 as stands is a complete operating system and will work fine in binary (no compiling) mode. However if you truly need Gentoo compatability or the ability to bring packages in from the other various Gentoo overlays then the following steps should position you to do so.

We will start with one single assumption, that you have actually already finished installing Pod. It is from that point, actually rebooting into the system and functioning from the install that we will proceed.

== Adding portage support to Sabayon 3.5 Pod ==

Before starting on this, you're going to want to download the portage database appropriate for your architecture. Please point your browser to:
[http://www.sabayonlinux.org/mod/mirrors/ http://www.sabayonlnux.org/mod/mirrors/] Choose a mirror.

If you are using the 32 bit Sabayon Pod, you will download the following file: Sabayon-Linux-x86-3.5-Pod.portage.db.tar.bz2

If you are using the 64 bit Sabayon Pod, you will download this file: Sabayon-Linux-x86_64-3.5-Pod.portage.db.tar.bz2

Once you have downloaded the appropriate portage database file, you will do the following commands:

{{Console|<pre class="clear">su (Please make sure to enter the root password when asked)
cd /var/db/pkg/
mv /home/user/Sabayon-Linux-x86-3.5-Pod.portage.db.tar.bz2 . (For 64 bit, the filename will beSabayon-Linux-x86_64-3.5-Pod.portage.db.tar.bz2 )
tar xjvf Sabayon-Linux-x86-3.5-Pod.portage.db.tar.bz2

***NOTE*** Please try your best to copy and paste, or you may miss a vital but easy to miss dot which is part of a command. </pre>}}

Now we are really ready to begin. From here on out we will be working ONLY in command line and as root. Yes some of this can be done with GUI applications, but trust me when I say it's faster and easier using command line. We will start with a little preparation work.

{{Console|<pre class="clear">equo update
equo install entropy
equo world</pre>}}

This will bring your system 100% up to current. So now we can get into the meat of the matter of bringing your system up to Gentoo compatability. As one command we can install all the packages we need. You may want to install gcc separately if you end up with errors regarding gcc. This may be attributed to needing to add the version number.

{{Console|<pre class="clear">equo install portage layman libtool gettext linux-sabayon glibc linux-headers subversion gentoolkit
equo install sys-devel/gcc</pre>}}

Add the following USE flags to /etc/make.conf
{{Console|<pre class="clear"> jpeg ldap spell fam vorbis gstreamer encode mpeg truetype mad xml mikmod xv device-mapper</pre>}}

Depending on your connection speed and the strength of your CPU this can take some time to accomplish. Once this is done we need to issue an few more time consuming commands.

{{Console|<pre class="clear">emerge --sync
etc-update
layman -S
echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf
fixpackages
gcc-config -l (After this, you will re-run gcc-config and choose the appropriate version)
source /etc/profile
eselect env update
</pre>}}

After all that is done ... congrats, your all finished. Everything should be working for you now.

== Acknowledgements ==
* Lythandrel: for proofreading and suggesting grammatical and syntax corrections
* Rand_A: for the start of the list of missing packages
* Wolfden: for more on the list of missing packages
* irc.freenode.net #Sabayon for moral support during the fresh install and long testing/trial period while putting this together
* lxnay: for putting out the best Linux distro to be had
* kakashi: for his patience in helping find what was missing.
Have fun and good computing

Azerthoth

[[Category:Package Management|3.5 Pod adding portageEn]]

Es:HOWTO: 3.5 Pod adding portage

2009-02-26T19:11:31Z

Zambayoni:

{{I18n| [[Ca:HOWTO: 3.5 Pod adding portage|ca]] [[En:HOWTO: 3.5 Pod adding portage|en]] [[Es:HOWTO: 3.5 Pod adding portage|es]] [[Fr:HOWTO: 3.5 Pod adding portage|fr]]}}

== Introducción ==
En primer lugar, es posible tener Sabayon 3.5 Pod (la edición mini de 700 MB) sin seguir los siguiente pasos. Si no tienes interés en compilar tu mismo los programas o en mantener un 100% de compatibilidad con Gentoo, puedes usar el sistema tal y como está usando el sistema de paquetes binario (no compila). Sin embargo, si verdaderamente necesitas compatibilidad con Gentoo o la posibilidad de de instalar paquetes desde alguno de los overlays de Gentoo,sigue los siguientes pasos:

Comenzaremos asumiendo que Sabayon 3.5 Pod acaba de ser recién instalado, una vez reiniciado desde el cd y entrado en el sistema ya funcional.

== Añadiendo soporte para Portage en Sabayon 3.5 Pod ==
Antes de empezar con esto, debes descargar la base de datos de Portage apropiada para tu arquitectura. Con un navegador web, dirígete a:
[http://www.sabayonlinux.org/mod/mirrors/ http://www.sabayonlinux.org/mod/mirrors/] y elige uno de los mirrors disponibles.

Si estás usando la versión 32 bits de Sabayon Pod, debes descargar el archivo: Sabayon-Linux-x86-3.5-Pod.portage.db.tar.bz2

Si estás usando la versión 64 bits de Sabayon Pod, debes descargar el archivo: Sabayon-Linux-x86_64-3.5-Pod.portage.db.tar.bz2

Una vez hayas descargado el archivo apropiado con la base de datos de Portage, debes ejecutar los siguientes comandos:

{{Console|<pre class="clear">su (Asegúrate de poner la contraseña de root cuando lo pida)
cd /var/db/pkg/
mv /home/TuUsuario/Sabayon-Linux-x86-3.5-Pod.portage.db.tar.bz2 . (Para 64 bit, el nombre del archivo sería Sabayon-Linux-x86_64-3.5-Pod.portage.db.tar.bz2 )
tar xjvf Sabayon-Linux-x86-3.5-Pod.portage.db.tar.bz2

***NOTA*** Por favor, ten cuidado al copiar y pegar los comandos o puede que olvides un punto que es parte de un comando.</pre>}}

Ahora estamos preparados para empezar. A partir de aquí, trabajaremos SÓLO en la consola y siendo usuario root. Algunas partes se pueden realizar en mdo gráfico pero es más rápido y sencillo desde consola.
Lo primero, algunos preparativos.

{{Console|<pre class="clear">equo update
equo install entropy
equo world</pre>}}

Esto actualizará el sistema al completo. A partir de aquí podremos crear la compatibilidad con Gentoo. Vamos a instalar todos los programas necesarios de un solo comando. Puede que quieras instalar además gcc separadamente si encuentras errores relacionados con gcc. Se pueden deber a la necesidad de añadir el número de versión.

{{Console|<pre class="clear">equo install portage layman libtool gettext linux-sabayon glibc linux-headers subversion gentoolkit
equo install sys-devel/gcc</pre>}}

Añade las siguientes banderas USE a /etc/make.conf
{{Console|<pre class="clear"> jpeg ldap spell fam vorbis gstreamer encode mpeg truetype mad xml mikmod xv device-mapper</pre>}}

Dependiendo de la velocidad de tu conexión a Internet y la potencia de tu CPU esto puede tardar un tiempo. Una vez esto acabe, debemos realizar algunos comandos mas que también tardan algún tiempo.

{{Console|<pre class="clear">emerge --sync
etc-update
layman -S
echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf
fixpackages
gcc-config -l (Después de esto, debes volver a ejecutar gcc-config y elegir la versión apropiada)
source /etc/profile
eselect env update
</pre>}}

Cuando todo esto haya finalizado... felicidades, has acabado. Todo debería funcionar a partir de ahora.

== Agradecimientos ==
* Lythandrel: por leer y releer y sugerir correcciones sintácticas y gramaticales en la versión inglesa
* Rand_A: por el comienzo de la lista de paquetes necesarios
* Wolfden: por mas paquetes necesarios en la lista
* irc.freenode.net #Sabayon por el apoyo moral durante la instalación y el largo periodo de testeo hasta conseguir finalizar esta guía
* lxnay: por crear la mejor distro Linex que podríamos tener
* kakashi: por su paciencia ayudando a encontrar lo que hacía falta
* Azerthoth: por crear la versión en inglés, la cual he traducido

DHalens

[[Category:Package Management|3.5 Pod adding portageES]]

Es:HOWTO: Incluir Portage en 3.5 Pod

2009-02-26T19:10:53Z

Zambayoni: Es:HOWTO: Incluir Portage en 3.5 Pod moved to Es:HOWTO: 3.5 Pod adding portage: En:Translations

#REDIRECT [[Es:HOWTO: 3.5 Pod adding portage]]

Category:Portage

2009-02-26T19:06:17Z

Zambayoni:

[[Category:Package Management]]

Talk:Portage

2009-02-26T19:04:15Z

Zambayoni: Talk:Portage moved to Talk:En:Portage

#REDIRECT [[Talk:En:Portage]]

Portage

2009-02-26T19:04:15Z

Zambayoni: Portage moved to En:Portage

#REDIRECT [[En:Portage]]

Talk:En:Portage

2009-02-26T19:04:15Z

Zambayoni: Talk:Portage moved to Talk:En:Portage

How can I get the Sabayon portage dir's ?

Pl:Strona Glowna

2009-02-26T19:01:05Z

Zambayoni: Pl:Strona Glowna moved to Pl:Main Page: En:Translations

#REDIRECT [[Pl:Main Page]]

Ca:Editing Guidelines

2009-02-26T18:58:29Z

Zambayoni:

{{I18n|[[Ca:Editing_Guidelines|ca]] [[En:Editing_Guidelines|en]] [[Es:Editing_Guidelines|es]] [[Fr:Editing_Guidelines|fr]] [[It:Editing_Guidelines|it]]}}

''Guia d’edició:'' Com fer articles decents pel wiki.
{{Warning| '''En construcció'''}} – Això és segur!!

== Directrius ==

*Feu articles decents, i feu-los a consciència, entenent que si veieu que no són útils, el millor és que no els pengeu.
*Assegureu-vos que '''TOTA''' la informació dels articles és correcta. Si la informació que pengeu no és correcta o li falten passos, probablement algú interpretarà que és errònia i l’editarà o, pitjor encara, l’esborrarà.
*Useu el codi correcte segons el tipus de línia.

{{Code|Python|<pre class="clear">
def chklayman(pkgname):
lst = os.listdir(laymandir)
for line in lst:
if os.path.isdir(laymandir+line+"/"+pkgname):
print 'Package found in '+laymandir+line+'/'+pkgname
return 1 </pre>}}
<nowiki>{{Code|Inseriu el nom del codi aquí|<pre class="clear">
(Inseriu el codi aquí) </pre>}}</nowiki> Per aconseguir un quadre de text com l'anterior.

{{File| /etc/X11/xorg.conf|<pre class="clear"> # **********************************************************************
# Screen sections.
# **********************************************************************

Section "Screen"

# The Identifier, Device and Monitor lines must be present

Identifier "Screen 1"
Device "VESA"
Monitor "Generic Monitor"
Option "AddARGBGLXVisuals" "true"

</pre>}}
<nowiki>{{File| (Nom del fitxer)| <pre class="clear"> (Contingut del fitxer) </pre>}}</nowiki> Useu aquest quadre de text pel contingut dels fitxers.

{{Console|<pre class="clear"> # emerge --sync</pre>}}
Useu <nowiki>{{Console| <pre class="clear"> (Ordres de la terminal i informació) </pre>}}</nowiki> pel quadre de text de la terminal

I recordeu tancar tots els quadres de text amb una instrucció </pre>, perquè sino tot el vostre text acabarà dins un gran quadre de text.

*Useu <nowiki>{{Commandgui|<highlighted word>}}</nowiki> per ressaltar paraules clau o passos importants que s’han de buscar dins un quadre de text.

*Si heu d’escriure advertències com "Pot causar danys en el sistema " o "Useu amb precaució " llavors <nowiki>{{Warning| <Insert Warning Here>}}</nowiki>

*Si heu d’escriure una nota com "Feu emerge --sync abans de fer el següent pas" o "Pot ser que us apareguin més paquets que els que necessiteu" llavors useu la <nowiki>{{Note| Insert Note Here}}</nowiki> plantilla.

*Si us plau, no envieu spam. Si envieu spam us bloquejarem la IP sense excepcions.

*Mantingueu els articles senzills. No hi inclogueu text sense utilitat, només el que sigui necessari. Malgrat tot, si necessiteu escriure alguna cosa com la sortida de lspci o algun text llarg, useu un quadre de text amb barra de desplaçament, usant una de les tres plantilles anteriors.

*Per últim: si podeu anar eliminant o editant articles inútils o antiquats ens fareu un favor. Gràcies!

[[Category:Sabayon Wiki|Editing GuidelinesCa]]

It:Editing Guidelines

2009-02-26T18:56:46Z

Zambayoni:

{{I18n|[[Ca:Editing_Guidelines|ca]] [[En:Editing_Guidelines|en]] [[Es:Editing_Guidelines|es]] [[Fr:Editing_Guidelines|fr]] [[It:Editing_Guidelines|it]]}}

''Linee Guida:'' Una guida alla creazione di articoli wiki decenti e funzionanti.
{{Warning/It| '''Lavori in corso'''}} - Tanto per chiarire.

== Linee guida ==

*Creare articoli decenti e renderli utili. Questo significa che se non ne se vede la necessità non è necessario inserli
*Assicurarsi che '''TUTTE''' le informazioni contenute negli articoli siano corrette. Per fare questo l'autore deve controllare passo passo i dati inseriti diversamente, se l'informazione non è corretta, i dati saranno corretti o, nella peggiore delle ipotesi, rimossi.
*Utilizzate la codifica esatta a seconda del tipo di informazione

{{Code|Python|<pre class="clear">
def chklayman(pkgname):
lst = os.listdir(laymandir)
for line in lst:
if os.path.isdir(laymandir+line+"/"+pkgname):
print 'Package found in '+laymandir+line+'/'+pkgname
return 1 </pre>}}
<nowiki>{{Code|Inserire il nome del codice in questa posizione|<pre class="clear">
(Inserire il codice) </pre>}}</nowiki> per ottere un risultato come nel box visualizzato qui sopra.

{{File| /etc/X11/xorg.conf|<pre class="clear"> # **********************************************************************
# Screen sections.
# **********************************************************************

Section "Screen"

# The Identifier, Device and Monitor lines must be present

Identifier "Screen 1"
Device "VESA"
Monitor "Generic Monitor"
Option "AddARGBGLXVisuals" "true"

</pre>}}
<nowiki>{{File| (Nome del file)| <pre class="clear"> (Contenuti del file) </pre>}}</nowiki> tag per questo box, da utilizzare per contenuti dei file.

{{Console|<pre class="clear"> # emerge --sync</pre>}}
Use <nowiki>{{Console| <pre class="clear"> (comandi console & info) </pre>}}</nowiki> per console input/output

Bisogna ricordare di chiudere ogni tag con </pre>, in caso contrario tutto il testo inserito verrà visualizzato in un unico grande box.

*Utilizzare <nowiki>{{Commandgui|<parole in evidenza>}}</nowiki> per evidenziare parole chiave o codici particolari che devono essere visualizzati in una casella di dialogo.

*Se è necessario mostrare avvisi quali '''può danneggiare il tuo sistema''' o '''usare con cautela''' utilizzare il template <nowiki>{{Warning| <Inserire il testo dell'avviso qui>}}</nowiki>

*Se è necessario evidenziare una note quale '''eseguire emerge --sync prima di compiere questa operazione''' o '''È possibile che il risultato contenga anche dati non necessari''' allora utilizzare il template <nowiki>{{Note| Inserire l'annotazione in questa posizione}}</nowiki> template.

*Niente spam. In questo caso l'IP e l'utente verranno bloccati senza alcuna eccezione.

*Mantenere l'articolo semplice. Non includere cose inutili. Inserite semplicemente quello che è necessario. Se si deve inserire qualche output o del codice molto lungo allora è necessario utilizzare uno dei tre template che abbiamo mostrato sopra.

*Se vi è possibile rimuovete gli articoli inutili o obsoleti o aggiornateli. Grazie!

[[Category:Sabayon Wiki|Editing GuidelinesIt]]

Es:Equo (Community Functions)

2009-02-26T18:47:17Z

Zambayoni:

{{I18n| [[Ca:Equo (Community Functions)|ca]] [[En:Equo_(Community_Functions)|en]] [[Es:Equo_(Community_Functions)|es]] [[Fr:Equo (Community Functions)|fr]]}}

{{Construction}}

{{warning| Estas características son experimentales.}}
{{warning| Cambiar las banderas USE puede causar una variación de los símbolos exportados de las librerías que puede derivar en problemas cuando se mezclan paquetes. Este problema será resuelto en la próxima versión de sabayon. Por el momento, simplemente presta atención.}}
{{warning| Mantener un repositorio no es apto para novatos.}}

{{note|Si ejecutas "equo --help" obtendrás una lista de los comandos disponibles. Pese a que todo debería de funcionar bien, esta característica sigue siendo experimental y necesita de ayuda en forma de comentarios por parte de quienes la usen.}}

==Configurando un Repositorio Community==
{{Es:Main|Es:HOWTO: Configurar un Repositorio Community|Configurando un Repositorio Community}}

==Administración de Paquetes==
Equo tiene algunas funciones avanzadas para manejar Repositorios Community. Esta página está pensada para dar una visión más detallada de las habilidades de Equo para manejar repositorios. Hay muchas cosas que puedes hacer con los Repositorios Community; sé paciente y lee detenidamente lo que ponga Equo.

===Añadiendo Paquetes===
{{note|Por favor, asegúrate de que tienes Portage completamente sincronizado y funcionando}}
1. Emerge el paquete que quieras
{{console|<pre class="clear">emerge -v1 <paquete></pre>}}
En este punto, cualquier función estándar de [[portage|Portage]] puede ser usada, por ejemplo para cambiar las banderas USE
{{console|<pre class="clear">USE="bandera1 -bandera2" emerge -v1 <paquete></pre>}}
{{note|Pese a que es posible hacer emerge a múltiples paquetes, NO es recomendable ya que las versiones actuales de Equo tienden a perder los primeros paquetes que son compilados}}
# Ejecuta el comando de estado para comprobar que tu repositorio está funcionando
{{console|<pre class="clear">equo community repo <la_cadena_de_identificación_de_tu_repositorio> status</pre>}}
2. Registra el sistema buscando paquetes y empaquétalos usando la función de actualizar repositorios
{{console|<pre class="clear">equo community repos update</pre>}}
Esto mostrará una lista de paquetes que han sido añadidos y te preguntará si quieres añadirlos a tu repositorio. Si quieres hacerlo, escribe yes. Si no quieres ser preguntado para esto, puedes usar el parámetro --noask
{{console|<pre class="clear">equo community repos update --noask</pre>}}
3. Ahora los paquetes han sido añadidos a la base de datos local, todo lo que necesitas es sincronizar tus mirrors. Para ello, ejecuta este comando:
{{console|<pre class="clear">equo community mirrors sync</pre>}}
Esto conectará con tu/s mirror/s y subirá los paquetes, md5sums, una nueva revisión de la base de datos y feeds RSS, etc.
4. Si has añadido tu propio repositorio como cliente, verás que hay actualizaciones disponibles.
5. ¡Felicidades!
===Eliminando Paquetes===

==Administración del Mirror==
==Administración de la Base de Datos==

[[Category:Entropy|Equo Community FunctionsEs]]

En:Equo (Community Functions)

2009-02-26T18:45:57Z

Zambayoni:

{{I18n| [[Ca:Equo (Community Functions)|ca]] [[En:Equo (Community Functions)|en]] [[Es:Equo (Community Functions)|es]] [[Fr:Equo (Community Functions)|fr]]}}

{{Construction}}

{{warning|These features are currently experimental.}}
{{warning|Changing USE flags can cause a variation of exported library symbols which can cause troubles when mixing packages. This issue is going to be solved in the next release, for now, just pay attention!}}
{{warning|Maintaining a repository is not for newbies.}}

{{note|If you run "equo --help" you will also find the list of available commands. Even if all should work quite fine, this feature is still experimental and needs your feedback!}}

==Setting Up A Community Repository==
{{main|En:HOWTO: Set Up A Community Repository|Setting up a Community Repo}}

==Package Management==
Equo has some advanced functions for managing community repositories, this page is designed to give a more detailed overview of equos community repository management abilities.There are a lot of things you can do on Community Repositories, just be patient and read the output carefully.

===Adding Packages===
{{note|Please make sure you have a fully synced and working portage system}}
1. Emerge the package of your choosing
{{console|<pre class="clear">emerge -v1 <package_name> </pre>}}
At this stage any standard [[portage|Portage]] functions can be used, for instance to change use flags
{{console|<pre class="clear">USE="flag1 -flag2" emerge -v1 <package_name></pre>}}
{{note|While it is possible to emerge multiple packages it is NOT recommended as current versions of equo tend to miss the first few packages that are compiled}}
# Run the status command to check your repository is working
{{console|<pre class="clear">equo community repo <your_repo_ID_here> status</pre>}}
2. Scan the system for new packages and package them using the repos update function
{{console|<pre class="clear">equo community repos update</pre>}}
This will present you with a list of packages that have been added, and will ask if you want to add them to your repo, if you do, select yes. If you don't want to be prompted about this you can use the --noask amendment, for instance
{{console|<pre class="clear">equo community repos update --noask</pre>}}
3. Now the packages have been added to the local database all you need to do is sync your mirrors, to do this simple run this command:
{{console|<pre class="clear">equo community mirrors sync</pre>}}
This will connect to your mirror(s) and upload the packages, md5sums, a new database revision and RSS feeds etc
4. If you have added your own repository as a client you will see that there are updates available!
5. Congratulations!
===Removing Packages===

==Mirror Management==
==Database Management==

[[Category:Entropy|Equo Community FunctionsEn]]

Es:Equo (Funciones Community)

2009-02-26T18:30:02Z

Zambayoni: Es:Equo (Funciones Community) moved to Es:Equo (Community Functions): En:Translations

#REDIRECT [[Es:Equo (Community Functions)]]

Es:Lista de funciones de Equo

2009-02-26T18:27:21Z

Zambayoni: Es:Lista de funciones de Equo moved to Es:List Of Equo Functions: En:Translations

#REDIRECT [[Es:List Of Equo Functions]]

Es:HOWTO: Run FrostWire

2009-02-26T18:21:59Z

Zambayoni:

{{i18n|[[En:HOWTO: Run FrostWire|En]] [[Es:HOWTO: Run FrostWire|Es]]}}

Siguiendo estos pasos usted tendrá FrostWire trabajando en poco tiempo. Yo he probado esto en Sabayon Linux 3.5 Loop 1 version 32-Bit.

{{Note| Asegure de correr '''emerge --sync && layman -S''' en un Terminal antes de proceder.}}

'''Paso 1.'''
Hágase Root en un Terminal.
{{Console| <pre class="clear">su</pre>}}
Entre su contraseña cuando se te sea solicitada.

'''Paso 2.'''
Instale Java Runtime de Sun.
{{Console| <pre class="clear"># emerge sun-jre-bin</pre>}}

'''Paso 3.'''
Instale FrostWire.
{{Console| <pre class="clear"># emerge frostwire-bin</pre>}}

'''Paso 4.'''
Este paso ha sido prestado de [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 Compiz-Fusion Update Guide].
{{Console| <pre class="clear"># echo "x11-libs/libX11 xcb" >> /etc/portage/package.use
# emerge x11-libs/libX11
# CFLAGS="-DNDEBUG" emerge x11-libs/libxcb</pre>}}

'''Paso 5.'''
Haga el Script de Frostwire ejecutable.
{{Console| <pre class="clear"># chmod +x /usr/share/frostwire/runFrostwire.sh</pre>}}

'''Paso 6.'''
Haga clic en la entrada de FrostWire en su menú principal, o solamente escriba "frostwire" (Sin comillas) en un Terminal (Como un usuario normal) y haga clic enter. Deberá de trabajar ahora..

Es:COMO: Instalar FrostWire

2009-02-26T18:19:07Z

Zambayoni: Es:COMO: Instalar FrostWire moved to Es:HOWTO: Run FrostWire: En:Translations

#REDIRECT [[Es:HOWTO: Run FrostWire]]

HOWTO: Run FrostWire

2009-02-26T18:18:36Z

Zambayoni: HOWTO: Run FrostWire moved to En:HOWTO: Run FrostWire

#REDIRECT [[En:HOWTO: Run FrostWire]]

Who Created Linux

2009-02-26T18:11:20Z

Zambayoni:

{{delete}}
In 1983 Richard Stallman started the GNU Project with the goal of creating a UNIX-like, POSIX-compatible operating system composed entirely of free software. Development began in 1984, and a year later he created the Free Software Foundation and wrote the first draft of the GNU General Public License (GPLv1). By the early 1990s, the project had produced or collected many necessary operating system components, including libraries, compilers, text editors, and a Unix shell, and the mid-level portions of the OS were almost complete. The upper level could be supplied by the X Window System, but the lower level which consisted of a kernel, device drivers, and daemons was still incomplete.

In 1990 the GNU project began developing the Hurd kernel which was based on the Mach microkernel, but development proved difficult and proceeded slowly.

In 1991, Linus Torvalds began to work on the Linux kernel while he was attending the University of Helsinki. Torvalds originally created the Linux kernel as a non-commercial replacement for the Minix kernel; he later changed his original non-free license to the GPLv2, which differed primarily in that it also allowed for commercial redistribution. Although dependent on the Minix userspace at first, work from both Linux kernel developers and the GNU project allowed Linux to work with GNU components. Thus Linux filled the last major gap in running a complete, fully functional free operating system.

''Taken from [http://en.wikipedia.org/wiki/Linux| wikipedia.org]''

Tux

2009-02-26T18:10:03Z

Zambayoni:

{{delete}}
http://www.isc.tamu.edu/~lewing/linux/sit3-shine.7.gif
 
Tux is the penguin who is the mascot of Linux.
He stars in many games and applications in and around the open source community.
He was created by Larry Ewing. See http://www.isc.tamu.edu/~lewing/linux/ for more information.

Dv 9210us

2009-02-26T18:01:43Z

Zambayoni:

== Sabayon on a DV 9210us , HP dv9000 series==

'''This will be my log on how I installed Sabayon on an HP DV9000 series pavillion laptop and the hangups I have doing it'''
I'm no power user but I have a bit of experience with Linux. I fell in love with the way Sabayon put their distro together and felt I should give back to the community. HP made no new freinds with this laptop but since I invested the money in it I might as well give it a shot.

DISCLAIMER: You follow the guidelines and info here at your own risk!! Dont hold anyone responsible but yourself. You have been warned.

On the lighter side of things anyone desiring to place info related to this topic please feel free as I will probably be learning from it too.

== My Thank You List ==
I want to say thanks to these people for giving me help mostly in the #Sabayon live help irc located at.
'irc.oftc.net #Sabayon'.
The developers at Sabayon Linux and Gentoo.
Appleman1234,rubengonc.

== Version of Sabayon Linux ==
As root using "''uname -a''":

Linux localhost 2.6.19-gentoo-r4 #1 SMP Sat Jan 6 03:12:26 UTC 2007 x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-52 AuthenticAMD GNU/Linux

== What works out of the Install: ==
The Install, which I must say worked without a hitch (Unlike Ubuntu which required a 'napic' command to boot), Installed smoothly (Great Job to the support staff on that one!!).
The Video, USB, keyboard, mouse, 3d AIGLX, Power management (when enabled), DVD RW, Ethernet ,as I know of, all worked automagically. It plays DVD's, Beryl worked with absolutely no (You heard it) NO extra configuration.VGA Out works.

== Concieved Issues: ==

Concieved issues:
#The sound is working but I have a problem getting it to work with Netscape and Flash. '''NOTE: The fix for this on the forums.'''
#Wifi appears to be working out of the box but this is the third Install because of Wifi. What I did to get the Wifi to work is leave it switched off for the install. (Thats all I did differently) Then I switch it on after the system is fully booted up and it works. I tried using the 'bwml6.inf' drivers from the Vista Install and 'ndiswrapper' it didn't work. But bcm43xx does (see the bcm43xx guide on this wiki for more information) (I know, weird huh?). I even tried Linuxant.
#.The quick play bar isn't working as of yet.
#.I don't even know what programs to use to try and get the web cam working.
#. Haven't tested the microphones.
#. Haven't tested the modem.
#. Haven't tested the TV out.
#. Other than the quick bar on the Docking station, it appears to work.

== Hardware on board: ==

I will be placing a list of all the hardware I can get from this laptop here.

Using "''lspci -v''" as root:
----
<pre>
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [e0] HyperTransport: MSI Mapping

00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: 66MHz, fast devsel

00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: 66MHz, fast devsel

00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: 66MHz, fast devsel

00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0

00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] #00 [00fe]
Capabilities: [fc] #00 [0000]

00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: 66MHz, fast devsel

00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
Flags: 66MHz, fast devsel

00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: b4000000-b7ffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000d0100000
Capabilities: [40] #0d [0000]
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit Queue=0/1 Enable-
Capabilities: [60] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot ) IRQ 0
Capabilities: [100] Virtual Channel

00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: b8000000-bbffffff
Capabilities: [40] #0d [0000]
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit Queue=0/1 Enable-
Capabilities: [60] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot ) IRQ 0
Capabilities: [100] Virtual Channel

00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2) (prog-if 00 [VGA])
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 18
Memory at b2000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at b1000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at 88000000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit Queue=0/0 Enable-

00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [e0] HyperTransport: MSI Mapping

00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 1d00 [size=128]

00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: 66MHz, fast devsel, IRQ 10
I/O ports at 3040 [size=64]
I/O ports at 3000 [size=64]
Capabilities: [44] Power Management version 2

00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
Memory at b0040000 (32-bit, non-prefetchable) [size=256K]

00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
Memory at b0004000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2

00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
Memory at b0005000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Debug port
Capabilities: [80] Power Management version 2

00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1) (prog-if 8a [Master SecP PriP])
Subsystem: Unknown device f03c:30b7
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 3080 [size=16]
Capabilities: [44] Power Management version 2

00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1) (prog-if 85 [Master SecO PriO])
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23
I/O ports at 30c0 [size=8]
I/O ports at 30b4 [size=4]
I/O ports at 30b8 [size=8]
I/O ports at 30b0 [size=4]
I/O ports at 3090 [size=16]
Memory at b0006000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Capabilities: [b0] Message Signalled Interrupts: 64bit Queue=0/2 Enable-
Capabilities: [cc] HyperTransport: MSI Mapping

00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=64
Memory behind bridge: bc000000-bc0fffff
Capabilities: [b8] #0d [0000]
Capabilities: [8c] HyperTransport: MSI Mapping

00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
Memory at b0000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit Queue=0/0 Enable-
Capabilities: [6c] HyperTransport: MSI Mapping

00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20
Memory at b0008000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 30e0 [size=8]
Capabilities: [44] Power Management version 2

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel
Capabilities: [f0] #0f [0010]

03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
Subsystem: Hewlett-Packard Company Unknown device 1363
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at b8000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 2
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Capabilities: [d0] Express Legacy Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel

07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, medium devsel, latency 64, IRQ 5
Memory at bc000000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [dc] Power Management version 2

07:05.1 Class 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, medium devsel, latency 64, IRQ 7
Memory at bc000800 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

07:05.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, medium devsel, latency 0, IRQ 11
Memory at bc000c00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

07:05.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: medium devsel, IRQ 11
Memory at bc001000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

07:05.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: medium devsel, IRQ 11
Memory at bc001400 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
</pre>

[[Category:Laptops]]

ControlCenter Proposal1

2009-02-26T17:59:33Z

Zambayoni: Undo revision 6224 by Zambayoni (Talk)

This isn't a complete proposal yet, just putting some thoughts out flouthing around in my head...

* Framework
** Manages a collection of configuration files (I would suggest XML) that describe the modules and how the framework should use them.
** Acts as the 'Controller' in the Model-View-Controller pattern.
** Language: Should be a language that can bind to other languages relatively easy.

* Modules
** Each module has a configuration file needed by the framework (I would suggest using XML)
** Each module uses the same interface that is called by the framework
** Each module should consist of 2 parts a 'View' and a 'Model' interacting through the 'Controller (our framework)'
***View: provides user interaction
***Model: provides the functionality

NOTE: making the modules standalone tools and letting the framework spawn those processes would probably ease the language binding problem, but has this other issues? Maybe a second proposal for this... Need to think about it...

NOTE: shouldn't it be possible to create a framework that is able to deal with both embedded and standalone tools... Need to think about it...

Cleanup

2009-02-26T17:57:10Z

Zambayoni:

Category:HDSPA

2009-02-26T17:21:37Z

Zambayoni: New page: Category:Networking

[[Category:Networking]]

HOWTO: Huawei e220

2009-02-26T17:21:04Z

Zambayoni:

== Howto install and setup huawei e220 HSDPA usb modem ==
----

'''Downloading OOZIE's workaround-kit for e220'''

'''1''') Open konsole (if you are using kde, press '''alt-f2''' and type '''konsole'''

'''2''') We need have root acces when installing it so type '''su''' and entter your root's password

'''3''') Go to directory where you want to download the pkg. it's ok to download it to your home folder also.

'''4''') type '''wget http://oozie.fm.interia.pl/src/huawei.tar.bz2'''

'''5''') extract huawei.tar.bz2

'''6''') type cd /where/huawei.tar.bz2/have/extracted/

'''7''') type '''make generic_install'''

'''8''') type '''make config'''

'''9''') plug in your e220 and wait untill blue led is blinking

'''10''') type '''pppd call huawei-e220''' and you are connected to internet :)

[[Category:HDSPA|Huawei e220]]

HOWTO: Huawei e220 and e169

2009-02-26T17:20:59Z

Zambayoni:

== '''Huawei e220 and e169''' ==

----

This howto explains howto install/use e220 and e169 hsdpa modems in sabayon. Huawei e220 and e169 are supported natively by Linux, over usbserial.ko (usbserial-generic) interface. Linux kernel versions prior to 2.6.20 have some problems with it, as the SCSI CDROM fakevolume with drivers for Microsoft systems gets automounted by usbstorage.ko module, preventing serial device /dev/ttyUSB0 from working properly.

----

''Huawei e220'''

Main Features

HSDPA/UMTS/EDGE/GPRS/GSM

HSDPA packet data service with a maximum transmission rate of 3.6Mbps

UMTS packet data service with a maximum transmission rate of 384kbps

EDGE packet data service with a maximum transmission rate of 236.8kbps

----

"Huawei e169"

Main Features:

HSDPA/UMTS900/2100MHz

GSM/GPRS/EDGE850/900/1800/1900MHz

Support 7.2Mbps HSDPA services

MicroSD Card Slot

----

1) You need huawei workaround package http://oozie.fm.interia.pl/src/huawei.tar.bz2

2) Extract package to directory (default is huawei)

3) Run make generic_install as root

4) Run make config as root

Next step is to edit /etc/wvdial.conf with your favourite text editor as root

Here is sample of my wvdial.conf

[Dialer Defaults]

Modem = /dev/ttyUSB0

Baud = 3600000

Init2 = ATZ

Init3 = ATQ0 V1 E1 S0=0 &C1 &D2

Phone = *99#

Username = ppp

Password = ppp

Ask Password = 0

Dial Command = ATDT

Stupid Mode = 1

Compuserve = 0

Idle Seconds = 0

ISDN = 0

Auto DNS = 1

When you type wvdial it will connect to internet with full speed as default.

If you want to connect to internet using gprs only add this also to your wvdial.conf

[Dialer gprs]

Modem = /dev/ttyUSB0

Baud = 115200

Init2 = ATZ

Init3 = ATE0V1&D2&C1S0=0+IFC=2,2

ISDN = 0

Modem Type = Analog Modem

To connect internet using gprs only type wvdial gprs

Enjoy your huawei :)

[[Category:HDSPA|Huawei e220 and e169]]

HOWTO: Avant Window Navigator

2009-02-26T17:15:44Z

Zambayoni:

{{Warning| Warning!! This method is able to grab unstable code that is primarily used for beta testing and development purposes only. If you would like to grab the latest stable code, follow this guide: [[HOWTO: Avant Window Navigator (AWN)]]}}

Avant Window Navigator (AWN) is a nice application dock for Gnome (might work in KDE, I havent tested it).

When writing this howto, the ebuild for AWN was not working. So this is how to build and install it from the svn sources.

==Install bzr==

<pre>
sudo emerge bzr
</pre>
If sudo does not work try su

== Fetch the Sources ==

To download the bzr sources, open a terminal and type the following:
<pre>
bzr checkout http://bazaar.launchpad.net/~awn-core/awn/trunk avant-window-navigator
</pre>

Once it is done downloading, enter the directory so we can begin compiling
<pre>
cd avant-window-navigator
</pre>

== Compile and Install ==

Now we are ready to compile and install, the following commands will take care of that:
<pre>
./autogen.sh
make
sudo make install
</pre>
NOTE: If you are using 3.4a and sudo doesn't work for you, either use "su -" command to become root, or read [http://www.sabayonlinux.org/wiki/index.php?title=HOWTO:_Enable_sudo HOWTO: Enable sudo]

== Fix Libraries ==

For some reason, AWN installs its libraries in /usr/local/lib instead of in /usr/lib. So you will get an error trying to run it. To solve this, I just symlinked the libraries like this:
<pre>
sudo ln -s /usr/local/lib/libawn.so.0.0.1 /usr/lib/libawn.so
sudo ln -s /usr/local/lib/libawn.so.0.0.1 /usr/lib/libawn.so.0
</pre>

== Run the Program ==

After fixing those libraries, AWN should run, you can run it in a terminal like this:
<pre>
avant-window-navigator &
</pre>

It should have created a menu entry under Accessories as well

===Auto Start at Login===

'''xfce4'''

Open the main menu and navigate to Settings -> Autostarted Applications

Click on add and enter the following information:
Name: Avant Window Navigator
Command: avant-window-manager

That should be it! Enjoy your new dock!

[[Category:Desktops|Avant Window Navigator]]

HOWTO: Installing CUPS Print to PDF driver

2009-02-26T17:15:06Z

Zambayoni:

==Introduction==

Although some applications (e.g. OpenOffice.org) have built-in support for 'printing' PDF files, and for applications without built-in support there is an installed Print to File (PDF) driver with Sabayon Linux, for some reason the Print to File (PDF) 'printer' does not appear in the list of available printers when I select Print in some applications. Therefore, if you want to install the CUPS driver to print to a PDF file, you can use the procedure given below.

===Installation and configuration===

{{Note|In the instructions below the GNOME printer manager is used to set up the cups-pdf driver. However you could instead use the CUPS browser manager (http://localhost:631/) or KDE printer manager to do it.}}

1. In a Terminal window, type the following as root:

{{Console| <pre class="clear">
# emerge cups-pdf
</pre>}}
or, alternatively, if you prefer to use Entropy instead of Portage:
{{Console| <pre class="clear">
# equo install cups-pdf
</pre>}}

2. K Menu > Applications > Settings > GNOME Settings > Printing

3. Double-click on 'New Printer'

4. If not already selected, set 'Printer Type:' to 'Local Printer'

5. Set 'Use a detected printer:' to 'Virtual PDF Printer'

6. Click 'Forward'

7. Set 'Select Manufacturer:' to 'Generic', and set 'Model:' to 'postscript color printer rev4' (or 'CUPS-PDF' if that is listed)

8. Leave 'Driver:' as 'Standard (Suggested)'

9. Click 'Forward'

10. Enter a name of your choice (must be without spaces) in 'Enter a Name:', e.g. Print_to_PDF_file

11. Enter a description of your choice in 'Enter a Description:', e.g. Virtual printer (print to PDF file)

12. Click 'Apply'.

13. When you select Print_to_file_PDF from the list of available printers when you come to print from an application, the PDF file will be saved in the directory /var/spool/cups-pdf/<your username>/. Note that that directory will be created automatically the first time you 'print' to PDF.

14. Optionally, you can create a shortcut (Desktop Config File) on your Desktop to open the directory mentioned in Step 13 above.

15. Optionally, edit the file /etc/cups/cups-pdf.conf as root to get cups-pdf to 'print' PDF documents to your desktop instead of /var/spool/cups-pdf/<your username>/, by changing the line:

{{File|/etc/cups/cups-pdf.conf| <pre class="clear">
#Out /var/spool/cups-pdf/${USER}
</pre>}}
to
{{File|/etc/cups/cups-pdf.conf| <pre class="clear">
Out ${HOME}/Desktop
</pre>}}

16. Optionally, if you prefer to be prompted for a file name so that you can save the PDF file wherever you want and give it the name you want, then do the following instead of Items 14 and 15 above:

Make sure the package '''zenity''' is installed (it should be, by default, with Sabayon Linux):

{{Console| <pre class="clear">
# emerge -s zenity
Searching...
[ Results for search key : zenity ]
[ Applications found : 1 ]

* gnome-extra/zenity
Latest version available: 2.24.0
Latest version installed: 2.22.1
Size of files: 2,183 kB
Homepage: http://www.gnome.org/
Description: Tool to display dialogs from the commandline and shell scripts
License: LGPL-2

#
</pre>}}

If zenity is not installed then install it using either Portage or Entropy:

{{Console| <pre class="clear">
# emerge zenity
</pre>}}
or
{{Console| <pre class="clear">
# equo install zenity
</pre>}}

Using a text editor of your choice, create the following script in your home directory and give it a meaningful name such as cups-pdf_script.sh:

{{File|cups-pdf_script.sh| <pre class="clear">
#!/bin/bash
CURRENT_PDF="${1}"
CURRENT_USER="${2}"
DISPLAY=:0.0
export DISPLAY
XAUTHORITY=/home/${CURRENT_USER}/.Xauthority
export XAUTHORITY
PDFNAME=$(zenity --file-selection --save --confirm-overwrite)
mv "$CURRENT_PDF" "$PDFNAME"
</pre>}}

Make the file executable:

{{Console| <pre class="clear">
# chmod ugo=rwx cups-pdf_script.sh
</pre>}}

Edit the file /etc/cups/cups-pdf.conf, find the line starting "#PostProcessing" and change it to:

{{File|/etc/cups/cups-pdf.conf| <pre class="clear">
PostProcessing /home/<your user name>/cups-pdf_script.sh
</pre>}}

Restart CUPS:

{{Console| <pre class="clear">
# /etc/init.d/cupsd restart
</pre>}}

Now, when you select the Print_to_PDF_file virtual printer in your applications, a pop-up window will appear allowing you to select the target directory for the PDF file and to enter a file name of your choice.

Authored by Fitzcarraldo on 29.05.07. Significant rewrite on 09.01.09.

[[Category:Printing|Installing CUPS Print to PDF driver]]

Category:Printing

2009-02-26T17:11:12Z

Zambayoni: New page: See also http://en.gentoo-wiki.com/wiki/Category:Printing Category:Hardware Category:HOWTOs

See also http://en.gentoo-wiki.com/wiki/Category:Printing

[[Category:Hardware]]
[[Category:HOWTOs]]

HOWTO: Belkin Bluetooth Keyboard

2009-02-26T17:08:27Z

Zambayoni:

{{Note|'''Warning 19 May 2007:''' This article may be out of date and may not work as expected with the most recent releases of Sabayon Linux (versions 3.4* and above). The procedure described in this article works with the Bluetooth software installed from the Sabayon Linux 3.3 LiveDVD. However, if you emerge the latest version of the BlueZ Bluetooth software then it will no longer work, as the way the Bluetooth software works has been changed: the files mentioned in Step 2 and Step 3 have been altered and the way a PIN is obtained has changed from the earlier version of the Bluetooth software.}}

==Procedure to get Sabayon Linux x86-64 3.26 to work with a Belkin Bluetooth keyboard (model F8T040), 14.03.07==

Carry out the following steps in the order given:

'''STEP 1'''

The first thing you need to do is find the MAC address of the Bluetooth keyboard. To do this, press the Connect button on the underside of the Belkin Bluetooth keyboard, and in a Terminal window type:

{{Console| <pre class="clear"># hcitool scan
Scanning ...
00:03:C9:52:14:80 Belkin Keyboard</pre>}}

Your MAC address will be different, so just use it instead of "00:03:C9:52:14:80" in the Steps that follow.

'''STEP 2'''

I believe the following is required to enable 'automatic' reconnection with the keyboard a) when it goes to sleep and you then press a key for several seconds, and b) when the PC boots and you then press a key for several seconds.

{{Console| <pre class="clear"># sudo gedit /etc/conf.d/bluetooth</pre>}}

Change
HIDD_ENABLE=false
to
HIDD_ENABLE=true

Change
HIDD_OPTIONS=””
to
HIDD_OPTIONS=”--connect 00:03:C9:52:14:80”

(HCID_ENABLE=true should already be in the file.)

'''STEP 3'''

{{Console| <pre class="clear"># sudo gedit /etc/bluetooth/hcid.conf</pre>}}

Add the following at the end of the file:

{{File|/etc/bluetooth/hcid.conf|<pre class="clear">device 00:03:C9:52:14:80 {
name "Belkin Keyboard";
auth enable;
encrypt enable;
}
</pre>}}

'''STEP 4'''

{{Console| <pre class="clear"># sudo /etc/init.d/bluetooth restart
* Caching service dependencies ... [ ok ]
* Shutting down Bluetooth ...
* Stopping rfcomm ... [ ok ]
* Stopping hidd ... [ ok ]
* Stopping sdpd ... [ ok ]
* Stopping hcid ... [ ok ]
* Starting Bluetooth ...
* Starting hcid ... [ ok ]
* Starting sdpd ... [ ok ]
* Starting hidd ... [ ok ]
* Starting rfcomm ... [ ok ]
</pre>}}

A window entitled KDE Bluetooth Framework may pop up stating “Failed to connect to the SDP server. Please make sure that sdpd is running; without it other devices will not be able to find out which services your computer offers.” I just ignored it and clicked OK.

'''STEP 5'''

Do the following just to check that the keyboard is still paired with Sabayon:

{{Console| <pre class="clear"># hcitool scan
Scanning ...
00:03:C9:52:14:80 Belkin Keyboard
</pre>}}

If the scan does not find the keyboard any more, press the Connect button on the underside of the Belkin Bluetooth keyboard and repeat the hcitool scan command.

'''STEP 6'''
{{Console| <pre class="clear"># sudo hidd --connect 00:03:C9:52:14:80</pre>}}

From now on the Bluetooth keyboard should work. If you press a key you should be able to see what you type appear on screen.

'''NOTES'''

{{Note|'''Note 1:''' If you do not type for a prolonged period of time, the Bluetooth keyboard will go to sleep (to prolong battery life). To reconnect the keyboard, press any key (Ctrl is a good choice, as it is non-printing) for a few seconds and this should automatically reconnect the keyboard. You should then be able to type again.

Similarly, following a reboot, the keyboard should connect automatically if you press any key for a few seconds.}}

{{Note|'''Note 2:''' The Bluetooth keyboard still works even if I omit Step 4. Nevertheless it does no harm to perform Step 4 and it presumably refreshes the Bluetooth configuration file so that, even before you reboot for the first time, the keyboard will be able to reconnect automatically as described in Note 1 if it goes to sleep.}}

----

HowTo was taken directly from [http://www.sabayonlinux.org/forum/viewtopic.php?t=3990&highlight= Sabayon Forums post here.]

Authored by Fitzcarraldo

[[Category:Input Devices|Belkin Bluetooth Keyboard]]