I got the same behavior on my SS20 with le0 and eth0. I wasn't able to change which one appeared at eth0 without getting some unusual routing behavior that I didn't have time to troubleshoot. In the end I didn't fight it & just put it back.
Rolf is right that you may be able to recompile the kernel with the modules for second SCSI adapter built into the kernel instead of configured as modules. Then they'd identify upon boot. Otherwise you have to insmod them in to get that adapter online. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 28, 2002 3:41 PM Subject: RE: [suse-sparc] External SCSI disks. > Hi, > IMHO le0 is initialiy always the primary eth0. The hme will be > eth1, same on the internal/sbus SCSI. RH may use more prelinked > modules at the Kernels but you can install them as additional > Modules later (initrd) or rebuild the Kernel with static SCSI > modules. But take a look at the openprom for listed/bootable > devices too. Sometimes small initstrings are used by some > Sparc-Linux-Distributions as a content of NVRAM to boot. > SuSE don't use this and it may cause trouble on booting. > > Rolf > > -- > [EOF] > > > -----Original Message----- > > From: Joseph Gordon [mailto:joseph.gordon@;bms.com] > > Sent: Monday, October 28, 2002 1:38 PM > > To: Nick Thompson > > Cc: [EMAIL PROTECTED] > > Subject: Re: [suse-sparc] External SCSI disks. > > > > > > I replaced the internal 2 GB drive with a 9 GB and did a full install, > > including source, just so I would have all available resources > > from the CD's on > > disk. > > The kernel does not see the external devices during boot from > > the CDROM. (But > > the Red Hat install does). I also discovered another anomally > > late last week > > with the network interfaces. Yast2 saw le0 and the hme which is > > part of SCSI > > card that also has a connector. I configured the hme as the > > primary interface > > but couldn't get out to the network. On a hunch I plugged the > > network cable into > > the le0 interface and voila! I was connected. > > Does Suse have anything that's equivalent to Sun's drvconfig or > > devfsadm? > > > > Nick Thompson wrote: > > > > > Are the external disks identified by the Kernel during boot > > from the CD-ROM? > > > > > > Try installing to small partition on the internal disk & then see if the > > > qlogic board can be troubleshot with an installed OS in place > > (so you can > > > send us the dmesg and other log files!) > > > > > > Is there a HOW-TO anywhere about the qlogic module? > > > > > > ----- Original Message ----- > > > From: "Joseph Gordon" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Thursday, October 24, 2002 7:52 AM > > > Subject: [suse-sparc] External SCSI disks. > > > > > > > I have an Ultra 1 with one internal 2 GB disk, 2, 4 GB > > external disks, > > > and a > > > > Multi-Pak. From the Multi-Pak I can boot Solaris 6, 8, or 9. > > > > When installing Suse 7.3 (2.4.14) I can't get linux to recognize the > > > external > > > > disks. I have the sources installed and when I try to > > modprobe qlogicisp > > > it > > > > complains about a license then exits. None of the FAQ's or > > HOWTO's I've > > > read > > > > address this issue either specifically or indirectly. Does > > anyone have any > > > > suggestions? > > > > > > > > PS Red Hat installs with no complaint and sees all the disks, but I'd > > > rather run > > > > > > > > Suse. > > > > > > > > -- > > > > Joe Gordon email: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > -- > > Joe Gordon email: [EMAIL PROTECTED] > > Bristol-Myers Squibb phone: 609.818.3909 > > PRI - Informatics Div. fax: 609.818.7693 > > Hopewell, NJ 08534 > > > > > > > > -- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
