Build Your Own Arcade Controls Forum
Main => Everything Else => Topic started by: TalkingOctopus on January 16, 2005, 03:12:34 am
-
I finally upgraded from Redhat 7 to Fedora core 3.
-
try booting linux single from grub , that should get you to the command line and not X , from their you can change your default run mode to 3 insted of the 5 it's in now ... then when you want to run X just do a startx from the command line , if that locks up on you you should still be able to do a ctrl-alt-f1 , or f2 , f3 etc and get to command.
-
The problem is that when I go to the commandline, nothing is sent to my monitor. There must be some kind of problem between my videocard and whatever vga mode it is using. Nothing is locking up. It just that nothing is displayed on the monitor.
-
Well it turns out I can boot to x from grub by editing the load commmand. I added linux 5 to get back into x. However, linux 3 still does not work. Nothing is displayed :(.
-
ah ok ... hmm , their are vga stuff you can put on the kernel line in grub for the command prompt .. just dont know them off hand and i'm at work ATM , if i work it out i'll post
-
ah ok ... hmm , their are vga stuff you can put on the kernel line in grub for the command prompt .. just dont know them off hand and i'm at work ATM , if i work it out i'll post
I figured out what I needed to. Thanks for the help. I can only boot into X, but once in X, I can run sbin/init 3 and it takes me to the prompt - a visible prompt!
-
from the grub FAQ ( i know you fixed your problem , but i'm posting this anyway :P )
root (hd0,1)
kernel /vmlinuz-2.4.16 root=/dev/hda2 hdd=ide-scsi vga=791
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
-
There are issues with the framebuffer with late 2.6 kernels,so you may want to disable it completely which will probably reuiqre you to compile your own kernel.Also fedora is bugged at the best of times,so be prepared for these issues coming up often.The main reason for this is the kernels after 2.6.7 are pretty much like development series kernels i.e frequently bugged and with lots of new features that aren't stable yet new schedulers,reiser4,memory management tweaks etc. Hopefully these will all be ready by 2.6.11,as some of these tweaks bring some nice performance improvements.