I have installed fedora core 4.

i have a good display in display 7.
but i did not go to the terminal 1 or 2 or 3 etc.
Where the blank screen will appear.it seems terminals are working but there is no display.A black screen appears.

While shutdown the system there is no display on display 1.

#chvt 1
it goes to virtual terminal 1 but black screen will appear.

where problem stands.

this is for all the systems havinf FC4.

I noticed the shutdown problem. If you move the mouse screen becomes visible. I also noticed the CLI problem when issuing a telinit 3 to install nvidia drivers. ctrl-alt-F1 brought the login prompt back up though. So, since I found work-arounds for both has been more of an annoyance than a problem. Interestingly enough though, the original kernel shipped with FC4 didn't exhibit this behavior. Seems the issue was introduced later.

What does this means CLI problem.Actually my problem is with virtual consoles.all he ALT+CTRL+F<n> consoles are not orking except GUI and konsole.I looking for this problem more on here.

okey ,let me explain more on this.
First look at my problem.

1)My GUI is working well.
2)all the virtual consoles are not working in CTRL+ALT+F<n>,n=1,2,....
3)I have Two systems of same type or hardware setup.100% same.
4)Both installed same FC4.Both boxes have the problem.
5)Both having mandrake 10.0.Virtual consoles are working well in this mandrake.
6)so the problem is like on FC4 side only.

Just see some imagination command i issued on the virtual consoles.
1)I pressed CTRL+ALT+F1.And then typed "root"and the "passwd" for my root.
2)So i got my Virtual console in tty1.
3)And then typed "#chvt 1"
4)It comes to the GUI windows.
5)Please trust,the tty1 terminal is not visible to me.

[root@localhost ~]# who -a
root + tty1 Jan 5 17:33 00:07 2276
LOGIN tty2 Jan 5 17:14 2277 id=2
LOGIN tty3 Jan 5 17:14 2278 id=3
LOGIN tty4 Jan 5 17:14 2279 id=4
LOGIN tty5 Jan 5 17:14 2280 id=5
LOGIN tty6 Jan 5 17:14 2281 id=6
Jan 5 17:14 2282 id=x
root ? :0 Jan 5 17:15 ? 2569
root + pts/1 Jan 5 17:15 00:26 2675
root - pts/2 Jan 5 17:15 00:11 2712
root - pts/3 Jan 5 17:15 . 2716
[root@localhost ~]#

[root@localhost ~]# w
17:49:05 up 35 min, 5 users, load average: 0.93, 0.65, 0.50
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root tty1 - 17:33 14:52 0.01s 0.01s -bash
root :0 - 17:15 ?xdm? 2:28 0.04s /bin/sh /usr/bin/startkde
root pts/1 - 17:15 33:52 0.00s 3.97s kded [kdeinit]
root pts/2 - 17:15 1.00s 0.03s 0.00s w
root pts/3 - 17:15 7:05 2:48 2:48 nmap
[root@localhost ~]#


[root@localhost ~]# ps -N
PID TTY TIME CMD
1 ? 00:00:01 init
2 ? 00:00:00 ksoftirqd/0
3 ? 00:00:00 watchdog/0
4 ? 00:00:00 events/0
5 ? 00:00:00 khelper
6 ? 00:00:00 kthread
8 ? 00:00:00 kblockd/0
11 ? 00:00:00 khubd
40 ? 00:00:00 kapmd
74 ? 00:00:00 pdflush
75 ? 00:00:00 pdflush
77 ? 00:00:00 aio/0
76 ? 00:00:00 kswapd0
164 ? 00:00:00 kseriod
326 ? 00:00:00 kjournald
795 ? 00:00:00 udevd
1153 ? 00:00:00 khpsbpkt
1165 ? 00:00:00 knodemgrd_0
1314 ? 00:00:00 kjournald
1618 ? 00:00:00 dhclient
1658 ? 00:00:00 syslogd
1660 ? 00:00:00 klogd
1670 ? 00:00:00 portmap
1688 ? 00:00:00 rpc.statd
1702 ? 00:00:00 auditd
1705 ? 00:00:00 kauditd
1730 ? 00:00:00 rpc.idmapd
1743 ? 00:00:00 hcid
1751 ? 00:00:00 sdpd
1764 ? 00:00:00 krfcommd
1790 ? 00:00:00 apmd
1952 ? 00:00:00 automount
1998 ? 00:00:00 automount
2011 ? 00:00:00 nifd
2041 ? 00:00:00 mDNSResponder
2073 ? 00:00:00 cupsd
2124 ? 00:00:00 sshd
2133 ? 00:00:00 xinetd
2150 ? 00:00:00 sendmail
2156 ? 00:00:00 sendmail
2165 ? 00:00:00 gpm
2173 ? 00:00:00 crond
2202 ? 00:00:00 xfs
2210 ? 00:00:00 anacron
2217 ? 00:00:00 atd
2225 ? 00:00:00 dbus-daemon
2237 ? 00:00:00 cups-config-dae
2246 ? 00:00:00 hald
2259 ? 00:00:00 hald-addon-stor
2276 ? 00:00:00 login
2277 tty2 00:00:00 mingetty
2278 tty3 00:00:00 mingetty
2279 tty4 00:00:00 mingetty
2280 tty5 00:00:00 mingetty
2281 tty6 00:00:00 mingetty
2282 ? 00:00:00 prefdm
2460 ? 00:00:00 gdm-binary
2494 ? 00:00:00 gdm-binary
2499 ? 00:01:30 X
2569 ? 00:00:00 startkde
2619 ? 00:00:00 ssh-agent
2622 ? 00:00:00 dbus-launch
2623 ? 00:00:00 dbus-daemon
2667 ? 00:00:00 kdeinit
2670 ? 00:00:00 dcopserver
2672 ? 00:00:00 klauncher
2675 ? 00:00:04 kded
2677 ? 00:00:01 gam_server
2687 ? 00:00:00 artsd
2690 ? 00:00:00 kaccess
2691 ? 00:00:00 kwrapper
2693 ? 00:00:00 ksmserver
2694 ? 00:00:04 kwin
2698 ? 00:00:04 kdesktop
2702 ? 00:00:06 kicker
2705 ? 00:00:00 eggcups
2708 ? 00:00:00 gconfd-2
2709 ? 00:00:02 kget
2710 ? 00:00:26 konqueror
2711 ? 00:00:01 konsole
2712 pts/2 00:00:00 bash
2716 pts/3 00:00:00 bash
2757 ? 00:00:00 kio_http
2890 ? 00:00:00 kio_uiserver
2892 ? 00:00:00 knotify
2941 ? 00:00:01 konqueror
3135 ? 00:00:01 aspell
3138 tty1 00:00:00 bash
3175 ? 00:00:00 gpm-root
3225 ? 00:00:00 firefox
3242 ? 00:00:00 run-mozilla.sh
3247 ? 00:00:16 firefox-bin
3277 pts/3 00:05:50 nmap
3323 ? 00:00:00 kio_http
3358 ? 00:00:00 kio_file
3359 ? 00:00:00 kio_http
3361 ? 00:00:00 kio_http
3387 ? 00:00:00 kio_file
3403 ? 00:00:00 kio_http
3404 ? 00:00:00 kio_http
3405 ? 00:00:00 kio_http
3406 ? 00:00:00 kio_http
3407 ? 00:00:00 kio_http
3408 ? 00:00:00 kio_http
3419 ? 00:00:00 kio_about
[root@localhost ~]#

So guys what do u think abt this.Look like hardware issue ,driver,or what?

It could be the graphics mode passed to Linux on boot. Check your bootloader for a line along the lines of "vga=XXXX" (where XXXX is a number). If it's present, then try removing that bit (and only that bit) and rebooting. Note that if you're using LILO then you'll need to run /sbin/lilo for the changes to take effect.

Reason: recent(ish) distros tend to use a graphical, "pretty" screen when Linux is loading. In order for this screen to be visible, a vga mode has to be passed to the kernel. If you stop passing the vga mode to the kernel, the pretty booting screen should stop being loaded, but more importantly, Linux will just load in text mode until X11 starts up, so leaving your virtual consoles (F1-F6) text only.

i am using grub now.

[root@localhost ~]# cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,1)
# kernel /boot/vmlinuz-version ro root=/dev/hda2
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,1)
kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ acpi=off rhgb quiet
initrd /boot/initrd-2.6.11-1.1369_FC4.img
title Other
rootnoverify (hd0,0)
chainloader +1
[root@localhost ~]#

sir,i do not have any line u mentioned.should i remove "rhgb"

should i pass any extra parameter to kernel or what?

Just a pssing thought:

Did u try to disable rhgb and see what happens?

Yes now i have disabled it.And rebooted again.
i think rhgb stands for "red hat graphical bootup".Becuase the bootup is went along a non-graphical side.And suddenly the login: comes and my system goes to graphical login at 7.After i logged i have pressed CTRL+ALT+F1 to F8.I got same problem.There is no display there.Now what goes wrong.

This problem purely dedicated to FC4 only not for suse or mandrake or debian.
May due to grub bootloder or what?

I have the same problem on two FC4 systems, although on one (a desktop with a CRT monitor) the vttys aren't completely blank.

The problem has to do with VGA mode switching that isn't happening correctly when using the CTRL+ALT+Fx keys.

Here's a workaround. After logging in on the vtty, issue the following command AS ROOT: 'resizecons -lines 25' (use su if you're not root). This will switch your display into the correct VGA mode. However, as soon as you switch back to vtty 7 (GUI mode) and then try to switch to a character vtty, you'll have the same problem. And now the resizecons command won't help. However, if you use su to switch to another user, you will get your display back.

Once you have a working character vtty, you can switch between character vttys without problem. You'll only have the problem when you switch to vtty 7.

Hopefully, someone with knowledge of the CTRL+ALT+Fx key handling logic can identify the real problem.

Here's some more information on the problem. Apparently it has to do with an incorrectly generated X11 module libvgahw.a. There's more information on the Fedora News web site. Unfortunalely because I've just registered I can't put the actual URL in here, but when you get to the site, look for the page on Caveats and Known Bugs on FC4. Bug #2 may describe the cause and have a more thorough workaround. As soon as I've tested it, I'll post the results.

OK. The information in my last post was correct. It turns out that this problem is solved if you install the FC4 rpm update packages. Do yum update as root and enjoy tour vttys.

I have a problem with proxy server.
So can u please tell me the file i want to install to remove the console bug.

[root@localhost ~]# yum update
Setting up Update Process
Setting up repositories
http://ftp.ipv6.funet.fi/pub/mirrors...ta/repomd.xml: [Errno 4] IOError: HTTP Error 500: Proxy-Connection: Close
Trying other mirror.
updates-released 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
http://mirror.usu.edu/mirrors/fedora...ta/repomd.xml: [Errno 4] IOError: HTTP Error 404: Date: Sat, 21 Jan 2006 11:24:17 GMT
Server: Apache
Content-Length: 317
Content-Type: text/html; charset=iso-8859-1
Connection: Keep-Alive
Trying other mirror.
base 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 32 kB 00:24
http://ftp.ps.pl/pub/linux/fedora-co...rimary.xml.gz: [Errno 4] Socket Error: timed out
Trying other mirror.
primary.xml.gz 100% |=========================| 8.0 kB 00:18
http://mirror.hiwaay.net/redhat/fedo...rimary.xml.gz: [Errno 4] Socket Error: timed out
Trying other mirror.


Which goes on....

will u mention the lib. to update.?