> For right now, I think the best thing to do if you want to run
> woody is install the potato release, (just the basics) and then
> do a apt-get dist-upgrade after changing you're
> /etc/apt/sources.list.
Yeah, that's what I am doing now, but point of using the woody install
disks was because D
> I assume you are suing current cvs?
No, I'm using the disks marked as current (April 11). I assumed
these were the ones that Dale was asking us to test. If not, is
there a HOWTO on how to make boot floppies from your CVS
server?
If there's to be a large scale testing of these disks by the te
Uhm, has *anyone* succeeded to install a machine using the woody boot
floppies? So far, I've just met with utter failure.
Every time I try to install the base system over the network the
machine prints "trying to get package" messages for a whole bunch of
packages, and then returns me to the me
> LSI Logic Symbios pci scsi bios.
>
> I think that is what you are looking for.
Not really, no. I wanted a chip number.
www.tekram.com, flip, flip, flip.
It's a Symbos 53C1010, which appears to be more or less compatible with the
53C8xx chips used in the earlier tekram cards. At least,
> That is not right. Please understand, I cannot see the hard drives
> because the scsi controler is not being loaded on boot. That means that
> Configure Device Driver Modules will not work. I have no drives at this
> time.
What chip is on that card? The DC390W/U/F use Symbios 53c8xx chips w
I haven't tried the latest disks yet, but...
> I have a problem. I need to reconize the tekram scsi controler card
Which Tekram scsi controller? (There's more than one incompatible kind.)
> I just tried your boot disks
> and I still cannot see the drives.
Which module did you insert? What
6 matches
Mail list logo
