headers
Michael Thompson | 28 Jul 2011 02:28
Picon

Keyboard Problem with V5.1 on an E4000

I am trying to revive an E4000. I did a "boot cdrom" at the OpenBoot
prompt, NetBSD boots, displays a bunch of configuration messages on
the console, changes the configuration of the video display (it says
wsdisplay0) displays the configuration messages, and asks for the
terminal type. At this point the keyboard stops working.  A "stop-A"
will not get it back to OpenBoot. They keyboard works OK with
OpenSolaris.

Ideas?

--

-- 
Michael Thompson
Permalink | Reply | 14 comments |
headers
Martin Husemann | 28 Jul 2011 09:36
Picon

Re: Keyboard Problem with V5.1 on an E4000

On Wed, Jul 27, 2011 at 08:28:48PM -0400, Michael Thompson wrote:
> Ideas?

From the kernel messages, can you tell what variant of {e,u,o}hci the usb
is on and what it says about the keyboard?

Can you try a current snapshot?

Martin
Permalink | Reply | 12 comments |
headers
Eduardo Horvath | 28 Jul 2011 17:45
Picon

Re: Keyboard Problem with V5.1 on an E4000

On Wed, 27 Jul 2011, Michael Thompson wrote:

> I am trying to revive an E4000. I did a "boot cdrom" at the OpenBoot
> prompt, NetBSD boots, displays a bunch of configuration messages on
> the console, changes the configuration of the video display (it says
> wsdisplay0) displays the configuration messages, and asks for the
> terminal type. At this point the keyboard stops working.  A "stop-A"
> will not get it back to OpenBoot. They keyboard works OK with
> OpenSolaris.
> 
> Ideas?

I expect the standard kernel config doesn't support the driver attachment 
points you need.  

How is your keyboard attached to your E4K?  What's the OBP device path for 
the keyboard and display?  Do you have SBus or PCI I/O cards?

Eduardo
Permalink | Reply | 0 comments |
headers
doomwarrior | 28 Jul 2011 20:16
Picon

Re: Keyboard Problem with V5.1 on an E4000


> > From the kernel messages, can you tell what variant of {e,u,o}hci the usb
> is on and what it says about the keyboard?
>
> Can you try a current snapshot?
>
> Martin
>
It is a E4000 - big Iron - this shouldn't have a USB-controller at all!
Normal Keyboard-connector was still type5 keyboard back then - At least 
my E4500 has one.
The E4000 and E4500 are very similar so I doubt there is a difference.

Best Regards
Permalink | Reply | 11 comments |
headers
Michael Thompson | 29 Jul 2011 02:19
Picon

Re: Keyboard Problem with V5.1 on an E4000

On Thu, Jul 28, 2011 at 2:16 PM, doomwarrior <doomwarriorx <at> gmail.com> wrote:
>
>> > From the kernel messages, can you tell what variant of {e,u,o}hci the
>> > usb
>> is on and what it says about the keyboard?
>>
>> Can you try a current snapshot?
>>
>> Martin
>>
> It is a E4000 - big Iron - this shouldn't have a USB-controller at all!
> Normal Keyboard-connector was still type5 keyboard back then - At least my
> E4500 has one.
> The E4000 and E4500 are very similar so I doubt there is a difference.
>
> Best Regards
>
>
>

It has the normal Sun non-USB keyboard port on an I/O board in slot 0.
It has a CGSix Sbus board on the I/O board in slot 0.

I pulled all of the CPU boards but one to simplify the configuration.

With the keyboard unplugged and using the serial console:

ok boot cdrom
Boot device: /sbus <at> 3,0/SUNW,fas <at> 3,8800000/sd <at> 6,0:f  File and args:
NetBSD IEEE 1275 Bootblock
(Continue reading)

Permalink | Reply | 10 comments |
headers
matthew green | 29 Jul 2011 04:27
Picon
Favicon

re: Keyboard Problem with V5.1 on an E4000


> avail memory = 981 MB
> mainbus0 (root): SUNW,Ultra-Enterprise (8-slot Sun Enterprise
> E4500/E5500): hostid 809db71e
> cpu0 at mainbus0: SUNW,UltraSPARC-II  <at>  336 MHz, UPA id 0
> cpu0: 16K instruction (32 b/l), 16K data (32 b/l), 4096K external (64 b/l)
> cpu at mainbus0 not configured
> central at mainbus0 not configured
> fhc at mainbus0 not configured

i think one of these is the problem.  either central or fhc should
be attaching something here, and we're missing some of the onboard
devices attached here.  both serial ports and keyboard are missing
from these boot logs.

the reason it works with serial console is that pcons attaches.  the
reason it doesn't work with the keyboard attached is that pcons does
not attach here, presumably because wsdiplay0 claimed the console?

