Re: NVIDIA drivers and virtual console problem

[Ric Moore]

On 09/15/2018 10:28 AM, Thakur Mahashaya wrote:

//"Есть два великих грехов в мире...
..грех невежества, грех от глупости.//
So stupidity is the mode of ignorance.


As the Sorting Hat once said, "I know what to do with YOU!" ...and off 
you go into my junk folder. :) Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: NVIDIA drivers and virtual console problem

[Thakur Mahashaya]

//here are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.//
So stupidity is the mode of ignorance.

15.09.2018, 17:20, "Ric Moore" :
> On 09/14/2018 07:54 AM, Marco Righi wrote:
>>  Hello,
>>  the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia 
>> site) do not allow me to have "virtual consoles" (to be clear, those that 
>> are activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem 
>> disappears, with the two different versions of the NVIDIA drivers the 
>> problem appears.
>>
>>  The video card is:
>>
>>  VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev 
>> a1)
>
> Are you running the correct nvidia driver version?? A 520 is pretty long
> in the tooth and might need the legacy driver. Ric
>
> --
> My father, Victor Moore (Vic) used to say:
> "There are two Great Sins in the world...
> ..the Sin of Ignorance, and the Sin of Stupidity.
> Only the former may be overcome." R.I.P. Dad.
> http://linuxcounter.net/user/44256.html

Re: NVIDIA drivers and virtual console problem

[Thakur Mahashaya]

//"Есть два великих грехов в мире...
..грех невежества, грех от глупости.//
So stupidity is the mode of ignorance.

15.09.2018, 17:20, "Ric Moore" :
> On 09/14/2018 07:54 AM, Marco Righi wrote:
>>  Hello,
>>  the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia 
>> site) do not allow me to have "virtual consoles" (to be clear, those that 
>> are activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem 
>> disappears, with the two different versions of the NVIDIA drivers the 
>> problem appears.
>>
>>  The video card is:
>>
>>  VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev 
>> a1)
>
> Are you running the correct nvidia driver version?? A 520 is pretty long
> in the tooth and might need the legacy driver. Ric
>
> --
> My father, Victor Moore (Vic) used to say:
> "There are two Great Sins in the world...
> ..the Sin of Ignorance, and the Sin of Stupidity.
> Only the former may be overcome." R.I.P. Dad.
> http://linuxcounter.net/user/44256.html

Re: NVIDIA drivers and virtual console problem

[Ric Moore]

On 09/14/2018 07:54 AM, Marco Righi wrote:

Hello,
the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia site) do not 
allow me to have "virtual consoles" (to be clear, those that are activated with 
Ctrl-Alt-F1 .. F6). By installing Nouveau the problem disappears, with the two different 
versions of the NVIDIA drivers the problem appears.

The video card is:

VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1)


Are you running the correct nvidia driver version?? A 520 is pretty long 
in the tooth and might need the legacy driver. Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

NVIDIA drivers and virtual console problem

[Marco Righi]

Hello,
the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia site) 
do not allow me to have "virtual consoles" (to be clear, those that are 
activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem 
disappears, with the two different versions of the NVIDIA drivers the problem 
appears.

The video card is:

VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1)

With the Nouveau drivers during the Boot there is a time when the video card 
switches from text mode to graphic mode (so to speak, when the [ok] in green 
are starting to appear). With the NVIDIA dirver it crashes while remaining in 
the text mode (lightdm is executed correctly).

I reported the bug with reportbug-ng, let's see what happens.

Thanks for your help.

m

Re: qemu/kvm spice console problem

[Gary Dale]

On 2017-12-28 04:01 PM, Celejar wrote:

On Wed, 27 Dec 2017 23:14:31 -0500
Gary Dale  wrote:


When I try to start a virtual machine, I get the error:

Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing

on whichever VM I try to start.

