MW - IPW Linux Driver and Distro

M

midasza

Well-Known Member
Joined
Jun 9, 2004
Messages
445
Reaction score
248
Location
.
Any suggestions as to what distro works best with the Mywireless USB Linux drivers?

Currently I have a system running Mandrake 10 and I am struggling to get PPP to connect and I was wondering if another distro may be more MW friendly?

thanks
Evan
 
do your self a big favor get the pppoe cable problem solved :)

i use my own linux build to run it and it works fine ...
 
Basically any 2.6 kernel based distro will do the job.

I have run into kernel oopses quite a few times if the tower dissapears. The connection drops,the modem seems to do some sort of reset. At that point rodent's USB goes ***a and everything hangs ... not had time to debug this yet....

but all in all Rodent's USB driver works gretty dang well. I've gotten it to talk to 3 modems at the same time on one box ;-)
 
Well I was having a problem on Mandrake 10 - but it was a pppd problem and not a IPW driver problem. What distro did you use regardtv?
 
Heya. 2.6.6-1 I think it's something obscure on the usb controller of the box I'm using... It's like the whole USB hub dissapears ... Don't have access to the unit at the moment - put in an ethernet cable for the unit and shipped it off.

Will try get access again or re-create the situation and pass any data on to you.
 
hi there just implemented the ipw into "cannonball linux" and have got a few oopses ill try reproduce them and get back to you ...

it has todo with the modem reconnecting what i can make out so far ...

kernel 2.6.8.1 (yes this is a official release - nfs patch to 2.6.8) with a sched API patch

drivers added
dazuko
acx100 802.11
atheros 802.11
ipw

devfs is in use ...

prehaps you can let me know what the optimum MTU/MRU is im useing 1492 with no problems so far ...
 
ok the MTU was not working 100% at 1492 many sites worked and could even send a 1492 ping packet ... so can someone explain this ??

my theory is the MTU is fine at 1492 but due to sentech not allowing path mtu discovery some [very few] sites ... require a lower MTU ...

the way i tell if MTU is correct is to ping with a packet size equal to the MTU [i dissallow all fragmented ICMP] and also check SSL sites as they are fussy about MTU ...

setting it to 1450 has done the trick ...
 
ta thx rodent ps the koops seem to be related to pppd not cleaning up properly and freeing the tty i aint worked on tty drivers since kernel 2.0 so not sure how to check for this in the driver ... been more parranoid about starting/restarting pppd has done the trick for now ...

its working great the only reason i aint used it till now is my GW did not have USB ...

you would not know how to obtain tower/... info from the device with a a chat script would you ??
 
thx a stack ive added it to the chat script so it now gets logged on every connect ...

grep -E "(\+CSQ:)|(\+CGATT:)" /var/log/messages
Aug 23 11:40:45 firewall chat[11858]: +CSQ: 13,99,-96,-98,3^M
Aug 23 11:40:45 firewall chat[11858]: +CGATT: 2530000, 7.68Mcps, 15, 60^M
Aug 23 11:47:40 firewall chat[14041]: +CSQ: 10,99,-95,-98,2^M
Aug 23 11:47:41 firewall chat[14041]: +CGATT: 2530000, 7.68Mcps, 15, 60^M

sending this through sed gives me a nice little web interface

Freq. Speed <Unknown> Tower: 2530000, 7.68Mcps, 15, 60
Model ID: Phase 1(c)
Firmware Version: 4.2.1.1 / A1 (2.0) / A2 (2.0); 4.2.1.1
IMEI Number: 351152000140790
SP Status Code Name: 1,2,"00000"
Signal Strength % RSCP ISCP: 10,99,-95,-98,2
Signal Strength % RSCP ISCP: 13,99,-96,-98,3
Signal Strength % RSCP ISCP: 17,99,-92,-98,4
 
You may want to look at moving to 4.2.1.8 -- reduces packet loss slightly.

But at this stage of the game I'd recommend you wait for the new v5 firmware ... IF/WHEN it gets released.


<hr noshade size="1"><font size="1"><div align="right">8:00 Thursday 26 August 2004 is <font color="red">D-Day</font id="red">....
<s> 16 17 18 19 20 <font color="green">21 22</font id="green"></s> 23 24 25 <font color="red"><b>26</b></font id="red">
</div id="right"></font id="size1">
 
i have not bothered yet waiting for v5 that ****er murphy is not my friend ...
 
Rodent Sentech Mywireless driver works on SuSE 9.1 but not 9.3

I've been trying to get the Rodent Sentech Mywireless driver working on the newer distros without any luck. It worked fine on SuSE 9.1 (after disabling the firewall), but on SuSE 9.3 and Ubuntu Hoary Hedgehog I've had no luck. On Ubuntu I also had to download the kernel source (2.6.10) from kernel.org, which took me a month or something to figure out.

The pppd debug call sentech command immediately comes back with an abort. Below is my /var/log/messages.

Help would be greatly appreciated.

