Problem setting up iBurst USB-terminal on SuSE 9.3

Good day all!
I've got the ibdriver-1.2.8 iBurst driver for Linux from Sourceforge and it compiled without any problems.
The problem that I do have is after following the instructions, and I plug in my iBurst terminal into the USB port the messages log returns the following:

Mar 25 23:26:54 SLinux ifup: Interface ib0 is not available
Mar 25 23:29:52 SLinux kernel: iburst: probe of 1-1:1.0 failed with error -110
Mar 25 23:29:52 SLinux kernel: usb 1-1: USB disconnect, address 3
Mar 25 23:29:55 SLinux kernel: usb 1-1: new full speed USB device using uhci_hcd and address 4
Mar 25 23:29:55 SLinux kernel: uhci_hcd 0000:00:1f.2: host system error, PCI problems?
Mar 25 23:29:55 SLinux kernel: uhci_hcd 0000:00:1f.2: host controller halted, very bad!


I have an old Pentium 3 running as my Linux Server with SuSE 9.3 .
Its running with the 2.6.11.4-20a kernel that came with SuSE 9.3 .
I want this PC to act as a router for our little LAN at home to go on the internet.

Any suggestions to this problem?

Thank you!

I have posted patches to the SourceForge iBurst driver project pages that should address this problem. I the forum prevents me from posting URLs to assist you. If you need more assistance please let me know. I would be interested to hear if the patches work for you or not.

Thanks a lot man!
I have recently upgraded to SuSE 10.0!
I will definately give it a shot.
Don't worry I got to the link that you have posted on sourceforge.
http://sourceforge.net/tracker/index...84&atid=742190

The strange thing though (with the current version), if I go into single user mode of Linux and I compile the driver then I can connect/disconnect the terminal (not on the internet yet) and it detects it without a problem (since I started using SuSE 10) but I didn't have the time to finish the installation but if I go into Linux normally with the Xserver running, etc. then when I have the terminal in or plug it in and call the 'lsusb' then it returns nothing. Linux says that its because there is a problem with the usb setup or something.
I really hope that your patch will fix it!

Its great that patch fixed the host controller.
Now I can plug my terminal in and pull it out whenever I want to but there is just 1 more problem.
The interface controller doesn't have a configuration file.
Like eth0, eth1 (which my machine picks it up as) can get loaded but it can't finish because it doesn't have that config file.
I reckon that I need such a file in /etc/sysconfig/network but how do I manually create one if needed?

Thanks

Thanks for the feedback. Give me a day or so, to fire up my SuSE installation to figure out what you need. Depending upon how urgently you want to get this working you might try Ubuntu, Ubuntu (Breezy) is what I'm working on currently.

I will provide the workings for SuSE shortly, if you can wait.

I tried the "sudo ifconfig ib-nas up" stuff you gave me, only I can't use "ib-nas" but I tried eth1 and that worked.
Also how can you use ifconfig to generate a configuration file for /etc/sysconfig/network ?
I made one manually but apparently it doesn't work.
I'm looking forward to hear from you coaic!

May the Lord Bless you!

Cheers

Sorry I just don't know how to get to configure devices.
I still have some time to wait...

The following is a very basic setup for SuSE, it doesn't take into account the full autoconfig capabilities of SuSE but should get you going with a single iBurst UT:

1. Follow the instructions per the README from the iBurst source

Then modify with the following steps:

2. Create a file /etc/modprobe.d/iburst.modeprobe with the following lines in it:

options ib-net ifname="eth" debug=9
options ib-pcmcia interval=100


3. sudo cp /etc/sysconfig/network/ifcfg.template /etc/sysconfig/network/ifcfg-eth?

Where ? is the interface number of the iBurst UT (USB or PCMCIA)

4. In the file created in step 3, set the following variables:
STARTMODE=hotplug
IPADDR='10.0.99.1'
NETMASK='255.255.255.0'
MTU='1492'
NAME='iBurst User Terminal'
USERCONTROL='yes'

5. Open YaST from the SuSE menu in KDE and select Network Devices->Network Card to confirm the iBurst card appears in the configuration.

6. From within YaST select Network Devices->DSL and configure the eth? interface corresponding to the iBurst UT as DSL service (you will need your username@realm and password to configure the provider).

