Re: Everything seems to cause a reboot

[goossens@rsc.anu.edu.au]

 On 12/19/2011 6:01 PM, goossens@rsc.anu.edu.au wrote:
>
>> I have a i7 quad core 2600K, running current squeeze 6.0.3 with default
>> Gnome installation.
...
>> I have an IBM Model M 101 keyboard.
>
> The quick fix is to simply swap your high quality clack-itty dinosaur KB
> with its inbuilt 8042 chip for any new off the shelf modern KB of your
> choice from $5 to $50.  However, your current selection of the Model M
> for modern use demonstrates a psychological profile that prevents you
> from taking the easy route.  (Or, did you tell a half truth?  Is this KB
> actually a newer Unicomp knockoff?  If so the problem is probably not
> the KB)
>
> So, you can monkey with the BIOS A20 setting, try a PS/2-USB converter,
> hack up a20.c, etc, to see if any of these things work for you.  If not,
> take option #1 and simply move on with life.  Hang the Model M on a wall
> or something as a trophy.

And it's also possible you have a video card/driver problem.  Post
make/model of video chip (GPU) and driver you are using.


THanks for that.  I really appreciate your response.

It is a real M.  I have two, with ps2 plugs, and I do a LOT of typing and
I really would like to not  have to swap for something else.  I have tried
a LOT of keyboards, since producing text is a major part of my job and
hobbies, and I really don't want to change.  Sorry if that sounds
ungrateful.... Also, I have the problem even when I logout using the mouse
to select the logout/shutdown from the gui (ie, make no use of keyboard at
all); maybe I have two separate issues?

I don't need a ps2 2 usb adapter (the machine has one), but I can try one.
 As for graphics info:

As far as I can tell in my ignorance, it has an intel H67 chipset with
integrated graphics --  I do not have a separate graphics card.  I suspect
that tallies with my psych profile too.   Driver... umm... you do not
quite realise the degree of ignorance here...  I append the output of some
grepping around

I have not idea what a BIOS A20 setting is, or a20.c, so I'll google away...

OK

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Sandy Bridge
Integrated Graphics Controller (rev 09)

OK

$ glxinfo | grep -i vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
OpenGL vendor string: Mesa Project

$ cat /etc/X11/xorg.conf
cat: /etc/X11/xorg.conf: No such file or directory

(I think this must be automagically built on demand)

$  cat /var/log/Xorg.0.log  | grep -i VGA
(II) VESA(0): VESA VBE OEM: Intel(R)Sandybridge Desktop Graphics Chipset
Accelerated VGA BIOS
(II) VESA(0): VESA VBE OEM: Intel(R)Sandybridge Desktop Graphics Chipset
Accelerated VGA BIOS

$ cat /var/log/Xorg.0.log | grep -i vid
(II) The server relies on udev to provide the list of input devices.
	X.Org Video Driver: 6.0
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
	ABI class: X.Org Video Driver, version 6.0
	ABI class: X.Org Video Driver, version 6.0
	ABI class: X.Org Video Driver, version 6.0
	ABI class: X.Org Video Driver, version 6.0
(II) VESA(0): #0: hsize: 640  vsize 480  refresh: 85  vid: 22833
(II) VESA(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
(II) VESA(0): #2: hsize: 1024  vsize 768  refresh: 85  vid: 22881
(II) VESA(0): #3: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
(II) VESA(0): #4: hsize: 640  vsize 480  refresh: 100  vid: 26673
(II) VESA(0): #5: hsize: 800  vsize 600  refresh: 100  vid: 26693
(II) VESA(0): #6: hsize: 1280  vsize 960  refresh: 60  vid: 16513
(II) VESA(0): #7: hsize: 1152  vsize 864  refresh: 75  vid: 20337
(II) GLX: Initialized DRISWRAST GL provider for screen 0