Jul 3 23:22:07 localhost kernel: [__wake_up+33/68] __wake_up+0x21/0x44
Jul 3 23:22:07 localhost kernel: [tty_release+14/23] tty_release+0xe/0x17
Jul 3 23:22:07 localhost kernel: [__fput+65/248] __fput+0x41/0xf8
Jul 3 23:22:07 localhost kernel: [filp_close+90/99] filp_close+0x5a/0x63
Jul 3 23:22:07 localhost kernel: [sys_close+88/122] sys_close+0x58/0x7a
Jul 3 23:22:07 localhost kernel: [sysenter_past_esp+82/117] sysenter_past_esp+ 0x52/0x75
Jul 3 23:22:17 localhost chat[12162]: timeout set to 30 seconds
Jul 3 23:22:17 localhost chat[12162]: abort on (NO CARRIER)
Jul 3 23:22:17 localhost chat[12162]: abort on (BUSY)
Jul 3 23:22:17 localhost chat[12162]: send (^MAT^M)




Jul 3 20:25:03 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for IPWireless converter
Jul 3 20:25:03 localhost kernel: ipwtty 2-1:1.0: IPWireless converter converter detected
Jul 3 20:25:03 localhost kernel: usb 2-1: IPWireless converter converter now attached to ttyUSB0
Jul 3 20:25:03 localhost kernel: usbcore: registered new driver ipwtty
Jul 3 20:25:03 localhost kernel: drivers/usb/serial/ipw.c: IPWireless tty driver v0.3
Jul 3 22:00:42 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for IPWireless converter
Jul 3 22:00:42 localhost kernel: ipwtty 2-1:1.0: IPWireless converter converter detected
Jul 3 22:00:42 localhost kernel: usb 2-1: IPWireless converter converter now attached to ttyUSB0
Jul 3 22:00:42 localhost kernel: usbcore: registered new driver ipwtty
Jul 3 22:00:42 localhost kernel: drivers/usb/serial/ipw.c: IPWireless tty driver v0.3
Jul 3 22:30:41 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for IPWireless converter
Jul 3 22:30:41 localhost kernel: ipwtty 2-1:1.0: IPWireless converter converter detected
Jul 3 22:30:41 localhost kernel: usb 2-1: IPWireless converter converter now attached to ttyUSB0
Jul 3 22:30:41 localhost kernel: usbcore: registered new driver ipwtty
Jul 3 22:30:41 localhost kernel: drivers/usb/serial/ipw.c: IPWireless tty driver v0.3
Jul 3 23:23:32 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for IPWireless converter
Jul 3 23:23:32 localhost kernel: ipwtty 2-1:1.0: IPWireless converter converter detected
Jul 3 23:23:32 localhost kernel: usb 2-1: IPWireless converter converter now attached to ttyUSB0
Jul 3 23:23:32 localhost kernel: usbcore: registered new driver ipwtty
Jul 3 23:23:32 localhost kernel: drivers/usb/serial/ipw.c: IPWireless tty driver v0.3
Jul 3 22:42:52 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for IPWireless converter
Jul 3 22:42:52 localhost kernel: ipwtty 2-1:1.0: IPWireless converter converter detected
Jul 3 22:42:52 localhost kernel: usb 2-1: IPWireless converter converter now attached to ttyUSB0
Jul 3 22:42:52 localhost kernel: usbcore: registered new driver ipwtty
Jul 3 22:42:52 localhost kernel: drivers/usb/serial/ipw.c: IPWireless tty driver v0.3
Jul 3 22:46:51 localhost kernel: drivers/usb/serial/ipw.c: USB IPWireless support registered
Jul 3 22:46:51 localhost kernel: drivers/usb/serial/ipw.c: USB IPWireless converter detected
Jul 3 22:46:51 localhost kernel: drivers/usb/serial/ipw.c: IPWireless converter now attached to ttyIPW0 (or usb/ttub/0 for devfs)
Jul 3 22:46:51 localhost kernel: usbcore: registered new driver ipwtty
Jul 3 22:46:51 localhost kernel: drivers/usb/serial/ipw.c: IPWireless tty driver v0.1
Jul 3 22:54:19 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:54:19 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
Jul 3 22:55:11 localhost pppd[8776]: Device ttyIPW0 is locked by pid 8752
Jul 3 22:55:21 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:55:21 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
Jul 3 22:55:51 localhost pppd[8752]: Device ttyIPW0 is locked by pid 8776
Jul 3 22:56:13 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:56:13 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
Jul 3 22:56:43 localhost pppd[8776]: Device ttyIPW0 is locked by pid 8752
Jul 3 22:56:46 localhost pppd[8824]: Device ttyIPW0 is locked by pid 8752
Jul 3 22:56:53 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:56:53 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
Jul 3 22:57:16 localhost pppd[8824]: Device ttyIPW0 is locked by pid 8776
Jul 3 22:57:23 localhost pppd[8752]: Device ttyIPW0 is locked by pid 8776
Jul 3 22:57:45 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:57:45 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
Jul 3 22:57:53 localhost pppd[8752]: Device ttyIPW0 is locked by pid 8824
Jul 3 22:58:15 localhost pppd[8776]: Device ttyIPW0 is locked by pid 8824
Jul 3 22:58:18 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:58:18 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
Jul 3 22:58:45 localhost pppd[8776]: Device ttyIPW0 is locked by pid 8752
Jul 3 22:58:48 localhost pppd[8824]: Device ttyIPW0 is locked by pid 8752
Jul 3 22:58:55 localhost kernel: [pg0+947586512/1069929472] ipw_close+0x1c0/0x1f9 [ipw]
Jul 3 22:58:55 localhost kernel: [pg0+947586523/1069929472] ipw_close+0x1cb/0x1f9 [ipw]
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X