Thursday, November 15, 2007
How to configure madwifi on IBM T42p
Well i'm not detailing everything here, as it's already done by other's. I'll just point out my findings on the last quest to have wifi working in linux 2.6.2x versions.
first step check, with dpkg -l | grep ^i.*'madwifi' all the already installed madwifi packages, if any, just delete them wth dpkg -r and purge them dpkg -p .
Alright, now the best and easiest way to do it is using the automated way :
1. Add to you /etc/apt/sources.lst the following lines :
2. Get the debian packages :
4.Now it comes the tricky part. The physical wireless interface is wifi0, but madwifi supports virtualization (concurrent/multiple AP's/stations), so it will creat a virtual interface called athx. The default is ath0, and you can safely do :
http://madwifi.org/wiki/UserDocs/Distro/Debian/MadWifi
Also, on old distributions marlow's site is quite good :
http://www.marlow.dk/site.php/tech/madwifi
first step check, with dpkg -l | grep ^i.*'madwifi' all the already installed madwifi packages, if any, just delete them wth dpkg -r
Alright, now the best and easiest way to do it is using the automated way :
1. Add to you /etc/apt/sources.lst the following lines :
# Testing
deb ftp://ftp.au.debian.org/debian testing main contrib non-free
deb-src ftp://ftp.au.debian.org/debian testing main contrib non-free
2. Get the debian packages :
$ su3.Check if modules are loaded :
# apt-get update
# apt-get install madwifi-source
# apt-get install madwifi-tools
# m-a prepare
# m-a a-i madwifi
# lsmod | grep ath
you should see something like this :
ath_rate_sample 11776 1
ath_pci 87712 0
wlan 183620 4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 191440 3 ath_rate_sample,ath_pci
NOTE: If you don't see it just do the following :
# modprobe ath_pci
Then do lsmod again to check that the module was loaded. If not check syslog (dmesg command) and see any error msg
4.Now it comes the tricky part. The physical wireless interface is wifi0, but madwifi supports virtualization (concurrent/multiple AP's/stations), so it will creat a virtual interface called athx. The default is ath0, and you can safely do :
# ifconfig ath0 upYou may find detailed information on madwifi main site at :
# iwlist ath0 scan
(use man iwconfig help to configure your AP parameter's)
# ifdown ath0
# ifup ath0 ( this is just to refresh dhcp query)
http://madwifi.org/wiki/UserDocs/Distro/Debian/MadWifi
Also, on old distributions marlow's site is quite good :
http://www.marlow.dk/site.php/tech/madwifi
Thursday, July 14, 2005
Nokia 6630 GPRS/UMTS connection
Hi people,
After some hours searching ...finnally the light. I manage to put to work my new nokia 6630 in linux, both using bluetooth or the USB cable (preferred because it's faster...).
Ok, so let's start....begining with some important information:
System:
IBM T42P 2379DYU
Debian Linux Sarge with kernel 2.6.12.2 (costumized)
First step, you need to check if their's kernel support for :
- the cable serial interface (/dev/ttyACM0)
- ppp asynchronous serial
This means the following. Check on your .config file on /boot directory (i.e. /boot/config-"kernelrelease") for the following parameters:
- CONFIG_USB_ACM=m (this will enable serial cable support for the phone)
- CONFIG_PPP_ASYNC=m
- CONFIG_PPP_SYNC_TTY=m (this will enable ppp negotiation both on bluetooth and serial connection)
NOTE: If you're using "make" to configure the kernel search here :
- Device Drivers/ Networking support/PPP support: PPP sync & PPP async tty support;
- Device Drivers/ USB Support/ Support for Host-Side USB: USB Modem (CDC ACM) support;
If that wasn't enable on the kernel... YOU HAVE TO RECOMPILE IT .JAJAJAJAJA GOOD LUCK
Now, for bluetooth connection ONLY the ASYNC TTY support is needed (ei.. i'm supposing that you already have bluetooth active ..right ;) ). Ussually when you try co connect to internet the error that comes with it is "PPP negotiation failed" or something like that.
For USB serial, you have to have also USB serial support... that you have now... If you check DMESG should appear something like this:
"...usb 3-2: new full speed USB device using uhci_hcd and address 4
cdc_acm 3-2:1.8: ttyACM0: USB ACM device..."
Ok, next fase ... connecting...
For Nokia 6630 their's NO script to use with easyconnect
Quite easy ..search the net for "pppd call gprs" you will find several scripts to make a ppp call. The important ones are:
gprs
gprs-connect-chat
gprs-disconnect-chat
...All this files should go to /etc/ppp/peers/. Their are several pages on the internet that can show you how to configure this. Here i will put only my configuration:
Devices:
# Serial device to which the GPRS phone is connected:
# /dev/ttyS0 #for serial port (COM1 in Windows),
# /dev/ircomm0 #for IrDA,
/dev/rfcomm0 # Bluetooth serial port one
#/dev/ttyACM0 # USB serial device - Nokia 6630
NOTE: if you're using locally a 10.x.x.x network do the following change:
# IP addresses:
# - accept peers idea of our local address and set address peer as 10.0.0.1
# (any address would do, since IPCP gives 0.0.0.0 to it)
# - if you use the 10. network at home or something and pppd rejects it,
# change the address to something else
:20.0.0.2 (i changed from :10.0.0.1)
...and that's it ... you're ready to surf...
In bluetooth just dor /etc/init.d/bluez-utils restart (to BIND the phone)...or, RFCOMM bind 0 HWaddr. With the cable sutff it in the USB port and check that kernel recognized the phone ...
Do, pppd call gprs and wait untill the connection is established and voila ..
After some hours searching ...finnally the light. I manage to put to work my new nokia 6630 in linux, both using bluetooth or the USB cable (preferred because it's faster...).
Ok, so let's start....begining with some important information:
System:
IBM T42P 2379DYU
Debian Linux Sarge with kernel 2.6.12.2 (costumized)
First step, you need to check if their's kernel support for :
- the cable serial interface (/dev/ttyACM0)
- ppp asynchronous serial
This means the following. Check on your .config file on /boot directory (i.e. /boot/config-"kernelrelease") for the following parameters:
- CONFIG_USB_ACM=m (this will enable serial cable support for the phone)
- CONFIG_PPP_ASYNC=m
- CONFIG_PPP_SYNC_TTY=m (this will enable ppp negotiation both on bluetooth and serial connection)
NOTE: If you're using "make" to configure the kernel search here :
- Device Drivers/ Networking support/PPP support: PPP sync & PPP async tty support;
- Device Drivers/ USB Support/ Support for Host-Side USB: USB Modem (CDC ACM) support;
If that wasn't enable on the kernel... YOU HAVE TO RECOMPILE IT .JAJAJAJAJA GOOD LUCK
Now, for bluetooth connection ONLY the ASYNC TTY support is needed (ei.. i'm supposing that you already have bluetooth active ..right ;) ). Ussually when you try co connect to internet the error that comes with it is "PPP negotiation failed" or something like that.
For USB serial, you have to have also USB serial support... that you have now... If you check DMESG should appear something like this:
"...usb 3-2: new full speed USB device using uhci_hcd and address 4
cdc_acm 3-2:1.8: ttyACM0: USB ACM device..."
Ok, next fase ... connecting...
For Nokia 6630 their's NO script to use with easyconnect
Quite easy ..search the net for "pppd call gprs" you will find several scripts to make a ppp call. The important ones are:
gprs
gprs-connect-chat
gprs-disconnect-chat
...All this files should go to /etc/ppp/peers/. Their are several pages on the internet that can show you how to configure this. Here i will put only my configuration:
Devices:
# Serial device to which the GPRS phone is connected:
# /dev/ttyS0 #for serial port (COM1 in Windows),
# /dev/ircomm0 #for IrDA,
/dev/rfcomm0 # Bluetooth serial port one
#/dev/ttyACM0 # USB serial device - Nokia 6630
NOTE: if you're using locally a 10.x.x.x network do the following change:
# IP addresses:
# - accept peers idea of our local address and set address peer as 10.0.0.1
# (any address would do, since IPCP gives 0.0.0.0 to it)
# - if you use the 10. network at home or something and pppd rejects it,
# change the address to something else
:20.0.0.2 (i changed from :10.0.0.1)
...and that's it ... you're ready to surf...
In bluetooth just dor /etc/init.d/bluez-utils restart (to BIND the phone)...or, RFCOMM bind 0 HWaddr. With the cable sutff it in the USB port and check that kernel recognized the phone ...
Do, pppd call gprs and wait untill the connection is established and voila ..
Starting this ...
Hi people,
It's time to start contributing to the Linux community. After two years of search and learning, i think i can now help/assist others with my achievments.
FINGERS CROSSED .....
P.S. - One "out of topic" subject... God help us all with this terrorism war ...
It's time to start contributing to the Linux community. After two years of search and learning, i think i can now help/assist others with my achievments.
FINGERS CROSSED .....
P.S. - One "out of topic" subject... God help us all with this terrorism war ...