> Absolutely wrong.  The previous situation was a mess, keyboard
> maps had to be coded up for every keyboard type out there.  Now,
> multi-lingual keyboard maps need to be written for only one
> keyboard type, x86.
> 
This is most probably a matter of taste. 
I would like using the additional Keys on the Keyboard but with the x86
layout they seem to be unaccessible, or is there a way of using them? 

> Reconfigure the console package properly to just use the kernel
> default keymap.
>
Wouldn't this give me a US KB layout? 
 
> Yes, there is some problem initializing the serial line that the
> keyboard and mouse use.  The break characters that get detected
> when the baud rate is incorrect are not showing up for some reason.
> 
> What kind of machine is this?  It only happens with certain serial
> controllers, not all, which is why your machine type is important.
>
The machine is an Ultra Sparc 30, I have posted some output from hwconfig
below. 

regards
 D. 

��<6>su0�at�0x000001fff13062f8�(irq�=�4,7ea)�is�a�16550A
��<6>su1�at�0x000001fff13083f8�(irq�=�9,7e9)�is�a�16550A
��<6>mice:�PS/2�mouse�device�common�for�all�mice
��<6>input:�Sun�Type�5�keyboard�on�su/serio1
��<6>input:�Sun�Mouse�on�su/serio0
----- /proc/interrupts -----
����4:�����112041��su(mouse):7ea,�sym53c8xx:7e0,�aic7xxx:7dc
����5:������29776��eth0:7e1
����8:����������1��parport0:7e2
����9:�������1863��su(kbd):7e9
���12:���������86��serial(sab82532):7eb
���15:����������0��PSYCHO�UE:7ee,�PSYCHO�CE:7ef,�PSYCHO�PCIERR:7f0,�PSYCHO
PCIERR:7f1
----- /proc/interrupts end -----
>> cpu.1: cpuinfo
----- /proc/cpuinfo -----
��cpu�����������:�TI�UltraSparc�II��(BlackBird)
��fpu�����������:�UltraSparc�II�integrated�FPU
��promlib���������������:�Version�3�Revision�9
��prom����������:�3.9.5
��type����������:�sun4u
��ncpus�probed��:�1
��ncpus�active��:�1
��Cpu0Bogo������:�491.52
��Cpu0ClkTck����:�000000000ec7f7dc
��MMU�Type������:�Spitfire
----- /proc/cpuinfo end -----
----- sysfs driver list (id 0xcbb836f31a7e9d8e) -----
��������sermouse:�/devices/serio0
����������sunkbd:�/devices/serio1
----- sysfs driver list end -----
----- /proc/tty/driver/serial -----
��0:�uart:SAB82532�V3.2�mmio:0x1FFF1400000�irq:7428896�tx:40�rx:0
��1:�uart:SAB82532�V3.2�mmio:0x1FFF1400040�irq:7428896�tx:48�rx:0
----- /proc/tty/driver/serial end -----
>> misc.5: misc data
----- misc resources -----
irq:0��4�(���112041)�"su(mouse):7ea"�"sym53c8xx:7e0"�"aic7xxx:7dc"
irq:0��9�(�����1863)�"su(kbd):7e9"
irq:0 12 (�������86)�"serial(sab82532):7eb"
irq:0 15 (��������0)�"PSYCHO�UE:7ee"�"PSYCHO�CE:7ef"�"PSYCHO�PCIERR:7f0"
"PSYCHO PCIERR:7f1"
dma:1 0 "parport0"
dma:1 4 "cascade"
----- misc resources end -----
>> usb.3.2: evdev mod
>> usb.3.3: input
��input:�name�=�event0,�path�=�/class/input/event0
����dev�=�13:64
����input�device:�bus�=�serio,�bus_id�=�serio1�driver�=�sunkbd
������path�=�/devices/serio1
��input:�name�=�event1,�path�=�/class/input/event1
����dev�=�13:65
����input�device:�bus�=�serio,�bus_id�=�serio0�driver�=�sermouse
������path�=�/devices/serio0
��input:�name�=�mice,�path�=�/class/input/mice
����dev�=�13:63
��input:�name�=�mouse0,�path�=�/class/input/mouse0
����dev�=�13:32
����input�device:�bus�=�serio,�bus_id�=�serio0�driver�=�sermouse
������path�=�/devices/serio0
>> usb.3.4: lp
>> input.2: input
----- /proc/bus/input/devices -----
��I:�Bus=0013�Vendor=0010�Product=0005�Version=0100
��N:�Name="Sun�Type�5�keyboard"
��P:�Phys=su/serio1/input0
��H:�Handlers=kbd�event0
��B:�EV=160003
��B:�KEY=7ff�e09efffd01cfffff�fffffffffffffffe
��B:�LED=f
��B:�SND=3

��I:�Bus=0013�Vendor=0002�Product=0001�Version=0100
��N:�Name="Sun�Mouse"
��P:�Phys=su/serio0/input0
��H:�Handlers=mouse0�event1
��B:�EV=7
��B:�KEY=70000�0�0�0�0
��B:�REL=3

----- /proc/bus/input/devices end -----
bus = 19, name = Sun Type 5 keyboard
��handlers�=�kbd�event0
��key�=�000007ffffffffffffffffff
��mouse�buttons�=�0
��mouse�wheels�=�0
bus = 19, name = Sun Mouse
��handlers�=�mouse0�event1
��key�=�0007000000000000000000000000000000000000
��rel�=�00000003
��mouse�buttons�=�0
��mouse�wheels�=�0


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

Reply via email to