Axoloti and AV linux


#1

Hi everyone, i'm trying to install axoloti on AV linux, however i'm encountering one main problem: i get the error: wrong architecture 'amd64'

Is there any way to override the problem?
I also tried compiling from git, however install.sh is not included in git!


#2

Sorry, install.sh was renamed to build.sh but the documentation not updated accordingly...

edit: updated in git now...


#3

Perfect. However i encountered another problem now:

apt-get install -y libtool libudev-dev automake autoconf ant curl lib32z1 lib32ncurses5 lib32bz2-1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
N: Ignoring file 'violetsky_steam.list.save' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unable to locate package lib32z1
E: Unable to locate package lib32ncurses5
E: Unable to locate package lib32bz2-1.0
E: Couldn't find any package by regex 'lib32bz2-1.0'

Is this due to the wrong architecture?


#4

There are some threads discussing this, do a search for libbz2 on this forum.
Could you try without the lib32z1, lib32ncurses5 and lib32bz2-1.0 packages?
(delete them from the build.sh script)


#5

I tried putting my hands there and all that code gave me an headache. I also searched some info on the internet and it seems to be a common problem on AVlinux (i mean the lib32z1 thing, not the headache), these packages will probably be added in a future release but by now i guess i'll have to abandon the idea of making a dedicated axo-music machine.

The problem however is that ubuntu 14.04 is really a cpu eater and the pc i'm using is really old, are there any confirmed linux distros that work with axoloti other than ubuntu 14.04?


#6

What's the error you get when the lib32z1, lib32ncurses5 and lib32bz2-1.0 packages are skipped?


#7

A lot of stuff is displayed, i can't even copy all of it.
I'll paste the last lines:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for libusb_init in -lusb... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for USB... yes
checking for usb_path2devnum in -lusbpath... no
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking usbpath.h usability... no
checking usbpath.h presence... no
checking for usbpath.h... no
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking sysexits.h usability... yes
checking sysexits.h presence... yes
checking for sysexits.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for working memcmp... yes
checking for ftruncate... yes
checking for getpagesize... yes
checking for nanosleep... yes
checking for err... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating doc/Makefile
config.status: creating config.h
config.status: executing depfiles commands
make  all-recursive
make[1]: Entering directory `/home/sputnki/axoloti/platform_linux/src/dfu-util-0.8'
Making all in src
make[2]: Entering directory `/home/sputnki/axoloti/platform_linux/src/dfu-util-0.8/src'
  CC     main.o
  CC     dfu_load.o
  CC     dfu_util.o
  CC     dfuse.o
  CC     dfuse_mem.o
  CC     dfu.o
  CC     dfu_file.o
  CC     quirks.o
  CCLD   dfu-util
/home/sputnki/axoloti/platform_linux/lib/libusb-1.0.a(libusb_1_0_la-linux_usbfs.o): In function `find_monotonic_clock':
/home/sputnki/axoloti/platform_linux/src/libusb-1.0.19/libusb/os/linux_usbfs.c:327: undefined reference to `clock_gettime'
/home/sputnki/axoloti/platform_linux/lib/libusb-1.0.a(libusb_1_0_la-linux_usbfs.o): In function `op_clock_gettime':
/home/sputnki/axoloti/platform_linux/src/libusb-1.0.19/libusb/os/linux_usbfs.c:2631: undefined reference to `clock_gettime'
/home/sputnki/axoloti/platform_linux/src/libusb-1.0.19/libusb/os/linux_usbfs.c:2633: undefined reference to `clock_gettime'
collect2: error: ld returned 1 exit status
make[2]: *** [dfu-util] Error 1
make[2]: Leaving directory `/home/sputnki/axoloti/platform_linux/src/dfu-util-0.8/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/sputnki/axoloti/platform_linux/src/dfu-util-0.8'
make: *** [all] Error 2
root@sputnik-1:/home/sputnki/axoloti/platform_linux#

