Xen dom0 virtual terminals
Hi! This may be a naive question, but does anyone know how to enable the virtual terminals (Ctrl-Alt-Fx) on a Wheezy dom0? -- Best regards, Panayiotis Karabassis -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f362b40.2000...@gmail.com
No virtual terminals
Running squeeze. I have NVidia video. Problem is, I have no virtual 8terminals. ctrl-alt-f1 to 6 gets me a blank screen, although c-a-f8 (yes, f8) does bring back X. I've looked for solutions but nothing I've found works. E.g., I created /etc/modprobe.d/nvidia-kernel-nkc.conf with one line - options nvidia NVreg_UseVBios=0. Still, I got nada. Any hints, pointers, etc. greatly appreciated. -- Everywhere I go I'm asked if I think the university stifles writers. My opinion is that they don't stifle enough of them. -- Flannery O'Connor -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009091934.58428.edj...@gmail.com
Re: Complete system freeze from virtual terminals / terminal emulators
[ If you want to make sure that your messages show up in the correct thread then you have to provide In-Reply-To headers. With your webmail interface it is probably best to use Reply-To-All and then to remove the email address of the original poster and to shift the list address from Cc: to To:. ] Thanks for the tips Florian :) I'm more used to forums than mailing lists :P I would also go to K-Menu Control Center Sound Multimedia System Bell and check the settings there. I don't know which other parts of KDE might want to use the system bell but it cannot hurt to make sure it is deactivated for all of KDE. I checked the system bell settings in the control center, and fortunately It was not enabled, so it shouldn't be a problem in any other applications. It looks like your X setup is OK as far as the graphics card is concerned (see my remarks below). Maybe the problem is in some weird way related to the pcspkr module which controls the system bell. You could try to (un)load the module and see if that makes any difference. The whole thing might be a very rare coincidence of several factors; tracking it down might be difficult and not really worth it. [...] Brilliant Florian, the problem does seem to be the pcspkr module. I modprobe -r pcspkr and the terminal works fine, then I modprobe pcspkr and everything freezes again. So I suppose all I have to do is blacklist the pcspkr module or something like that and my problems should be over. Should I file a bug report for this with the kernel team then?? Thanks again for all your help, Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
On Sat, Apr 14, 2007 at 21:09:16 -0700, Pat Primate wrote: Florian Kulzer wrote earlier: [...] It looks like your X setup is OK as far as the graphics card is concerned (see my remarks below). Maybe the problem is in some weird way related to the pcspkr module which controls the system bell. You could try to (un)load the module and see if that makes any difference. The whole thing might be a very rare coincidence of several factors; tracking it down might be difficult and not really worth it. [...] Brilliant Florian, the problem does seem to be the pcspkr module. I modprobe -r pcspkr and the terminal works fine, then I modprobe pcspkr and everything freezes again. So I suppose all I have to do is blacklist the pcspkr module or something like that and my problems should be over. Should I file a bug report for this with the kernel team then?? I would first test if the pcspkr module works (beeps) on the TTYs. This bug could very well be somewhere in KDE (or X) and the absence of the pcspkr module might fix things only because it leads to KDE/X skipping some buggy code. You can check dmesg | grep -i speaker for clues while playing around with the module. It would be especially interesting to see if the magic switch X-TTY-X changes anything in /dev/input. (Don't ask me why the device node of the speaker is generated in input.) Anyway, if all else fails you can simply use echo blacklist pcspkr /etc/modprobe.d/pcspkr to blacklist the pcspkr module during boot. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
Thank you Florian and Kamaraju, I am impressed by the speed and helpfulness of the Debian-Users mailing list :) As for my system, I am completely up to date (clean install of 4.0r0) and the crash doesn't happen in the tty1 terminals, Only inside KDE/X11. I checked the bell settings in Konsole (settings --- bell) and it was set to System bell and not visual bell, BUT (the good news) I tried setting the bell settings to 'system notification', 'visual bell', and 'none' and all three of those settings allow me to use konsole with NO CRASHES :D So it seems that the crashes only happen when the bell setting is set to 'system bell', but the funny thing is that I don't actually hear the bell beep, the crash happens first (even though my sound SEEMS to work fine for other things). So here are the attachments you wanted me to add, if you could help me figure out where to file a bug report and what info to include I would be very grateful :) Thank you both so much Pat 1) lspci | egrep -i 'vga|display|video|graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) -- 2) awk '/Section (Device|Module)/,/EndSection/' /etc/X11/xorg.conf Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe EndSection Section Device Identifier Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller Driver i810 BusID PCI:0:2:0 EndSection -- 3) patop:/home/pat# egrep '^\((EE|WW)\)' /var/log/Xorg.0.log (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist. (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): config file hsync range 43.8857-48.5053kHz not within DDC hsync ranges. (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Extended BIOS function 0x5f05 failed. (WW) AIGLX: 3D driver claims to not support visual 0x23 (WW) AIGLX: 3D driver claims to not support visual 0x24 (WW) AIGLX: 3D driver claims to not support visual 0x25 (WW) AIGLX: 3D driver claims to not support visual 0x26 (WW) AIGLX: 3D driver claims to not support visual 0x27 (WW) AIGLX: 3D driver claims to not support visual 0x28 (WW) AIGLX: 3D driver claims to not support visual 0x29 (WW) AIGLX: 3D driver claims to not support visual 0x2a (WW) AIGLX: 3D driver claims to not support visual 0x2b (WW) AIGLX: 3D driver claims to not support visual 0x2c (WW) AIGLX: 3D driver claims to not support visual 0x2d (WW) AIGLX: 3D driver claims to not support visual 0x2e (WW) AIGLX: 3D driver claims to not support visual 0x2f (WW) AIGLX: 3D driver claims to not support visual 0x30 (WW) AIGLX: 3D driver claims to not support visual 0x31 (WW) AIGLX: 3D driver claims to not support visual 0x32 -- h, bad v_bios checksum eh.. I had 915Resolution installed on a previous operating system - would that cause that??? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
[ If you want to make sure that your messages show up in the correct thread then you have to provide In-Reply-To headers. With your webmail interface it is probably best to use Reply-To-All and then to remove the email address of the original poster and to shift the list address from Cc: to To:. ] On Fri, Apr 13, 2007 at 10:08:58 -0700, Pat Primate wrote: Thank you Florian and Kamaraju, I am impressed by the speed and helpfulness of the Debian-Users mailing list :) As for my system, I am completely up to date (clean install of 4.0r0) and the crash doesn't happen in the tty1 terminals, Only inside KDE/X11. I checked the bell settings in Konsole (settings --- bell) and it was set to System bell and not visual bell, BUT (the good news) I tried setting the bell settings to 'system notification', 'visual bell', and 'none' and all three of those settings allow me to use konsole with NO CRASHES :D So it seems that the crashes only happen when the bell setting is set to 'system bell', but the funny thing is that I don't actually hear the bell beep, the crash happens first (even though my sound SEEMS to work fine for other things). I would also go to K-Menu Control Center Sound Multimedia System Bell and check the settings there. I don't know which other parts of KDE might want to use the system bell but it cannot hurt to make sure it is deactivated for all of KDE. So here are the attachments you wanted me to add, if you could help me figure out where to file a bug report and what info to include I would be very grateful :) It looks like your X setup is OK as far as the graphics card is concerned (see my remarks below). Maybe the problem is in some weird way related to the pcspkr module which controls the system bell. You could try to (un)load the module and see if that makes any difference. The whole thing might be a very rare coincidence of several factors; tracking it down might be difficult and not really worth it. [...] 1) lspci | egrep -i 'vga|display|video|graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) -- 2) awk '/Section (Device|Module)/,/EndSection/' /etc/X11/xorg.conf Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe EndSection Section Device Identifier Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller Driver i810 BusID PCI:0:2:0 EndSection All is fine as far as I can tell. -- 3) patop:/home/pat# egrep '^\((EE|WW)\)' /var/log/Xorg.0.log (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. [ snip: similar errors for other font directories ] You can comment out these paths in the Files section of your xorg.conf to make these (harmless) warnings go away. (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found I see the same here (Intel Q965 chipset) and I never noticed any problem arising from it. (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): config file hsync range 43.8857-48.5053kHz not within DDC hsync ranges. (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Extended BIOS function 0x5f05 failed. My laptop (Intel 855GM chipset) works without trouble in spite of similar Bad V_BIOS and Extended BIOS function ... warnings. I think these are symptoms of minor glitches of the driver. You have to adjust the values in the Monitor section of xorg.conf if you want to get rid of the hsync range message. (WW) AIGLX: 3D driver claims to not support visual 0x23 [ snip: the same for other visuals ] Same story: I get these warnings too and I never had problems. I guess these messages will go away once AIGLX support for the Intel chipsets has matured a bit more. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Complete system freeze from virtual terminals / terminal emulators
I have an LG LW40-S3MU1 laptop and I'm new to Debian and I would love to give her a good run, but I have run into a persistant problem. With a fresh install (all software is original Etch 4.0r0 versions) if I open up a virtual terminal / terminal emulator (like konsole) and press one of the arrow keys on my keyboard (e.g., the left arrow key) my entire system will freeze solid I have to hold the power button down for 4 or 5 seconds to shut it down. The freeze is easily replicated (every single time I try). To make this more clear, If I open up Konsole, Yakuake, Xterm, or Eterm (those were the 4 terminal emulators I tried it on) and I press the left arrow key - my entire system freezes completely The same thing happens if I press the right arrow key, or the down arrow key or the up arrow key. To make matters weirder, if I pres ctrl+alt+F1 to enter one of the tty1 sessions (I don't even have to log in) and then press ctrl+alt+F7 to get back to the KDE desktop I can suddenly go into any of the terminal emulation programs and press the arrow keys to my hearts content, without any freezes I would of course like to fix this, but I would also like to file a bug report for this. I unfortunately do not know which application to file the bug for, and I do not what/how to dig for more useful debug information. A post on the Debian-help forums suggested I access my Dmesg log from a live cd after the freeze - I will do that as soon as I have a live cd downloaded. Any advice or feedback would be appreciated Thank you very much Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
Pat Primate wrote: I have an LG LW40-S3MU1 laptop and I'm new to Debian and I would love to give her a good run, but I have run into a persistant problem. With a fresh install (all software is original Etch 4.0r0 versions) if I open up a virtual terminal / terminal emulator (like konsole) and press one of the arrow keys on my keyboard (e.g., the left arrow key) my entire system will freeze solid I have to hold the power button down for 4 or 5 seconds to shut it down. The freeze is easily replicated (every single time I try). When the freeze happens, are you able to ssh into that machine? If so, then you can check /var/log/Xorg.0.log and see if you find any errors. Another workaround is to completely disable the graphical environments (KDM etc.,) and see if you can reproduce the crash in a pure console based environment. If the console based system does not hang, run startx and see what errors you are receiving. BTW, are all your packages up to date? Sometimes when the KDE packages from different versions are mixed together, strange things can happen. hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
On Thu, Apr 12, 2007 at 11:39:20 -0700, Pat Primate wrote: I have an LG LW40-S3MU1 laptop and I'm new to Debian and I would love to give her a good run, but I have run into a persistant problem. With a fresh install (all software is original Etch 4.0r0 versions) if I open up a virtual terminal / terminal emulator (like konsole) and press one of the arrow keys on my keyboard (e.g., the left arrow key) my entire system will freeze solid I have to hold the power button down for 4 or 5 seconds to shut it down. The freeze is easily replicated (every single time I try). To make this more clear, If I open up Konsole, Yakuake, Xterm, or Eterm (those were the 4 terminal emulators I tried it on) and I press the left arrow key - my entire system freezes completely The same thing happens if I press the right arrow key, or the down arrow key or the up arrow key. It seems that the (visual) bell hangs your system. (???) To make matters weirder, if I pres ctrl+alt+F1 to enter one of the tty1 sessions (I don't even have to log in) and then press ctrl+alt+F7 to get back to the KDE desktop I can suddenly go into any of the terminal emulation programs and press the arrow keys to my hearts content, without any freezes Do you see the terminal window flash or do you hear a beep if you press one of the arrow keys in this situation? That would at least tell us if the bell could really be responsible for the hard lock. I think the main effect of your magic fix (X-tty-X) is that the video mode of your graphics card gets changed twice. Your initial problem might therefore be related to an initialization error of the video hardware, so maybe we should have a closer look at that. Please post the output of the following three commands: lspci | egrep -i 'vga|display|video|graphics' awk '/Section (Device|Module)/,/EndSection/' /etc/X11/xorg.conf egrep '^\((EE|WW)\)' /var/log/Xorg.0.log -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Subject: Re: Complete system freeze from virtual terminals / terminal emulators
Ooops, sorry everyone, I accidently forgot to put the subject in my previous post. So if Florian or Kamaraju did not read my 'no subject' post (sent 2 minutes ago) please do so, I have responses to your questions :) Thanx pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Thu Jan 18 14:05:12 2007, Kevin Ross wrote: CTRL-ALT-Fx is for switching virtual consoles while X is running. Use just ALT-Fx while at a regular console. Yes, I should have been more precise. In my experience (most recently Red Hat WS3), ALT-Fx works from a regular console. CTRL-ALT-Fx works from both a regular console and from X. In any case, I have a problem now with etch. Neither ALT-Fx nor CTRL-ALT-Fx gives a virtual terminal under any circumstance I've tried, including: During installation After booting to a regular console From the X window I get after calling xinit From the gnome desktop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Thu, Jan 18, 2007 at 07:05:36PM -0500, Steve Kleene wrote: On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Thu Jan 18 14:05:12 2007, Kevin Ross wrote: CTRL-ALT-Fx is for switching virtual consoles while X is running. Use just ALT-Fx while at a regular console. Yes, I should have been more precise. In my experience (most recently Red Hat WS3), ALT-Fx works from a regular console. CTRL-ALT-Fx works from both a regular console and from X. In any case, I have a problem now with etch. Neither ALT-Fx nor CTRL-ALT-Fx gives a virtual terminal under any circumstance I've tried, including: During installation After booting to a regular console From the X window I get after calling xinit From the gnome desktop Init runs getty on the VTs. Are they running? ps -C getty from within whatever terminal you do have will tell you this. If there's no getty, then there's nothing to switch to (e.g. on a regular system, ALT-F9 does nothing). Just a thought. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 15:13:59 2007, Matt Zagrabelny wrote: when i boot, the screen flickers when it is spawning the getty's. does your screen flicker when the boot message says it is spawning the getty's? I never see it flicker. I also didn't catch any message about spawning the gettys. They go by pretty fast. I didn't see anything in dmesg or /var/log/messages either. have you modified /etc/inittab ? I just made one change, changing initdefault from 2 to 3. I removed /etc/rc3.d/S21gdm so that runlevel 3 comes up as a console. if you put in the install disc again, do the VC's work in the installer? No. F1, etc, by themselves give the help menus at the boot prompt. At no point, though, does CTRL-ALT-Fn give a virtual terminal. Thanks. CTRL-ALT-Fx is for switching virtual consoles while X is running. Use just ALT-Fx while at a regular console. -- Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
no virtual terminals after fresh etch install
I just did my first Debian install on a new desktop using the testing- i386-netinst CD. The install completed and I have several problems to look into. Here's the first. I am booting into runlevel 3, which I set to bring up a console instead of gnome. This works, but I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. I recently also brought up Ubuntu Edgy and had the same problem. I gave up on Ubuntu for other reasons. I'd appreciate any suggestions on how to get the virtual terminals working. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, Steve Kleene wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. The install completed and I have several problems to look into. Here's the first. I am booting into runlevel 3, which I set to bring up a console instead of gnome. This works, but I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. I recently also brought up Ubuntu Edgy and had the same problem. I gave up on Ubuntu for other reasons. I'd appreciate any suggestions on how to get the virtual terminals working. Thanks. Maybe have a look at: http://wiki.debian.org/DebianInstaller/Today Thierry -- Linux is like a tipi: no Windows, no Gate and an Apache inside -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Mon, 15 Jan 2007 13:01:49 -0500 Steve Kleene [EMAIL PROTECTED] wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. The install completed and I have several problems to look into. Here's the first. I am booting into runlevel 3, which I set to bring up a console instead of gnome. This works, but I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. I recently also brought up Ubuntu Edgy and had the same problem. I gave up on Ubuntu for other reasons. I'd appreciate any suggestions on how to get the virtual terminals working. Thanks. What changes did you make to runlevel 3? Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 13:15:29 2007, Thierry Chatelet wrote: Maybe have a look at: http://wiki.debian.org/DebianInstaller/Today Thanks, Thierry. I looked there and didn't see anything that helped. It did suggest that I try apt-get install xserver-xorg-video-all xserver-xorg-input-all I did that and was told that I already have the newest versions. I did select the Desktop Environment during the software-selection stage of the install. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 13:15:38 2007, Andrei wrote: What changes did you make to runlevel 3? Just one: I removed /etc/rc3.d/S21gdm. And I set initdefault to 3 in /etc/inittab. I forgot to mention that processes are running for tty[2-5], e.g. /sbin/getty 38400 tty2 Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Mon, 15 Jan 2007 13:45:09 -0500 Steve Kleene [EMAIL PROTECTED] wrote: On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 13:15:38 2007, Andrei wrote: What changes did you make to runlevel 3? Just one: I removed /etc/rc3.d/S21gdm. And I set initdefault to 3 in /etc/inittab. I forgot to mention that processes are running for tty[2-5], e.g. /sbin/getty 38400 tty2 Maybe it's a problem with your keymap and the system doesn't recognize the ALT or the F1 key. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 14:05:09 2007 Andrei wrote: Maybe it's a problem with your keymap and the system doesn't recognize the ALT or the F1 key. I'm not sure how to check this. If I call xinit, I do get a crude X-window. Holding down ALT plus various keys does give various non-ASCII characters as expected, and xmodmap -pm shows Alt_L and Alt_R as mod1. In console mode (no X), different things happen. Hitting ALT-g, for example, caused the string Desktop/ to appear. F1 doesn't seem to send anything in either situation or when gnome is running. However, the Fn keys were functional at the very start of the install and gave the usual help screens. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:40, Steve Kleene wrote: On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 13:15:29 2007, Thierry Chatelet wrote: Maybe have a look at: http://wiki.debian.org/DebianInstaller/Today Thanks, Thierry. I looked there and didn't see anything that helped. It did suggest that I try apt-get install xserver-xorg-video-all xserver-xorg-input-all I did that and was told that I already have the newest versions. I did select the Desktop Environment during the software-selection stage of the install. The problem seems to hav evolved! I did an install 3 days ago and go out of this problem by, first installing apt-get install xserver-xorg-video-vesa, and then, since the video card was a nvidia, installing nvidia driver. If someone can help more Thierry -- Linux is like a tipi: no Windows, no Gate and an Apache inside -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no virtual terminals after fresh etch install
On Mon, 2007-01-15 at 13:01 -0500, Steve Kleene wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. The install completed and I have several problems to look into. Here's the first. I am booting into runlevel 3, which I set to bring up a console instead of gnome. This works, but I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. when i boot, the screen flickers when it is spawning the getty's. does your screen flicker when the boot message says it is spawning the getty's? have you modified /etc/inittab ? if you put in the install disc again, do the VC's work in the installer? -- Matt Zagrabelny - [EMAIL PROTECTED] - (218) 726 8844 University of Minnesota Duluth Information Technology Systems Services PGP key 1024D/84E22DA2 2005-11-07 Fingerprint: 78F9 18B3 EF58 56F5 FC85 C5CA 53E7 887F 84E2 2DA2 He is not a fool who gives up what he cannot keep to gain what he cannot lose. -Jim Elliot signature.asc Description: This is a digitally signed message part
Re: no virtual terminals after fresh etch install
On Monday 15 January 2007 19:01, I wrote: I just did my first Debian install on a new desktop using the testing- i386-netinst CD. ... I cannot bring up the usual virtual terminals 1-6 (e.g. CTRL-ALT-F1). If I try, nothing at all happens. On Mon Jan 15 15:13:59 2007, Matt Zagrabelny wrote: when i boot, the screen flickers when it is spawning the getty's. does your screen flicker when the boot message says it is spawning the getty's? I never see it flicker. I also didn't catch any message about spawning the gettys. They go by pretty fast. I didn't see anything in dmesg or /var/log/messages either. have you modified /etc/inittab ? I just made one change, changing initdefault from 2 to 3. I removed /etc/rc3.d/S21gdm so that runlevel 3 comes up as a console. if you put in the install disc again, do the VC's work in the installer? No. F1, etc, by themselves give the help menus at the boot prompt. At no point, though, does CTRL-ALT-Fn give a virtual terminal. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg and virtual terminals still
Bill Thompson wrote: On Thu, 14 Jul 2005 17:54:22 -0700 Paul Scott [EMAIL PROTECTED] wrote: Starting a new thread which may or may not be the same problem as the others had with virtual terminals. On one of three machines that I switched to xorg when I go to a virtual terminal I get a text mode screen with various colored stripes and no readable characters. I can tell that the VT's are actually working. I can log in but the screen is unreadable (because of all the unwanted ANSI escape codes?). reset doesn't help. I am running the latest xorg packages and have done dpkg-reconfigure xserver-xorg Any ideas? It sounds more like a video driver issue that the XKB trouble we were discussing earlier. Have you tried using a frame buffer setting like VESA for your driver? I guess I don't really understand how this is working. I switched the video driver to VESA instead of s3/virge which is the correct one and the one I used with Xfree86. This did solve the VT problem. If this is what you me can you refer me to something to read to understand how this works? I still have to change the mouse protocol to ImPs/2 each time I dpkg-reconfigure since it gets set to Imtellimouse with presenting me the opportunity to change it to ImPS/2 during the dpkg-reconfigure. Do I need to temporarily change the mouse to /dev/psaux instead of /dev/gpmdata to change the protocol? Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg and virtual terminals still
On Fri, 15 Jul 2005 00:26:42 -0700 Paul Scott [EMAIL PROTECTED] wrote: Bill Thompson wrote: On Thu, 14 Jul 2005 17:54:22 -0700 Paul Scott [EMAIL PROTECTED] wrote: Starting a new thread which may or may not be the same problem as the others had with virtual terminals. On one of three machines that I switched to xorg when I go to a virtual terminal I get a text mode screen with various colored stripes and no readable characters. I can tell that the VT's are actually working. I can log in but the screen is unreadable (because of all the unwanted ANSI escape codes?). reset doesn't help. I am running the latest xorg packages and have done dpkg-reconfigure xserver-xorg Any ideas? It sounds more like a video driver issue that the XKB trouble we were discussing earlier. Have you tried using a frame buffer setting like VESA for your driver? I guess I don't really understand how this is working. I switched the video driver to VESA instead of s3/virge which is the correct one and the one I used with Xfree86. This did solve the VT problem. If this is what you me can you refer me to something to read to understand how this works? I still have to change the mouse protocol to ImPs/2 each time I dpkg-reconfigure since it gets set to Imtellimouse with presenting me the opportunity to change it to ImPS/2 during the dpkg-reconfigure. Do I need to temporarily change the mouse to /dev/psaux instead of /dev/gpmdata to change the protocol? Possibly if you remove the mdetect package which allows for autodetecting the mouse, it will ask you manually to give the information. Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg and virtual terminals still
On Fri, 15 Jul 2005 00:26:42 -0700 Paul Scott [EMAIL PROTECTED] wrote: I guess I don't really understand how this is working. I switched the video driver to VESA instead of s3/virge which is the correct one and the one I used with Xfree86. This did solve the VT problem. If this is what you me can you refer me to something to read to understand how this works? Since VESA is a generic frame buffer driver it will work with almost any card, although not usually as well as a specific driver. Perhaps the name of the driver for your card in X.org has changed from Xfree86? Check out http://wiki.x.org/wiki/VideoDrivers for a list of which chip-sets use which x.org drivers. I notice there are three different s3 drivers currently listed. Good luck, -- Bill Thompson [EMAIL PROTECTED] pgpPLTuF7Lt0J.pgp Description: PGP signature
xorg and virtual terminals still
Starting a new thread which may or may not be the same problem as the others had with virtual terminals. On one of three machines that I switched to xorg when I go to a virtual terminal I get a text mode screen with various colored stripes and no readable characters. I can tell that the VT's are actually working. I can log in but the screen is unreadable (because of all the unwanted ANSI escape codes?). reset doesn't help. I am running the latest xorg packages and have done dpkg-reconfigure xserver-xorg Any ideas? TIA, Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg and virtual terminals still
On Thu, 14 Jul 2005 17:54:22 -0700 Paul Scott [EMAIL PROTECTED] wrote: Starting a new thread which may or may not be the same problem as the others had with virtual terminals. On one of three machines that I switched to xorg when I go to a virtual terminal I get a text mode screen with various colored stripes and no readable characters. I can tell that the VT's are actually working. I can log in but the screen is unreadable (because of all the unwanted ANSI escape codes?). reset doesn't help. I am running the latest xorg packages and have done dpkg-reconfigure xserver-xorg Any ideas? It sounds more like a video driver issue that the XKB trouble we were discussing earlier. Have you tried using a frame buffer setting like VESA for your driver? -- Bill Thompson [EMAIL PROTECTED] pgpU6XYXjjl1v.pgp Description: PGP signature
Re: Inaccessible virtual terminals (monitor problem?)
On Thu, Apr 01, 2004 at 10:18:23AM +0900, Victor Munoz wrote:
Hello. During the last couple of weeks I've had to live with the xwindows
virtual terminal only, as I cannot use the text ones. When I switch with
Ctrl-Alt-Fn, n=1,...,6, I only get some monitor information about frequency.
It seems to be complaining (sorry, it's in Japanese!), but it's a little
weird that if it is a problem with the electronics, it only complains in
text mode. Does this make sense to anyone?
Rebooting solves the problem, for a while though.
I tried to reset terminals with
ps aux | grep getty | awk '{print $2}' | xargs kill -HUP
I have the same problem, but in my case it is related to using the
wrong (but best option) video driver. I have to use vesa, since I have
a Radeon 9800, for which there isn't anything available, except the
ati binaries. But these cause a bunch of problems, hence my use of
vesa.
HTH
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Inaccessible virtual terminals (monitor problem?)
Hello. During the last couple of weeks I've had to live with the xwindows
virtual terminal only, as I cannot use the text ones. When I switch with
Ctrl-Alt-Fn, n=1,...,6, I only get some monitor information about frequency.
It seems to be complaining (sorry, it's in Japanese!), but it's a little
weird that if it is a problem with the electronics, it only complains in
text mode. Does this make sense to anyone?
Rebooting solves the problem, for a while though.
I tried to reset terminals with
ps aux | grep getty | awk '{print $2}' | xargs kill -HUP
but the problem didn't go. I don't have a spare monitor to try now, and
would like to try any operating system solution possible before trying to
get a new monitor.
Thanks for any help,
Victor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
virtual terminals become unusable when starting x on sid
hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals become unusable when starting x on sid
On Mon, Nov 17, 2003 at 12:38:16PM +, navaja wrote: hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. video driver? kernel module(s) where applicable? framebuffer for vts? -- Jon Dowland http://jon.dowland.name/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals become unusable when starting x on sid
navaja wrote: hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. thanks And what happens if you then go back to X (alt-ctrl-F7) and back again to the virtual terminal? Hugo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals become unusable when starting x on sid
on Mon, Nov 17, 2003 at 12:38:16PM +, navaja ([EMAIL PROTECTED]) wrote: hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. You need to provide more information. I'd very strongly recommend you read the following excellent essay by Simon Tatham, How to Report Bugs Effectively: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html The essay How To Ask Questions The Smart Way by Eric S. Raymond and Rick Moen essay is is also good: http://www.catb.org/~esr/faqs/smart-questions.html Please note that you are the person in the best position to know what you're trying to do, what you've done, how the system's responded, and generally how it's configured. It's very helpful if you can post: - *Exact* commands or steps tried. - *Exact* error output or log messages. Often, entering the error messages into a good search engine such as AlltheWeb (http://www.alltheweb.com/) or Google (http://www.google.com/) will help set you on the road to resolving your problems. While others can offer suggestions, guidance, and experience, we cannot see into either your mind or your machine's state. This is very much a case of you have to help us help you. Good luck. Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? The truth behind the H-1B IT indentured servant scam: http://heather.cs.ucdavis.edu/itaa.real.html pgp0.pgp Description: PGP signature
Compaq Armada and virtual terminals messing up
hi, i'm running unstable, and xfree86 3.2.1-14 before starting x everything is fine. Then I start it and when i try to to got to one of the virtual terminal consoles, the screen is messed up. Even if I stop X they stay messed up (ie loads of colors just garbage completely unreadeable) anyone had a similar problem? my settins for the virtual terminals dont seem ideal as text is only printed in a small square in the screen, it doesent take up the whole screen width or height for some reason thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals
The file you probably want is /etc/inittab. the lines in my (unstable) setup that control the virtual terminals are: 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 But notice that only tty1 is started if I am in run level 5. I just migrated to Debian myself. Just installing the x-windows-systems metapackage and kdm caused the kdm manager to launch and switch to what would be virtual terminal 7. BUT I AM STILL IN RUN LEVEL 2!! (I think. at least thats the default run level from inittab.) So what may have happened is that you may be more use to the RedHat way of doing things and you may have edited /etc/inittab to fire up at runlevel 5 the way RedHat gets X going. If you've done this then you accidentally disabled the other virtual terminals. I didn't have to change anything in /etc/inittab. My basic installation runs at runlevel 2 and launchs the graphical login manager with the same results as RedHat's system. - Jeff On Wed, 2003-07-23 at 22:02, dm wrote: Ok quick question, my girlfriend's system after installing a display manager (gdm, xdm, or kdm) only starts one virtual terminal. This was awhile ago when she was in testing, now she is in unstable, this has been bothering her for a while now, and I would like to fix it, what config file do I need to change. Thank you in advance, dm. signature.asc Description: This is a digitally signed message part
Re: virtual terminals
On Thu, 2003-07-24 at 08:52, Jeff Wiegley wrote: The file you probably want is /etc/inittab. the lines in my (unstable) setup that control the virtual terminals are: 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 But notice that only tty1 is started if I am in run level 5. I just migrated to Debian myself. Just installing the x-windows-systems metapackage and kdm caused the kdm manager to launch and switch to what would be virtual terminal 7. BUT I AM STILL IN RUN LEVEL 2!! (I think. at least thats the default run level from inittab.) So what may have happened is that you may be more use to the RedHat way of doing things and you may have edited /etc/inittab to fire up at runlevel 5 the way RedHat gets X going. If you've done this then you accidentally disabled the other virtual terminals. I didn't have to change anything in /etc/inittab. My basic installation runs at runlevel 2 and launchs the graphical login manager with the same results as RedHat's system. - Jeff On Wed, 2003-07-23 at 22:02, dm wrote: Ok quick question, my girlfriend's system after installing a display manager (gdm, xdm, or kdm) only starts one virtual terminal. This was awhile ago when she was in testing, now she is in unstable, this has been bothering her for a while now, and I would like to fix it, what config file do I need to change. Thank you in advance, dm. Debian unlike redhat doesn't have a different runlevel for graphical login. Debian uses runlevel 2 by default and if xdm/gdm/kdm/... are installed it uses them. If you wan't to change this behaviour the place to look would be /etc/inittab The default is 6 terminals no matter if X login is enabled, so it has either been changed or something else is a problem, can you post the file? Wasn't completely clear, from the message is the only terminal the X login or is there another text terminal. Just in case, you are aware that to switch between X and a regular terminal you need Alt-Ctrl-Fterm num and between regulat terminals Alt-Fterm num. On the lines as appearing above in /etc/inittab make sure that the number 2 appears between the first and second : characters (where marked) for each terminal you want to enable. v 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 And make sure that the default runlevel is actually set to 2 as follows: id:2:initdefault: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
virtual terminals
Ok quick question, my girlfriend's system after installing a display manager (gdm, xdm, or kdm) only starts one virtual terminal. This was awhile ago when she was in testing, now she is in unstable, this has been bothering her for a while now, and I would like to fix it, what config file do I need to change. Thank you in advance, dm. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X 4.2 virtual terminals
On Mon, Nov 11, 2002 at 12:06:40PM -0500, Mark Copper wrote: my inittab has default run level = 2. It's not changed anywhere else is it? Don't think so. And would that explain why /etc/init.d/xdm stop kills the display entirely? I don't think so. Every run level is going to have at least one VT setup. I commneted agpgart out of /etc/modules and rebooted. lsmod no longer shows apgart, but behavior wrt virtual consoles remains the same. Sounds like you've just found a bug in the X server code. -rob msg12487/pgp0.pgp Description: PGP signature
Re: X 4.2 virtual terminals
This one time, at band camp, nate said: Mark Copper said: I just upgraded to testing to get X 4.2 because it supports my card. Now X starts fine but (1) I can't cltrl-alt Fx to a virtual terminal, (2) /etc/init.d/xdm stop not only kills X but it also kills any further output to the monitor, (3) nothing is printed to the screen after X has been killed during shutdown. Two things come to mind. If you've changed your runlevels to login at 4 or 5, you may have to modify inittab to allow virtual consoles in runlevels 4 and 5. Change lines of this form: 2:23:respawn:/sbin/getty 38400 tty2 To this form: 2:2345:respawn:/sbin/getty 38400 tty2 Also, if you're using the agpgart module, that could be the cause of the trouble. None of the systems I have that use Radeon 7500's can reliably use agpgart. One system allows a single return to console mode and back to X, a 2nd trip to the console will crash everything. The other systems are even less tolerant. HTH, Warren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X 4.2 virtual terminals
On Mon, 11 Nov 2002, Warren Dodge wrote: This one time, at band camp, nate said: Mark Copper said: I just upgraded to testing to get X 4.2 because it supports my card. Now X starts fine but (1) I can't cltrl-alt Fx to a virtual terminal, (2) /etc/init.d/xdm stop not only kills X but it also kills any further output to the monitor, (3) nothing is printed to the screen after X has been killed during shutdown. Two things come to mind. If you've changed your runlevels to login at 4 or 5, you may have to modify inittab to allow virtual consoles in runlevels 4 and 5. my inittab has default run level = 2. It's not changed anywhere else is it? And would that explain why /etc/init.d/xdm stop kills the display entirely? Also, if you're using the agpgart module, that could be the cause of the trouble. None of the systems I have that use Radeon 7500's can reliably use agpgart. One system allows a single return to console mode and back to X, a 2nd trip to the console will crash everything. The other systems are even less tolerant. I commneted agpgart out of /etc/modules and rebooted. lsmod no longer shows apgart, but behavior wrt virtual consoles remains the same. Curious, eh? Thanks. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X 4.2 virtual terminals
I think I've seen this question here lately but haven't been able to locate it. Sorry. I just upgraded to testing to get X 4.2 because it supports my card. Now X starts fine but (1) I can't cltrl-alt Fx to a virtual terminal, (2) /etc/init.d/xdm stop not only kills X but it also kills any further output to the monitor, (3) nothing is printed to the screen after X has been killed during shutdown. Any ideas what is causing this? Thanks. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X 4.2 virtual terminals
Mark Copper said: I think I've seen this question here lately but haven't been able to locate it. Sorry. I just upgraded to testing to get X 4.2 because it supports my card. Now X starts fine but (1) I can't cltrl-alt Fx to a virtual terminal, (2) /etc/init.d/xdm stop not only kills X but it also kills any further output to the monitor, (3) nothing is printed to the screen after X has been killed during shutdown. Any ideas what is causing this? Thanks. did it work on 4.1 ? I have mentioned on other threads I have seen this kind of behavior on and off for at least 5 years now on various systems, buggy hardware, or buggy driver. Best off not switching to virtual console from X. Safer to exit out of X then restart it when you need it. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X 4.2 virtual terminals
On Sun, 10 Nov 2002, nate wrote: Mark Copper said: I think I've seen this question here lately but haven't been able to locate it. Sorry. I just upgraded to testing to get X 4.2 because it supports my card. Now X starts fine but (1) I can't cltrl-alt Fx to a virtual terminal, (2) /etc/init.d/xdm stop not only kills X but it also kills any further output to the monitor, (3) nothing is printed to the screen after X has been killed during shutdown. Any ideas what is causing this? Thanks. did it work on 4.1 ? I have mentioned on other threads I have seen this kind of behavior on and off for at least 5 years now on various systems, buggy hardware, or buggy driver. Best off not switching to virtual console from X. Safer to exit out of X then restart it when you need it. There was no support in 4.1 for the card (Radeon 7500), so no it didn't, but that doesn't help much, I guess. I suppose the only practical implication is that I'm blind at shutdown. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
XFree 86 and Woody kills virtual terminals
Booting multiuser and switching to a from GDM to Virtual Terminal locks the machine. Booting Single User and no X I can switch between virtual text terminals w/o problems. thanks
Switching to virtual terminals hangs woody.
All, Woody is booting fine under kernel 2.4.13 ; howver, when I switch to a virtual terminal, all I get is a blank black scrren. Then everything hangs. I have compiled in pts98 terminals and also virtual terminals - no virtual frame buffers Thanks to all of you that helped with the /dev problem
virtual terminals
hey folks. i was just wondering about virtual terms -- is there an easy way to change how many there are? debian seems to default at 6 running getty, and X opens up 7. presumably i can use as many as 12? how does this work? is it as simple as running getty from init, or is there a kernel definition somewhere that specifies how many i can have, or a little of both? is there some documentation on the subject somewhere? -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpFXolmkpsQm.pgp Description: PGP signature
Re: virtual terminals
On Mon, Mar 19, 2001 at 11:27:44PM -0800, Alexander Poquet wrote: hey folks. i was just wondering about virtual terms -- is there an easy way to change how many there are? debian seems to default at 6 running getty, and X opens up 7. presumably i can use as many as 12? how does this work? is it as simple as running getty from init, or is there a kernel definition somewhere that specifies how many i can have, or a little of both? is there some documentation on the subject somewhere? -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! I think up until kernel 1.1.54 you had to recompile to change the number of virtual consoles. Now you can just add a line in /etc/inittab: 8:23:respawn:/sbin/getty 38400 tty8 This will give you another console on cntrl-alt-f8 after a reboot. Be careful using tty7 to avoid an X conflict--I don't know what would happen if getty and X both tried to use the same device. There's a huge number of tty's available (try ls /dev/tty*), but I suppose you're limited to 12, one for each of the F keys.
Re: virtual terminals
on Mon, Mar 19, 2001 at 01:07:06AM -0700, Jed Strauss ([EMAIL PROTECTED]) wrote: On Mon, Mar 19, 2001 at 11:27:44PM -0800, Alexander Poquet wrote: hey folks. i was just wondering about virtual terms -- is there an easy way to change how many there are? debian seems to default at 6 running getty, and X opens up 7. presumably i can use as many as 12? how does this work? is it as simple as running getty from init, or is there a kernel definition somewhere that specifies how many i can have, or a little of both? is there some documentation on the subject somewhere? -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! I think up until kernel 1.1.54 you had to recompile to change the number of virtual consoles. Now you can just add a line in /etc/inittab: 8:23:respawn:/sbin/getty 38400 tty8 This will give you another console on cntrl-alt-f8 after a reboot. Be careful using tty7 to avoid an X conflict X launches to the first unoccupied VT if one isn't explicitly specified. --I don't know what would happen if getty and X both tried to use the same device. Things get ugly. Fast. There's a huge number of tty's available (try ls /dev/tty*), 64 by default. You can compile in more if you need them. but I suppose you're limited to 12, one for each of the F keys. Nope. man chvt Cheers. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpNVqSGPFxn7.pgp Description: PGP signature
Re: virtual terminals
On Mon, Mar 19, 2001 at 11:27:44PM -0800, Alexander Poquet wrote: hey folks. i was just wondering about virtual terms -- is there an easy way to change how many there are? debian seems to default at 6 running getty, and X opens up 7. presumably i can use as many as 12? how does this work? is it as simple as running getty from init, or is there a kernel definition somewhere that specifies how many i can have, or a little of both? is there some documentation on the subject somewhere? Edit /etc/inittab Continue adding lines, just change the two outside numbers. # Format: # id:runlevels:action:process 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 To continue with tty9 - 9:23:respawn:/sbin/getty 38400 tty9 See man inittab hth, kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
switching virtual terminals
There's a package that I need to install that allows switching virtual terminals by hitting [Ctrl Alt 'left or right arrow']. Anyone happen to remember what the name of that package is? thanks
Re: switching virtual terminals
On Fri, Oct 27, 2000 at 09:50:03PM -0700, Dale Morris wrote: There's a package that I need to install that allows switching virtual terminals by hitting [Ctrl Alt 'left or right arrow']. Anyone happen to remember what the name of that package is? thanks uh... alt left|right arrow already changes virtual terminals on my systems... control alt does not but do you really need it to be control+alt or will just alt do? -- Ethan Benson http://www.alaska.net/~erbenson/ pgp5kcXyYu9Wa.pgp Description: PGP signature
Re: switching virtual terminals
alt left|right arrow is fine, guess I'm confused. Not unusual. Thanks.. Ethan Benson [EMAIL PROTECTED] wrote: On Fri, Oct 27, 2000 at 09:50:03PM -0700, Dale Morris wrote: There's a package that I need to install that allows switching virtual terminals by hitting [Ctrl Alt 'left or right arrow']. Anyone happen to remember what the name of that package is? thanks uh... alt left|right arrow already changes virtual terminals on my systems... control alt does not but do you really need it to be control+alt or will just alt do? -- Ethan Benson http://www.alaska.net/~erbenson/ -- The major advances in civilization are processes that all but wreck the societies in which they occur. --Albert North Whitehead
Re: switching virtual terminals
On Fri, Oct 27, 2000 at 09:50:03PM -0700, Dale Morris wrote: There's a package that I need to install that allows switching virtual terminals by hitting [Ctrl Alt 'left or right arrow']. Anyone happen to remember what the name of that package is? thanks Is it konsole that you are thinking of ? Just reconfirm this [Ctrl-Alt-Arrow keys] aspect, because I think konsole uses [Shift - Arrow Keys] for VT switching. USM Bish
Re: switching virtual terminals
thanks. I can't remember the exact key sequence, I just remember apt-getting the package on a different install. And.. I seem to have it now with [Alt-Arrow keys] USM Bish [EMAIL PROTECTED] wrote: On Fri, Oct 27, 2000 at 09:50:03PM -0700, Dale Morris wrote: There's a package that I need to install that allows switching virtual terminals by hitting [Ctrl Alt 'left or right arrow']. Anyone happen to remember what the name of that package is? thanks Is it konsole that you are thinking of ? Just reconfirm this [Ctrl-Alt-Arrow keys] aspect, because I think konsole uses [Shift - Arrow Keys] for VT switching.
Re: xserver-svga 3.3.2.3 messes virtual terminals
Jean Orloff [EMAIL PROTECTED] writes: 1) what more can I try (outside reboot) to clear the terminals? setfont -- Carey Evans http://home.clear.net.nz/pages/c.evans/ Microsoft is the answer! The question is, Why did my PC crash?
xserver-svga 3.3.2.3 messes virtual terminals
Hi! I just switched X11 server from s3v to svga (the staroffice install freezes otherwise). Now I get the rather annoying problem: whenever I start X, all the virtual terminals get scrambled. I tried the allmighty reset inside one of the terminals with no success. I also tried stty sane /dev/tty0 with no effect. The only thing that worked was switching back and forth to a preexisting X server. Questions: 1) what more can I try (outside reboot) to clear the terminals? 2) Any idea what X might do to cause such a scramble on *all* terminals? Every space has little black dot in it, there are permutations (eg e becomes %), but numbers are all OK. X is working fine, but I feel insecure to live with such garbage in the virtual terminals. Jean Orloff + + + + + + + + ++ + Tel:(33)473.40.72.27Fax: (33)473.26.45.98 + + + + + + + + + ++
Re: Virtual terminals
On: Fri, 5 Jun 1998 14:21:37 +0100 (BST) M C Vernon writes: Dear all, How can I address more than 6 vts? I have X installed, and it usually runs on altf7, but when it's running, I get Warning: dev (03:03) tty-count(1) != #fd's(2) in do_tty_hangup Appletalk 0.17 for Linux NET3.035 X will always use the next free virtual terminal. Just edit your /etc/inittab file and search for the block: 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 Now just add lines like: 7:23:respawn:/sbin/getty 38400 tty7 8:23:respawn:/sbin/getty 38400 tty8 9:23:respawn:/sbin/getty 38400 tty9 10:23:respawn:/sbin/getty 38400 tty10 11:23:respawn:/sbin/getty 38400 tty11 to create 5 additional virtual terminals. Make sure that at least one is free for starting X. I have seen the error you mentioned above but don't know the reason for it. Torsten -- Whenever a system becomes completely defined, some damn fool discovers something which either abolishes the system or expands it beyond recognition. Fortune Cookie PGP Public key available -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Virtual terminals
Dear all, How can I address more than 6 vts? I have X installed, and it usually runs on altf7, but when it's running, I get Warning: dev (03:03) tty-count(1) != #fd's(2) in do_tty_hangup Appletalk 0.17 for Linux NET3.035 On the top of the screen when I hit altf7 and on 8, Warning: dev (03:00) tty-count(1) != #fd's(2) in do_tty_hangup and 9-12 are blank. How can I get to use these? Thanks, Matthew -- Elen sila lumenn' omentielvo Steward-elect of the Cambridge Tolkien Society Selwyn College Computer Support http://www.geocities.com/Area51/Chamber/8841/ http://www.cam.ac.uk/CambUniv/Societies/tolkien/ http://pick.sel.cam.ac.uk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
switching virtual terminals from C
HEllo! Does anyone know of a way to change, in C, _which_ virtual terminal is currently on the screen? I just have no idea where to look for this. Thanks. Aaron Brick. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: switching virtual terminals from C
[EMAIL PROTECTED] (Aaron Brick) writes: HEllo! Does anyone know of a way to change, in C, _which_ virtual terminal is currently on the screen? I just have no idea where to look for this. Thanks. Aaron Brick. Well, the chvt command from the kbd package does this. Therefore, I'd suggest either using a system(chvt blah) call, or looking at the chvt source code, which you'll find in the kbd source package. p.s. Hmmm - I wonder how common Debian is here at jhu... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
X server or window manager dies when changing virtual terminals.
I have been having a problem that has now gotten really bad with the new Netscape 4.03. When I am using X and change to one of the other virtual terminals then come back to X the server shuts down and I end up back at the xdm prompt. It is almost guaranteed to happen with Netscape 4.03 and sometimes with tkmail. It is rare if there are only xterm or rxvt sessions running. Any ideas would be great. Thanks for the help. Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X server or window manager dies when changing virtual terminals.
On Mon, 13 Oct 1997, R Chris Ross wrote: I have been having a problem that has now gotten really bad with the new Netscape 4.03. When I am using X and change to one of the other virtual terminals then come back to X the server shuts down and I end up back at the xdm prompt. It is almost guaranteed to happen with Netscape 4.03 and sometimes with tkmail. It is rare if there are only xterm or rxvt sessions running. Any ideas would be great. Thanks for the help. Chris Have you looked to see what's in .xsession-errors after this problem happens? Don't log back in via xdm, as that would zero it out; switch to a text console, log in, and copy the .xsession-errors file to some other name so that it won't be overwritten next time you log on via xdm. DANIEL MARTIN -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X server or window manager dies when changing virtual terminals.
I have been having a problem that has now gotten really bad with the new Netscape 4.03. When I am using X and change to one of the other virtual terminals then come back to X the server shuts down and I end up back at the xdm prompt. It is almost guaranteed to happen with Netscape 4.03 and sometimes with tkmail. It is rare if there are only xterm or rxvt sessions running. Any ideas would be great. Thanks for the help. Chris Have you looked to see what's in .xsession-errors after this problem happens? Don't log back in via xdm, as that would zero it out; switch to a text console, log in, and copy the .xsession-errors file to some other name so that it won't be overwritten next time you log on via xdm. I've got an even wierder problem. Before I disabled acceleration (XAA), I could reliably cause my xserver to lock up the entire machine -- no external logins, control-alt-delete, etc... -- Jon Nelson U of MN Housing and Res. Life Computing Supervisor [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Virtual Terminals Greater Than tty8.
What was the command line for your mknod for each one? mknod tty9 c 4 9 mknod tty10 c 4 10 mknod tty11 c 4 11 etc. Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Virtual Terminals Greater Than tty8.
I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. Thanks Paul You can even go to tty24! To switch, hit LEFT ALT-(F1 - F12) for the first 12, RIGHT ALT-(F1-F12) for the upper 12. I have two dos sessions started automatically on tty23 and tty24 for a DOS based BBS telnet. Adam Heath [EMAIL PROTECTED] http://www.geocities.com/Siliconvalley/Park/6562/ -- This message was delayed because the list mail delivery agent was down.
Re: Virtual Terminals Greater Than tty8.
On Wed, 27 Nov 1996 18:01:15 EST Adam Heath ([EMAIL PROTECTED] g) wrote: I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. You can even go to tty24! To switch, hit LEFT ALT-(F1 - F12) for the first 12, RIGHT ALT-(F1-F12) for the upper 12. I have two dos sessions started automatically on tty23 and tty24 for a DOS based BBS telnet. I've even go further: you can go up to 64 !!! To switch, use ALT-right arrow and ALT-left-arrow. No more direct access for ttys 24. :-) Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Virtual Terminals Greater Than tty8.
On Wed, 27 Nov 1996, Adam Heath wrote: I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. You can even go to tty24! To switch, hit LEFT ALT-(F1 - F12) for the first 12, RIGHT ALT-(F1-F12) for the upper 12. I have two dos sessions started automatically on tty23 and tty24 for a DOS based BBS telnet. I've always wondered what the right alt was for. Thanks Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Virtual Terminals Greater Than tty8.
I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. Thanks Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Virtual Terminals Greater Than tty8.
On Wed, 27 Nov 1996 09:30:56 CST ugs ([EMAIL PROTECTED]) wrote: I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. No, no problem with it. Go ahead. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
