Results 1 to 7 of 7

Thread: WUSB54GC - BT3 Final - Segmentation Fault

  1. #1
    Just burned his ISO
    Join Date
    Dec 2008
    Posts
    6

    Default WUSB54GC - BT3 Final - Segmentation Fault

    I purchased the WUSB54GC adapter based on the comment in the hardware compatibilty list. (Everything works out of the BT3 box!) Unfortunately, that's not true in my situation.

    I've followed several tutorials to the letter. (And yes, I waited for the boot process to complete before plugging it in.) Everytime I use iwconfig or ifconfig, it causes a segmentation fault. These commands worked fine prior to plugging it in. I also tried the enhanced drivers, but no luck.

    I've tried the adapter on a different computer with the same results. I thought it might be dead, but it works fine under Windows XP.

    Here is the info on the adapter.
    FCC ID:Q87-WUSB54GC
    IC:3839A-WUSB54GC
    Manufactured 10/2008

    If you have had the same problem, please let me know how you resolved it!

    Here is the message I'm getting:
    Code:
    bt ~ # ifconfig rausb0 down
    Segmentation fault
    bt ~ #
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: Oops: 0000 [#1]
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: SMP
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: CPU:    1
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: EIP:    0060:[<c065e500>]    Not tainted VLI
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: EFLAGS: 00210202   (2.6.21.5 #4)
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: EIP is at __dev_get_by_name+0x90/0xe0
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: eax: ffffffff   ebx: f67a9f30   ecx: 0000000f   edx: 00c30102
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: esi: f467c001   edi: f67a9f31   ebp: f467c000   esp: f67a9ecc
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: Process ifconfig (pid: 7005, ti=f67a8000 task=dfd1e570 task.ti=f67a8000)
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: Stack: f7f616c0 f392c95c 00200286 f952c1b1 f67a9f30 00000001 00008913 f67a9f30
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:        c06603a7 c06548f0 f7048440 c06548f0 c0660ff1 bf93aa8c 00000000 c014f115
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: Call Trace:
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<f952c1b1>] aufs_nopage+0x61/0x100 [aufs]
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c06548f0>] sock_ioctl+0x0/0x210
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c06548f0>] sock_ioctl+0x0/0x210
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c0660ff1>] dev_ioctl+0x2c1/0x330
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c014f115>] __handle_mm_fault+0x235/0x960
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:        00001000 00200246 f68de000 fffffffe ffffff9c c016b3da f67a9f44 0804a341
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c06603a7>] dev_load+0x17/0x50
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c016b3da>] __user_walk_fd+0x3a/0x50
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c065499f>] sock_ioctl+0xaf/0x210
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c06548f0>] sock_ioctl+0x0/0x210
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c016c9ff>] do_ioctl+0x1f/0x70
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c016caa0>] vfs_ioctl+0x50/0x2c0
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c0102a90>] syscall_call+0x7/0xb
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c06d0000>] svc_sock_enqueue+0x210/0x2e0
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  =======================
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: Code: 00 90 8d 6a f0 b8 10 00 00 00 89 ee 89 df 89 c1 49 78 08 ac ae 75 08 84 c0 75 f5 31 c0 eb 04 19 c0 0c 01 85 c0 75 2d eb 33 66 90 <8b> 02 0f 18 00 90 8d 6a f0 89 ee 89 df b9 10 00 00 00 49 78 08
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel: EIP: [<c065e500>] __dev_get_by_name+0x90/0xe0 SS:ESP 0068:f67a9ecc
    
    Message from syslogd@(none) at Tue Dec 16 20:58:03 2008 ...
    (none) kernel:  [<c016cd72>] sys_ioctl+0x62/0x90
    
    bt ~ #

  2. #2
    Senior Member secure_it's Avatar
    Join Date
    Feb 2010
    Location
    在這兩者之間 BackTrack是4 FwdTrack4
    Posts
    854

    Default

    Don't put NIC in both monitor and managed mode at the same time and this problem also occurs when the card is scanning in monitor mode and cables becomes loose/ removed.

  3. #3
    Just burned his ISO
    Join Date
    Dec 2008
    Posts
    6

    Default

    I repeated my tests without cables, but I'm still getting error messages. Regarding the monitor/managed mode, I haven't been able to get that far.

    The commands airmon-ng, airmon-ng rausb0 stop, ifconfig, iwconfig cause segmentation faults. I tested each command individually (allow BT3 to boot fully, connect adapter, enter command, segmentation fault, reboot)

    Are there any other commands I should try which might provide a clue of what's going wrong?

  4. #4
    Senior Member secure_it's Avatar
    Join Date
    Feb 2010
    Location
    在這兩者之間 BackTrack是4 FwdTrack4
    Posts
    854

    Default

    update drivers for your rt73 chipset based usb nic from
    http://homepages.tu-darmstadt.de/~p_larbig/wlan/
    and try again.

  5. #5
    Member
    Join Date
    Sep 2008
    Posts
    306

    Default

    Quote Originally Posted by secure_it View Post
    update drivers for your rt73 chipset based usb nic from
    http://homepages.tu-darmstadt.de/~p_larbig/wlan/
    and try again.
    See:
    I also tried the enhanced drivers, but no luck.
    @digitalbob

    I use the same one , and everything works fine with it.

    Even if your stick runs under windows , it maybe that your adapter crashes at some point with the linux drivers.
    My assumption is, anyway there's any failfunction with your adapter.
    Do you have any other boot cd like ubuntu or something? Does it work there?
    Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:

    * post your question to a forum where it's off topic
    * post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
    * cross-post to too many different newsgroups
    * post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem

  6. #6
    Just burned his ISO
    Join Date
    Dec 2008
    Posts
    6

    Default

    secure_it and terminal86, I appreciate the input you have provided..

    update drivers for your rt73 chipset based usb nic from
    hxxp://homepages.tu-darmstadt.de/~p_larbig/wlan
    I did this at one point, but still had a fault message. However, I will try it again and repeat the tests I mentioned in my previous posts.

    Do you have any other boot cd like ubuntu or something?
    I just tried the kubuntu live cd. According to KNetwork manager, the internal card detects around 10 APs, and the USB NIC shows only 3 APs. (My router appears on both).
    I entered my WPA key, and was able to connect to my router.

    It appears the USB NIC is operational, but I don't know why so few APs were detected.

    I'm getting ready for a trip, but I will check this message thread every couple of days and will post the results of any other tests I perform.

  7. #7
    Just burned his ISO
    Join Date
    Dec 2008
    Posts
    6

    Default

    I am no longer getting segmentation faults. I was running my laptop with it's native OS (WinXP) for the past two days. I booted BT3 CD today, and the commands which were previously crashing my system are now working fine.

    Correct me if I'm wrong. I was under the assumption that a Live CD does not leave data on your hard drive. It appears that after my initial crash, some data was retained. (possibly due to an incomplete shutdown.) This data may have been carried over to the next reboot. I'm guessing that my use of XP may have finally deleted that data, and allowed a proper boot of BT3.

    My next issue is now a failure to authenticate. I will look through the forums to figure this one out.

    I'd like to keep this thread open for another week as I'd like to document how I finally get this USB NIC to work....

Posting Permissions

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