So how do I set up linux to work with my USB Cable mode? - Page 2


Page 2 of 2 FirstFirst 12
Results 16 to 29 of 29

Thread: So how do I set up linux to work with my USB Cable mode?

  1. #16
    Join Date
    Apr 2001
    Location
    SF Bay Area, CA
    Posts
    14,947
    Just a side note: BadCRC errors can also be caused by bad IDE cables. If you use anything other than a real 80-conductor flat ribbon cable, then the cable may be to blame.

    I've gotten a lot of BadCRC errors from one specific "rounded" IDE cable that I was using for a while, until I replaced it with the flat one that's in there now. (The drive is still working fine, probably a year and a half later.) Yes, flat cables are bad for airflow, and hard to route -- but if the alternative is CRC errors from the drive, then too bad, I'm going with the flat cables.

    Anyway, as I said, just a note -- it may not be the drive itself that's causing those errors.

  2. #17
    Join Date
    Nov 2003
    Location
    Phoenix, AZ, USA
    Posts
    287
    banzaikai is right, your /var/log/messages shows that there's a harddrive problem and that is something you should take very seriously. hopefully: it's just a cable problem like bwkaz says.

    with your modem connected, what does
    Code:
    lsusb
    show?
    BEHOLD!!! MY AWESOME HUMILITY!
    Ex Linux, Scientia

    i use:
    centos 5.2 on 3.0 GHz Pentium 4 (filer/print server)
    ubuntu 8.10 on 1.6 GHz Celeron M (personal laptop)

  3. #18
    Join Date
    Mar 2007
    Location
    India
    Posts
    25

    Hi Davy,banzaikai,acid45 and bwkaz

    Well, this

    Quote:
    ubuntu kernel: [ 485.600000] usb 1-1: new full speed USB device using uhci_hcd and address 3
    ubuntu kernel: [ 485.780000] usb 1-1: no configuration chosen from 1 choice

    means that it saw the modem/router, but had no module to load for it. This is where the usb-serial or usb-eth would be used. Once associated, it'll show up for that device.
    So what module do i need to load ?
    what is usb-serial and usb-eth?
    I've been reading about them but didnt get
    my understanding anywhere!!

    And as far as Dma/CRC error is concerned i'll reveal about my hdd
    a little later and crazy things i did with it ......as i need to run my
    internet first!!

    Heres' the o/p of
    Code:
    lsusb
    
    Bus 002 Device 001: ID 0000:0000  
    Bus 001 Device 002: ID 2001:5b00 D-Link Corp. [hex] 
    Bus 001 Device 001: ID 0000:0000
    Somewhere between nowhere
    srajv
    Beyond fear lies success

  4. #19
    Join Date
    Nov 2003
    Location
    Phoenix, AZ, USA
    Posts
    287
    then you do as i said in my instructions to the other guy. you run modprobe usbserial vendor=0x2001 product=0x5b00 and also give us the output of /var/log/messages as you run modprobe.

    you should see to your harddrive first. that sort of output from /var/log/messages about your harddrive usually means that your computer is about to die.
    BEHOLD!!! MY AWESOME HUMILITY!
    Ex Linux, Scientia

    i use:
    centos 5.2 on 3.0 GHz Pentium 4 (filer/print server)
    ubuntu 8.10 on 1.6 GHz Celeron M (personal laptop)

  5. #20
    Join Date
    Mar 2007
    Location
    India
    Posts
    25

    Hi Davy and all

    Though i did the modprobe thing .....and posted the results earlier too,
    here's doing it again :


    Code:
     
    tail -f /var/log/messages before i did modprobe
    
    Jul 30 19:10:24 ubuntu kernel: [  255.170000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Jul 30 19:10:24 ubuntu kernel: [  255.170000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.170000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.280000] ide0: reset: success
    The output of tail -f /var/log/messages, after i did modeprobe :

    Code:
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.280000] ide0: reset: success
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] usbcore: registered new interface driver usbserial
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] usbcore: registered new interface driver usbserial_generic
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] drivers/usb/serial/usb-serial.c: USB Serial Driver core
    Somewhere between nowhere
    srajv
    Beyond fear lies success

  6. #21
    Join Date
    Nov 2003
    Location
    Phoenix, AZ, USA
    Posts
    287
    sorry, if you actually ran
    Code:
    modprobe usbserial vendor=0x2001 product=0x5b00
    with your device connected and that was all the /var/log/messages showed, then your device isn't supported.

    it's peculiar that we didn't even get an error message. can you describe, in steps, exactly what you did to get this output?
    BEHOLD!!! MY AWESOME HUMILITY!
    Ex Linux, Scientia

    i use:
    centos 5.2 on 3.0 GHz Pentium 4 (filer/print server)
    ubuntu 8.10 on 1.6 GHz Celeron M (personal laptop)

  7. #22
    Join Date
    Jun 2007
    Location
    London, U.K.
    Posts
    13
    What an interesting Site, such good information.

    I run Ubuntu6.06 on this pc (not now, oops) and have had a modem change from a large Motorola one to a smaller unti whoise name I don't recall (Scientific Atlanta, a cisco company - model 2100) - I will try this and see if the ethernet (10/100) link to the PC still works.
    THe other-end of the modem is a coax tv-style screed connector (10mm dia) - this is part of a wired cable system so I guess the modem is behaving like a tv-decoder and tuning me to the "internet" station, rather than any one of many TV channels. This cable-system is burried in the road.
    The Motorola modem lasted years, but finally died from lightning, - presumably up the coax as this was the only thing connected....
    I remove the cables from the PC when not in use, just to be sure.....now, I unscrew the modem input coax also.

  8. #23
    Join Date
    Jun 2007
    Location
    London, U.K.
    Posts
    13

    Ubuntu recognises new modem 10/100

    Back again - using Ubuntu 6.06 and this is Firefox.....slightly different j-l home-page with no sign of the usual log-in, but let that pass -
    "obviously" the modem is talking to this PC set-up ( I swapped the HDD, from a somewhat more-familiar Win98SE, set-up)....so the Modem appears to work into Ubuntu (using the 10/100 cable ).
    Not sure if it helps the Thread Originator - but at least it appears as easy as pie....of course USB "might be different" - although it's never objected to camera-memory via an all-in-one reader using USB - or an external HDD connected by USB/IDE converter - such a useful device and it came with a mini-CD with the Win drivers ( Oh shut up Harry!)
    Bye....
    PS the coax connector is 9.3 mm dia,
    not 10, as mentioned in the earlier post.
    Last edited by jl_harry12; 07-31-2007 at 01:23 PM. Reason: technical update

  9. #24
    Join Date
    Mar 2007
    Location
    India
    Posts
    25
    I still believe my DSL 502t Dlink modem/routercan work with my ubuntu 7.04
    .....

    Here are what my /etc/network/interfaces saying :

    Code:
    # This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).
    
    # The loopback network interface
    auto lo
    iface lo inet loopback
    nameserver 59.17.243.70
    nameserver 203.94.243.70
    Here are what my /etc/resolv file saying :

    Code:
    nameserver 59.17.243.70
    nameserver 203.94.243.70
    When i tried loading the module for my usb modem, using modprobe this is what i had :

    Code:
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    Jul 30 19:10:24 ubuntu kernel: [  255.210000] ide: failed opcode was: unknown
    Jul 30 19:10:24 ubuntu kernel: [  255.280000] ide0: reset: success
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] usbcore: registered new interface driver usbserial
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] usbcore: registered new interface driver usbserial_generic
    Jul 30 19:13:45 ubuntu kernel: [  456.430000] drivers/usb/serial/usb-serial.c: USB Serial Driver core
    By the way the dma crc error is gone now, it doesnt appear anymore, when i do :

    Code:
    tail -f /var/log/messages 
    
    Aug  2 20:02:09 ubuntu kernel: [   13.800000] input: PC Speaker as /class/input/input2
    Aug  2 20:02:09 ubuntu kernel: [   14.180000] NET: Registered protocol family 23
    Aug  2 20:02:09 ubuntu kernel: [   14.220000] parport: PnPBIOS parport detected.
    Aug  2 20:02:09 ubuntu kernel: [   14.220000] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    Aug  2 20:02:09 ubuntu kernel: [   14.330000] input: ImPS/2 Logitech Wheel Mouse as /class/input/input3
    Aug  2 20:02:09 ubuntu kernel: [   15.110000] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
    Aug  2 20:02:09 ubuntu kernel: [   15.110000] ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
    Aug  2 20:02:09 ubuntu kernel: [   15.960000] lp0: using parport0 (interrupt-driven).
    Aug  2 20:02:09 ubuntu kernel: [   16.160000] Adding 650560k swap on /dev/disk/by-uuid/25dfefad-8c45-44e5-b768-ea62096b68d2.  Priority:-1 extents:1 across:650560k
    Aug  2 20:02:09 ubuntu kernel: [   16.320000] EXT3 FS on hdc3, internal journal
    Any takers to advise me on what iam missing.........

    Your Save is someone else's gain
    srajv
    Beyond fear lies success

  10. #25
    Join Date
    Aug 2007
    Posts
    1
    thanks to all..

    i have been followin the post since a long time and , i too have the SAME problem ..

    also d output of modprobe usbserial is the same ..
    Plz provide some solution ..

    i also found, i could use ndiswrapper .. but got problems with that too ..
    someone posted that i can obtain the inf and config files from exe files using unzip in linux .. but im unable to do it ..
    any suggestions ??

  11. #26
    Join Date
    Jul 2002
    Location
    43.46N 83.52W
    Posts
    982

    Cool

    srajv, the "lo" interface is an internal "loopback" that Linux uses for testing. Think of it as a "null:" adaptor. Those nameserver addys link to one from India, and the other Korea. I don't know how they got in there. I'm betting bwkaz was right about that cable.

    Essentially, what Davy and I are trying to explain is that the D-Link has a built-in router. Most DSL equipment with the LAN/USB ports are just "dumb" modems, but can be interfaced to Linux using the PPPoE modules. This is because those models have been around for some time, and the developers have had "lots-o-timeŽ" to write some code for 'em.

    Not the D-Link.

    Now, if it were just a modem, then it would probably work. Thing is, we're not interfacing to the modem section, but the router. What protocol/interface the router uses is what we're guessing at, and what we're trying to load up (usbserial, usbethernet, usbjujubag, etc.). Since the D-Link site/manual isn't very clear as to what's in there, then we're doing this hit-or-miss module loading/probing/failing thing.

    As jl_harry12 points out, just plugging this thing in using the eth port does the trick, as this uses standard networking protocols (called "wham-bam-thank-you-DSLAM" in the biz).

    Our mission, folks, is to find out what to use to get this silly thing operating via usb and Linux. So far, usbserial doesn't seem to be it...

    Now, admittedly, I pulled "usb-eth" outta my behind, but I'm sure there's something like it in the Linux world, as I have two 3Com usb-to-ethernet (10 base only) adaptors that I use on older Win98 machines (last version of Windows that they wrote drivers for). I'm sure there's some usb3c9xx module out there, but I've never looked... maybe Davy or Kaz has heard of something?

    rave23, you bring up an interesting idea! I'll take a peek and see if the ndiswrapper folks have anything... BTW, you can go into the Windows device manager, select the modem/router/usb port listed, and look at what drivers it's using. You can then copy those to a floppy/usb drive and use that for the ndiswrapper without having to extract from an exe. Errr, provided you have a Windows machine/partition, that is.

    Update: nothing at ndiswrapper for the DSL-502T, sorry.

    banzai "stumped at the moment" kai
    "Mind you, I got to do the licking this time, so it wasn't too bad."
    - Jane Horrocks, The Guardian, 1995

  12. #27
    Join Date
    Apr 2001
    Location
    SF Bay Area, CA
    Posts
    14,947
    Well, Googling for "usb ethernet spec" found this page:

    http://www.ixbat.de/index.php?page_id=88

    which talks about three different protocols that Ethernet-over-USB can be implemented with. The best one is "CDC Ethernet", which another Google (for "cdc ethernet driver linux") found this page:

    http://www.linux-usb.org/devices.html

    which says that the "CDC Ethernet" protocol is supported by the usbnet module in 2.6 kernels. (From poking around in my kernel source, you may also need to load cdc_ether to get this to work.)

    The first page also says that the usbnet module handles the second-best protocol, "CDC Subset" (although poking around in my kernel source shows that you may also need to load cdc_subset).

    There's a third protocol that's spoken by some USB Ethernet devices, called RNDIS -- this is Microsoft's NDIS (network driver spec) protocol, adapted to talk over an RPC link, in this case over a USB connection. Because it's Microsoft, it's not documented very well (in some places not at all), and so support is pretty thin. If your device only supports RNDIS, you might as well forget about it, in my opinion.

  13. #28
    Join Date
    Mar 2007
    Location
    India
    Posts
    25

    Attention BanzaiKai :)

    Hi all,

    Actually, what you were doing wrong is loading the PPPoE module in Linux, when you don't need it (the router is handling all that). All you need to do is set eth# to DHCP, and let 'er rip. Essentially, what happened was the PPPoE in the router got things going, then set up it's built-in DHCP server to look out to the network. Your computer then launched the PPPoE module, and set out looking for the modem, finding only a DHCP server answering any broadcasts, so it failed. Once the PPPoE is disabled on the Linux/XP side of things (and DHCP enabled), then things work as advertised. Believe it or not, this is exactly why you want the DSL-502T - so you don't have to mess with PPPoE, and just set all your computers for DHCP and get on with your life.
    BanzaiKai, how this thing, the dhcp thing, would help me ?

    Can you put some more light on it, and help me understand this.
    Lemme know if you need any sort of file o/p.

    By the way, my DSL502T Dlink is unfortunately using the RNDIS drivers

    Your save is someone else's gain
    srajv
    Beyond fear lies success

  14. #29
    Join Date
    Jul 2002
    Location
    43.46N 83.52W
    Posts
    982

    Cool

    By the way, my DSL502T Dlink is unfortunately using the RNDIS drivers
    Is bwkaz da man, or whut?

    So, it looks like usbnet is the guy we want. If it helps any, I found a mention of someone saying there's a Texas Instruments chipset on that usb port in the D-Link.

    FWIW, that 3Com 3C19250 I have works flawlessly with FC6. No setup required! True plug-n-play. It uses the Kawasaki chipset, if you're wondering. Anyway...
    BanzaiKai, how this thing, the dhcp thing, would help me ?
    You haven't quite "got it" yet. Dynamic Host Configuration Protocol is the way of automatically assigning IPs to devices on your network. What you need is a way to connect to the network. In this case, usb is the issue, and switching to the ethernet/RJ45 port will fix this. All you need is a cheap 10/100 baseT network card (post the models for sale in your area, so we can tell you if it's supported or not, before you buy it). Install the card, Linux should auto-detect it, and you just plug in the RJ-45 cable and go. Even an older 10baseT (NE-2000) will work, as most ISPs only let you have 3-5Mbps bandwidth anyway. At least, in the U. S. of A.

    Once the physical connection is made, the DHCP takes over to set things up for you.

    banzai "Kawa-bunga, dude!" kai
    "Mind you, I got to do the licking this time, so it wasn't too bad."
    - Jane Horrocks, The Guardian, 1995

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •