Sorry, sorry, sorry. Good news and bad news. Last night I got home after a quite bad day and my mind wasn't so clear.
I decided to test it again this morning and suddenly remembered that, in order to use my my old hardy wvdial.conf, I disabled pin request and did the same in Broadband GUI configuration so that I could test without having to resort to my cell to switch pin on/off all the time. Unfortunately I did re-enabled it to use it in Intrepid and last night I forgot Jaunty was doing without. Back to business: 1. The modified 77-nm-probe-modem-capabilities.rules does not work and does not list any Broadband connection. 2. The old one does. Now it shows two identical connections as it did when it was still working and after a session log-out/log-in or an extraction/insertion of the modem stick and when, then, only the second listed was working. Now the first one appears as using /dev/ttyUSB2 while the second listed uses /dev/ttyUSB0. This time the second does not work, but the first one does. 3. Though the good new are "it works", the bad news are: It does not disconnect and to do so I have to halt the system. 4. Attached is the latest syslog that to you surely speaks louder than my explanations. ** Attachment added: "syslog_260309_091157" http://launchpadlibrarian.net/24359036/syslog_260309_091157 -- MASTER - modems not detected - udev prober broken (Was: Huawei e169 doesn't connect + Globetrotter 3G+ card not recognized anymore) https://bugs.launchpad.net/bugs/346835 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