The Virtual Machine Manager shows the VM is running but I can't connect.
The system running the VMs is Debian/Stretch while my workstation is
Debian/Buster. This worked until fairly recently (I don't start up the
VMs too often, but I'm sure I did sometime in the last month). So far as
I can tell, spice is running on both the host and client machines.

Any ideas on what's changed to cause this problem?

No, but I do remember that when I installed virt* packages, it took a
fair bit of sleuthing / trial and error to figure out which spice
packages needed to be installed to get the graphical console to work.
Here's what I currently have:

$ apt list --installed '*spice*'
Listing... Done
gir1.2-spice-client-glib-2.0/stable,now 0.33-3.3 amd64 [installed,automatic]
gir1.2-spice-client-gtk-3.0/stable,now 0.33-3.3 amd64 [installed,automatic]
libspice-client-glib-2.0-8/stable,now 0.33-3.3 amd64 [installed,automatic]
libspice-client-gtk-3.0-5/stable,now 0.33-3.3 amd64 [installed,automatic]
libspice-server1/stable,stable,now 0.12.8-2.1+deb9u1 amd64 [installed,automatic]
spice-client-glib-usb-acl-helper/stable,now 0.33-3.3 amd64 [installed,automatic]

Celejar


apt list --installed '*spice*'
Listing... Done
gir1.2-spiceclientglib-2.0/testing,now 0.34-1.1 amd64 [installed,automatic]
libspice-client-glib-2.0-8/testing,now 0.34-1.1 amd64 [installed,automatic]
libspice-client-gtk-3.0-5/testing,now 0.34-1.1 amd64 [installed,automatic]
libspice-server1/testing,now 0.14.0-1 amd64 [installed,automatic]
spice-client-glib-usb-acl-helper/testing,now 0.34-1.1 amd64 
[installed,automatic]

spice-client-gtk/testing,now 0.34-1.1 amd64 [installed]

The missing package seems to be gir1.2-spice-client-gtk-3.0. Thanks!

Re: qemu/kvm spice console problem

[Gary Dale]

On 2017-12-28 01:57 AM, john doe wrote:

On 12/28/2017 5:14 AM, Gary Dale wrote:

When I try to start a virtual machine, I get the error:

Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing

on whichever VM I try to start.

The Virtual Machine Manager shows the VM is running but I can't 
connect. The system running the VMs is Debian/Stretch while my 
workstation is Debian/Buster. This worked until fairly recently (I 
don't start up the VMs too often, but I'm sure I did sometime in the 
last month). So far as I can tell, spice is running on both the host 
and client machines.


Any ideas on what's changed to cause this problem?



Do you have the "missing" package installed?
The error seems to be common when searching online.

https://packages.debian.org/search?keywords=spice-client-gtk


Yes. I have the package installed on both the host and client machines.

Re: qemu/kvm spice console problem

[Celejar]

On Thu, 28 Dec 2017 22:23:05 +0100
Zoltán Herman  wrote:

> If started in terminal as root?

I'm not sure what you're asking, but the graphical console works here
even when I launch virt-manager as my regular user (although that user
is a member of groups libvirt, kvm, and adm).

Also, I should note that I'm running Stretch.

> 2017. dec. 28. 10:01 du. ezt írta ("Celejar" ):
> 
> > On Wed, 27 Dec 2017 23:14:31 -0500
> > Gary Dale  wrote:
> >
> > > When I try to start a virtual machine, I get the error:
> > >
> > > Error connecting to graphical console:
> > > Error opening Spice console, SpiceClientGtk missing
> > >
> > > on whichever VM I try to start.
> > >
> > > The Virtual Machine Manager shows the VM is running but I can't connect.
> > > The system running the VMs is Debian/Stretch while my workstation is
> > > Debian/Buster. This worked until fairly recently (I don't start up the
> > > VMs too often, but I'm sure I did sometime in the last month). So far as
> > > I can tell, spice is running on both the host and client machines.
> > >
> > > Any ideas on what's changed to cause this problem?
> >
> > No, but I do remember that when I installed virt* packages, it took a
> > fair bit of sleuthing / trial and error to figure out which spice
> > packages needed to be installed to get the graphical console to work.
> > Here's what I currently have:
> >
> > $ apt list --installed '*spice*'
> > Listing... Done
> > gir1.2-spice-client-glib-2.0/stable,now 0.33-3.3 amd64
> > [installed,automatic]
> > gir1.2-spice-client-gtk-3.0/stable,now 0.33-3.3 amd64
> > [installed,automatic]
> > libspice-client-glib-2.0-8/stable,now 0.33-3.3 amd64 [installed,automatic]
> > libspice-client-gtk-3.0-5/stable,now 0.33-3.3 amd64 [installed,automatic]
> > libspice-server1/stable,stable,now 0.12.8-2.1+deb9u1 amd64
> > [installed,automatic]
> > spice-client-glib-usb-acl-helper/stable,now 0.33-3.3 amd64
> > [installed,automatic]
> >
> > Celejar
> >
> >


Celejar

Re: qemu/kvm spice console problem

[Zoltán Herman]

If started in terminal as root?

2017. dec. 28. 10:01 du. ezt írta ("Celejar" ):

> On Wed, 27 Dec 2017 23:14:31 -0500
> Gary Dale  wrote:
>
> > When I try to start a virtual machine, I get the error:
> >
> > Error connecting to graphical console:
> > Error opening Spice console, SpiceClientGtk missing
> >
> > on whichever VM I try to start.
> >
> > The Virtual Machine Manager shows the VM is running but I can't connect.
> > The system running the VMs is Debian/Stretch while my workstation is
> > Debian/Buster. This worked until fairly recently (I don't start up the
> > VMs too often, but I'm sure I did sometime in the last month). So far as
> > I can tell, spice is running on both the host and client machines.
> >
> > Any ideas on what's changed to cause this problem?
>
> No, but I do remember that when I installed virt* packages, it took a
> fair bit of sleuthing / trial and error to figure out which spice
> packages needed to be installed to get the graphical console to work.
> Here's what I currently have:
>
> $ apt list --installed '*spice*'
> Listing... Done
> gir1.2-spice-client-glib-2.0/stable,now 0.33-3.3 amd64
> [installed,automatic]
> gir1.2-spice-client-gtk-3.0/stable,now 0.33-3.3 amd64
> [installed,automatic]
> libspice-client-glib-2.0-8/stable,now 0.33-3.3 amd64 [installed,automatic]
> libspice-client-gtk-3.0-5/stable,now 0.33-3.3 amd64 [installed,automatic]
> libspice-server1/stable,stable,now 0.12.8-2.1+deb9u1 amd64
> [installed,automatic]
> spice-client-glib-usb-acl-helper/stable,now 0.33-3.3 amd64
> [installed,automatic]
>
> Celejar
>
>

Re: qemu/kvm spice console problem

[Celejar]

On Wed, 27 Dec 2017 23:14:31 -0500
Gary Dale  wrote:

> When I try to start a virtual machine, I get the error:
> 
> Error connecting to graphical console:
> Error opening Spice console, SpiceClientGtk missing
> 
> on whichever VM I try to start.
> 
> The Virtual Machine Manager shows the VM is running but I can't connect. 
> The system running the VMs is Debian/Stretch while my workstation is 
> Debian/Buster. This worked until fairly recently (I don't start up the 
> VMs too often, but I'm sure I did sometime in the last month). So far as 
> I can tell, spice is running on both the host and client machines.
> 
> Any ideas on what's changed to cause this problem?

No, but I do remember that when I installed virt* packages, it took a
fair bit of sleuthing / trial and error to figure out which spice
packages needed to be installed to get the graphical console to work.
Here's what I currently have:

$ apt list --installed '*spice*'
Listing... Done
gir1.2-spice-client-glib-2.0/stable,now 0.33-3.3 amd64 [installed,automatic]
gir1.2-spice-client-gtk-3.0/stable,now 0.33-3.3 amd64 [installed,automatic]
libspice-client-glib-2.0-8/stable,now 0.33-3.3 amd64 [installed,automatic]
libspice-client-gtk-3.0-5/stable,now 0.33-3.3 amd64 [installed,automatic]
libspice-server1/stable,stable,now 0.12.8-2.1+deb9u1 amd64 [installed,automatic]
spice-client-glib-usb-acl-helper/stable,now 0.33-3.3 amd64 [installed,automatic]

Celejar

Re: qemu/kvm spice console problem

[john doe]

On 12/28/2017 5:14 AM, Gary Dale wrote:

When I try to start a virtual machine, I get the error:

Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing

on whichever VM I try to start.

The Virtual Machine Manager shows the VM is running but I can't connect. 
The system running the VMs is Debian/Stretch while my workstation is 
Debian/Buster. This worked until fairly recently (I don't start up the 
VMs too often, but I'm sure I did sometime in the last month). So far as 
I can tell, spice is running on both the host and client machines.


Any ideas on what's changed to cause this problem?



Do you have the "missing" package installed?
The error seems to be common when searching online.

https://packages.debian.org/search?keywords=spice-client-gtk

--
John Doe

qemu/kvm spice console problem

[Gary Dale]

When I try to start a virtual machine, I get the error:

Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing

on whichever VM I try to start.

The Virtual Machine Manager shows the VM is running but I can't connect. 
The system running the VMs is Debian/Stretch while my workstation is 
Debian/Buster. This worked until fairly recently (I don't start up the 
VMs too often, but I'm sure I did sometime in the last month). So far as 
I can tell, spice is running on both the host and client machines.


Any ideas on what's changed to cause this problem?

keymap console problem

[Jose Manuel Velasco]

Hi, I have the next problem trying to configure the keyboard. These
are the steps that i have made more or less.
0) Installing woody and upgrade to unstable (SID)
1) apt-get install console-data console-common locales
2) configure locales
sinsoporte:~# locale
[EMAIL PROTECTED]
LC_CTYPE=[EMAIL PROTECTED]
LC_NUMERIC=[EMAIL PROTECTED]
LC_TIME=[EMAIL PROTECTED]
LC_COLLATE=[EMAIL PROTECTED]
LC_MONETARY=[EMAIL PROTECTED]
LC_MESSAGES=[EMAIL PROTECTED]
LC_PAPER=[EMAIL PROTECTED]
LC_NAME=[EMAIL PROTECTED]
LC_ADDRESS=[EMAIL PROTECTED]
LC_TELEPHONE=[EMAIL PROTECTED]
LC_MEASUREMENT=[EMAIL PROTECTED]
LC_IDENTIFICATION=[EMAIL PROTECTED]
LC_ALL=
sinsoporte:~#
3) The keyboard is right, i can type all the keys, but ñ key doesn't
work on the text console. I have tried also to add to /etc/enviorement
[EMAIL PROTECTED]
4) I have check in another system that there is a symbolic link at
/usr/share/kbd/defaultkbd.gz (or something like that) to
/usr/share/keymaps/mykeymap_layout, but i don't have this in the
system that i'm experimenting problems. So, maybe this is the work
from any script that i don't have. If this is the case, please tell
me.
5) I've tryed to install kbd, but without knowing if this is really
necesary. In fact i took a dependency problem between kbd and
console-tools. Maybe is this the problem, but i don't know how to fix.
6) When I have installed X enviorement, I have configured the keyboard
layout to Spanish Eliminate dead keys and the ñ is typed correctly
as you can see.
7) Finally, here is the env command output of the system:
sinsoporte:~# env
HZ=100
DESKTOP_STARTUP_ID=
TERM=xterm
SHELL=/bin/bash
GTK_RC_FILES=/etc/gtk/gtkrc:/root/.gtkrc-1.2-gnome2
WINDOWID=29360177
HUSHLOGIN=FALSE
USER=root
GNOME_KEYRING_SOCKET=/tmp/keyring-vi4arh/socket
SESSION_MANAGER=local/sinsoporte:/tmp/.ICE-unix/584
XPSERVERLIST=:64
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
MAIL=/var/mail/root
PWD=/root
[EMAIL PROTECTED]
PS1=\h:\w\$
HOME=/root
SHLVL=3
GNOME_DESKTOP_SESSION_ID=Default
LOGNAME=root
DISPLAY=:0.0
COLORTERM=gnome-terminal
XAUTHORITY=/root/.Xauthority
_=/usr/bin/env
sinsoporte:~#

