Author Topic: <SOLVED by upgrade> Virtual ttys not accessible  (Read 315 times)

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3979
<SOLVED by upgrade> Virtual ttys not accessible
« on: November 28, 2010, 04:56:47 PM »
If I use ctrl+alt +F1 etc to switch virtual terminals I can't get to a log in screen, even if I boot with a 3 added to the end of the kernel options.

ctrl+alt +F1 gives me a screen with "acpi: skipping conf file /etc/acpi/events.." as the last line.
ctrl+alt +F2 gives me a black screen with a flashing horizontal cursor in the top left corner.
ctrl+alt +F3 gives me a screen with
Code: [Select]

PCMCIA: probing for Databook TCIC-2 (ISA)
*        Not found
as the last two lines.
ctrl+alt +F4-6 give me a black screen with a flashing horizontal cursor in the top left corner.
ctrl+alt +F7 gives me a screen with boot messages ending in "Checking for new Hardware  [OK]" with a flashing horizontal cursor on the line below.

I see this on both my Acer Aspire and this machine (spec in sig). The Acer was installed from a recent remaster and is only a couple of weeks behind current.

I also had the problem on my old K2VT7 system around 27th August. That was installed from a contemporary remaster. I noticed it then because I was trying to get the serial mouse working and without a mouse switching terminals becomes a natural way to access things. However, I didn't realise until recently it wasn't just that machine.

My eeepc which is still running KDE 4.5.00 from an earlier remaster has the terminals 1-6 as normal, although number 7 still has the boot messages.

Is it just my system or are others getting the same?
« Last Edit: December 02, 2010, 10:10:13 AM by kjpetrie »
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline Bald Brick

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6372
  • I'm going South
Re: Virtual ttys not accessible
« Reply #1 on: November 28, 2010, 06:45:19 PM »
Ctrl+Alt+F1 to F6 work as they always have giving me tty1 to tty6.

Ctrl+Alt+F7 gives me a black screen with
Quote
Loading sensors modules:
Starting sensord:
Starting netprofile: The default is the current profile.
Checking for new hardware

The first three lines are followed by  a normal [  OK  ], but it seems that the checking for new hardware is never finished.

Ctrl+Alt+F8 gives me back my first graphical screen, or in other words, it does what Ctrl+Alt+F7 used to do.



Edit: The machine is an Acer Aspire M5201 desktop, with the KDE version of PCLinuxOS, fully updated and with lots of additional programmes.
« Last Edit: November 28, 2010, 06:55:20 PM by Bald Brick »
Feed the trolls!
They need it!

AMD Athlon 7450 Dual-Core Processor, 7.80 GiB RAM, Nvidia GeForce GT 120/PCIe/SSE2, OpenGL/ES-version: 3.3 0 NVIDIA 295.40, SBx00 Azalia (Intel HDA) soundcard, ‎Logitech B500 webcam, SAA7146 DVB card, HDDs: Seagate 250824AS, Western Digital WD10EAVS-00D

Offline tschommer

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 1889
  • MLU and BLU (Bacon lovin' user)
Re: Virtual ttys not accessible
« Reply #2 on: November 29, 2010, 09:17:55 AM »
I thought the same at first, but then noticed that the boot procedure had not yet finished entirely.

If I wait another 10 seconds or so, I get the usual login prompt on tty1 thru tty6.
tty7 has the "Checking for new hardware" and is locked, tty8 thru tty11 my graphical screens (when using several user logins simultaneously), and tty12 the system log (if I'm not mistaken).

Torsten
Our defense is in the preservation of the spirit which prizes liberty as the heritage of all men, in all lands, everywhere."
Abraham Lincoln --September 11, 1858 Speech at Edwardsville, Illinois

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3979
Re: Virtual ttys not accessible
« Reply #3 on: December 01, 2010, 05:37:19 PM »
Thanks. I started playing around with shutting down processes and thought I'd found a pointer, but I now realise the problem has gone away with my last upgrade. Maybe it was already solved in the repo when I posted my first question!

The seventh screen certainly looks as if something is hanging, but it's not being able to get into the terminals if the GUI went down that bothered me most.
« Last Edit: December 02, 2010, 10:13:16 AM by kjpetrie »
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf