headers
Lukas Kaminski | 1 Dec 2010 22:06

(unknown)

Hello again!

i think providing diffs wasn't my best idea, so i send the changes again,
this time as patches.
recently i've forgotten one header and spx.c was a mess. now i've fixed
this up :)

i've never tried to build everything from scratch with this patches, only
to build the needed drivers and the server itself in
/usr/src/external/mit/xorg/server (native), but i'll try to crossbuild a
full system tonight.

unfortunately i don't have much time to search the remaining bug with the
keyboard. maybe someone can give me a hint?

Lukas
Attachment (bsd_kbd.c.patch): application/octet-stream, 695 bytes
Attachment (bsd_KbdMap.c.patch): application/octet-stream, 6302 bytes
Attachment (compiler.h.patch): application/octet-stream, 1411 bytes
Attachment (drivers_Makefile.patch): application/octet-stream, 612 bytes
Attachment (Makefile.common.patch): application/octet-stream, 1107 bytes
Attachment (spx.c.patch): application/octet-stream, 663 bytes
Attachment (xfree86_Makefile.patch): application/octet-stream, 1227 bytes
Attachment (xorgos_Makefile.patch): application/octet-stream, 2080 bytes
Permalink | Reply | 0 comments |
headers
Lukas Kaminski | 1 Dec 2010 22:08

Patches for building Xorg-Server on VAX

Hello again!

i think providing diffs wasn't my best idea, so i send the changes again,
this time as patches.
recently i've forgotten one header and spx.c was a mess. now i've fixed
this up :)

i've never tried to build everything from scratch with this patches, only
to build the needed drivers and the server itself in
/usr/src/external/mit/xorg/server (native), but i'll try to crossbuild a
full system tonight.

unfortunately i don't have much time to search the remaining bug with the
keyboard. maybe someone can give me a hint?

Lukas

PS.: Sorry for the SPAM
Attachment (bsd_kbd.c.patch): application/octet-stream, 695 bytes
Attachment (bsd_KbdMap.c.patch): application/octet-stream, 6302 bytes
Attachment (compiler.h.patch): application/octet-stream, 1411 bytes
Attachment (drivers_Makefile.patch): application/octet-stream, 612 bytes
Attachment (Makefile.common.patch): application/octet-stream, 1107 bytes
Attachment (spx.c.patch): application/octet-stream, 663 bytes
Attachment (xfree86_Makefile.patch): application/octet-stream, 1227 bytes
Attachment (xorgos_Makefile.patch): application/octet-stream, 2080 bytes
Permalink | Reply | 1 comment |
headers
David Brownlee | 1 Dec 2010 22:55
Picon

Re: Patches for building Xorg-Server on VAX

On 1 December 2010 21:08, Lukas Kaminski <kaminski <at> sdf-eu.org> wrote:
> Hello again!
>
> i think providing diffs wasn't my best idea, so i send the changes again,
> this time as patches.
> recently i've forgotten one header and spx.c was a mess. now i've fixed
> this up :)
>
> i've never tried to build everything from scratch with this patches, only
> to build the needed drivers and the server itself in
> /usr/src/external/mit/xorg/server (native), but i'll try to crossbuild a
> full system tonight.
>
> unfortunately i don't have much time to search the remaining bug with the
> keyboard. maybe someone can give me a hint?

Just a quick question or two :)

src/external/mit/xorg/server/xorg-server/Makefile.common
- Why disable Xvfb? - its a useful testing tool on headless machines

src/sys/arch/vax/vsa/spx.c
- Did the spx_putchar crash on the first character output?

src/external/mit/xorg/server/xorg-server/hw/xfree86/Makefile
- Any changes to remove dri or similar should be conditional on vax -
though why do they need to be disabled?

src/external/mit/xorg/server/xorg-server/hw/xfree86/xorgos/Makefile
- The later changes to enable a (commented out) netbsdPci.c on vax are
(Continue reading)

Permalink | Reply | 0 comments |
headers
Manuel Bouyer | 6 Dec 2010 18:26

microvax II 3300 dead ethernet

