Two new IRC servers have been added, jacklab.net was connected a few days ago and localh0rst.de fulfills its duties as a leafserver since today. The new opers are GraveDigger, who is a TeRa IRC veteran and has been around from the very beginning, he is responsible for the jacklab.net server. The other oper is Jon, he is quite new to TeRa an decided to hook up a server just today. BTW jacklab.net can only be accessed via TLS.
Asus strikes yet again. You might remember that I ordered an Asus mainboard the other day, mentioned it here. Unfortunately it was too late to change my order. I recieved the board about a week ago and found time to install it yesterday. As it turns out, the mainboard is either completly broken OR it just does not support my WD3200JS harddrive, either way, Asus f*cked up again, it’s one thing to not support Linux but another to not support a SATA harddrive. According to the
Related articles:
After the harddrive crash I decided to upgrade the server’s hardware, so that next time I wouldn’t have to cry over lost data. The new lineup of my server’s storage system now is:
The whole idea is to create a RAID5 which has a redundancy of 1 harddrive, this leaves the server with 3*320gig space. The Zalman heatpipes will hopefully keep the harddrives at a appropriate temperatur level and reduce vibrations, which should increase the potential lifetime of the drives. Additionally, they expand the 3.5 inch harddrives’ width to 5,25 inches, which enables me to install them into the cdrom drive bays that are located above the usual harddrive bays. The pictures below illustrate the use of the heatpipes and what the server looked like before the installation of the harddrives.
After “screwing around” for about one and a half hours, always trying not to break the new hardware by mistake, all harddrives were installed.
Time to move on and connect the drives to the powersupply, the first picture shows the server before the rearrangement of the cables, all following pictures display the actual improvement.
But wait … due to the fact that my old mainboard does not provide the PCIe slots needed for the RAID controller, a new mainboard had to be bought. I also wanted to use my old CPU (Sempron 3100+), which runs on 754. It was hard to find a mainboard featuring PCIe x8 (or higher) that also supports 754 CPUs. After solving the PCIe issue, the next problem arose. My old power supply, a TAGAN TG380-U01 only provided 20 pins but the new mainboard needed 24. I did not want to use some crappy 20pin to 24 pin translator, so I went to my local pc dealer and got an Enermax Liberty power supply. Finally everything was compatible and I could proceed installing the hardware.
HIER NOCH BILDER VON MAINBOARD ADDEN!!!
As you can see on the pictures, it was time to install the cpu, ram and pci(e) cards and wire up the harddrives. When I tried to unhook the cpu from the old socket, I discovered that the cooling paste makes a really good glue, it took me half a day to get the guts to pull harder, never experienced such a bitch ever before, usually they stick a bit but this time it was more cement than it was cooling paste.
First of all I had to get rid of the cement, for this purpose, I can only recommend the two component ArticClean, worked perfectly as the picutures below illustrate.
After that new cool paste was applied and the active cooler was reattached.
Ok lets recall what I have had to do so far. I bought a raid controller, which did not fit my old mainboard. The new mainboard was not supported by my old powersupply so I had to get a new one. Now if you think my problems were over, you are wrong, just take a look at the next few pictures ….
Yes, the raid controller does not properly fit the case, well fortunately, this is just a minor flaw. Up next wireing up the harddrives. The Enermax power supply features a modular buildup, you only connect the wires you really need.
Well, well finally done. Took me weeks to get the system set up as it is now. Ordering hardware, waiting, ordering more hardware, even more waiting. But now everything seemed to work, powered the computer and guess what …
I am tired now and will continue tomorrow, just finished this post so that you can get an impression of my path of suffering …
Wie ihr wisst, hab ich ein Thinkpad, mit dem ich auch schon mal unterwegs bin. Da braucht man manchmal auch Internet und man findet gerade kein offenes WLAN. Mit dem passendem Kleingeld in der Tasche kann man sich per GPRS mit Vodafone verbinden und E-Mails abrufen (mehr würde ich aus Kostengründen nicht machen). Dazu habe ich mir von meinem Vater das passende USB Datenkabel (Nokia CA-53) für mein Nokia 6230i ausgeliehen, da ich irgendwie keins habe und angefangen mein Debian zu vergewaltigen.
Beim Einstöpseln des USB-Kabels fragt das Handy, ob man es "als Speichergerät verwenden" möchte - heißt im Klartext, dass es sich wie ein USB-Storage verhält, man kann aber nur auf die MMC zugreifen, nicht auf die Daten im Handyspeicher. Also abbrechen und das Handy ist nun einfach angeschlossen. lsusb sagt:
Bus 003 Device 005: ID 0421:0428 Nokia Mobile Phones
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0×0421 Nokia Mobile Phones
idProduct 0×0428
bcdDevice 3.50
iManufacturer 1 Nokia
iProduct 2 Nokia 6230i
iSerial 0
bNumConfigurations 1
…
Wenn der Kernel bereits mit CONFIG_USB_ACM=m gebaut ist, wird das cdc_acm Modul geladen und /dev/ttyACM0 erstellt (ich musste erstmal Kernel neubauen).
Bis dato hatte ich keinen Erfolg Wammu oder Gammu zum Funktionieren zu bewegen. Liegt anscheinend am Kabel (über Infrarot hab ich das mal vor längerer Zeit gemacht) ist aber nicht so tragisch, denn ich möchte primär ins Internet. Dafür braucht man den pppd, unter Debian im Paket "ppp" enthalten. Des weiteren muss der Kernel mit PPP-Unterstützung gebaut sein (war meiner natürlich wieder nicht). Also mal schauen ob man folgende Optionen hat:
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
Bei Multilink und Filter bin ich mir nicht sicher, dass man sie braucht, aber schaden tun sie nicht.
Wenn der Kernel und Userspace bereit für PPP sind, muss man dieses konfigurieren. Also geht man auf vodafone.de und schaut sich die GPRS Einstellungen an. Daraus ergeben sich dann folgende zwei Konfigurationsdateien:
chatscipt (/etc/chatscripts/vodafone-gprs):
TIMEOUT 5
ECHO ON
ABORT ‘\nBUSY\r’
ABORT ‘\nERROR\r’
ABORT ‘\nNO ANSWER\r’
ABORT ‘\nNO CARRIER\r’
ABORT ‘\nNO DIALTONE\r’
ABORT ‘\nRINGING\r\n\r\nRINGING\r’
” \rAT
TIMEOUT 12
OK ATE1
OK ‘AT+CGDCONT=1,"IP","web.vodafone.de"’
OK ATD*99#
CONNECT ""
peer (/etc/ppp/peers/vodafone-gprs):
connect "/usr/sbin/chat -v -f /etc/chatscripts/vodafone-gprs"
/dev/ttyACM0
115200
noipdefault
usepeerdns
defaultroute
persist
noauth
Nun reicht ein herzliches pon vodafone-gprs und nach wenigen Sekunden hat man eine Verbindung. poff vodafone-gprs beendet diese dann wieder.
Das Problem ist nun, dass GRPS-by-Call bei Vodafone ca 19Cent pro 10KB kostet und ich mir das auf Dauer nicht leisten kann. Bei ALDI-Talk kriegt man 1MB für 24Cent, was ich recht okay finde (wenn auch super teuer im Vergleich zu DSL oder Cable) und man darf (passende Hardware vorausgesetzt) UMTS zu selben Preisen nutzen. Der Hacken an der Sache ist, dass ALDI-Talk im E-Plus Netz werkelt, und die absolut bescheidene Abdeckung haben, was GPRS und UMTS angeht. Mal schauen, werde mir so ne Prepaid Karte dennoch holen denk ich, und dann sehen wir weiter. Immerhin hab ich keine Kosten wenn das Ding in der Ecke vergammelt.
I recently bought a compact-flash WLAN card for my PDA - a BUFFALO WLI-CF-S11G which came with a fucking old firmware (1.3.4) so I could not get WPA working with wpa_supplicant.
On the net I found several hints, I should update my firmware to 1.7.4 or something like it. I also found a nice howto by jun sun how actually to do the update and also where to get the firmware-files.
ffs the hostap driver of my PDA was not compiled with CONFIG_HOSTAP_FIRMWARE=y and CONFIG_HOSTAP_FIRMWARE_NVRAM=y so I couldn’t update the firmware directly on the PDA. So I got a cheap (8.50EUR incl shipping) CF to PCMCIA adaptor (Panasonic BN-CFADPP3) and tried my luck with my Debian laptop.
Off course my kernel was without hostap support - why should it if I have only Intel and Atheros cards here? Recompiled, installed and got weird errors during modprobe:
hostap: disagrees about version of symbol skb_queue_purge
and so on - after a reboot it worked - don’t ask me why, usually recompiling the modules and running depmod -a is sufficient.
I also built hostap-utils 0.4.7 from source, because Debian still has 0.4.0 :(
As root I ran
./prism2_srec -v wlan0 pk010101.hex sf010704.hex
./prism2_srec -v -f wlan0 pk010101.hex sf010704.hex
from the dir with the hostap-utils and the downloaded firmware-files.
Now I get
# ./hostap_diag wlan0
Host AP driver diagnostics information for ‘wlan0′
NICID: id=0×800c v1.0.0 (PRISM II (2.5) PCMCIA (SST parallel flash))
PRIID: id=0×0015 v1.1.1
STAID: id=0×001f v1.7.4 (station firmware)
And WPA is working like a charm ;)
