I took the development release for a spin - VirtIO not working, so it's not possible to run BT in a KVM/VirtIO virtual environment
Backtrack must be one of the only Linux distributions left, which doesn't support VirtIO out-of-the-box. Ubuntu/Fedora/CentOS/OpenSuse/ArchLinux/[lots of other distributions] all supports VirtIO out-of-the-box, to allow installation onto virtual VirtIO block devices, use of VirtIO NICs, etc.
Essentially, these are the missing modules:
- CONFIG_VIRTIO_PCI=m (Virtualization -> PCI driver for virtio devices)
- CONFIG_VIRTIO_BALLOON=m (Virtualization -> Virtio balloon driver)
- CONFIG_VIRTIO_BLK=m (Device Drivers -> Block -> Virtio block driver)
- CONFIG_VIRTIO_NET=m (Device Drivers -> Network device support -> Virtio network driver)
- CONFIG_VIRTIO=m (automatically selected)
- CONFIG_VIRTIO_RING=m (automatically seleced)
There is no disadvantage in enabling these modules, it will not conflict with Vmware or other modules.
The modules should also be included in the initramfs to allow booting from VirtIO block devices.
It would be highly appreciated if you could fix this, I'll be more than happy to help out with testing if you need a tester...
one solution to all problems is to move out of intrepid and go into lucid
I have to agree with you Purehate, moving to Lucid is just not the answer.
duh I know its hard, but without it backtrack is just fail, updating packages is a bitch, ah dam they dont have it in the repo...
and when it comes to new hardware, backtrack fails again
Just got to form another team of developers
yea and i know we still need a custom kernel, that only to fix injection for wireless
Seem to be having issues with promisc mode with the WUSB54GC which works fine in BT4F.
Tested on netbook Samsung N110, promisc mode and injection working fine with the built-in Atheros chipset.
EDITCode:root@bt:~# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 011: ID 13b1:0020 Linksys WUSB54GC 802.11g Adapter [ralink rt73] Bus 001 Device 004: ID 0ac8:c326 Z-Star Microelectronics Corp. Bus 001 Device 003: ID 13fe:3100 Kingston Technology Company Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth root@bt:~# airmon-ng Interface Chipset Driver wlan0 Atheros ath5k - [phy0] wlan1 Ralink 2573 USB rt73usb - [phy3] root@bt:~# airmon-ng start wlan1 Interface Chipset Driver wlan0 Atheros ath5k - [phy0] wlan1 Ralink 2573 USB rt73usb - [phy3]SIOCSIFFLAGS: No such file or directory (monitor mode enabled on mon0) root@bt:~# airmon-ng Interface Chipset Driver wlan0 Atheros ath5k - [phy0] wlan1 Ralink 2573 USB rt73usb - [phy3] mon0 Ralink 2573 USB rt73usb - [phy3] root@bt:~# aireplay-ng -9 mon0 ioctl(SIOCSIFFLAGS) failed: No such file or directory root@bt:~#
the WUSB54GC does not work at all, get the same error message when trying to 'up' the interface.
Last edited by TAPE; 05-20-2010 at 04:49 PM.
1024x600 on Intel 3150... ? Thx
Would you please offer us a special copy of the kernel, which is compiled without PAE ?
My old laptop with a Dothan CPU cannot boot the new bt4 r1, due to the lack of PAE feather. And I really wan't to test this new version on my poor laptop.
we would have to wait until nl80211 is out of development, ath5k/ath9k are totaly broken