Any suggestion will be really apreciate. I'm thinking that maybe is an
installation bug since I'm with SID (the last time i did I think)

Thank you for your time.

Re: graphical console problem

[Luis Finotti]

Dear Ming and all,

Thanks for the reply, Ming.  I really appreciate your help.

I put video=sisfb:mode:none in the append part of lilo.conf and it did work 
(back to text mode), but now the computer try to fit more lines than it fits 
in the screen, in the sense that there are lines below what the screen is 
showing.  For instance, if I type ls -l, some of the entries (and the 
prompt) will be below the visible part of the screen...  Can that be fixed?  
(It did not happen before the update changed to graphic...)

Is there a configuration file for this graphic console?

Thanks,

Luis

On Sunday 07 November 2004 22:59, Ming wrote:
 Try to pass video=sisfb:mode:none to your kernel, just like pass
 vga=ask. This options tells kernel does not turn on the sis framebuffer.
 If this option works, you will bootup your machine in text console. At
 that point you can try to activate standard framebuffer by passing
 vga=791 to your kernel.

 Best Regards,
 Ming

Re: graphical console problem

[Kam-Ming Siu]

Dear Luis,

Try to tune the vertical lenght of your monitor manually(using
the button on the screen). The problem seems to be the refresh rate has
changed .

