https://wiki.archlinux.org/api.php?action=feedcontributions&user=RedShift&feedformat=atomArchWiki - User contributions [en]2024-03-28T10:53:57ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54943Initscripts/Writing rc.d scripts2008-12-05T11:30:24Z<p>RedShift: </p>
<hr />
<div>==Naming scheme==<br />
The name of the rc.d script should follow the name of the executable, not the name of the package. It must reflect what it's going to do.<br />
<br />
==Requirements==<br />
* If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
* The rc.d script must have at least three methods, being start, stop and restart.<br />
<br />
==Example==<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54942Initscripts/Writing rc.d scripts2008-12-05T11:29:40Z<p>RedShift: /* Requirements */</p>
<hr />
<div>==Naming scheme==<br />
The name of the rc.d script should follow the name of the executable, not the name of the package. It must reflect what it's going to do.<br />
<br />
==Requirements==<br />
[*] If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
[*] The rc.d script must have at least three methods, being start, stop and restart.<br />
<br />
==Example==<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54941Initscripts/Writing rc.d scripts2008-12-05T11:27:43Z<p>RedShift: /* Naming scheme */</p>
<hr />
<div>==Naming scheme==<br />
The name of the rc.d script should follow the name of the executable, not the name of the package. It must reflect what it's going to do.<br />
<br />
==Requirements==<br />
If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
==Example==<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54934Initscripts/Writing rc.d scripts2008-12-05T11:00:44Z<p>RedShift: </p>
<hr />
<div>==Naming scheme==<br />
<br />
<br />
==Requirements==<br />
If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
==Example==<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54933Initscripts/Writing rc.d scripts2008-12-05T11:00:00Z<p>RedShift: </p>
<hr />
<div>{Naming scheme}<br />
<br />
<br />
{Requirements}<br />
If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
{Example}<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54931Initscripts/Writing rc.d scripts2008-12-05T10:59:27Z<p>RedShift: </p>
<hr />
<div>If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54930Initscripts/Writing rc.d scripts2008-12-05T10:59:04Z<p>RedShift: </p>
<hr />
<div>If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54929Initscripts/Writing rc.d scripts2008-12-05T10:58:38Z<p>RedShift: </p>
<hr />
<div>If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=Initscripts/Writing_rc.d_scripts&diff=54928Initscripts/Writing rc.d scripts2008-12-05T10:58:20Z<p>RedShift: New page: If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d. A proper example for tftpd: /etc/conf.d/tftpd: TFTPD_ARGS="-l -s /var/tftpboot -c" /etc/rc.d/tftpd ...</p>
<hr />
<div>If a daemon accepts arguments, the script must have its equivalent in /etc/conf.d.<br />
<br />
<br />
A proper example for tftpd:<br />
<br />
/etc/conf.d/tftpd:<br />
TFTPD_ARGS="-l -s /var/tftpboot -c"<br />
<br />
/etc/rc.d/tftpd<br />
<br />
#!/bin/bash<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
TFTPD_ARGS=<br />
[ -f /etc/conf.d/tftpd ] && . /etc/conf.d/tftpd<br />
<br />
PID=`pidof -o %PPID /usr/sbin/in.tftpd`<br />
case "$1" in<br />
start)<br />
stat_busy "Starting TFTPD"<br />
[ -z "$PID" ] && /usr/sbin/in.tftpd ${TFTPD_ARGS}<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
add_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Stopping TFTPD"<br />
[ ! -z "$PID" ] && kill $PID &> /dev/null<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon in.tftpd<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}" <br />
esac<br />
exit 0</div>RedShifthttps://wiki.archlinux.org/index.php?title=List_of_applications&diff=53823List of applications2008-11-19T00:05:05Z<p>RedShift: </p>
<hr />
<div>== Text Editors ==<br />
[[Vim]] <== you have just go to be kidding me<br /><br />
[[Emacs]] <br /><br />
<br />
== Chat Clients ==<br />
[[Weechat]] ncurses IRC client <br /><br />
[[Irssi]] ncurses IRC client <br /><br />
[[Bitlbee]] Instant Message from your IRC client <br /><br />
<br />
== Image Viewers ==<br />
[[feh]] Can be used to set wallpapers <br /></div>RedShifthttps://wiki.archlinux.org/index.php?title=HP_Compaq_nc6220&diff=52854HP Compaq nc62202008-11-07T14:27:12Z<p>RedShift: /* Wireless */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
==Introduction==<br />
My plan when I finish is to have my laptop (HP Compaq nc6220) dual booted with Windows XP Pro (work image). I repartitioned my hard drive with [http://gparted.sourceforge.net/livecd.php Gparted Live CD]. It only took a minute or so. I will be doing the install with the arch 0.8 beta2 base cd. There is an [http://archlinux.org/static/docs/arch-install-guide.html installation guide (0.7.2)] that may help.I will do my best to give as much detail as possible.<br />
<br />
NOTE: Per [http://h18000.www1.hp.com/products/quickspecs/12130_na/12130_na.HTML HP's website], this laptop is Novell Linux Desktop 9 certified. So getting linux on this laptop should not be too hard.<br />
<br />
===System Specifications===<br />
<br />
HP Compaq nc6220 - Intel Centrino<br />
* Intel Pentium M processor 750 (1.86-GHz, 533-MHz FSB, 2-MB L2 cache)<br />
* Mobile Intel 915GM Express Chipset<br />
* 512-MB 533-MHz DDR2 SDRAM<br />
* 60-GB 5400 rpm IDE ATA Harddrive <br />
* 14.1-inch color TFT SXGA+ (1400 x 1050 resolution and 16 M colors)<br />
* Intel Graphics Media Accelerator 900 with up to 128 MB of shared system memory<br />
* ADI AC '97 CODEC<br />
* 9.5-mm DVD/CD-RW Combo (Matshita UJDA775 IDE ATA 8x DVD/24x CDRW)<br />
* 56K Fax/Modem<br />
* NetXtreme Gigabit PCI Express Ethernet Controller (10/100/1000 NIC)<br />
* Intel PRO/Wireless 2200BG 802.11b/g WLAN<br />
* One Type I/II PC Card Slot??<br />
* One Integrated Smart Card Reader??<br />
* One Integrated Secure Digital Slot??<br />
* Dual pointing devices (both Pointstick and Touchpad)<br />
* 6-cell high capacity Lithium-Ion (52Wh)<br />
* External 65W adapter<br />
<br />
<br />
Output of lshwd<br />
<br />
00:00.0 Host bridge: Intel Corp.|Mobile Memory Controller Hub (intel-agp)<br />
00:02.0 VGA compatible controller: Intel Corp.|Mobile 915GM/GMS/910GML Express Graphics Controller (i810)<br />
00:02.1 Display controller: Intel Corp.|Mobile Graphics Controller (vesa)<br />
00:1c.0 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 0 (unknown)<br />
00:1c.1 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 1 (unknown)<br />
00:1d.0 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.1 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.2 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.7 USB Controller: Intel Corp.|I/O Controller Hub USB2 (unknown)<br />
00:1e.0 PCI bridge: Intel Corp.|82801 Hub Interface to PCI Bridge (hw_random)<br />
00:1e.2 Multimedia audio controller: Intel Corp.|82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (snd-intel8x0)<br />
00:1e.3 Modem: Intel Corp.|I/OController Hub Modem (Hsf:www.linmodems.org)<br />
00:1f.0 ISA bridge: Intel Corp.|I/O Controller Hub LPC (i810-tco)<br />
00:1f.1 IDE interface: Intel Corp.|I/O Controller Hub PATA (piix)<br />
02:04.0 Network controller: Intel Corp.|Intel(R) PRO/Wireless 2200BG (ipw2200)<br />
02:06.0 CardBus bridge: Texas Instruments|Texas Instruments PCIxx21/x515 Cardbus Controller (yenta_socket)<br />
02:06.3 Mass storage controller: Texas Instruments|Texas Instruments PCIxx21 Integrated FlashMedia Controller (unknown)<br />
02:06.4 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) C (unknown)<br />
02:06.5 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Smart Card Controller (unknown)<br />
10:00.0 Ethernet controller: Broadcom Corp.|NetXtreme BCM5751M Gigabit Ethernet PCI Express (tg3)<br />
004:001 USB Hub: Virtual|Hub (unknown)<br />
003:001 USB Hub: Virtual|Hub (unknown)<br />
002:001 USB Hub: Virtual|Hub (unknown)<br />
001:001 USB Hub: Virtual|Hub (unknown)<br />
<br />
<br />
===What works/What doesn't===<br />
Pretty much everything works on this laptop except the SD-card reader. I am still working on it. The screen needs a little tweaking to get the full resolution and works great. Also I have not tried the modem (no POTS line) or tried to suspend the laptop yet.<br />
<br />
==Installation==<br />
Boot from the CD and do the base installation from the CD. My partitions are setup as follows:<br />
<br />
HDA1 20gb Win XP<br />
HDA5 32mb /boot<br />
HDA6 1gb swap (needed for hibernate mode...I think)<br />
HDA7 39gb /<br />
<br />
With Windows XP as an option, the grub boot loader should look something like this:<br />
<br />
# Windows XP<br />
title Microsoft Windows XP Professional<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26-fallback.img<br />
<br />
==Post Installation==<br />
First, create your user account:<br />
#useradd -m <user><br />
Add yourself to some needed group:<br />
#gpasswd -a <user> audio; gpasswd -a <user> optical; gpasswd -a <user> storage; gpasswd -a <user> users<br />
Next is to upgrade:<br />
#pacman -Syu<br />
<br />
==Xorg==<br />
<br />
===Video Driver===<br />
The NC6220 has an onboard Intel 9xx series VGA, supported by the xf86-video-intel driver.<br />
<br />
====Mouse====<br />
There is a synaptic touchpad on this laptop. If you follow this [http://wiki.archlinux.org/index.php/Touchpad_Synaptics howto], you should have no problems getting this to work. It works great for me.<br />
Note: Make sure you update the modules in /etc/rc.conf.<br />
====Compiz Fusion====<br />
This laptop supports Compiz Fusion. So I followed the [http://wiki.archlinux.org/index.php/Compiz_fusion wiki], and it worked great.<br />
<br />
===Fix Resolution===<br />
xf86-video-i810 used to required 915resolution to get a correct resolution. This isn't needed anymore by the superseeding xf86-video-intel driver.<br />
<br />
Section "ServerLayout"<br />
Identifier "Xorg Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Touchpad" "SendCoreEvents"<br />
Option "AIGLX" "true"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail" "true" <br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc:unscaled"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/PEX"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/Type1"<br />
FontPath "/usr/share/fonts/ttf/western"<br />
FontPath "/usr/share/fonts/ttf/decoratives"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/truetype/openoffice"<br />
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"<br />
FontPath "/usr/share/fonts/latex-ttf-fonts"<br />
FontPath "/usr/share/fonts/defoma/CID"<br />
FontPath "/usr/share/fonts/defoma/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "ddc" # ddc probing of monitor<br />
Load "dbe"<br />
Load "dri"<br />
Load "extmod"<br />
Load "glx"<br />
Load "bitmap" # bitmap-fonts<br />
Load "type1"<br />
Load "freetype"<br />
Load "record"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "keyboard"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" ""<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "USB Mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "SendCoreEvents" "true"<br />
Option "Protocol" "IMPS/2"<br />
Option "ZAxisMapping" "4 5"<br />
Option "Buttons" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.12"<br />
Option "AccelFactor" "0.0010"<br />
Option "SHMConfig" "true"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "DPMS" "true"<br />
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors<br />
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.<br />
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz<br />
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "i810"<br />
VendorName "Intel Corp."<br />
BoardName "Unknown Board"<br />
Option "XAANoOffscreenPixmaps" "true"<br />
Option "DRI" "true"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultColorDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1400x1050"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
<br />
==Audio==<br />
Now for the sound. It works out of the box, but alsa needs to be installed for saving sound setting and all the other good stuff alsa does. Thankfully there is a [http://wiki.archlinux.org/index.php/ALSA howto here].<br />
<br />
== Network ==<br />
=== Wired ===<br />
The wired connection worked out of the box. The Neworkmanager, that we will setup in the next section, will manage this as well as the wireless.<br />
<br />
=== Wireless ===<br />
To enable the blue wireless LED, add the following to /etc/modprobe.conf:<br />
<br />
options ipw2200 led=1<br />
==== Troubles with wireless ====<br />
It appears the NC6220 can come with a "restricted" ethernet controller. If for some reason you can't get the wireless working, try unplugging the ethernet adaptor. Symptoms are: sending commands to the wireless fails (for example: ipw2200: Failed to send POWER_MODE: Command timed out), the kernel complains about the "Radio Frequency Kill Switch is On".<br />
<br />
=== Modem ===<br />
Have not tried.<br />
<br />
== ACPI ==<br />
When I login to gnome, I keep getting a acpi did not load error. I installed:<br />
pacman -Sy acpid gnome-power-manager<br />
And I added the daemons in the /etc/rc.conf file<br />
DAEMONS=(... acpid)<br />
And rebooted. Now I have the battery monitor to the gnome panel and life is good.<br />
<br />
== Card Readers ==<br />
=== PCMCIA ===<br />
As far as I've understood from other reports, the pcmcia card works as expected. I don't have one at this time, so I can't confirm it.<br />
=== Compact Flash ===<br />
The same goes for the Compact Flash. It's supposed to work as it uses the same interfaces as the PCMCIA does, but I can't confirm anything since I don't have a CF-card.<br />
=== Secure Digital ===<br />
The SD-card reader on the other hand is a pain! It uses proprietary drivers from ricoh under windows and there are no drivers under linux. I would really want this working but I think the only chance would be to reverse engineer the reader and I guess not enough coders have this device. Subsequently, there are no drivers now and there won't be in the foreseeable future...<br />
<br />
==Other Tweaks==<br />
===kernel26beyond===<br />
I use the beyond kernel because I am looking to get [http://wiki.archlinux.org/index.php/Suspend_to_Disk suspend] working. There is a list of different kernel patches/patchsets [http://wiki.archlinux.org/index.php/Kernel_Patches_and_Patchsets here].<br />
Now, lets install the beyond kernel:<br />
# pacman -Sy kernel26beyond<br />
Now add the following to the boot loader. For me, it is grub:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond-fallback.img<br />
<br />
===Sudo===<br />
I like to use sudo to manage my system. So as root, I do a:<br />
# pacman -Sy sudo<br />
Then I do a give myself rights:<br />
# visudo -f /etc/sudoers<br />
Add myself under root.<br />
===DISABLE IPV6===<br />
I disabled the IPV6 module because I do not need it. Here is the [http://wiki.archlinux.org/index.php/IPv6_-_Disabling_the_Module howto] to get this.<br />
===SSHfs===<br />
To connect to other shares and doing updates I use SSHfs. Here is a [http://wiki.archlinux.org/index.php/Sshfs howto] for that.<br />
===Packages===<br />
affinity<br />
firefox<br />
thunderbird<br />
flashplugin<br />
flashplayer-standalone<br />
jre # Java<br />
mplayer<br />
vlc<br />
Glipper<br />
tomboy<br />
gaim<br />
ms-fonts<br />
ntp<br />
tracker<br />
affinity<br />
f-spot<br />
<br />
===Files Edited===<br />
<br />
rc.local<br />
rc.conf<br />
pacman.conf<br />
modprobe.conf<br />
inittab<br />
xorg.conf<br />
sudoers<br />
<br />
= External Links =<br />
<br />
* This report is listed at the [http://tuxmobil.org/fujitsu.html TuxMobil: Linux Laptop and Notebook Installation Guides Survey: Fujitsu-Siemens - FSC].</div>RedShifthttps://wiki.archlinux.org/index.php?title=HP_Compaq_nc6220&diff=52853HP Compaq nc62202008-11-07T14:26:17Z<p>RedShift: /* Wireless */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
==Introduction==<br />
My plan when I finish is to have my laptop (HP Compaq nc6220) dual booted with Windows XP Pro (work image). I repartitioned my hard drive with [http://gparted.sourceforge.net/livecd.php Gparted Live CD]. It only took a minute or so. I will be doing the install with the arch 0.8 beta2 base cd. There is an [http://archlinux.org/static/docs/arch-install-guide.html installation guide (0.7.2)] that may help.I will do my best to give as much detail as possible.<br />
<br />
NOTE: Per [http://h18000.www1.hp.com/products/quickspecs/12130_na/12130_na.HTML HP's website], this laptop is Novell Linux Desktop 9 certified. So getting linux on this laptop should not be too hard.<br />
<br />
===System Specifications===<br />
<br />
HP Compaq nc6220 - Intel Centrino<br />
* Intel Pentium M processor 750 (1.86-GHz, 533-MHz FSB, 2-MB L2 cache)<br />
* Mobile Intel 915GM Express Chipset<br />
* 512-MB 533-MHz DDR2 SDRAM<br />
* 60-GB 5400 rpm IDE ATA Harddrive <br />
* 14.1-inch color TFT SXGA+ (1400 x 1050 resolution and 16 M colors)<br />
* Intel Graphics Media Accelerator 900 with up to 128 MB of shared system memory<br />
* ADI AC '97 CODEC<br />
* 9.5-mm DVD/CD-RW Combo (Matshita UJDA775 IDE ATA 8x DVD/24x CDRW)<br />
* 56K Fax/Modem<br />
* NetXtreme Gigabit PCI Express Ethernet Controller (10/100/1000 NIC)<br />
* Intel PRO/Wireless 2200BG 802.11b/g WLAN<br />
* One Type I/II PC Card Slot??<br />
* One Integrated Smart Card Reader??<br />
* One Integrated Secure Digital Slot??<br />
* Dual pointing devices (both Pointstick and Touchpad)<br />
* 6-cell high capacity Lithium-Ion (52Wh)<br />
* External 65W adapter<br />
<br />
<br />
Output of lshwd<br />
<br />
00:00.0 Host bridge: Intel Corp.|Mobile Memory Controller Hub (intel-agp)<br />
00:02.0 VGA compatible controller: Intel Corp.|Mobile 915GM/GMS/910GML Express Graphics Controller (i810)<br />
00:02.1 Display controller: Intel Corp.|Mobile Graphics Controller (vesa)<br />
00:1c.0 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 0 (unknown)<br />
00:1c.1 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 1 (unknown)<br />
00:1d.0 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.1 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.2 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.7 USB Controller: Intel Corp.|I/O Controller Hub USB2 (unknown)<br />
00:1e.0 PCI bridge: Intel Corp.|82801 Hub Interface to PCI Bridge (hw_random)<br />
00:1e.2 Multimedia audio controller: Intel Corp.|82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (snd-intel8x0)<br />
00:1e.3 Modem: Intel Corp.|I/OController Hub Modem (Hsf:www.linmodems.org)<br />
00:1f.0 ISA bridge: Intel Corp.|I/O Controller Hub LPC (i810-tco)<br />
00:1f.1 IDE interface: Intel Corp.|I/O Controller Hub PATA (piix)<br />
02:04.0 Network controller: Intel Corp.|Intel(R) PRO/Wireless 2200BG (ipw2200)<br />
02:06.0 CardBus bridge: Texas Instruments|Texas Instruments PCIxx21/x515 Cardbus Controller (yenta_socket)<br />
02:06.3 Mass storage controller: Texas Instruments|Texas Instruments PCIxx21 Integrated FlashMedia Controller (unknown)<br />
02:06.4 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) C (unknown)<br />
02:06.5 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Smart Card Controller (unknown)<br />
10:00.0 Ethernet controller: Broadcom Corp.|NetXtreme BCM5751M Gigabit Ethernet PCI Express (tg3)<br />
004:001 USB Hub: Virtual|Hub (unknown)<br />
003:001 USB Hub: Virtual|Hub (unknown)<br />
002:001 USB Hub: Virtual|Hub (unknown)<br />
001:001 USB Hub: Virtual|Hub (unknown)<br />
<br />
<br />
===What works/What doesn't===<br />
Pretty much everything works on this laptop except the SD-card reader. I am still working on it. The screen needs a little tweaking to get the full resolution and works great. Also I have not tried the modem (no POTS line) or tried to suspend the laptop yet.<br />
<br />
==Installation==<br />
Boot from the CD and do the base installation from the CD. My partitions are setup as follows:<br />
<br />
HDA1 20gb Win XP<br />
HDA5 32mb /boot<br />
HDA6 1gb swap (needed for hibernate mode...I think)<br />
HDA7 39gb /<br />
<br />
With Windows XP as an option, the grub boot loader should look something like this:<br />
<br />
# Windows XP<br />
title Microsoft Windows XP Professional<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26-fallback.img<br />
<br />
==Post Installation==<br />
First, create your user account:<br />
#useradd -m <user><br />
Add yourself to some needed group:<br />
#gpasswd -a <user> audio; gpasswd -a <user> optical; gpasswd -a <user> storage; gpasswd -a <user> users<br />
Next is to upgrade:<br />
#pacman -Syu<br />
<br />
==Xorg==<br />
<br />
===Video Driver===<br />
The NC6220 has an onboard Intel 9xx series VGA, supported by the xf86-video-intel driver.<br />
<br />
====Mouse====<br />
There is a synaptic touchpad on this laptop. If you follow this [http://wiki.archlinux.org/index.php/Touchpad_Synaptics howto], you should have no problems getting this to work. It works great for me.<br />
Note: Make sure you update the modules in /etc/rc.conf.<br />
====Compiz Fusion====<br />
This laptop supports Compiz Fusion. So I followed the [http://wiki.archlinux.org/index.php/Compiz_fusion wiki], and it worked great.<br />
<br />
===Fix Resolution===<br />
xf86-video-i810 used to required 915resolution to get a correct resolution. This isn't needed anymore by the superseeding xf86-video-intel driver.<br />
<br />
Section "ServerLayout"<br />
Identifier "Xorg Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Touchpad" "SendCoreEvents"<br />
Option "AIGLX" "true"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail" "true" <br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc:unscaled"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/PEX"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/Type1"<br />
FontPath "/usr/share/fonts/ttf/western"<br />
FontPath "/usr/share/fonts/ttf/decoratives"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/truetype/openoffice"<br />
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"<br />
FontPath "/usr/share/fonts/latex-ttf-fonts"<br />
FontPath "/usr/share/fonts/defoma/CID"<br />
FontPath "/usr/share/fonts/defoma/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "ddc" # ddc probing of monitor<br />
Load "dbe"<br />
Load "dri"<br />
Load "extmod"<br />
Load "glx"<br />
Load "bitmap" # bitmap-fonts<br />
Load "type1"<br />
Load "freetype"<br />
Load "record"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "keyboard"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" ""<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "USB Mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "SendCoreEvents" "true"<br />
Option "Protocol" "IMPS/2"<br />
Option "ZAxisMapping" "4 5"<br />
Option "Buttons" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.12"<br />
Option "AccelFactor" "0.0010"<br />
Option "SHMConfig" "true"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "DPMS" "true"<br />
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors<br />
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.<br />
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz<br />
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "i810"<br />
VendorName "Intel Corp."<br />
BoardName "Unknown Board"<br />
Option "XAANoOffscreenPixmaps" "true"<br />
Option "DRI" "true"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultColorDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1400x1050"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
<br />
==Audio==<br />
Now for the sound. It works out of the box, but alsa needs to be installed for saving sound setting and all the other good stuff alsa does. Thankfully there is a [http://wiki.archlinux.org/index.php/ALSA howto here].<br />
<br />
== Network ==<br />
=== Wired ===<br />
The wired connection worked out of the box. The Neworkmanager, that we will setup in the next section, will manage this as well as the wireless.<br />
<br />
=== Wireless ===<br />
To enable the blue wireless LED, add the following to /etc/modprobe.conf:<br />
[code]<br />
options ipw2200 led=1<br />
[/code]<br />
==== Troubles with wireless ====<br />
It appears the NC6220 can come with a "restricted" ethernet controller. If for some reason you can't get the wireless working, try unplugging the ethernet adaptor. Symptoms are: sending commands to the wireless fails (for example: ipw2200: Failed to send POWER_MODE: Command timed out), the kernel complains about the "Radio Frequency Kill Switch is On".<br />
<br />
=== Modem ===<br />
Have not tried.<br />
<br />
== ACPI ==<br />
When I login to gnome, I keep getting a acpi did not load error. I installed:<br />
pacman -Sy acpid gnome-power-manager<br />
And I added the daemons in the /etc/rc.conf file<br />
DAEMONS=(... acpid)<br />
And rebooted. Now I have the battery monitor to the gnome panel and life is good.<br />
<br />
== Card Readers ==<br />
=== PCMCIA ===<br />
As far as I've understood from other reports, the pcmcia card works as expected. I don't have one at this time, so I can't confirm it.<br />
=== Compact Flash ===<br />
The same goes for the Compact Flash. It's supposed to work as it uses the same interfaces as the PCMCIA does, but I can't confirm anything since I don't have a CF-card.<br />
=== Secure Digital ===<br />
The SD-card reader on the other hand is a pain! It uses proprietary drivers from ricoh under windows and there are no drivers under linux. I would really want this working but I think the only chance would be to reverse engineer the reader and I guess not enough coders have this device. Subsequently, there are no drivers now and there won't be in the foreseeable future...<br />
<br />
==Other Tweaks==<br />
===kernel26beyond===<br />
I use the beyond kernel because I am looking to get [http://wiki.archlinux.org/index.php/Suspend_to_Disk suspend] working. There is a list of different kernel patches/patchsets [http://wiki.archlinux.org/index.php/Kernel_Patches_and_Patchsets here].<br />
Now, lets install the beyond kernel:<br />
# pacman -Sy kernel26beyond<br />
Now add the following to the boot loader. For me, it is grub:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond-fallback.img<br />
<br />
===Sudo===<br />
I like to use sudo to manage my system. So as root, I do a:<br />
# pacman -Sy sudo<br />
Then I do a give myself rights:<br />
# visudo -f /etc/sudoers<br />
Add myself under root.<br />
===DISABLE IPV6===<br />
I disabled the IPV6 module because I do not need it. Here is the [http://wiki.archlinux.org/index.php/IPv6_-_Disabling_the_Module howto] to get this.<br />
===SSHfs===<br />
To connect to other shares and doing updates I use SSHfs. Here is a [http://wiki.archlinux.org/index.php/Sshfs howto] for that.<br />
===Packages===<br />
affinity<br />
firefox<br />
thunderbird<br />
flashplugin<br />
flashplayer-standalone<br />
jre # Java<br />
mplayer<br />
vlc<br />
Glipper<br />
tomboy<br />
gaim<br />
ms-fonts<br />
ntp<br />
tracker<br />
affinity<br />
f-spot<br />
<br />
===Files Edited===<br />
<br />
rc.local<br />
rc.conf<br />
pacman.conf<br />
modprobe.conf<br />
inittab<br />
xorg.conf<br />
sudoers<br />
<br />
= External Links =<br />
<br />
* This report is listed at the [http://tuxmobil.org/fujitsu.html TuxMobil: Linux Laptop and Notebook Installation Guides Survey: Fujitsu-Siemens - FSC].</div>RedShifthttps://wiki.archlinux.org/index.php?title=HP_Compaq_nc6220&diff=52852HP Compaq nc62202008-11-07T14:24:52Z<p>RedShift: /* Fix Resolution */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
==Introduction==<br />
My plan when I finish is to have my laptop (HP Compaq nc6220) dual booted with Windows XP Pro (work image). I repartitioned my hard drive with [http://gparted.sourceforge.net/livecd.php Gparted Live CD]. It only took a minute or so. I will be doing the install with the arch 0.8 beta2 base cd. There is an [http://archlinux.org/static/docs/arch-install-guide.html installation guide (0.7.2)] that may help.I will do my best to give as much detail as possible.<br />
<br />
NOTE: Per [http://h18000.www1.hp.com/products/quickspecs/12130_na/12130_na.HTML HP's website], this laptop is Novell Linux Desktop 9 certified. So getting linux on this laptop should not be too hard.<br />
<br />
===System Specifications===<br />
<br />
HP Compaq nc6220 - Intel Centrino<br />
* Intel Pentium M processor 750 (1.86-GHz, 533-MHz FSB, 2-MB L2 cache)<br />
* Mobile Intel 915GM Express Chipset<br />
* 512-MB 533-MHz DDR2 SDRAM<br />
* 60-GB 5400 rpm IDE ATA Harddrive <br />
* 14.1-inch color TFT SXGA+ (1400 x 1050 resolution and 16 M colors)<br />
* Intel Graphics Media Accelerator 900 with up to 128 MB of shared system memory<br />
* ADI AC '97 CODEC<br />
* 9.5-mm DVD/CD-RW Combo (Matshita UJDA775 IDE ATA 8x DVD/24x CDRW)<br />
* 56K Fax/Modem<br />
* NetXtreme Gigabit PCI Express Ethernet Controller (10/100/1000 NIC)<br />
* Intel PRO/Wireless 2200BG 802.11b/g WLAN<br />
* One Type I/II PC Card Slot??<br />
* One Integrated Smart Card Reader??<br />
* One Integrated Secure Digital Slot??<br />
* Dual pointing devices (both Pointstick and Touchpad)<br />
* 6-cell high capacity Lithium-Ion (52Wh)<br />
* External 65W adapter<br />
<br />
<br />
Output of lshwd<br />
<br />
00:00.0 Host bridge: Intel Corp.|Mobile Memory Controller Hub (intel-agp)<br />
00:02.0 VGA compatible controller: Intel Corp.|Mobile 915GM/GMS/910GML Express Graphics Controller (i810)<br />
00:02.1 Display controller: Intel Corp.|Mobile Graphics Controller (vesa)<br />
00:1c.0 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 0 (unknown)<br />
00:1c.1 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 1 (unknown)<br />
00:1d.0 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.1 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.2 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.7 USB Controller: Intel Corp.|I/O Controller Hub USB2 (unknown)<br />
00:1e.0 PCI bridge: Intel Corp.|82801 Hub Interface to PCI Bridge (hw_random)<br />
00:1e.2 Multimedia audio controller: Intel Corp.|82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (snd-intel8x0)<br />
00:1e.3 Modem: Intel Corp.|I/OController Hub Modem (Hsf:www.linmodems.org)<br />
00:1f.0 ISA bridge: Intel Corp.|I/O Controller Hub LPC (i810-tco)<br />
00:1f.1 IDE interface: Intel Corp.|I/O Controller Hub PATA (piix)<br />
02:04.0 Network controller: Intel Corp.|Intel(R) PRO/Wireless 2200BG (ipw2200)<br />
02:06.0 CardBus bridge: Texas Instruments|Texas Instruments PCIxx21/x515 Cardbus Controller (yenta_socket)<br />
02:06.3 Mass storage controller: Texas Instruments|Texas Instruments PCIxx21 Integrated FlashMedia Controller (unknown)<br />
02:06.4 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) C (unknown)<br />
02:06.5 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Smart Card Controller (unknown)<br />
10:00.0 Ethernet controller: Broadcom Corp.|NetXtreme BCM5751M Gigabit Ethernet PCI Express (tg3)<br />
004:001 USB Hub: Virtual|Hub (unknown)<br />
003:001 USB Hub: Virtual|Hub (unknown)<br />
002:001 USB Hub: Virtual|Hub (unknown)<br />
001:001 USB Hub: Virtual|Hub (unknown)<br />
<br />
<br />
===What works/What doesn't===<br />
Pretty much everything works on this laptop except the SD-card reader. I am still working on it. The screen needs a little tweaking to get the full resolution and works great. Also I have not tried the modem (no POTS line) or tried to suspend the laptop yet.<br />
<br />
==Installation==<br />
Boot from the CD and do the base installation from the CD. My partitions are setup as follows:<br />
<br />
HDA1 20gb Win XP<br />
HDA5 32mb /boot<br />
HDA6 1gb swap (needed for hibernate mode...I think)<br />
HDA7 39gb /<br />
<br />
With Windows XP as an option, the grub boot loader should look something like this:<br />
<br />
# Windows XP<br />
title Microsoft Windows XP Professional<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26-fallback.img<br />
<br />
==Post Installation==<br />
First, create your user account:<br />
#useradd -m <user><br />
Add yourself to some needed group:<br />
#gpasswd -a <user> audio; gpasswd -a <user> optical; gpasswd -a <user> storage; gpasswd -a <user> users<br />
Next is to upgrade:<br />
#pacman -Syu<br />
<br />
==Xorg==<br />
<br />
===Video Driver===<br />
The NC6220 has an onboard Intel 9xx series VGA, supported by the xf86-video-intel driver.<br />
<br />
====Mouse====<br />
There is a synaptic touchpad on this laptop. If you follow this [http://wiki.archlinux.org/index.php/Touchpad_Synaptics howto], you should have no problems getting this to work. It works great for me.<br />
Note: Make sure you update the modules in /etc/rc.conf.<br />
====Compiz Fusion====<br />
This laptop supports Compiz Fusion. So I followed the [http://wiki.archlinux.org/index.php/Compiz_fusion wiki], and it worked great.<br />
<br />
===Fix Resolution===<br />
xf86-video-i810 used to required 915resolution to get a correct resolution. This isn't needed anymore by the superseeding xf86-video-intel driver.<br />
<br />
Section "ServerLayout"<br />
Identifier "Xorg Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Touchpad" "SendCoreEvents"<br />
Option "AIGLX" "true"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail" "true" <br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc:unscaled"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/PEX"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/Type1"<br />
FontPath "/usr/share/fonts/ttf/western"<br />
FontPath "/usr/share/fonts/ttf/decoratives"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/truetype/openoffice"<br />
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"<br />
FontPath "/usr/share/fonts/latex-ttf-fonts"<br />
FontPath "/usr/share/fonts/defoma/CID"<br />
FontPath "/usr/share/fonts/defoma/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "ddc" # ddc probing of monitor<br />
Load "dbe"<br />
Load "dri"<br />
Load "extmod"<br />
Load "glx"<br />
Load "bitmap" # bitmap-fonts<br />
Load "type1"<br />
Load "freetype"<br />
Load "record"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "keyboard"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" ""<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "USB Mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "SendCoreEvents" "true"<br />
Option "Protocol" "IMPS/2"<br />
Option "ZAxisMapping" "4 5"<br />
Option "Buttons" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.12"<br />
Option "AccelFactor" "0.0010"<br />
Option "SHMConfig" "true"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "DPMS" "true"<br />
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors<br />
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.<br />
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz<br />
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "i810"<br />
VendorName "Intel Corp."<br />
BoardName "Unknown Board"<br />
Option "XAANoOffscreenPixmaps" "true"<br />
Option "DRI" "true"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultColorDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1400x1050"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
<br />
==Audio==<br />
Now for the sound. It works out of the box, but alsa needs to be installed for saving sound setting and all the other good stuff alsa does. Thankfully there is a [http://wiki.archlinux.org/index.php/ALSA howto here].<br />
<br />
== Network ==<br />
=== Wired ===<br />
The wired connection worked out of the box. The Neworkmanager, that we will setup in the next section, will manage this as well as the wireless.<br />
<br />
=== Wireless ===<br />
Now lets get wireless going. There is a [http://wiki.archlinux.org/index.php/Wireless_Setup wireless setup howto] and there is a [http://wiki.archlinux.org/index.php/Networkmanager Networkmanager howto]. I will go into detail about this because wireless is one of the most difficult things to get running (generally). This should be pretty easy to get going.<br />
<br />
Install wireless drivers and network tools<br />
#pacman -Sy ipw2200-fw wireless_tools gnome-network-manager<br />
Add yourself to the network group<br />
#gpasswd -a <user> network<br />
Load module<br />
#modprobe ipw2200<br />
See what device the wireless card it on:<br />
#iwconfig<br />
lo no wireless extensions.<br />
<br />
eth0 no wireless extensions.<br />
<br />
eth1 IEEE 802.11g ESSID:"" <br />
Mode:Managed Frequency:2.442 GHz Access Point: 00:90:4C:7E:00:10 <br />
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 <br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality=98/100 Signal level=-27 dBm Noise level=-92 dBm<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
While still in the /etc/rc.conf file still open, edit the network part of the file:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
eth1="dhcp"<br />
INTERFACES=(lo !eth0 !eth1)<br />
I belive this is optional. It is just to get the blue LED to light up when the wireless is enabled. I added the following to /etc/modprobe.conf:<br />
options ipw2200 led=1 hwcrypto=0<br />
With /etc/rc.conf still open, edit it to stop the network daemon from starting and have networkmanager and dhcdpd daemons start at boot:<br />
DAEMONS=(... !network ... networkmanager dhcdbd)<br />
Now reboot or stop/start the daemons:<br />
# /etc/rc.d/network stop;/etc/rc.d/networkmanager start;/etc/rc.d/dhcdbd start<br />
<br />
That should do it. Note, this is a generic way to set it up. My wireless router is broadcasting its SSID and has no encryption on it. I want to get WPA working though. That will be a task for later.<br />
==== Troubles with wireless ====<br />
It appears the NC6220 can come with a "restricted" ethernet controller. If for some reason you can't get the wireless working, try unplugging the ethernet adaptor. Symptoms are: sending commands to the wireless fails (for example: ipw2200: Failed to send POWER_MODE: Command timed out), the kernel complains about the "Radio Frequency Kill Switch is On".<br />
<br />
=== Modem ===<br />
Have not tried.<br />
<br />
== ACPI ==<br />
When I login to gnome, I keep getting a acpi did not load error. I installed:<br />
pacman -Sy acpid gnome-power-manager<br />
And I added the daemons in the /etc/rc.conf file<br />
DAEMONS=(... acpid)<br />
And rebooted. Now I have the battery monitor to the gnome panel and life is good.<br />
<br />
== Card Readers ==<br />
=== PCMCIA ===<br />
As far as I've understood from other reports, the pcmcia card works as expected. I don't have one at this time, so I can't confirm it.<br />
=== Compact Flash ===<br />
The same goes for the Compact Flash. It's supposed to work as it uses the same interfaces as the PCMCIA does, but I can't confirm anything since I don't have a CF-card.<br />
=== Secure Digital ===<br />
The SD-card reader on the other hand is a pain! It uses proprietary drivers from ricoh under windows and there are no drivers under linux. I would really want this working but I think the only chance would be to reverse engineer the reader and I guess not enough coders have this device. Subsequently, there are no drivers now and there won't be in the foreseeable future...<br />
<br />
==Other Tweaks==<br />
===kernel26beyond===<br />
I use the beyond kernel because I am looking to get [http://wiki.archlinux.org/index.php/Suspend_to_Disk suspend] working. There is a list of different kernel patches/patchsets [http://wiki.archlinux.org/index.php/Kernel_Patches_and_Patchsets here].<br />
Now, lets install the beyond kernel:<br />
# pacman -Sy kernel26beyond<br />
Now add the following to the boot loader. For me, it is grub:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond-fallback.img<br />
<br />
===Sudo===<br />
I like to use sudo to manage my system. So as root, I do a:<br />
# pacman -Sy sudo<br />
Then I do a give myself rights:<br />
# visudo -f /etc/sudoers<br />
Add myself under root.<br />
===DISABLE IPV6===<br />
I disabled the IPV6 module because I do not need it. Here is the [http://wiki.archlinux.org/index.php/IPv6_-_Disabling_the_Module howto] to get this.<br />
===SSHfs===<br />
To connect to other shares and doing updates I use SSHfs. Here is a [http://wiki.archlinux.org/index.php/Sshfs howto] for that.<br />
===Packages===<br />
affinity<br />
firefox<br />
thunderbird<br />
flashplugin<br />
flashplayer-standalone<br />
jre # Java<br />
mplayer<br />
vlc<br />
Glipper<br />
tomboy<br />
gaim<br />
ms-fonts<br />
ntp<br />
tracker<br />
affinity<br />
f-spot<br />
<br />
===Files Edited===<br />
<br />
rc.local<br />
rc.conf<br />
pacman.conf<br />
modprobe.conf<br />
inittab<br />
xorg.conf<br />
sudoers<br />
<br />
= External Links =<br />
<br />
* This report is listed at the [http://tuxmobil.org/fujitsu.html TuxMobil: Linux Laptop and Notebook Installation Guides Survey: Fujitsu-Siemens - FSC].</div>RedShifthttps://wiki.archlinux.org/index.php?title=HP_Compaq_nc6220&diff=52851HP Compaq nc62202008-11-07T14:23:51Z<p>RedShift: /* Install GUI */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
==Introduction==<br />
My plan when I finish is to have my laptop (HP Compaq nc6220) dual booted with Windows XP Pro (work image). I repartitioned my hard drive with [http://gparted.sourceforge.net/livecd.php Gparted Live CD]. It only took a minute or so. I will be doing the install with the arch 0.8 beta2 base cd. There is an [http://archlinux.org/static/docs/arch-install-guide.html installation guide (0.7.2)] that may help.I will do my best to give as much detail as possible.<br />
<br />
NOTE: Per [http://h18000.www1.hp.com/products/quickspecs/12130_na/12130_na.HTML HP's website], this laptop is Novell Linux Desktop 9 certified. So getting linux on this laptop should not be too hard.<br />
<br />
===System Specifications===<br />
<br />
HP Compaq nc6220 - Intel Centrino<br />
* Intel Pentium M processor 750 (1.86-GHz, 533-MHz FSB, 2-MB L2 cache)<br />
* Mobile Intel 915GM Express Chipset<br />
* 512-MB 533-MHz DDR2 SDRAM<br />
* 60-GB 5400 rpm IDE ATA Harddrive <br />
* 14.1-inch color TFT SXGA+ (1400 x 1050 resolution and 16 M colors)<br />
* Intel Graphics Media Accelerator 900 with up to 128 MB of shared system memory<br />
* ADI AC '97 CODEC<br />
* 9.5-mm DVD/CD-RW Combo (Matshita UJDA775 IDE ATA 8x DVD/24x CDRW)<br />
* 56K Fax/Modem<br />
* NetXtreme Gigabit PCI Express Ethernet Controller (10/100/1000 NIC)<br />
* Intel PRO/Wireless 2200BG 802.11b/g WLAN<br />
* One Type I/II PC Card Slot??<br />
* One Integrated Smart Card Reader??<br />
* One Integrated Secure Digital Slot??<br />
* Dual pointing devices (both Pointstick and Touchpad)<br />
* 6-cell high capacity Lithium-Ion (52Wh)<br />
* External 65W adapter<br />
<br />
<br />
Output of lshwd<br />
<br />
00:00.0 Host bridge: Intel Corp.|Mobile Memory Controller Hub (intel-agp)<br />
00:02.0 VGA compatible controller: Intel Corp.|Mobile 915GM/GMS/910GML Express Graphics Controller (i810)<br />
00:02.1 Display controller: Intel Corp.|Mobile Graphics Controller (vesa)<br />
00:1c.0 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 0 (unknown)<br />
00:1c.1 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 1 (unknown)<br />
00:1d.0 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.1 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.2 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.7 USB Controller: Intel Corp.|I/O Controller Hub USB2 (unknown)<br />
00:1e.0 PCI bridge: Intel Corp.|82801 Hub Interface to PCI Bridge (hw_random)<br />
00:1e.2 Multimedia audio controller: Intel Corp.|82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (snd-intel8x0)<br />
00:1e.3 Modem: Intel Corp.|I/OController Hub Modem (Hsf:www.linmodems.org)<br />
00:1f.0 ISA bridge: Intel Corp.|I/O Controller Hub LPC (i810-tco)<br />
00:1f.1 IDE interface: Intel Corp.|I/O Controller Hub PATA (piix)<br />
02:04.0 Network controller: Intel Corp.|Intel(R) PRO/Wireless 2200BG (ipw2200)<br />
02:06.0 CardBus bridge: Texas Instruments|Texas Instruments PCIxx21/x515 Cardbus Controller (yenta_socket)<br />
02:06.3 Mass storage controller: Texas Instruments|Texas Instruments PCIxx21 Integrated FlashMedia Controller (unknown)<br />
02:06.4 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) C (unknown)<br />
02:06.5 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Smart Card Controller (unknown)<br />
10:00.0 Ethernet controller: Broadcom Corp.|NetXtreme BCM5751M Gigabit Ethernet PCI Express (tg3)<br />
004:001 USB Hub: Virtual|Hub (unknown)<br />
003:001 USB Hub: Virtual|Hub (unknown)<br />
002:001 USB Hub: Virtual|Hub (unknown)<br />
001:001 USB Hub: Virtual|Hub (unknown)<br />
<br />
<br />
===What works/What doesn't===<br />
Pretty much everything works on this laptop except the SD-card reader. I am still working on it. The screen needs a little tweaking to get the full resolution and works great. Also I have not tried the modem (no POTS line) or tried to suspend the laptop yet.<br />
<br />
==Installation==<br />
Boot from the CD and do the base installation from the CD. My partitions are setup as follows:<br />
<br />
HDA1 20gb Win XP<br />
HDA5 32mb /boot<br />
HDA6 1gb swap (needed for hibernate mode...I think)<br />
HDA7 39gb /<br />
<br />
With Windows XP as an option, the grub boot loader should look something like this:<br />
<br />
# Windows XP<br />
title Microsoft Windows XP Professional<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26-fallback.img<br />
<br />
==Post Installation==<br />
First, create your user account:<br />
#useradd -m <user><br />
Add yourself to some needed group:<br />
#gpasswd -a <user> audio; gpasswd -a <user> optical; gpasswd -a <user> storage; gpasswd -a <user> users<br />
Next is to upgrade:<br />
#pacman -Syu<br />
<br />
==Xorg==<br />
<br />
===Video Driver===<br />
The NC6220 has an onboard Intel 9xx series VGA, supported by the xf86-video-intel driver.<br />
<br />
====Mouse====<br />
There is a synaptic touchpad on this laptop. If you follow this [http://wiki.archlinux.org/index.php/Touchpad_Synaptics howto], you should have no problems getting this to work. It works great for me.<br />
Note: Make sure you update the modules in /etc/rc.conf.<br />
====Compiz Fusion====<br />
This laptop supports Compiz Fusion. So I followed the [http://wiki.archlinux.org/index.php/Compiz_fusion wiki], and it worked great.<br />
<br />
===Fix Resolution===<br />
xf86-video-i810 used to required 915resolution to get a correct resolution. This isn't needed anymore by the superseeding xf86-video-driver.<br />
<br />
Section "ServerLayout"<br />
Identifier "Xorg Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Touchpad" "SendCoreEvents"<br />
Option "AIGLX" "true"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail" "true" <br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc:unscaled"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/PEX"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/Type1"<br />
FontPath "/usr/share/fonts/ttf/western"<br />
FontPath "/usr/share/fonts/ttf/decoratives"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/truetype/openoffice"<br />
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"<br />
FontPath "/usr/share/fonts/latex-ttf-fonts"<br />
FontPath "/usr/share/fonts/defoma/CID"<br />
FontPath "/usr/share/fonts/defoma/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "ddc" # ddc probing of monitor<br />
Load "dbe"<br />
Load "dri"<br />
Load "extmod"<br />
Load "glx"<br />
Load "bitmap" # bitmap-fonts<br />
Load "type1"<br />
Load "freetype"<br />
Load "record"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "keyboard"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" ""<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "USB Mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "SendCoreEvents" "true"<br />
Option "Protocol" "IMPS/2"<br />
Option "ZAxisMapping" "4 5"<br />
Option "Buttons" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.12"<br />
Option "AccelFactor" "0.0010"<br />
Option "SHMConfig" "true"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "DPMS" "true"<br />
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors<br />
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.<br />
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz<br />
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "i810"<br />
VendorName "Intel Corp."<br />
BoardName "Unknown Board"<br />
Option "XAANoOffscreenPixmaps" "true"<br />
Option "DRI" "true"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultColorDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1400x1050"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
<br />
==Audio==<br />
Now for the sound. It works out of the box, but alsa needs to be installed for saving sound setting and all the other good stuff alsa does. Thankfully there is a [http://wiki.archlinux.org/index.php/ALSA howto here].<br />
<br />
== Network ==<br />
=== Wired ===<br />
The wired connection worked out of the box. The Neworkmanager, that we will setup in the next section, will manage this as well as the wireless.<br />
<br />
=== Wireless ===<br />
Now lets get wireless going. There is a [http://wiki.archlinux.org/index.php/Wireless_Setup wireless setup howto] and there is a [http://wiki.archlinux.org/index.php/Networkmanager Networkmanager howto]. I will go into detail about this because wireless is one of the most difficult things to get running (generally). This should be pretty easy to get going.<br />
<br />
Install wireless drivers and network tools<br />
#pacman -Sy ipw2200-fw wireless_tools gnome-network-manager<br />
Add yourself to the network group<br />
#gpasswd -a <user> network<br />
Load module<br />
#modprobe ipw2200<br />
See what device the wireless card it on:<br />
#iwconfig<br />
lo no wireless extensions.<br />
<br />
eth0 no wireless extensions.<br />
<br />
eth1 IEEE 802.11g ESSID:"" <br />
Mode:Managed Frequency:2.442 GHz Access Point: 00:90:4C:7E:00:10 <br />
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 <br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality=98/100 Signal level=-27 dBm Noise level=-92 dBm<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
While still in the /etc/rc.conf file still open, edit the network part of the file:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
eth1="dhcp"<br />
INTERFACES=(lo !eth0 !eth1)<br />
I belive this is optional. It is just to get the blue LED to light up when the wireless is enabled. I added the following to /etc/modprobe.conf:<br />
options ipw2200 led=1 hwcrypto=0<br />
With /etc/rc.conf still open, edit it to stop the network daemon from starting and have networkmanager and dhcdpd daemons start at boot:<br />
DAEMONS=(... !network ... networkmanager dhcdbd)<br />
Now reboot or stop/start the daemons:<br />
# /etc/rc.d/network stop;/etc/rc.d/networkmanager start;/etc/rc.d/dhcdbd start<br />
<br />
That should do it. Note, this is a generic way to set it up. My wireless router is broadcasting its SSID and has no encryption on it. I want to get WPA working though. That will be a task for later.<br />
==== Troubles with wireless ====<br />
It appears the NC6220 can come with a "restricted" ethernet controller. If for some reason you can't get the wireless working, try unplugging the ethernet adaptor. Symptoms are: sending commands to the wireless fails (for example: ipw2200: Failed to send POWER_MODE: Command timed out), the kernel complains about the "Radio Frequency Kill Switch is On".<br />
<br />
=== Modem ===<br />
Have not tried.<br />
<br />
== ACPI ==<br />
When I login to gnome, I keep getting a acpi did not load error. I installed:<br />
pacman -Sy acpid gnome-power-manager<br />
And I added the daemons in the /etc/rc.conf file<br />
DAEMONS=(... acpid)<br />
And rebooted. Now I have the battery monitor to the gnome panel and life is good.<br />
<br />
== Card Readers ==<br />
=== PCMCIA ===<br />
As far as I've understood from other reports, the pcmcia card works as expected. I don't have one at this time, so I can't confirm it.<br />
=== Compact Flash ===<br />
The same goes for the Compact Flash. It's supposed to work as it uses the same interfaces as the PCMCIA does, but I can't confirm anything since I don't have a CF-card.<br />
=== Secure Digital ===<br />
The SD-card reader on the other hand is a pain! It uses proprietary drivers from ricoh under windows and there are no drivers under linux. I would really want this working but I think the only chance would be to reverse engineer the reader and I guess not enough coders have this device. Subsequently, there are no drivers now and there won't be in the foreseeable future...<br />
<br />
==Other Tweaks==<br />
===kernel26beyond===<br />
I use the beyond kernel because I am looking to get [http://wiki.archlinux.org/index.php/Suspend_to_Disk suspend] working. There is a list of different kernel patches/patchsets [http://wiki.archlinux.org/index.php/Kernel_Patches_and_Patchsets here].<br />
Now, lets install the beyond kernel:<br />
# pacman -Sy kernel26beyond<br />
Now add the following to the boot loader. For me, it is grub:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond-fallback.img<br />
<br />
===Sudo===<br />
I like to use sudo to manage my system. So as root, I do a:<br />
# pacman -Sy sudo<br />
Then I do a give myself rights:<br />
# visudo -f /etc/sudoers<br />
Add myself under root.<br />
===DISABLE IPV6===<br />
I disabled the IPV6 module because I do not need it. Here is the [http://wiki.archlinux.org/index.php/IPv6_-_Disabling_the_Module howto] to get this.<br />
===SSHfs===<br />
To connect to other shares and doing updates I use SSHfs. Here is a [http://wiki.archlinux.org/index.php/Sshfs howto] for that.<br />
===Packages===<br />
affinity<br />
firefox<br />
thunderbird<br />
flashplugin<br />
flashplayer-standalone<br />
jre # Java<br />
mplayer<br />
vlc<br />
Glipper<br />
tomboy<br />
gaim<br />
ms-fonts<br />
ntp<br />
tracker<br />
affinity<br />
f-spot<br />
<br />
===Files Edited===<br />
<br />
rc.local<br />
rc.conf<br />
pacman.conf<br />
modprobe.conf<br />
inittab<br />
xorg.conf<br />
sudoers<br />
<br />
= External Links =<br />
<br />
* This report is listed at the [http://tuxmobil.org/fujitsu.html TuxMobil: Linux Laptop and Notebook Installation Guides Survey: Fujitsu-Siemens - FSC].</div>RedShifthttps://wiki.archlinux.org/index.php?title=HP_Compaq_nc6220&diff=52708HP Compaq nc62202008-11-05T21:21:45Z<p>RedShift: /* Wireless */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
==Introduction==<br />
My plan when I finish is to have my laptop (HP Compaq nc6220) dual booted with Windows XP Pro (work image). I repartitioned my hard drive with [http://gparted.sourceforge.net/livecd.php Gparted Live CD]. It only took a minute or so. I will be doing the install with the arch 0.8 beta2 base cd. There is an [http://archlinux.org/static/docs/arch-install-guide.html installation guide (0.7.2)] that may help.I will do my best to give as much detail as possible.<br />
<br />
NOTE: Per [http://h18000.www1.hp.com/products/quickspecs/12130_na/12130_na.HTML HP's website], this laptop is Novell Linux Desktop 9 certified. So getting linux on this laptop should not be too hard.<br />
<br />
===System Specifications===<br />
<br />
HP Compaq nc6220 - Intel Centrino<br />
* Intel Pentium M processor 750 (1.86-GHz, 533-MHz FSB, 2-MB L2 cache)<br />
* Mobile Intel 915GM Express Chipset<br />
* 512-MB 533-MHz DDR2 SDRAM<br />
* 60-GB 5400 rpm IDE ATA Harddrive <br />
* 14.1-inch color TFT SXGA+ (1400 x 1050 resolution and 16 M colors)<br />
* Intel Graphics Media Accelerator 900 with up to 128 MB of shared system memory<br />
* ADI AC '97 CODEC<br />
* 9.5-mm DVD/CD-RW Combo (Matshita UJDA775 IDE ATA 8x DVD/24x CDRW)<br />
* 56K Fax/Modem<br />
* NetXtreme Gigabit PCI Express Ethernet Controller (10/100/1000 NIC)<br />
* Intel PRO/Wireless 2200BG 802.11b/g WLAN<br />
* One Type I/II PC Card Slot??<br />
* One Integrated Smart Card Reader??<br />
* One Integrated Secure Digital Slot??<br />
* Dual pointing devices (both Pointstick and Touchpad)<br />
* 6-cell high capacity Lithium-Ion (52Wh)<br />
* External 65W adapter<br />
<br />
<br />
Output of lshwd<br />
<br />
00:00.0 Host bridge: Intel Corp.|Mobile Memory Controller Hub (intel-agp)<br />
00:02.0 VGA compatible controller: Intel Corp.|Mobile 915GM/GMS/910GML Express Graphics Controller (i810)<br />
00:02.1 Display controller: Intel Corp.|Mobile Graphics Controller (vesa)<br />
00:1c.0 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 0 (unknown)<br />
00:1c.1 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 1 (unknown)<br />
00:1d.0 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.1 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.2 USB Controller: Intel Corp.|I/O Controller Hub USB (unknown)<br />
00:1d.7 USB Controller: Intel Corp.|I/O Controller Hub USB2 (unknown)<br />
00:1e.0 PCI bridge: Intel Corp.|82801 Hub Interface to PCI Bridge (hw_random)<br />
00:1e.2 Multimedia audio controller: Intel Corp.|82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (snd-intel8x0)<br />
00:1e.3 Modem: Intel Corp.|I/OController Hub Modem (Hsf:www.linmodems.org)<br />
00:1f.0 ISA bridge: Intel Corp.|I/O Controller Hub LPC (i810-tco)<br />
00:1f.1 IDE interface: Intel Corp.|I/O Controller Hub PATA (piix)<br />
02:04.0 Network controller: Intel Corp.|Intel(R) PRO/Wireless 2200BG (ipw2200)<br />
02:06.0 CardBus bridge: Texas Instruments|Texas Instruments PCIxx21/x515 Cardbus Controller (yenta_socket)<br />
02:06.3 Mass storage controller: Texas Instruments|Texas Instruments PCIxx21 Integrated FlashMedia Controller (unknown)<br />
02:06.4 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) C (unknown)<br />
02:06.5 : Texas Instruments|Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Smart Card Controller (unknown)<br />
10:00.0 Ethernet controller: Broadcom Corp.|NetXtreme BCM5751M Gigabit Ethernet PCI Express (tg3)<br />
004:001 USB Hub: Virtual|Hub (unknown)<br />
003:001 USB Hub: Virtual|Hub (unknown)<br />
002:001 USB Hub: Virtual|Hub (unknown)<br />
001:001 USB Hub: Virtual|Hub (unknown)<br />
<br />
<br />
===What works/What doesn't===<br />
Pretty much everything works on this laptop except the SD-card reader. I am still working on it. The screen needs a little tweaking to get the full resolution and works great. Also I have not tried the modem (no POTS line) or tried to suspend the laptop yet.<br />
<br />
==Installation==<br />
Boot from the CD and do the base installation from the CD. My partitions are setup as follows:<br />
<br />
HDA1 20gb Win XP<br />
HDA5 32mb /boot<br />
HDA6 1gb swap (needed for hibernate mode...I think)<br />
HDA7 39gb /<br />
<br />
With Windows XP as an option, the grub boot loader should look something like this:<br />
<br />
# Windows XP<br />
title Microsoft Windows XP Professional<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26 root=/dev/sda7 ro<br />
initrd /kernel26-fallback.img<br />
<br />
==Post Installation==<br />
First, create your user account:<br />
#useradd -m <user><br />
Add yourself to some needed group:<br />
#gpasswd -a <user> audio; gpasswd -a <user> optical; gpasswd -a <user> storage; gpasswd -a <user> users<br />
Next is to upgrade:<br />
#pacman -Syu<br />
<br />
==Install GUI==<br />
Now, lets get the gui going.<br />
<br />
===Video Driver===<br />
First things first. Lets install the driver. Per the lshwd command I displayed earlier, it should be the i810 driver. Let's search for it:<br />
<br />
#pacman -Ss i810<br />
current/xf86-video-i810 1.7.4-2<br />
X.org Intel i810/i830/i915 video drivers<br />
<br />
Now let's install it:<br />
<br />
#pacman -S xf86-video-i810<br />
<br />
===Xorg/Gnome===<br />
I am a gnome person. To get it installed, I followed the [http://wiki.archlinux.org/index.php/Xorg Xorg] and [http://wiki.archlinux.org/index.php/Gnome Gnome] wikis. They provide enough information to get it setup. I will post my xorg.conf file in the next section.<br />
Note: Make sure you update the daemons in /etc/rc.conf.<br />
====Mouse====<br />
There is a synaptic touchpad on this laptop. If you follow this [http://wiki.archlinux.org/index.php/Touchpad_Synaptics howto], you should have no problems getting this to work. It works great for me.<br />
Note: Make sure you update the modules in /etc/rc.conf.<br />
====Compiz Fusion====<br />
This laptop supports Compiz Fusion. So I followed the [http://wiki.archlinux.org/index.php/Compiz_fusion wiki], and it worked great.<br />
<br />
===Fix Resolution===<br />
When I got Gnome up and running, I wanted to get the display to its native resolution to 1400x1050. I installed 915resolution. To configure it, I found a good site called [http://www.geocities.com/stomljen/ 915Resolution: Intel Video BIOS Hack]. There is also a [http://wiki.archlinux.org/index.php/Intel_945_GM_How_To_Resolution wiki howto] for it. I followed this [http://www.geocities.com/stomljen/readme.html howto], and it worked like a champ. This is what I did:<br />
<br />
#pacman -Sy 915resolution<br />
<br />
You will need to uncomment the community repo from /etc/pacman.conf. Next to list the resolutions:<br />
<br />
#915resolution -l<br />
Intel 800/900 Series VBIOS Hack : version 0.5.2<br />
<br />
Chipset: 915GM<br />
BIOS: TYPE 1<br />
Mode Table Offset: $C0000 + $269<br />
Mode Table Entries: 36<br />
<br />
Mode 30 : 640x480, 8 bits/pixel<br />
Mode 32 : 800x600, 8 bits/pixel<br />
Mode 34 : 1024x768, 8 bits/pixel<br />
Mode 38 : 1280x1024, 8 bits/pixel<br />
Mode 3a : 1600x1200, 8 bits/pixel<br />
Mode 3c : 1920x1440, 8 bits/pixel<br />
Mode 41 : 640x480, 16 bits/pixel<br />
Mode 43 : 800x600, 16 bits/pixel<br />
Mode 45 : 1024x768, 16 bits/pixel<br />
Mode 49 : 1280x1024, 16 bits/pixel<br />
Mode 4b : 1600x1200, 16 bits/pixel<br />
Mode 4d : 1920x1440, 16 bits/pixel<br />
Mode 50 : 640x480, 32 bits/pixel<br />
Mode 52 : 800x600, 32 bits/pixel<br />
Mode 54 : 1024x768, 32 bits/pixel<br />
Mode 58 : 1280x1024, 32 bits/pixel<br />
Mode 5a : 1600x1200, 32 bits/pixel<br />
Mode 5c : 1920x1440, 32 bits/pixel<br />
<br />
Now pick the one you want to overwrite. For me, it is 3c. So I then do a:<br />
<br />
#915resolution 3c 1400 1050<br />
<br />
Now to make sure it took:<br />
<br />
#915resolution -l<br />
Intel 800/900 Series VBIOS Hack : version 0.5.2 <br />
<br />
Chipset: 915GM<br />
BIOS: TYPE 1<br />
Mode Table Offset: $C0000 + $269<br />
Mode Table Entries: 36<br />
<br />
Mode 30 : 640x480, 8 bits/pixel<br />
Mode 32 : 800x600, 8 bits/pixel<br />
Mode 34 : 1024x768, 8 bits/pixel<br />
Mode 38 : 1280x1024, 8 bits/pixel<br />
Mode 3a : 1600x1200, 8 bits/pixel<br />
Mode 3c : 1400x1050, 8 bits/pixel<br />
Mode 41 : 640x480, 16 bits/pixel<br />
Mode 43 : 800x600, 16 bits/pixel<br />
Mode 45 : 1024x768, 16 bits/pixel<br />
Mode 49 : 1280x1024, 16 bits/pixel<br />
Mode 4b : 1600x1200, 16 bits/pixel<br />
Mode 4d : 1400x1050, 16 bits/pixel<br />
Mode 50 : 640x480, 32 bits/pixel<br />
Mode 52 : 800x600, 32 bits/pixel<br />
Mode 54 : 1024x768, 32 bits/pixel<br />
Mode 58 : 1280x1024, 32 bits/pixel<br />
Mode 5a : 1600x1200, 32 bits/pixel<br />
Mode 5c : 1400x1050, 32 bits/pixel<br />
<br />
Now you can start/restart the xserver. I did not reboot because it would mess up my settings. Now to make sure that this works. I want to make sure that it will do this automatically. I added the following into /etc/rc.local:<br />
<br />
/usr/sbin/915resolution 3c 1400 1050<br />
<br />
Now I can reboot without any more worries.<br />
<br />
Here is the output of my /etc/X11/xorg.conf:<br />
<br />
Section "ServerLayout"<br />
Identifier "Xorg Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Touchpad" "SendCoreEvents"<br />
Option "AIGLX" "true"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail" "true" <br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc:unscaled"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/PEX"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/Type1"<br />
FontPath "/usr/share/fonts/ttf/western"<br />
FontPath "/usr/share/fonts/ttf/decoratives"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/truetype/openoffice"<br />
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"<br />
FontPath "/usr/share/fonts/latex-ttf-fonts"<br />
FontPath "/usr/share/fonts/defoma/CID"<br />
FontPath "/usr/share/fonts/defoma/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "ddc" # ddc probing of monitor<br />
Load "dbe"<br />
Load "dri"<br />
Load "extmod"<br />
Load "glx"<br />
Load "bitmap" # bitmap-fonts<br />
Load "type1"<br />
Load "freetype"<br />
Load "record"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "keyboard"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" ""<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "USB Mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "SendCoreEvents" "true"<br />
Option "Protocol" "IMPS/2"<br />
Option "ZAxisMapping" "4 5"<br />
Option "Buttons" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.12"<br />
Option "AccelFactor" "0.0010"<br />
Option "SHMConfig" "true"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "DPMS" "true"<br />
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors<br />
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.<br />
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz<br />
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "i810"<br />
VendorName "Intel Corp."<br />
BoardName "Unknown Board"<br />
Option "XAANoOffscreenPixmaps" "true"<br />
Option "DRI" "true"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultColorDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1400x1050"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
<br />
==Audio==<br />
Now for the sound. It works out of the box, but alsa needs to be installed for saving sound setting and all the other good stuff alsa does. Thankfully there is a [http://wiki.archlinux.org/index.php/ALSA howto here].<br />
<br />
== Network ==<br />
=== Wired ===<br />
The wired connection worked out of the box. The Neworkmanager, that we will setup in the next section, will manage this as well as the wireless.<br />
<br />
=== Wireless ===<br />
Now lets get wireless going. There is a [http://wiki.archlinux.org/index.php/Wireless_Setup wireless setup howto] and there is a [http://wiki.archlinux.org/index.php/Networkmanager Networkmanager howto]. I will go into detail about this because wireless is one of the most difficult things to get running (generally). This should be pretty easy to get going.<br />
<br />
Install wireless drivers and network tools<br />
#pacman -Sy ipw2200-fw wireless_tools gnome-network-manager<br />
Add yourself to the network group<br />
#gpasswd -a <user> network<br />
Load module<br />
#modprobe ipw2200<br />
See what device the wireless card it on:<br />
#iwconfig<br />
lo no wireless extensions.<br />
<br />
eth0 no wireless extensions.<br />
<br />
eth1 IEEE 802.11g ESSID:"" <br />
Mode:Managed Frequency:2.442 GHz Access Point: 00:90:4C:7E:00:10 <br />
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 <br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality=98/100 Signal level=-27 dBm Noise level=-92 dBm<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
While still in the /etc/rc.conf file still open, edit the network part of the file:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
eth1="dhcp"<br />
INTERFACES=(lo !eth0 !eth1)<br />
I belive this is optional. It is just to get the blue LED to light up when the wireless is enabled. I added the following to /etc/modprobe.conf:<br />
options ipw2200 led=1 hwcrypto=0<br />
With /etc/rc.conf still open, edit it to stop the network daemon from starting and have networkmanager and dhcdpd daemons start at boot:<br />
DAEMONS=(... !network ... networkmanager dhcdbd)<br />
Now reboot or stop/start the daemons:<br />
# /etc/rc.d/network stop;/etc/rc.d/networkmanager start;/etc/rc.d/dhcdbd start<br />
<br />
That should do it. Note, this is a generic way to set it up. My wireless router is broadcasting its SSID and has no encryption on it. I want to get WPA working though. That will be a task for later.<br />
==== Troubles with wireless ====<br />
It appears the NC6220 can come with a "restricted" ethernet controller. If for some reason you can't get the wireless working, try unplugging the ethernet adaptor. Symptoms are: sending commands to the wireless fails (for example: ipw2200: Failed to send POWER_MODE: Command timed out), the kernel complains about the "Radio Frequency Kill Switch is On".<br />
<br />
=== Modem ===<br />
Have not tried.<br />
<br />
== ACPI ==<br />
When I login to gnome, I keep getting a acpi did not load error. I installed:<br />
pacman -Sy acpid gnome-power-manager<br />
And I added the daemons in the /etc/rc.conf file<br />
DAEMONS=(... acpid)<br />
And rebooted. Now I have the battery monitor to the gnome panel and life is good.<br />
<br />
== Card Readers ==<br />
=== PCMCIA ===<br />
As far as I've understood from other reports, the pcmcia card works as expected. I don't have one at this time, so I can't confirm it.<br />
=== Compact Flash ===<br />
The same goes for the Compact Flash. It's supposed to work as it uses the same interfaces as the PCMCIA does, but I can't confirm anything since I don't have a CF-card.<br />
=== Secure Digital ===<br />
The SD-card reader on the other hand is a pain! It uses proprietary drivers from ricoh under windows and there are no drivers under linux. I would really want this working but I think the only chance would be to reverse engineer the reader and I guess not enough coders have this device. Subsequently, there are no drivers now and there won't be in the foreseeable future...<br />
<br />
==Other Tweaks==<br />
===kernel26beyond===<br />
I use the beyond kernel because I am looking to get [http://wiki.archlinux.org/index.php/Suspend_to_Disk suspend] working. There is a list of different kernel patches/patchsets [http://wiki.archlinux.org/index.php/Kernel_Patches_and_Patchsets here].<br />
Now, lets install the beyond kernel:<br />
# pacman -Sy kernel26beyond<br />
Now add the following to the boot loader. For me, it is grub:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond.img<br />
<br />
# (1) Arch Linux<br />
title Arch Linux Fallback<br />
root (hd0,4)<br />
kernel /vmlinuz26beyond root=/dev/sda7 ro<br />
initrd /kernel26beyond-fallback.img<br />
<br />
===Sudo===<br />
I like to use sudo to manage my system. So as root, I do a:<br />
# pacman -Sy sudo<br />
Then I do a give myself rights:<br />
# visudo -f /etc/sudoers<br />
Add myself under root.<br />
===DISABLE IPV6===<br />
I disabled the IPV6 module because I do not need it. Here is the [http://wiki.archlinux.org/index.php/IPv6_-_Disabling_the_Module howto] to get this.<br />
===SSHfs===<br />
To connect to other shares and doing updates I use SSHfs. Here is a [http://wiki.archlinux.org/index.php/Sshfs howto] for that.<br />
===Packages===<br />
affinity<br />
firefox<br />
thunderbird<br />
flashplugin<br />
flashplayer-standalone<br />
jre # Java<br />
mplayer<br />
vlc<br />
Glipper<br />
tomboy<br />
gaim<br />
ms-fonts<br />
ntp<br />
tracker<br />
affinity<br />
f-spot<br />
<br />
===Files Edited===<br />
<br />
rc.local<br />
rc.conf<br />
pacman.conf<br />
modprobe.conf<br />
inittab<br />
xorg.conf<br />
sudoers<br />
<br />
= External Links =<br />
<br />
* This report is listed at the [http://tuxmobil.org/fujitsu.html TuxMobil: Linux Laptop and Notebook Installation Guides Survey: Fujitsu-Siemens - FSC].</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=43054Xen2008-06-14T17:30:08Z<p>RedShift: /* Installing the necessary packages */</p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor.<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
* Hardware VT: Hardware VT (VirTualization) is hardware assisted virtualization. It makes near-native performance possible.<br />
* VT-d: VT-d is the next step in virtualization. With VT-d not only the processor, but I/O devices like network cards can be virtualized - i.e. they can be accessed natively by the guest OS without going through the host OS.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
Install xen and linux-xen0.<br />
<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
<pre><br />
kernel /xen.gz<br />
module /linux-xen0.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen0.img<br />
</pre><br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=43053Xen2008-06-14T17:29:45Z<p>RedShift: </p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor.<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
* Hardware VT: Hardware VT (VirTualization) is hardware assisted virtualization. It makes near-native performance possible.<br />
* VT-d: VT-d is the next step in virtualization. With VT-d not only the processor, but I/O devices like network cards can be virtualized - i.e. they can be accessed natively by the guest OS without going through the host OS.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
Install xen and linux-xen.<br />
<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
<pre><br />
kernel /xen.gz<br />
module /linux-xen0.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen0.img<br />
</pre><br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=42782Xen2008-06-08T20:25:55Z<p>RedShift: /* Terminology */</p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor.<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
* Hardware VT: Hardware VT (VirTualization) is hardware assisted virtualization. It makes near-native performance possible.<br />
* VT-d: VT-d is the next step in virtualization. With VT-d not only the processor, but I/O devices like network cards can be virtualized - i.e. they can be accessed natively by the guest OS without going through the host OS.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
Install xen and linux-xen.<br />
<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
<pre><br />
kernel /xen.gz<br />
module /linux-xen.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen.img<br />
</pre><br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=42781Xen2008-06-08T20:23:53Z<p>RedShift: /* What is Xen? */</p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor.<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
Install xen and linux-xen.<br />
<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
<pre><br />
kernel /xen.gz<br />
module /linux-xen.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen.img<br />
</pre><br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=42780Xen2008-06-08T20:23:12Z<p>RedShift: /* Installing the necessary packages */</p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor. In Xen terminology anything virtualized is called a "domain".<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
Install xen and linux-xen.<br />
<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
<pre><br />
kernel /xen.gz<br />
module /linux-xen.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen.img<br />
</pre><br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=42779Xen2008-06-08T20:22:47Z<p>RedShift: </p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor. In Xen terminology anything virtualized is called a "domain".<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
<pre><br />
kernel /xen.gz<br />
module /linux-xen.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen.img<br />
</pre><br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=42778Xen2008-06-08T20:22:13Z<p>RedShift: /* Configuring GRUB */</p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor. In Xen terminology anything virtualized is called a "domain".<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
===Configuring GRUB===<br />
At first the Xen hypervisor is booted, and then the Dom0 kernel. Configure your menu.lst as following:<br />
<br />
[code]<br />
kernel /xen.gz<br />
module /linux-xen.gz root=/dev/sda3 ro console=tty0 vga=0x307<br />
module /linux-xen.img<br />
[/code]<br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Xen&diff=42777Xen2008-06-08T20:21:04Z<p>RedShift: New page: Category:System administration (English) Category:HOWTOs (English) This document explains how you setup Xen for Arch Linux ==What is Xen?== According to the Xen development team:...</p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor. In Xen terminology anything virtualized is called a "domain".<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
===Configuring GRUB===<br />
<br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=42776Sun Cobalt RAQ 5502008-06-08T20:20:44Z<p>RedShift: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
===Jumpers on the RaQ 550===<br />
The RaQ 550 has two jumpers that are soldered, JP1 and JP8.<br />
* JP1: On: Sets the FSB to 100 Mhz, Off: Sets the FSB to AUTO<br />
* JP8: Doesn't seem to do anything on and off<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel. You can find the cobalt-panels-utils in the redshift repository. The binaries start with lcd-. See their respective manpages<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers<br />
* My homepage [http://users.opengate.be/~glenn/cobaltraq/]: Some usefull stuff</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=42775Sun Cobalt RAQ 5502008-06-08T20:03:48Z<p>RedShift: </p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor. In Xen terminology anything virtualized is called a "domain".<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
<br />
<br />
==Setting up Xen==<br />
===Installing the necessary packages===<br />
===Configuring GRUB===<br />
<br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=42774Sun Cobalt RAQ 5502008-06-08T20:02:58Z<p>RedShift: </p>
<hr />
<div>[[Category:System administration (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you setup Xen for Arch Linux<br />
<br />
==What is Xen?==<br />
According to the Xen development team: "The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. (more)".<br />
<br />
Basically Xen exists out of two components: the Xen hypervisor, and the userland tools to manage that hypervisor. In Xen terminology anything virtualized is called a "domain".<br />
<br />
===Terminology===<br />
In this document I will be refering to a few basic concepts:<br />
* Host OS: this is the operating system that hosts the guests.<br />
* Guest OS: this is the operating system running in virtualization.<br />
* Domain: when we are talking about virtualization, a domain is one of the virtual machines that run on the system. Domain0 is the first domain started by the Xen hypervisor at boot, and will be running a Linux OS. This domain is privileged: it may access the hardware and can run the XenControlTools that manage other domains. These other domains are referred to as DomUs, the U standing for "user". They are unprivileged, and could be running any operating system that has been ported to Xen.<br />
<br />
===The hypervisor===<br />
The hypervisor is actually a modified linux kernel. It is currently based on kernel 2.6.18.8. This also means that your hardware must be supported by that kernel. A Xen kernel is provided by the linux-xen package.<br />
<br />
===Userland tools===<br />
These tools allow controlling the guests that are running on the system. You can find these tools in the xen package.<br />
<br />
<br />
==Resources==<br />
<br />
* Xen's homepage: [http://www.xen.org/]<br />
* The Xen Wiki: [http://wiki.xensource.com/xenwiki/]</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38826Sun Cobalt RAQ 5502008-03-19T10:35:50Z<p>RedShift: /* Jumpers on the RaQ 550 */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
===Jumpers on the RaQ 550===<br />
The RaQ 550 has two jumpers that are soldered, JP1 and JP8.<br />
* JP1: On: Sets the FSB to 100 Mhz, Off: Sets the FSB to AUTO<br />
* JP8: Doesn't seem to do anything on and off<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel. You can find the cobalt-panels-utils in the redshift repository. The binaries start with lcd-. See their respective manpages<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers<br />
* My homepage [http://users.opengate.be/~glenn/cobaltraq/]: Some usefull stuff</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38825Sun Cobalt RAQ 5502008-03-19T10:35:32Z<p>RedShift: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
===Jumpers on the RaQ 550===<br />
The RaQ 550 has two jumpers that are soldered, JP1 and JP8.<br />
JP1: On: Sets the FSB to 100 Mhz, Off: Sets the FSB to AUTO<br />
JP8: Doesn't seem to do anything on and off<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel. You can find the cobalt-panels-utils in the redshift repository. The binaries start with lcd-. See their respective manpages<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers<br />
* My homepage [http://users.opengate.be/~glenn/cobaltraq/]: Some usefull stuff</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38399Sun Cobalt RAQ 5502008-03-09T17:18:52Z<p>RedShift: /* Resources */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel. You can find the cobalt-panels-utils in the redshift repository. The binaries start with lcd-. See their respective manpages<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers<br />
* My homepage [http://users.opengate.be/~glenn/cobaltraq/]: Some usefull stuff</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38379Sun Cobalt RAQ 5502008-03-08T22:16:42Z<p>RedShift: /* What about the LCD/Front panel? */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel. You can find the cobalt-panels-utils in the redshift repository. The binaries start with lcd-. See their respective manpages<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38378Sun Cobalt RAQ 5502008-03-08T22:11:40Z<p>RedShift: /* What about the LCD/Front panel? */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel. You can find the cobalt-panels-utils in the redshift repository.<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38377Sun Cobalt RAQ 5502008-03-08T22:02:27Z<p>RedShift: /* What about the LCD/Front panel? */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use of the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel.<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38376Sun Cobalt RAQ 5502008-03-08T20:10:35Z<p>RedShift: /* What about the LCD/Front panel? */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
Yes, you can make use the front panel! The kernel is patched to make the Sun Cobalt specific hardware work. Install the cobalt-panel-utils to control the front panel.<br />
<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38361Sun Cobalt RAQ 5502008-03-08T12:19:54Z<p>RedShift: /* Partitioning */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see [[#How the RAQ 550 boots]]). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38360Sun Cobalt RAQ 5502008-03-08T12:19:22Z<p>RedShift: /* System configuration */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see "How the RAQ 550 boots"). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[#Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38359Sun Cobalt RAQ 5502008-03-08T12:18:34Z<p>RedShift: /* System configuration */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see "How the RAQ 550 boots"). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [[Important note about drive assignements]]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38358Sun Cobalt RAQ 5502008-03-08T12:18:18Z<p>RedShift: /* Installing the base system */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see "How the RAQ 550 boots"). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
====System configuration====<br />
'''Important:''' Check your fstab file to have the correct harddrive notation. See [Important note about drive assignements]!<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38356Sun Cobalt RAQ 5502008-03-08T12:17:08Z<p>RedShift: /* '''Important''' note about drive assignements */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware and fstab.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see "How the RAQ 550 boots"). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38355Sun Cobalt RAQ 5502008-03-08T12:16:07Z<p>RedShift: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
=='''Important''' note about drive assignements==<br />
The firmware's kernel uses the "old" style harddisk notation, for example hda2. The linux-raq550 kernel uses the newer libata drivers, causing the harddrive assignements to become for example sda2. Keep this in mind when you're configuring the firmware.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see "How the RAQ 550 boots"). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Sun_Cobalt_RAQ_550&diff=38354Sun Cobalt RAQ 5502008-03-08T12:12:14Z<p>RedShift: /* Configuring the firmware */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This document explains how you can install Arch Linux on a Sun Cobalt RAQ 550 machine.<br />
<br />
==About the RAQ 550==<br />
The Sun Cobalt RAQ 550 is actually just standard PC hardware with customized firmware and board layout. It contains a ServerWorks CSB5 dual channel IDE controller. It has no VGA adaptor, although there is a PCI slot where you could install one (and you would be able to use it). A RAQ 550 comes with the following specifications:<br />
* Processor: Intel Pentium 3 1 Ghz (256 kB Cache) or 1,26 Ghz (512 kB Cache). (That last one is pretty rare because of Intel's limited production of Tuatulatin cores)<br />
* Memory: Supports up to 2 GB of registered ECC PC133 SDRAM. It will not take non-ECC modules, I've tried.<br />
* Disks: Supports 2 LBA24 IDE disks (LBA24 means it only uses 24 bits for addressing, thus it only supports a maximum of ~137 GB. This is a hardware limitation)<br />
* Expansion: 1 x PCI 33 Mhz, 64 Bit (266 mB/s)<br />
* Network: 2 x National Semiconductor DP83815 Fast Ethernet (linux module natsemi)<br />
<br />
You can get them second hand for a good price these days.<br />
<br />
===About the processor===<br />
The original RAQ 550 came shipped with a Pentium 3 1 Ghz (Coppermine) or a Pentium 3 1,26 Ghz (Tuatulatin). However, there's no reason why you can't replace the processor with something else. I tested a celeron 1,2 Ghz (Tuatulatin) and it works. The celeron only has 100 Mhz FSB, and I haven't found a way yet to force the FSB to be 133 Mhz. I believe anything that's Coppermine or Tuatulatin should work.<br />
<br />
==Terminology==<br />
Keep these things in mind, they can be confusing:<br />
* boot kernel/firmware: This is the software loaded on the system's EEPROM. This is basically a modified linux kernel.<br />
* load kernel: This is the kernel that the firmware will try to load. You can use your own kernel here.<br />
<br />
==Requirements==<br />
* One Sun Cobalt RAQ 550<br />
* One hard drive<br />
* One Arch Linux installer CD<br />
* Another computer<br />
* One crazy admin<br />
<br />
Firmware requirements: I haven't tested this with the original firmware that normally ships with the RAQ 550, because mine already came with updated (unofficial) firmware. Updating the firmware is beyond the scope of this document. '''BIG FAT WARNING:''' ''If the firmware update process goes wrong and you reboot your system, you just have turned your RAQ 550 into a '''piece of junk'''''. The only way to fix it would be to desolder the flash chip and have it flashed again with correct firmware. '''If your firmware works for you, I recommend not touching it'''.<br />
<br />
==Setting up your serial port==<br />
The RAQ 550 has two serial ports, which the first one (marked with a single dot) serves as console access. Configure your terminal application to use 115200 baudrate, 8 bits, no parity and 1 stop bit (115200 8N1). Use screen: screen /dev/ttyS0 115200. This serial port setting is hardcoded and cannot be changed.<br />
<br />
==How the RAQ 550 boots==<br />
====Booting from hard disk====<br />
The firmware is actually a modified linux kernel, serving as a bootloader. It will search for<br />
* vmlinux.gz<br />
* vmlinux.bz2<br />
* /boot/vmlinux.gz<br />
* /boot/vmlinux.bz2<br />
on the first partition of the first disk, so this means '''the boot kernel needs to be able to read the filesystem where your load kernel resides'''. This limits the filesystems you can use where the load kernel resides to the filesystems that the firmware supports. Customized firmware may support other filesystems, cobalt's official software only supports ext2. Use ext2. If you have a seperate /boot, you can use whatever filesystem for / that the load kernel supports.<br />
<br />
====Booting from network====<br />
As you might have noticed, the RAQ 550 supports "netbooting". But it's not the netbooting you would expect, it doesn't use PXE. It uses its firmware kernel and tries to set it up with an NFS (Network File System) root.<br />
<br />
==Installing without RAID==<br />
===Moving the RAQ 550 hard drive===<br />
The easiest way for installing Arch Linux is to take out the hard drive, put it in another computer and install Arch Linux from there. If you know what you're doing you can install it any way you want, this article only covers installation via the Arch Linux installer CD. Put the hard drive in the other computer and start the install CD.<br />
===Installing the base system===<br />
Select your method of installation (I always use FTP installs) and proceed with the installation as usual.<br />
====Partitioning====<br />
When it's time to partition your harddrive, the partition where the kernel resides ''must be supported by the firmware'' (see "How the RAQ 550 boots"). Unless you're running modified firmware, the built in firmware only supports ext2 (ext3 is backwards compatible). The kernel must also be located on the first partition.<br />
* Load kernel must be located on the first partition<br />
* Filesystem of the first partition must be supported by the firmware<br />
* Kernel must have a specific name (see "How the RAQ 550 boots")<br />
<br />
====Installation, continued====<br />
Skip the install kernel and install bootloader step. You don't need a bootloader (the firmware is the bootloader) and the stock arch kernel doesn't work because the firmware doesn't support initial ramdisks.<br />
<br />
===Install the linux-raq550 kernel===<br />
Exit the installation and chroot to your new system. Configure pacman's mirrorlist and run<br />
<pre><br />
# chroot /mnt /bin/bash<br />
# nano -w /etc/pacman.d/mirrorlist<br />
# pacman -Sy<br />
</pre><br />
After that, add the redshift repository to your pacman.conf file:<br />
<pre><br />
[redshift]<br />
Server = http://archserver.be/packages/redshift/i686<br />
</pre><br />
Then install the linux-raq550 package:<br />
<pre><br />
# pacman -Sy linux-raq550<br />
</pre><br />
<br />
===Configure the serial port for terminal access===<br />
We're not done yet. We need to configure init to spawn a terminal on the serial port. Add this to your /etc/inittab:<br />
<pre><br />
s0:0123456:respawn:/sbin/agetty -8 -L 115200 ttyS0 vt100<br />
</pre><br />
That will spawn agetty vt100 on the first serial port with a linespeed of 115200 bits/s and assume the line is 8 bit clean. You can comment out the virtual consoles (the vc/n) ones if you don't intend on using them.<br />
<br />
''Notice that you won't be able to log in as root on the serial''. In order to allow root to login from the serial add that serial port to /etc/securetty<br />
<br />
It's useful to already setup sshd. Don't forget to set a password for root (sshd denies passwordless logins by default), and don't forget about hosts.deny.<br />
<br />
===Put the RAQ 550 harddrive back===<br />
Put the RAQ 550 harddrive back in its place, connect the serial cable and power up the system.<br />
<br />
===Configuring the firmware===<br />
Now you'll need to configure the firmware and set your root device. Pay close attention to the startup messages and press the space bar to enter the system rom menu mode. Type boot and then set_root_dev to set the root device. For example:<br />
<br />
<pre><br />
Press spacebar to enter ROM mode<br />
<br />
Cobalt:Main Menu> boot<br />
Cobalt:Boot Menu> set_boot_dev sda3<br />
Cobalt:Boot Menu> reboot<br />
</pre><br />
<br />
After this your system should boot up, ready for use.<br />
<br />
==Notes==<br />
====What about the LCD/Front panel?====<br />
The only way I've found to make the LCD and front panel work is by the patches supplied by Jeff Walter (see resources). These aren't included in the linux-raq550 kernel, as there's no clean way to apply these patches yet. (The patches were written for gentoo's kernel)<br />
====What about earlier RAQ servers, like the RAQ 4?====<br />
The RAQ 4 and 3 have an AMD K6-2 processor, which do not support the full i686 instruction set. RAQ 2 and 1 use MIPS processors. Therefore you cannot use Arch Linux on these RAQ servers.<br />
====Post-install cleanup====<br />
Because of the customized kernel without an initial ramdisk, you can get rid of the following packages:<br />
* kernel26<br />
* mkinitcpio<br />
* klibc-udev<br />
* klibc-module-init-tools<br />
* klibc-extras<br />
* klibc<br />
* gen-init-cpio<br />
* grub<br />
* cpio<br />
* lilo<br />
And obviously packages like pcmcia-utils.<br />
====Using your own kernel====<br />
You can use your own compiled kernel, but the compressed size of the vmlinux file may not be larger than ~1,8 megabytes. Using bzip2 results in a slightly better compression than gzip. The configuration of the linux-raq550 kernel is a good starting point, you can find it in /proc/config.gz<br />
<br />
==Resources==<br />
Unfortunatly, information about the Cobalt RAQ servers is sparse and scattered. Most documentation insists on using CentOS. Here are some interesting links:<br />
* Jeff Walter [http://gentoo.404ster.com/texts.php?action=view&id=10]: This guy installed gentoo on his raq, and wrote kernel patches for using the LCD and front panel.<br />
* Sun's Cobalt site [http://www.sun.com/hardware/serverappliances/discontinued.html#550]: Contains the original documentation for the raq 550 server.<br />
* CobaltFAQs [http://www.cobaltfaqs.com/]<br />
* Sourceforge Cobalt ROM [http://sourceforge.net/projects/cobalt-rom/]: New ROM images for your RAQ and flash utilities<br />
* Depopo.net [http://www.depopo.net]: FAQ site for Cobalt RAQ servers</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38345Jinzora2008-03-08T10:00:06Z<p>RedShift: </p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download and extract Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download and extract the contents using tar.<br />
<br />
<pre><br />
# wget http://get.jinzora.com/jz2current.tar.gz<br />
# tar -xvf jz2current.tar.gz<br />
</pre><br />
<br />
<br />
<br />
==Setting up Jinzora==<br />
===Correct directory permissions===<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
# sh configure.sh<br />
</pre><br />
===Run the installer===<br />
The installer will automatically configure jinzora, and create the database. Open up your webbrowser and go to http://localhost/jinzora2/index.php and follow the instructions<br />
<br />
* Pay attentions to these setup steps:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be.<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. <br />
<br />
You can also import more files from the '''Settings''' interface when Jinzora is up and running. You don't have to do it while installing.<br />
<br />
'''Note:''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
===Save the configuration===<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''.<br />
<br />
==Setting up MPD to play your music==<br />
===Configure jinzora===<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38344Jinzora2008-03-08T09:57:01Z<p>RedShift: </p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download and extract Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download and extract the contents using tar.<br />
<br />
<pre><br />
# wget http://get.jinzora.com/jz2current.tar.gz<br />
# tar -xvf jz2current.tar.gz<br />
</pre><br />
<br />
<br />
<br />
==Setting up Jinzora==<br />
===Correct directory permissions===<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
# sh configure.sh<br />
</pre><br />
===Run the installer===<br />
The installer will automatically configure jinzora, and create the database. Open up your webbrowser and go to http://localhost/jinzora2/index.php and follow the instructions<br />
<br />
* Pay attentions to these setup steps:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be.<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38343Jinzora2008-03-08T09:55:02Z<p>RedShift: /* Step 6 */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download and extract Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download and extract the contents using tar.<br />
<br />
<pre><br />
# wget http://get.jinzora.com/jz2current.tar.gz<br />
# tar -xvf jz2current.tar.gz<br />
</pre><br />
<br />
<br />
<br />
==Setting up Jinzora==<br />
===Correct directory permissions===<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
# sh configure.sh<br />
</pre><br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38342Jinzora2008-03-08T09:54:15Z<p>RedShift: /* Step 5 */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download and extract Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download and extract the contents using tar.<br />
<br />
<pre><br />
# wget http://get.jinzora.com/jz2current.tar.gz<br />
# tar -xvf jz2current.tar.gz<br />
</pre><br />
<br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38341Jinzora2008-03-08T09:54:03Z<p>RedShift: /* Download and extract Jinzora */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download and extract Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download and extract the contents using tar.<br />
<br />
<pre><br />
# wget http://get.jinzora.com/jz2current.tar.gz<br />
# tar -xvf jz2current.tar.gz<br />
</pre><br />
<br />
==Step 5==<br />
<br />
Copy the downloaded file to '''~/httpd/html''' (i.e. '''''your user's home directory''/httpd/html''') and then extract it with <br />
<pre>tar -zxvf [filename]</pre><br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38340Jinzora2008-03-08T09:52:56Z<p>RedShift: /* Download Jinzora */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download and extract Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download Extract the contents using tar: tar -xvf ''filename''.<br />
<br />
==Step 5==<br />
<br />
Copy the downloaded file to '''~/httpd/html''' (i.e. '''''your user's home directory''/httpd/html''') and then extract it with <br />
<pre>tar -zxvf [filename]</pre><br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38339Jinzora2008-03-08T09:52:01Z<p>RedShift: /* Step 4 */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Download Jinzora==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download .<br />
<br />
==Step 5==<br />
<br />
Copy the downloaded file to '''~/httpd/html''' (i.e. '''''your user's home directory''/httpd/html''') and then extract it with <br />
<pre>tar -zxvf [filename]</pre><br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38338Jinzora2008-03-08T09:51:44Z<p>RedShift: /* Step 3 */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
<br />
<br />
==Step 4==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download .<br />
<br />
==Step 5==<br />
<br />
Copy the downloaded file to '''~/httpd/html''' (i.e. '''''your user's home directory''/httpd/html''') and then extract it with <br />
<pre>tar -zxvf [filename]</pre><br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38337Jinzora2008-03-08T09:51:35Z<p>RedShift: /* Configure PHP */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these.<br />
Uncomment gd.so and iconv.so in /etc/php/php.ini.<br />
<pre><br />
extension=gd.so<br />
extension=iconv.so<br />
</pre><br />
The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
Also take a look at the open_basedir setting. Your media directory should be or below the paths specified in this directory.<br />
<br />
==Step 3==<br />
<br />
Uncomment the following line in '''/etc/php.ini''' (by deleting the semicolon in front of it ;))<br />
<pre><br />
extension=gd.so<br />
</pre><br />
<br />
<br />
==Step 4==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download .<br />
<br />
==Step 5==<br />
<br />
Copy the downloaded file to '''~/httpd/html''' (i.e. '''''your user's home directory''/httpd/html''') and then extract it with <br />
<pre>tar -zxvf [filename]</pre><br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShifthttps://wiki.archlinux.org/index.php?title=Jinzora&diff=38336Jinzora2008-03-08T09:49:59Z<p>RedShift: /* Step 2 */</p>
<hr />
<div>[[Category:Audio/Video (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Stub}}<br />
<br />
:''Jinzora is a GPL web based multimedia application. It serves as a streaming server as well as a media mangement platform.''<br />
:''This article will show you how to install and configure Jinzora.''<br />
<br />
==Step 0==<br />
Jinzora can run in two modes, ''streaming'' and using ''mpd''. If you haven't installed MPD already, follow the wiki guide: [[mpd]] (It's not required for the streaming mode to operate)<br />
<br />
==Setup the webserver==<br />
Follow the wiki tutorial for installing Apache, PHP and MySQL: [[LAMP]]<br />
<br />
(Note: Installing phpMyAdmin from the above guide is optional; if you're ever likely to make your own website that will use PHP and MySQL, I'd suggest you install it. Otherwise you probably won't need it).<br />
<br />
==Configure PHP==<br />
Jinzora can make use of the GD and iconv library. It is recommend you enable these. Uncomment gd.so and iconv.so in /etc/php/php.ini. The PHP gd extension requires the gd library to be installed:<br />
<pre><br />
pacman -S gd<br />
</pre><br />
<br />
==Step 3==<br />
<br />
Uncomment the following line in '''/etc/php.ini''' (by deleting the semicolon in front of it ;))<br />
<pre><br />
extension=gd.so<br />
</pre><br />
<br />
<br />
==Step 4==<br />
<br />
Download the latest version of Jinzora2 from http://en.jinzora.com/download .<br />
<br />
==Step 5==<br />
<br />
Copy the downloaded file to '''~/httpd/html''' (i.e. '''''your user's home directory''/httpd/html''') and then extract it with <br />
<pre>tar -zxvf [filename]</pre><br />
<br />
<br />
==Step 6==<br />
<br />
In the jinzora2 directory you've now got in '''~/httpd/html''', run configure.sh<br />
<pre><br />
sh configure.sh<br />
</pre><br />
<br />
<br />
==Step 7==<br />
<br />
Open up your webbrowser and go to http://localhost/jinzora2/index.php , then follow the installation guide.<br />
<br />
* The only things you'll have to change are:<br />
** '''Page 4 - Installation Type :''' Change from 'Streaming' to 'Streaming & Jukebox' if you wish to listen to the music on the computer you're installing Jinzora2 on (it's primarily a streaming application to allow remote access to, and control of, a streaming server running it).<br />
** '''Page 5 - Main Settings :''' If you hover over the boxes here, they explain the settings, so choose whatever you want. It's best to choose 'Database' for Backend Type. I'd also suggest using the 'Tag Data' option for 'Data Structure', unless your music is organized on your filesystem exactly the way you want it to be :P<br />
** '''Page 6 - Backend Setup :''' Unless you've used Jinzora before, or for some reason wish to manually create a MySQL database for it to use, then select 'True' under 'Create Database'.<br />
** '''Page 7 - Import Media :''' This step may take a few minutes if you've got a few gigs of music; simply enter into the box the directory where your music is stored. When the installer's finished importing the music from this directory, you'll have the option to import as many other directories as you want, one after the other. You can also import more files from the '''Settings''' interface when Jinzora is up and running.<br />
<br />
<br />
'''Note :''' While Jinzora was importing my music collection, I had the following error appear twice on the page:<br />
<br />
<pre>Warning: strpos() [function.strpos]: Offset not contained in string. in /home/httpd/html/jinzora2/services/services/tagdata/getid3/module.tag.id3v2.php<br />
on line 1542</pre><br />
<br />
This seemed to have no adverse effect on the installation though, so if something similar happens to you, don't worry!)<br />
<br />
<br />
==Step 8==<br />
<br />
When you've finished importing your music, click '''Proceed to save config''', then '''Proceed to launch Jinzora'''. You will now get an error message - to resolve this, you must go into your '''~/httpd/html/jinzora2''' directory and delete the 'install' directory.<br />
<br />
<br />
==Step 9==<br />
<br />
Edit '''~/httpd/html/jinzora2/jukebox/settings.php''': under 'Description', change 'Winamp Media Player' to `Music Player Daemon` (or whatever you want), and under 'type' change 'winamp3' to 'mpd'.<br />
<br />
Change 'password' to be empty (so it just reads <nowiki>''</nowiki> rather than 'jinzora'), or change this to whatever password you've set in '''/etc/mpd.conf''' .<br />
<br />
Also in this file, change the port from '4800' to '6600', or whatever port you've set MPD to accept connections on in '''/etc/mpd.conf''' .<br />
<br />
<br />
==Step 10==<br />
<br />
If you wish to use Jinzora's streaming functionality, you will need to edit '''/etc/hosts.allow''' and add<br />
<br />
<pre><br />
mpd:ALL<br />
</pre><br />
<br />
(or alternatively, simply add the ip (range) from whichever remote computer(s) you'll be accessing the stream server with.<br />
<br />
Now go back to your webbrowser, click refresh, select 'Music Player Daemon' from the 'Playback To' dropdown menu and Voila! Your own working copy of Jinzora !<br />
<br />
==Troubleshooting==<br />
<br />
* If you can't get any sound despite all of the above, try testing mpd with another GUI client (Glurp is a nice simple one - do '''pacman -S glurp''', add a track to its playlist and try to play it). If you have no sound in this either, you need to further edit /etc/mpd.conf. Try uncommenting some of the ALSA settings in this file (assuming you use ALSA).<br />
<br />
* If you know that MPD ''is'' working, then try to match up the settings in Jinzora as closely to those in /etc/mpd.conf as possible (the settings in Jinzora are accessed from the 4th small green button on the upper left of the 'Slick' interface).<br />
<br />
* If changes to your playlist are ignored, go to System Tools -> Settings Manager -> Main Settings/Playlist and set 'use_ext_playlists' to 'false'.<br />
<br />
* If when you click on the PLAY button of any song / album you are offered a 'playlist.m3u' download, then you haven't changed the 'Playback To' option to 'Music Player Daemon'.</div>RedShift