#8

could you try modifying line 138 of build.sh to

./configure --prefix="${PLATFORM_ROOT}" USB_LIBS="${PLATFORM_ROOT}/lib/libusb-1.0.a -ludev -lrt -pthread" USB_CFLAGS="-I${PLATFORM_ROOT}/include/libusb-1.0/"

(add -lrt after -ludev)

Tell me if it this works.


#9

Another error...

apt-get install openjdk-7-jdk
Reading package lists... Done
Building dependency tree       
Reading state information... Done
N: Ignoring file 'violetsky_steam.list.save' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unable to locate package openjdk-7-jdk

It seems there's this "violetsky_steam.list.save" file that's causing trouble

UPDATE: I tried to delete the violetsky....save file, that error went away.

UPDATE2: i tried adding to etc/apt/sources.list the line deb http://security.debian.org/debian-security wheezy/updates main
Did some apt-get update and then run build.sh again (the one with all the modifications)

I got another error, but at least this time is trying to install java:

apt-get install -y libtool libudev-dev automake autoconf ant curl lib32z1 lib32ncurses5 lib32bz2-1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
autoconf is already the newest version.
automake is already the newest version.
libudev-dev is already the newest version.
libtool is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 364 not upgraded.

udev rules already present, skipping

DONE

chibios directory already present, skipping...

bin/arm-none-eabi-gcc already present, skipping...

libusb already present, skipping...
dfu-util already present, skipping...

apt-get install openjdk-7-jdk
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
openjdk-7-jdk : Depends: openjdk-7-jre (= 7u91-2.6.3-1~deb7u1) but it is not going to be installed
E: Broken packages
root@sputnik-1:/home/sputnki/axoloti/platform_linux#


#10

Advising how to install openjdk on a distribution I'm not familiar with is unrelated to Axoloti, can't provide much help with that.
I'm not sure mixing in the debian package repository is the right thing to do. Maybe try
sudo apt-get install openjdk-7-jre


#11

I manually installed jdk7, deleted the lines:
echo "apt-get install openjdk-7-jdk"
sudo apt-get install openjdk-7-jdk

in build.sh and the terminal has almost got to the end of the code:

##### building GUI... #####
./build.sh: line 163: ant: command not found

What now?


#12

sudo apt-get install ant


#13

I finally managed to install axoloti patcher. Except something went wrong with the usb thing, since i connected the board and it's not being recognised from the patcher :pensive:

I got to a similar result using wine.

I think i'll have to wait until i get my decent computer back...


#14

what's the output when you run
lsusb
in a terminal?
And what does the "Select Device" dialog in Axoloti tell?


#15
Bus 002 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 003: ID 04f2:0111 Chicony Electronics Co., Ltd KU-9908 Keyboard
Bus 002 Device 002: ID 147a:e00d Formosa Industrial Computing, Inc. 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
Bus 001 Device 003: ID 0bda:0103 Realtek Semiconductor Corp. USB 2.0 Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

As for the select device dialog there's nothing to select, blank screen


#16

Seems the firmware is not loaded anymore...
You'll need to do a rescue flash. Push and hold button S1 while you plug in the board, then, in Axoloti, select board->Firmware->Flash (rescue).


#17

No devices in DFU mode detected. To bring Axoloti Core in DFU mode, remove power from Axoloti Core, and power it up while holding button S1. The USB port needs to be connected with this computer too...

And, however, the firmware was loaded the last time i used axoloti


#18

Green led on after the leds blink during powerup? Then firmware is indeed loaded.
Perhaps your USB cable only has power wires but no data wires? (A charging-only cable... these things should never have been made...)


#19

Red and green leds blinking on powerup, green led lit after. The cable is a regular data wire


#20

Please check if your board is recognized on a different computer and with different cable that proves to have data wires (the micro-usb cable can be checked by connecting for instance an Android phone, does the computer recognize the phone?)