PDA

View Full Version : Is my CPU compatible with BT5?



yomama07024
05-13-2011, 02:26 PM
I was able to use all previous versions of BT on this computer, but when I pit the 32-bit KDE version to boot from my flash drive and I boot up, I get an error saying "This kernel requires an x86-64 CPU, but only detected an i1686 CPU. Unable to boot - please use a kernel appropriate for your CPU". I have an Intel Core Duo T2050. Can I run Backtrack 5 on this computer anymore?

yomama07024
05-13-2011, 02:54 PM
Why does it give me that error, but when I run Backtrack 5 from a DVD instead of booting off a flash drive, it works just fine?

So BT5 works flawlessly when booting it off the DVD. When I try to boot off my flash drive using the same exact 32-bit image, I get that error that I wrote up above. Why is this?

yomama07024
05-13-2011, 04:16 PM
ok so its an install error to usb or setting go into to your bios and check the settings
also try unetbootin

http://unetbootin.sourceforge.net/unetbootin-linux-latest linux version
http://unetbootin.sourceforge.net/unetbootin-windows-latest.exe windows version

Thank you, sir! I am trying that right now. I was using Universal USB Installer. I'll post back in a few minutes letting you know if it worked.

yomama07024
05-13-2011, 04:20 PM
Where to I save file to when using persistence?
Can I save them on the desktop and the next time I boot, they'll still be there?

While booting, it says:
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) Can not mount /dev/loop0 (/cdrom/casper/filesystem.squashfs) on //filesystem.squashfs

What does this mean?

enrekansugik
05-13-2011, 04:47 PM
While booting, it says:
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) Can not mount /dev/loop0 (/cdrom/casper/filesystem.squashfs) on //filesystem.squashfs

What does this mean?


I had same error message when boot from USB ThumbDrive "create by using UNetbootin".

yomama07024
05-13-2011, 05:18 PM
it means it didnt install properly ive had this numerous times format the usb to fat 32 and try again

when uisng lil usb creator in section 4 tick the persistant box and select how much space you want

unetbootin can be very buggy i found lili usb creator more dependable also universal usb creator is also ok but still can be as buggy as unetbootin


r083rt

For some reason, after I got that message, now my computers doesn't recognize my flash drive. In Windows, it makes a sound when I plug my flash drive in, but it doesn't appear in My Computer or Disk Management. My other computer doesn't recognize my flash drive either. Why could this be?

yomama07024
05-13-2011, 05:39 PM
partitons are messed up delet all partitions use fdisk in linux
fdisk -l
select your usb xxxx
fdisk /dev/xxxx
press d then 1
press d then 2
press d then 3
press w and enter

in windows use disk manager and delete all partitons on your usb

format the usb

r083rt

Windows doesn't see it at all in Disk Management. It's like nothing is plugged in. I do hear the sound Windows makes though when I plug the flash drive in. So how can I format it? If the flash drive is plugged in when I turn on my computer, my computer just hangs at the BIOS screen until I take the flash drive out and then it boots right up.

yomama07024
05-13-2011, 05:51 PM
http://www.mediafire.com/?cod0xwroarte3d9

copy that to the C:\windows\inf directory

unplug usb and plug back in

reason:the usb inf is deleted off the usb so it cant be loaded

you gave me a link to download linuxlive usb creator. you want me to put that exe in the inf directory?

yomama07024
05-13-2011, 05:54 PM
fyi, in device manager, this is what it looks like when i plug the flash drive in. i tried disabling the driver, uninstalling the driver and letting windows install it again but nothing worked. i'm sure it's some corrupt data on the flash drive but how can i delete it lol

http://i51.tinypic.com/ncmdeq.png

yomama07024
05-13-2011, 06:37 PM
quick answer f*** it in the bin :) just kidding oh nooooooooooooooooooo windows ahhhhhh my head is starting to hurt you need to delete registry keys for the usb so the usb keys can be reinstalled when its plugged back in and which keys are these lol I cant remember all the workarounds its been a while and the windows part of my brain has died sorry mate you can google for the answer

or just burn the iso to dvd drive and boot into bt5 and use fdisk and delete partitions and reformat the usb
if you dont have a dvd drive hmmm i suppose ill ransack my brain for the solution or find a tool that will reinstate the files onto the usb


r083rt

It seems that Linux doesn't recognize it either, though. How can I check to see if Linux recognizes the flash drive?

r083rt
05-13-2011, 06:57 PM
fdisk -l


this will show all usb and hardrives

yomama07024
05-13-2011, 07:00 PM
fdisk -l


this will show all usb and hardrives

I tried that and it didn't show up

yomama07024
05-13-2011, 08:18 PM
hmmm you broke it :) my head is fried let me think theres a way around it it happend me a couple of ytimes with usb need to think ill go an get a cup of tea and try to remember

its a real simple fix lol but for the life of me I cant rememer


r083rt

Thanks very much. Please get back to me with that solution!

yomama07024
05-14-2011, 03:31 AM
Any news, r083rt?

r083rt
05-14-2011, 03:43 AM
modprobe usb-uhci
modprobe usb-ohci
modprobe usb-storage

