Menu

#76 Could not write to device (anymore?)

found_in_0.8
closed-fixed
5
2009-01-26
2008-02-19
wolfi
No

After successful installation and testing, the next day (= after reboot) umtsmon does not work anymore.
On the commandline (umtsmon -v5) they asked me to post this output in a new bug report. Well, that's what I'm doing now ;-)
System is openSUSE 10.3 using a 2.6.22 kernel. The UMTS device is a Huawei E220 using base.de (Germany).

Discussion

  • wolfi

    wolfi - 2008-02-19

    output from command line

     
  • wolfi

    wolfi - 2008-02-21

    Logged In: YES
    user_id=2013846
    Originator: YES

    Originally I had installed umtsmon-0.7.91.20080212-1.1.i586.rpm
    As reported earlier, this worked 'only once'.
    Now I downloaded and installed umtsmon-0.7.91.20080212-3.1.i586.rpm - I am back online with no problems. Will check if it still works after reboot ...

     
  • wolfi

    wolfi - 2008-02-22

    Logged In: YES
    user_id=2013846
    Originator: YES

    Next retry ...
    It didn't work once, so I reinstalled the umtsmon package (this time the same version, using --force), after the next reboot it's working again. BTW I got all the necessary groups, at least I think so ;-)

    wolfi@linux-y89x:~> groups
    users tty disk uucp dialout video

     
  • wolfi

    wolfi - 2008-02-22
    • summary: Could not connect to device (anymore?) --> Could not write to device (anymore?)
     
  • wolfi

    wolfi - 2008-02-29

    Logged In: YES
    user_id=2013846
    Originator: YES

    After some days on 0.7.92 the problem has not reoccured yet .. (knock on wood)

     
  • Nobody/Anonymous

    Logged In: NO

    Got a similar problem and the following output:
    "root# umtsmon -v5
    umtsmon version 0.7 .
    ##P2 t=222: set verbosity level to 5
    installing text SIGABRT handler
    ##P5 t=222: TheDeviceManagerSingleton::TheDeviceManagerSingleton()
    ##P3 t=222: TheDeviceManagerSingleton::setupDevice(void)
    ##P3 t=222: TheDeviceManagerSingleton::readFromConfigFile()
    ##P5 t=222: TheSettingsSingleton::TheSettingsSingleton()
    ##P2 t=222: Settings will be saved in : '/root/.umtsmon'
    ##P3 t=222: Start iterating through all AutoDetectors

    ##P3 t=222: AutoDetectBase::go() for 'Device creation from supplied parameters'
    ##P3 t=222: AutoDetectBase::createDevice() for Device 5e21a700
    ##P3 t=222: Device creation for type 0x5e21a700 requested
    umtsmon: src/controller/AutoDetect.cpp:44: virtual Device* AutoDetectBase::createDevice(): Assertion `!theATSerialPortName
    .isNull()' failed.

    *** umtsmon version 0.7 closed due to an unrecoverable program error.
    *** Please e-mail all of the above output to umtsmon-develop@lists.sourceforge.net,
    *** Or go to the umtsmon website and file a bug.

    Aborted"

    I realized that there is no '/root/.umtsmon'.

    Currently it is working fine again.

     
  • wolfi

    wolfi - 2008-03-12

    Logged In: YES
    user_id=2013846
    Originator: YES

    It still occurs from time to time. Running 0.8 now.
    What I am doing now: When this happens, I check all plug connections between machine and UMTS modem. There is the laptop, then a 3 meter long cable (it allows me to put the modem closer to the window for better strength of field), then a short connection cable and then there is the modem. So there are three connections which might have intermitting contact.
    Then I kill the umtsmon process, if there is one running, and retry. Sometimes I have to reboot, but normally this treatment appears to be working.

    Could this output just mean that there is trouble concerning the wired connection to the modem? Had such problems with Windows too, but the statement was clearer - so stupid me could understand it.
    It said 'wireless device does not exist or is unavailable'.

     
  • wolfi

    wolfi - 2008-03-17

    Logged In: YES
    user_id=2013846
    Originator: YES

    I found out one more thing which might be related to the problem:

    UMTSmon doesn't work and shows the error mentioned above
    -> I plugged the modem only during boot time and I see only one /dev/ttyUSB0
    -> When I unplug the modem, /dev/ttyUSB0 vanishes. When I replug, then there is, once again, only this very entry /dev/ttyUSB0

    After reboot it does work (modem was already plugged in before boot now) and I got three entries:
    /dev/ttyUSB0, /dev/ttyUSB1 and /dev/ttyUSB2

     
  • wolfi

    wolfi - 2008-03-17
    • milestone: 805096 --> found_in_0.8
     
  • Klaas van Gend

    Klaas van Gend - 2008-06-22
    • labels: --> query and/or AT handling
    • assigned_to: nobody --> kvangend
    • status: open --> open-fixed
     
  • Klaas van Gend

    Klaas van Gend - 2008-06-22

    Logged In: YES
    user_id=1208561
    Originator: NO

    Hi wolfi_z, I now own a Huawei E220, and I think I solved your problems.
    Please try the current CVS version.

     
  • wolfi

    wolfi - 2008-06-24

    Logged In: YES
    user_id=2013846
    Originator: YES

    Hi kvangend,

    Will check it asap.
    My old laptop will be sent to trash now so I'll most likely do this with the new one which I should receive after my holyday (mid-July).

     
  • wolfi

    wolfi - 2008-07-13

    Logged In: YES
    user_id=2013846
    Originator: YES

    Got 0.8.90 now from openSUSE 11.0 on the previously mentioned new machine.
    Apparently it is now OK.
    Even if modem is hotplugged I get two devices (/dev/ttyUSB0 and -1) and connecting to the internet does work.
    I'll check if it remains that way.

     
  • Klaas van Gend

    Klaas van Gend - 2009-01-26
    • status: open-fixed --> closed-fixed
     
  • Klaas van Gend

    Klaas van Gend - 2009-01-26

    closing.

     

Log in to post a comment.