Yes, wescht reported this same problem, but in his 4th post he solved it by having the modem plugged in while booting up ... which is contrary to the process he explained in his 1st post.
wescht also reports in his 4th post the importance of creating the file /etc/ppp/peers/wvdial

kattami wrote:

I am right now in the wvdial.conf file and put in phonenumber and also PIN code in dialer default and dialer pin ...

Just checking; the pin code should go under the "[Dialer pin]" section, to replace the default pin code "1234".
If this continues to be an issue, you could consider deactivating the pin under Windows, as wescht suggested.

Yes, wescht reported this same problem, but in his 4th post he solved it by having the modem plugged in while booting up ... which is contrary to the process he explained in his 1st post.
wescht also reports in his 4th post the importance of creating the file /etc/ppp/peers/wvdial

kattami wrote:

I am right now in the wvdial.conf file and put in phonenumber and also PIN code in dialer default and dialer pin ...

Just checking; the pin code should go under the "[Dialer pin]" section, to replace the default pin code "1234".
If this continues to be an issue, you could consider deactivating the pin under Windows, as wescht suggested.

But the thing is that I did boot up with the usb device plugged in the next morning, and got the same message.

I will look in Vista (ugh) if that program that comes up has any disable pin function. Didnt see that when I tried with XP on another laptop my father uses.

So it is obviously not doing anything with the ttyUSB0. Thats why its not finding the ttyUSB0 when I do the next step, using the wvdial.

I went to the site that has with this device to do and they recommend this site when its about getting the Option HSDPA Usb modems to work in Linux.

From what I can see I have either GT MAX 3.6 (7.2 Ready) or GlobeTrotter Express 7.2. I am not sure which of them I have because when it was working on the other laptop in winXP, it says speed 7.2 Mbps in the program for the mobile internet.

Anyway, they obviously use USB_modeswitch to get many of those devices to work.

I gave up trying to figure out this after several tries where I couldnt get the compiling to work in the puppylinux (puppylinux frugal installation plus devx sfs file and also full installation on the laptop). Didnt go further than that.

Now I am somewhere where I have only the cellphone modem to get online with (only with windows) and will not have a chance to get any other ways of internet access for some weeks. So no possibility to get puppylinux online in meantime.

But anyway I found that the cellphone modem I have is a GlobeSurfer Icon 7.2 and that the driver for it has no .inf file so I cant use Ndiswrapper either to get this to work. It has only one .sys file and Ndiswrapper didnt take it.

The simplest way is to reboot your computer (or reload the rules into udev and restart it). Do not have the iCON plugged in while booting,

When you computer is up and running again, plugg the iCON in.
Now list you USB devices:

Code:

# lsusb

Within 30 seconds you should have a device presenting it self as "Option"
Code:

Bus xxx Device xxx: ID 0af0:6901 Option

Now you should have three new nodes in /dev/

Code:

ls /dev/ttyUSB*
/dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2

Now your iCON should be working. I use kppp to connect. the only important things in kppp is the following:
The modem pointing at /dev/ttyUSB0 (could perhaps be 1 or 2 as well don't know the difference)
I use RTS/CTS as flowcontrol.
Deselect "wait for dial tone"
Add the connection, dial *99# and use PAP as authentication
Username and password should not matter."

************

So I am per today stuck at being not able to compile the icon_switch.c and therefore cant try this setup.

I dont have motivation or energy to start again with different installation of puppylinux to try to figure out how to get compiling to work after failing so many times last time.

So I post this just in case someone is looking for information how to get Globesurfer Icon 7.2 to work with puppylinux. First step would be to compile the icon_switch.c, or even better, usb_modeswitch.

After seeing that it begins to be more people asking about how to get puppylinux to work with the new usb-dongles, I decided to do a new try with the newest versions that I could find. I asked another one who had got his to work and he was so kind to reply to me. But unfortunately his setup didnt work for me. Thanks alot for the quick reply anyway

I also found a good guide in a norwegian forum and it was from that norwegian guide that I finally found the combination that works for my globesurfer in puppylinux.

7. Here I got unsure about what is what of the files so I put both the usb_modeswitch.c and usb_modeswitch file in /sbin and /urs/sbin. I just didnt bother figuring out which file it was about and where it should be. Up to the experts to point out this one.

8. Put the file usb_modeswitch.conf into /etc and edit with geany to the number your usb dongle uses. In my case with globesurfer icon 7.2, I changed to the text for globesurfer icon 7.2 (adding the ; where the first globesurfer model lines is and removing the ; where my globesurfer model is).

Then I installed the nozomi-2.21alpha-k2.6.21.7.pet. They said it was for puppylinux 3.x versions

"They" is me. You're referring to the nozomi driver dotpet package from here
http://www.murga-linux.com/puppy/viewtopic.php?p=163587#163587
The "k2.6.21.7" in the name of the dotpet tells you what kernel version the driver package is compatible with - so it's compatible with Puppy 3.x and 4.0 which both have the 2.6.21.7 kernel.
Sure it will install in Puppy 4.1.1, but it will be completely ineffectual, so clearly the "nozomi" driver is not necessary at all ... and this is confirmed by the nozomi compatibility list here -
http://www.pharscape.org/content/view/40/53/

kattami wrote:

expecting that I would have to edit the wvdial.conf

wvdial.conf is the configuration file for wvdial. But you're using gnome-ppp as your dialler application, not wvdial.

Then I installed the nozomi-2.21alpha-k2.6.21.7.pet. They said it was for puppylinux 3.x versions

"They" is me. You're referring to the nozomi driver dotpet package from here
http://www.murga-linux.com/puppy/viewtopic.php?p=163587#163587
The "k2.6.21.7" in the name of the dotpet tells you what kernel version the driver package is compatible with - so it's compatible with Puppy 3.x and 4.0 which both have the 2.6.21.7 kernel.
Sure it will install in Puppy 4.1.1, but it will be completely ineffectual, so clearly the "nozomi" driver is not necessary at all ... and this is confirmed by the nozomi compatibility list here -
http://www.pharscape.org/content/view/40/53/

kattami wrote:

expecting that I would have to edit the wvdial.conf

wvdial.conf is the configuration file for wvdial. But you're using gnome-ppp as your dialler application, not wvdial.

Yeah, I know it was you. I just didnt want to say something about a person, if you get me. Kinda anonymizing things, just to be respectful.

So you are telling me that it was not necessary to install the nozomi drivers?

Thats interesing. I didnt try the usb_modeswitch and gnome-ppp alone, because I tried to install once before only usb_modeswitch and then trying to modify the wvdial. That didnt work.

Next time I need to install this on new savefile I will remember to just use usb_modeswitch and gnome-ppp.

When its about gnome-ppp it says that it needs wvdial version 1.5 I think, and I saw in that norwegian guide that he had modified the wvdial.conf to point to telenor and other things that had with my country to do, hence I said I expected having to modify that file.

But in my case it connected with pppd after waiting abit so I didnt need to modify it at all.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum