When I try to boot my Ultra10 with a 2.6.9 kernel everything is fine
until the end. When X is starting it fails, because there's no core
pointer. But not just core pointer is missing, I cannot use my
keyboard (SUN Type 6). Even Stop-A is not working.
With a 2.4.27 (deb-package) everything
In article [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
When I try to boot my Ultra10 with a 2.6.9 kernel everything is fine
until the end. When X is starting it fails, because there's no core
pointer. But not just core pointer is missing, I cannot use my
keyboard (SUN Type 6). Even Stop
On Thu, Nov 04, 2004 at 10:19:48AM +1300, Kim Shepherd wrote:
When I try to boot my Ultra10 with a 2.6.9 kernel everything is fine
until the end. When X is starting it fails, because there's no core
pointer. But not just core pointer is missing, I cannot use my
keyboard (SUN Type 6). Even
Ok you need to run dpkg-reconfigure console-data and select the option
to use the kernel's keymap, or your keyboard won't work right in 2.6.
The reason is, 2.6 converts scancodes to be PC, and 2.4 uses the raw
SPARC scancodes. Therefore if you use the kernel's own keymap, it will
work OK
- Original Message -
From: [EMAIL PROTECTED]
To: Kim Shepherd [EMAIL PROTECTED]; debian-sparc@lists.debian.org
Sent: Thursday, November 04, 2004 2:38 PM
Subject: Re: Ultra10, keyboard with 2.6.9
That driver is b0rk3d on my box and barfs when I run it. I am monkeying
about with ALSA
keymap usable?
Only when the keyboard being used behaves like an AT keyboard. (In
general: no, but more often so on sparc64.)
Thinking about it, the best idea is probably to _ignore_ boottime.kmap.gz
if 2.6 is detected at boot time, instead of removing it the first time we
see it. That way, once
Hi,
I'm looking at bug #269405, which apparently is due to 2.6 kernels now
using non-Sparc keyboards.
A proposed solution is for console-data to remove old boottime.kmap.gz
files (which contain the sun keymap) when it detects 2.6 kernels on
sparc. However I am wondering how this affects 2.4
Hi,
I'm looking at bug #269405, which apparently is due to 2.6 kernels now
using non-Sparc keyboards.
A proposed solution is for console-data to remove old boottime.kmap.gz
files (which contain the sun keymap) when it detects 2.6 kernels on
sparc. However I am wondering how this affects 2.4
Hi,
OpenBoot(2.22.2 on a SS20) will fall back to ttya if no keyboard is plugged
in. That's pretty bad for linux since it does not find console in this case
and getty complains about respawning to fast.
How can I solve this problem?
I want it to work in both cases or tell OpenBoot to not fall
cp arch/sparc64/defconfig .config
make oldconfig
i build some working kernels before ;-) ...
there is something about the obsolete devfs in 2.6 and i googled a bit and
find a working solution (for me):
/etc/fstab:
devpts /dev/ptsdevpts defaults0 0
Thorsten
Hi,
last night i successfully compiled 2.6.6 (i mean it boots :-) )
but after booting i had no keyboard!
only a few key resulted in escape characters...
i tried to ssh but got the following error Server refused to allocate pty
stdin: is not a tty
any ideas?
cheers
Thorsten
On Wed, Jul 14, 2004 at 02:11:48PM +0200, Thorsten Richter wrote:
Hi,
last night i successfully compiled 2.6.6 (i mean it boots :-) )
but after booting i had no keyboard!
only a few key resulted in escape characters...
i tried to ssh but got the following error Server refused to allocate
thanks for the fast answer!
For the keyboard problem, make sure console tools isn't doing a keymap for
i don't think about it!
a quick mv /etc/console /etc/console.old works fine!
As for the pty, be sure to compile in the Unix98 pty's into the kernel.
i leave the settings in the kernel config
On Wed, Jul 14, 2004 at 02:31:58PM +0200, Thorsten Richter wrote:
thanks for the fast answer!
For the keyboard problem, make sure console tools isn't doing a keymap for
i don't think about it!
a quick mv /etc/console /etc/console.old works fine!
As for the pty, be sure to compile
On Tue, 25 May 2004, Jiann-Ming Su wrote:
I'm not sure if this is related, but I just installed Debian Woody on my
Ultra1. I've since did a apt-get dist-upgrade and everything seems to
work, except for the keyboard in X. The Sun keyboard works fine on the
console, but as soon as I
On Mon, May 24, 2004 at 08:40:54AM +0200, Joerg Friedrich wrote:
some weeks ago I reported a problem with my keyboard (and mouse) not
working with
kernel = 2.6.5 on my Ultra60.
After searching a lot and even more kernel building I know now that is
absolutly neccessary to set
On Mon, 24 May 2004, Joerg Friedrich wrote:
Hi,
some weeks ago I reported a problem with my keyboard (and mouse) not working
with
kernel = 2.6.5 on my Ultra60.
After searching a lot and even more kernel building I know now that is
absolutly neccessary to set
CONFIG_SERIAL_SUNSU=y
Hi,
some weeks ago I reported a problem with my keyboard (and mouse) not working
with
kernel = 2.6.5 on my Ultra60.
After searching a lot and even more kernel building I know now that is
absolutly neccessary to set
CONFIG_SERIAL_SUNSU=y
The sun keyboard connection a serial one and the the su
Hi,
I have an Ultra5 with a Type 6 keyboard and mouse (miniDIN-8 connectors)
and while they work perfectly on the installer kernel 2.4.26-sparc64,
they're dead on Linux 2.6.
I turned on the 'Sun Type 4 and Type 5 keyboard support', but figured
that Type 6 might be different...
Also, I build
Was this issue ever resolved? I am having the exact same problem except that
when I ssh in to kill X, it does not give me any tty's back and the keyboard
is still completely unresponsive (I have to reboot). The lights for Caps
Lock, Num Lock, etc are even out and unresponsive. I can't figure
On Tue, 2004-04-27 at 11:01, Joerg Friedrich wrote:
Hi,
yesterday I managed to build 2.6.5 for my Ultra60.
Problem was the default of NR_CPU=64 when enabling SMP. see my previous
post.
But now I have no keyboard. It is simply not recognized. I think I did
something wrong in kernel-config
On Sun, 2004-05-02 at 19:46, FStruck wrote:
On Tue, 2004-04-27 at 11:01, Joerg Friedrich wrote:
Hi,
yesterday I managed to build 2.6.5 for my Ultra60.
Problem was the default of NR_CPU=64 when enabling SMP. see my previous
post.
But now I have no keyboard. It is simply not recognized
Hi,
yesterday I managed to build 2.6.5 for my Ultra60.
Problem was the default of NR_CPU=64 when enabling SMP. see my previous
post.
But now I have no keyboard. It is simply not recognized. I think I did
something wrong in kernel-config, but I don't find the problem.
config attached.
--
Jörg
Jim wrote:
Have you set the keymap to NONE? Remove any keymap files in /etc/console
or use dpkg-reconfigure console-tools .
I have now tried removing the keymap, and I have run dpkg-reconfigure
console-tools via ssh but it doesn't help, still no keyboard.
Any other ideas?
Thanks
rich
Ben Collins wrote
I think for Ultra10, you need to enable the AT keyboard aswell.
# CONFIG_KEYBOARD_ATKBD is not set
I have tried with this too and have the same problem. I have started to look
to see if the serial 8250 is the cause of the problem, but when I try to
complie in that module
On Tue, Apr 06, 2004 at 09:36:29AM +0100, Richard Marshall wrote:
Ben Collins wrote
I think for Ultra10, you need to enable the AT keyboard aswell.
# CONFIG_KEYBOARD_ATKBD is not set
I have tried with this too and have the same problem. I have started to look
to see if the serial
Ben Collins wrote
Do you see a kernel message about it detecting the kbd?
I haven't seen any kernel message about kbd (in dmesg), but I also don't see
one when I boot the 2.4.19 kernel where the keyboard does work. If dmesg
isn't the place to look, where is correct? I'll try your other
Ben Collins wrote
Find where -Werror is set in arch/sparc64/Makefile and delete it. That
should get the compile going again.
Hello Ben,
No sign of -Werror in arch/sparc64/Makefile or in the 'mother' Makefile
either. What should I do?
Thanks
Rich
This e-mail is confidential and may be
Richard Marshall [EMAIL PROTECTED] writes:
Ben Collins wrote
I think for Ultra10, you need to enable the AT keyboard aswell.
# CONFIG_KEYBOARD_ATKBD is not set
I have tried with this too and have the same problem. I have started to look
to see if the serial 8250 is the cause
On Wednesday 07 April 2004 01:28, James Morrison wrote:
This e-mail is confidential and may be privileged. It may be read, copied
and used only by the intended recipient. If you have received it in
(blah blah)
You are sending to a public list. This email is not confidential.
A small note
Hello
I have been playing with compiling a 2.6.4 kernel for my Ultra 10. Ihave
(finally) managed to get everything working as I'd like (well allmost).
However, I have managed to disable my type-5 keyboard somehow.
When booting to the new kernel, the machine stops at the SILO prompt and I
type
On Mon, Apr 05, 2004 at 03:50:09PM +0100, Richard Marshall wrote:
Hello
I have been playing with compiling a 2.6.4 kernel for my Ultra 10. Ihave
(finally) managed to get everything working as I'd like (well allmost).
However, I have managed to disable my type-5 keyboard somehow.
When
Op ma 08-03-2004, om 01:58 schreef Eric Brower:
Janos Sziliczi wrote:
This tends to hit the list once every few weeks.
In both sparc and sparc64 the kernel will not power-off systems that are
running with a serial console-- instead they are dropped to OBP (2.2.x
did not act this way). I
Hi All,
I've compiled a 2.4.25 kernel.
When I'd typed the 'halt' command as root, the Linux shutdowned and the
machine turned off automatically (no 'power-off' needed on PROM prompt).
I plugged out the monitor and the keyboard.
Just the UTP patch cables and the power coord are remained connected
On Monday 08 March 2004 12:58 am, Eric Brower wrote:
Janos Sziliczi wrote:
Hi All,
I've compiled a 2.4.25 kernel.
When I'd typed the 'halt' command as root, the Linux shutdowned and the
machine turned off automatically (no 'power-off' needed on PROM prompt).
This tends to hit the list
But be warned that if you tell an E150 to power-off you will have great
weeping and wailing and gnashing of teeth getting it to restart.
Rather drop to OBP and pull the power.
Seems to make much more sense to let it drop to the OBP and then type
power-off if that's really what's needed.
---
On Wed, 2003-10-01 at 09:42, Thurmond, Phillip wrote:
I have a newly installed debian (unstable) system. So far, I can’t
get X to work. The mouse and display work fine, however the keyboard
is completely unresponsive. The machine doesn’t even respond to
ctrl-alt-del, stop-a, or ctrl-alt
I have an Ultra30. I used it to write in Brazilian Portuguese. Also I'm
using testing distro.
Whit the last locales version (2.3.2-7) I can't get accent characteres
(using compose key) if set pt_BR-ISO-8859-1 through dpkg-reconfigure
locales, but it works if I choose C (Posix) enviroment.
I have a newly installed debian (unstable) system. So
far, I cant get X to work. The mouse and display work fine,
however the keyboard is completely unresponsive. The machine doesnt
even respond to ctrl-alt-del, stop-a, or ctrl-alt-bspc. If I ssh in and
kill the X server, Im dropped
final note re last attempt to get 2.4.23-pre5
working on dual hypersparc ss20 with smp
enabled
I'm going to turn off the ss20 for now and
continue to monitor these lists. I'll
try another kernel farther down the line.
Otherwise, if someone knows the ins and outs
of the kernel size limitation
Hi everybody,
is there a proper configuration for sun's type6 keyboards in X?
I've only seen type4 and type5.
Micha.
--
-- Michael Daum
-- Natural Language Systems (NatS)
-- University of Hamburg, Department for Informatics
-- http://nats-www.informatik.uni-hamburg.de/~micha
is there a proper configuration for sun's type6 keyboards in X?
I've only seen type4 and type5.
I've configured mine as type 5 and if works just fine. If anyone can
tell me how to bind the function keys on the left of the keyboard (IE
undo, again, cut, copy, paste, et al.) in X or in emacs I'd
Robert Zakaria [EMAIL PROTECTED] writes:
I have a Swedish keyboard so I choosed fi for keyboard
language during installation
If Finnish is available but not Swedish, you might report a bug. It
looks as though `se' should work instead of `fi', at least in Woody.
any idea where to check
I use the cs4231 module on a ss4, kernel 2.2.20.
Daniel van Eeden [EMAIL PROTECTED]
Ben Collins wrote:
changed to the following
Option XkbRules xfree86
and I got a very strange keyboard where c became caps
lock. I had to reboot the machine with debian cd in
to change /etc/X11
thanx for helping in advance
Sun Ultra 10 hardware
q1
in console mode the pipe works but in X, pipe is not
working.
I have a Swedish keyboard so I choosed fi for keyboard
language during installation
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
thanx for helping in advance
q1
in console mode the pipe works but in X pipe is not
working.
I have a Swedish keyboard so I choosed fi for keyboard
language during installation
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option
On Sat, May 03, 2003 at 01:42:40AM +0200, Robert Zakaria wrote:
thanx for helping in advance
q1
in console mode the pipe works but in X pipe is not
working.
I have a Swedish keyboard so I choosed fi for keyboard
language during installation
Section InputDevice
Identifier
have a Swedish keyboard so I choosed fi for
keyboard
language during installation
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option CoreKeyboard
Option XkbRules sun
Option
changed to the following
Option XkbRules xfree86
and I got a very strange keyboard where c became caps
lock. I had to reboot the machine with debian cd in
to change /etc/X11/XF86Config-4 because ctrl+alt+f1
didn't work.
Oops. Next time you can simply do boot single
Andreas Rother [EMAIL PROTECTED] writes:
since I switched from SuSE to Debian on my Ultra10, I can't get my keyboard
fully functional with XFree. My keyboard is a german type6, but I configured
it as a type5, as someone said the differences are almost
non-existant.
Right. I use Type 6
I currently have available a Sun E3500 that is running Debian 3.0r1 and I
have a couple of questions.
1. A custom kernel was rebuilt adding a couple drivers and removing some
others. This kernel now will boot and run fine, except the keyboard is
unresponsive. I've checked
located at the left hand side of
the keyboard, like
(COPY, PASTE, FRONT, OPEN etc etc) on the type 6 sun keyboard to work
on my SUN ULTRA sparc 10
I'm using suse distribution 7.3 for sparc architectures
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
Yo,
I have 2 probs:
1) My keyboard: under the console everything works OK (except for the delete
key which still behaves as a backspace). Under X it does not, I configured it
as a Sun Type 5 and when I press enter I get a backspace, meta is enter and
more weird combinations :)
2) I'm trying
On Wednesday 12 March 2003 16:36, you wrote:
1) Please post the keyboard section from your X config.
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option CoreKeyboard
Option XkbRules sun
Option XkbLayout us
EndSection
Frank Van Damme wrote:
1) Please post the keyboard section from your X config.
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option CoreKeyboard
Option XkbRules sun
Option XkbLayout us
EndSection
Try this line
xev indeed.
Frank Van Damme wrote:
On Wednesday 12 March 2003 21:07, Daniel van Eeden wrote:
Frank Van Damme wrote:
1) Please post the keyboard section from your X config.
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option CoreKeyboard
logged out and X got restarted on me.
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option CoreKeyboard
Option XkbRules sun
Option XkbModel type5
Option XkbLayout us
InputDevice section of XF86Config-4 was working fine
until I logged out and X got restarted on me.
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
Option CoreKeyboard
Option XkbRules sun
Option
Hi.
I have a Sparcstation 5 clone with a Sun 4 keyboard, and during Debian
installation (I do not think this is the reason) I run into a problem. The
machine behaved as if the Return key was permanently pressed. I switched off
and removed the keycaps, but could not find any mechanical problem
Could anyone with an interest in UK type 4/5/6 keyboards please take a
look at Bug#162469 for problems and improvements. I don't have a UK
type 4 to hand to check, so would be interested to know whether they
need anything different.
a
real terminal and keyboard but I do not get to the login prompt.
Instead, when I push the 'Stop' button, I get a message like this:
SysRq : HELP : loglevel0-8 reBoot tErm kIII saK showMem showPc unRaw
showTasks Unmount
but I get inte the server remotely...
Now, I guess
have just installed a TGX video card and hooked up a
real terminal and keyboard but I do not get to the login prompt.
Instead, when I push the 'Stop' button, I get a message like this:
SysRq : HELP : loglevel0-8 reBoot tErm kIII saK showMem showPc unRaw
showTasks Unmount
.
I had a SS20 (sun4m) system running debian 3.0 on a serial
terminal... Now I have just installed a TGX video card and hooked up a
real terminal and keyboard but I do not get to the login prompt.
[snip]
# Format:
# id:runlevels:action:process
#1:2345:respawn:/sbin/getty
:20AM +0200, Christian J?nsson wrote:
I have a little problem here.
I had a SS20 (sun4m) system running debian 3.0 on a serial
terminal... Now I have just installed a TGX video card and hooked up a
real terminal and keyboard but I do not get to the login prompt.
[snip
On Sun, Sep 15, 2002 at 11:25:20AM +0200, Christian J?nsson wrote:
I have a little problem here.
I had a SS20 (sun4m) system running debian 3.0 on a serial
terminal... Now I have just installed a TGX video card and hooked up a
real terminal and keyboard but I do not get to the login prompt
and keyboard but I do not get to the login prompt.
Instead, when I push the 'Stop' button, I get a message like this:
SysRq : HELP : loglevel0-8 reBoot tErm kIII saK showMem showPc unRaw
showTasks Unmount
but I get inte the server remotely...
Now, I guess there's some
I have a little problem here.
I had a SS20 (sun4m) system running debian 3.0 on a serial
terminal... Now I have just installed a TGX video card and hooked up a
real terminal and keyboard but I do not get to the login prompt.
Instead, when I push the 'Stop' button, I get a message like
terminal and keyboard but I do not get to the login prompt.
check the values of input-device and output-device in the PROM. if they're
ttya, set them to keyboard/screen.
thanks for your suggestion, they're set to keyboard/screen
accordingly, and I do see the machine boot off, all the way ut
Identifier XFree86 Configured
Screen 0 Screen0 0 0
InputDeviceMouse0 CorePointer
InputDevicekeyboard CoreKeyboard
EndSection
Section Files
FontPathunix/:7100# local font server
# if the local font server has
My mesage is below, someboday help please!
- Original Message -
From: tclwrap [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Uwe A. P. Wuerdinger
[EMAIL PROTECTED]
Sent: Sunday, August 18, 2002 11:52 PM
Subject: Re: What choice for Type 6 keyboard
Hi:
Newbye, I have a Blade 100 also
tclwrap wrote:
Hi:
Newbye, I have a Blade 100 also and could not
get a cd that installs debian correctly. I have the following cd's that
failed (all SPARC versions and seem to contain
vmlinux64 or something similar):
Debian 2.2r2
RedHat 6.2
Mandrake 7.0
Suse 7.0
Most
tclwrap wrote:
My mesage is below, someboday help please!
- Original Message -
From: tclwrap [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Uwe A. P. Wuerdinger
[EMAIL PROTECTED]
Sent: Sunday, August 18, 2002 11:52 PM
Subject: Re: What choice for Type 6 keyboard
Hi:
Newbye, I have
- WAS: What choice for Type 6
keyboard
tclwrap wrote:
My mesage is below, someboday help please!
- Original Message -
From: tclwrap [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Uwe A. P. Wuerdinger
[EMAIL PROTECTED]
Sent: Sunday, August 18, 2002 11:52 PM
Subject: Re: What choice
I'm installing Debian on a SunBlade 100; never done it before. Early on
in the process when it asks me to select the keyboard I took the default
(first one listed) which was a sun/sunkeymap US Type 4/5, and that was
the *wrong* thing to do. I had to hit the power button to regain
control.
Next
Hi, I made a mistake configuring the keyboard of an Ultra, type
sunkeyboard. I used to use 'kbdconfig' to reconfigure it, but it's not
present in woody, I installed console and console-utils but kbdconfig
doesn't appear, I also tried the package kbd to see if kbdconfig would
be installed
On Fri, Jul 26, 2002 at 08:30:37PM -0500, Igor T?mara wrote:
Hi, I made a mistake configuring the keyboard of an Ultra, type
sunkeyboard. I used to use 'kbdconfig' to reconfigure it, but it's not
present in woody, I installed console and console-utils but kbdconfig
doesn't appear, I also
Antonio Luiz Pacifico [EMAIL PROTECTED] writes:
My keyboard is type 5c.
Probably its exact layout is important. There is no basic map for a
Brazilian keyboard in /usr/share/keymaps/sun -- I guess the closest is
Spanish.
`dpkg-reconfigure console-common' allows you to change it. See also
I run Debian GNU/Linux on a Sparc Ultra 30. My keyboard is type 5c. My
problem is: I`d like to write in Portuguese (Brazilian), but all the
documents I read, e.g., keyboard HOWTO's, etc.., teach how to configure
it on i386. I also noticed that some files and directories commoun in
i386 I haven`t
Branden Robinson writes:
Have you guys tried using type5_euro for your XkbModel?
Let me know if it works,
It doesn't for me per se. This is with a UK keyboard, about which
I've asked previously. What's the incantation supposed to be to
specify a UK layout?
I resorted to xmodmap to get
On Sun, Dec 16, 2001 at 07:57:28AM +0100, Christian Jönsson wrote:
I would just like to say that I have the same problem, only I'm on a
Swedish keyboard which ought to be the same as Finnish. I'd consider
this a bug, valid for the debian bug reporting system, that I just
yesterday started
I have got Finnish Sun type 5c keyboard and current XFree 4.1 in Woody
works otherwise fine but one key needs fixing. Every time I restart X
server, I have to execute this to get the key between left shift and
Z to behave as expected:
xmodmap -e keycode 131 = less greater bar
In /etc/X11
I just got a RDI BriteLite IPX as surplus from work, and I've been
attempting to get Debian going on it, but I keep running into problems
with the keyboard with the install kernel. I can boot it from
rescue.bin or linux-a.out from the sun4cdm/ directory, and while it
detects the keyboard as a Sun4
Okay, here's one for you. When I boot one of my Ultra-5s without
a keyboard plugged in, the OpenPROM switches to a serial console.
Connecting a keyboard after this point has no effect; no input
will be accepted from it or sent to the screen. This isn't good
for me. I have them on a rack connected
On Sat, 2001-10-27 at 16:02, paul cannon wrote:
Okay, here's one for you. When I boot one of my Ultra-5s without
a keyboard plugged in, the OpenPROM switches to a serial console.
Connecting a keyboard after this point has no effect; no input
will be accepted from it or sent to the screen
On Sun, Sep 23, 2001 at 04:20:29PM -0600, Alvaro F. Figueroa Cabezas wrote:
Is it possible to simutaniously have serial console and
keyboard/monitor?
Well, you could have the prom pointing at screen/keyboard, and the kernel,
with an open console at the serial port.
Read Documentation
I installed Debian (Woody) on a Sparc Station 10.
Boot console is the serial line ttya. Thats OK.
In addition I'd like to operate the attached keyboard/monitor.
But all I get is:
INIT: Id 1 respawning too fast: disabled for 5 minutes
(Boot console on keyboard/monitor is OK)
Is it possible
Is it possible to simutaniously have serial console and
keyboard/monitor?
Well, you could have the prom pointing at screen/keyboard, and the kernel,
with an open console at the serial port.
Read Documentation/serial-console.txt and Serial Console in the
Text-Terminal-HOWTO.
--
Alvaro
On Tue, 10 Jul 2001 15:50:32 -0500, Branden Robinson wrote:
If someone can find a configuration that works and uses only:
XkbRules
XkbModel
XkbLayout
That would be great. XkbVariant and XkbOptions are also acceptable, but
should not be necessary.
Here's what I use:
XkbRules sun
On Mon, Jul 09, 2001 at 04:27:17PM +0200, Guenter Millahn wrote:
Section InputDevice
Identifier Keyboard0
Driver keyboard
Option XkbRules sun
Option XkbModel type5_unix
Option XkbLayout en_US
Option XkbKeymap
On Tue, Jul 10, 2001 at 03:50:32PM -0500, Branden Robinson wrote:
On Mon, Jul 09, 2001 at 04:27:17PM +0200, Guenter Millahn wrote:
Section InputDevice
Identifier Keyboard0
Driver keyboard
Option XkbRules sun
Option XkbModel type5_unix
Thanks to everybody that helped with the video, mouse and the keyboard
setting.
Here is the working configuration that I managed to put up with your
help, so maybe someone with my problem can find it in the archives:
(search engine baits: x xwindow linux sparc ultrasparc ultra10 sun
xkbmodel
why you have to describe a type6 keyboard as a typ4 to get it
working? =)
Because the Type5 and Type6 keyboards are cosmetic (ergonomic, I guess)
changes
to the Type4. But hw-wise they're the same. More on this in the Sun h/w
faq.
Thanks to everybody that contributed
on the problem myself. I can start X, the server log
indicates that it recognizes my framebuffer, but the keyboard and mouse
are completely ignored. Same story with xf86cfg. I'd be really very
greatfull for any input on this problem. For reference, my own config is:
Sun Ultra60,
Creator3d ffb
On Sat, 12 May 2001, B.C.J.O wrote:
On Fri, 11 May 2001, Jim Crumley wrote:
Thanks. This worked perfectly. I've searched through the archives
several times, but didn't come across the requisite info -- my bad. Any
idea why you have to describe a type6 keyboard as a typ4 to get
(again... please CC when you reply :-)
so, I got X working, but I have not been able to get it to correctly
recognize the keyboard It's a type 6 sun keyboard.
Can anyone of you mail me a working example?
Pf
Has anyone been able to get a type6 keyboard working with xfree-4?
Everything else, mouse, creator, ffb, etc, seem to be working fine.
I have tried type6, type5, and type5c.
The key layout is the same as type5. But they are jumbled up when I type.
Any help would be appreciated.
Randy
--
Why yes
woody or sid the keymaps in the xserver go crazy, and the system
has no idea about the maus. The keyboard is a newish sun type6 /w
accompanying mouse. I would appreciate it if somebody would be good enough
to paste an operational InputDevice XF86Config section for a type6
keyboard and mouse.. even
AP == Andrew Pollock [EMAIL PROTECTED] writes:
AP Well, today, I can announce that I've found a valuable use for
AP Red Hat on Sparc, looking at it's XF86Config file :-)
AP You need to put these lines in your keyboard section and all
AP becomes good:
I've been able to get away
G'day Renato,
You need to link /dev/mouse to /dev/sunmouse
PS. Its a bus mouse not ps2.
Check the back of your keyboard for the type eg. mine is a US type 5, run
kbdconfig as root, choose /sun for the keyboard definition, and choose
sunkeymap for the layout if you have a US keymap.
Otherwise
Hi friends,
First of all, i would like to say thanks to your helpfull e-mails. They put
me on the rigth way to solve my keyboard and mouse problems.
I already solved the mouse trouble. After a lot of racking, I readed in
Debian-sparc list that a french guy had the same problem
101 - 200 of 268 matches
Mail list logo