Hi,
I have a microvax II 3300 which I usually netboot. When powering it up
today, netboot failed and it seems that the MVII doesn't send any
packet to the network (tcpdump on the MOP server, and on another box
on the same ethernet, doesn't see anything from the vax). I checked cables
and tried both the thin ethernet and AUI ports, both are silent.

Could it be a software issue (some setting in the microvax II firmware
than have been lost while powered down) or is it really a hardware issue ?
There is no unusual messages on the serial console when it is powered up ...

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 2 comments |
headers
John Klos | 15 Dec 2010 06:37

Re: VAXstation 4000/90 help

Hi,

>  I also verified that without any memory, the LEDS show 0xF2 and it
> sits there with no other action or output.  With working memory present,
> the LEDS start with 0xFC, runs through a number of other combinations, and 
> ends with 0xF3 displaying when it's at the ROM prompt.  This would seem to 
> indicate that you don't have working memory.

This helped me narrow things down. I tried various combinations until I 
looked very carefully at both the memory SIMMs and the motherboard and 
noticed a strange fuzz which looked a little bit like how circuit boards 
look when a battery has leaked and has caused corrosion. I cleaned both 
the SIMM which had it as well as the motherboard slot, looked for anything 
which might've caused it (leaky capacitor, for instance), but I couldn't 
find anything, so I put everything back and got blinky lights, then the 
tones that play after several minutes!

      5         MEM    OK
                       32MB   0A,0B,0C,0D=4MB, 1E,1F,1G,1H=4MB

Next... Does anyone know what this error means?

      2       LCSPX    ?? 001 0480
                       Highres 66Hz - 8 Plane 4Mpixel FB - V1.0

...

>>> T 2
| |
###
(Continue reading)

Permalink | Reply | 4 comments |
headers
Michael L. Hitch | 15 Dec 2010 19:56

Re: VAXstation 4000/90 help

On Wed, 15 Dec 2010, John Klos wrote:

> Next... Does anyone know what this error means?
>
>     2       LCSPX    ?? 001 0480
>                      Highres 66Hz - 8 Plane 4Mpixel FB - V1.0
>
> ...
>
>>>> T 2
> | |
> ###
> ?? 001   2     LCSPX  0480
>
>
>  84 FAIL
>>>> show error
>
> ?? 001   2     LCSPX  01E0
> 015 01E1 00FC1503 0054C797 00000000 00000000 00000000 00000000

   I think the graphics board can detect the presence of a monitor, and 
will show an error if there is no monitor connected.

--
Michael L. Hitch			mhitch <at> montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA
(Continue reading)

Permalink | Reply | 3 comments |
headers
John Klos | 16 Dec 2010 20:50

Re: VAXstation 4000/90 help

>>     2       LCSPX    ?? 001 0480
>>                      Highres 66Hz - 8 Plane 4Mpixel FB - V1.0

>  I think the graphics board can detect the presence of a monitor, and will 
> show an error if there is no monitor connected.

Whew! I read something about it being a DAC error, and I suppose the DAC 
would have the circuitry to detect the connection of a monitor.

Does anyone know of a way to have the VAX skip this error and boot 
automatically anyway?

Just for everyone's general information, a 4000/90 won't boot NetBSD (5.1, 
generic kernel) without the graphics card installed. I got a kernel panic 
when I booted without the card, and while I'm sure I can just make a 
custom kernel to get around it, it might be good for others to know.

Thanks,
John
Permalink | Reply | 2 comments |
headers
arcarlini | 17 Dec 2010 20:32

RE: VAXstation 4000/90 help

John Klos wrote:
> Does anyone know of a way to have the VAX skip this error and boot
> automatically anyway? 

You can try flicking the switch at the front to tell it to run headless.
That must work - mine boots OpenVMS that way just by being powered up.

> Just for everyone's general information, a 4000/90 won't boot NetBSD
> (5.1, generic kernel) without the graphics card installed. I got a
> kernel panic
> when I booted without the card, and while I'm sure I can just make a
> custom kernel to get around it, it might be good for others to know.

Even with the switch in the "I'm a VAXserver not a VAXstation" position?

Antonio
arcarlini <at> iee.org
Permalink | Reply | 1 comment |
headers
John Klos | 17 Dec 2010 21:31

RE: VAXstation 4000/90 help

>> Does anyone know of a way to have the VAX skip this error and boot
>> automatically anyway?
>
> You can try flicking the switch at the front to tell it to run headless.
> That must work - mine boots OpenVMS that way just by being powered up.

I forgot that when I was trying to diagnose the doing-nothing-at-all 
problem I had toggled that switch.

>> Just for everyone's general information, a 4000/90 won't boot NetBSD 
>> (5.1, generic kernel) without the graphics card installed. I got a 
>> kernel panic when I booted without the card, and while I'm sure I can 
>> just make a custom kernel to get around it, it might be good for others 
>> to know.
>
> Even with the switch in the "I'm a VAXserver not a VAXstation" position?

That hadn't even occured to me. I'll ty it. I figure if it's just doing 
bulk builds, it doesn't need the extra power draw and heat.

Thanks,
John
Permalink | Reply | 0 comments |
headers
John Klos | 19 Dec 2010 18:36

Panic question

Hi,

Any ideas? It might not be that much of a coincidence that this happened 
while I was moving the system... But why? (VAXstation 4000/90, building 
perl from pkgsrc, 32 megs memory, netbsd-5 from two days ago)

panic: 380.1 (??): KSP invalid 0x84b8ec04 <at> 0x800d7606 pcb 0x84b8d000 fp 
0x84b8ec08 psl 0xc00004)
Begin traceback...
panic: %d.%d (%s): KSP invalid %#x <at> %#x pcb %p fp %#x psl %#x)
Stack traceback :
          Process is executing in user space.
End traceback...

Thanks,
John
--

-- 
Your mother manages RSX systems in Hell!
Permalink | Reply | 0 comments |

Gmane