Re: Interrupt Storm Dell PowerEdge 1850

2005-08-31 Thread Alex Zbyslaw

Nicklas B. Westerlund wrote:


Alex Zbyslaw wrote:

 


But if you do that, then I believe you will not be able to use the
DRAC as a remote console because your virtual keyboard won't work.
(not without changing to the ukbd0 from your real keyboard, which
pretty much defeats the point of the virtual keyboard i.e. using it
automatically from miles away).
   




Which I'd have to prove wrong, as it works great on my end here.  Or
atleast it did when I tried the DRAC console, after everything was in
order..  Ofcourse, I might be wrong. although I doubt it.

 

What version of FreeBSD?  AFAIU, FreeBSD only supports one console 
keyboard, so if you plug in ukbd1 and make it the console, the DRAC on 
ukbd0 shouldn't work.  I'm sure I tried this and that it didn't work, 
but I'd be happy to be wrong.  Are you sure that both your DRAC and USB 
work at the same time?


--Alex

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-31 Thread Nicklas B. Westerlund
Alex Zbyslaw wrote:


 What version of FreeBSD?  AFAIU, FreeBSD only supports one console
 keyboard, so if you plug in ukbd1 and make it the console, the DRAC on
 ukbd0 shouldn't work.  I'm sure I tried this and that it didn't work,
 but I'd be happy to be wrong.  Are you sure that both your DRAC and
 USB work at the same time?


Alex,

On those machines we're running releng_5_4.
But, as I said, I might be wrong. After all, it is quite some time since
I tried this.

I never tried using both at the same time, but I do know that I set ukbd
to 1, to be able to use the console. Then, when I was done and put the
machine into pre-production I used the DRAC. (Again, this is what I
remember - so I'm not going to argue points before I get a chance to try
it again).

The question we should ask ourselves though is why anyone would have to
use a 'normal' console keyboard, when there's the DRAC console.

Nick.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-31 Thread Alex Zbyslaw
This may be getting a bit Off Topic, but I always find it annoying when 
archive thread peter out without any conclusion...


Nicklas B. Westerlund wrote:


Alex Zbyslaw wrote:

 


What version of FreeBSD?  AFAIU, FreeBSD only supports one console
keyboard, so if you plug in ukbd1 and make it the console, the DRAC on
ukbd0 shouldn't work.  I'm sure I tried this and that it didn't work,
but I'd be happy to be wrong.  Are you sure that both your DRAC and
USB work at the same time?
   




Alex,

   On those machines we're running releng_5_4.
But, as I said, I might be wrong. After all, it is quite some time since
I tried this.

I never tried using both at the same time, but I do know that I set ukbd
to 1, to be able to use the console. Then, when I was done and put the
machine into pre-production I used the DRAC. (Again, this is what I
remember - so I'm not going to argue points before I get a chance to try
it again).

The question we should ask ourselves though is why anyone would have to
use a 'normal' console keyboard, when there's the DRAC console.
 

I may have a chance to test this again, sometime, but the machine is 
installed remotely now and I don't know if they have a USB keyboard or 
not :-(  If you made ukdb1 the console from the command line, then this 
would have gone away when the machine was rebooted.


Why would you want to do this?  2 reasons I can think of:

   1) There actually are sometimes staff at the remote location, and 
having a keyboard next to the machine makes it easier to use the console 
at the same time as doing hardware things like inserting CDs.  (Note 
that you can use a local keyboard if you are fiddling with the BIOS, 
since it's just FreeBSD which forces one keyboard).  The same issue 
affects PS/2 keyboards as well as USB ones, btw.


   2) The DRAC keyboard through the Java app is a bit funny.  Below is 
a quick message I wrote (not to this list) summarising my difficulties.  
The lack of a \ is a pain as there is rarely one on-screen to 
cut-and-paste.  # less difficult since it's usually in some file which 
has other comments in it already.


Neither of those *require* you to use a local keyboard, though.

--Alex


Here is my experienced behaviour using the Java console applet.

Sometimes, when the applet starts you get these key mappings:

\ - #
| - ~
ALT` - |
# - f
~ - F

nothing produces \

If you change the mouse acceleration mode you get these instead:

\ - \
| - |
@ - 
 - @
# - f
~ - F

nothing produces #


However, BEWARE of changing the mode when in the BIOS, as it seems to 
make the keyboard stop working.  When in FreeBSD with a mouse, you can 
copy some text with the white cursor, and that seems to make the 
keyboard work again.  That option not available in the BIOS.


--Alex

PS No way to paste text as yet.




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-31 Thread John Straiton

You sir, are a genius. Fixed

John


On Aug 27, 2005, at 6:42 AM, Nicklas B. Westerlund wrote:


John Straiton wrote:



Hello,

I am attempting to install 5.4R on a brand new Dell PowerEdge 1850
machine. The installation goes perfectly however after the reboot, I
am unable to log into the machine (or in this case, create the
entropy salt)




John,

Let me take a quick guess.. You've got the DRAC4 card installed?
If you do, that's why the keyboard doesn't work, as it defaults to the
DRAC4 one (Although it's only a virtual keyboard).
If that's the case, just go to singleuser, and change devd.conf and
change ukbd0 to ukbd1.

Nick.




John Straiton
[EMAIL PROTECTED]



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-29 Thread Alex Zbyslaw

Nicklas B. Westerlund wrote:


John Straiton wrote:

 


Hello,

I am attempting to install 5.4R on a brand new Dell PowerEdge 1850 
machine. The installation goes perfectly however after the reboot, I 
am unable to log into the machine (or in this case, create the 
entropy salt)
   




John,

Let me take a quick guess.. You've got the DRAC4 card installed?
If you do, that's why the keyboard doesn't work, as it defaults to the
DRAC4 one (Although it's only a virtual keyboard). 
If that's the case, just go to singleuser, and change devd.conf and

change ukbd0 to ukbd1.
 

But if you do that, then I believe you will not be able to use the DRAC 
as a remote console because your virtual keyboard won't work.  (not 
without changing to the ukbd0 from your real keyboard, which pretty much 
defeats the point of the virtual keyboard i.e. using it automatically 
from miles away).


My advice is to use the DRAC as your console.  You can still use a PS/2 
kbd for the BIOS or from the install CD (as long as you don't pick 
option 8(?) boot with USB kbd).


--Alex

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-29 Thread Nicklas B. Westerlund
Alex Zbyslaw wrote:



 But if you do that, then I believe you will not be able to use the
 DRAC as a remote console because your virtual keyboard won't work.
 (not without changing to the ukbd0 from your real keyboard, which
 pretty much defeats the point of the virtual keyboard i.e. using it
 automatically from miles away).


Which I'd have to prove wrong, as it works great on my end here.  Or
atleast it did when I tried the DRAC console, after everything was in
order..  Ofcourse, I might be wrong. although I doubt it.

Nick.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-27 Thread Nicklas B. Westerlund
John Straiton wrote:

 Hello,

 I am attempting to install 5.4R on a brand new Dell PowerEdge 1850 
 machine. The installation goes perfectly however after the reboot, I 
 am unable to log into the machine (or in this case, create the 
 entropy salt)


John,

Let me take a quick guess.. You've got the DRAC4 card installed?
If you do, that's why the keyboard doesn't work, as it defaults to the
DRAC4 one (Although it's only a virtual keyboard). 
If that's the case, just go to singleuser, and change devd.conf and
change ukbd0 to ukbd1.

Nick.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Interrupt Storm Dell PowerEdge 1850

2005-08-26 Thread John Straiton

Hello,

I am attempting to install 5.4R on a brand new Dell PowerEdge 1850  
machine. The installation goes perfectly however after the reboot, I  
am unable to log into the machine (or in this case, create the  
entropy salt)


I have noticed 2 quirky behaviors with this machine.
1)  I get to just about the local package time of boot when I start  
seeing

Interrupt storm detected on irq18: uhci; throttling interrupt source

While not a solution, I got this to go away by disabling the USB  
ports on the system in the BIOS. I only mention it because it's the  
only other new behaviour I'm seeing on this machine versus the  
other boxes I maintain.


2) The keyboard works until the devd detects a PS2 keyboard and  
installs the device for it.
As in, I can pick which way I'd like to boot FreeBSD from the menu  
and can hit keys during the probing but as soon as I see the message  
that it's set up the keyboard, bam..nonresponsive.


As a test, I installed 4.11R on the machine tonight and it works  
flawlessly. The only problem is that the machine this was intending  
to replace is already running 5.2+ so I'll need to get this one into  
the 5.X arena somehow.


Thoughts?


John Straiton
j k s @clickcom.com



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-26 Thread N.J. Thomas
* John Straiton [EMAIL PROTECTED] [2005-08-26 15:25:40 -0400]:
 While not a solution, I got this to go away by disabling the USB
 ports on the system in the BIOS. I only mention it because it's the
 only other new behaviour I'm seeing on this machine versus the
 other boxes I maintain.

Bad mobo perhaps? (I'm presuming the USB is intergrated into it.

Under 4.11, can you use the USB ports successfully?

Thomas

-- 
N.J. Thomas
[EMAIL PROTECTED]
Etiamsi occiderit me, in ipso sperabo
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interrupt Storm Dell PowerEdge 1850

2005-08-26 Thread John Straiton

John Straiton [EMAIL PROTECTED] [2005-08-26 15:25:40 -0400]:



 While not a solution, I got this to go away by disabling the USB
 ports on the system in the BIOS. I only mention it because it's the
 only other new behaviour I'm seeing on this machine versus the
 other boxes I maintain.

Bad mobo perhaps? (I'm presuming the USB is intergrated into it.
Under 4.11, can you use the USB ports successfully?

Thomas

Come to think of it, no. I tried using a USB keyboard in 4.11 and  
although I got a message on console to the effect of it seeing the  
keyboard I had just added, I was not able to log in until I swapped  
to a PS2 one.


I think I'm going to just load a WinServer image on it long enough to  
see what errors pop up in that realm and try to gather a more  
extensive list of behaviours.




Thanks for answering, 'till later..

John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]