run dmesg


dmesg


you show get some output like this



Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 78242976 512-byte hdwr sectors (40060 MB)
sdb: assuming drive cache: write through
SCSI device sdb: 78242976 512-byte hdwr sectors (40060 MB)
sdb: assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: Attached scsi disk sdb
usb-storage: device scan complete


now lets


fdisk -l | grep sdb (sdb is the output yours might be differnet check the output of dmesg)


output


Disk /dev/sda doesn't contain a valid partition table
Disk /dev/sdb: 40.0 GB, 40060403712 bytes
/dev/sdb1 1 4870 39118243+ c W95 FAT32 (LBA)



now mount the usb



mount /dev/sdb1 /mnt


note (sdb1)maynot be yours it just an example

then do as above delete the partitons and format

r083rt

yomama07024
05-14-2011, 08:36 PM
when i type modprobe usb-uci, it says FATAL: Module usb_uhci not found. and the same thing happens when i type modprobe usb-ohci. when i type modprobe usb-storage, it says nothing and just goes to another line so i can type a new command. when i type dmesg, it says a bunch of stuff but i just copied the end where it mentions usb. this is what it says:


4061.848954] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4061.932266] b44 ssb1:0: eth0: powering down PHY
[ 4061.946023] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4062.999895] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4071.156073] usb 1-1: device not accepting address 2, error -110
[ 4071.156155] usb 1-1: USB disconnect, address 2
[ 4071.156189] scsi 2:0:0:0: Device offlined - not ready after error recovery
[ 4071.268089] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 4074.480776] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4074.556263] b44 ssb1:0: eth0: powering down PHY
[ 4074.570072] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4074.720105] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4077.208834] wlan0: authenticate with 00:1c:10:31:b8:6e (try 1)
[ 4077.210461] wlan0: authenticated
[ 4077.210794] wlan0: associate with 00:1c:10:31:b8:6e (try 1)
[ 4077.212889] wlan0: RX AssocResp from 00:1c:10:31:b8:6e (capab=0x411 status=0 aid=2)
[ 4077.212897] wlan0: associated
[ 4077.214532] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 4086.380100] usb 1-1: device descriptor read/64, error -110
[ 4087.888044] wlan0: no IPv6 routers present
[ 4101.596116] usb 1-1: device descriptor read/64, error -110
[ 4101.812100] usb 1-1: new high speed USB device using ehci_hcd and address 4
[ 4116.924056] usb 1-1: device descriptor read/64, error -110
[ 4132.140067] usb 1-1: device descriptor read/64, error -110
[ 4132.360073] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 4142.768064] usb 1-1: device not accepting address 5, error -110
[ 4142.880083] usb 1-1: new high speed USB device using ehci_hcd and address 6
[ 4153.288071] usb 1-1: device not accepting address 6, error -110
[ 4153.288108] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 4153.556083] usb 2-1: new full speed USB device using uhci_hcd and address 2
[ 4168.668083] usb 2-1: device descriptor read/64, error -110
[ 4183.884082] usb 2-1: device descriptor read/64, error -110
[ 4184.100106] usb 2-1: new full speed USB device using uhci_hcd and address 3
[ 4199.212062] usb 2-1: device descriptor read/64, error -110
[ 4214.428091] usb 2-1: device descriptor read/64, error -110
[ 4214.644082] usb 2-1: new full speed USB device using uhci_hcd and address 4
[ 4225.052070] usb 2-1: device not accepting address 4, error -110
[ 4225.164074] usb 2-1: new full speed USB device using uhci_hcd and address 5
[ 4235.572046] usb 2-1: device not accepting address 5, error -110
[ 4235.572084] hub 2-0:1.0: unable to enumerate USB device on port 1


So is this good or bad? What do I do from here?

loudbird
09-02-2011, 05:26 PM
Where to I save file to when using persistence?
Can I save them on the desktop and the next time I boot, they'll still be there?

While booting, it says:
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) Can not mount /dev/loop0 (/cdrom/casper/filesystem.squashfs) on //filesystem.squashfs

What does this mean?

Did someone tell me how i can resolve this problem?

tonyITa
09-11-2011, 06:17 AM
Squashfs its a highly compressed system, the warning meaning it could not decompress the file and mount during start up.
You should prepare the USB to install the ISO. Meaning you need to format it so it will boot, personally I used YUMI, the windows version, note some version of YUMI are old and dont support BT5, this one worked for me, even I used a microsd card.
Yumi offers the option to format the USB stick.
Also it's important to check the checksum of the ISO. Also if you have problems after installation with your CPU, look using synaptic for Intel Microcode, which updates the microcode during boot, when starting the devices.

http://www.pendrivelinux.com/yumi-multiboot-usb-creator/

Anonymous0
12-22-2012, 09:58 PM
Greetings,
The Problem is not with the Linux. Its with BIOS. I had this problem too. What you need to do is Just Start The BIOS and then according to what Mother Board you are using you will have to ENABLE "Virtualization Tech". It is disabled for many computers as a result it give that error. Check Out Google on how to do It according to your Board.
Hope this Helps.