Results 1 to 6 of 6

Thread: Widescreen resolution issues and 3945 aircracking weirdness.

  1. #1
    Just burned his ISO
    Join Date
    Feb 2008
    Posts
    4

    Default Widescreen resolution issues and 3945 aircracking weirdness.

    Hey, noob crap obviously, but I searched the forums and found no answers so here I am. Firstly I'm using a Gateway NX5600 laptop with an ATi x1400 card, and the only way to even get X to start is to boot in vesa mode, even after doing a xorgconfig or xconfig. In vesa mode however, I cannot use any resoultion above 1024x768, which looks a tad off on my widescreen 1280x800 screen. I have the ati.lzm sitting in the modules directory and it does not help either of those issues, any clue how to fix this?

    Secondly using aircrack with the ipw3945 *kinda* works as detailed in another post in the forum, but unlike in the tutorial on getting injection to work from this forum, there is some weirdness going on with the injection. The card is in monitoring mode, and everything works fine including the fakeauth attack. Airodump sees the two resulting packets from the successful fakeauth fine as well, but when I try to do the aireplay -3 attack, it acts like it is working, but no matter how many packets it reads it never gets any ACK or ARP reads. Similarly no packets get intercepted by Airodump. Any clue whats up with that? Using the aireplay -3 -b macaddytarget -h mymacaddy wifi0.

  2. #2
    Junior Member
    Join Date
    Nov 2007
    Posts
    36

    Default

    Yes. Here is a link to the exact steps I took to resolve this same issue on my Gateway m285.

    http://forums.remote-exploit.org/sho...highlight=m285

    And here is a link to a slight issue I had when I upgraded to BT3b

    http://forums.remote-exploit.org/sho...highlight=m285

  3. #3
    Just burned his ISO
    Join Date
    Feb 2008
    Posts
    4

    Default

    Thanks for the advice... funny thing is though, is that I'm using a liveusb, not an installation? do I really need to go through the process of installing the ati drivers and restarting and reconfiguring x every time I want to use backtrack..?

  4. #4
    Junior Member
    Join Date
    Nov 2007
    Posts
    36

    Default

    How about making your changes to the USB drive persistent?

  5. #5
    Jenkem Addict imported_wyze's Avatar
    Join Date
    Jul 2007
    Posts
    1,543

    Default

    Quote Originally Posted by prelate View Post
    How about making your changes to the USB drive persistent?
    Read the wiki
    dd if=/dev/swc666 of=/dev/wyze

  6. #6
    Junior Member
    Join Date
    Nov 2007
    Posts
    36

    Default

    Quote Originally Posted by swc666 View Post
    Read the wiki
    Here you go (direct from the Wiki). According to Re@lity in my original post about this issue there is an ATI.lzm.


    WIKI:

    Save configuration to USB stick
    After having produced the personalization, open the console and digit dir2lzm /mnt/live/memory/changes changes.lzm (changes.lzm or pippo.lzm ...) changes.lzm you have in root folder, paste in USB modules folder (BT/modules). Reboot you have saved setting up. -bzImage

    There is an issue after you save to changes.lzm and boot from the module then make new changes and try to save them because you only get the new changes and not the previous. Then create new changes and have to save them. Seems you have to copy /mnt/live/memory/changes to a tmp dir then merge /mnt/live/memory/images/changes.lzm/ onto the tmp dir. Then turn that into a new module to load. -Kinchyle

    If you make a subsequent change, you can just save the new change.lzm file in the /BT/modules folder using a different name: ie change1.lzm and change2.lzm and then a subsequent file called change3.lzm all without merging them. -Milon

Posting Permissions

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