Messages

91

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 17, 2013, 10:57:19 pm »

Thanks, checked for nulls on FK_DeviceCategory, then checked for non existant categories in the FK of DeviceTemplate... nothing.

But I *did* find my old Device with an FK_DeviceTemplate that didn't exist -> set to the old devicetemplate of the Rii before I sqlcvsed myself. Updated to the new template ID and...
voila...

we're back in business.

So, I'm guessing here, the issue was that I already had a Device in the Device table, which pointed to a non-existant template. Presumably, the code was trying to get the DeviceCategory of the non-existant template so it looked like a DeviceCategory issue. Red-herring.

All good, though, screen is back and I can pick up from there.

Thanks a stack, Thom...  useful info on the gdb and coredump stuff that I can use in future. I even found the offending line in TableDeviceTemplate.cpp:

Code: [Select]

long int Row_DeviceTemplate::FK_DeviceCategory_get(){PLUTO_SAFETY_LOCK_ERRORSONLY(sl,table->database->m_DBMutex);

return m_FK_DeviceCategory;}

but I haven't a cooking clue what it does... that's a battle for another day perhaps.

92

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 17, 2013, 10:23:37 pm »

dmesg output:

http://pastebin.com/SUq81gMt

And here's the gdb output

Code: [Select]

Core was generated by `/usr/pluto/bin/UpdateEntArea -h localhost -P 3306 -u root -D pluto_main'.
Program terminated with signal 11, Segmentation fault.
#0  Row_DeviceTemplate::FK_DeviceCategory_get (this=0x0) at Table_DeviceTemplate.cpp:248
248 Table_DeviceTemplate.cpp: No such file or directory.
in Table_DeviceTemplate.cpp

So it does seem to be to do with mucking about with the device templates....

93

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 17, 2013, 07:59:17 am »

Sweet, thanks. Will try to hit this tonight.

94

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 16, 2013, 11:27:05 am »

Oh, no.... I think it's cooked. I went a away for a few days and shutdown the core. When I start up again, none of my MDs or orbiters come up properly... and dmesg reports a segfault from libpluto_main.so (IIR) in updateEntArea or something. I wonder if this is due to a corrupt device database - missing PKs or FKs or something?

I can scan through the DB manually but may be difficult to determine exactly where the problems are. Is there any way I can start with a "clean" pluto_main databse and then add everything from there? I took screenshots of my new devices and saved the IR codes anyway just in case of this scenario?

95

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 09, 2013, 10:15:45 pm »

Hi Thom

Thanks again... I've done what you suggested - checked in the new manufacturer (Rii) and the updated mini i8 template linked to this manufacturer but I'm afraid we're probably going to have another key issue.... because the manufacturer number (mine) will probably differ with the master.

Shucks.... at the end of this I'm going to search the wiki for every entry that refers to creating a device template and put in bold at the top !!Make sure you update your datbase *before* merrily creating templates if you want to share with the rest of the class!!

When you get a moment, please check the submissions and see if they can work.

Ta

96

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 08, 2013, 10:07:59 pm »

Done... I think I've checked the sucker in against ticket http://svn.linuxmce.org/trac.cgi/ticket/1836
 

97

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 08, 2013, 09:54:32 pm »

Woah, forgot about rule#1. 
update came back with success.

98

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 08, 2013, 09:51:35 pm »

Just say, completely hypothetically speaking, that I completely cooked the database....

Am I looking at a re-install of linuxmce?

If, for the sake of argument, I had run the sqlCVSupdate from the web-admin.... checked all the update options ... then pressed submit... while logged in as root to the pluto_main db from a terminal. and then, after waiting a reasonable time for a blank firefox window that said only "Waiting for dcerouter..." at the bottom, that I'd tried again to log in to pluto_main from the terminal, and found a bunch of error stuff scrolling past the screen ending in something like

Code: [Select]

nnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
130708 21:46:26  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
130708 21:46:26  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
130708 21:46:26 [ERROR] Plugin 'InnoDB' init function returned error.
130708 21:46:26 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
mysqld: Too many arguments (first extra is 'pluto_main').
Use --verbose --help to get a list of available options
130708 21:46:26 [ERROR] Aborting

130708 21:46:26 [Note] mysqld: Shutdown complete

Would that be a bad thing? Would it be advisable to carry on "Waiting for dcerouter...." and go to bed..... and see what it looked like in the morning? Or should I start downloading the latest snapshot now?

99

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 08, 2013, 09:22:30 pm »

And, for next time, please only work on one device template at a time, before submitting.

Now you tell me!!
OK... so I need to take screenshots of all those shiny new templates I've created because my DB is so out of date I need to update the sucker and then add them back and *then* submit. hmm...

All learning is good. Thanks Thom, appreciate the help... hope my piddly little effort can help someone else one day.

100

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 08, 2013, 09:00:23 am »

Thanks!

 

And if I've changed one or two others....? Is there any way of isolating them at sqlcvs diff time?

101

Users / Re: Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 07, 2013, 12:56:41 pm »

Thanks Tschak...

Have read it and applied it. Works very well. What was messing things up was that I was battling to run "xev" because it wants to use "X" - ie it asks for 'DISPLAY' enviro variable to be set and generally I'm running it from a text terminal.

I tried setting 'DISPLAY' to '192.168.80.4:0.0' which worked a bit but didn't get the events coming through nicely... some errors/messages in xev where I think it's fighting with LMCE over the window visibility... so I just plugged the Rii into my zoneminder server and ran xev there and copied all the keycodes I needed.

Have created the template and it's working brilliantly. Very pleased, thanks for the pointers.

Now to share the template with others- are the instructions in
http://wiki.linuxmce.org/index.php/LinuxMCEsqlCVScommitProcedure
still relevant. What's a mantis ticket?

PS have already wikified on the assumption that I'll share the device template with others.

102

Users / Rii mini i8 wifi multimedia keyboard template: getting multimedia keys working

« on: July 05, 2013, 09:53:02 am »

As promised, opening a new thread since I got the template up and running and autodetecting in the following thread:

http://forum.linuxmce.org/index.php/topic,13309.0.html

Now the problem is getting the multimedia keys working... which is why I need a template in the first place since the rest of the keyboard works otb.

103

Users / Re: Plug and play detection - troubleshooting for Rii wireless keyboard template

« on: July 05, 2013, 09:50:11 am »

OK, plug and play sorted. Getting the media keys running is another story. Time to branch threads. Closing this one as resolved.

104

Users / Re: Plug and play detection - troubleshooting for Rii wireless keyboard template

« on: July 04, 2013, 08:25:23 pm »

Ha ha... I take it back, autodetect works.... sweet. I was looking in the wrong place. Silly tit... I was looking under the MD rather than under the onscreen orbiter in the device tree. Now to see if the media keys work.....

105

Users / Re: Core continually "finds" hard drive.

« on: July 04, 2013, 08:18:32 pm »

I don't think that's 100% correct. I would say 50%

Mounting and unmounting is done on demand.... correct, but I'm pretty sure discovery doesn't work the same way and once a drive is discovered you shouldn't keep seeing it showing up in messages every 15min or whatever. I think that is an error. I even think I've had something similar and others have too and I'm sure if you search the forum with the right search phrases you'll find it.

Hope I haven't added to the confusion.

If I recall correctly the script that does the detection is StorageDevices_Radar.sh or something like that and it basically runs every so often to scan for new drives.  It's quite well commented and if you know something about shell scripting you can potentially figure out what is going on in there.