rbino / ems-qart

A Qt application to flash EMS 64M cartridges
GNU General Public License v3.0
181 stars 13 forks source link

Not recognising cartridge on linux #9

Open naught101 opened 7 years ago

naught101 commented 7 years ago

Using the deb versions on Kde Neon (ubuntu 16.04 base), I can get the program running, but it does not work. The interface appears, and I seem to be able to select the lsdj.gb rom that I want to load, but the "click to refresh EMS cart status" does nothing, and the "start" button is always greyed out.

This is the console output:

$ ems-qart 
qrc:/qml/MainView.qml:416: TypeError: Cannot read property 'title' of null
qrc:/qml/MainView.qml:422: TypeError: Cannot read property 'checksumValid' of null
qrc:/qml/MainView.qml:453: TypeError: Cannot read property 'title' of null
qrc:/qml/MainView.qml:459: TypeError: Cannot read property 'checksumValid' of null
usb_claim_interface error  -4 

The first four messages appear when the program starts, the last message appears when I click "refresh EMS cart status" the first time, but it doesn't appear on subsequent requests.

I've tried compiling from sources, but it also fails, because libqt5svg5-dev qtbase5-dev qtdeclarative5-dev are not available on 16.04. When I try qmake .., I get:

qmake ../
Could not find qmake configuration file linux-g++.
Error processing project file: ../ems-qart.pro
rbino commented 7 years ago

Can you post the output of dmesg when you connect the cart to the USB?

naught101 commented 7 years ago
[97625.950498] usb 2-3.2: new full-speed USB device number 23 using xhci_hcd
[97626.055160] usb 2-3.2: New USB device found, idVendor=4670, idProduct=9394
[97626.055162] usb 2-3.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
naught101 commented 7 years ago

(I got ems-qart running on a friend's windows laptop, so I got LSDJ flashed, but I would still like to be able to update it without borrowing a laptop)

rbino commented 7 years ago

Can you paste the output of groups for your user?

BarrensZeppelin commented 6 years ago

I had the same problem on Ubuntu 17.10 with the latest prebuilt release. Building from source fixed the issue.

RSAsir commented 6 years ago

I had the same problem on Ubuntu 18.04, i can confirm that building from source as @BarrensZeppelin said fix the issue.

rbino commented 6 years ago

I will have a look on Ubuntu 18.04.

Then again, I will probably start providing AppImages instead of debs to reduce variance between distros (and to be able to use slightly more modern dependencies).

evilblade666 commented 5 years ago

Guys, I'm having the same issue here and when I try to build it from source I get the following:

g++ -Wl,-O1 -o ems-qart main.o CartController.o EmsCart.o RomInfo.o qrc_resources.o moc_CartController.o moc_EmsCart.o moc_RomInfo.o   -lusb-1.0 -lQt5Quick -lQt5Svg -lQt5Widgets -lQt5Gui -lQt5Qml -lQt5Network -lQt5Concurrent -lQt5Core -lGL -lpthread 
/usr/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status
Makefile:161: recipe for target 'ems-qart' failed
make: *** [ems-qart] Error 1

What can I do to fix this?

evilblade666 commented 5 years ago

Update: just FINALLY got it working!!

What I did was I found this "-lGL" in Makefile and simply removed it :) After that "make" compiled it without errors and it's actually working :))

rbino commented 5 years ago

@evilblade666 what distro are you using? Can you paste the output of dmesg when you connect the cartridge and the output of the groups command?

The build problem means that you don't have libgl1-mesa-dev installed (if you're on Ubuntu), but I'd rather understand why the cartridge isn't detected by the packaged version

evilblade666 commented 5 years ago

I'm using Ubuntu 18.04 dmesg [187781.300247] usb 1-1.2: new full-speed USB device number 28 using ehci-pci [187781.409159] usb 1-1.2: New USB device found, idVendor=4670, idProduct=9394 [187781.409165] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 groups evilblade adm cdrom sudo dip plugdev lpadmin sambashare vboxusers debian-tor bumblebee

eugeneromero commented 4 years ago

On Ubuntu 20.04, can confirm that installing deb file produces this issue, however building it without any changes to current source works as intended.

rbino commented 4 years ago

The deb packages probably need some love (as does all the project). I'll make a note to myself to do a new release as soon as I have a little bit of time.