[Voyage-linux] Is the PS/2 keyboard configured work on VIA EPIA?

[Punky Tse]

Robert,

I have no idea at the moment.  But if I experienced the same I would
check the followings:

cat /proc/devices
cat /proc/interrupts

then see if /proc/input/keyboard is there?

if not,
mknod /dev/input/keyboard c 10 150

On 6/9/05, Robert Haskins <rhaskins at cnetwork.com> wrote:
> No line defining a serial console that I can see. I am no LILO expert
> mind you; I work much more with grub.
> 
> Here is my lilo.conf:
> 
> boot = /dev/hdc
> #compact
> install=text
> map=/boot/map
> vga=normal
> delay=1
> default=Linux
> 
> image=/vmlinuz
> #       initrd=/initrd.img
>                  root=/dev/hdc1
>          label=Linux
>          read-only
> #       restricted
> #       alias=1
> 
> image=/vmlinuz.old
>                  root=/dev/hda1
>          label=LinuxOLD
>          read-only
>          optional
> #       restricted
> #       alias=2
> 
> Punky Tse wrote:
> > please check if the /etc/lilo.conf contain a line:
> >
> >    append="console=ttyS0,9600n8"
> >
> > I don't know if this line cause you problem.  You can try to remove it
> > and re-run lilo on CF.  But doing so you can only ssh to the box.
> >
> > Robert Haskins wrote:
> >
> >> Yes indeed, ssh to the box works just fine. And the ttyS0 console port
> >> works just fine (with changes). Console related stuff comes out to the
> >> VGA display. It's *just* the PS/2 keyboard that doesn't work.
> >>
> >> Here is my (modified) inittab file:
> >>
> >> # /etc/inittab: init(8) configuration.
> >> # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
> >>
> >> # The default runlevel.
> >> id:2:initdefault:
> >>
> >> # Boot-time system configuration/initialization script.
> >> # This is run first except when booting in emergency (-b) mode.
> >> si::sysinit:/etc/init.d/rcS
> >>
> >> # What to do in single-user mode.
> >> ~~:S:wait:/sbin/sulogin
> >>
> >> # /etc/init.d executes the S and K scripts upon change
> >> # of runlevel.
> >> #
> >> # Runlevel 0 is halt.
> >> # Runlevel 1 is single-user.
> >> # Runlevels 2-5 are multi-user.
> >> # Runlevel 6 is reboot.
> >>
> >> l0:0:wait:/etc/init.d/rc 0
> >> l1:1:wait:/etc/init.d/rc 1
> >> l2:2:wait:/etc/init.d/rc 2
> >> l3:3:wait:/etc/init.d/rc 3
> >> l4:4:wait:/etc/init.d/rc 4
> >> l5:5:wait:/etc/init.d/rc 5
> >> l6:6:wait:/etc/init.d/rc 6
> >> # Normally not reached, but fallthrough in case of emergency.
> >> z6:6:respawn:/sbin/sulogin
> >>
> >> # What to do when CTRL-ALT-DEL is pressed.
> >> ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
> >>
> >> # Action on special keypress (ALT-UpArrow).
> >> #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let
> >> this work."
> >>
> >> # What to do when the power fails/returns.
> >> pf::powerwait:/etc/init.d/powerfail start
> >> pn::powerfailnow:/etc/init.d/powerfail now
> >> po::powerokwait:/etc/init.d/powerfail stop
> >>
> >> # /sbin/getty invocations for the runlevels.
> >> #
> >> # The "id" field MUST be the same as the last
> >> # characters of the device (after "tty").
> >> #
> >> # Format:
> >> #  <id>:<runlevels>:<action>:<process>
> >> #
> >> # Note that on most Debian systems tty7 is used by the X Window System,
> >> # so if you want to add more getty's go ahead but skip tty7 if you run X.
> >> #
> >> 1:2345:respawn:/sbin/getty 38400 tty1
> >> 2:23:respawn:/sbin/getty 38400 tty2
> >> 3:23:respawn:/sbin/getty 38400 tty3
> >> 4:23:respawn:/sbin/getty 38400 tty4
> >> 5:23:respawn:/sbin/getty 38400 tty5
> >> 6:23:respawn:/sbin/getty 38400 tty6
> >>
> >> # Example how to put a getty on a serial line (for a terminal)
> >> #
> >> S0:2345:respawn:/sbin/getty -L ttyS0 38400 vt100
> >> #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
> >> #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
> >>
> >> # Example how to put a getty on a modem line.
> >> #
> >> #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
> >>
> >> Punky Tse wrote:
> >>
> >>> But you should be able to ssh to the box.  BTW, can you send me the
> >>> /etc/inittab for verification?
> >>>
> >>> On 6/8/05, Robert Haskins <rhaskins at cnetwork.com> wrote:
> >>>
> >>>> Do I need to do something special to get the PS/2 keyboard on VIA EPIA
> >>>> to work under voyage-0.1? I've checked the kernel config and the
> >>>> appropriate settings seem to be turned on, yet I get no respose when
> >>>> using the PS/2 keyboard after it boots into multi-user mode. And the
> >>>> keyboard works just fine in the BIOS, so this has got to be an issue
> >>>> with voyage.
> >>>>
> >>>> Thanks for your help!
> >>>>
> >>>> _______________________________________________
> >>>> Voyage-linux mailing list
> >>>> Voyage-linux at list.voyage.hk
> >>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
> >>>>
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Voyage-linux mailing list
> >> Voyage-linux at list.voyage.hk
> >> http://list.voyage.hk/mailman/listinfo/voyage-linux
> >
> >
> >
> 


-- 
-- 
Regards,
Punky
P U N K N ! X  . c o m
Technology + Lifestyle
(http://www.punknix.com) 

Voyage Linux
(http://www.voyage.hk/software/voyage.html)