<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c319">Comment # 319</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:laserhawk64@gmail.com" title="Christopher <laserhawk64@gmail.com>"> Christopher</a> <pre>@ Jeffrey -- I've been proactive. I've been sidelined --only recently-- by an issue related tangentially to this bug (install issues), and I'm working actively with a member of the Puppy community to fix that. It's just not fixed yet. @ Kevin -- I'm still confused, at least a little bit. I'm not blaming you for anything at this point -- indeed, I'm very thankful for all you've done for me -- except for this one somewhat frustrating bit of not doing what I've asked to confirm whether it is indeed my environment or not. You insist -- but you will not offer proof. I understand that you are frustrated. I can relate! But I still need to know whether or not it's the environment for certain -- and until that is tested, all we have is speculation and assumption. You've tested it on a different OS and a different chipset, and it works. That's great. That's amazing. That's wonderful. But it's not my OS and it's not my hardware. I'm using a TahrPup 6.0.2 based Pup, not Tahr 6.0.5. I'm using the VX855 chipset, not CN896. You don't need a network stack to follow my instructions as provided, except to download packages and code to a flash drive on another, Internet-connected system that is not the target machine. All you need as far as the Wyse Cx0 is concerned are -- my instructions, a bootable drive with Puppy, and either a folder on that drive or a second drive containing current openchrome code, the "devx" for Puppy, and the additional packages that satisfy build deps. The Wyse client itself need never connect to a network for these purposes, and indeed mine has not yet done that in the time I've owned it. Nevertheless, as reported previously, I've ordered another WYSE Cx0 from eBay -- specifically, a C90LEW. I believe that the only changes in the design between C90LE and C90LEW relate to internal Disk-On-Module and RAM capacity when shipped... we will see what happens with that when it arrives. If it is my environment, I suspect I know what the issue is and replacing the client will fix that. At some point I replaced the thermal material under the heatsink with much better stuff, which is unfortunately somewhat conductive -- it could be a short there, or it could be the one single surface-mount passive I knocked off in the process of undoing one of the spring-pins for the heatsink. I did not previously report this damage, because the client operates 100% fine in every other respect that I have tested it with. Usually, in my experience, motherboard damage is either inconsequential or fatal. Nevertheless -- testing is the only way to know for sure; I will do the testing, since you've made it clear that you will not. Again -- I do appreciate all of what you've done. "It's been a long road, getting from there to here..." ;) and I honestly cannot thank you enough for all of the help you've given me. When I can next report back with a logfile, I will do so... until then I will probably be silent. It may be a week or two... but I'm not gone yet, I'm just resting ;)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>