[syslinux] Dell and pxelinux keyboard problems

J.H. warthog19 at eaglescrag.net
Fri Feb 2 10:52:53 PST 2007


Make sure that the bios has turned on usb keyboard and usb mouse
support, as syslinux doesn't have a usb stack in it.  It's likely in one
of the Bios upgrades that they either changed the setting or broke
legacy usb support.  But thats the direction I would look in.

- John 'Warthog9' Hawley

On Fri, 2007-02-02 at 19:33 +0100, Michael Redinger wrote:
> Hm, strange. We have quite a lot of them, too. I tried 4 different 
> machines - same problem with all of them.
> 
> I will try to have somebody at Dell look at this and will tell you when 
> I know more.
> 
> Thanks,
> Michael
> 
> Matt Barbieri schrieb:
> > I have many of those machines with A11 BIOS and they boot pxelinux with
> > no problem and keyboard works as it should
> > 
> > -----Original Message-----
> > From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On
> > Behalf Of H. Peter Anvin
> > Sent: Friday, February 02, 2007 12:57 PM
> > To: Michael Redinger
> > Cc: syslinux at zytor.com
> > Subject: Re: [syslinux] Dell and pxelinux keyboard problems
> > 
> > Michael Redinger wrote:
> >> Hi,
> >>
> >> I am having trouble with one Dell system and pxelinux: The keyboard
> > does
> >> not properly work.
> >> The computer boots, I press F12 to select the boot device, then I
> > select
> >>  the network card. Up to that point the keyboard works fine.
> >> Then pxelinux is booted, and I use menu.c32 to display a menu (or
> >> vesamenu.c32 - same result). Now the keyboard does not work anymore
> > ...
> >> This is a Dell OptiPlex GX620 (with an USB keyboard). The problem only
> >> occurs with the latest BIOS, A11. I have tried both A07 (factory
> >> installed) and A10 - both work fine.
> >> On the Dell homepage I found the following information about this BIOS
> >> version:
> >> "Improve OROM shadowing into BIOS"
> >>
> >> Could this be a pxelinux problem or do you (too) think that this is
> >> Dell's problem?
> > 
> > It probably is Dell touching memory they shouldn't be, but it's 
> > obviously not possible to diagnose at this distance.
> > 
> > Can you report this problem to Dell?
> > 
> > 	-hpa
> > 
> > _______________________________________________
> > SYSLINUX mailing list
> > Submissions to SYSLINUX at zytor.com
> > Unsubscribe or set options at:
> > http://www.zytor.com/mailman/listinfo/syslinux
> > Please do not send private replies to mailing list traffic.
> > 
> > 
> > 
> > 
> > ****************IMPORTANT--PLEASE READ*******************
> > This electronic message, including its attachments, is COMPANY CONFIDENTIAL and may contain PROPRIETARY or
> > LEGALLY PRIVILEGED information. If you are not the intended recipient, you are hereby notified that any use, 
> > disclosure, copying, or distribution of this message or any of the information included in it is unauthorized and strictly prohibited.
> > If you have received this message in error, please immediately notify the sender by reply e-mail and permanently delete this
> > message and its attachments, along with any copies thereof. Thank you
> > 
> 
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.




More information about the Syslinux mailing list