Text 12991, 99 rader
Skriven 2009-07-25 12:50:04 av Maurice Kinal (1:261/38)
     Kommentar till en text av James Bradley
Ärende: oh you ain't gettin' no younger
=======================================
Hey James!

> "Fun" Oh... Is that what it's called.

Relatively speaking to most computer type activities, yes.

Looks to me like you have a conflict between vesafb and matroxfb. What I do is
add an append line to lilo which gives me only matroxfb info upon bootup.  The
line I add to /etc/lilo.conf is;

  append="video=matroxfb:vesa:0x1B8,fv:70"

The fv part you might want to drop as that sets the horizonal frequency and it
may not work with your monitor but I left it in to demonstrate at least one of
the many extra finetunes that can be farmed out to create a suitable day to day
thingy for oneself.  A safe starting point would be just 'matroxfb:vesa:0x1B8'.

According to linux-2.6.30.3/Documentation/fb/matroxfb.txt the hex numbers for
setting resolution and bitness are as follows;

-----------------------------------------------------------
[Graphic modes]

bpp | 640x400  640x480  768x576  800x600  960x720
----+--------------------------------------------
  4 |            0x12             0x102
  8 |  0x100    0x101    0x180    0x103    0x188
 15 |           0x110    0x181    0x113    0x189
 16 |           0x111    0x182    0x114    0x18A
 24 |           0x1B2    0x184    0x1B5    0x18C
 32 |           0x112    0x183    0x115    0x18B


[Graphic modes (continued)]

bpp | 1024x768 1152x864 1280x1024 1408x1056 1600x1200
----+------------------------------------------------
  4 |   0x104             0x106
  8 |   0x105    0x190    0x107     0x198     0x11C
 15 |   0x116    0x191    0x119     0x199     0x11D
 16 |   0x117    0x192    0x11A     0x19A     0x11E
 24 |   0x1B8    0x194    0x1BB     0x19C     0x1BF
 32 |   0x118    0x193    0x11B     0x19B


[Text modes]

text | 640x400  640x480  1056x344  1056x400  1056x480
-----+------------------------------------------------
 8x8 |  0x1C0    0x108     0x10A     0x10B     0x10C
8x16 | 2, 3, 7                       0x109
-----------------------------------------------------------

As you can see 0x1B8 corresponds to 1024x768 24bpp.  With a proper
/etc/fb.modes and fbset on board, matroxes can be changed on the fly
unlike vesafb which is stuck at the resolution and bitness that was set with
the append line.

I'd advise obtaining a copy of
linux-2.6.30.3/Documentation/fb/matroxfb.txt as that tells much of the tale.

> my first HW troubleshoot is to strip out the Brooktree device
> in a simplification effort, to working on the Matrox. That
> should take the Philips tuner out of the equation.

An excellent idea.  Lately I've been tweaking usb flashdisk boots. I am almost
'finished' with a 32 bit one booting off a spinney 2.5" drive wired to a usb
port and over the next couple days will tweak kernel upgrades for it.  I am
using a jiggery-pokery ramdisk method so that it won't matter what drive letter
gets assigned to it on bootup. It works!  Now to get kernel upgrades working
and it'll be a keeper, and then follow the same logic for 64 bit boots.

> I've found the BT cards' audio all need to go externally into
> the sound cards' line in, or at least an outboard amp.

I have one here like that made by ATI with a bt878.  It worked great until I
upgraded the kernel.  :-/

> record only the nefarious bits, and the weather if it kicks up
> a fuss.

Some type of motion detection?  Never played with anything like that ... yet. 
I am not sure I want to.  Maybe if I get REALLY bored one day.

> Is that a good thing, or just a thing?

Depends who you ask, and since the question is aimed at me, it is a mixed bag. 
Every once and awhile Paul and I are in sync but usually not ... which can be a
good thing.  Depends on the weather I guess.

> "Maurice has his priorities."

Today ... or tommorrow ... we'll see.

Life is good,
Maurice

--- BBBS/LiI v4.01 Flag
 * Origin: Prism bbs (1:261/38)