Hi, On Fri, Jun 17, 2005 at 01:04:23PM +0930, Ron wrote: > Hi, I'm afraid you are going to have to clarify a few things, > and/or do some debugging of your own here. I've just been > forwarded a separate report where you claim(ed) this is the > solution? I gather you no longer believe that??
After uncommenting the "Cursor" line in /etc/TextConig I find by restarting (/etc/init.d/svgatextmode restart) I am able to activate the cursor on tty2 to tty6. If there are things you would like me to look into, do mention and I'll take a stab at them. > > This could be a whole lot of things, and possibly specific > to your graphics card. It is impossible for me to say on > the information given. > My graphics card is Riva TNT based Nvidia's Diamond Viper 550. My computer is an old one, Intell Pentium II (Deschutes) with the 440BX motherboard. My monitor is a Sony Trinitron Multiscan 200sx. > I will take one punt though, now that I have some inkling this > may be with kernel 2.6, and suggest you look at the initialisation > order of related things after a cold boot. > I have not changed anything about the initialization order in any way. In fact if I create /etc/rc2.d/S99local -> /etc/init.d/local and add a line "/etc/init.d/svgatextmode restart", this does not solve the problem. I need to log in from tty1 and manually do the restart to get the cursor working. This is very odd and I have no clue what is happening here. Permit me to repeat this for emphasis restarting SVGATextMode at no point in the boot process, no matter how late (such as through /etc/init.d/local) does not fix the problem. It needs to be started manually after a console login from the working tty1. Further logging in through tty2-tty6 and restarting causes a problem in that only half my monitor screen seems to be used. > If simply restarting stm makes things better, it is possible > that we are initialising something too early (or late) now, > before udev and/or other mechanisms fully configure the all > console vt's or so. > As mentioned restarting from /etc/init.d/local after udev has created the device nodes does not seem to help. > But I'm not going to be able to do much here without a tested > patch, or a much more detailed analysis of exactly what is > going wrong on what sort of systems. > Ok. I'll try looking into this as and when I get a new idea. I have run out of them for now :-(. > Is anyone else (not) seeing this? > > Ron > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
