Bug 17642

I can't reproduce this on any of our alpha machines; can you tell me a
bit more about the configuration?

On Tue, 28 Mar 2000, Jordan K. Hubbard wrote:

> I can't reproduce this on any of our alpha machines; can you tell me a
> bit more about the configuration?
> 
Sure -- I actually realized after I hit the send button that my hardware
configuration wasn't specified:

AlphaPC164 366MHz, 128MB RAM, SRM v. 5.5 (I think -- I upgraded several
months ago with the firmware CD included with Tru64 5.0).  The system has
2 IDE disks on ata0, the master has NT, the slave has Redhat 6.1 -- these
disks are seen by SRM, ata1 has a CD-ROM drive, not seen by SRM.  I put an
ELSA Gloria Synergy video card in the system.  It has a SCSI/Ethernet PCI
combo card that was originally in an AlphaStation 600 5/266.  The combo
card has 2 Qlogic ISP 1020 UW SCSI channels and a DEC 21040-AA 10MB
ethernet.  The card has a 21050 bridge (?) chip on it.  On SCSI channel A
I have an IBM 18GB UW disk and on SCSI channel B I have a Toshiba SCSI
CD-ROM.  This card works with Linux, Tru64 and OpenVMS (I haven't tried
NetBSD or switched to ARC and tried NT). 

If I try to boot FreeBSD either from CD-ROM or floppies, it will give me a
machine check panic when it queries the SCSI controllers.  I had posted
this to the FreeBSD/alpha group when trying to run with the release
candidate and I ended up loaning the card to Matthew Jacob.  He told me he
got it to work with his AlphaPC164 system and that I needed to either
interrupt the boot after the kernel and mfsroot load and give the boot
loader: set isp_mem_map=0xff    or else build a custom kernel with:
SCSI_ISP_PREFER_MEM_MAP=1

I obviously can't build a kernel if I can't install.  If I interrupt the
boot and give the boot loader the set isp_mem_map=0xff,  it will get past
the PCI device probe when it hits the SCSI controllers and it looks like
it correctly identifies the system hardware but come to think of it, I
never recall it reporting the devices on the SCSI channels -- it gets to
the "waiting 15 seconds for SCSI devices to settle" and then the screen
flashes to the red installation background and it immediately gives me the
going nowhere can't find my init message and reboots.

But I guess the installation is supposed to find a memory filesystem and
so it shouldn't matter initially whether or not there are devices on the
SCSI channels.  It sounds to me like it can't find the memory filesystem.
It certainly reports the ethernet, both scsi channels, both ide channels,
the 2 ide disks and the ide cdrom.  I also think I tried to boot from
floppies with the 4.0 CD in the IDE cdrom drive and still got the panic
and reboot.

Dirk

Dirk, uh, was this the board I borrowed from you? It certainly did work for me
when I did the isp_mem_map=0xff and it saw disks and I booted what was very
close to the FreeBSD-4.0 kernel. No- I didn't boot the INSTALL kernel- it
wasn't readily available to me at the time.

I have the same basic system. Dirk- I'll clone you a disk to get you going if
you like- I'm really not quite sure what the problem here is.