can you send or link to a prtconf -v or whatever it is from solaris
that will show the entire OFW device tree?  it would be great to get
these systems finally supported!

thanks.

.mrg.
Permalink | Reply | 9 comments |
headers
matthew green | 29 Jul 2011 10:01
Picon
Favicon

re: Keyboard Problem with V5.1 on an E4000


so, i ported the fhc and central drivers, and the clock and zs
attachments for them.  however, it crashes when attaching the
central device.  not sure what is up there yet, it crashes in
a very strange way.

myself and others will keep looking.

.mrg.
Permalink | Reply | 3 comments |
headers
MISS HELEZ QUENZIE | 29 Jul 2011 21:45
Picon
Favicon

Very Important Message


-- 
Good afternoon to you, I know you must be highly surprise to receive this
message from complete stranger you have never meet,I am using this as the
only medium to communicate you at the moment in Brief. My name is Miss
Helez Quenzie. I,m a single female medical. I come from Cuba Stingray City
is located 25 minutes east of Havana. I want to relocate to your area..

I have something very concerning, important to tell you and to discuss
with you which I need your concern and help over it. Can we discuss on it
and I need your private email address to enable me write in details and
direct mobile or phone line for us to discuss.
I would like to apply through this medium for your co-operation to secure
an opportunity to invest and to go into joint business partnership with
you. I have a substantial capital I honourably intend to invest with you
into a very lucrative business venture based on your advice and directive
after losing my father/family in the war in Libya.

MY DATA: MY NAME: MISS HELEZ QUENZIE
MY BIRTH: 19/04/1987
MY OCCUPATION:  STUDENT
MARITAL STATUS: SINGLE
NATIONALITY: CUBA

MY FATHER'S DATA:
HIS NAME: MR.ALBERTO QUENZIE
OCCUPATION: EXPORTER OF GOLD  AND DIAMOND INTO LIBYA
AGE BEFORE HIS DEATH : 69
NATIONALITY: CUBA
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Thompson | 30 Jul 2011 02:29
Picon

Re: Keyboard Problem with V5.1 on an E4000

On Thu, Jul 28, 2011 at 10:27 PM, matthew green <mrg <at> eterna.com.au> wrote:
>
>> avail memory = 981 MB
>> mainbus0 (root): SUNW,Ultra-Enterprise (8-slot Sun Enterprise
>> E4500/E5500): hostid 809db71e
>> cpu0 at mainbus0: SUNW,UltraSPARC-II  <at>  336 MHz, UPA id 0
>> cpu0: 16K instruction (32 b/l), 16K data (32 b/l), 4096K external (64 b/l)
>> cpu at mainbus0 not configured
>> central at mainbus0 not configured
>> fhc at mainbus0 not configured
>
> i think one of these is the problem.  either central or fhc should
> be attaching something here, and we're missing some of the onboard
> devices attached here.  both serial ports and keyboard are missing
> from these boot logs.
>
> the reason it works with serial console is that pcons attaches.  the
> reason it doesn't work with the keyboard attached is that pcons does
> not attach here, presumably because wsdiplay0 claimed the console?
>
> can you send or link to a prtconf -v or whatever it is from solaris
> that will show the entire OFW device tree?  it would be great to get
> these systems finally supported!
>
> thanks.
>
>
> .mrg.
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Michael Thompson | 30 Jul 2011 02:36
Picon

Re: Keyboard Problem with V5.1 on an E4000

On Thu, Jul 28, 2011 at 10:27 PM, matthew green <mrg <at> eterna.com.au> wrote:
>
>> avail memory = 981 MB
>> mainbus0 (root): SUNW,Ultra-Enterprise (8-slot Sun Enterprise
>> E4500/E5500): hostid 809db71e
>> cpu0 at mainbus0: SUNW,UltraSPARC-II  <at>  336 MHz, UPA id 0
>> cpu0: 16K instruction (32 b/l), 16K data (32 b/l), 4096K external (64 b/l)
>> cpu at mainbus0 not configured
>> central at mainbus0 not configured
>> fhc at mainbus0 not configured
>
> i think one of these is the problem.  either central or fhc should
> be attaching something here, and we're missing some of the onboard
> devices attached here.  both serial ports and keyboard are missing
> from these boot logs.
>
> the reason it works with serial console is that pcons attaches.  the
> reason it doesn't work with the keyboard attached is that pcons does
> not attach here, presumably because wsdiplay0 claimed the console?
>
> can you send or link to a prtconf -v or whatever it is from solaris
> that will show the entire OFW device tree?  it would be great to get
> these systems finally supported!
>
> thanks.
>
>
> .mrg.
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane