Results 1 to 2 of 2

Thread: win32 live usb not working

  1. #1
    Join Date
    2014-Jul
    Posts
    1

    win32 live usb not working

    I followed the sites documentation and whenever I boot into USB it gets stuck. There is a spades symbol and a blinking dash on the bottom. I formatted USB to FAT32 and wrote the 64bit ISO file on to it.

    I also have Ubuntu but the sites documentation is very vague. "Verify usb location with dmesg". I don't know what the **** that is.

    Can someone, in noobish terms, explain to me how to solve this?

  2. #2
    The "dmesg" command is to "print or control the kernel ring buffer" (which is useful to show "driver messages" - which is information about the hardware thats connected, been disconnected and any errors since boot).
    For more information: http://www.linuxnix.com/2013/05/what...to-use-it.html
    Man(ual) page: http://unixhelp.ed.ac.uk/CGI/man-cgi?dmesg+8



    1.) Plug in your USB device to your Linux computer’s USB port.
    2.) Verify the device path of your USB storage with dmesg.
    3.) Proceed to (carefully!) image the Kali ISO file on the USB device:
    Source: http://docs.kali.org/installation/ka...ve-usb-install



    By using dmesg, you can see if the USB stick is working correctly and the OS is able to use it.

    e.g. everything thats "USB" related (hubs, devices - mouse/keyboard, as well as the USB stick).
    Code:
    root@kali ~$ dmesg | grep -i usb
    [    0.945553] ACPI: bus type USB registered
    [    0.945631] usbcore: registered new interface driver usbfs
    [    0.945690] usbcore: registered new interface driver hub
    [    0.955804] usbcore: registered new device driver usb
    [    0.956364] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [    0.957603] ehci-pci 0000:02:04.0: new USB bus registered, assigned bus number 1
    [    0.958974] uhci_hcd: USB Universal Host Controller Interface driver
    [    0.983308] ehci-pci 0000:02:04.0: USB 2.0 started, EHCI 1.00
    [    0.983515] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [    0.983856] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.983945] usb usb1: Product: EHCI Host Controller
    [    0.984005] usb usb1: Manufacturer: Linux 3.14-kali1-amd64 ehci_hcd
    [    0.984074] usb usb1: SerialNumber: 0000:02:04.0
    [    0.986571] hub 1-0:1.0: USB hub found
    [    0.988054] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
    [    0.988703] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
    [    0.988784] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.988881] usb usb2: Product: UHCI Host Controller
    [    0.988947] usb usb2: Manufacturer: Linux 3.14-kali1-amd64 uhci_hcd
    [    0.989030] usb usb2: SerialNumber: 0000:02:00.0
    [    0.989244] hub 2-0:1.0: USB hub found
    [    1.302485] usb 2-1: new full-speed USB device number 2 using uhci_hcd
    [    2.225050] usb 2-1: New USB device found, idVendor=0e0f, idProduct=0003
    [    2.225135] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    2.225209] usb 2-1: Product: VMware Virtual USB Mouse
    [    2.225270] usb 2-1: Manufacturer: VMware
    [    2.341304] usb 2-2: new full-speed USB device number 3 using uhci_hcd
    [    2.478668] usb 2-2: New USB device found, idVendor=0e0f, idProduct=0002
    [    2.478784] usb 2-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
    [    2.478888] usb 2-2: Product: VMware Virtual USB Hub
    [    2.484874] hub 2-2:1.0: USB hub found
    [    2.506435] usbcore: registered new interface driver usbhid
    [    2.506541] usbhid: USB HID core driver
    [    2.508974] input: VMware VMware Virtual USB Mouse as /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/0003:0E0F:0003.0001/input/input2
    [    2.509331] hid-generic 0003:0E0F:0003.0001: input,hidraw0: USB HID v1.10 Mouse [VMware VMware Virtual USB Mouse] on usb-0000:02:00.0-1/input0
    [28515.487120] usb 1-1: new high-speed USB device number 2 using ehci-pci
    [28515.786591] usb 1-1: New USB device found, idVendor=1b1c, idProduct=1ab1
    [28515.786597] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [28515.786600] usb 1-1: Product: Voyager
    [28515.786602] usb 1-1: Manufacturer: Corsair
    [28515.786604] usb 1-1: SerialNumber: AA00000000000xxx
    [28515.883320] usb-storage 1-1:1.0: USB Mass Storage device detected
    [28515.883466] scsi3 : usb-storage 1-1:1.0
    [28515.883831] usbcore: registered new interface driver usb-storage
    [28703.960047] usb 1-1: USB disconnect, device number 2
    [28704.783145] usb 1-1: new high-speed USB device number 3 using ehci-pci
    [28705.079561] usb 1-1: New USB device found, idVendor=1b1c, idProduct=1ab1
    [28705.079567] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [28705.079570] usb 1-1: Product: Voyager
    [28705.079572] usb 1-1: Manufacturer: Corsair
    [28705.079574] usb 1-1: SerialNumber: AA00000000000xxx
    [28705.092174] usb-storage 1-1:1.0: USB Mass Storage device detected
    [28705.092652] scsi4 : usb-storage 1-1:1.0
    [28706.226567] usb 1-1: USB disconnect, device number 3
    [28737.514216] usb 1-1: new high-speed USB device number 4 using ehci-pci
    [28737.810107] usb 1-1: New USB device found, idVendor=1b1c, idProduct=1ab1
    [28737.810112] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [28737.810114] usb 1-1: Product: Voyager
    [28737.810115] usb 1-1: Manufacturer: Corsair
    [28737.810116] usb 1-1: SerialNumber: AA00000000000xxx
    [28737.821727] usb-storage 1-1:1.0: USB Mass Storage device detected
    [28737.821862] scsi5 : usb-storage 1-1:1.0
    root@kali ~$
    You can see a huge jump in the numbers on the left hand side. The first lower set of numbers relates to when the machine was starting up. The numbers at the end, is when I plugged in the USB stick.






    Other useful USB commands (lsusb & mount):
    * lsusb - lists all USB devices
    * mount - mount filesystems (used to show the path of the partation on the device on the OS - e.g. /dev/sdb1)
    Code:
    root@kali ~$ lsusb
    Bus 001 Device 005: ID 1b1c:1ab1 Corsair 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
    Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    root@kali ~$ mount                                                                                                                                                       
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=254823,mode=755)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=205896k,mode=755)
    /dev/disk/by-uuid/5ade5368-9e6c-42ae-b136-8d711f547570 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
    tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
    tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1100320k)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
    /dev/sdb1 on /media/Kali Live type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks)
    root@kali ~$ mount | grep '/dev/s'
    /dev/sdb1 on /media/Kali Live type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks)
    root@kali ~$


    ...For even more commands: https://forums.kali.org/showthread.p...ll=1#post32652

    Quote Originally Posted by retraction View Post
    ...whenever I boot into USB it gets stuck. There is a spades symbol and a blinking dash on the bottom.
    This could be happening for any number of reasons. Without more information, its hard to say why.







    Please note:
    Kali is a Linux distribution specifically geared towards professional penetration testing and security auditing and as such, it is NOT a recommended distribution for those unfamiliar with Linux.
    Source: http://docs.kali.org/introduction/sh...use-kali-linux
    Last edited by g0tmi1k; 2014-07-08 at 09:25.
    This is a Kali-Linux support forum - not general IT/infosec help.

    Useful Commands: OS, Networking, Hardware, Wi-Fi
    Troubleshooting: Kali-Linux Installation, Repository, Wi-Fi Cards (Official Docs)
    Hardware: Recommended 802.11 Wireless Cards

    Documentation: http://docs.kali.org/ (Offline PDF version)
    Bugs Reporting & Tool Requests: https://bugs.kali.org/
    Kali Tool List, Versions & Man Pages: https://tools.kali.org/

Similar Threads

  1. win32-loader.ini not found
    By mokhethiblogger in forum Installing Archive
    Replies: 0
    Last Post: 2020-03-18, 11:37

Posting Permissions

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