For knoppix, try booting with 'vga=normal' That avoids booting
with framebuffer text. (there are other vga=settings, but I haven't
bothered to learn them).
The VGA text code for knoppix seems to go for the 'best possible' mode
which can overwhelm the monitor.
James Miller wrote:
Hello Ray:
No. I
Hello Ray:
On Sun, 24 Oct 2004, Ray Olszewski wrote:
> initrd doesn't work that way. It loads modules *after* the kernel itself is
> loaded, but *before* the "real" root filesystem is mounted. So it provides
> a way to supply, for example, modules needs to mount disk drives to the
> kernel before
At 12:45 AM 10/24/2004 -0500, James Miller wrote:
[...]
A final stray thought: don't know if you caught my earlier statement about
entering atyfb in /etc/modules. I created an initrd that, so far as I can
tell, contains this module. However when I boot with the video=atyfb:etc,
the module doesn't
On Sat, 23 Oct 2004, Ray Olszewski wrote:
> On that score ... just a wild, blue-sky thought here ... maybe your trying
> to use an 8 MB SGRAM on a card that only supports 4 MB is introducing a
> problem. Does anything improve if you remove this module and use only the
> onboard 4 MB?
Well, if I d
Editing quite a bit, since I'm responding only to a few specifics.
At 10:16 PM 10/23/2004 -0500, James Miller wrote:
Hello Ray:
Good to see you're still with me. I was beginning if I were the only one
on this list manic enough to spend their weekend trying to work out
framebuffer display issues.
Hello Ray:
On Sat, 23 Oct 2004, Ray Olszewski wrote:
> One more thought: although the spec for setting video mode looks like you
> can put in any old values, in fact you have to use a mode that the kernel
> source understands. I don't have a 2.6.x source tree handy, but 2.4.21
> doesn't include a
Hello Ray:
Good to see you're still with me. I was beginning if I were the only one
on this list manic enough to spend their weekend trying to work out
framebuffer display issues. Looks like I'm in good company, though :)
> First question: do you KNOW that your LCD display will support a refres
At 03:06 PM 10/23/2004 -0500, James Miller wrote:
Latest on this problem is that I'm using only the video=atyfb:[EMAIL PROTECTED]
argument (no vga=xxx argument) in menu.lst. During the boot process the
screen goes black for a time--with just a cursor at the very bottom, which
starts scooting back
At 03:06 PM 10/23/2004 -0500, James Miller wrote:
Latest on this problem is that I'm using only the video=atyfb:[EMAIL PROTECTED]
argument (no vga=xxx argument) in menu.lst. During the boot process the
screen goes black for a time--with just a cursor at the very bottom, which
starts scooting back
Latest on this problem is that I'm using only the video=atyfb:[EMAIL PROTECTED]
argument (no vga=xxx argument) in menu.lst. During the boot process the
screen goes black for a time--with just a cursor at the very bottom, which
starts scooting back and forth horizontally--then comes back just as it
The framebuffer how to documentation actually gives two lilo arguments for
the ati cards: vga=791 ("to make the display sane" as they say) and
video=atyfb:[EMAIL PROTECTED] after the "append" argument. They presume you've
compiled the atyfb module into your kernel (which I haven't, though I made
a
James Miller wrote:
On Fri, 22 Oct 2004, Jim Nelson wrote:
If you are using a 2.6 kernel (and maybe the 2.4), the kernel module for
the ATI Rage series of graphics systems is aty128fb, not atyfb. I've
had problems with vesafb myself, but with really old hardware (Trident
TGUI 9660 on an old Think
Hello Ray:
On Fri, 22 Oct 2004, Ray Olszewski wrote:
> The vesa framebuffer is pretty generic; almost any *modern* video card
> should be able to drop back to its standards. But I do have older cards,
> like the ancient S3 I use in one of my test systems, that does not support
> the vesa framebuf
On Fri, 22 Oct 2004, Ray Olszewski wrote:
> You might want to try 1280x1024 in vesa to see if it works
> there. Depending on color depth, the values for that are:
>
> 8 bit 0x307 = 775
> 16 bit 0x31A = 794
> 24 bit 0x31B =
On Fri, 22 Oct 2004, Jim Nelson wrote:
> If you are using a 2.6 kernel (and maybe the 2.4), the kernel module for
> the ATI Rage series of graphics systems is aty128fb, not atyfb. I've
> had problems with vesafb myself, but with really old hardware (Trident
> TGUI 9660 on an old Thinkpad).
Thank
At 02:00 PM 10/22/2004 -0500, James Miller wrote:
Looking over the framebuffer how to again (fairly dated document by now)
I'm beginning to wonder if maybe my video card doesn't require a special
framebuffer module. There, under section 5.6 "Got an ATI card?" they
mention a particular module--atyf
James Miller wrote:
Looking over the framebuffer how to again (fairly dated document by now)
I'm beginning to wonder if maybe my video card doesn't require a special
framebuffer module. There, under section 5.6 "Got an ATI card?" they
mention a particular module--atyfb. In my initrd, on the other
Looking over the framebuffer how to again (fairly dated document by now)
I'm beginning to wonder if maybe my video card doesn't require a special
framebuffer module. There, under section 5.6 "Got an ATI card?" they
mention a particular module--atyfb. In my initrd, on the other hand, I
appear to h
I'm having some problems with the console display under a new Debian
variant (Ubuntu) I'm trying out and would like to ask for advice on
troubleshooting and maybe fixing the problem. The problem is that I
cannot seem to get the console to display at a high enough resolution. I
understand that the
19 matches
Mail list logo
