Date: Tue, 14 Jan 2003 11:39:29 -0700 From: mki@03cbd642.mozone.net To: "Brian J. McGovern" <bmcgover@cisco.com> Cc: qa@FreeBSD.ORG, bmcgover@bmcgover-pc.cisco.com Subject: Re: can't install anything higher than 4.5-R on Gigabyte SR101 Message-ID: <20030114183929.GJ17839@cyclonus.mozone.net> In-Reply-To: <200301141423.h0EENlWN024133@bmcgover-pc.cisco.com> References: <20030114073226.GI17839@cyclonus.mozone.net> <200301141423.h0EENlWN024133@bmcgover-pc.cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 14, 2003 at 09:23:47AM -0500, Brian J. McGovern wrote:
> Are these on-motherboard controllers, or PCI cards? I have the 100s, the
> 133s, and the TX2s all running FreeBSD as PCI cards with no problems. I'm not
> sure of the chipsets involved, though.
These are onboard controllers. You can probably find the chipset via
pciconf -l -v. I believe the one on the gigabytes has oem id 0x0d30105a.
The output from pciconf should tell you the respective chip ids for yours.
It is feasible that the problem we're seeing is specific to this chipset,
or specific to the fact that they are onboard controllers.
> >From the looks of the output, this may be a bus and/or drive problem. I've
> attached the output of one of my systems that runs the 133 RAID adapter. I have
> a not-yet-used system running one of the TX2 cards. I'll try to see if I can
> get the output for you today, if you're interested.
Hmm, i believe the problem may be specific to the FastTrack 100s
identified by the following pciconf. Also, as you saw from the dmesg
output from my previous message, the controllers are found just fine, it
is only when the first actual block read occurs in order to mount the
array/drives that the thing times out.
atapci1@pci0:16:0: class=0x010400 card=0x4d39105a chip=0x0d30105a rev=0x02 hdr=0x00
vendor = 'Promise Technology'
device = 'PDC20265 FastTrak100 Lite/Ultra100 EIDE Controller'
class = mass storage
subclass = RAID
> Just out of curiousity, have you checked the cables, gotten the orientation
> right, checked the master/slave jumpers, and zero'ed the drives to make sure
> they're healthy?
We've got over 15 gigabyte sr101s, *all* produce identical results after
either cvsup/makeupdating or trying to boot via any kern/mfsroot floppy
which is over 4.5-RELEASE. So I seriously doubt every one of them has
bad cables/orientation/masterslave jumpering issues, considering that
everything continues to work flawlessly as long as we use a kernel release
that does not contain the new ata code (which was introduced in 4.5-STABLE).
> Anyhow, here is the output of my 4.7 system, just so you can see that the
> controllers are recognized and usable :)
Hmm, this one was with the TX adapter. Do you have something with the
standard FastTrak100 ? Also, if you can check the chipset id etc via
pciconf, that'd be helpful.
Thanks.
-mohan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030114183929.GJ17839>