Sylvestre's blog

Still boring to manage proprietary drivers with a Linux Kernel... Each time I want to update my kernel, I have to reinstall the ATI (ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]) and WIFI (Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter) drivers ...

So, I write down a quick procedure for a lazy copy/paste the next time.
Procedure for GNU/Linux with gcc 3.3 / kernel 2.6.13 / Ati Drivers fglrx 8.16.20 for X.org / ipw2100 1.1.0 / Alien 8.56 (RPM to .deb)
ATI drivers :

wget http://dlmdownloads.ati.com/drivers/linux/fglrx_6_8_0-8.19.10-1.i386.rpm

alien fglrx_6_8_0-8.19.10-1.i386.rpm
dpkg --force-overwrite -i fglrx-6-8-0_8.19.10-2_i386.deb
cd /lib/modules/fglrx/build_mod
chmod +x ./make.sh && ./make.sh
cd ..
chmod +x ./make_install.sh && ./make_install.sh

Wifi Card :

wget http://switch.dl.sourceforge.net/sourceforge/ipw2100/ipw2100-1.1.0.tgz
tar zxvf ipw2100-1.1.0.tgz
cd ipw2100-1.1.0
wget http://www.bughost.org/bugzilla/attachment.cgi?id=429
mv attachment.cgi\?id\=429 compilation_fix
patch < compilation_fix
make
make install

And the /etc/modules should have (the order does matter) :

agpgart
agp_ati
fglrx
i8k force=1
ipw2100

Edit : Comments are closed. Thank you spammers

Just a quick memo for me and other who will get this external harddrive/card reader.

This box contains a 60 go (in fact 56) and can read a few memory card : CF I and II, MS, MS Pro, SD, MMC, IBM MicroDrive, RS-MMC, mini-SD, MS Duo and MS Pro Duo.

As I don't want to reboot under Windows each time I want to use it, here is the procedure to have it working under Linux.

You need a few modules :

- SCSI disk support (BLK_DEV_SD)
-> Device Drivers
  -> SCSI device support
    -> SCSI device support (SCSI [=y])
      ->  SCSI disk support

- Qlogic QLA 1240/1x80/1x160 SCSI support (SCSI_QLOGIC_1280)
-> Device Drivers
  -> SCSI device support
    -> SCSI device support (SCSI [=y])
      -> SCSI low-level drivers
        -> Qlogic QLA 1240/1x80/1x160 SCSI support

- USB Mass Storage support (USB_STORAGE)
-> Device Drivers
  -> USB support
    -> Support for Host-side USB (USB [=y])
      -> USB Mass Storage support 

It should be enough. Recompile kernel/modules. Reboot

Plug the two USB connectors (DON'T forget to plugin both if it is not working with only one because of the lack of energy provided by my laptop).
If you try the command lsusb, you should see that :

Bus 001 Device 008: ID 0d7d:1470 Phison Electronics Corp.

And in /var/log/kern.org, you should get messages :

Jul  8 16:34:18 zoidberg kernel: usb-storage: scsi cmd done, result=0x0
Jul  8 16:34:18 zoidberg kernel: usb-storage: *** thread sleeping.
Jul  8 16:34:18 zoidberg kernel: SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
Jul  8 16:34:18 zoidberg kernel: sda: assuming drive cache: write through

Then, you should be able to mount the /dev/sdXX (sda1 for me) partition where you want with the command :

mount -t vfat /dev/sda1 /mnt/external

Or add in the /etc/fstab this line :

/dev/sda1	/mnt/external			vfat    rw,user

Edit : comments are closed. Thank your spammer.

Imagine that you are dirty with your DNS server. You make some modifications very often and you are not sure when your DNS server is up, RFC and running. Here is a little script which will automatically test some domains and send emails in case of error.

In order to test domains validity, I use DNSdoctor (http://www.dnsdoctor.org/), a fork from Zonecheck (http://www.afnic.fr/outils/zonecheck), a tool developed to perform verifications on the quality of the configuration (it is mandatory with a .fr to have the domain correctly configured). DNSdoctor exists with a few GUI :
- the web interface - http://demo.dnsdoctor.org/
- a classical application using GTK
- a command line application

Of course, I am using the last one to perform the automatic testing system.

As DNSdoctor has been made using Ruby, I made this script with this language (I don't want to have to install python for this script). It will call the DNSdoctor with the appropriate parameters. If an error is detected, it will send an email associated to the domain in the configuration.

If an error occurs, this kind of email will be sent :

ZONE  : ledru.info.
NS <= : akira.ecranbleu.org. [195.137.249.60]
NS    : radium.meaweb.com. [83.217.68.103]
NS    : trunks.ecranbleu.org. [195.137.249.61]

[> ICMP answer
w> Host doesn't reply to ICMP requests (firewall?)
=> radium.meaweb.com./83.217.68.103
=> akira.ecranbleu.org./195.137.249.60
=> trunks.ecranbleu.org./195.137.249.61

[> UDP connectivity
f> Server doesn't listen/answer on port 53 for UDP protocol
 | Ref: IETF RFC1035 (p.32 4.2. Transport)
 |   The DNS assumes that messages will be transmitted as datagrams or in
 | a byte stream carried by a virtual circuit. While virtual circuits can
 | be used for any DNS activity, datagrams are preferred for queries due
 | to their lower overhead and better performance.
 `----- -- -- - -  -
=> radium.meaweb.com./83.217.68.103

==> FAILURE (and 3 warning(s))

#!/usr/bin/ruby
require 'net/smtp'

###########" Parameters ###############
pathCommand="export LANG=en_EN; /usr/bin/dnsdoctor"
paramCommand="-q -vn,d,x,-c "
logFile="/tmp/massDNS.log"
subject="DNS error"
from="tech@linesurf.com"
testDNS= [
	{'domain'=>'ecranbleu.org',
	'email'=>'email@domain.com'},

	{'domain'=>'ledru.info',
	'email'=>'email@mondomaine.com'}
]

def sendmail(from,to,content)
	# --- Send using class methods
	msg = [ "Subject: Test\n", "\n", content ]
	Net::SMTP.start('localhost') do |server|
		server.sendmail( msg,  from , [ to ] )
	end
end

######### Don't edit under #############

command="#{pathCommand} #{paramCommand} "	
for domain in testDNS
	puts "Processing of #{domain['domain']}"
	commandLine=command + domain['domain']
	system(commandLine +'  > '+ logFile +' 2>&1')
	if ($? != 0) 
		content=""
		IO.foreach(logFile) { |line| content+=line }
		sendmail(from,domain['email'],content)
		puts "Erreur"
	end
	File.delete(logFile)	
end

Edit : comments are closed. Thank you spammer.

Un ami testant mon interface graphique chez lui, il s'est mis dans la tête de faire la même chose avec mac au niveau du menu (à savoir les icones qui grossissent quand la souris passe dessus).
Connaissant relativement bien Fvwm, je l'ai donc aidé. Après quelques recompilations de Fvwm avec les quelques patchs de rigueur (fvwm-2.5.9-translucent-menus.diff pour les menus transparents et fvwm-2.5.10-fvwmbuttonshover.diff pour le mouseOver) et un changement de tous les icones pour des plus récents, voila le résultat de la manipulation.

Menu Fvwm

Pas à dire, bien tunné, FVWM explose beaucoup d'interfaces graphiques même celles développées par des boites de Seattle.

Les icones viennent de deux thèmes d'icones : aCurve & Etiquette.

Lire la suite »