Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
Hi,
I have Ubuntu 18.04 LTS on VirtualBox and during flashing RDV4 with the newest files from repo I can't reconnect to RDV properly.
Waiting for a response from proxmark.
I see proxmark is reconnecting to Ubuntu (switched off, pressed button, connected, released button), but there is no new action in terminal.
Regards,
PS. I cannot add screens yet nor text from Ubuntu (due to well-known clipboard problem with Ubuntu).
Offline
I prepared ProxSpace env with my W10 and it seems be working fine everything so we can forget it
If someone has answer I would appreciate it.
Thx in advance!
Regards,
Offline
A bit too little information to go on.
...are your virtual machine able to see usb devices? ie is it configured correct?
...did you install the blacklist rules? .... as instructions says https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux
sudo cp -rf driver/77-mm-usb-device-blacklist.rules /etc/udev/rules.d/77-mm-usb-device-blacklist.rules
sudo udevadm control --reload-rulesAdd user to dialout group. If you do this one, you need to logout and login in again to make sure your rights got changed.
sudo adduser $USER dialout
Offline
Hi Iceman,
too little, because it was so clear as a day
Yes, I see device, because I can compile app and connect to pm3.
Yes, blacklist step was also done as instruction said.
Last edited by szymonunion (2018-12-05 09:31:58)
Offline
Good, I suggest you edit your first post and add the prefix [solved] to your title
Offline
Iceman,
no no. Not solved. I can connect by already compiled client, but flashing is still not working under Ubuntu.
Everything from the beginning was done as instruction said.
I wrote in 1st post what the problem is (under Ubuntu).
Offline
Strange, Dunno if its a virtulbox issue. I run my ubuntu's on vmware without problems.
Which steps are you doing when you are trying to flash in ubuntu on virtualbox?
Offline
You should check `dmesg` to see if your device is being assigned a different port.
I've often seen it available on the correct port (eg, /dev/ttyACM0) but when rebooting modes, it will be assigned a different port (eg, /dev/ttyACM1), and then it's obviously not reachable.
You can safely SIGKILL and re-issue it on the correct port.
Offline
I haven't used VirtualBox in a while, but I remember USB issues before. Since even in a hardware install of Linux the device will sometimes change to a new port, this issue will also occur on VirtualBox. It may also be that it no longer sees the PM3 as the same device, and you may need to reassign the "new" device (in flash mode) to the virtual machine before Linux will see it and can flash it.
Offline
Hi,
in dmesg it was always seen as /dev/TTYACM0. I even used option to always connect directly proxmark by USB to guest machine (Ubuntu) not to the host. During flashing I am putting out USB and putting in and from this time flashing process is not able to see my device. With ProxSpace it works like a charm.
Offline
I still suspect the issue is in the virtualization and/or USB forwarding for the virtual machine. It may very well be that it takes too long to populate and the device may drop out of bootloader/flashing mode and back into operating mode during this period of time.
I can confirm that this issue did not present when connecting the PM3 to a Ubuntu installation (16.04 or 18.04) on physical hardware. I have done this numerous times with multiple devices with only one likely unrelated issue.
The issue I experienced was that one device (PM3 Easy) became unresponsive following a bootloader flash. Resolution of the issue I experienced only required that the PM3's button be held starting before connecting the device. In my case, the button had to be held until the fullimage flash was completed. I don't know if the resolution for my issue might help for this as well, but it's worth a try.
Offline
Thx for answer. I will test it in a moment...
OK, tested. Not working.
During reflash it is reconnecting to /dev/ttyACM1, but flasher is waiting for /dev/ttyACM0.
Fortunately with the newest version of software I can recompile/flash my RDV4 with success with ProxSpace.
Last edited by szymonunion (2018-12-12 18:09:58)
Offline
Changing device names is not uncommon when trying to flash. I'm not sure if this is due to some kind of change in the USB descriptor when the device is seen in bootloader/flash mode or if there's something else going on, but I've seen it change occasionally, too. When that happens, the only real solution is to break out of the application and re-issue the flash command with the new device name.
Offline
Pages: 1