Skip to main content

Setting up wireless with Mandriva 2007

I rarely install Linux on laptop. It was great to have one and saw how Linux distros progressed in this area. Since last week, I have been a responsible person for one of my office's laptop. I tried installing Fedora Core 6 on it. It was no good. After a couple of minutes, it started to become slower like something was going on in the background. It was so annoying. I tried upgrading the kernel and all the latest updates using yum but to no avail. Of course your mileage may vary.

Mandriva 2007
With Mandriva 2007, I was in luck. I got the DVD from LinuxForYou magazine. I am no stranger with Mandriva. I have been using it for 5 years and one of servers I managed using it. As any desktop-oriented distros, Mandriva is one of the user-friendliest distros out there. It is good and will be better in the future.

Wireless
My laptop is Intel-based. What i mean here is the wireless, CPU and VGA chipsets are from Intel. My wireless is ipw3945. No driver for this chipset I could found in the DVD. After googling, the driver is here. This is the kernel module (driver) for the wireless chipset. Hence, I activated it with modprobe : modprobe ipw3945. It created a device called eth1 (eth0 was reserved for wired connection).

Connecting to AP
Open Mandriva Control Center and go to Network And Internet:
Click on the Wireless connection.


As you see in the diagram below, the AP signal was detected and shown. The button Disconnect should be Connect before you connect your laptop to the AP.


If the connection is successful, then you can connect to your network and internet. Contact your network administrator if you have problem. Good luck.

Comments

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Moving your mysql database to another hard disk

Recently, my server's only hard disk was almost full. I bought a new hard disk with bigger size and I decided to just add it as a second hard disk. Since I need to move it to the 2nd hard disk, I need to find a proper way to move the db with minimum downtime. So I googled around and found a solution.
First, I needed to format the 2nd hard disk and I chose xfs as the filesystem. I created 2 partitions using Linux's fdisk for this task. First partition is 10 GB and 2nd one is around 900 GB. That's approximately added up to 1 TB. Then I mounted the 2nd partition in current partition eg /media/hd2 as follows:
mount -t xfs /dev/sdb5 /media/hd2
where /dev/sdb5 is the partition and /media/hd2 is the mounting dir.
Stop mysql db before doing anything:
service mysql stop
Afterthat, I copied the entire db to newly mounted hard disk:
cp -rv /var/lib/mysql /media/hd2
It will take a while if you have huge databases.
Then, change the ownership of the dir to user and group of mysql:
chown -R mysql:…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy