Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Dlink DLW 121

  1. #1
    warbenekar1 NNTP User

    Default Dlink DLW 121

    I just installed OpenSuse 11.0, and I have a Dlink DWL-121. Yast Network Settings shows it as

    Prism 2.x 802.11b Adapter (Not connected)

    Now I know its connected, so I am not sure about all that, but then it says

    Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details.

    So I opened up a terminal and did a dmesg and found this section

    prism2usb_init: prism2_usb.o: 0.2.7 Loaded
    prism2usb_init: dev_info is: prism2_usb
    ------------[ cut here ]------------
    kernel BUG at net/core/dev.c:861!
    invalid opcode: 0000 [1] SMP
    last sysfs file: /sys/devices/pci0000:00/0000:00:0f.0/usb1/1-3/1-3:1.0/bInterfaceClass
    CPU 0
    Modules linked in: prism2_usb(+) p80211 usbhid hid ff_memless rtc_cmos parport_pc rtc_core parport ohci1394 sundance rtc_lib floppy snd_intel8x0 serio_raw k8temp mii ieee1394 snd_ac97_codec ac97_bus i2c_ali15x3 snd_pcm snd_timer usblp i2c_ali1563 i2c_ali1535 shpchp snd sr_mod soundcore button cdrom i2c_core pci_hotplug snd_page_alloc usb_storage sg ehci_hcd ohci_hcd usbcore sd_mod edd ext3 mbcache jbd fan pata_ali sata_uli libata scsi_mod dock thermal processor
    Pid: 1152, comm: modprobe Tainted: G N 2.6.25.5-1.1-default #1
    RIP: 0010:[<ffffffff803d5cf2>] [<ffffffff803d5cf2>] dev_alloc_name+0x1c/0x4f
    RSP: 0018:ffff81003d471b48 EFLAGS: 00010246
    RAX: ffff81003e9ab000 RBX: ffff81003e50d800 RCX: ffff81003e50d800
    RDX: ffff81003e12d830 RSI: ffffffff8834c631 RDI: 0000000000000000
    RBP: ffff81003d471b78 R08: ffff81003d471ba8 R09: ffff81003e50d800
    R10: 0000000000000000 R11: ffff81003e812508 R12: ffff81003e9ab000
    R13: ffff81003e9ab000 R14: ffff81003e014000 R15: ffff81003e12d800
    FS: 00007f0be0e176f0(0000) GS:ffffffff80630000(0000) knlGS:0000000000000000
    CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    CR2: 00007f882a491098 CR3: 000000003e1c1000 CR4: 00000000000006e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Process modprobe (pid: 1152, threadinfo ffff81003d470000, task ffff81003d8ca3c0)
    Stack: ffff81003d471b68 ffffffff803deefd ffff81003e9ab000 ffff81003e50d800
    ffff81003e91c000 ffff81003e9ab000 ffff81003d471ba8 ffffffff8834af86
    ffff81003d471ba8 ffff81003e50d800 ffff81003e91c000 ffffffff8835f9ab
    Call Trace:
    [<ffffffff8834af86>] : p80211:register_wlandev+0x26/0xe8
    [<ffffffff8835efee>] : prism2_usb: prism2sta_probe_usb+0x16a/0x234
    [<ffffffff8810b18f>] :usbcore:usb_probe_interface+0xe5/0x133
    [<ffffffff8039fcee>] driver_probe_device+0xc0/0x16e
    [<ffffffff8039fe0c>] __driver_attach+0x70/0xae
    [<ffffffff8039f541>] bus_for_each_dev+0x4f/0x89
    [<ffffffff8039fb39>] driver_attach+0x1c/0x1e
    [<ffffffff8039edeb>] bus_add_driver+0xb7/0x200
    [<ffffffff8039ffbf>] driver_register+0x5e/0xde
    [<ffffffff8810b3ed>] :usbcore:usb_register_driver+0x80/0xe4
    [<ffffffff88100056>] : prism2_usb: prism2usb_init+0x56/0x58
    [<ffffffff8025a818>] sys_init_module+0x1b0a/0x1c47
    [<ffffffff8020bfea>] system_call_after_swapgs+0x8a/0x8f
    DWARF2 unwinder stuck at system_call_after_swapgs+0x8a/0x8f

    Leftover inexact backtrace:



    Code: 3e 51 80 31 c0 e8 52 0f e7 ff 5b 41 5c c9 c3 55 48 89 e5 41 55 41 54 49 89 fc 53 48 83 ec 18 48 8b bf 50 04 00 00 48 85 ff 75 04 <0f> 0b eb fe 4c 8d 6d d0 4c 89 ea e8 2e d8 ff ff 85 c0 89 c3 78
    RIP [<ffffffff803d5cf2>] dev_alloc_name+0x1c/0x4f
    RSP <ffff81003d471b48>
    ---[ end trace a5c1982a0961e955 ]---

    Ok, so in short what do I need to do on my system to get my device to work. I should like to add the comment that my device is a DWL-121, which is technically non existent. I know in Windows XP you can use DWL-122 drivers and modify the INF files to get them to work. However I have tried NDISWrapper, with the same files that worked in XP and that bore no working results.

    Also, note I had to put spaces everywhere where there was because it wanted to make that face. So : p is actually shouldn't have a space, just so there is no confusion.

  2. #2
    Join Date
    Jun 2008
    Location
    Sarasota
    Posts
    301

    Default Re: Dlink DLW 121

    Quote Originally Posted by warbenekar1 View Post
    I have a Dlink DWL-121. Yast Network Settings shows it as

    Prism 2.x 802.11b Adapter (Not connected)

    Now I know its connected, so I am not sure about all that,

    I know in Windows XP you can use DWL-122 drivers and modify the INF files to get them to work. However I have tried NDISWrapper, with the same files that worked in XP and that bore no working results.
    So, how do you 'know its connected'? [You don't show any output that would
    make us agree with that, such as 'ifconfig', 'iwconfig', 'route']

    I don't own this device (tho I did in the distant past, and always used ndiswrapper
    on it, under Mandrake-Linux)

    I tend to believe that the msg about 'missing firmware'...SUSE is known for
    installing drivers, and then NOT installing the needed firmware to go with it.
    But, that's only a guess.

    Your best bet is to try again to use ndiswrapper. Once you get the windows
    driver installed in ndiswrapper, post the output of the cmd:

    ndiswrapper -l

    and then we'll see whether the results of that look promising.

    Hope this helps...

    Dave

  3. #3
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,235

    Default Re: Dlink DLW 121

    cookdav wrote:
    > warbenekar1;1829781 Wrote:
    >> I have a Dlink DWL-121. Yast Network Settings shows it as
    >>
    >> Prism 2.x 802.11b Adapter (Not connected)
    >>
    >> Now I know its connected, so I am not sure about all that,
    >>
    >> I know in Windows XP you can use DWL-122 drivers and modify the INF
    >> files to get them to work. However I have tried NDISWrapper, with the
    >> same files that worked in XP and that bore no working results.
    >>
    >>

    >
    > So, how do you 'know its connected'? [You don't show any output that
    > would
    > make us agree with that, such as 'ifconfig', 'iwconfig', 'route']
    >
    > I don't own this device (tho I did in the distant past, and always used
    > ndiswrapper
    > on it, under Mandrake-Linux)
    >
    > I tend to believe that the msg about 'missing firmware'...SUSE is known
    > for
    > installing drivers, and then NOT installing the needed firmware to go
    > with it.
    > But, that's only a guess.


    That is _NOT_ SUSE's fault. Most of the vendors do not allow any
    distro to distribute firmware, which is why you need to go elsewhere
    to get it.

    > Your best bet is to try again to use ndiswrapper. Once you get the
    > windows
    > driver installed in ndiswrapper, post the output of the cmd:
    >
    > ndiswrapper -l
    >
    > and then we'll see whether the results of that look promising.


    You very well may need to use ndiswrapper; however, be aware that when
    you do, you are loading a piece of Windows into your kernel and
    allowing it to run with absolutely no restrictions and/or checking.
    Any bugs in that driver will crash Linux!

    Larry

  4. #4
    warbenekar1 NNTP User

    Question Re: Dlink DLW 121

    I ran ifconfig, iwconfig, and route and got nothing. I mean that is to say the output implied there was no Internet connection which I knew there wouldn't be. When I ran ndiswrapper the first time I did an ndiswrapper -l and it told me there were no installed drivers. Which makes sense, as there were none. Then I ran ndiswrapper -i and told it where to find the inf file, which was in my home directory. It seemed to install successfully, or at least it generated no errors, however after the fact I ran ndiswrapper -l again and I got nothing, but this time there was no output at all. So I waited and waited and waited, until 1/2 hour passed by. Still no output. I got tired of waiting and restarted my computer to see if that made a difference, but doing ndiswrapper -l still does the same thing.

    Can anyone tell me why ndiswrapper -l doesn't work? Also, assuming I installed it correctly is there a guide or something that can tell me what to do next? I don't know anything at all about ndiswrapper really...

  5. #5
    Join Date
    Jun 2008
    Location
    Sarasota
    Posts
    301

    Default Re: Dlink DLW 121

    Please post the output of the cmd:
    uname -a

  6. #6
    Join Date
    Jul 2008
    Location
    Palampur Himachal India
    Posts
    16

    Default Re: Dlink DLW 121

    hi
    checkout for the verification of existance of the FIRMWARE for your device (my DLINK DWL-G122 dint worked until i installed the firmware! )

    try to install the rpm containing RT73.BIN (search google with this name and it will surely point to a rpm source for the same)

    install and reboot...

    further i recommend installing another program wifi-radar

    good luck
    -vaibhav
    Experience is a hard teacher. She gives the test first and the lessons afterwards!!

  7. #7
    warbenekar1 NNTP User

    Default Re: Dlink DLW 121

    Here is everything in full. As I said ndiswrapper -l produces no output, although it does seem that the INF file worked lasttime as it says that netprism is already installed. So, now assuming that the driver is installed correctly, what do I have to do to make it work?

    linux-b2jr:/home/ben # ifconfig
    eth0 Link encap:Ethernet HWaddr 00:50:8D:7F:E9:B3
    inet6 addr: fe80::250:8dff:fe7f:e9b3/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:49 errors:0 dropped:0 overruns:0 carrier:49
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:15174 (14.8 Kb)
    Interrupt:21 Base address:0xef00

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:54 errors:0 dropped:0 overruns:0 frame:0
    TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:3460 (3.3 Kb) TX bytes:3460 (3.3 Kb)

    linux-b2jr:/home/ben # iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    linux-b2jr:/home/ben # route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    loopback * 255.0.0.0 U 0 0 0 lo

    linux-b2jr:/home/ben # uname -a
    Linux linux-b2jr 2.6.25.5-1.1-default #1 SMP 2008-06-07 01:55:22 +0200 x86_64 x86_64 x86_64 GNU/Linux

    linux-b2jr:/home/ben # ndiswrapper -v
    utils version: '1.9', utils version needed by module: '1.9'
    module details:
    filename: /lib/modules/2.6.25.5-1.1-default/updates/ndiswrapper.ko
    version: 1.52
    vermagic: 2.6.25.5-1.1-default SMP mod_unload

    linux-b2jr:/home/ben # ndiswrapper -i NETPRISM.inf
    driver netprism is already installed

    linux-b2jr:/home/ben # ndiswrapper -l

  8. #8
    Join Date
    Jun 2008
    Location
    Sarasota
    Posts
    301

    Default Re: Dlink DLW 121

    Quote Originally Posted by warbenekar1 View Post
    As I said ndiswrapper -l produces no output, although it does seem that the INF file worked lasttime as it says that netprism is already installed. So, now assuming that the driver is installed correctly, what do I have to do to make it work?

    linux-b2jr:/home/ben # uname -a
    Linux linux-b2jr 2.6.25.5-1.1-default #1 SMP 2008-06-07 01:55:22 +0200 x86_64 x86_64 x86_64 GNU/Linux
    No the driver is NOT installed correctly, if it doesn't display it's name AND show
    device/hardware PRESENT, when you run 'ndiswrapper -l'.

    The probable REASON that it isn't showing up is that you are running the
    64-bit kernel, but are (probably) installing the 32-bit Windows driver. If so,
    either install 32-bit SUSE or find the 64-bit Windows driver.
    More info here:
    Ndiswrapper - openSUSE
    NDISwrapper

    Hope this helps...

    Dave

  9. #9
    warbenekar1 NNTP User

    Default Re: Dlink DLW 121

    I will go 32 Bit and see what happens...

  10. #10
    Join Date
    Jul 2008
    Location
    Palampur Himachal India
    Posts
    16

    Default Re: Dlink DLW 121

    & for 32-bit, you shall probably not need ndiswrapper!
    try to install the linux only software. If DWL122 can work, i am very sure yours should also work fine...
    i am just pasting my dlink h/w info, just incase its of some assistance:

    vaibhav:~ # hwinfo --wlan
    20: USB 00.0: 0282 WLAN controller
    [Created at usb.122]
    UDI: /org/freedesktop/Hal/devices/usb_device_7d1_3c03_noserial_if0
    Unique ID: 7bWa.Pj1JuB68U+F
    Parent ID: pBe4.3f5c44ENLJ9
    SysFS ID: /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0
    SysFS BusID: 2-3:1.0
    Hardware Class: network
    Model: "D-Link 802.11 bg WLAN"
    Hotplug: USB
    Vendor: usb 0x07d1 "D-Link System"
    Device: usb 0x3c03 "802.11 bg WLAN"
    Revision: "0.01"
    Driver: "rt73usb"
    Driver Modules: "rt73usb"
    Device File: wlan0
    Features: WLAN
    Speed: 480 Mbps
    HW Address: 00:15:e9:a4:c1:54
    Link detected: yes
    WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
    WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
    WLAN encryption modes: WEP40 WEP104 TKIP CCMP
    WLAN authentication modes: open sharedkey wpa-psk wpa-eap
    Module Alias: "usb:v07D1p3C03d0001dc00dsc00dp00icFFiscFFipFF"
    Driver Info #0:
    Driver Status: rt73usb is active
    Driver Activation Cmd: "modprobe rt73usb"
    Config Status: cfg=no, avail=yes, need=no, active=unknown
    Attached to: #22 (Hub)
    ----------------------------
    -Good Luck!
    Experience is a hard teacher. She gives the test first and the lessons afterwards!!

Page 1 of 2 12 LastLast

Posting Permissions

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