On Mon, 2007-05-21 at 19:27 -0400, cga2000 wrote: > _Owen_, > > What do you get .. a kernel oops .. a black screen of death .. a vga > console with oversized fonts ..? With any video= parameter, I get the default resolution (640x480/80x25, I suppose), just like there was no vga= or video= parameter appended to the kernel boot line. > With little detail about what's happening .. I would suggest building a > kernel with support for you hardware built in .. rather than provided > via a module. That's how I eventually got this to work with a 2.4.27 > kernel & atyfb/mach64. ... > I suspect that debian kernels are compiled w/o native driver support > because the sum total of all the specific drivers ends up support only a > subset of the hundreds or video cards & chipsets available .. and since > once they're present they would appear to preempt vesa support .. So, I > would say I am reasonably confident he will end up making his own custom > kernel if he wants to use the native driver for his video card. Yeah, last time I compiled a custom kernel was back when I first started using Linux, with Fedora Core... I thought I had to for some hardware problem or something... (New to Linux, and impressed that everything "just worked" even when using the latest kernel, and compiled by me who knew nothing about it) I was glad to discover later that it wasn't really necessary. And now my policy is to use stock kernels in Debian unless I absolutely have to use a custom kernel, because it simplifies things so much. (Wait, maybe it's a lot easier on Debian, using deb sources... perhaps I'll investigate sometime.) :) And this isn't really a problem: it just bugs me that I have to wait for my CRT monitor to switch resolutions when switching between X and other consoles. Anyway, I tried some other video= lines and nothing makes any difference. I tried vesafb, rivafb, and nvidiafb for the driver and both 1024x768 (vga=791 works fine) and 1280x960 for the resolution (all combinations for rivafb and nvidiafb, not vesafb:1024x768 I think). I don't know if it is relevant, but once the system is booted, I can load a nvidiafb module, but not either of vesafb and rivafb. Why am I not getting any errors? I can't find anything in /var/log, searching for "video" or "nvidia". Hopefully this is irrelevant: the root fs is encrypted on top of RAID5. Like I said, this isn't really a problem; if I just need to make a custom kernel, I'll drop it for now and maybe later... sometime... Thanks
Attachment:
signature.asc
Description: This is a digitally signed message part