<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c237">Comment # 237</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 <span class="vcard"><a class="email" href="mailto:laserhawk64@gmail.com" title="Christopher <laserhawk64@gmail.com>"> <span class="fn">Christopher</span></a>
</span></b>
<pre>My test environment is X-Tahr 1b3, based on TahrPup 6.0.2 (X-Tahr is here -->
<a href="http://www.murga-linux.com/puppy/viewtopic.php?t=99849">http://www.murga-linux.com/puppy/viewtopic.php?t=99849</a> ). You will need to boot
Puppy in another computer and install the OS to an internal drive (so that you
get the option of a full install, which you only get when Puppy thinks you're
using an internal platter drive), then transfer that drive to the WYSE Cx0 you
have.
The Cx0 series clients cannot power a platter drive, but if you lie to the
Puppy Universal Installer (telling it your SSD is a platter drive) it will be
none the wiser. When you put down the bootloader, if you use grub4dos make sure
to edit menu.lst so that both the line with "pfix=fsck" and the line with
"pfix=ram" have those statements immediately preceded by "pmedia=usbhd" (if
using USB) or "pmedia=atahd" (if plugging into the Cx0's internal 44pin IDE
header).
Alternately, I can post the bash script that 01micko has been working on for me
-- he popped up two days ago to say he was back and would look, but I haven't
heard a peep since. If that script can be made to work, we will have a workable
way to do a full install to USB, which right now the Puppy Universal Installer
will absolutely not ever ever do.
----------
Puppy indeed does not have aptitude -- we have 'petget' instead. PET packages
are our preferred format; PET stands for "Puppy's Extra Treats" (rather cornier
than Jiffy Pop, but not my doing). The good news is that Puppy is a derivative
distro -- if you type (sans quotes) "petget /root/git.deb" and then [ENTER],
PetGet will install the package "git.deb" quite obligingly, even though it's
not a PET. At least in TahrPup, PetGet will run in text mode, although it's
messy because it echoes everything to stdout... go figure.
95% or so of Ubuntu Precise Pangolin DEBs will install and run in Precise
Puppy, without breaking anything, although they may occasionally require
dependent libs that have been stripped out of Puppy to be (re) installed.
95% or so of Ubuntu Trusty Tahr DEBs will run in TahrPup, with the same
behavior and caveat.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>