There is a web page shows the usage of sisfb. It may help you.

 http://www.winischhofer.at/linuxsisvga.shtml 

As I know there is not a file store the setting of  graphical console.
If you want to change the graphical console mode, you have to set it as
the modules is loading or by using kernel parameter.

Regards,
Ming

On Mon, Nov 08, 2004 at 05:34:35PM -0500, Luis Finotti wrote:
 Dear Ming and all,
 
 Thanks for the reply, Ming. ?I really appreciate your help.
 
 I put video=sisfb:mode:none in the append part of lilo.conf and it did work 
 (back to text mode), but now the computer try to fit more lines than it fits 
 in the screen, in the sense that there are lines below what the screen is 
 showing. ?For instance, if I type ls -l, some of the entries (and the 
 prompt) will be below the visible part of the screen... ?Can that be fixed? ?
 (It did not happen before the update changed to graphic...)
 
 Is there a configuration file for this graphic console?
 
 Thanks,
 
 Luis
 
 On Sunday 07 November 2004 22:59, Ming wrote:
  Try to pass video=sisfb:mode:none to your kernel, just like pass
  vga=ask. This options tells kernel does not turn on the sis framebuffer.
  If this option works, you will bootup your machine in text console. At
  that point you can try to activate standard framebuffer by passing
  vga=791 to your kernel.
 
  Best Regards,
  Ming
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

