Re: Alpha/EISA broken?
Wilko Bulte writes: Sounds like an SRM problem or EISA configuration problem. Normaly the bus and then system board should be probed at this point. We never used EISA on alpha before - EISA bridge support was only conditionalisized on pci. Which triggers me: did you run the ECU? A copy is at: ftp://ftp.tcja.nl/pub/wilko/alpha I have this now. It looks like something I dd(1) onto a floppy? In case something is wrong with your eisa setup. Eisa configuration has to be done via alphabios. Do 'runecu' from the SRM console and it should work. With the froppy in the drive, I presume? The SRM console is the prompt where you type boot, right? (Typing from work - will do at home later). M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote: Wilko Bulte writes: Sounds like an SRM problem or EISA configuration problem. Normaly the bus and then system board should be probed at this point. We never used EISA on alpha before - EISA bridge support was only conditionalisized on pci. Which triggers me: did you run the ECU? A copy is at: ftp://ftp.tcja.nl/pub/wilko/alpha I have this now. It looks like something I dd(1) onto a floppy? yessir -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
Wilko Bulte writes: On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote: Wilko Bulte writes: Sounds like an SRM problem or EISA configuration problem. Normaly the bus and then system board should be probed at this point. We never used EISA on alpha before - EISA bridge support was only conditionalisized on pci. Which triggers me: did you run the ECU? A copy is at: ftp://ftp.tcja.nl/pub/wilko/alpha I have this now. It looks like something I dd(1) onto a floppy? yessir :-) And then do what with? Boot off it? run it from the bios? M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Thu, Jul 31, 2003 at 02:03:12PM +0100, Mark Murray wrote: Wilko Bulte writes: On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote: Wilko Bulte writes: Sounds like an SRM problem or EISA configuration problem. Normaly the bus and then system board should be probed at this point. We never used EISA on alpha before - EISA bridge support was only conditionalisized on pci. Which triggers me: did you run the ECU? A copy is at: ftp://ftp.tcja.nl/pub/wilko/alpha I have this now. It looks like something I dd(1) onto a floppy? yessir :-) And then do what with? Boot off it? run it from the bios? runecu from SRM. Better have a VGA card installed. Serial console is possible to but is a bit (hum..) of a challenge. -- | / o / /_ _ FreeBSD core team secretary |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
Wilko Bulte writes: And then do what with? Boot off it? run it from the bios? runecu from SRM. Better have a VGA card installed. Serial console is possible to but is a bit (hum..) of a challenge. I'm in big trouble. I have no VGA, it hangs off EISA, and I need to turn it on. I can connect on a serial console, but ECU assumes a VT220, and the output is unreadable. Any suggestions? M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Alpha/EISA broken?
Hi Latest boot on my Alpha breaks thus: Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xfc3303c0... sio1: gdb debugging port Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Fri Jul 25 11:50:23 BST 2003 [EMAIL PROTECTED]:/usr/src/sys/alpha/compile/G_ALPHA Preloaded elf kernel /boot/kernel/kernel at 0xfc868000. Preloaded elf module /boot/kernel/linux.ko at 0xfc8680d0. Preloaded elf module /boot/kernel/sysvshm.ko at 0xfc8681a0. Preloaded elf module /boot/kernel/sysvsem.ko at 0xfc868270. Preloaded elf module /boot/kernel/sysvmsg.ko at 0xfc868340. Preloaded elf module /boot/kernel/osf1.ko at 0xfc868410. Preloaded elf module /boot/kernel/if_dc.ko at 0xfc8684e0. Preloaded elf module /boot/kernel/miibus.ko at 0xfc8685b0. Preloaded elf module /boot/kernel/random.ko at 0xfc868680. Preloaded elf module /boot/kernel/isp.ko at 0xfc868750. Preloaded elf module /boot/kernel/cam.ko at 0xfc868820. Preloaded elf module /boot/kernel/nfsserver.ko at 0xfc8688f0. Preloaded elf module /boot/kernel/nfsclient.ko at 0xfc8689c8. AlphaServer 1000/1000A AlphaServer 1000A 5/500, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1BWX OSF PAL rev: 0x1000600020117 real memory = 266371072 (254 MB) avail memory = 250863616 (239 MB) cia0: 2117x Core Logic chipset cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21DWEN,BWEN pcib0: 2117x PCI host bus adapter on cia0 pci0: PCI bus on pcib0 eisab0: PCI-EISA bridge at device 7.0 on pci0 halted CPU 0 halt code = 7 machine check while in PAL mode PC = 18100 Any idea what gives? M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 01:07:46PM +0100, Mark Murray wrote: Hi Latest boot on my Alpha breaks thus: real memory = 266371072 (254 MB) avail memory = 250863616 (239 MB) cia0: 2117x Core Logic chipset cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21DWEN,BWEN pcib0: 2117x PCI host bus adapter on cia0 pci0: PCI bus on pcib0 eisab0: PCI-EISA bridge at device 7.0 on pci0 halted CPU 0 halt code = 7 machine check while in PAL mode PC = 18100 Any idea what gives? Not really, but as a datapoint today's -current does work OK on a EISA-less machine. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
Wilko Bulte writes: halt code = 7 machine check while in PAL mode PC = 18100 Any idea what gives? Not really, but as a datapoint today's -current does work OK on a EISA-less machine. GENERIC kernel also has above error. Remove eisa, and the boot goes straight to panic (no clock). M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 05:31:27PM +0100, Mark Murray wrote: Wilko Bulte writes: halt code = 7 machine check while in PAL mode PC = 18100 Any idea what gives? Not really, but as a datapoint today's -current does work OK on a EISA-less machine. GENERIC kernel also has above error. Remove eisa, and the boot goes straight to panic (no clock). That is because your clock sits behind eisa I think. ticso recently posted some days ago that eisa is now mandatory on alpha. I did not follow in detail to be honest. Check the archives. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
Wilko Bulte writes: GENERIC kernel also has above error. Remove eisa, and the boot goes straight to panic (no clock). That is because your clock sits behind eisa I think. ticso recently posted some days ago that eisa is now mandatory on alpha. I did not follow in detail to be honest. Check the archives. Well, that's left me hosed :-(. I looked through current@ and alpha@ (briefly) and saw nothing obvious. What should I be looking for? M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 01:07:46PM +0100, Mark Murray wrote: Hi Latest boot on my Alpha breaks thus: Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xfc3303c0... sio1: gdb debugging port Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Fri Jul 25 11:50:23 BST 2003 [EMAIL PROTECTED]:/usr/src/sys/alpha/compile/G_ALPHA Preloaded elf kernel /boot/kernel/kernel at 0xfc868000. Preloaded elf module /boot/kernel/linux.ko at 0xfc8680d0. Preloaded elf module /boot/kernel/sysvshm.ko at 0xfc8681a0. Preloaded elf module /boot/kernel/sysvsem.ko at 0xfc868270. Preloaded elf module /boot/kernel/sysvmsg.ko at 0xfc868340. Preloaded elf module /boot/kernel/osf1.ko at 0xfc868410. Preloaded elf module /boot/kernel/if_dc.ko at 0xfc8684e0. Preloaded elf module /boot/kernel/miibus.ko at 0xfc8685b0. Preloaded elf module /boot/kernel/random.ko at 0xfc868680. Preloaded elf module /boot/kernel/isp.ko at 0xfc868750. Preloaded elf module /boot/kernel/cam.ko at 0xfc868820. Preloaded elf module /boot/kernel/nfsserver.ko at 0xfc8688f0. Preloaded elf module /boot/kernel/nfsclient.ko at 0xfc8689c8. AlphaServer 1000/1000A AlphaServer 1000A 5/500, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1BWX OSF PAL rev: 0x1000600020117 real memory = 266371072 (254 MB) avail memory = 250863616 (239 MB) cia0: 2117x Core Logic chipset cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21DWEN,BWEN pcib0: 2117x PCI host bus adapter on cia0 pci0: PCI bus on pcib0 eisab0: PCI-EISA bridge at device 7.0 on pci0 halted CPU 0 halt code = 7 machine check while in PAL mode PC = 18100 Any idea what gives? Sounds like an SRM problem or EISA configuration problem. Normaly the bus and then system board should be probed at this point. We never used EISA on alpha before - EISA bridge support was only conditionalisized on pci. I tested localy on an AS4100 system: eisab0: PCI-EISA bridge at device 1.0 on pci1 eisa0: EISA bus on eisab0 mainboard0: DEC6400 (System Board) on eisa0 slot 0 isa0: ISA bus on eisab0 What says show config and show device? In case something is wrong with your eisa setup. Eisa configuration has to be done via alphabios. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 07:02:09PM +0200, Bernd Walter wrote: eisab0: PCI-EISA bridge at device 7.0 on pci0 halted CPU 0 halt code = 7 machine check while in PAL mode PC = 18100 Any idea what gives? Sounds like an SRM problem or EISA configuration problem. Normaly the bus and then system board should be probed at this point. We never used EISA on alpha before - EISA bridge support was only conditionalisized on pci. Which triggers me: did you run the ECU? A copy is at: ftp://ftp.tcja.nl/pub/wilko/alpha In case something is wrong with your eisa setup. Eisa configuration has to be done via alphabios. Do 'runecu' from the SRM console and it should work. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 05:49:15PM +0100, Mark Murray wrote: Wilko Bulte writes: GENERIC kernel also has above error. Remove eisa, and the boot goes straight to panic (no clock). That is because your clock sits behind eisa I think. ticso recently posted some days ago that eisa is now mandatory on alpha. I did not follow in detail to be honest. Check the archives. Well, that's left me hosed :-(. I looked through current@ and alpha@ (briefly) and saw nothing obvious. What should I be looking for? I think cvs-all@ would be more appropriate. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
