Where it came from was a search of Google for info on getting the WLAN up and running
on a Dell 4800 running Linux.
As for why I am not using the Kali Repository, from what I can tell the...
Type: Posts; User: village_idiot
Where it came from was a search of Google for info on getting the WLAN up and running
on a Dell 4800 running Linux.
As for why I am not using the Kali Repository, from what I can tell the...
Have installed Kali 2019.1 on bootable flash with persistency.
Now trying to load Broadcom Wireless Driver but no joy.
Installed dkms using package: dkms_2.6.2-4_all.deb (dpkg -i...
Rufus and a couple of others seem to use their own method of creating a bootable flash.
I found if you DD the Kali ISO to the USB drive it does not hunt for the CD during the
installation to a hard...
Thanks for the heads up on restarting the computer. Had been in a continuous loop
trying to find out why the drivers where not working after installation. Read your
note, tried it and Voila _...
I am running Kali from a bootable flash drive and running into a couple of problems.
First is the default Bluetooth card in the Dell M4800 does not appear to be working properly.
Three or four...
Can btmon be used in a passive mode to monitor
bluetooth traffic? It works when actively sending
the GIAC (General Inquiry Access Code0 and
responses to the GIAC are shown. However
unless I am...
Did you ever determine where 'bluemaho' wandered off?
I downloaded it to 2016.1 and it launches the GUI but
several of the functions are producing error messages
such 'Set BD Address', or the Play...
Followup on the bluetooth naming issue.
1 Linux creates the Bluetooth Device Name at boot and assigns the name to the Bluetooth Device.
2 If more than one Bluetooth Device is attached at boot...
Have been going in circles with the 'hciconfig' tool.
Using 'hciconfig -a hci0 name whacko' does not
change the device name. When monitoring the
device with 'btmon' the old device name continues...
I decided to upgrade to Bluez-5.38 from 5.36. It mentioned a
few items which had been a problem for me such as OBEX
and others.
Following the upgrade I checked the current version using
the...
When running bluefogger I noticed the alias is being changed on the local system
however on a remote device (in this case a Samsung phone) when the phone
displays the devices identified during a...
More notes on the booting issue.
I received an order of flash drives direct from PNY yesterday afternoon.
A 32 GB USB 3.0 drive was selected for the test. The test would be to
dd the Kali 2016...
Noah I have had no end of problems creating bootable flash drives with recent distributions
of varied Linux flavors. I have tried different brands of flash drives and even different models
within...
Anyone with experience with blueranger.sh that is willing to share
info on problems encountered please rattle my cage. I can see
numerous addresses but using blueranger or even l2ping results in...
Quick Followup
I ran a checksum on each of the partitions on
each of the two drives. There are two partitions
displayed on each drive when running fdisk -l
They are
/dev/sdc1 * ...
I have been having similar problems. The bootable pen drive
seemed to load properly but when attempting to use it as
a boot device it would either bypass the device during the
boot process or...
When the install balks about the CD/DVD not being found,
pull the pen drive out, wait ten seconds and reinsert the
pen drive. Again wait ten seconds and then select 'Continue'.
I found this...
Wunderbar. Unfortunately I have to admit it is likely the simplest solution.
Having same roadblock here.
'apt-get dist-upgrade' is run after apt-get update per the
recommended procedure and is the step for me where
the upgrade breaks down. Looked at dmesg output and ...
I am using a Dell M6500 laptop with a Broadcom
chipset (BCM2046B1) for Bluetooth. Use of various
tools and apps have raised questions which seem
to elude me and hopefully someone can clarify.
...
Your link displays that the Bluetooth device is
a Dell Wireless 370 Bluetooth Minicard, v.6.2.0.9603,
A02-1 proprietary device.
Does 'lsusb' reveal a Bluetooth device attached?
You should see...