I'm having some problems with fingerprint reader on Thinkpad T430 ID 147e:2020 Upek
For few days i was trying every tip i could find but it didn't work for me.
Mainly i tried to Build and make it running through Fingerprint GUI and i was able to build it and install it properly (after few fixes) but it simply was not able to pick up my device.
At one point i thought that i have solution, since i realized that Fingerprint sensor on this laptop is quite new and is maybe not supported by default with proprietary libbsapi.so so i tried to follow tips from this blog: http://volker.de/2012/12/fingerprint-gui-und-das-thinkpad-t430s/
Guy has exactly same device and in same PC but as i expected it didn't work for me.
Platform is Debian-squeeze
If you have any idea what could be solution, pls help.
Used the same info as you did, but a quick look at the French Ubuntu doc did the fix for me: the problem appears to be that the fingerprint-gui doesn't have access to the USB device bus, thus, we have to give it to it.
Find your device's bus and device adress using the lsusb command, for me, it was:
Bus 001 Device 003: ID 147e:2020 Upek
Thus the bus is 001 and the device is 003. Let's call them x and y.
Then, we use chmod (apparently it doesn't pose any security threat as the system fixes it by itself):
sudo chmod 666 /dev/bus/usb/00x/00y
For me, for instance, it was:
sudo chmod 666 /dev/bus/usb/001/003
Then, follow the instructions given to you by the German guy (volker - the link you cited).
On my side, I was running Ubuntu 12.04 (debian bro'), so I could use the fingerprint PPA. I don't know if Ubuntu PPA's work on debian. I suggest you keep your own install of the fingerprint-gui program, as well as the fix provided by volker's blog post. Then, just launch fingerprint-gui and it should recognize you device.
The German blog got actually updated was a problem with the quotes:
For non german users:
Be aware to use the copy and paste funktion to insert the above lines in your 40-libbsapi.rules, because the quotes are different from that quotes that you get when hitting on your keyboard.
It was pain in the a….. to find it out.
You'll need to apply this patch to libfprint.
Related
I started this project with a Raspberry Pi, but realized that the Banana's hardware set is a much better fit for what I'm doing. Unfortunately, it appears that, even though LeMaker (the group behind the BPi) offers just about every OS imaginable pre-optimized for the Banana, only Bananian supports all the hardware that I need, and it doesn't come with a GUI of any kind.
So, given a Debian-derivative on an ARM chip that will never see a physical display and has root SSH functional by default, how can I make it boot to an auto-logged-in VNC server?
Here's what I've done so far, as root over SSH:
# bananian-config
# bananian-update
# apt-get update
# apt-get upgrade
# adduser pi
# passwd root
# apt-get install task-lxde-desktop
(the first two are announced in the SSH welcome message and are used to initially setup the generic image for this variation of the board)
Then I uncommented these lines in /etc/lightdm/lightdm.conf:
autologin-user=pi
autologin-user-timeout=0
[VNCServer]
enabled=true
command=Xvnc
port=5900
width=1024
height=768
depth=8
At this point, I rebooted and tried to connect with VNC, but the client gave the same error as when the server doesn't exist. SSH still works as root and now the "pi" user also, except that the "pi" user doesn't know sudo.
At this point, I'm lost. I don't know if there's a desktop waiting for me on the HDMI plug or not, or whether I need an explicit VNC server like x11vnc or tightvnc, or if there's something else wrong.
This is all I've done so far. I can re-flash the image if needed; I want to make this part work before adding anything project-specific.
Okay, I noticed in LeMaker's own instructions to make Wifi work that they included Android and Lubuntu too, and that someone on their forum had made VNC work on Lubuntu. I didn't see before that some other OS's would support the WiFi chip.
So I switched to Lubuntu, which already has a working desktop, installed x11vnc per its instructions, and it basically just worked.
Then I backed up the SD card and spent all of Saturday trying different ways to make it a WiFi access point, which usually resulted in kicking myself out and restoring the backup to try again. And finally that works too. So I backed up the card again and now I can work on the real functionality.
I am looking for a way to store a script on a USB flash drive that will be executed she the device is inserted in a computer.
It should be a script that keep the files on my USB key up to date with their source on the web.
I have identified two main issues :
Security issue
Platform agnostic issue: may be easily solved by a test of the platform
Can anyone give me a hint for my research?
Thanks
That is impossible on the newer versions on windows. But you could try something like a bad usb, it's a usb that you can program to act like a keyboard, try looking it up and see if it is something you can use. If you think it can be used you can create it your self or buy one, if you choose to buy i would recommend either a rubber ducky or a malduino.
Hope it helps ;)
I am trying to build v1.2 of firefox os for my zte-open. With a few hiccups I was a able to configure and build it using the inari device profile. But the process fails at the last stage of flashing.
here is the output of the ./flash.sh command
rog% sudo ./flash.sh
[sudo] password for abhiram:
< waiting for device >
erasing 'cache'...
OKAY [ 0.531s]
finished. total time: 0.531s
erasing 'userdata'...
OKAY [ 1.399s]
finished. total time: 1.399s
sending 'userdata' (53571 KB)...
OKAY [ 4.518s]
writing 'userdata'...
FAILED (status read failed (No such device))
finished. total time: 9.911s
After that the device starts fresh with no userdata (obviously). Right now I am guessing that if it passes the user-data phase it might flash the system and boot partitions.
Btw, my phone running the version 1.1 of the firmware, which was from an official Zte update.
update
I tried flashing separate partitions of (system and boot) but the it gives me the same error.
with ./flash.sh system
FAILED (status read failed (No such device))
I have this same problem. However I do not think that fastboot is disabled.. I say that because I can see ROAMER2 if I do a
fastboot devices
Please note.. if you cannot preform that command try running the following command first
adb reboot bootloader
after this I bet you will be able to see the devices using the fastboot command.
So fastboot seems to be able to connect to the device and the fastboot command erasing cache seemed to have worked, and the fastboot command erasing userdata command worked. So my guess is that it is not fastboot itself but the device preventing the push from occurring.
Perhaps there is a log we can read somewhere?
Update:
I called the company. Their official line is that they do not support updating the phone and you should only use the Update feature on the phone itself. There is an update coming however it is being pushed out one a time not a global push to all devices. In some blogs on this subject I saw users complain that the device is advertised as open but is not in fact open. Point being this: If the device is preventing the push as I suspect (then we as a consumer have been tricked) and the device is operating correctly.
Update: (more info)
There is a set of problems and it depends on if you upgraded your phone or not. If you read the discussion here I think it pretty much covers everything: http://www.reddit.com/r/FireFoxOS/comments/1ugx5g/firefoxos_buils_for_zte_open/
Also check to see if your device is rooted by the following
adb shell
if you see $ continue to the next command, if you see # you have root
su
If you are in the same boat as me, and have updated to 1.1 using the ZTE images. Then you are a little stuck. We need to downgrade back to 1.0 revision 2 (B02). This will require the clockwork mod recovery to do this. The problem is that we also need the original img. ZTE has taken this image down. If you have this image or if you can find it please upload it and post it here and in the link I provided (you'll be a hero to a very small group of nerds). Otherwise.. a Mozilla developer stated that ZTE will have yet another update coming soon. (However chances are this is going to be yet another locked down version). So the hunt in on for the original image.
After emailing the b2g-dev mailing list, I figured out that this was a problem with the firmware of the zte-open.
AFAIK, the latest firmware update to 1.1 brings all the devices to OPEN_US_DEV_FFOS_V1.10B01 firmware, which for some reason comes with fast-boot disabled. Hence it is not possible to flash it.
It looks like zte are working to bring out a new update that comes with fastboot enabled. So I guess I'll have to just wait it out.
Update
It took me a while to figure out how to update the damn phone, to upgrade you need to downgrade to the firmware 1.0B02 on which fastboot seems to work.
To downgrade I had to install clockworkmod as the default recovery program complains of signature mismatch( Zte! can't I donwngrade to your older official firmware?).
Rooting and installing clockworkmod, I had to remove some assert checks on the device-name from the updater-script and then pack it. Once this is done downgrading the device is quite simple.
After this I had to individually flash the three images (boot,system,userdata) using fastboot flash command
I'm struggling now for a few days to setup bluetooth services on an ARM embedded device running Linux. I'm using a bluetooth dongle connected via USB.
Let's start with the beginning. I had to compile myself all the required packages, and that means expat, dbus, zlib, libffi, glib, bluez-3.36-libs and bluez-3.36-utils (yeah 3.36, I know they're old but so is my cross-compiler), libopenobex-1.3, obexd-0.3, obexftp. Then I put the binaries and libs on the device. Also, bluetooth is enabled in kernel.
I'm able to activate the bluetooth using hciconfig hci0 up command, I can perform scan using hcitool scan, I can even ping with l2ping previously discovered devices.
What I want is to be able to transfer files between that ARM device and another bluetooth device using ftp protocol and here my problems begin.
Are these the only tools that I need?
After putting everything on the device, I turn on bluetooth using hciconfig hci0 up, then I start dbus daemon using dbus-launch and after these I try to start obexd. When I run dbus-launch, it prints the values for DBUS_SESSION_BUS_ADDRESS and some pid and next when I try to start obexd it asks me to set the DBUS_SESSION_BUS_ADDRESS. Is this normal because I read that you have to set this only for test purposes? What is the default (real) dbus session bus address? How should I properly configure dbus?
I tend to think that the problem is in the pairing process, when the two bluetooth devices are trying to authenticate. How can I do this from command line as this is all that I have (no GUI)?
Could you please present me the detailed step to follow in order to achieve my goal. I tried to learn more about them from the Internet and also I tried to find these steps online but I could not find what I need.
Could you please explain me the difference between obexd, obexd-client, obexd-server, obex-data-server, obexftp? Are they meant to be used together or they offer the same functionalities? I could not clarify this from their man pages.
I know this is a really long post with a lot of questions, but I don't have experience with bluetooth and I'm under time pressure to solve this. Any help would be kindly appreciated.
Many questions you raised, but will try to answer them :
Thatz pretty much everything you will need.
Why are you starting session bus ? Will not starting system bus help and hcid uses system bus( as far as i know ). You need to execute the cross-compiled obexd ( or any other utility) with correct parameters.
you can use simple-agent ( it is in tools dir in 3.36 release if i am not wrong ). In a non-gui mode ( simple-agent --default [ follower by your pincode ] ) will work.
Basically you will need to find a device ( do scan ), authenticate ( pair ) and then proceed with file transfer which will involve obex level request / response ( to put in simple words).
As much i know, initially obexftp / obex-push were the only standalone utilities that worked on top of openobex for file transfer. Obex-data-serer was developed as part of GSOC competition, which got included in major distros. obexd is the slimmer version of obex-data-server specifically designed for embedded usage and is closely integrated with hcid ( and bluetoothd later). Please use only one of the utilities and not all at same time.
Well, i have an Altera FPGA and USB blaster. I downloaded quartus, but it doesn't detect FPGA, i tried with urjtag and it works fine. I tried running it with sudo, but again the same. Help please
It would probably be good if this question could be moved.
Here is a link to a site with instructions on this problem: http://www.fpga-dev.com/altera-usb-blaster-with-ubuntu/
In short, since Quartus will typically attempt to use the USB device as a user, nu must give the user permissions to use the device. This can be accomplished by udev rules. You can at first confirm that this is a permission problem by running the following sequence of commands. If devices are found now, this indicates a permission problem since we have now been running everything as root:
$ sudo killall -9 jtagd # Kill jtagd, ...
$ sudo killall -9 jtagd # ...and verify jtagd is indeed not running.
jtagd: no process found # Good, verified.
$ jtagconfig
1) CV SoCKit [2-1]
02D020DD 5CSEBA6(.|ES)/5CSEMA6/..
4BA00477 SOCVHPS
I agree with Tim here, the question should be asked on another location, your problem is probably because of a the driver of USB blaster is not installed properly. Try to do a search on internet and see if you can find any similar problems, or go to Altera forum and ask the question there, there are many experienced users there who are familiar with this kinds of problems.