(I also offered you 

On Wed, 29 Mar 2000, Dirk Kleinhesselink wrote:

> The following reply was made to PR alpha/17642; it has been noted by GNATS.
> 
> From: Dirk Kleinhesselink <dkleinh@phy.ucsf.EDU>
> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
> Cc: freebsd-gnats-submit@FreeBSD.ORG
> Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init 
> Date: Wed, 29 Mar 2000 09:01:09 -0800 (PST)
> 
>  On Tue, 28 Mar 2000, Jordan K. Hubbard wrote:
>  
>  > I can't reproduce this on any of our alpha machines; can you tell me a
>  > bit more about the configuration?
>  > 
>  Sure -- I actually realized after I hit the send button that my hardware
>  configuration wasn't specified:
>  
>  AlphaPC164 366MHz, 128MB RAM, SRM v. 5.5 (I think -- I upgraded several
>  months ago with the firmware CD included with Tru64 5.0).  The system has
>  2 IDE disks on ata0, the master has NT, the slave has Redhat 6.1 -- these
>  disks are seen by SRM, ata1 has a CD-ROM drive, not seen by SRM.  I put an
>  ELSA Gloria Synergy video card in the system.  It has a SCSI/Ethernet PCI
>  combo card that was originally in an AlphaStation 600 5/266.  The combo
>  card has 2 Qlogic ISP 1020 UW SCSI channels and a DEC 21040-AA 10MB
>  ethernet.  The card has a 21050 bridge (?) chip on it.  On SCSI channel A
>  I have an IBM 18GB UW disk and on SCSI channel B I have a Toshiba SCSI
>  CD-ROM.  This card works with Linux, Tru64 and OpenVMS (I haven't tried
>  NetBSD or switched to ARC and tried NT). 
>  
>  If I try to boot FreeBSD either from CD-ROM or floppies, it will give me a
>  machine check panic when it queries the SCSI controllers.  I had posted
>  this to the FreeBSD/alpha group when trying to run with the release
>  candidate and I ended up loaning the card to Matthew Jacob.  He told me he
>  got it to work with his AlphaPC164 system and that I needed to either
>  interrupt the boot after the kernel and mfsroot load and give the boot
>  loader: set isp_mem_map=0xff    or else build a custom kernel with:
>  SCSI_ISP_PREFER_MEM_MAP=1
>  
>  I obviously can't build a kernel if I can't install.  If I interrupt the
>  boot and give the boot loader the set isp_mem_map=0xff,  it will get past
>  the PCI device probe when it hits the SCSI controllers and it looks like
>  it correctly identifies the system hardware but come to think of it, I
>  never recall it reporting the devices on the SCSI channels -- it gets to
>  the "waiting 15 seconds for SCSI devices to settle" and then the screen
>  flashes to the red installation background and it immediately gives me the
>  going nowhere can't find my init message and reboots.
>  
>  But I guess the installation is supposed to find a memory filesystem and
>  so it shouldn't matter initially whether or not there are devices on the
>  SCSI channels.  It sounds to me like it can't find the memory filesystem.
>  It certainly reports the ethernet, both scsi channels, both ide channels,
>  the 2 ide disks and the ide cdrom.  I also think I tried to boot from
>  floppies with the 4.0 CD in the IDE cdrom drive and still got the panic
>  and reboot.
>  
>  Dirk
>  
>  
>  
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>

A similar (?) problem was seen by people who had a DUNIX/Tru64
disk attached to the system. The problem went away after disconnecting
that disk from the SCSI bus. 

Might be worth a try if you have such a disk on your system.
-- 
Wilko Bulte  	 	http://www.freebsd.org  "Do, or do not. There is no try"
wilko@freebsd.org	http://www.nlfug.nl	- Yoda - The Empire Strikes Back

Received the following information <see quote>. For the time being 
I've commited a warning to both 4.x and -current in INSTALL.TXT for the
alpha. At least people have an opportunity to -know- what hurts them
(assuming they read docs ;-)

Wilko


<quote>
I had seen those posts and as a matter of fact, last week I wiped all my
disks of BSD disk labels and was able to install.  I don't know where
this
information should be put, but I think it definitely needs to be
documented until it is fixed.  The problem seems to be the existence of
a
BSD disklabel on other disks, the disklabel can be from Linux, NetBSD,
OpenBSD, Digital/Tru64 Unix - doesn't matter -- the FreeBSD install will
give the "can't find init" error.  I installed NT and created NTFS
partitions on my disks and then was able to install FreeBSD/alpha.
     
Dirk
</quote?>
-- 
Wilko Bulte  	 	http://www.freebsd.org  "Do, or do not. There is no try"
wilko@freebsd.org	http://www.nlfug.nl	- Yoda - The Empire Strikes Back

Comment 6 Matt Jacob 2001-10-02 02:58:00 UTC

State Changed
From-To: open->feedback

We believe that this was fixed by 4.4. Can you try to install again with 
FreeBSD 4.4?

Comment 7 Giorgos Keramidas 2002-08-26 04:05:37 UTC

State Changed
From-To: feedback->closed

Feedback timeout.