graphical console problem

[Luis Finotti]

Hi,

I am running Debian on my laptop and after an upgrade, it tries to enter
in graphical console mode.

On boot I get:

sisfb: Using MMIO qeue mode

the screen goes blank and it enters in graphic mode (with the penguin on
the screen), but it's all fuzzy.  I can't use the text consoles
(Ctrl+Alt+F1, etc.) either.  It works, but I can't see anything on the
screen.

Here is what comes after the above line in dmesg:

.
sisfb: Using MMIO queue mode
sisfb: Detected SiS301LV video bridge
sisfb: Detected LCD PDC 0x03 (for LCD=CRT2)
sisfb: Detected LCD PDC1 0x06 (for LCD=CRT1)
sisfb: Mode is 800x600x8 (60Hz)
sisfb: Initial vbflags 0x422
sisfb: Added MTRRs
Console: switching to colour frame buffer device 100x37
sisfb: Installed SISFB_GET_INFO ioctl (80046ef8)
sisfb: Installed SISFB_GET_VBRSTATUS ioctl (80046ef9)
sisfb: 2D acceleration is enabled, scrolling mode ypan (auto-max)
fb0: SiS 65x frame buffer device, Version 1.6.32
sisfb: (C) 2001-2004 Thomas Winischhofer.
tridentfb: Trident framebuffer 0.7.5 initializing
vesafb: abort, cannot reserve video memory at 0xd000
vesafb: framebuffer at 0xd000, mapped to 0xd0876000, size 600k
vesafb: mode is 640x480x8, linelength=640, pages=24
vesafb: protected mode interface info at cbb9:
vesafb: scrolling: redraw
fb1: VESA VGA frame buffer device
vga16fb: itializing
vga16fb: mapped to 0xc00a
fb2: VGA16 VGA frame buffer device
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT 
SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 8250


I tried vga=ask in lilo.conf and all the possibilitied from the list,
taking off the line vga=.. from it, but nothing works.

How can I fix it or just go back to plain text console?

Any help would be greatly appreciated!

Best to all,

Luis

