Printable View
I compiled the kernel 2.4.6 the other day in slackware 8. Everything whent smooth, then i go and do a startx. Then this error appers telling me "NO Screens Found". So I do xf86config go threw all that and installed new drivers for the video card. I reinstalled 3 times finaly said screw it and stayed with the default 2.2.19 kernel. Anyways any ideas on how how or what causes this "No Screens Found" error?
Hmm...did you compile a kernel to use the Frame Buffer???Quote:
Originally posted by slick:
I compiled the kernel 2.4.6 the other day in slackware 8. Everything whent smooth, then i go and do a startx. Then this error appers telling me "NO Screens Found". So I do xf86config go threw all that and installed new drivers for the video card. I reinstalled 3 times finaly said screw it and stayed with the default 2.2.19 kernel. Anyways any ideas on how how or what causes this "No Screens Found" error?
------------------
"Given enough time and money..Microsoft will eventually invent a Unix." - ME
Why Yes! I am a proud member of the SF Linux Hippy Club.
-----------------------------
ABIT KT133A-RAID
Athlon 1.2/266 OC@1330 Mhz (10x133)
512MB PC133 Crucial RAM
2 x Quantum 20GB Fireballs
Voodoo 3 3000 AGP (Still getting 60 FPS baby)
SB Live 5.1
Linux Debian Unstable+
Linux Mandrake 8.0+
Linux Flavor of the Month
Windows 2000 Professional
BeOS 5 just for fun
No unless its picked by default. The only part I really messed with where. Nat and scsi emulation.
Could it have been an xfree problem? The only time I have ever gotten that error was when xfree wasn't set up correctly (the config file that is).Quote:
Originally posted by slick:
No unless its picked by default. The only part I really messed with where. Nat and scsi emulation.
------------------
Q: How many UGA students does it take to change a lightbulb?
A: Two, one to call a friend at GT and another to follow the directions.
I agree. In my comparitively small linux experience, i have gotten that error when messing with the XFree config file, so i'm pretty sure this is an Xfree problem.Quote:
Originally posted by jtshaw:
Could it have been an xfree problem? The only time I have ever gotten that error was when xfree wasn't set up correctly (the config file that is).
------------------
------
Pat D.
Visit a music site I write for:
http://www.geocities.com/mjareviews
I think Hit_Man is on to something, if you were using the Frame Buffer driver under XFree86 and it is working fine under kernel 2.2.19 then you will have to compile Frame Buffer support on your new 2.4 kernel. This is something that is not enabled by default, though it should be. You can always go to linuxmafia.org and download a 2.4 kernel for Slack that is already compiled and ready to run and see if the problem still exist.Quote:
Originally posted by blppt:
I agree. In my comparitively small linux experience, i have gotten that error when messing with the XFree config file, so i'm pretty sure this is an Xfree problem.
Jim
------------------
Life is art..Paint your destiny!
Sys info:
AMD Athlon 650mhz
Tyan Trinity K7
IBM PC100 256mb ram
IBM Deskstar 21gb ata66
Quantium Bigfoot 6.4gb
3Dfx Voodoo 4 4500 (for sale! $50!)
Soundblaster PCI 512
Hapauge WinTV PCI
IBM Etherjet 10/100 nic
Pioneer 8x/32x DVD
Phillips Ominiwriter
OS: WinME/Linux 2.2.19/BeOS5 PE/OS/2 E-Buisness
Other:
Toshiba Protege 7010CT
PII 300
160mb ram
Windows ME
BeOS 5 PE
I don't think it has anything to do with xf86config files. Saying that I been wrong before though. I will check out the frame buffer driver later today. Since I think thats probaly it thinking about it. Thanks for the help everyone.