7. You should then be able to initiate a connection using Kinternet which appears as a plug icon in the panel at the bottom right portion of you screen/desktop.

I need do do more investigation to see if this procedure can be more generalised. If you or anybody else can provide slightly less cryptic descriptions than the man page on getcfg, I will try and incorporate those suggestions.

Cheers, Shane

I'm just wondering, I'm having trouble getting KInternet to connect but I'm starting over with the hope to get it right this time, what else should be configured?
Like should I set the routing info, dns, etc?

Thanks for your help, it was a lot. I got it once to connect on the internet but it didn't want to surf the web. When I went to google, my browser just said : "Connecting ..."

Could you please post the contents of /var/log/messages while you are trying to initiate the connection, there may be a clue there. Plus the output of ifconfig -a.

Ok, I have the following in /var/log/messages. This is what I received for 5 minutes before I closed the file:

Apr 25 10:25:25 SLinux pppd[5502]: Plugin rp-pppoe.so loaded.
Apr 25 10:25:25 SLinux kernel: CSLIP: code copyright 1989 Regents of the University of California
Apr 25 10:25:25 SLinux kernel: PPP generic driver version 2.4.2
Apr 25 10:25:25 SLinux pppd[5502]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
Apr 25 10:25:25 SLinux pppd[5502]: Plugin passwordfd.so loaded.
Apr 25 10:25:25 SLinux kernel: NET: Registered protocol family 17
Apr 25 10:25:25 SLinux pppd[5502]: pppd 2.4.3 started by root, uid 0
Apr 25 10:25:25 SLinux pppd[5502]: Renamed interface ppp0 to dsl0
Apr 25 10:25:25 SLinux pppd[5502]: Using interface dsl0
Apr 25 10:25:25 SLinux pppd[5502]: Couldn't increase MTU to 1500
Apr 25 10:25:25 SLinux pppd[5502]: Couldn't increase MRU to 1500
Apr 25 10:25:25 SLinux pppd[5502]: local  IP address 192.168.99.1
Apr 25 10:25:25 SLinux pppd[5502]: remote IP address 192.168.99.99
Apr 25 10:27:45 SLinux nmbd[4634]: [2006/04/25 10:27:45, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Apr 25 10:27:45 SLinux nmbd[4634]:   *****
Apr 25 10:27:45 SLinux nmbd[4634]:
Apr 25 10:27:45 SLinux nmbd[4634]:   Samba name server LSERVER is now a local master browser for workgroup WORKGROUP on subnet 10.0.99.1
Apr 25 10:27:45 SLinux nmbd[4634]:
Apr 25 10:27:45 SLinux nmbd[4634]:   *****

And this is what I have received in ifconfig -a, I even have an extra device!

eth0      Link encap:Ethernet  HWaddr 00:D0:B7:85:42:71
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:b7ff:fe85:4271/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15554 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37572 errors:0 dropped:0 overruns:0 carrier:0
          collisions:12943 txqueuelen:1000
          RX bytes:1070761 (1.0 Mb)  TX bytes:49753046 (47.4 Mb)

eth1      Link encap:Ethernet  HWaddr 00:C0:EE:C3:69:A8
          inet addr:10.0.99.1  Bcast:10.0.99.255  Mask:255.255.255.0
          inet6 addr: fe80::2c0:eeff:fec3:69a8/64 Scope:Link
          UP BROADCAST RUNNING NOARP DYNAMIC  MTU:1492  Metric:1
          RX packets:5325 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5404 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:42600 (41.6 Kb)  TX bytes:51562 (50.3 Kb)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20852 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9568347 (9.1 Mb)  TX bytes:9568347 (9.1 Mb)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Its weird! But I really don't connect at all.

Looking at log output the line that says:
"Renamed interface ppp0 to dsl0"

Leads me to believe you haven't associated eth1 with dsl0. If you look in /etc/sysconfig/network/providers you should see something like:

. .. provider0 provider1 ... providern

One of these provider files should contain something like the following:

KPASSWORD='no'
AUTODNS='yes'
DEMAND='no'
DSLSUPPORTED='yes'
IDLETIME='300'
ISDNSUPPORTED='no'
MODEMSUPPORTED='no'
MODIFYDNS='yes'
PASSWORD=<your password>
PHONE=''
PROVIDER=<your iBurst provider name>
USERNAME=<your iBurst user @ realm>

Now if you look in /etc/sysconfig/network you should have at least two files:

ifcfg-eth1
ifcfg-dsl0

The output from ifconfig -a confirms that ifcfg-eth1 exists.

If you examine ifcfg-dsl0 it should contain something like the following:

BOOTPROTO='none'
DEVICE='eth1'
MODEM_IP=<Ip Address in format n.n.n.n>
NAME='DSL Connection'
PPPD_OPTIONS=''
PPPMODE='pppoe'
PROVIDER=<Provider file name corresponding to provider file examined above>
STARTMODE='manual'
UNIQUE=''
USERCONTROL='yes'
VPIVCI=''

The linkage here is the DEVICE='eth1'

You can establish the creation of this file <dsl0> by doing the following:

1. Open YaST

2. Select Network Devices from the left panel

3. Click on the DSL icon

4. If the DSL Configuration shows no configured devices then click in the Configure... button in the top panel; Otherwise click on the Change... button on the bottom panel.

5. In the DSL Devices <top panel> add/edit the DSL device

6. Set PPP Mode to PPP over Ethernet

7. Select eth1 as the Ethernet Card

8. Select Device Activation Manual

9. Check User Controlled and finish.

As you are in South Africa, you should step through the creation of a custom provider in the bottom panel of the DSL Configuration Overview screen.

You then need to make sure Kinternet uses the correct connection, to this:

1. Right click on the Kinternet plug icon

2. Ensure interface is set to dsl0.

3. Provider is set to the name you have given to your iBurst provider.

Once you've done this hopefully you should be able to connect. You should see log entries something like the following:

swlaptop2 pppd[22466]: Plugin rp-pppoe.so loaded.
swlaptop2 kernel: CSLIP: code copyright 1989 Regents of the University of California
swlaptop2 kernel: PPP generic driver version 2.4.2
swlaptop2 pppd[22466]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
swlaptop2 pppd[22466]: Plugin passwordfd.so loaded.
swlaptop2 pppd[22466]: pppd 2.4.3 started by root, uid 0
swlaptop2 pppd[22466]: Interface eth1 has MTU of 1462 -- should be 1500. You may have serious connection problems.
swlaptop2 pppd[22466]: PPP session is 34
swlaptop2 kernel: NET: Registered protocol family 24
swlaptop2 pppd[22466]: Renamed interface ppp0 to dsl0
swlaptop2 pppd[22466]: Using interface dsl0
swlaptop2 pppd[22466]: Connect: dsl0 <--> eth1
swlaptop2 pppd[22466]: Couldn't increase MTU to 1500
swlaptop2 pppd[22466]: Couldn't increase MRU to 1500
swlaptop2 pppd[22466]: CHAP authentication succeeded
swlaptop2 pppd[22466]: peer from calling number 00:C0:EE:0E:00:37 authorized
swlaptop2 pppd[22466]: replacing old default route to eth0 [172.17.200.1]
swlaptop2 pppd[22466]: local IP address 172.17.64.188
swlaptop2 pppd[22466]: remote IP address 10.1.1.1
swlaptop2 pppd[22466]: primary DNS address 172.24.144.63
swlaptop2 pppd[22466]: secondary DNS address 172.17.48.11
swlaptop2 modify_resolvconf: Service pppd modified /etc/resolv.conf. See info block in this fi

Hey man thanks alot!
I am now posting from my machine in Linux with the iBurst terminal directly connected to it.

I just had to add the gateway and DNSs found by KInternet to the routing and domain name searches and BOOM! It worked!

Now my next challenge would be to connect to the internet without using VNC on this machine to use KInternet to connect. He he, part of a project for university.

Again I say thanks to you, you have been a GREAT help!

God Bless!

Hey coaic!
I discovered that when I disconnect and reconnect a few times, the device refuses to connect after 3 or 4 times (I think). I don't do it directly afterwards, but after successive internet browsing. Then I have to reboot the machine before it works again.

Just thoaght I meantioned it.

BTW. does anyone maybe know how to restart the hotplug in SuSE 10.0? I looked for anything like hotplug but found nothing.

Are you having the problem on SuSE 9.3 or SuSE 10.0?

Also could you please post a transcript of /var/log/messages when you get the failure to connect?