mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: markus reichelt <ml@mareichelt.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.27.9
Date: Sun, 14 Dec 2008 22:11:27 +0100	[thread overview]
Message-ID: <20081214211127.GC3928@tatooine.rebelbase.local> (raw)
In-Reply-To: <49456C76.20006@wizards.de>

[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]

* Holger Hoffstätte <holger@wizards.de> wrote:

> That's really all I know.

Apart from all the mainline excuses why patches aren't accepted - I'd
REALLY like to know why each and every 2.6.27 kernel so totally fails
on me when it comes to X ... the vesa driver refuses to come up
with the magic to do its 75 Hz wonders of the pre .27 series.

Really, there's no error that I could track down to solve the
problem. X seems to run in a loop (unkillable), but a reboot works
(if there's not a kernel panic and hard lockup involved first whilst
me trying to get the darn thing working) - my screen even tells me
during these desperate times that there's no signal. Awesome. 

Seems like other people encountered the same problem but short of
getting rubbed the obvious answers in their faces, namely mentioning
some magic spell to cope with nvidia (well, doh!), nothing of
substance ever really has come up. Bummer.

Framebuffer or not, radeon driver or not, vesa driver or
not, I still get that 60 Hz eye cancer at best. Sucks. MTRR cleanup
enabled, PAT enabled or not, nada.

Strangely, this reminds me of my hatred towards VIA and its Nehemiah
scam. Suitcase nukes, what a wonderful concept :)


I hope the new mainboard (GMA 3100) works out of the box, cos the
current ancient (!) ati card gives me nothing but a headache on .27.

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250
If [Radeon 9000] (rev 01) (prog-if 00 [VGA controller])
        Subsystem: PC Partner Limited RV250 If [Sapphire Radeon 9000
Pro]
        Flags: bus master, stepping, 66MHz, medium devsel, latency
64, IRQ 19
        Memory at e8000000 (32-bit, prefetchable) [size=64M]
        I/O ports at a800 [size=256]
        Memory at ff4f0000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at ff4c0000 [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2
        Kernel driver in use: radeonfb

Writing this on 2.6.26.8. .... Just venting, dont mind me.

-- 
left blank, right bald

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-14 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14  0:10 Greg KH
2008-12-14  0:10 ` Greg KH
2008-12-14  8:06 ` Holger Hoffstaette
2008-12-14 19:08   ` Greg KH
2008-12-14 20:28     ` Holger Hoffstätte
2008-12-14 21:11       ` markus reichelt [this message]
2008-12-15  6:05         ` Greg KH
2008-12-16 11:50           ` markus reichelt
2008-12-15  0:00       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081214211127.GC3928@tatooine.rebelbase.local \
    --to=ml@mareichelt.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®