P.S.: if this e-mail has been posted in duplicate, please accept my
appologies...  I sent this e-mail before but it didn't seem to work.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: graphical console problem

[Kam-Ming Siu]

Try to pass video=sisfb:mode:none to your kernel, just like pass
vga=ask. This options tells kernel does not turn on the sis framebuffer.
If this option works, you will bootup your machine in text console. At
that point you can try to activate standard framebuffer by passing
vga=791 to your kernel.

Best Regards,
Ming

On Sun, Nov 07, 2004 at 09:47:34PM -0500, Luis Finotti wrote:
 Hi,
 
 I am running Debian on my laptop and after an upgrade, it tries to enter
 in graphical console mode.
 
 On boot I get:
 
 sisfb: Using MMIO qeue mode
 
 the screen goes blank and it enters in graphic mode (with the penguin on
 the screen), but it's all fuzzy.  I can't use the text consoles
 (Ctrl+Alt+F1, etc.) either.  It works, but I can't see anything on the
 screen.
 
 Here is what comes after the above line in dmesg:
 
 .
 sisfb: Using MMIO queue mode
 sisfb: Detected SiS301LV video bridge
 sisfb: Detected LCD PDC 0x03 (for LCD=CRT2)
 sisfb: Detected LCD PDC1 0x06 (for LCD=CRT1)
 sisfb: Mode is 800x600x8 (60Hz)
 sisfb: Initial vbflags 0x422
 sisfb: Added MTRRs
 Console: switching to colour frame buffer device 100x37
 sisfb: Installed SISFB_GET_INFO ioctl (80046ef8)
 sisfb: Installed SISFB_GET_VBRSTATUS ioctl (80046ef9)
 sisfb: 2D acceleration is enabled, scrolling mode ypan (auto-max)
 fb0: SiS 65x frame buffer device, Version 1.6.32
 sisfb: (C) 2001-2004 Thomas Winischhofer.
 tridentfb: Trident framebuffer 0.7.5 initializing
 vesafb: abort, cannot reserve video memory at 0xd000
 vesafb: framebuffer at 0xd000, mapped to 0xd0876000, size 600k
 vesafb: mode is 640x480x8, linelength=640, pages=24
 vesafb: protected mode interface info at cbb9:
 vesafb: scrolling: redraw
 fb1: VESA VGA frame buffer device
 vga16fb: itializing
 vga16fb: mapped to 0xc00a
 fb2: VGA16 VGA frame buffer device
 pty: 256 Unix98 ptys configured
 Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT 
 SHARE_IRQ SERIAL_PCI enabled
 ttyS00 at 0x03f8 (irq = 4) is a 8250
 
 
 I tried vga=ask in lilo.conf and all the possibilitied from the list,
 taking off the line vga=.. from it, but nothing works.
 
 How can I fix it or just go back to plain text console?
 
 Any help would be greatly appreciated!
 
 Best to all,
 
 Luis
 
 P.S.: if this e-mail has been posted in duplicate, please accept my
 appologies...  I sent this e-mail before but it didn't seem to work.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: keyboard (console?) problem

[Johannes Resch]

[please CC me on replies]

On Sun, July 4, 2004 at 17:13, Thomas Adam wrote:
 --- Johannes Resch [EMAIL PROTECTED] wrote:

 Deferring virtual terminal setup until console accessible.
 pluto:/usr/local/bin#

 Where are you running this command from? Is it from an xterm, or a VT. If
 you switch to a VT and run it, before you do, what does the following
 produce:

 # tty
 # ls -l $(tty)

#tty
/dev/tty1
#ls -l $(tty)
crw---1 root tty4,   1 Jul  5 07:55 /dev/tty1

some more (possibly important) info: this system was installed from debian
woody-CDs (base system only), then unstable sources were entered in
sources.list and a apt-get update  apt-get upgrade and apt-get
dist-upgrade brought the system to current unstable.

--jr

Re: keyboard (console?) problem

[Johannes Resch]

[please CC me on replies] 

 --- Johannes Resch [EMAIL PROTECTED] wrote:
  i already did dpkg-reconfigure -plow console-common a couple of times,

 Although they do the same thing, you should also:

 dpkg-reconfigure console-data

unluckily, this just brings up the same error:

