https://wiki.archlinux.org/api.php?action=feedcontributions&user=Gianguido&feedformat=atomArchWiki - User contributions [en]2024-03-28T21:02:18ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=PulseAudio_(Italiano)&diff=372041PulseAudio (Italiano)2015-05-01T20:41:11Z<p>Gianguido: /* QEMU */ s/QUEMU/QEMU</p>
<hr />
<div>[[Category:Audio/Video (Italiano)]]<br />
[[Category:Sound (Italiano)]]<br />
[[cs:PulseAudio]]<br />
[[en:PulseAudio]]<br />
[[es:PulseAudio]]<br />
[[fr:PulseAudio]]<br />
[[ja:PulseAudio]]<br />
[[pt:PulseAudio]]<br />
[[ru:PulseAudio]]<br />
[[tr:PulseAudio]]<br />
{{Related articles start (Italiano)}}<br />
{{Related|PulseAudio/Examples (Italiano)}}<br />
{{Related|PulseAudio/Troubleshooting (Italiano)}}<br />
{{Related articles end}}<br />
[[Wikipedia:PulseAudio|PulseAudio]] è un sound server utilizzato comunemente da ambienti desktop come [[GNOME (Italiano)|GNOME]] e [[KDE (Italiano)|KDE]] e funge da proxy per le applicazioni che richiedano l'utilizzo dell'audio utilizzando componenti come [[ALSA (Italiano)|ALSA]] od [[OSS (Italiano)|OSS]]. Dal momento che Alsa viene incluso in Arch Linux di default, i casi di utilizzo più comuni proposti di seguito coprono l'utilizzo di PulseAudio con Alsa.<br />
<br />
==Installazione==<br />
<br />
* Pacchetto richiesto: {{Pkg|pulseaudio}}<br />
* GUI GTK opzionali: {{Pkg|paprefs}} e {{Pkg|pavucontrol}}<br />
* Controllo volume opzionale via tastiera: {{AUR|pulseaudio-ctl}}<br />
* Mixer da console (CLI) opzionali: {{AUR|ponymix-git}} e {{AUR|pamixer-git}}<br />
* Controllo volume via web opzionale: <br />
* Icona nella tray di sistema opzionale: [https://github.com/Siot/PaWebControl PaWebControl]{{AUR|pasystray-git}}<br />
* Applet di Plasma per KDE: {{Pkg|kdemultimedia-kmix}} e {{AUR|kdeplasma-applets-veromix}} (Se KMix/Veromix non riescono a connettersi a PulseAudio all'avvio, potrebbe essere necessario modificare {{ic|/etc/pulse/client.conf}} e modificare {{ic|1=autospawn = yes}} in {{ic|1=autospawn = no}}.)<br />
<br />
==Configurazione==<br />
<br />
Si sarà notato che PulseAudio supporta vari moduli per estendere le proprie funzionalità. È possibile reperirne un elenco completo [http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/ qui].<br />
Per abilitarli sarà sufficiente aggiungere {{ic|load-module <module-name-from-list>}} a {{ic|/etc/pulse/default.pa}}.<br />
<br />
==Esecuzione==<br />
<br />
{{Attenzione|Se si dispone di copie locali dei files di configurazione ({{ic|client.conf}}, {{ic|daemon.conf}} o {{ic|default.pa}} in {{ic|~/.config/pulse}}, sarà necessario allinearle ai cambiamenti dei files situati in {{ic|/etc/pulse}}, altrimenti PulseAudio potrebbe non avviarsi a causa di errori di configurazione.}}<br />
<br />
{{Nota|<br />
La maggior parte degli ambienti grafici avviano PulseAudio automaticamente.<br />
}}<br />
<br />
Nel caso in cui PulseAudio non venisse automaticamente avviato all'avvio di X, può essere avviato con:<br />
<br />
$ pulseaudio --start<br />
<br />
PulseAudio può essere interrotto con:<br />
<br />
$ pulseaudio --kill<br />
<br />
===Avvio automatico in ambienti desktop non supportati===<br />
<br />
{{Nota|Come già detto in precedenza, PulseAudio viene molto probabilmente già lanciato automaticamente tramite {{ic|/etc/X11/xinit/xinitrc.d/pulseaudio}} o i file in {{ic|/etc/xdg/autostart}}, se si è installato un DE.}}<br />
<br />
Si controlli se PulseAudio è in esecuzione:<br />
<br />
{{hc|<nowiki>$ pgrep -af pulseaudio</nowiki>|<br />
369 /usr/bin/pulseaudio<br />
}}<br />
<br />
Se PulseAudio non è avviato e si sta utilizzando X, il comando che segue ne consentirà l'avvio manuale, assieme a tutti i plugin richiesti:<br />
<br />
$ start-pulseaudio-x11<br />
<br />
Se non si sta utilizzando GNOME, KDE o Xfce e il proprio [[Xinitrc|~/.xinitrc]] non effettua il source degli script in {{ic|/etc/X11/xinit/xinitrc.d}}, è possibile avviare PulseAudio al boot con:<br />
<br />
{{hc|~/.xinitrc|<br />
/usr/bin/start-pulseaudio-x11<br />
}}<br />
<br />
==Configurazione del backend==<br />
<br />
===ALSA===<br />
<br />
Si installi {{Pkg|pulseaudio-alsa}} dai [[Official Repositories (Italiano)|repository ufficiali]]. Il pacchetto contiene il file {{ic|/etc/asound.conf}} per impostare ALSA per l'utilizzo con PulseAudio.<br />
<br />
Si installino inoltre {{Pkg|lib32-libpulse}} e {{Pkg|lib32-alsa-plugins}} se si è su un sistema a 64 bit e si utilizzano applicazioni [[Multilib|multilib]] a 32 bit come Wine, Skype e Steam.<br />
<br />
Per impedire alle applicazioni di usare l'emulazione OSS di ALSA bypassando così Pulseaudio (non consentendo così ad altri programmi di riprodurre suoni), assicurarsi che il modulo {{ic|snd_pcm_oss}} non venga caricato al boot. Se è caricato (controllare con {{ic|<nowiki>lsmod | grep oss</nowiki>}}), è possibile rimuoverlo con:<br />
<br />
# rmmod snd_pcm_oss<br />
<br />
===ALSA / dmix senza che PulseAudio prenda possesso della scheda audio===<br />
<br />
{{Nota|Questa sezione descrive una configurazione alternativa, generalmente '''NON''' consigliabile.}}<br />
<br />
Si potrebbe voler utilizzare ALSA direttamente nella maggior parte delle applicazioni e al tempo stesso utilizzarne delle altre che richiedono PulseAudio.<br />
I passi seguenti consentiranno a PulseAudio di utilizzare dmix senza che lo stesso debba prendere il controllo della scheda audio.<br />
<br />
* Si rimuova il pacchetto {{Pkg|pulseaudio-alsa}}, che fornisce un layer di compatibilità tra le applicazioni ALSA e PulseAudio. Una volta fatto, tali applicazioni utilizzeranno ALSA direttamente senza passare per PulseAudio.<br />
<br />
* Si modifichi {{ic|/etc/pulse/default.pa}}.<br />
: Si identifichino e decommentino le linee che effettuano il caricamento dei drivers per i backend e si aggiunga loro il parametro '''device''' come mostrato sotto. Si commentino poi le linee che caricano i moduli per l'autorilevamento.<br />
<br />
load-module module-alsa-sink '''device=dmix'''<br />
load-module module-alsa-source '''device=dsnoop'''<br />
# load-module module-udev-detect<br />
# load-module module-detect<br />
<br />
* ''Opzionale:'' Se si utilizza {{Pkg|kdemultimedia-kmix}}, si potrebbe voler controllare il volume di ALSA invece che quello di PulseAudio:<br />
<br />
$ echo export KMIX_PULSEAUDIO_DISABLE=1 > ~/.kde4/env/kmix_disable_pulse.sh<br />
$ chmod +x ~/.kde4/env/kmix_disable_pulse.sh<br />
<br />
* Si riavvii il pc e si provi quindi ad eseguire applicazioni che utilizzano ALSA e PulseAudio contemporaneamente: il suono dovrebbe venir riprodotto simultaneamente da entrambe.<br />
: Si utilizzi quindi {{Pkg|pavucontrol}} per regolare il volume di PulseAudio secondo le proprie necessità.<br />
<br />
===OSS===<br />
<br />
Ci sono diversi modi per fare in modo che programmi compatibili solo con OSS passino l'output a PulseAudio:<br />
<br />
===={{Pkg|ossp}}====<br />
<br />
Si installi il pacchetto {{Pkg|ossp}} e si avvii il servizio {{ic|osspd.service}}.<br />
<br />
====padsp wrapper====<br />
<br />
I programmi che utilizzano OSS, possono funzionare con Pulseaudio se avviati con padsp (incluso in PulseAudio):<br />
<br />
$ padsp OSSprogram<br />
<br />
Un paio di esempi:<br />
<br />
$ padsp aumix<br />
$ padsp sox foo.wav -t ossdsp /dev/dsp<br />
<br />
E' anche possibile creare un wrapper, in questo modo:<br />
<br />
{{hc|/usr/local/bin/nome_programma|<nowiki><br />
#!/bin/sh<br />
exec padsp /usr/bin/OSSprogram "$@"<br />
</nowiki>}}<br />
<br />
Assicurarsi che {{ic|/usr/local/bin}} abbia la precedenza su {{ic|/usr/bin}} nel vostro {{ic|PATH}}.<br />
<br />
===Gstreamer===<br />
<br />
Si installi il pacchetto {{Pkg|gst-plugins-good}} oppure {{Pkg|gstreamer0.10-good-plugins}} se il programma in questione utilizza un'implementazione vecchia di [[GStreamer]].<br />
<br />
===OpenAL===<br />
OpenAL Soft dovrebbe utilizzare PulseAudio di default, ma in caso di necessità può essere manualmente configurato tramite<br />
{{hc|/etc/openal/alsoft.conf|2=drivers=pulse,alsa}}<br />
<br />
===libao===<br />
Modificare il file di configurazione di libao:<br />
{{hc|/etc/libao.conf|2=default_driver=pulse}}<br />
<br />
Assicurarsi di rimuovere l'opzione {{ic|1=dev=default}} del driver alsa o specificare il nome di un sink di PulseAudio o il relativo numero.<br />
<br />
{{Nota|È possibile mantenere i valori di default di libao e lasciargli usare il driver {{ic|alsa}} per l'output se si installa il pacchetto {{Pkg|pulseaudio-alsa}}, poichè in quel caso il dispositivo ALSA di default sarebbe PulseAudio.}}<br />
<br />
==Equalizzatore==<br />
<br />
Le nuove versioni di PulseAudio dispongono di un equalizzatore a 10 bande integrato. Per utilizzarlo, si proceda come segue:<br />
<br />
====Caricamento dei moduli equalizer-sink e dbus-protocol====<br />
<br />
$ pactl load-module module-equalizer-sink<br />
$ pactl load-module module-dbus-protocol<br />
<br />
====Installazione ed esecuzione del frontend grafico====<br />
<br />
Si installi il pacchetto {{Pkg|python2-pyqt4}} e si esegua:<br />
<br />
$ qpaeq<br />
<br />
{{Nota|Se {{ic|qpaeq}} non ha effetto, si installi {{Pkg|pavucontrol}} e si modifichi l'opzione "ALSA Playback on" in "FFT based equalizer on" mentre il player è in riproduzione.}}<br />
<br />
====Caricamento automatico dei moduli equalizer-sink e dbus-protocol al boot====<br />
<br />
Si modifichi il file {{ic|/etc/pulse/default.pa}}, aggiungendo le righe seguenti:<br />
<br />
### Load the intergrated pulseaudio equalizer module<br />
load-module module-equalizer-sink<br />
load-module module-dbus-protocol<br />
<br />
==Applicazioni==<br />
<br />
===QEMU===<br />
<br />
Per verificare se QEMU supporta PulseAudio, si esegua:<br />
<br />
$ qemu-system-x86_64 -audio-help | grep 'Name: pa'<br />
<br />
QEMU può utilizzare le variabili d'ambiente per la configurazione dell'audio:<br />
<br />
{{bc|1=<br />
export QEMU_AUDIO_DRV=pa<br />
export QEMU_PA_SINK=alsa_output.pci-0000_04_01.0.analog-stereo.monitor<br />
export QEMU_PA_SOURCE=input<br />
}}<br />
<br />
Per altre opzioni di configurazione di PulseAudio, si esegua:<br />
<br />
$ qemu-system-x86_64 -audio-help | grep '_PA_'<br />
<br />
Per una lista dei driver emulati supportati si esegua:<br />
<br />
$ qemu-system-x86_64 -soundhw help<br />
<br />
Ad esempio, per utilizzare il driver {{ic|ac97}} per il sistema guest, si passi il parametro {{ic|-soundhw ac97}} a QEMU.<br />
<br />
{{Nota|<br />
* Nel comando {{ic|qemu-system-''XXX''}}, ''XXX'' specifica l'architettura del sistema guest. Per visualizzare un elenco di quelle disponibili, eseguire: {{ic|ls /usr/bin/qemu-system-* -1}}<br />
* I driver video emulati potrebbero causare problemi di qualità audio nella macchinav irtuale. Si provi ogni driver per identificare quello più adatto. È possibile visualizzare un elenco dei driver disponibili con: {{ic|<nowiki>qemu-system-x86_64 -h | grep vga</nowiki>}}.}}<br />
<br />
===AlsaMixer.app===<br />
<br />
Per fare in modo che la dockapp {{AUR|AlsaMixer.app}} per {{Pkg|windowmaker}} utilizzi PulseAudio, utilizzare:<br />
<br />
$ AlsaMixer.app --device pulse<br />
<br />
Di seguito due esempi, il primo per ALSA e il secondo per PulseAudio. È possibile eseguire istanze multiple dell'applicazione. Si utilizzi l'opzione {{ic|-w}} per scegliere quale dei due pulsanti di controllo assegnare alla rotella del mouse:<br />
<br />
# AlsaMixer.app -3 Mic -1 Master -2 PCM --card 0 -w 1<br />
# AlsaMixer.app --device pulse -1 Capture -2 Master -w 2<br />
<br />
{{Nota|L'applicazione può utilizzare solamente gli output sinks impostati come default.}}<br />
<br />
===XMMS2===<br />
<br />
Per utilizzare PulseAudio come output:<br />
<br />
$ nyxmms2 server config output.plugin pulse<br />
<br />
Per utilizzare ALSA:<br />
<br />
$ nyxmms2 server config output.plugin alsa<br />
<br />
Per utilizzare un sink di output differente:<br />
<br />
$ nyxmms2 server config pulse.sink alsa_output.pci-0000_04_01.0.analog-stereo.monitor<br />
<br />
Consultare inoltre la guida ufficiale: [https://xmms2.org/wiki/Using_the_application].<br />
<br />
===KDE Plasma Workspaces e Qt4===<br />
<br />
PulseAudio viene utilizzato automaticamente dalle applicazioni KDE/Qt4 e supportato di default nel mixer di KDE.<br />
Per ulteriori informazioni si veda la [http://www.pulseaudio.org/wiki/KDE pagina] relativa a KDE sul wiki di PulseAudio. Un consiglio utile dal link di cui sopra è quello di aggiungere {{ic|load-module module-device-manager}} a {{ic|/etc/pulse/default.pa}}.<br />
<br />
Se si sta utilizzando il backend phonon-gstreamer per Phonon, sarà necessario configurare anche GStreamer come descritto in [[#GStreamer]].<br />
<br />
===Audacious===<br />
[[Audacious|Audacious]] supporta Pulseaudio nativamente. Per usarlo, è necessario avviare Audacious e recarsi in: Audacious Preferences -> Audio -> Current Output plugin, quindi scegliere 'Pulseaudio Output Plugin'<br />
<br />
===Java/OpenJDK 6===<br />
<br />
Si crei un wrapper per l'eseguibile java usando {{ic|padsp}} come si è visto alla pagina [[Java_(Italiano)#Audio_Java_con_Pulseaudio|Audio Java con Pulseaudio]].<br />
<br />
===Music Player Daemon (MPD)===<br />
È necessario [http://mpd.wikia.com/wiki/PulseAudio configurare] mpd affinché usi Pulseaudio. Si veda anche [[MPD/Tips and Tricks#MPD and PulseAudio]].<br />
<br />
Si noti comunque che quanto sopra potrebbe causare un bug che impedisce a PulseAudio di togliere il muto agli altoparlanti quando vengono rimosse cuffie o altri dispositivi audio.<br />
<br />
===MPlayer===<br />
<br />
MPlayer supporta l'output attraverso Pulseaudio specificando l'opzione {{ic|"-ao pulse"}}. È inoltre possibile configurarlo affinché venga usato in modo predefinito modificando {{ic|~/.mplayer/config}} per l'utente corrente o {{ic|/etc/mplayer/mplayer.conf}} per applicare le modifiche a tutto il sistema.<br />
<br />
{{hc|/etc/mplayer/mplayer.conf<br />
|2=ao=pulse<br />
}}<br />
<br />
=== guvcview ===<br />
<br />
È possibile che l'input audio venga sospeso quando si utilizza l'input PulseAudio da una [[Webcam]], causando cosi la mancata registrazione dell'audio.<br />
<br />
Si verifichi eseguendo:<br />
<br />
$ pactl list sources<br />
<br />
Se la sorgente audio è sospesa, si modifichi {{ic|/etc/pulse/default.pa}} cambiando:<br />
<br />
load-module module-suspend-on-idle<br />
<br />
in:<br />
<br />
#load-module module-suspend-on-idle<br />
<br />
Così facendo, il riavvio di PulseAudio o del sistema metterà in idle la sorgente di input invece di sospenderla. {{Pkg|guvcview}} potrà quindi registrare l'audio dal dispositivo in maniera corretta.<br />
<br />
==Risoluzione dei problemi==<br />
<br />
Si veda [[PulseAudio/Troubleshooting (Italiano)]].<br />
<br />
== Link esterni ==<br />
<br />
*[http://www.alsa-project.org/main/index.php/Asoundrc http://www.alsa-project.org/main/index.php/Asoundrc] - Pagina del wiki di ALSA relativa ad .asoundrc<br />
*[http://www.pulseaudio.org/ http://www.pulseaudio.org/] - Sito ufficiale di Pulseaudio<br />
*[http://www.pulseaudio.org/wiki/FAQ http://www.pulseaudio.org/wiki/FAQ] - Faq per Pulseaudio.</div>Gianguidohttps://wiki.archlinux.org/index.php?title=MacBookPro11,x&diff=313811MacBookPro11,x2014-05-07T07:40:03Z<p>Gianguido: /* Using the MacBook's native EFI bootloader */</p>
<hr />
<div>[[Category:Apple]]<br />
{{Article summary start}}<br />
{{Article summary text|This wiki page should help you in getting your MacBook Pro(Late 2013) to work with Arch Linux.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Installation guide}}<br />
{{Article summary wiki|Beginners' guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary wiki|MacBookPro10,x}}<br />
{{Article summary wiki|MacBook}}<br />
{{Article summary end}}<br />
<br />
== Preparing for the Installation ==<br />
=== Preparing the hard drive ===<br />
Assuming you want to dual boot with OS X, so you can update firmware, you have to shrink its partition with Disk Utility. You can either create a HFS+ partition now to override later, or leave it empty.<br />
<br />
== Installation ==<br />
=== Booting the live image ===<br />
Now, download the latest [[Archboot]] ISO, write it to USB, and boot from it by selecting it in the Apple boot loader by holding {{ic|Alt}} on boot (use rEFIt if you cannot manage to select it). If you are using a kernel before 3.13 when it comes to the syslinux boot loader, press {{ic|Tab}} to edit the entry and append {{ic|nomodeset}} to fix screen corruption, do not use nomodeset for kernel 3.13 and above, it is not needed anymore (and it will break vaapi).<br />
<br />
=== Internet === <br />
{{Note|You can skip this if you use the Thunderbolt or USB-to-Ethernet adapter for the installation.}}<br />
<br />
==== Wireless ====<br />
As mentioned below, {{ic|broadcom-wl}} is sufficient if you are using the Linux mainline kernel. For custom kernels, you need to use {{ic|broadcom-wl-dkms}}. Both are available from the [[AUR]]. The easiest way to get Wi-Fi connectivity during install is to build the package driver on a separate system using:<br />
$ curl -O https://aur.archlinux.org/packages/br/broadcom-wl-dkms/broadcom-wl-dkms.tar.gz<br />
$ tar -zxvf broadcom-wl-dkms.tar.gz<br />
$ cd broadcom-wl-dkms<br />
$ makepkg -s<br />
This will give you a package ({{ic|broadcom-wl-*.pkg.tar.xz}}) which can be installed using [[pacman]]. Put this package on a USB drive, mount it, and install the package using<br />
# pacman -U broadcom-wl-*.pkg.tar.xz<br />
# modprobe wl<br />
during install.<br />
You may now use {{ic|wifi-menu}} to connect to your network of choice.<br />
{{Note|You need to repeat this process when you have finished your installation, for instance when booting into the system for the first time or when you have chrooted your install.}}<br />
<br />
=== The installation ===<br />
{{Note|Refer to the [[MacBook]] page if you do not want to have a separate partition for GRUB but rather prefer to use [http://www.rodsbooks.com/refind/ rEFInd] (or [[MacBook#rEFIt|rEFIt]]).}}<br />
Run the installation wizard.<br />
{{Tip|If you want to use the native MacBook bootloader, you need an extra partition of at least 128 MiB.}}<br />
<br />
=== Bootloader ===<br />
==== Using the MacBook's native EFI bootloader ====<br />
This method uses the MacBook's native EFI bootloader, i.e. the one the can be reached when holding the alt-key during boot. <br />
<br />
{{Note|For this method you need an extra partition of at least 128 MiB. This partition will be used by the MacBook's native bootloader to launch Arch. It also assumes that you are dual-booting OS X and Arch.}}<br />
{{Note|It's possible to avoid the HFS+ partition by using FAT32, this way you can do all the bootloader stuff right from the LiveCD.}}<br />
<br />
At the end of the install process we would normally install GRUB or a variation the the drive. For this method we will place a {{ic|boot.efi}} file on an extra partition used by the MacBook's native bootloader.<br />
<br />
First, [[pacman|install]] the {{Pkg|grub}} package from the [[official repositories]].<br />
<br />
When generating a {{ic|boot.efi}} file, GRUB looks to {{ic|/etc/default/grub}} for its configuration. Edit the parameter {{ic|GRUB_CMDLINE_LINUX_DEFAULT}} to look something like this:<br />
{{bc|<br />
<nowiki><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootflags=data=writeback libata.force=noncq"<br />
</nowiki><br />
}}<br />
<br />
The {{ic|1=libata.force=noncq}} parameter will prevent SSD lockups and the {{ic|rootflags}} option is used for SSD-performance.<br />
<br />
{{Note|Do not use the {{ic|rootflags}} option on Btrfs. It is not supported.}}<br />
<br />
Now we generate the {{ic|boot.efi}} file:<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
# grub-mkstandalone -o boot.efi -d /usr/lib/grub/x86_64-efi -O x86_64-efi /boot/grub/grub.cfg<br />
<br />
Put this file on a USB (or other OS X accessible media) and reboot into OS X.<br />
<br />
Launch {{ic|DiskUtility.app}} and erase the extra partition, mentioned above, to HFS+ and mount it.<br />
$ mkdir -p <Path to root of extra partition>/System/Library/CoreServices<br />
$ mkdir <Parth to root of extra partition>/mach_kernel<br />
<br />
Copy the {{ic|boot.efi}} file to the {{ic|<Path to extra partition>/System/Library/CoreServices/}} directory. Using your editor of choice, create a {{ic|SystemVersion.plist}} file in the CoreServices directory, which is located here:<br />
''<path to extra partition>''/System/Library/CoreServices/SystemVersion.plist<br />
<br />
Edit that file to look like this:<br />
{{bc|<br />
<nowiki><br />
<xml version="1.0" encoding="utf-8"?><br />
<plist version="1.0"><br />
<dict><br />
<key>ProductBuildVersion</key><br />
<string></string><br />
<key>ProductName</key><br />
<string>Linux</string><br />
<key>ProductVersion</key><br />
<string>Arch Linux</string><br />
</dict><br />
</plist><br />
</nowiki><br />
}}<br />
<br />
The last step is then to bless the extra partition using:<br />
# bless --device disk0sX --setBoot<br />
If this command doesn't work try calling bless by the mount point instead.<br />
# bless --mount /Volumes/<mount> --setBoot <br />
<br />
Where {{ic|disk0sX}} is the extra partitions id. The id can be found using either {{ic|DiskUtility.app}} or by issuing:<br />
# diskutil list<br />
<br />
{{Note|In order to change grub settings both {{ic|grub.cfg}} and {{ic|boot.efi}} will have to be generated. This can be done without booting OS X.}}<br />
<br />
Generate {{ic|grub.cfg}} and {{ic|boot.efi}} from Arch Linux:<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
# mount -t hfsplus -o force,rw /dev/sdXY /mnt # mount the HFS+ partition<br />
# grub-mkstandalone -o /mnt/System/Library/CoreServices/boot.efi -d /usr/lib/grub/x86_64-efi -O x86_64-efi /boot/grub/grub.cfg<br />
<br />
==== Direct EFI booting (rEFInd) ====<br />
''See: [[UEFI_Bootloaders]]''<br />
<br />
As of August 2013, refind can automatically detect the Arch kernel, removing the need for copying the kernel into the EFI partition. Simply install refind without the EFI file system drivers [http://forums.gentoo.org/viewtopic-t-967024-start-0.html] using the {{ic|--nodrivers}} option [https://bbs.archlinux.org/viewtopic.php?pid=1348145#p1348145], and enable the {{ic|scan_all_linux_kernels}} and {{ic|also_scan_dirs}} options in {{ic|refind.conf}} (see link above for instructions.).<br />
<br />
An alternative way is to omit all the scans and put the following bootentry at the end of your "refind.conf":<br />
menuentry "Arch" {<br />
icon EFI/refind/icons/os_arch.icns <br />
volume <Volume label><br />
ostype Linux<br />
loader /boot/vmlinuz-linux<br />
initrd /boot/initramfs-linux.img<br />
options "rw root=/dev/<arch partition> rootfstype=<filesystem type> libata.force=noncq"<br />
}<br />
Don't forget to replace the angle brackets with your data.<br />
<br />
==== GRUB (with OS X) ====<br />
Another solution is to install [[GRUB]]. Edit {{ic|/tmp/install/boot/grub/grub.cfg}} and edit the boot entry to load Linux mainline instead of the normal one.<br />
<br />
{{Note|{{ic|1=libata.force=noncq}} helps with hangs due to SSD speed.}}<br />
<br />
Now cd into {{ic|/tmp/install/}} and create the GRUB image by running:<br />
grub-mkstandalone -o bootx64.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg<br />
This will create file called {{ic|boot64.efi}} which contains GRUB and the configuration file incorporated inside. It is important to {{ic|cd}} into the right directory to make it pick up the configuration file and put it into the right place within the image.<br />
<br />
Copy this file to the MacBook's EFI partition. The downside of this method is that you need to repeat this step whenever you want to change the GRUB config. Reboot the machine and you should be able to select your installed Arch Linux by keeping the {{ic|Alt}} button pressed. It should appear as {{ic|EFI boot}}.<br />
<br />
To generate a nicer config use: {{ic|grub-mkconfig}}, remove {{ic|quiet}} if you like the text, then to update your GRUB post-installation, do this to make the GRUB EFI file and put it in the EFI partition:<br />
cd /<br />
grub-mkstandalone -o bootx64.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg<br />
sudo mount /dev/sda1 /mnt<br />
sudo cp bootx64.efi /mnt/EFI/boot/bootx64.efi<br />
<br />
{{note|You'll need {{ic|hfsprogs}} to run the above commands}}<br />
<br />
== Post installation ==<br />
=== Console ===<br />
Largest console font (although ugly) achieved by adding {{ic|1=FONT=sun12x22}} to {{ic|/etc/vconsole.conf}}<br />
It is still tiny but is at least readable.<br />
<br />
=== Graphics ===<br />
MacBook Pro 11,1<br />
* Intel works on 3.12 with nomodeset<br />
* Intel works from 3.13.4-1-ARCH<br />
MacBook Pro 11,2<br />
* Intel works from 3.13.4-1-ARCH<br />
MacBook Pro 11,3<br />
* Nvidia works (both 319.60 and 331.17 drivers)<br />
** Follow http://cberner.com/2013/03/01/installing-ubuntu-13-04-on-macbook-pro-retina/<br />
* Intel works after patching grub, see below<br />
<br />
See [[HiDPI]] for information on how to tweak the system for a Retina screen.<br />
<br />
If you are using [[Xfce]], you will probably experience tearing in Firefox, VLC, etc. Until newer versions of xfwm support OpenGL rendering, use another compositing window manager like [[compton]] with {{ic|1=backend = "glx"}}.<br />
<br />
==== Getting the integrated intel card to work on 11,3 ====<br />
By default the integrated card is powered off. To fix this we need a grub function called "apple_set_os". This function hasn't oficially been merged yet, so we need to build grub ourselves. Download the {{AUR|grub-git}} package from the AUR. Using something like:<br />
<br />
$ packer -G grub-git<br />
$ cd grub-git<br />
<br />
Get the patch from here: http://lists.gnu.org/archive/html/grub-devel/2013-12/msg00442.html<br />
<br />
Put the patch contents into a file labeled something like "apple.patch"<br />
<br />
Add this patch to your PKGBUILD and run:<br />
<br />
$ makepkg -si<br />
<br />
Reboot into OS X and download gfxCardStatus v2.2.1 (newer versions do not work properly) run the app and specify the integrated card.<br />
<br />
Reboot and at the grub prompt typ 'c' to get into console, followed by "apple_set_os" at the prompt.<br />
<br />
You should now be able to install {{Pkg|xf86-video-intel}} and get your card running.<br />
<br />
Note that the HDMI port and MiniDP are soldered to the nvidia card meaning that to run external displays you need to use the dedicated card.<br />
<br />
=== Sound ===<br />
* Headphones work<br />
* Speakers work from kernel 3.13 and 3.12.2. 3.12.1 only with patch<br />
** Patch: https://bugzilla.kernel.org/attachment.cgi?id=114081.<br />
** See discussion here: https://bugzilla.kernel.org/show_bug.cgi?id=64401<br />
* Optical audio can be turned off and on with above sound patch.<br />
<br />
If you do not want to hear the annoying sound at system start-up, one way to get rid of it is to turn sound off while under Mac OS.<br />
<br />
Volume keys can be made to work with {{ic|xfce4-volumed}} (if you are using Xfce).<br />
<br />
Also, if you are using PulseAudio, sometimes it thinks HDMI is the default sound card; to solve this problem, install {{pkg|pavucontrol}} and set Analog Stereo as the fallback device.<br />
<br />
=== Touchpad ===<br />
One method is to install {{pkg|xf86-input-synaptics}} and configure to your liking in {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}:<br />
Section "InputClass"<br />
MatchIsTouchpad "on"<br />
Identifier "touchpad catchall"<br />
Driver "synaptics"<br />
# 1 = left, 2 = right, 3 = middle<br />
Option "TapButton1" "1" <br />
Option "TapButton2" "3"<br />
Option "TapButton3" "2"<br />
# Palm detection<br />
Option "PalmDetect" "1"<br />
# Horizontal scrolling<br />
Option "HorizTwoFingerScroll" "1"<br />
# Natural Scrolling (and speed)<br />
Option "VertScrollDelta" "-100"<br />
Option "HorizScrollDelta" "-100"<br />
EndSection<br />
<br />
=== Keyboard backlight ===<br />
* Works, see [[MacBook#Keyboard_Backlight]]<br />
<br />
=== Screen backlight ===<br />
* Intel, works on Linux 3.13<br />
* Framebuffer, works for MacBook Pro 11,1 and 11,3 via {{ic|/sys/class/backlight/gmux_backlight/brightness}}.<br />
* Nvidia, does not work using default settings. Try adding {{ic|1=setpci -v -H1 -s 00:01.00 BRIDGE_CONTROL=0}} to {{ic|/etc/rc.local}}.<br />
{{note|If the screen doesn't show the prompt or the login manager (i.e. a black screen), append {{ic|1=i915.invert_brightness=1}} to the kernel. }}<br />
<br />
=== Suspend ===<br />
* Works on MacBook Pro 11,2 with Linux 3.13<br />
* No backlight after suspend with Linux 3.12<br />
** Use hibernate instead<br />
<br />
== What does not work ==<br />
Updated 2013-12-07<br />
<br />
=== General ===<br />
<br />
=== Wi-Fi ===<br />
* {{AUR|broadcom-wl}} from the [[AUR]] works<br />
** Stability is an issue for some<br />
<br />
=== Web cam ===<br />
* Listed on PCI bus as: Multimedia controller: Broadcom Corporation Device 1570.<br />
* In OS X, the camera is listed as FaceTime HD camera 1570.<br />
* No known Linux driver. [https://bugzilla.kernel.org/show_bug.cgi?id=71131 Kernel.org Bug]<br />
<br />
== Discussions ==<br />
* https://bbs.archlinux.org/viewtopic.php?id=171883<br />
<br />
== See also ==<br />
* [[MacBookPro10,x]]<br />
* [[MacBook]]</div>Gianguidohttps://wiki.archlinux.org/index.php?title=MacBookPro11,x&diff=297770MacBookPro11,x2014-02-15T14:22:02Z<p>Gianguido: </p>
<hr />
<div>[[Category:Apple]]<br />
{{Article summary start}}<br />
{{Article summary text|This wiki page should help you in getting your MacBook Pro(Late 2013) to work with Arch Linux.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}}<br />
{{Article summary wiki|Beginners Guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary wiki|MacBookPro10,x}}<br />
{{Article summary wiki|MacBook}}<br />
{{Article summary end}}<br />
<br />
== Preparing for the Installation ==<br />
=== Preparing the hard drive ===<br />
Assuming you want to dual boot with OS X, so you can update firmware, you have to shrink its partition with Disk Utility. You can either create a HFS+ partition now to override later, or leave it empty.<br />
<br />
== Installation ==<br />
=== Booting the live image ===<br />
Now, download the latest [[Archboot]] ISO, write it to USB, and boot from it by selecting it in the Apple boot loader by holding {{ic|Alt}} on boot (use rEFIt if you cannot manage to select it). When it comes to the syslinux boot loader, press {{ic|Tab}} to edit the entry and append {{ic|nomodeset}} to fix screen corruption.<br />
<br />
=== Internet === <br />
{{Note|You can skip this if you use the Thunderbolt or USB-to-Ethernet adapter for the installation.}}<br />
<br />
==== Wireless ====<br />
As mentioned below, {{ic|broadcom-wl}} is sufficient if you are using the Linux mainline kernel. For custom kernels, you need to use {{ic|broadcom-wl-dkms}}. Both are available from the [[AUR]]. The easiest way to get Wi-Fi connectivity during install is to build the package driver on a separate system using:<br />
$ curl -O https://aur.archlinux.org/packages/br/broadcom-wl-dkms/broadcom-wl-dkms.tar.gz<br />
$ tar -zxvf broadcom-wl-dkms.tar.gz<br />
$ cd broadcom-wl-dkms<br />
$ makepkg -s<br />
This will give you a package ({{ic|broadcom-wl-*.pkg.tar.xz}}) which can be installed using [[pacman]]. Put this package on a USB drive, mount it, and install the package using<br />
# pacman -U broadcom-wl-*.pkg.tar.xz<br />
# modprobe wl<br />
during install.<br />
You may now use {{ic|wifi-menu}} to connect to your network of choice.<br />
{{Note|You need to repeat this process when you have finished your installation, for instance when booting into the system for the first time or when you have chrooted your install.}}<br />
<br />
=== The installation ===<br />
{{Note|Refer to the [[MacBook]] page if you do not want to have a separate partition for GRUB but rather prefer to use [http://www.rodsbooks.com/refind/ rEFInd] (or [[MacBook#rEFIt|rEFIt]]).}}<br />
Run the installation wizard.<br />
{{Tip|If you want to use the native MacBook bootloader, you need an extra partition of at least 128 MiB.}}<br />
<br />
=== Bootloader ===<br />
==== Using the MacBook's native EFI bootloader ====<br />
This method uses the MacBook's native EFI bootloader, i.e. the one the can be reached when holding the alt-key during boot. <br />
<br />
{{Note|For this method you need an extra partition of at least 128 MiB. This partition will be used by the MacBook's native bootloader to launch Arch. It also assumes that you are dual-booting OS X and Arch.}}<br />
<br />
At the end of the install process we would normally install GRUB or a variation the the drive. For this method we will place a {{ic|boot.efi}} file on an extra partition used by the MacBook's native bootloader.<br />
<br />
First, [[pacman|install]] the {{Pkg|grub}} package from the [[Official Repositories|official repositories]].<br />
<br />
When generating a {{ic|boot.efi}} file, GRUB looks to {{ic|/etc/default/grub}} for its configuration. Edit the parameter {{ic|GRUB_CMDLINE_LINUX_DEFAULT}} to look something like this:<br />
{{bc|<br />
<nowiki><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootflags=data=writeback libata.force=noncq"<br />
</nowiki><br />
}}<br />
<br />
The {{ic|1=libata.force=noncq}} parameter will prevent SSD lockups and the {{ic|rootflags}} option is used for SSD-performance.<br />
<br />
{{Note|Do not use the {{ic|rootflags}} option on Btrfs. It is not supported.}}<br />
<br />
Now we generate the {{ic|boot.efi}} file:<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
# grub-mkstandalone -o boot.efi -d /usr/lib/grub/x86_64-efi -O x86_64-efi /boot/grub/grub.cfg<br />
<br />
Put this file on a USB (or other OS X accessible media) and reboot into OS X.<br />
<br />
Launch {{ic|DiskUtility.app}} and erase the extra partition, mentioned above, to HFS+ and mount it.<br />
$ mkdir -p <Path to root of extra partition>/System/Library/CoreServices<br />
$ mkdir <Parth to root of extra partition>/mach_kernel<br />
<br />
Copy the {{ic|boot.efi}} file to the {{ic|<Path to extra partition>/System/Library/CoreServices/}} directory. Using your editor of choice, create a {{ic|SystemVersion.plist}} file in the CoreServices directory, which is located here:<br />
''<path to extra partition>''/System/Library/CoreServices/SystemVersion.plist<br />
<br />
Edit that file to look like this:<br />
{{bc|<br />
<nowiki><br />
<xml version="1.0" encoding="utf-8"?><br />
<plist version="1.0"><br />
<dict><br />
<key>ProductBuildVersion</key><br />
<string></string><br />
<key>ProductName</key><br />
<string>Linux</string><br />
<key>ProductVersion</key><br />
<string>Arch Linux</string><br />
</dict><br />
</plist><br />
</nowiki><br />
}}<br />
<br />
The last step is then to bless the extra partition using:<br />
# bless --device disk0sX --setBoot<br />
<br />
Where {{ic|disk0sX}} is the extra partitions id. The id can be found using either {{ic|DiskUtility.app}} or by issuing:<br />
# diskutil list<br />
<br />
{{Note|In order to change grub settings both {{ic|grub.cfg}} and {{ic|boot.efi}} will have to be generated. This can be done without booting OS X.}}<br />
<br />
Generate {{ic|grub.cfg}} and {{ic|boot.efi}} from Arch Linux:<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
# mount -t hfsplus -o force,rw /dev/sdXY /mnt # mount the HFS+ partition<br />
# grub-mkstandalone -o /mnt/System/Library/CoreServices/boot.efi -d /usr/lib/grub/x86_64-efi -O x86_64-efi /boot/grub/grub.cfg<br />
<br />
==== Direct EFI booting (rEFInd) ====<br />
''See: [[UEFI_Bootloaders]]''<br />
<br />
As of August 2013, refind can automatically detect the Arch kernel, removing the need for copying the kernel into the EFI partition. Simply install refind without the EFI file system drivers [http://forums.gentoo.org/viewtopic-t-967024-start-0.html] using the {{ic|--nodrivers}} option [https://bbs.archlinux.org/viewtopic.php?pid=1348145#p1348145], and enable the {{ic|scan_all_linux_kernels}} and {{ic|also_scan_dirs}} options in {{ic|refind.conf}} (see link above for instructions.)<br />
<br />
==== GRUB (with OS X) ====<br />
Another solution is to install [[GRUB]]. Edit {{ic|/tmp/install/boot/grub/grub.cfg}} and edit the boot entry to load Linux mainline instead of the normal one. You might want to append {{ic|nomodeset}} to the kernel line again, at least for now.<br />
<br />
{{Note|{{ic|1=libata.force=noncq}} helps with hangs due to SSD speed.}}<br />
<br />
Now cd into {{ic|/tmp/install/}} and create the GRUB image by running:<br />
grub-mkstandalone -o bootx64.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg<br />
This will create file called {{ic|boot64.efi}} which contains GRUB and the configuration file incorporated inside. It is important to {{ic|cd}} into the right directory to make it pick up the configuration file and put it into the right place within the image.<br />
<br />
Copy this file to the MacBook's EFI partition. The downside of this method is that you need to repeat this step whenever you want to change the GRUB config. Reboot the machine and you should be able to select your installed Arch Linux by keeping the {{ic|Alt}} button pressed. It should appear as {{ic|EFI boot}}.<br />
<br />
To generate a nicer config use: {{ic|grub-mkconfig}}, (add in {{ic|nomodeset}} if you are using framebuffer), remove {{ic|quiet}} if you like the text, then to update your GRUB post-installation, do this to make the GRUB EFI file and put it in the EFI partition:<br />
cd /<br />
grub-mkstandalone -o bootx64.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg<br />
sudo mount /dev/sda1 /mnt<br />
sudo cp bootx64.efi /mnt/EFI/boot/bootx64.efi<br />
<br />
{{note|You'll need {{ic|hfsprogs}} to run the above commands}}<br />
<br />
== Post installation ==<br />
=== Console ===<br />
Largest console font (although ugly) achieved by adding {{ic|1=FONT=sun12x22}} to {{ic|/etc/vconsole.conf}}<br />
It is still tiny but is at least readable.<br />
<br />
=== Graphics ===<br />
MacBook Pro 11,1<br />
* Intel works fine<br />
MacBook Pro 11,2<br />
* Intel works on Linux 3.13 and on Linux 3.12 with patch, see https://bugs.freedesktop.org/show_bug.cgi?id=71049<br />
** Alternatively, use framebuffer, {{Pkg|xf86-video-fbdev}}.<br />
MacBook Pro 11,3<br />
* Nvidia works (both 319.60 and 331.17 drivers)<br />
** Follow http://cberner.com/2013/03/01/installing-ubuntu-13-04-on-macbook-pro-retina/<br />
* Intel works after patching grub, see below<br />
<br />
See [[HiDPI]] for information on how to tweak the system for a Retina screen.<br />
<br />
If you are using [[Xfce]], you will probably experience tearing in Firefox, VLC, etc. Until newer versions of xfwm support OpenGL rendering, use another compositing window manager like [[compton]] with {{ic|1=backend = "glx"}}.<br />
<br />
==== Getting the integrated intel card to work on 11,3 ====<br />
By default the integrated card is powered off. To fix this we need a grub function called "apple_set_os". This function hasn't oficially been merged yet, so we need to build grub ourselves. Download the {{Pkg|grub-git}} package from the AUR. Using something like:<br />
<br />
$ packer -G grub-git<br />
$ cd grub-git<br />
<br />
Get the patch from here: http://lists.gnu.org/archive/html/grub-devel/2013-12/msg00442.html<br />
<br />
Put the patch contents into a file labeled something like "apple.patch"<br />
<br />
Add this patch to your PKGBUILD and run:<br />
<br />
$ makepkg -si<br />
<br />
Reboot into OS X and download gfxCardStatus v2.2.1 (newer versions do not work properly) run the app and specify the integrated card.<br />
<br />
Reboot and at the grub prompt typ 'c' to get into console, followed by "apple_set_os" at the prompt.<br />
<br />
You should now be able to install {{Pkg|xf86-video-intel}} and get your card running.<br />
<br />
Note that the HDMI port and MiniDP are soldered to the nvidia card meaning that to run external displays you need to use the dedicated card.<br />
<br />
=== Sound ===<br />
* Headphones work<br />
* Speakers work from kernel 3.13 and 3.12.2. 3.12.1 only with patch<br />
** Patch: https://bugzilla.kernel.org/attachment.cgi?id=114081.<br />
** See discussion here: https://bugzilla.kernel.org/show_bug.cgi?id=64401<br />
* Optical audio can be turned off and on with above sound patch.<br />
<br />
If you do not want to hear the annoying sound at system start-up, one way to get rid of it is to turn sound off while under Mac OS.<br />
<br />
Volume keys can be made to work with {{ic|xfce4-volumed}} (if you are using Xfce).<br />
<br />
Also, if you are using PulseAudio, sometimes it thinks HDMI is the default sound card; to solve this problem, install {{pkg|pavucontrol}} and set Analog Stereo as the fallback device.<br />
<br />
=== Touchpad ===<br />
One method is to install {{pkg|xf86-input-synaptics}} and configure to your liking in {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}:<br />
Section "InputClass"<br />
MatchIsTouchpad "on"<br />
Identifier "touchpad catchall"<br />
Driver "synaptics"<br />
# 1 = left, 2 = right, 3 = middle<br />
Option "TapButton1" "1" <br />
Option "TapButton2" "3"<br />
Option "TapButton3" "2"<br />
# Palm detection<br />
Option "PalmDetect" "1"<br />
# Horizontal scrolling<br />
Option "HorizTwoFingerScroll" "1"<br />
# Natural Scrolling (and speed)<br />
Option "VertScrollDelta" "-100"<br />
Option "HorizScrollDelta" "-100"<br />
EndSection<br />
<br />
=== Keyboard backlight ===<br />
* Works, see [[MacBook#Keyboard_Backlight]]<br />
<br />
=== Screen backlight ===<br />
* Intel, works on Linux 3.13<br />
* Framebuffer, works for MacBook Pro 11,1 and 11,3 via {{ic|/sys/class/backlight/gmux_backlight/brightness}}.<br />
* Nvidia, does not work<br />
{{note|If the screen doesn't show the prompt or the login manager (i.e. a black screen), append {{ic|1=i915.invert_brightness=1}} to the kernel. }}<br />
<br />
=== Suspend ===<br />
* Works on MacBook Pro 11,2 with Linux 3.13<br />
* No backlight after suspend with Linux 3.12<br />
** Use hibernate instead<br />
<br />
== What does not work ==<br />
Updated 2013-12-07<br />
<br />
=== General ===<br />
<br />
=== Wi-Fi ===<br />
* {{AUR|broadcom-wl}} from the [[AUR]] works<br />
** Stability is an issue for some<br />
<br />
=== Web cam ===<br />
* Listed on PCI bus as: Multimedia controller: Broadcom Corporation Device 1570.<br />
* In OS X, the camera is listed as FaceTime HD camera 1570.<br />
* No known Linux driver.<br />
<br />
== Discussions ==<br />
* https://bbs.archlinux.org/viewtopic.php?id=171883<br />
<br />
== See also ==<br />
* [[MacBookPro10,x]]<br />
* [[MacBook]]</div>Gianguidohttps://wiki.archlinux.org/index.php?title=Palm_Pre_(Italiano)&diff=121591Palm Pre (Italiano)2010-11-17T12:58:04Z<p>Gianguido: /* Installazione */</p>
<hr />
<div>[[Category:smartphones]]<br />
Il Palm Pre è uno smartphone prodotto da Palm Inc. dal 2009 in poi, avente sistema operativo basato su Linux chiamato webOS.<br />
Questa pagina vuole aiutare i possessori di questo smartphone ad integrarlo al meglio col proprio sistema Arch.<br />
<br />
=Installazione=<br />
Quasi la maggioranza delle applicazioni lato desktop per gestire il Palm Pre sono scritte in [[Java]], di conseguenza necessitiamo di quest'ultimo.<br />
Installiamo la versione open source chiamata OpenJDK (da root):<br />
pacman -S openjdk6<br />
Fatto ciò, è importante installare l'SDK distribuito da Palm per assicurarci la possibilità di ripristinare il sistema operativo del nostro device in caso di necessità.<br />
Visto che è disponibile solamente pacchettizzato in .deb, su [[AUR]].<br />
C'è una correzione da fare al PKGBUILD visto che quest'ultimo vuole installare una versione di VirtualBox troppo vecchia e non disponibile su AUR, oltre che la Java virtual machine distribuita da Oracle.<br />
Ecco il PKGBUILD corretto:<br />
# Contributor: Ryan Corder <ryanc@greengrey.org><br />
<br />
pkgname=palm-sdk<br />
pkgver=1.4.5<br />
pkgrel=1<br />
pkgdesc="Unofficial package of Palm webOS SDK"<br />
url="http://developer.palm.com/index.php"<br />
arch=('i686' 'x86_64')<br />
license=("unknown")<br />
depends=('virtualbox_bin' 'palm-novacom=1.0.56') <br />
source=("http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/palm-sdk_1.4.5-svn307799-sdk1457-pho465_i386.deb")<br />
noextract=()<br />
install=('palm-sdk.install')<br />
md5sums=('dc85db1897d0aa31e4c50130184ac508')<br />
<br />
build() {<br />
cd $startdir/src<br />
<br />
ar x $startdir/palm-sdk_1.4.5-svn307799-sdk1457-pho465_i386.deb || return 1<br />
mkdir data || return 1<br />
<br />
tar zxvf $startdir/src/data.tar.gz -C $startdir/pkg || return 1<br />
<br />
rm -rf $startdir/pkg/usr/local || return 1<br />
rm -rf $startdir/pkg/usr/share || return 1<br />
<br />
mkdir $startdir/pkg/usr/bin || return 1<br />
<br />
ln -s /opt/PalmSDK/Current/bin/palm-emulator $startdir/pkg/usr/bin/palm-emulator || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-generator $startdir/pkg/usr/bin/palm-generator || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-help $startdir/pkg/usr/bin/palm-help || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-inspector $startdir/pkg/usr/bin/palminspector || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-install $startdir/pkg/usr/bin/palm-install || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-launch $startdir/pkg/usr/bin/palm-launch || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-log $startdir/pkg/usr/bin/palm-log || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-package $startdir/pkg/usr/bin/palm-package || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-worm $startdir/pkg/usr/bin/palm-worm || return 1 <br />
}<br />
Questo invece il file <tt>palm-sdk.install</tt>:<br />
# $Id: $<br />
#<br />
# Description: post-install script for palm-sdk<br />
# Contributor: Ryan Corder <ryanc@greengrey.org><br />
#<br />
<br />
# arg 1:new package version<br />
post_install() {<br />
echo<br />
echo "The following entires will likely be required for you to add to"<br />
echo "your /etc/hosts file:"<br />
echo<br />
echo "# Added for palm-sdk"<br />
echo "127.0.0.1 qemu"<br />
echo "# Added for palmtools"<br />
echo "127.0.0.1 device"<br />
echo<br />
echo "Additionally, you should have this entry in your /etc/hosts file anyway:"<br />
echo<br />
echo "127.0.0.1 localhost"<br />
echo<br />
}<br />
<br />
post_upgrade() {<br />
post_install $1<br />
}<br />
<br />
op=$1<br />
shift<br />
<br />
$op $*<br />
Inserite questi due file in una stessa cartella, spostatevi in essa ed eseguite:<br />
makepkg<br />
Finita l'operazione, installate i file tar.pkg.xz con il comando (da root):<br />
pacman -U<br />
In ordine, installate prima VirtualBox, poi il Palm SDK.<br />
Fatto ciò, siete pronti anche allo sviluppo di applicazioni per webOS. Se avreste bisogno di un IDE, questo [http://developer.palm.com/index.php?option=com_content&id=1639 link] contiene tutto il necessario per sviluppare con [[Eclipse]]<br />
<br />
=Configurazione=<br />
Alcune applicazioni, come webOS Doctor, necessitano del daemon <tt>novacomd</tt> avviato in background.<br />
Per automatizzare ciò, bisogna aggiungere <br />
novacomd<br />
allo spazio <tt>DAEMONS</tt> nel file<br />
/etc/rc.conf<br />
Casomai voleste avviarlo al momento, basta eseguire (con i permessi di root):<br />
/etc/rc.d/novacomd start<br />
Per stopparlo:<br />
/etc/rc.d/novacomd stop<br />
<br />
=Tips & Tricks=<br />
Per eseguire un file .jar, è necessario passare a <tt>java</tt> l'opzione ''-jar'':<br />
java -jar filejava</div>Gianguidohttps://wiki.archlinux.org/index.php?title=Palm_Pre_(Italiano)&diff=121565Palm Pre (Italiano)2010-11-16T19:50:12Z<p>Gianguido: Created page with "Category:smartphones Il Palm Pre è uno smartphone prodotto da Palm Inc. dal 2009 in poi, avente sistema operativo basato su Linux chiamato webOS. Questa pagina vuole aiutare..."</p>
<hr />
<div>[[Category:smartphones]]<br />
Il Palm Pre è uno smartphone prodotto da Palm Inc. dal 2009 in poi, avente sistema operativo basato su Linux chiamato webOS.<br />
Questa pagina vuole aiutare i possessori di questo smartphone ad integrarlo al meglio col proprio sistema Arch.<br />
<br />
=Installazione=<br />
Quasi la maggioranza delle applicazioni lato desktop per gestire il Palm Pre sono scritte in [[Java]], di conseguenza necessitiamo di quest'ultimo.<br />
Installiamo la versione open source chiamata OpenJDK (da root):<br />
pacman -S openjdk6<br />
Fatto ciò, è importante installare l'SDK distribuito da Palm per assicurarci la possibilità di ripristinare il sistema operativo del nostro device in caso di necessità.<br />
Visto che è disponibile solamente pacchettizzato in .deb, su [[AUR]].<br />
C'è una correzione da fare al PKGBUILD visto che quest'ultimo vuole installare una versione di VirtualBox troppo vecchia e non disponibile su AUR, oltre che la Java virtual machine distribuita da Oracle.<br />
Ecco il PKGBUILD corretto:<br />
# Contributor: Ryan Corder <ryanc@greengrey.org><br />
<br />
pkgname=palm-sdk<br />
pkgver=1.4.5<br />
pkgrel=1<br />
pkgdesc="Unofficial package of Palm webOS SDK"<br />
url="http://developer.palm.com/index.php"<br />
arch=('i686' 'x86_64')<br />
license=("unknown")<br />
depends=('virtualbox_bin' 'palm-novacom=1.0.56') <br />
source=("http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/palm-sdk_1.4.5-svn307799-sdk1457-pho465_i386.deb")<br />
noextract=()<br />
install=('palm-sdk.install')<br />
md5sums=('dc85db1897d0aa31e4c50130184ac508')<br />
<br />
build() {<br />
cd $startdir/src<br />
<br />
ar x $startdir/palm-sdk_1.4.5-svn307799-sdk1457-pho465_i386.deb || return 1<br />
mkdir data || return 1<br />
<br />
tar zxvf $startdir/src/data.tar.gz -C $startdir/pkg || return 1<br />
<br />
rm -rf $startdir/pkg/usr/local || return 1<br />
rm -rf $startdir/pkg/usr/share || return 1<br />
<br />
mkdir $startdir/pkg/usr/bin || return 1<br />
<br />
ln -s /opt/PalmSDK/Current/bin/palm-emulator $startdir/pkg/usr/bin/palm-emulator || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-generator $startdir/pkg/usr/bin/palm-generator || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-help $startdir/pkg/usr/bin/palm-help || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-inspector $startdir/pkg/usr/bin/palminspector || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-install $startdir/pkg/usr/bin/palm-install || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-launch $startdir/pkg/usr/bin/palm-launch || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-log $startdir/pkg/usr/bin/palm-log || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-package $startdir/pkg/usr/bin/palm-package || return 1<br />
ln -s /opt/PalmSDK/Current/bin/palm-worm $startdir/pkg/usr/bin/palm-worm || return 1 <br />
}<br />
Fatto ciò, siete pronti anche allo sviluppo di applicazioni per webOS. Se avreste bisogno di un IDE, questo [http://developer.palm.com/index.php?option=com_content&id=1639 link] contiene tutto il necessario per sviluppare con [[Eclipse]]<br />
<br />
=Configurazione=<br />
Alcune applicazioni, come webOS Doctor, necessitano del daemon <tt>novacomd</tt> avviato in background.<br />
Per automatizzare ciò, bisogna aggiungere <br />
novacomd<br />
allo spazio <tt>DAEMONS</tt> nel file<br />
/etc/rc.conf<br />
Casomai voleste avviarlo al momento, basta eseguire (con i permessi di root):<br />
/etc/rc.d/novacomd start<br />
Per stopparlo:<br />
/etc/rc.d/novacomd stop<br />
<br />
=Tips & Tricks=<br />
Per eseguire un file .jar, è necessario passare a <tt>java</tt> l'opzione ''-jar'':<br />
java -jar filejava</div>Gianguido