Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tilt100

Pages: [1]
1
General / Re: AliTV Airmouse on js0
« on: October 23, 2016, 08:38:40 AM »
Haven't had any responses on this but here's a little more info. Below is an extract from the system messages log during boot. I only have a keyboard plugged in to one usb port which you can see is discovered correctly but then there's a bunch of entries for the AliTV remote. The last entry where it is discovered as a gamepad is probably where the js0 dev entry is being created. I've no idea why this device is being discovered. I've tried various udev rule.d entries to try to both ignore and reassign without any luck. Anyone with more linux experience have any ideas?

Oct 22 21:25:44 retropie kernel: [    2.729373] usb 1-1.3: new low-speed USB device number 4 using dwc_otg
Oct 22 21:25:44 retropie kernel: [    2.846400] usb 1-1.3: New USB device found, idVendor=0461, idProduct=0010
Oct 22 21:25:44 retropie kernel: [    2.846422] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 22 21:25:44 retropie kernel: [    2.846435] usb 1-1.3: Product: USB Keyboard
Oct 22 21:25:44 retropie kernel: [    2.846446] usb 1-1.3: Manufacturer: NOVATEK
Oct 22 21:25:44 retropie kernel: [    2.858485] input: NOVATEK USB Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0461:0010.0001/input/input0
Oct 22 21:25:44 retropie kernel: [    2.910240] hid-generic 0003:0461:0010.0001: input,hidraw0: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-3f980000.usb-1.3/input0
Oct 22 21:25:44 retropie kernel: [    2.932122] input: NOVATEK USB Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:0461:0010.0002/input/input1
Oct 22 21:25:44 retropie kernel: [    2.989745] hid-generic 0003:0461:0010.0002: input,hidraw1: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-3f980000.usb-1.3/input1
Oct 22 21:25:44 retropie kernel: [    3.168901] fuse init (API version 7.23)
Oct 22 21:25:44 retropie kernel: [    3.229838] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
Oct 22 21:25:44 retropie kernel: [    3.340589] usb 1-1.5: New USB device found, idVendor=0c45, idProduct=3451
Oct 22 21:25:44 retropie kernel: [    3.340610] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 22 21:25:44 retropie kernel: [    3.340623] usb 1-1.5: Product: Airmouse
Oct 22 21:25:44 retropie kernel: [    3.340635] usb 1-1.5: Manufacturer: AliTV Remote V1
Oct 22 21:25:44 retropie kernel: [    3.348391] input: AliTV Remote V1 Airmouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:0C45:3451.0003/input/input2
Oct 22 21:25:44 retropie kernel: [    3.400671] hid-generic 0003:0C45:3451.0003: input,hidraw2: USB HID v1.01 Keyboard [AliTV Remote V1 Airmouse] on usb-3f980000.usb-1.5/input0
Oct 22 21:25:44 retropie kernel: [    3.405047] input: AliTV Remote V1 Airmouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:0C45:3451.0004/input/input3
Oct 22 21:25:44 retropie kernel: [    3.405610] hid-generic 0003:0C45:3451.0004: input,hidraw3: USB HID v1.01 Mouse [AliTV Remote V1 Airmouse] on usb-3f980000.usb-1.5/input1
Oct 22 21:25:44 retropie kernel: [    3.409698] hid-generic 0003:0C45:3451.0005: hiddev0,hidraw4: USB HID v1.10 Device [AliTV Remote V1 Airmouse] on usb-3f980000.usb-1.5/input2
Oct 22 21:25:44 retropie kernel: [    3.415784] input: AliTV Remote V1 Airmouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.3/0003:0C45:3451.0006/input/input4
Oct 22 21:25:44 retropie kernel: [    3.416104] hid-generic 0003:0C45:3451.0006: input,hidraw5: USB HID v1.01 Gamepad [AliTV Remote V1 Airmouse] on usb-3f980000.usb-1.5/input3

2
General / AliTV Airmouse on js0
« on: October 19, 2016, 10:30:09 AM »
I'm using image V0.5 and I notice that js0 is assigned to an Airmouse...

