Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
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.
Perhaps the pin floats on a convex bubble above its' contact, kind of like joystick D-pad or old keyboard? If that is the case then it is achieving gnd first AND normally open functionality like I plan to do on the circuit, all at the pin level. That is an great idea for me to add into my build.
The caps will be important, as those are for DC power conditioning and noise suppression, so Armor Gnome will need to match those values in his build. You could always post a pic of the parts if they're surface mount, and we could figure out the values for him.
I have used USB pins on mobos straight to the USB and I have pulled them from cases where the mobo leads went to a board with caps and diodes before going to the USB housing. Both have worked so I wasn't overly concerned with that side of it. On the iPhone USB hardwired dock I need to power up the WebDT with the orbiter running and see if the detection of USB storage causes any problems. I have no reason to suspect it would but its an easy test to see how the iPhone is handled if present at startup, when coming out of suspend and detected while running.
The wall-wort plug I am housing inside the cradle is other than the PC standard 110-120V line plug, exactly the same as the OEM charger. 12v 3.5A. Something I am wondering now is if the cradle takes a higher Amp power supply?
Or upgrade your core, and then run /usr/pluto/bin/Diskless_CreateTBZ.sh as root. Delete your MD and create it again.
Since I tossed this out there I will be the one to have a first crack at it and will submit what I come up with for everyone to review. Typically I overthink things but in this case I might be thinking its too easy of a change. The DVD installer adds some desktop applications on the hybrid/core. It was odd to me then that the Diskless_Setup by default actually creates more desktop applications and programs. If there is discussion about the usefulness of a desktop environment lets keep it to media director only. The core/hybrid has a desktop now and if you want to add little progs or apps then put them there or work on changing the primary installer.
My proposal and the task I believe I am up to involved the Diskless_Setup only, it is something I think I have the ability to change myself with my limited programming ability. Correct me if I am completely off the wall but this is how I think the process works.
A new device is plugged into the network and looks for a DHCP to point it towards a bootloader.
DCErouter (specifically tftpboot.cfg) creates a few new directories based on its MAC address and points it to initrd and vnlinuz
The new device uses these as kernel= and boot=, and builds its image in root=<core>/?/nfs
Based on the content of vnlinuz and initrd, combined with polled info from various scripts the MD image is created just as it would install itself on a computer with a ubuntu install cd.
-add my changes
Because bootloaders can have options in the menu.1st file (sorry I know grub best, even though lmce I think uses something else because of the APPEND options) I believe I can add options here that will point to alternative initrd and vnlinuz versions.
Default option = just like it is now
Option1 = load initrd and vnlinuz that install different applications
Option2 = load initrd and vnlinuz that install different applications
Option3 = load initrd and vnlinuz that install different applications
There are options in the web-admin and warnings about kernel version on MDs so that part I don't think I have any control over. I have tinkered though and adjusted the bootloader on the core to point a specific MAC address to a custom folder which booted TinyCore, DSL, 12.04 LTS and openWRT on different machines around my house. I never got my own custom dsl+squeezebox configuration to boot however and is what led me to the idea of taking LMCE's setup and changing it to my desire.
I believe that I can take all of the source code needed to compile LMCE diskless, change and remove certain components and then compile and make options in the bootloader menu to select that version. Is that an accurate statement? Obviously I would need to debug and repeat a lot of effort but because I am only altering working source code, I would assume I am only looking at minor necessary work. The years of hard work and coding behind current LMCE remains and I am just the jack-wagon that stripped some off.
If some off-the-shelf hardware doesn't quite fit the bill for a full MD, why not have the option to boot as audio only MD? If an MD is going on the bedroom wall where a keyboard will never touch it why not have the ability to boot it without a desktop? If I want to build a minimal media MD for use as an intercom outdoors, why can't I load a boot template designed for just that? These are all just pipe-dreams of mine at this time as I haven't done yet any modification or compiling of lmce code. I have just booted other pre-compiled kernels using lmce tftpboot.
Hopefully this novel of a comment clears up what I plan to do and how I plan to do it. After everyone has a laugh at my ignorance please feel free to correct me.
Those trying 1004 for the first time, please be aware of the fact that on the snapshots, you do NOT need to run Diskless_CreateTBZ.sh as it is embedded. Network installs will still require it. From snap install you just have to plug an MD in and roll.