stiginge,
Since you were able to get me a pmodemdiag file, I gather you figured out what I meant by "new pupsave". My intent with that is that there be no residue from other activities that might confound the diagnosis.

I have concluded two things.

1. There is no driver module that claims to support your modem, which has the hardware ID of 05c6:ffff. That means either that the "ffff" is bogus, or that yours is just not yet added to the kernel, but might work if a module can be loaded for it. It shows "interface class" as "ff", which should mean that it is already in "modem" mode. Vodaphone has a workaround for module loading for some modems. I have added a uevent rule to do just that, in the attached test/debug package, in the file in /etc/udev/rules.d/. See if that causes module "option" to be loaded.

2. It appears you have a built-in HDA (sound card) modem, which should be detected as ttySL0. But that didn't happen. Since the firmware/init-script is in place, it should have found it and set ttySL0. I suspect something wrong in that script (/etc/init.d/slmodem and 2 links to it). In the attached package, I have a version of it that should tell us where the problem might be (by logging to /tmp/bootsysinit.log). That should be tested with the USB modem unplugged, or if that modem is still not detected. (I suspect there might be an issue with the "ps aux" command, which may have changed with the newer kernels. Just a hunch.)

So, we have two chances to get some new info from the debug package. I assume you are now running quirky 1.2 with the "-5" and "-7" packages above. Install this new package on top of that setup. Thanks.
Richard

stiginge, Toy4,
Oops, I left out some things from my cleanup of the modprobe-workaround business for Vodaphones and usbserial-related module loading. The attached debug package attempts to fix things and adds more debug messages to help me get it right.

Toy4, your diag file shows that the driver got loaded eventually, but it also does not show your attempt to dial up and connect. So I cannot analyze the connect issue. I hope the debug messages will explain some things. Like why the modem is not detected at boot-up -- assuming it is plugged in at that time..

Both, please install the attached package after installing all the previous packages. But the previous debug package, stiginge-test2, can be uninstalled BEFORE installing this new package, although uninstalling would be only to keep things neat.

Eagerly awaiting the diag files from your efforts. Thanks.
Richard

UPDATE 7/26/2010: Uploaded "-3", to maybe fix bugs in detection and in loading of driver following mode-switch. Also patches triggering of modeswitch in puppeee.

UPDATE 8/2/2010: Uploaded "-4" for use with the 7.2 updates, which include fixes in "-3".

OK, I have installed the file you requested and restarted the machine with the modem in and it isn't finding it. Tried the probe and it says it isn't there. Tried pulling the modem and replacing it and still nothing. Did that numerous times and still won't find the modem. Attaching diagnostic file.

Might just be having a bad day. Let me know what you find if anything and what steps to take next. Thanks........

Toy4,
Now that I have been able to get to your diag file (after a busy weekend), I see that ttyUSB0 eventually got placed in the wvdial.conf file, implying that the probe found it. It looks like it took many tries to get to that point. However, I also see that you did not actually install my latest debug package.

Although they do no harm. the following packages are no longer needed, but DO NOT uninstall them:
- pmodemdiag-1.0
- modem_fix_pack_delta-7-to-7.1 (since it is already part of modem_fix_pack_delta-6-to-7.1)
I mention this only so that others can leave them out.

Quote:

Did that numerous times and still won't find the modem.

It appears that the last time might have worked. But know that when you replug it, you then have to probe it again. Automatic detection operates only during boot-up. But probing should accomplish the same thing.

When your modem is recognized and its mode switched to "modem" (without the need for the mode-switch utility, BTW), probing should find it. Just be sure to wait a minute or two between plugging and probing, to give the device time to respond.

Other things: I see no evidence that you actually probed the device. Be sure to click on the "CHOOSE" (formerly "probe") button, then on the "PROBE" button on the next popup. I expect to see two log files, which are missing. They may get deleted when you exit Pupdial, so get the diag while pupdial is still up.

Also, when you make the diag file, please have the modem plugged in at the time. The list of USB devices (pupscan) looks strange, which is why I need to be sure it was plugged in.

It still doesn't look like it did anything. Well, at least the proper files are now in place so we are going in the right direction again. Sorry for taking that step backwardd. I have attached another diag file and I left Pupscan open while I created it. I hope I did that in the correct sequence. Here goes......

Oh, It appears RC8 is available for update. If I update to RC8 will that screw up anything that has been loaded previously.

If I update to RC8 will that screw up anything that has been loaded previously.

I believe jemimah has brought RC8 up to the 7.1 level. So, on a fresh installation/pupsave with RC8, just install the latest debug package, modem_7.1_debug-2.pet. Don't use your current pupsave, at least for these tests.
Richard

This one looks like something good happened and you may get some good info out of this file It didn't connect but it it tried and we maybe a lot closer to a good result. Let me know what you think. Thanks for your assistance.

Toy4,
I have updated, again, the debug package, to "-3". The mode switching is not being triggered. I suspect that puppeee RC7 does not have the latest usb_modeswitch packages. I will recommend that jemimah add them to the next RC, but I am out of time right now. Please uninstall "-2" and install "-3". The new package has a workaround for the missing modeswitch upgrade.
Richard

Toy4,
Thanks for the diag file. It looks like everything worked as it should! As far as you went. If you intend to connect to the internet through the modem, you need to provide a "phone number", user ID and password -- often the ID and passwords are just fakes, because the provider does not require any, but the dialer requires something in those fields. The phone number is usually *99# or *99***1#.

When I sent that diag file last night my NetBook was already updated to RC8 (3rd Diag file).

I just tried what you suggested and used the real phone number and Toy4 as the username and a word for the password. It didn't work. OK, before I continue please make sure I am on the right path. I have done another diag file from after my latest attempt. Here it is: