if the syslog-ng service get started in the init process the cursor dont get moved to the next line and stay there the service starts without a error. then i see "login : " prompt but there is no cursor login works its np, pressing ALT-F2/F1 get the cursor on the prompt back to. checked the log's but found nothing im not 100% sure but i thing this starts after i upgrade to kernel 2.6.16 Nothing important/critical, but if you have some time check it out plz. emerge --info : Gentoo Base System version 1.12.0_pre16 Portage 2.1_pre7-r1 (default-linux/x86/2006.0, gcc-3.4.4, glibc-2.3.6-r3, 2.6.16-gentoo i686) ================================================================= System uname: 2.6.16-gentoo i686 AMD Athlon(TM) XP 2500+ ccache version 2.4 [enabled] dev-lang/python: 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=athlon-xp -pipe" DISTDIR="/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS=".cut." LC_ALL="de_DE@euro" LINGUAS="de" PKGDIR="/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/portage/main" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X alsa apache2 apm avi berkdb bitmap-fonts cdr cli crypt ctype cups dba dbus dri dvd eds emboss encode expat fam fastbuild foomaticdb force-cgi-redirect fortran ftp gd gdbm gif gpm gstreamer gtk2 hal imlib ipv6 jpeg kde libg++ libwww linguas_de mad mbox memlimit mikmod motif mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre pdflib perl png posix python qt quicktime readline sdl session simplexml soap sockets spell spl ssl tcpd tokenizer truetype truetype-fonts type1-fonts udev userlocales vorbis xml xmms xsl xv zlib elibc_glibc input_devices_evdev input_devices_keyboard input_devices_mouse input_devices_joystick kernel_linux userland_GNU video_cards_fglrx" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LDFLAGS, MAKEOPTS, PORTDIR_OVERLAY
What makes you think this is related to syslog-ng?
i pressed I for Interactice Init Mode and then i start one service after another by confirming it with a keypress to find exactly where its happend and after syslog-ng got started the cursor was not moved correctly.
and if you remove syslog-ng from startup, things work fine ?
I can confirm this. It started for me after upgrade to gentoo-sources-2.6.16. Still here with gentoo-sources-2.6.16-r1. If I boot single user mode, I have to do these two things: /etc/init.d/consolefont start /etc/init.d/syslog-ng start The cursor always jumps up to the line just under "Setting user font...". What I mean is, if I boot in normal mode without syslog-ng, so that consolefont starts normally, and then start syslog-ng, the cursor jumps up about half the screen up into the boot messages. The cursor goes to that line, but typed characters appear where they should. The problem is consolefont + syslog-ng, not keymaps + syslog-ng. I have not modified /etc/conf.d/consolefont.
I just figured out that this only happens on a framebuffer console.
(In reply to comment #5) > I just figured out that this only happens on a framebuffer console. > confirmed i use "video=vesafb:1280x1024-16@85,ywrap,mtrr" as kernel parameter after some deeper testing i found out that the "ywrap" parameter causing this, without ywrap its works fine.
ok, not syslog-ng related then...
I too was using ywrap. I found it also happens with ypan.
vesafb-tng bug
Hmm, I think I saw this a few times on my own system as well. I'm not sure how to reproduce it though (I'm using ywrap all the time, and it the bug doesn't always manifest itself). If any of you are able to reproduce it, could you please check whether you get the same behaviour with the standard vesafb driver?
This problem does not happen with gentoo-sources-2.6.17.
Closing since the problem appears to be fixed in gs-2.6.17.