https://wiki.archlinux.org/api.php?action=feedcontributions&user=Stanto&feedformat=atomArchWiki - User contributions [en]2024-03-28T15:46:28ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Steam_Deck&diff=787843Steam Deck2023-09-16T16:48:01Z<p>Stanto: /* Shortcuts */ added instructions for accessing efi boot menu</p>
<hr />
<div>[[Category:Ultra-mobile PC]]<br />
[[ja:Steam Deck]]<br />
{{Warning|SteamOS is an Arch based distribution, it has [https://steamdeck-packages.steamos.cloud/archlinux-mirror/ several packages] that differ from the [[official repositories]]. It is [[code of conduct#arch-linux-distribution-support-only|not supported]] by the Arch Linux support staff.}}<br />
<br />
{{Expansion|Mention {{AUR|opensd-git}}.}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
|-<br />
! Hardware !! PCI/USB ID !! Working?<br />
|-<br />
| microSD card reader || {{ic|1217:8621}} || {{Yes}}<br />
|-<br />
| WiFi || {{ic|10ec:c822}} || {{Yes}}<br />
|-<br />
| GPU || {{ic|1002:163f}} || {{Yes}}<br />
|-<br />
| Audio || {{ic|1002:1640}} || {{Yes}}<br />
|-<br />
| Bluetooth || {{ic|13d3:3553}} || {{Yes}}<br />
|-<br />
| Gyroscope || || {{Yes}}<br />
|-<br />
| Touchpads || || {{Yes}}<br />
|-<br />
| Touchscreen || || {{Yes}}<br />
|-<br />
| Steam Deck controls || {{ic|28de:1205}} || {{Yes}}<br />
|}<br />
The [https://www.steamdeck.com Steam Deck] is a custom PC hardware from Valve that is focused on gaming. It can, however, also be used as a regular PC, and comes with a customized [[Plasma]] session. Also, it is completely unlocked, so one could install any OS they wish on it, including [[Arch Linux]].<br />
<br />
== Installation ==<br />
<br />
A [[USB flash installation medium]] can be used through the microSD card slot or the USB-C port.<br />
<br />
While booting up the deck, hold down {{ic|Volume Down}} and press the {{ic|Power}} buttons. Choose your Arch Linux [[USB flash installation medium|installation medium]].<br />
<br />
== Firmware ==<br />
<br />
As of October 2022, {{Pkg|fwupd}} does not support any devices in the Steam Deck. Updates for the firmware are provided through SteamOS. <br />
<br />
=== Shortcuts ===<br />
<br />
* Hold down {{ic|Volume Up}} and press the {{ic|Power}} button to access the UEFI settings, <br />
* Hold down {{ic|Volume Down}} and press the {{ic|Power}} button to access the boot menu, <br />
* Hold down {{ic|Three Dots Button}} and press the {{ic|Power}} button to access the SteamOS efi boot menu,<br />
* Hold down {{ic|Volume Down+Power+⋯}} (the button under the right touchpad) to reset the UEFI settings to their defaults (keep the two buttons other than {{ic|Power}} held after the first blink of the LED: the LED will blink during the operation and stop once done, then release the buttons).<br />
<br />
=== Advanced settings ===<br />
<br />
{{Warning|<br />
* As opposed to regular UEFI settings available on consumer boards, there are no guardrails after following the instructions below: [https://steamdeckhq.com/news/undervolting-and-overclocking-push-your-steam-deck-beyond-its-limits/#comment-1995 backup your firmware], it is possible to completely "brick" your device, which then requires an SPI chip programmer to fix.<br />
* While undervolting will at worst "brick" your device, overclocking or overvolting should be done with the [[Wikipedia:Overclocking#Disadvantages|usual caveats]] in mind.<br />
}}<br />
<br />
AMD's CBS (''C''ustom ''B''IOS ''S''ettings) and PBS (''P''latform ''B''IOS ''S''ettings) are not accessible by default, but can be [https://gist.github.com/SmokelessCPUv2/8c1e6559031e199d9a678c9fe2ebf7d4 unlocked] (running the resulting binary will be silent and finish with a return code of 119) to have access to undervolting and overclocking options. These options are then visible when booting into the Steam Deck firmware, but there are [https://www.stanto.com/games/unlocking-the-steam-deck-bios-for-under-voltage-and-over-clocking/ restrictions on the TDP settings] that can be overcome using a [https://github.com/DavidS95/Smokeless_UMAF different method of loading the UEFI form browser].<br />
<br />
A [https://github.com/badly-drawn-wizards/vangogh_oc_fix fix is needed] for AMD Van Gogh APU PowerPlay limits to scale properly after higher frequencies are set when overclocking the CPU and GPU of the APU in the BIOS after unlocking it.<br />
<br />
== Fan controls ==<br />
<br />
The Steam Deck's fan control can be enhanced by a daemon provided in Valve's ''jupiter'' repository, but are fully functional without it. <br />
<br />
If you are using a mainline kernel, you need [https://gitlab.com/evlaV/linux-integration/-/commits/features/platform patches from Valve's kernel] to expose the corresponding ACPI functionality, for example by installing the {{AUR|linux-steamos}} kernel.<br />
<br />
== See also ==<br />
<br />
* [https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3 Steam Deck Recovery Instructions]<br />
* [https://linux-hardware.org/?probe=a0ee1dbeff Linux Hardware Database probe]</div>Stantohttps://wiki.archlinux.org/index.php?title=Steam_Deck&diff=781170Steam Deck2023-06-15T23:51:10Z<p>Stanto: /* Advanced settings */ added information about restrictions from amdgpu powerplay and restrictions on power limits set in the bios.</p>
<hr />
<div>[[Category:Ultra-mobile PC]]<br />
[[ja:Steam Deck]]<br />
{{Warning|SteamOS is an Arch based distribution, it has [https://steamdeck-packages.steamos.cloud/archlinux-mirror/ several packages] that differ from the [[official repositories]]. It is [[code of conduct#arch-linux-distribution-support-only|not supported]] by the Arch Linux support staff.}}<br />
<br />
{{Expansion|Mention {{AUR|opensd-git}}.}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
|-<br />
! Hardware !! PCI/USB ID !! Working?<br />
|-<br />
| microSD card reader || {{ic|1217:8621}} || {{Yes}}<br />
|-<br />
| WiFi || {{ic|10ec:c822}} || {{Yes}}<br />
|-<br />
| GPU || {{ic|1002:163f}} || {{Yes}}<br />
|-<br />
| Audio || {{ic|1002:1640}} || {{Yes}}<br />
|-<br />
| Bluetooth || {{ic|13d3:3553}} || {{Yes}}<br />
|-<br />
| Gyroscope || || {{Yes}}<br />
|-<br />
| Touchpads || || {{Yes}}<br />
|-<br />
| Touchscreen || || {{Yes}}<br />
|-<br />
| Steam Deck controls || {{ic|28de:1205}} || {{Yes}}<br />
|}<br />
The [https://www.steamdeck.com Steam Deck] is a custom PC hardware from Valve that is focused on gaming. It can, however, also be used as a regular PC, and comes with a customized [[Plasma]] session. Also, it is completely unlocked, so one could install any OS they wish on it, including [[Arch Linux]].<br />
<br />
== Installation ==<br />
<br />
A [[USB flash installation medium]] can be used through the microSD card slot or the USB-C port.<br />
<br />
While booting up the deck, hold down {{ic|Volume Down}} and press the {{ic|Power}} buttons. Choose your Arch Linux [[USB flash installation medium|installation medium]].<br />
<br />
== Firmware ==<br />
<br />
As of October 2022, {{Pkg|fwupd}} does not support any devices in the Steam Deck. Updates for the firmware are provided through SteamOS. <br />
<br />
=== Shortcuts ===<br />
<br />
* Hold down {{ic|Volume Up}} and press the {{ic|Power}} button to access the UEFI settings, <br />
* Hold down {{ic|Volume Down}} and press the {{ic|Power}} button to access the boot menu, <br />
* Hold down {{ic|Volume Down+Power+⋯}} (the button under the right touchpad) to reset the UEFI settings to their defaults (keep the two buttons other than {{ic|Power}} held after the first blink of the LED: the LED will blink during the operation and stop once done, then release the buttons).<br />
<br />
=== Advanced settings ===<br />
<br />
{{Warning|As opposed to regular UEFI settings available on consumer boards, there are no guardrails after following the instructions below: [https://steamdeckhq.com/news/undervolting-and-overclocking-push-your-steam-deck-beyond-its-limits/#comment-1995 backup your firmware], it is possible to completely brick your device, which then requires an SPI chip programmer to fix.}}<br />
<br />
AMD's CBS (''C''ustom ''B''IOS ''S''ettings) and PBS (''P''latform ''B''IOS ''S''ettings) are not accessible by default, but can be [https://gist.github.com/SmokelessCPUv2/8c1e6559031e199d9a678c9fe2ebf7d4 unlocked] (running the resulting binary will be silent and finish with a return code of 119) to have access to undervolting and overclocking options. These options are then visible when booting into the Steam Deck BIOS, but there are [https://www.stanto.com/games/unlocking-the-steam-deck-bios-for-under-voltage-and-over-clocking/ restrictions on the TDP settings] that can be overcome using a [https://github.com/DavidS95/Smokeless_UMAF different method of loading the UEFI form browser].<br />
<br />
A [https://github.com/badly-drawn-wizards/vangogh_oc_fix fix is needed] for AMD Van Gogh APU PowerPlay limits to scale properly after higher frequencies are set when overclocking the CPU and GPU of the APU in the BIOS after unlocking it.<br />
<br />
== Fan controls ==<br />
<br />
The Steam Deck's fan control can be enhanced by a daemon provided in Valve's ''jupiter'' repository, but are fully functional without it. <br />
<br />
If you are using a mainline kernel, you need [https://gitlab.com/evlaV/linux-integration/-/commits/features/platform patches from Valve's kernel] to expose the corresponding ACPI functionality, for example by installing the {{AUR|linux-steamos}} kernel.<br />
<br />
<br />
== See also ==<br />
<br />
* [https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3 Steam Deck Recovery Instructions]<br />
* [https://linux-hardware.org/?probe=a0ee1dbeff Linux Hardware Database probe]</div>Stantohttps://wiki.archlinux.org/index.php?title=Huawei_E220&diff=131325Huawei E2202011-02-17T19:01:42Z<p>Stanto: /* Packages */ Don't delete the page, it's useful for reference and has link to useful file in next section. AUR package is dead though.</p>
<hr />
<div>[[Category:Communication and network (English)]]<br />
<br />
= Introduction =<br />
Marketed by various telecommunications companies in several countries, the [http://en.wikipedia.org/wiki/Huawei_E220 E220] is a 3.5G HSDPA USB modem used mainly for wireless Internet access via mobile telephony networks. Technically it is a modem, USB and (due to the CDFS format) CD-ROM device. With a kernel version older than 2.6.20, getting Linux to recognize the device as a modem and accessing its functions requires a workaround.<br />
<br />
''"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."''<br />
<br />
However, as support for it was added in 2.6.20 via modules ''usb-storage'' and ''usbserial'', getting it to work is as simple as plugging it in and dialling up (the above statement is of no concern to us as we can load and unload modules at will, it was probably meant for pre-packaged GNU and Linux distributions). In fact, using the modem under Linux proves to be more reliable as there are no uncalled-for disconnections. This is probably due to the fact that we are communicating directly with the modem, whereas in Windows or Mac OS X drivers are installed on first run (that is what the storage portion is for) and connection is achieved through a thick software layer every time, leaving room for possible interferences and conflicts.<br />
<br />
= Plugging In =<br />
Archers do not use old stuff, let alone use old kernels. That is, however, not enough reason to explain why in some cases the modem still needs the workaround. Thus, you have to see for yourself if you are one of the lucky ones. It almost seems as if the "support" in kernels > 2.6.20 is a myth, although that may be entirely incorrect (maybe it is how Arch developers package the vanilla kernels in which case we have only [http://www.archlinux.org/developers/ phrakkkture and gang] to thank).<br />
<br />
The magic (trick) lies in the kernel modules; udev rules, unloading, blacklisting, reloading and loading things will get it done.<br />
<br />
== Quick Start ==<br />
=== Easy Install using Network Manager ===<br />
If you are using network-manager then this modem should be plug 'n play. I tested using Huawei E270, but since lsusb said that my modem is E220/E270 then I assume it is the same.<br />
<br />
The required packages are modemmanager and network-manager-applet from extra.<br />
<br />
Start the networkmanager demon from rc.conf or manually using /etc/rc.d/networkmanager start. Start the nm-applet if it hasn't started yet. <br />
Make sure the modem is connected; I used a cable with two usb port like the one for an external harddrive. Then from nm-applet add a wireless broadband config using the edit connection button. Set the config according your network; usually apn, username, and password.<br />
Activate the connection by choosing it. And it will try to connect, once it is connected the icon will change. You're good to go then.<br />
<br />
<br />
For ''Vodafone'' brands of this device, you can use [http://aur.archlinux.org/packages.php?ID=32986 vodafone-mccd] which is the [http://forge.vodafonebetavine.net/projects/vodafonemobilec/ Vodafone Mobile Connect Card Driver for Linux]. The official name is very long, yes.<br />
<br />
=== Scripting ===<br />
If you have UDEV and HAL set up right but do not want extra bulk like an entire package (yeah right as if it adds a GiB full of stuff), then have no fear - bash is here. You can have my custom "installer" which incorporates everything including the HAL and UDEV rules. You can change the default installation of stuff to '''/usr''' instead of '''/usr/local''' if you want. Well, you can change anything if you want (or can). Download the [http://www.mediafire.com/?l5jtywnmycn tar archive] and then extract it and ''pwn'' it:<br />
$ tar xf huawei-e220.tar.gz<br />
$ cd huawei-e220<br />
$ nano setup.sh # if you want to<br />
# ./setup.sh<br />
Enjoy me lad!<br />
<br />
=== Bare Naked ===<br />
You can just try ''Plug 'n Dial'' first to see if it works (I will give you free beer if it does!). After hooking up to the USB port (some say an upright position is best; let it hang over the edge of the desk), check to make sure it is detected.<br />
$ cat /proc/bus/usb/devices<br />
You should see '''Huawei''' somewhere there. If not, you are on your own. The ''usb-storage'' and/or ''usbserial'' modules must be loaded, whether manually or by [[HAL]] is up to you and/or your system.<br />
# modprobe usb-storage<br />
# modprobe usbserial<br />
$ sleep 6 # the modem may take a while to initialize<br />
$ ls /dev/ttyUSB*<br />
You should see three renditions of '''ttyUSB'''. If not, we will get to that later. This ''is'' a "Quick Start" after all, no? The ports:<br />
* ttyUSB0 - Modem<br />
* ttyUSB1 - USB?<br />
* ttyUSB2 - Nothing<br />
Now you need a dialler. Most convenient of all would be ''wvdial'', so install it. You should have ''ppp'' already, if not just pull them both in.<br />
# pacman -S wvdial ppp<br />
<br />
=== Configure n' Dial ===<br />
Most SIM and data services provided together with the device do not require special settings and work with similar configuration to get connected. They are almost "Plug n' Play", a special trait of Linux. Edit ''/etc/wvdial.conf'' and use something like the following:<br />
[Dialer hsdpa]<br />
Phone = *99***16#<br />
Username = 65<br />
Password = user123<br />
Stupid Mode = 1<br />
Dial Command = ATDT<br />
Modem = /dev/ttyUSB0<br />
Baud = 460800<br />
Init2 = ATZ<br />
Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0<br />
ISDN = 0<br />
Modem Type = Analog Modem<br />
<br />
For providers that do require a specific Init string and user/password combination, [http://aur.archlinux.org/packages.php?ID=29534 mkwvconf-git] in AUR can help generate a wvdial configuration (based on the [http://aur.archlinux.org/packages.php?ID=29530 mobile-broadband-provider-info-git] package).<br />
<br />
=== If using PIN code add this before Init2 ===<br />
Init1 = AT+CPIN=9999<br />
where 9999 is changed for your PIN-code<br />
<br />
There is an example [http://www.insync.za.net/3g_docs/wvdial.conf here] by a "Linux Guru". Then load the PPP module.<br />
# modprobe ppp-generic<br />
You can now connect immediately, but probably only as root, which is '''not''' a disadvantage.<br />
# wvdial hsdpa<br />
<br />
== Slow Start ==<br />
<br />
''Edit: This section is nullified if you have UDEV and HAL workarounds, or a script, or a package from AUR.''<br><br />
<br />
So why then? Well, for some reason those of us on newer kernels still have to ride the old ways. In some cases, all that is needed to be done is to remove the ''usb-storage'' module first, then load ''usbserial'' with the device IDs. The first ''cat'' command on this page will have that information, while ''lsusb'' is an alternative. Anyhow, the IDs are the same for almost all E220s, so you can copy wholesale.<br />
# modprobe -r usb-storage usbserial<br />
# modprobe usbserial vendor=0x12d1 product=0x1003<br />
In other cases, where the ''option'' module gets autoloaded for use by ''usbserial'', you just have to blacklist it in [[rc.conf]]:<br />
MOD_BLACKLIST=(option) <br />
When you cannot salvage anything from this either, you have to ''go Gentoo'' and compile something. Do not worry, it is only a script and we do things like this almost everyday, albeit in ''bash''.<br />
$ mkdir ~/huawei-e220 && cd ~/huawei-e220<br />
$ wget http://www.kanoistika.sk/bobovsky/archiv/umts/huaweiAktBbo.c<br />
$ gcc -lusb -o e220 *.c<br />
# ./e220<br />
This gets around the kernel to recognize the modem functionalities of the device. You can now carry on and connect using the above methods. If you had to follow this step, you will always need the script unless you set ''udev'' rules and such (package link below). So move it to a global ''PATH''.<br />
$ cd ~/huawei-e220<br />
# mv e220 /usr/bin/e220<br />
Now it is easier.<br />
<br />
= Extras =<br />
''Note: It seems some people get it to work using ttyUSB1, which should not be the case, but rest assured that at least on recent kernels and systems ttyUSB0 is the correct port to dial with.''<br />
<br />
== Port Testing ==<br />
To check if the device is functioning alright on a particular serial port, there is a program for probing serial devices.<br />
# pacman -S minicom<br />
Now run it.<br />
# minicom -s<br />
Change the serial port to ''/dev/ttyUSB1'' and exit from the page, this will open the main program. When it initializes the modem, issue the command ''AT''. The answer should be ''OK'', which means the modem is working well on that port.<br />
<br />
= Troubleshooting =<br />
<br />
== Hal ==<br />
<br />
The hald daemon detects the SCSI CD-ROM drive and because of that it will try to change the modem to storage mode. To prevent this you need to create a Hal policy so it ignores the device.<br />
<br />
Create a file the /usr/share/hal/fdi/preprobe/20thirdparty/10-huawei-e220.fdi and putt this in it<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<deviceinfo version="0.2"><br />
<device><br />
<match key="usb.vendor_id" int="0x12d1"> <!-- Huawei --><br />
<match key="usb.product_id" int="0x1003"> <!-- E220 --><br />
<merge key="info.ignore" type="bool">true</merge><br />
</match><br />
</match><br />
</device><br />
</deviceinfo><br />
With this, for my experience, only two USB serial ports are created and them vodafone-mccd doesn't recognize correctly the modem but you can connect correctly with wvdial.<br />
<br />
== Route ==<br />
<br />
If problem with connection through ppp0 one might need to add the network manually:<br />
route add -net 10.0.0.0 netmask 255.0.0.0 ppp0 <br />
if the remote adress starts on 10.<br />
<br />
Then you add default route and dns as usually:<br />
route add default gw 10.x.x.x<br />
(change to remote adress recieved and viewed with ifconfig)<br />
<br />
= Links =<br />
http://wwwu.uni-klu.ac.at/agebhard/HuaweiE220/<br><br />
http://oozie.fm.interia.pl/pro/huawei-e220/<br><br />
http://mybroadband.co.za/vb/showthread.php?t=21726<br><br />
[[USB 3G Modem]]</div>Stantohttps://wiki.archlinux.org/index.php?title=TFTP&diff=68421TFTP2009-05-08T04:35:41Z<p>Stanto: /* Configuration */ in case mkpxeboot confuses anyone or doesn't work</p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
{{stub}}<br />
<br />
== Introduction ==<br />
This HOWTO describes how to set up a tftpd server under Arch Linux.<br />
<br />
== Installation ==<br />
The first thing is to install all necessary stuff:<br />
# pacman -S mkpxelinux tftp-hpa dhcpcd<br />
<br />
== Configuration ==<br />
At first we will create a /etc/dhcpd.conf file. It has to look like this (basic dhcpd config):<br />
<br />
ddns-update-style interim;<br />
<br />
subnet *'''your subnet'''* netmask *'''your netmask'''* {<br />
option routers *'''IP of your router'''*;<br />
option subnet-mask *'''your subnet again'''*;<br />
<br />
option domain-name "'''here you can put your domain name if you dont have one take example.com'''";<br />
<br />
option time-offset -18000; # Eastern Standard Time<br />
next-server *'''IP of your machine where dhcpd is running'''*;<br />
filename "pxelinux.0";<br />
<br />
allow booting;<br />
allow bootp;<br />
<br />
range *'''the range of ip addresses your dhcpd is allow to take, example: 10.0.0.10 10.0.0.200'''*;<br />
}<br />
<br />
Remove the ** from the config.<br />
<br />
After this you have to run:<br />
# mkpxeboot -a<br />
<br />
Or run <code>mkpxelinux</code>, which will put the required boot files in <code>/var/tftpboot</code>.<br />
<br />
~# mkpxelinux -c=/etc/mkpxelinux.conf<br />
<br />
This will create all images and stuff to boot.<br />
<br />
Now we replace the kernel and the initrd.img with the newest from the install iso.<br />
$ wget ftp://ftp.archlinux.org/other/0.8/i686/ftp-0.8-beta2-20070222-i686.iso<br />
When the download is finished, we nearly finished.<br />
# mount -o loop /where/the/iso/is/located /path/to/mount/<br />
# cp /path/to/mount/isolinux/initd.img /var/tftpboot/<br />
# cp /path/to/mount/isolinux/vmlinuz /var/tftpboot/<br />
<br />
Now last config and then we can load all the stuff:<br />
# nano /etc/hosts.allow<br />
Add these lines:<br />
tftpd: ALL<br />
in.tftpd: ALL<br />
<br />
Now do:<br />
# /etc/rc.d/tftpd start<br />
And in a terminal:<br />
# dhcpd<br />
<br />
Now you can start the PC you want to install.<br />
<br />
Good Luck!</div>Stantohttps://wiki.archlinux.org/index.php?title=TFTP&diff=68420TFTP2009-05-08T04:13:46Z<p>Stanto: /* Installation */</p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
{{stub}}<br />
<br />
== Introduction ==<br />
This HOWTO describes how to set up a tftpd server under Arch Linux.<br />
<br />
== Installation ==<br />
The first thing is to install all necessary stuff:<br />
# pacman -S mkpxelinux tftp-hpa dhcpcd<br />
<br />
== Configuration ==<br />
At first we will create a /etc/dhcpd.conf file. It has to look like this (basic dhcpd config):<br />
<br />
ddns-update-style interim;<br />
<br />
subnet *'''your subnet'''* netmask *'''your netmask'''* {<br />
option routers *'''IP of your router'''*;<br />
option subnet-mask *'''your subnet again'''*;<br />
<br />
option domain-name "'''here you can put your domain name if you dont have one take example.com'''";<br />
<br />
option time-offset -18000; # Eastern Standard Time<br />
next-server *'''IP of your machine where dhcpd is running'''*;<br />
filename "pxelinux.0";<br />
<br />
allow booting;<br />
allow bootp;<br />
<br />
range *'''the range of ip addresses your dhcpd is allow to take, example: 10.0.0.10 10.0.0.200'''*;<br />
}<br />
<br />
Remove the ** from the config.<br />
<br />
After this you have to run:<br />
# mkpxeboot -a<br />
<br />
This will create all images and stuff to boot.<br />
<br />
Now we replace the kernel and the initrd.img with the newest from the install iso.<br />
$ wget ftp://ftp.archlinux.org/other/0.8/i686/ftp-0.8-beta2-20070222-i686.iso<br />
When the download is finished, we nearly finished.<br />
# mount -o loop /where/the/iso/is/located /path/to/mount/<br />
# cp /path/to/mount/isolinux/initd.img /var/tftpboot/<br />
# cp /path/to/mount/isolinux/vmlinuz /var/tftpboot/<br />
<br />
Now last config and then we can load all the stuff:<br />
# nano /etc/hosts.allow<br />
Add these lines:<br />
tftpd: ALL<br />
in.tftpd: ALL<br />
<br />
Now do:<br />
# /etc/rc.d/tftpd start<br />
And in a terminal:<br />
# dhcpd<br />
<br />
Now you can start the PC you want to install.<br />
<br />
Good Luck!</div>Stantohttps://wiki.archlinux.org/index.php?title=NetworkManager&diff=42342NetworkManager2008-06-01T14:01:45Z<p>Stanto: /* Xfce */</p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Deutsch|:Networkmanager (Deutsch)}}<br />
{{i18n_entry|English|:NetworkManager}}<br />
{{i18n_entry|Italiano|:NetworkManager (Italiano)}}<br />
{{i18n_entry|Português do Brasil|:NetworkManager (Português)}}<br />
{{i18n_entry|简体中文|:网络管理器}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
NetworkManager is an advanced network connection tool. It attempts to make networking invisible to the end user, so that when moving into areas you've been before, NetworkManager automatically connects to the last network you chose to connect to.<br />
<br />
= Installation =<br />
Check that '''wireless_tools''' is installed first, otherwise Networkmanager won't work.<br />
<br />
Also check that HAL[[http://wiki.archlinux.org/index.php/HAL]] is installed, and loaded as a daemon in rc.conf.<br />
<br />
==Gnome==<br />
# pacman -S gnome-network-manager<br />
<br />
==KDE==<br />
# pacman -S knetworkmanager<br />
<br />
==Xfce==<br />
Xfce uses the same package as GNOME, however it requires the xfapplet plugin as well, which allows GNOME applets to be displayed within the xfce4-panel:<br />
# pacman -S gnome-network-manager xfce4-xfapplet-plugin<br />
<br />
If after installation you get four or more instances of nm-applet running when automatically starting gnome services and you're not using a session manager; consider doing the following:<br />
1) Kill all nm-applet processes<br />
2) Add nm-applet --sm-disable to the autostarted applications.<br />
3) Log out of xfce.<br />
4) Delete the XFCE session file (in ~/.cache/sessions/)<br />
5) Log into xfce and all is good.<br />
<br />
==Fluxbox and Other WM's==<br />
You will need the hicolor theme to be able to run nm-applet:<br />
<br />
# pacman -S gnome-network-manager hicolor-icon-theme<br />
<br />
After configuring your system for use with the network manager, to autostart the network manager applet, go to<br />
settings --> Autostarted Applications then add, "nm-applet --sm-disable", This should start up the network manager applet<br />
on startup, the "--sm-disable" option is used to prevent multiple instances of the nm-applet, you should only need it if multiple instances are running when you startup.<br />
<br />
=Configuration=<br />
If you want to use NetworkManager on an interface you will have to '''disable''' it in /etc/rc.conf. You can do this by placing a '!' in front of the interface of your choice, for example:<br />
INTERFACES=(lo !eth0 !ath0)<br />
<br />
NetworkManager parses your /etc/rc.conf to see if you want to have a static or dynamic IP on your interfaces.<br />
<br />
So just put your preferred config into it.<br />
<br />
example for static IP:<br />
eth0="eth0 172.19.3.18 netmask 255.255.255.0 broadcast 172.19.3.255"<br />
<br />
example for dynamic IP:<br />
eth0="dhcp"<br />
<br />
You must also "disable" the default ''network'' daemon, and add the ''dhcdbd'' and ''networkmanager'' daemons '''in this order''':<br />
<br />
DAEMONS=( ... !network '''dhcdbd networkmanager''' ... )<br />
<br />
'''''Note:''' If you happen to specify the ''fam'' daemon in your array, it ''must'' appear ''after'' networkmanager. The same also applies to ''portmap'' if specified.''<br />
<br />
Finally, add yourself to the network group as shown below (replacing USERNAME with the appropriate username):<br />
# gpasswd -a USERNAME network<br />
<br />
==Automatically unlock keyring in GNOME after login==<br />
<br />
This will prevent nm-applet from asking for your keyring password. Note that this will only work when logging in via GDM.<br />
<br />
In '''/etc/pam.d/gdm''', add these lines at the end of the 'auth', 'session' blocks: <br />
auth optional pam_gnome_keyring.so<br />
<br />
session optional pam_gnome_keyring.so auto_start<br />
<br />
In '''/etc/pam.d/passwd''', add this line to the 'password' block:<br />
<br />
password optional pam_gnome_keyring.so<br />
<br />
Next time you log in, you should get asked if you want the password to be unlocked automatically on login.<br />
<br />
See http://live.gnome.org/GnomeKeyring/Pam for reference.<br />
<br />
<br />
= Additional Resources =<br />
*[[Wireless Setup]] -- The wireless setup wiki<br />
*[http://www.gnome.org/projects/NetworkManager/ NetworkManager] - The official website for NetworkManager</div>Stantohttps://wiki.archlinux.org/index.php?title=NetworkManager&diff=42341NetworkManager2008-06-01T14:00:25Z<p>Stanto: /* Xfce */ Tidying</p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Deutsch|:Networkmanager (Deutsch)}}<br />
{{i18n_entry|English|:NetworkManager}}<br />
{{i18n_entry|Italiano|:NetworkManager (Italiano)}}<br />
{{i18n_entry|Português do Brasil|:NetworkManager (Português)}}<br />
{{i18n_entry|简体中文|:网络管理器}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
NetworkManager is an advanced network connection tool. It attempts to make networking invisible to the end user, so that when moving into areas you've been before, NetworkManager automatically connects to the last network you chose to connect to.<br />
<br />
= Installation =<br />
Check that '''wireless_tools''' is installed first, otherwise Networkmanager won't work.<br />
<br />
Also check that HAL[[http://wiki.archlinux.org/index.php/HAL]] is installed, and loaded as a daemon in rc.conf.<br />
<br />
==Gnome==<br />
# pacman -S gnome-network-manager<br />
<br />
==KDE==<br />
# pacman -S knetworkmanager<br />
<br />
==Xfce==<br />
Xfce uses the same package as GNOME, however it requires the xfapplet plugin as well, which allows GNOME applets to be displayed within the xfce4-panel:<br />
# pacman -S gnome-network-manager xfce4-xfapplet-plugin<br />
<br />
If after installation you get four instances of nm-applet running when automatically starting gnome services or otherwise; consider doing the following:<br />
1) Kill all nm-applet processes<br />
2) Add nm-applet --sm-disable to the autostarted applications.<br />
3) Log out of xfce.<br />
4) Delete the XFCE session file (in ~/.cache/sessions/)<br />
5) Log into xfce and all is good.<br />
<br />
==Fluxbox and Other WM's==<br />
You will need the hicolor theme to be able to run nm-applet:<br />
<br />
# pacman -S gnome-network-manager hicolor-icon-theme<br />
<br />
After configuring your system for use with the network manager, to autostart the network manager applet, go to<br />
settings --> Autostarted Applications then add, "nm-applet --sm-disable", This should start up the network manager applet<br />
on startup, the "--sm-disable" option is used to prevent multiple instances of the nm-applet, you should only need it if multiple instances are running when you startup.<br />
<br />
=Configuration=<br />
If you want to use NetworkManager on an interface you will have to '''disable''' it in /etc/rc.conf. You can do this by placing a '!' in front of the interface of your choice, for example:<br />
INTERFACES=(lo !eth0 !ath0)<br />
<br />
NetworkManager parses your /etc/rc.conf to see if you want to have a static or dynamic IP on your interfaces.<br />
<br />
So just put your preferred config into it.<br />
<br />
example for static IP:<br />
eth0="eth0 172.19.3.18 netmask 255.255.255.0 broadcast 172.19.3.255"<br />
<br />
example for dynamic IP:<br />
eth0="dhcp"<br />
<br />
You must also "disable" the default ''network'' daemon, and add the ''dhcdbd'' and ''networkmanager'' daemons '''in this order''':<br />
<br />
DAEMONS=( ... !network '''dhcdbd networkmanager''' ... )<br />
<br />
'''''Note:''' If you happen to specify the ''fam'' daemon in your array, it ''must'' appear ''after'' networkmanager. The same also applies to ''portmap'' if specified.''<br />
<br />
Finally, add yourself to the network group as shown below (replacing USERNAME with the appropriate username):<br />
# gpasswd -a USERNAME network<br />
<br />
==Automatically unlock keyring in GNOME after login==<br />
<br />
This will prevent nm-applet from asking for your keyring password. Note that this will only work when logging in via GDM.<br />
<br />
In '''/etc/pam.d/gdm''', add these lines at the end of the 'auth', 'session' blocks: <br />
auth optional pam_gnome_keyring.so<br />
<br />
session optional pam_gnome_keyring.so auto_start<br />
<br />
In '''/etc/pam.d/passwd''', add this line to the 'password' block:<br />
<br />
password optional pam_gnome_keyring.so<br />
<br />
Next time you log in, you should get asked if you want the password to be unlocked automatically on login.<br />
<br />
See http://live.gnome.org/GnomeKeyring/Pam for reference.<br />
<br />
<br />
= Additional Resources =<br />
*[[Wireless Setup]] -- The wireless setup wiki<br />
*[http://www.gnome.org/projects/NetworkManager/ NetworkManager] - The official website for NetworkManager</div>Stantohttps://wiki.archlinux.org/index.php?title=NetworkManager&diff=42340NetworkManager2008-06-01T13:59:39Z<p>Stanto: /* Xfce */ Irritating nm-applet configuration issues, solution may help others</p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Deutsch|:Networkmanager (Deutsch)}}<br />
{{i18n_entry|English|:NetworkManager}}<br />
{{i18n_entry|Italiano|:NetworkManager (Italiano)}}<br />
{{i18n_entry|Português do Brasil|:NetworkManager (Português)}}<br />
{{i18n_entry|简体中文|:网络管理器}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
NetworkManager is an advanced network connection tool. It attempts to make networking invisible to the end user, so that when moving into areas you've been before, NetworkManager automatically connects to the last network you chose to connect to.<br />
<br />
= Installation =<br />
Check that '''wireless_tools''' is installed first, otherwise Networkmanager won't work.<br />
<br />
Also check that HAL[[http://wiki.archlinux.org/index.php/HAL]] is installed, and loaded as a daemon in rc.conf.<br />
<br />
==Gnome==<br />
# pacman -S gnome-network-manager<br />
<br />
==KDE==<br />
# pacman -S knetworkmanager<br />
<br />
==Xfce==<br />
Xfce uses the same package as GNOME, however it requires the xfapplet plugin as well, which allows GNOME applets to be displayed within the xfce4-panel:<br />
# pacman -S gnome-network-manager xfce4-xfapplet-plugin<br />
<br />
If after installation you get four instances of nm-applet running when automatically starting gnome services or otherwise; consider doing the following:<br />
1) Kill all nm-applet processes and add nm-applet --sm-disable to the autostarted applications.<br />
2) Log out of xfce.<br />
3) Delete the XFCE session file (in ~/.cache/sessions/)<br />
4) Log into xfce and all is good.<br />
<br />
==Fluxbox and Other WM's==<br />
You will need the hicolor theme to be able to run nm-applet:<br />
<br />
# pacman -S gnome-network-manager hicolor-icon-theme<br />
<br />
After configuring your system for use with the network manager, to autostart the network manager applet, go to<br />
settings --> Autostarted Applications then add, "nm-applet --sm-disable", This should start up the network manager applet<br />
on startup, the "--sm-disable" option is used to prevent multiple instances of the nm-applet, you should only need it if multiple instances are running when you startup.<br />
<br />
=Configuration=<br />
If you want to use NetworkManager on an interface you will have to '''disable''' it in /etc/rc.conf. You can do this by placing a '!' in front of the interface of your choice, for example:<br />
INTERFACES=(lo !eth0 !ath0)<br />
<br />
NetworkManager parses your /etc/rc.conf to see if you want to have a static or dynamic IP on your interfaces.<br />
<br />
So just put your preferred config into it.<br />
<br />
example for static IP:<br />
eth0="eth0 172.19.3.18 netmask 255.255.255.0 broadcast 172.19.3.255"<br />
<br />
example for dynamic IP:<br />
eth0="dhcp"<br />
<br />
You must also "disable" the default ''network'' daemon, and add the ''dhcdbd'' and ''networkmanager'' daemons '''in this order''':<br />
<br />
DAEMONS=( ... !network '''dhcdbd networkmanager''' ... )<br />
<br />
'''''Note:''' If you happen to specify the ''fam'' daemon in your array, it ''must'' appear ''after'' networkmanager. The same also applies to ''portmap'' if specified.''<br />
<br />
Finally, add yourself to the network group as shown below (replacing USERNAME with the appropriate username):<br />
# gpasswd -a USERNAME network<br />
<br />
==Automatically unlock keyring in GNOME after login==<br />
<br />
This will prevent nm-applet from asking for your keyring password. Note that this will only work when logging in via GDM.<br />
<br />
In '''/etc/pam.d/gdm''', add these lines at the end of the 'auth', 'session' blocks: <br />
auth optional pam_gnome_keyring.so<br />
<br />
session optional pam_gnome_keyring.so auto_start<br />
<br />
In '''/etc/pam.d/passwd''', add this line to the 'password' block:<br />
<br />
password optional pam_gnome_keyring.so<br />
<br />
Next time you log in, you should get asked if you want the password to be unlocked automatically on login.<br />
<br />
See http://live.gnome.org/GnomeKeyring/Pam for reference.<br />
<br />
<br />
= Additional Resources =<br />
*[[Wireless Setup]] -- The wireless setup wiki<br />
*[http://www.gnome.org/projects/NetworkManager/ NetworkManager] - The official website for NetworkManager</div>Stanto