- #SOUNDGRAPH IMON MONITOR CHANGE COLORS HOW TO#
- #SOUNDGRAPH IMON MONITOR CHANGE COLORS DRIVER#
- #SOUNDGRAPH IMON MONITOR CHANGE COLORS PATCH#
- #SOUNDGRAPH IMON MONITOR CHANGE COLORS CODE#
Finally, copy the new over to the appropriate location on the tftp boot server (and rename it if you are using a different filename in your setup). Edit /etc/initramfs-tools/nf and make sure BOOT is set to nfs.
In my case, I'm doing a diskless boot over NFS, so I had to do it slightly different. If you are running a typical installation, you can do this by running: Options usbhid quirks=0x15c2:0x0038:0x0004ģ) You need to rebuild your initrd.
#SOUNDGRAPH IMON MONITOR CHANGE COLORS CODE#
The first hex code is the vendor ID, the second is the product ID, and the 0x0004 means ignore this device. The following instruction work for the 2.6.24 kernel under Debian.ġ) Edit /etc/modprobe.d/usbhid (create it if it doesn't exist) and add the following line.
#SOUNDGRAPH IMON MONITOR CHANGE COLORS DRIVER#
Instead, you want to tell the driver to ignore your particular device. You probably don't want to completely disable the usbhid driver, because that can prevent other devices from working properly (such as usb keyboards and mice). Step 3 - Prevent usbhid from controlling the iMONĪssuming the usbhid driver has been loaded, you now need to disable that. To mount it, and then /proc/bus/usb/devices should exist. Apparently not every distribution has usbfs mounted. Anything else and you are on your own.Įdit: It has come to my attention that /proc/bus/usb/devices doesn't exist on all systems. If you see lirc_imon, then you already have the proper driver loaded. If it's "(none)", you can just skip step 3. If the driver is "usbhid", you need to continue on to disable it. That will tell you what driver is loaded for that device. Then look down a few lines further in the block and look for the line that contains "Driver=".
You want to find the block(s) that has Vendor=152c and ProdID=0038. The output of this will be 1 block of info for each USB device in on the system. So the first step necessary in setting up the iMON is to make sure the usbhid driver hasn't taken control of it. Later, when the lirc_imon module loads, it's unable to take over the device. That means when the usbhid driver starts, it takes control of the iMON. Well, as it turns out, it seems newer versions of the kernel (I'm running Debian 2.6.24) have support for the iMON in the usbhid driver. I followed them to the letter, but had no luck. Originally, the instruction I found for setting up the iMON display didn't work. Step 2 - Determine if usbhid is controlling the iMON In either case, you can have a look around at the forums and see someone has figured it out. If you have another version number, then that means either Soundgraph has changed the device again, or you don't actually have the LCD (perhaps you have the VFD, which is a very different device). If you have the 15c2:ffdc version, you have the original, and you can probably just follow Deans instructions from. If this is the version you have, then the rest of the instructions on this page should hopefully get you up and running. In my case, it's 15c2:0038, with the 15c2 being the vendor ID and the 0038 the product ID. Run the lsusb command and look for a line that says Soundgraph. Step 1 - Determine which version of the iMON you haveįirst, you need to get the ID of your iMON device.
#SOUNDGRAPH IMON MONITOR CHANGE COLORS HOW TO#
I'm trying to provide as thorough instructions as possible and describe whats going on, so that if you run into problems (ex: your configuration is a bit different), hopefully you will understand what needs to be done and figure out how to work around it.
#SOUNDGRAPH IMON MONITOR CHANGE COLORS PATCH#
Also, thanks to many of the people in those forums who provided followup info and helped troubleshoot/patch things to work with newer versions of the hardware (especially madCoder for his patch for the 0038 model).Īlso, I just want to say that, while the following instructions may seem a bit long, it really doesn't take that much work. Since it was so problematic, I'd like to share details of how I did it.īefore continuing on, I have to give huge thank you to Dean Harding for setting up the forums and for all the work he did with the iMON. However, I managed to get it all working. As I mentioned before, getting the iMON display working was a bit troublesome.