Gobi2000 on CF-31 mk3 LinuxMint

Discussion in 'Panasonic' started by theoak2, Jul 17, 2017.

  1. theoak2

    theoak2 Notebook Evangelist

    Reputations:
    84
    Messages:
    315
    Likes Received:
    31
    Trophy Points:
    41
    Anyone get this to work on this or any other Linux? EmperorLinux sells CF-31s with Gobi cards, so I presume it is possible.

    LinuxMint 18.2 and Ubuntu Linux 16.04 LTS report from lsusb:

    No sign of Gobi 2000. It does work in Windows 10 eek! :eek: so card is recognized in BIOS.

    I have a Verizon account, and would like to add my CF-31 mk3 to the fray, but have only found info for doing this with ThinkPads (my second favorite laptop), so far.
     
  2. UNCNDL1

    UNCNDL1 Notebook Evangelist

    Reputations:
    192
    Messages:
    528
    Likes Received:
    40
    Trophy Points:
    41
    Sheepman (aka sadlmkr) has Gobi working and hopefully will have some insight in your questions.

    Sent from my SM-G920V using Tapatalk
     
  3. theoak2

    theoak2 Notebook Evangelist

    Reputations:
    84
    Messages:
    315
    Likes Received:
    31
    Trophy Points:
    41
    Thanks UNCNDL1, Good to hear. I believe some firmware has to be loaded by kernel before Gobi shows in lsusb.

    I tried using info from this ThinkPad-centric webpage:

    http://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000

    but none of the UQCN.mbn md5sums (in the twelve folders) matched the Verizon md5sum shown for Verizon, so I can only presume that these instructions match a different downloaded file for Gobi 2000 drivers. Probably Lenovo verson of Gobi card has different files with different md5sums. I tried copying each folder's contents to /lib/firmware/gobi folder, then rebooting, but so far have not met with success. Only 3 folders have all three files referenced (1, 3, and 12).

    Another thing I have noticed is that /lib/udev/rules.d/60-gobi.rules has the wrong device ID for Vendor ID 04da

    According to Hardware ID in Windows Device Manager, the Vendor ID for Gobi 2000 is 04DA and Device ID is 250F.

    But /lib/udev/rules.d/60-gobi.rules shows Device ID 250d for Vendor ID 04da. Changing that to 250f (to match Windows) does nothing.
     
  4. Shawn

    Shawn Crackpot Search Ninja and Options Whore

    Reputations:
    1,410
    Messages:
    6,595
    Likes Received:
    1,032
    Trophy Points:
    331
    I just sent some smoke signals to SHEEPMAN!. If he is looking to the sky, he will respond soon.:hi: :vbthumbsup:
     
  5. SHEEPMAN!

    SHEEPMAN! Freelance

    Reputations:
    794
    Messages:
    2,331
    Likes Received:
    220
    Trophy Points:
    81
    Too many fires, couldn't see the smoke......or as the fire look-out said "I can't see the fire from here... it's too smoky". (This happened, I heard it)
    Add your device number to udev.rules.d .
    250D is Gobi 1000.
    It seems to me that you need a USB-Serial converter. It's probably black-listed.
    Udev should automatically see and load the Gobi. See "gobi-loader".
    More later as the coffee soaks in.
     
  6. Shawn

    Shawn Crackpot Search Ninja and Options Whore

    Reputations:
    1,410
    Messages:
    6,595
    Likes Received:
    1,032
    Trophy Points:
    331
  7. theoak2

    theoak2 Notebook Evangelist

    Reputations:
    84
    Messages:
    315
    Likes Received:
    31
    Trophy Points:
    41
    i have gobi-loader installed.

    sudo /lib/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi

    says:

    Failed to open serial device: : No such file or directory
    usage: /lib/udev/gobi_loader [-2000] serial_device firmware_dir

    and sure enough, /dev/ttyUSB0 does not exist (or any other /dev/ttyUSB)
     
  8. UNCNDL1

    UNCNDL1 Notebook Evangelist

    Reputations:
    192
    Messages:
    528
    Likes Received:
    40
    Trophy Points:
    41
  9. theoak2

    theoak2 Notebook Evangelist

    Reputations:
    84
    Messages:
    315
    Likes Received:
    31
    Trophy Points:
    41
    Thanks UNCNDL1, but been there, done that

    What I have done so far:

    installed gobi-loader

    copied extracted Gobi drivers from working Windows install
    (path: /Images/Panasonic/) where there are 11 folders with required .mbn files)

    Created /lib/firmware/gobi folder

    Copied amss.mbn, apps.mbn, and UQCN.mbn to that new gobi folder ( tried contents of folder # 1, #3, and #12 which were the only folders that contained all 3 files)

    Rebooted after trying each new batch of files copied to /lib/firmware/gobi

    typed lsusb in console, which never shows the Gobi 2000 device

    No /dev/ttyUSB* devices exist
     
  10. theoak2

    theoak2 Notebook Evangelist

    Reputations:
    84
    Messages:
    315
    Likes Received:
    31
    Trophy Points:
    41
    Wine is only used to extract the .mbn files from the msi file.

    I think SaddleMaker is on the right track with USB-Serial converter being the problem, but have yet to find where it is blacklisted.
     

Share This Page