[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91966

--- Comment #171 from Christopher <laserhawk64 at gmail.com> ---
A Cx0-series client is what I have. Mine is an Oct 2009 version, labeled C90LE,
but I don't believe that there were any substantial revisions, and the various
versions deal primarily with variations in RAM, storage capacity (IDE
DiskOnModule is the medium), and operating system. I will note that mine has
2gb RAM installed at this time (with no issues AFAICT), and that I'm using a
64gb SD card in an IDE adapter, along with a short-ish 44wire, 44pin cable (~4"
long, and I'll note that there is no cable equivalent to an 80 wire 40 pin
cable, for 44pin "notebook" style connections, sadly) to connect the adapter to
the board, as both have male connections.

To install Puppy the way I do it, which is not as advanced as it sounds -- we
call it a Manual Frugal Install over in Puppy-land -- it goes like this:

(1) Boot Puppy from any install. You can do this on any computer that can
access the install medium. LiveCD, LiveUSB (flash or HDD), hard drive install,
etc, doesn't matter.

(2) Once you get to a graphical interface, mount the install-to medium and copy
over Puppy's core files (vmlinuz, initrd.gz, puppy_*.sfs, and zdrv_*.sfs if it
exists -- for one or two Pups out there, you'll also see an adrv_*.sfs; copying
this is non-essential, but recommended; it's extra applications).

(3) Run the Grub4Dos wizard. For X-Tahr and other XFCE based Pups, this is
under the Control Panel option in the Menu. (In particular, X-Tahr uses the
XFCE Whisker Menu, and it's the little icon immediately to the right of the
search box, that you're looking for.) For JWM based Pups, it's somewhere in the
schmoo of the Setup section of the Menu. Usually. Might be System on some Pups,
and some have it in BOTH places. Puppy is kind of a mess at times!

(4) Edit the Grub4Dos-produced menu.lst (that would be "menu dot list", mind
you!) -- you will, at least, need to find a line specifying "pfix=ram" and edit
that part of that line to read "pmedia=ataflash pfix=ram" for IDE/SATA flash
disks (such as SSDs or a CompactFlash or SD card in an adapter), or
"pmedia=atahd pfix=ram" for platter drive based systems. You also want the line
in the menu entry above that to have a matching "pmedia=" statement just before
"pfix=fsck" -- which you definitely want to keep. I tend to eliminate
everything other than the header at the top, the main entry and the "RAM Mode"
entry, and the "additionals" section's reboot and halt entries. As far as I'm
concerned, the rest is cruft. (I can upload a sample menu.lst if you're
confused.)

(5) Unmount the install-to medium, stick it in the target system, and fire 'er
up.

You may be able to do this in other Linuces (that would be the proper Latin
cognate of that word :P ), or even in Windows, by mounting the ISO manually and
copying from there. I will note that Windows is well known amongst Puppians to
have capitalization issues. ALL SFS FILES MUST BE NAMED COMPLETELY IN LOWERCASE
LETTERS OR PUPPY WON'T BOOT. Also -- use a savefolder, when prompted. Savefiles
corrupt over time (spontaneously!) and the Puppy community as a whole does not
know exactly why. Keeping that "pfix=fsck" remark in the menu.lst file helps a
lot as well, but it doesn't eliminate savefile corruption -- using it with a
savefolder, though, does.

I should also note that I *NEVER* expected you to work on this thing every
single day -- that in my mind would make for a lot of very boring and tedious
days! Take your time, man, you're not holding me up. No, seriously. I know
you've got a life. Live it. Don't worry too much about me! SERIOUSLY.

Oh, and I'll get you those logs probably tomorrow morning (it's 11:30ish here
still, as I type this) and I'll put the patches in and report back ASAP. I've a
friend of a friend who's having a 50th birthday party late tomorrow afternoon,
so I won't be able to do all that much necessarily... but I'll do what I can
and the rest will wait till Sunday. I'll keep you posted :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openchrome-devel/attachments/20160130/0e3f55b7/attachment.html>