{ID_VENDOR}=="AliTV_Remote_V1"
{ID_MODEL}=="Airmouse"

I presume since this image has kodi that at some point the airmouse was being used and there is some module that is creating js0 for it. I don't have this device and I would like to have my joypads assigned to js0, js1 etc. Right now they always get assigned to js1 js2 because js0 is taken. Can someone point me to where  I could remove or uninstall whatever is attaching js0 to the air mouse.

Thx

Jerry

3
General / Re: NOOB Question
« on: September 28, 2016, 08:45:44 PM »
Yes I'll investigate the control mappings in both and see if I can see what's going on.

I figured out the issue with boot to the front end (wheel etc) rather than config menu, I guess there's no option to force that but if startup mode is set to last selection and the last selection is the front end then that's what it boots to. So basically if you escape, quit and reboot from the command line then it boots back to the front end. It would be nice if there was a way to always force that behavior though, and maybe there is if I dig around some more or I'm sure someone here knows.

Jerry

4
General / Re: NOOB Question
« on: September 28, 2016, 04:12:02 PM »
I had watched that video, but watching it again allowed me to catch one small detail I was missing. I couldn't figure out how he was getting from the menu to the wheel type display and after I watched it again I realized that right arrow on the key board shifts you to the next "display" which is the actual AM front end. I new there had to be something really stupid on my part but it really wasn't that obvious. So the good news is that everything is working as far as what I said up wheel wise and I can launch a few test games.

So a couple more questions...

Can I get AM to launch into the front end (wheel or whatever layout is selected) on boot and not the configuration menu? I'm looking at the start up settings in configuration general and its not obvious what to select there and even if this is the right place to control this. for a cab setup this is preferable.

Another weird issue which I think is more retropie and my mame setup then anything to do with AM is that I can't escape out of MAME once I fire up a game. Just wondering if anyone has seen this before? I really don't want to reset the PI every time. With all my previous MAME setups ESC always got you out. every other key seems to respond as I would expect.

Anyhow, some progress now which is good :-)

Jerry

5
General / NOOB Question
« on: September 28, 2016, 09:50:46 AM »
OK so I'm a NOOB to attract mode and I'm probably doing something really stupid but I'm having issues getting this running correctly. I'm pretty familar with emulation environments and have built PC based highly customized setup's in the past and have recently played with retropie / emulation station without to many issues but really wanted to play with attract mode as I really like the hyperspin type environment that I've used before.

So I've tried both V04 and V05 of the pre built images, both have the same issue.

On boot I end up in the AM inital menu where I can configure AM, reboot in EM etc. I think I have everything setup correctly, I've setup some initial MAME roms, built ROM list in AM which seems to work, I can launch them in EM but no matter what I do I can't get AM to launch, it always dumps me back in the initial menu.

I do see the following output including errors on the console....

Starting Attract-Mode v2.1.0 (Linux)
Config: /home/pi/.attract/attract.cfg

*** Initializing display: 'Attract Mode Setup'
- Loaded master romlist 'Attract Mode Setup' in 11ms (7 entries kept, 0 discarded)
- Constructed 2 filters in 6ms (14 comparisons)
AL Lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
glGetError 0x500
glGetError 0x500
glGetError 0x500
 - Loaded layout: /usr/local/share/attract/layouts/Basic/ (layout.nut)

*** Running: /bin/bash "/home/pi/.attract/Attract Mode Setup/V0.5 build 23-08-2016.sh
glGetError 0x500
^[^[[B^[[A^[[A

If I select the name of this image version from the inital menu (which I'm guessing is the way to fire up AM manually) I see the console output briefly and then I'm back in the menu and the same console output is repeated.

Looking around the forum it seems like the errors are known and most folks say they have to impact on AM running so I really am not sure what's going on. My first thought was that there was something I was not configuring that i needed to and hence it was just dumping me back in the menu but I'm really not sure. Second thought was I've got to be doing something really stupid :-) as plenty of other folks seem to have this working. I'm running on a PI3.

Anyhow, any help would be greatly appreciated as I'd really like to get past this and actually start setting up an AM based system and i'm running out of hair to pull out :-)

Jerry

Pages: [1]