Page 111 of 121 FirstFirst ... 1161101109110111112113 ... LastLast
Results 1,101 to 1,110 of 1210

Thread: Comprehensive ndiswrapper troubleshooting guide

  1. #1101
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    29,807
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Trendnet TEW-684UB adapter and Ubuntu setup problem

    Hi, you will most likely need to use ndiswrapper.

    You should ask a staff member to move your thread here
    http://ubuntuforums.org/showthread.php?t=885847
    This person is great with ndiswrapper.
    Thank you

  2. #1102
    Join Date
    Sep 2011
    Location
    Pennsylvania, U.S.A.
    Beans
    3,068
    Distro
    Ubuntu Development Release

    Re: Trendnet TEW-684UB adapter and Ubuntu setup problem

    Too bad. If your adapter were a TEW-649UB, it'd be plug & play. I'm using one right now. My adapter uses a RealTek RTL8192SU chipset, the TEW-648UB uses a RealTek RTL8188SU according to http://www.wikidevi.com/wiki/TRENDnet_TEW-648UB I've learned to also check with model # and version. Manufacturers have been know to use one chipset in widget abc v1 and a different chipset in widget abc v2.

    Hmmm, I just checked Realtek's web site. They offer a Linux driver for kernel 2.6.37 and earlier. Does that infer that this chipset is supported OOB in kernel 2.6.38 and later?
    http://www.realtek.com.tw/downloads/...Downloads=true
    Last edited by kurt18947; November 24th, 2011 at 07:34 AM.

  3. #1103
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    OldschoolVgamer: could you please post the output of these commands when the adapter is plugged in:
    Code:
    lsusb
    lshw -C Network
    uname -a
    That will tell us exactly what the chipset is, plus some other useful information. It's better to determine the chipset this way than based on the manufacturer's name of the device, since as noted above the manufacturers sometimes sell devices with totally different chipsets under near-identical names--and as far as Linux is concerned the only thing that matters it the chipset.

    Once we know which chipset you have we can either try to find a native Linux driver for it, or use a Windows driver in conjunction with ndiswrapper.

  4. #1104
    Join Date
    Apr 2009
    Location
    Germany
    Beans
    178
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Comprehensive ndiswrapper troubleshooting guide

    Hello,
    I have put together some packages for latest Realtek drivers and installation using DKMS. Maybe someone can use it.

    * rtl8712u (modul 8712u) for Ubuntu 10.04/11.04 (DKMS)
    * rtl8192cu for Ubuntu 10.04/11.04/11.10 (DKMS)
    * rtl8192ce for Ubuntu 10.04/10.10 (DKMS)
    * rtl8192de/ce/se Combo package for a single installation (Ubuntu 11.10)
    Last edited by flash63; November 27th, 2011 at 11:26 AM. Reason: add version 11.10

  5. #1105
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    flash63: that's great, thanks. I'm sure this will make life much easier for people who need those to compile those drivers.

  6. #1106
    Join Date
    Nov 2011
    Beans
    4

    Re: Comprehensive ndiswrapper troubleshooting guide

    Quote Originally Posted by pytheas22 View Post
    OldschoolVgamer: could you please post the output of these commands when the adapter is plugged in:
    Code:
    lsusb
    lshw -C Network
    uname -a
    That will tell us exactly what the chipset is, plus some other useful information. It's better to determine the chipset this way than based on the manufacturer's name of the device, since as noted above the manufacturers sometimes sell devices with totally different chipsets under near-identical names--and as far as Linux is concerned the only thing that matters it the chipset.

    Once we know which chipset you have we can either try to find a native Linux driver for it, or use a Windows driver in conjunction with ndiswrapper.
    I take it that you meant using the gnome-terminal. I used that.

    lsusb
    Code:
    Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 007 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 003: ID 148f:3573 Ralink Technology, Corp. 
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    lshw -C Network
    Code:
    WARNING: you should run this program as super-user.
      *-network               
           description: Ethernet interface
           product: 88E8056 PCI-E Gigabit Ethernet Controller
           vendor: Marvell Technology Group Ltd.
           physical id: 0
           bus info: pci@0000:06:00.0
           logical name: eth0
           version: 12
           serial: 48:5b:39:1c:07:27
           capacity: 1Gbit/s
           width: 64 bits
           clock: 33MHz
           capabilities: bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.28 firmware=N/A latency=0 multicast=yes port=twisted pair
           resources: irq:67 memory:fbdfc000-fbdfffff ioport:d800(size=256) memory:fbdc0000-fbddffff
      *-network
           description: Ethernet interface
           product: 88E8056 PCI-E Gigabit Ethernet Controller
           vendor: Marvell Technology Group Ltd.
           physical id: 0
           bus info: pci@0000:05:00.0
           logical name: eth1
           version: 12
           serial: 48:5b:39:1c:01:cd
           capacity: 1Gbit/s
           width: 64 bits
           clock: 33MHz
           capabilities: bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.28 firmware=N/A latency=0 multicast=yes port=twisted pair
           resources: irq:68 memory:fbcfc000-fbcfffff ioport:c800(size=256) memory:fbcc0000-fbcdffff
    WARNING: output may be incomplete or inaccurate, you should run this program as super-user.
    uname -a
    Code:
    Linux ubuntu 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
    Is that what you're looking for?

  7. #1107
    Join Date
    Nov 2011
    Beans
    1

    Re: Comprehensive ndiswrapper troubleshooting guide

    Does the robert wolverton name ring a bell?

  8. #1108
    Join Date
    Aug 2011
    Location
    Berlin, Germany
    Beans
    7,967
    Distro
    Ubuntu Mate 20.04 Focal Fossa

    Re: Comprehensive ndiswrapper troubleshooting guide

    @OldschoolVgamer:

    Please show additionally:
    Code:
    lsmod
    iwconfig
    rfkill list

  9. #1109
    Join Date
    Nov 2011
    Beans
    4

    Re: Comprehensive ndiswrapper troubleshooting guide

    Quote Originally Posted by praseodym View Post
    @OldschoolVgamer:

    Please show additionally:
    Code:
    lsmod
    iwconfig
    rfkill list
    lsmod
    Code:
    Module                  Size  Used by
    parport_pc             36959  0 
    ppdev                  17113  0 
    snd_hda_codec_hdmi     28167  4 
    binfmt_misc            17565  1 
    snd_hda_codec_realtek   336771  1 
    snd_hda_intel          33176  2 
    snd_hda_codec         103804  3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
    snd_hwdep              13604  1 snd_hda_codec
    snd_pcm                96391  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
    snd_seq_midi           13324  0 
    nouveau               682322  2 
    snd_rawmidi            30486  1 snd_seq_midi
    ttm                    76664  1 nouveau
    snd_seq_midi_event     14899  1 snd_seq_midi
    snd_seq                61621  2 snd_seq_midi,snd_seq_midi_event
    snd_timer              29602  2 snd_pcm,snd_seq
    snd_seq_device         14462  3 snd_seq_midi,snd_rawmidi,snd_seq
    drm_kms_helper         42136  1 nouveau
    i7core_edac            27903  0 
    snd                    67382  14 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_rawmidi,snd_pcm,snd_seq,snd_timer,snd_seq_device
    asus_atk0110           17976  0 
    drm                   227534  4 nouveau,ttm,drm_kms_helper
    i2c_algo_bit           13400  1 nouveau
    video                  19438  1 nouveau
    edac_core              53845  1 i7core_edac
    soundcore              12680  1 snd
    snd_page_alloc         18529  2 snd_hda_intel,snd_pcm
    lp                     17825  0 
    parport                46458  3 parport_pc,ppdev,lp
    usbhid                 46956  0 
    hid                    91020  1 usbhid
    ahci                   25951  1 
    libahci                26642  1 ahci
    firewire_ohci          40370  0 
    firewire_core          62646  1 firewire_ohci
    sky2                   58509  0 
    crc_itu_t              12707  1 firewire_core
    xhci_hcd               77643  0
    iwconfig
    Code:
    lo        no wireless extensions.
    eth0      no wireless extensions.
    eth1      no wireless extensions.
    rfkill list

    I typed this one and it didn't do anything

  10. #1110
    Join Date
    Aug 2011
    Location
    Berlin, Germany
    Beans
    7,967
    Distro
    Ubuntu Mate 20.04 Focal Fossa

    Re: Comprehensive ndiswrapper troubleshooting guide

    Try to add the device ID to the driver rt2800usb. This is one line, you better copy/paste it:
    Code:
    echo 'install rt2800usb modprobe --ignore-install rt2800usb ; /bin/echo "148f 3573" > /sys/bus/usb/drivers/rt2800usb/new_id' | sudo tee /etc/modprobe.d/rt2800usb.conf
    Load the driver:
    Code:
    sudo modprobe -v rt2800usb
    and replug the stick. Check after that:
    Code:
    iwconfig
    sudo iwlist scan
    dmesg | grep rt2

Page 111 of 121 FirstFirst ... 1161101109110111112113 ... LastLast

Bookmarks

Posting Permissions

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