pluto:/usr/local/bin# dpkg-reconfigure console-data
Looking for keymap to install:
de-latin1-nodeadkeys
Deferring virtual terminal setup until console accessible.
pluto:/usr/local/bin#


--jr


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: keyboard (console?) problem

[Thomas Adam]

--- Johannes Resch [EMAIL PROTECTED] wrote: 

 Deferring virtual terminal setup until console accessible.
 pluto:/usr/local/bin#

Where are you running this command from? Is it from an xterm, or a VT. If
you switch to a VT and run it, before you do, what does the following
produce:

# tty
# ls -l $(tty)

-- Thomas Adam

=
The Linux Weekend Mechanic -- http://linuxgazette.net
TAG Editor -- http://linuxgazette.net

shrug We'll just save up your sins, Thomas, and punish 
you for all of them at once when you get better. The 
experience will probably kill you. :)

 -- Benjamin A. Okopnik (Linux Gazette Technical Editor)





___ALL-NEW Yahoo! Messenger - 
so many all-new ways to express yourself http://uk.messenger.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

keyboard (console?) problem

[Johannes Resch]

hi,

i want to setup a german keymap (using the nodeadkeys-variant) on a
daily updated debian unstable system (debian kernel 2.6.6-2-686).

when trying to install the keymap, this error message is displayed:

pluto:/# install-keymap
/usr/share/keymaps/i386/qwertz/mac-usb-de-latin1-nodeadkeys.kmap.gz
Deferring virtual terminal setup until console accessible.

i already did dpkg-reconfigure -plow console-common a couple of times,
but the same error appears there.
i also re-installed console-common and console-data.

while searching for this error, i came across
http://lists.debian.org/debian-user/2004/03/msg13096.html, which seems
related. unluckily, there are no answers.

any ideas what could cause this problem?

best regards,
johannes resch

Re: keyboard (console?) problem

[Thomas Adam]

--- Johannes Resch [EMAIL PROTECTED] wrote: 
 i already did dpkg-reconfigure -plow console-common a couple of times,

Although they do the same thing, you should also:

dpkg-reconfigure console-data

-- Thomas Adam

=
The Linux Weekend Mechanic -- http://linuxgazette.net
TAG Editor -- http://linuxgazette.net

shrug We'll just save up your sins, Thomas, and punish 
you for all of them at once when you get better. The 
experience will probably kill you. :)

 -- Benjamin A. Okopnik (Linux Gazette Technical Editor)





___ALL-NEW Yahoo! Messenger - 
so many all-new ways to express yourself http://uk.messenger.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Console problem after upgrade to Woody

[Jaroslaw Berezowski]

Hi everybody.

I have upgraded my Potato box to Woody. Seems that almost all is OK except console 
behaviour: I have lost support for console iso02 mapping from fonty package.
I've tried to completely reload and reinstall libc6, libreadline4, with no results. 
Fonts are 
displayed properly, but I can't input any polish character from keyboard.
On the other box, system installed from scratch with those settings copied from my box 
works fine.

Starting X with XKB set to 'pl' produces message:
parse error: line 1 of stdin
Errors encountered in stdin; not compiled
Couldn't load XKB map, falling back to pre-XKB map
and of course I have no polish kbd

Seems that upgrade has messed up input layer. Any suggestion?
--
Jaroslaw Jaros Berezowski 





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

bizarre console problem

[settimio di cori]

I'm running debian unstable, kernel 2.4.2, latest kde packages.

From the moment the kdm logon screen appears and at any point thereafter
(i.e. when kde is running), if I switch to a text console (alt-ctrl-F1
etc.) the screen is filled with vertical black and white stripes and I
cannot see any text characters. Commands appear to work - if I type
shutdown -h 0 it actually works, even though I cannot see any of the
characters I am typing.

While the system is booting everything looks fine - the problem seems to
begin only after the kde logon screen appears.

Any ideas??? Have I accidentally deleted an essential package or
corrupted an essential file???

Thank you,

Mino

Re: bizarre console problem

[Michael Heldebrant]

What version of X are you running?  For a brief stretch of time on
4.1.0-1 I had console corruption coming out of X.  It seems to have gone
away in 4.1.0-2.

