IBurst pcmcia and Linux (suse 9.1 and 9.2 )

T

thezonk

New Member
Joined
Mar 24, 2005
Messages
2
Reaction score
0
I am still green behind the ears with iBurst and wireless.

I have been given a PCMCIA iBurst card and would like to know how to get it working in Linux.
Any one prepared to assist. Please?


:o
 
thezonk said:
I am still green behind the ears with iBurst and wireless.

I have been given a PCMCIA iBurst card and would like to know how to get it working in Linux.
Any one prepared to assist. Please?


:o
Click to expand...

I am not sure on the version numbers of the Kernel in Suse 9.1 & 9.2
I have the drivers that are supposed to work with a 2.4.xx kernel. If you want , send me an email addy and I will forward them on to you.
 
heh they use 2.6 by default, you could get a diff version though
 
An iBurst PCMCIA driver for linux 2.6 kernels now exists. A number of folk in Australia have succeeded in porting the existing open source driver from ArrayCom to the 2.6 kernel. The current status is pre-release, in that it works without obvious errors (I'm using it at the moment), but is *not* thoroughly tested.

If anyone would like to test it, then we would value your feedback. If you are just impatient, and want to get going on 2.6, then feel free to use it right away. If you prefer to wait until any initial kinks have been ironed out, then watch this space.

pre-release 2.6 drivers available from here:

http://nik.homelinux.net/files/ibut-3.10a0.tz

There is a README file that explains the installation procedures.

Cheers - and enjoy!
Nik
 
Ah, this is brilliant! I've been meaning to try get iburst working under suse 9.2. I'll try out the drivers and give you my feedback. Thanks Nik and zonk for bring up this topic.
 
Just tried the drivers under mandrake 10.1 and it doesnt seem to work. Also a newbie to linux, but followed the commands in the readme file with no luck. Unless the driver is ment for fedora core 2 & 3. Would appreciate some help. It fails on the make, something to do with build.
 
You folks here are awesome! Thanks for the quick feedback.

Sadly, there have been some changes between 2.6.9 (Fedora Core 3) and 2.6.11 (the newer Mandrakes), so my apologies for the problems - however this is how they are found and fixed.

With the help of a Mandrake user, I have fixed the compilation problem. He hasn't actually run the driver yet (as far as I know), so I'm still waiting on feedback on whether this is the extent of the differences.

For anyone who wishes to try it, the new file is at:

http://nik.homelinux.net/files/ibut-3.10a3.tz

> Unless the driver is ment for fedora core 2 & 3.

No, the driver is meant for as many 2.6 kernels as possible. However, it was developed and tested on Fedora Core 3.

Cheers!
Nik
 
Last edited by a moderator:
Thanks, but for some reason I cant download the file, says file not found, error 403 forbidden error. any way that u can mail it to me ?
 
ye the link does not work, I am very interested to give these drivers a shot, im sure you have my mail address, mail it for me please.

Dylan
 
I'm sorry - I'm lost folks. I checked the link before I posted, and in the infamous words of the programmer "it works on my computer"... I have just checked again, and I can still download the file.

WitWolf, I would be interested in knowing the name of the web server that gave you the 403 message. I'm wondering if there is a proxy in the way that is causing the trouble. The other possibility is that your browser is trying to unpack the download rather than just downloading it, although that shouldn't give you a 403 error. You could try right-clicking on the link, and selecting the option that says something like "save link as".

The file is only 66kB, so I can easily email it to a few people.
WitWolf, sihen, I have clicked on your handles, but your email links are not activaed. If you send me mail to the following temporary address, I will reply with the driver.

[email protected]

Cheers!
Nik.
 
The requested URL /files/ibut-3.10a3 was not found on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.40 Server at nik.homelinux.net Port 80
 
Luke7777 said:
The requested URL /files/ibut-3.10a3 was not found on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.40 Server at nik.homelinux.net Port 80
Click to expand...
Thats funny, I've never had a problem downloading the file. I just downloaded it a again with no hassles.

Last night (early this morning actually) I tried to get this working. Everything went pretty well but I got stuck with setting up the pppoe link. I compiled and installed the driver using make; make install; no hassles there. I edited my /etc/modprobe.conf and /etc/pcmcia/config. I then rebooted (sorry, windows background - whats the proper way again) and it looked like the drivers worked because the little lights started flickering and eventually settled down as blue and green just like they would on windows. So far so good.

Now at step 7 of the rtf I get a bit stuck. I don't think I have either of the pppoe dialler packages mentioned in the rtf installed on my system so I went into Yast and tried to setup a dsl connection. This didn't show the iburst modem as an option for the ethernet interface but there was a little pcmcia tick box. I ticked that on and filled in everything else but that just didn't seem to work. When I tried dialling with kinternet (think its called that) it wouldn't connect.

I'm fairly sure I did something wrong with setting up the connection but I'm not sure what. I'm going to download the roaring penquin dialer and give that a bash. If someone can get it setup using Yast then please post a howto for me. Thanks!
 
Last edited:
I'm connected!

Okay, got it working! I'm posting this from Suse 9.2 on my laptop :cool:

I downloaded the roaring penguin package and installed and configured it. I had one or two hiccups but nothing major. At first I managed to connect but still couldn't access anything. Apparently Linux was trying to use my eth0 connection for the internet cos after I disabled that (ifdown eth0) and reconnected it worked fine. Big kudos to iNik! You da man :D

My kernel is 2.6.8 if I'm not mistaken and its a pretty stock standard Suse 9.2 install. My laptop is an Acer 1362LC but that shouldn't matter cos its pcmcia.
 
> Last night (early this morning actually) I tried to get this working.
[...]
> I then rebooted (sorry, windows background - whats the proper way again)

On linux, with dynamic modules (which this is) you just insert the card. No reboot, no restart. :o)

> If someone can get it setup using Yast then please post a howto for me. Thanks!

I'll have a look as Yast for you.

> Okay, got it working! I'm posting this from Suse 9.2 on my laptop

Woo-hoo! Way to go! :o)

> Apparently Linux was trying to use my eth0 connection for the internet

Hmm, sounds like your PPPoE hasn't been configured to set a default route (which is the one that sends data to the internet). If you are up to editing system files, look in /etc/sysconfig/network-scripts/ifcfg-ppp0 (or .../ifcfg-pppx if you configured your PPP to be something other than ppp0). Make sure you have the following two lines in the file:

DEFROUTE=yes
PEERDNS=yes

The first one tells PPP to create a default route (to the internet) using the ppp interface. The second tells PPP to set your DNS entry to use your iBurst ISP's DNS server (which I assume you have set, since it worked once you dropped the eth0 interface).

The other possibility is that eth0 is being started *after* ppp0, but I would not expect that to be the case.

> And you'll need the roaring-penguin pppoe client as well:

Only on those distros that don't ship it by default. I know Fedora Core ships it, so you might want to check if it's installed before installing it again. :o)

I'm glad to see it's working for people!

Cheers!
Nik.
 
Hi Nik

Thanks for all the tips and help!

Nik said:
If you are up to editing system files, look in /etc/sysconfig/network-scripts/ifcfg-ppp0 (or .../ifcfg-pppx if you configured your PPP to be something other than ppp0).
Click to expand...
I had a look in /etc/sysconfig/network/ and there aren't any files that look like ifcfg-ppp0. There's a couple of others but none of them look they're for the iburst connection. Its not a problem though because I don't need my LAN connection at the moment. Some time later I'll see if I can setup my laptop as the internet gateway so I can connect my other box to the net through it.
 
One more question...

Is it ok to just unplug the pcmcia card at any time? You don't have to stop it first in case you damage it or something? This is my first pcmcia card so I'm just checking :)
 
Well It looks like my luck is it still ! :-( Managed to get the file to download late last night, but still doesnt want to install on to mandrake 10.1. Will post the exact error a bit later give a bit of a better idea of what it error is.
 
> I had a look in /etc/sysconfig/network/ and there aren't any files that look like ifcfg-ppp0.

Firstly, is the directory name that you tried "network" or "network-scripts"? On my system, there is a "networking" directory *and* a "network-scripts" directory.
Secondly, the interface files may be in a different place on your system. Try "find /etc/ -name "*ppp0*", and see what that turns up.

Alternatively, you can try the GUI configuration programs. On my system, I use KDE, so under the "System Settings" menu, I can select "Network". I get asked for the root password, and then I get a list of configured interfaces. If I double-click on "ppp0", I get a set of tabs. Under the "Advaned" tab, there is a check-box labelled "Make this connection the default route". This box should be checked. If it already is, then we have a different problem to solve...

> Is it ok to just unplug the pcmcia card at any time?

To the best of my knowledge, you can just eject the card. The PCMCIA standard was designed to support this (it's called "hot-plugging"). I certainly eject and re-insert the card regularly, However, I cannot guarantee that it won't damage your device. I would recommend that you stop any network connection using it first, though. So "adsl-stop" would be a good idea. :o)

There is a control command, "cardctl" which lets you control PCMCIA cards, so if you want to be really careful, you could do:

$ cardctl status
to find out which card(s) are currently active, then:

$ cardctl eject x
which tells the PCMCIA system to disconnect the card in socket x (typically 0 or 1), and prepare it to be physically ejected.

However, I am quite sure that this is basically a diagnostic tool, and is not required for regular use.

WitWolf. I'll keep a lookout for your error report. We want you online as soon as possible.

Cheers!
Nik.
 
Nik, thanks again for the feedback. I'll have a look at it a bit later again and get back to you with the results.

Where abouts are you from and are you the developer that put ported the drivers to the 2.6 kernel?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X