From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.62)
(envelope-from <gentoo-user+bounces-60745-garchives=archives.gentoo.org@gentoo.org>)
id 1HMVJu-0002IC-51
for garchives@archives.gentoo.org; Wed, 28 Feb 2007 20:22:38 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l1SKL5ch008606;
Wed, 28 Feb 2007 20:21:05 GMT
Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.231])
by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l1SKGa7r003452
for <gentoo-user@lists.gentoo.org>; Wed, 28 Feb 2007 20:16:36 GMT
Received: by nz-out-0506.google.com with SMTP id s1so226980nze
for <gentoo-user@lists.gentoo.org>; Wed, 28 Feb 2007 12:16:35 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
d=gmail.com; s=beta;
h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=n2i4yqj+7CLKt2q92NVs6Y9hMwt6JFvFtM6PccTa7xQ9NnN1As8Ck4iALOssrpFvTtgyw2AiIQfeW+j43xBfMxmZosHfDEwWmVU2839ZS80mUNSph0LzpSSKM9+YJSCecfyejb/SdcZKid1sj5b2vVnUlbm/fYF1PyvFQgwsicI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=fwcZ/7bm4b5QG80/FpJqeT5Dv7bCbej8Tn+Fpqy8vthZh+77TMLbpMiBWyn/bI7pZQlp3SAR+XCOF5nZRButDDiWVfEvGkdxeu70HmZN3mtGssqn8eF9qhgIUY6nZf9JOe47rm1+HoU7s97nQqSZQCHnRQcnxzNGTOq8VaxzYbw=
Received: by 10.115.33.1 with SMTP id l1mr33804waj.1172693790859;
Wed, 28 Feb 2007 12:16:30 -0800 (PST)
Received: by 10.115.92.9 with HTTP; Wed, 28 Feb 2007 12:16:30 -0800 (PST)
Message-ID: <430ec6620702281216n103453f5j7655a59751ecd1bf@mail.gmail.com>
Date: Wed, 28 Feb 2007 15:16:30 -0500
From: "il-young son" <il.young.son@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] kernel upgrade and vesafb-tng issue.
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Archives-Salt: e781771f-08bc-49d6-bda4-ff19ec95c1b2
X-Archives-Hash: 175e80245428c6d29b2e571aec8502c9
hello,
here's something weird i ran into after upgrading my kernel from
2.6.18-r6 to 2.6.19-r5. now if i compile the kernel with framebuffer
enabled with vesafb-tng support and set the resolution to anything
other than 640x480-16@-- in grub, i get this error upon booting.
"Block device /dev/sdb3 is not a valid root device."
it then proceeds to ask me to specify the device to boot (or type
"shell" for shell). now at this point if i specify /dev/sdb3 (where
my root partition is -- btw, the new kernel also seems to have
switched what's assigned to sda and sdb) then it continues to boot
fine. so it's definitely detecting sdb3 fine. it seems to be somehow
(however indirectly) associated with enabling framebuffer in the
kernel. if i don't enable it or if i set the resolution to 640x480
with 16-bit colors, it boots without a hitch. does anyone have any
idea as to why this is happening? i have radeon x300 card if that
helps.
somewhat unrelated, i've also noticed with the new kernel, when i run
glxgears it's giving me low fps score. but when i try fgl_glxgears it
looks fine. and also everything else looks fine. fglrxinfo gives me
the right info and glxinfo says "direct rendering : yes". just
curious as to why glxgears would give me a vastly different result
than before.
thanks in advance,
il.
--
gentoo-user@gentoo.org mailing list