--mike
On 10 Aug 2001 09:12:33 -0400, settimio di cori wrote:
 I'm running debian unstable, kernel 2.4.2, latest kde packages.
 
 From the moment the kdm logon screen appears and at any point thereafter
 (i.e. when kde is running), if I switch to a text console (alt-ctrl-F1
 etc.) the screen is filled with vertical black and white stripes and I
 cannot see any text characters. Commands appear to work - if I type
 shutdown -h 0 it actually works, even though I cannot see any of the
 characters I am typing.
 
 While the system is booting everything looks fine - the problem seems to
 begin only after the kde logon screen appears.
 
 Any ideas??? Have I accidentally deleted an essential package or
 corrupted an essential file???
 
 Thank you,
 
 Mino
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 

Strange console problem when X is running

[Hall Stevenson]

I already posted this in a different message, so if you've already read
it, I apologize. I have determined a little more though... Here's the
original message:



I've recompiled the kernel again. Why ?? ;-) The console has started
getting flakey... no characters +show up when I type. Or the characters
that do show up are missing pixels in the horizontal plane +(hard to
describe) and they're also about 1/4 the size of my monitor !! I did
enable framebuffer for +my Matrox card, but this has worked fine with
2.2.17 and .18. This time though, I enabled some +additional fonts. Have
to assume that's the problem, so I've removed them and will try again.
Is this +a known problem ... anyone ??



I do know how to fix it, but it's less than ideal ;-) How ?? Exit X.
When I have the xdm login screen open, the console behaves properly.
Any ideas ??

Here's some versions of what I'm running:

Package: xfree86-common
Version: 4.0.2-1

GNU bash, version 2.04.0(1)-release (i386-pc-linux-gnu)

Package: console-tools
Version: 1:0.2.3-14

Kernel: 2.4.0 (upgrading to this is when the problem started...)

Any other relevant packages ?? They're all from debs, via apt-get,
except the kernel.

Thanks in advance
Hall Stevenson

umlauts-in-terminal/console-problem after upgrading to woody

[Michael Mertins]

Hi,
I have a large problem getting umlauts to work since I upgraded to woody.
I made the XFree4.0-Server run although I use a voodoo3-2000. Caused me
some problems etc. but it works now. Aswell I got that new locales-package. I
edited /etc/locale.gen and generated de_DE aswell I edited
/etc/X11/XF86Config-4 and changed us to de and 104 keys to 102. Now I have a 
german keymap.
But still _no_ Umlauts like (äöü) under any terminal or console. Neither
without nor under X.
I already asked around in debian-chat but the only thing they could tell
me was: export LC_ALL=de_DE and then restart bash. Which really made Umlauts
work under a single console/terminal, but not systemwide!
How can I apply this systemwide now?
Greetings,
Michael

-- 
Sent through GMX FreeMail - http://www.gmx.net

Re: umlauts-in-terminal/console-problem after upgrading to woody

[Peter Palfrader]

Hi Michael!

Michael Mertins schrieb am Donnerstag, dem 30. November 2000:

 I have a large problem getting umlauts to work since I upgraded to woody.

If you are who I think you are, then we solved this problem by
setting the LC* variables in /etc/environment, right?

also see man locale (not esp you Michael but everyone else
interested in the subject)

So long,
Weasel

-- 
PGP signed and encrypted messages preferred.
http://www.palfrader.org/


pgpI5K0ALGQfc.pgp
Description: PGP signature

Console Problem

[Jack Morgan]

I'm having with my console nd running aplications (e.g. mutt,lynx) I'm using a 
laptop with 800x600 resolution, but i'm getting 640x480. How can I increase the 
resolution. Running potato.

TIA
Jack Morgan
[EMAIL PROTECTED]

Re: Console Problem

[Moritz Schulte]

On Thu, Aug 03, 2000 at 04:37:17PM +0900, Jack Morgan wrote:

 I'm having with my console nd running aplications (e.g. mutt,lynx)
 I'm using a laptop with 800x600 resolution, but i'm getting
 640x480. How can I increase the resolution. Running potato.

with framebuffer?

 moritz
-- 
/* Moritz Schulte [EMAIL PROTECTED]
 * http://hp9001.fh-bielefeld.de/~moritz/
 * PGP-Key available, encrypted Mail is welcome.
 */