Hello,
I think you understood when you readed the subject: I need some help to compile Wiird on linux... 64 bits :(
It seems to be really simple when you read the compile.txt but i didn't successed ::)
I tried to search, but i didn't find anything =/
You should build Linux binaries ;)
PS/ Sorry for my (bad) english
Can't you run WiiRD in WINE?
I thought someone said that was the only way they got it to work.
Or maybe it was that it didn't work.
Give it a try and tell me how it goes.
I've already tried before but it's like the USBGecko wasn't connected
For the moment I use a Virtual Machine, but it need many resources ^^
WiiRd will not work on WINE that's unfortunately correct.. yet I wonder, I need to set up a Linux box again, actually it should compile :(
...but the sourcecode of WiiRD isn't published (Opensource?)... is it?
Yes, YES, YES!!!
Please look on http://wiird.l0nk.org (http://wiird.l0nk.org)
This is the home page of WiiRd.. WIIRD HOME above there.. the source code of WiiRd is published!!!!!!
hm. Thanks ^^
So simply compile it under unix(linux) using a makefile (gcc -c -Wall -G64) ?
Or do i need any crypto libs (openSSl ^^)
Quote from: milw0rm on April 22, 2009, 12:04:57 PM
hm. Thanks ^^
So simply compile it under unix(linux) using a makefile (gcc -c -Wall -G64) ?
Or do i need any crypto libs (openSSl ^^)
There is a compile instruction applied, it's not written in c so GCC won't help you far!
i noticed *shame on me* ^^
hm... how to read out what is _on_ the ICs? (FTDi, etc...). I want to make a backup, dunno how to do it ;-)
Did anyone by now manage to use WiiRD under linux ?
Please try:
http://wiird.l0nk.org/WiiRd-Linux-x86.tar.bz2 (http://wiird.l0nk.org/WiiRd-Linux-x86.tar.bz2) - 32 bit build, was not working on 64 bit Linux in my test
http://wiird.l0nk.org/WiiRd-Linux-amd64.tar.bz2 (http://wiird.l0nk.org/WiiRd-Linux-amd64.tar.bz2) - 64 bit build
I'll sort out compilable source code projects now, so that people with other platforms - or distributions without the typical /usr/lib structure should be able to compile them!
Please note: YOU'LL NEED(!!!!) the newest libftdi from http://www.intra2net.com/en/developer/libftdi/ (http://www.intra2net.com/en/developer/libftdi/)
Unfortunately many destributions (in my case Ubuntu) do not keep it up-to-date and if you use an old (my Ubuntu shipped with 0.14 - current is 0.16) the purge_tx and purge_rx which WiiRd depends on might not work.. installing libftdi works the typical ./configure, make, make install way you'll need the headers for libusb though!
And: if you wonder.. "where does WiiRd put my dumps, screenshots etc" - the WIndows version normally stores everything into its application directory.. as many of you might put wiird into /usr/bin or related, I decided that WiiRd on Linux will always use ~/WiiRd for storing and searching if you do not specify full paths!
And no!!!!!!!!!!!!!!!!!!!!!!!!!!!! GUI will not happen!
Hi Link,
thanks for the binary. I can run it on a debian sid sytem but I just cannot get a connection to the USB Gecko.
Any config files where I have to adjust the port where the gecko is connected ?
Any ideas what could be the problem ?
Thank you for your help.
Cajon
do you have libusb and the libftdi I mentioned installed?
I just found out my problem is some user right thing because as root it works, only as user, it can not connect.
But until now I could not find out which rights to change to be able to connect.
hm.. maybe for some reason it still creates data in its exectuable directory
please copy the executable into your user's home and run it from there.. then it should work
I am running it from my user directory.
This is not the problem. It also creates a directory WiiRD in the user directory and stores its data there.
That works perfect.
It seems that I just have a problem accessing the USBGecko with a normal user.
I already tried to change the userrights of /dev/ttyUSB0 but this did not solve the problem
A normal user still does not get a connection when running wiird but root does.
yeah if you run it from a home directory then it's most likely to be a permission problem as FTDI module directly writes on the USB output..
Please try changing permissions /dev/bus/usb
In case your system uses udev I guess I can give you instructions how the USB Gecko will be accessible for users
Would you mind trying the following bash script (save as text file, make it executable and run it):
#!/bin/bash
usb_gecko=`lsusb | grep 0403:6001`
if [ "$usb_gecko" != "" ]; then
bus="${usb_gecko:4:3}"
device="${usb_gecko:15:3}"
sudo chmod 666 /dev/bus/usb/$bus/$device
echo "Permissions adjusted"
else
echo "USB Gecko not detected"
fi
It should make the USB Gecko writeable.. it will ask you for (depending on distribution) your user password or root password
Hi Link,
I just experienced the same problem with another usb device.
Thank you very much, your hint was the right one.
Is there a way to add a udev rule to make the port writable by everyone all the time ??
Quote from: cajon on May 12, 2009, 10:35:26 PM
Is there a way to add a udev rule to make the port writable by everyone all the time ??
yes, however, udev configuration unfortunately differs from distribution to distribution :(
I got a debian sid here, well I will google and try if I find out how to do it.
Thanks for your help, link.
Update:
I just found out how to do it.
I changed the permission file in /etc/udev/rules.d
There I found an entry for USB devices and I just added GROUP="USB" and added my user to this user group.
Now I can also use the Gecko as my user.