It seems Zwane Mwaikambo wrote:
> On Sun, 2 Dec 2001, Greg Lehey wrote:
>
> > Note that there are other chips out there which return the same PCI
> > information but which appear to be capable of ATA 100. I recently
> > gave a patch to Richard Sharpe (copied) which he says was able to get
> > hi
On Sun, 2 Dec 2001, Greg Lehey wrote:
> Note that there are other chips out there which return the same PCI
> information but which appear to be capable of ATA 100. I recently
> gave a patch to Richard Sharpe (copied) which he says was able to get
> his "SiS 5591" to run at ATA 100. I'm still w
It seems Richard Sharpe wrote:
> Attached is the patch I am using, which is based on what Greg gave me.
> It tries UDMA5 first, and steps down ...
The following patch is bogus, it doesn't set the chip to the prober
mode (always sets it to UDMA2), it just set the disk, this wont
work guys...
I
On Sunday, 2 December 2001 at 17:53:37 +1030, Richard Sharpe wrote:
> Greg Lehey wrote:
>> On Saturday, 1 December 2001 at 13:05:53 +0100, Søren Schmidt wrote:
>>
>>> It seems Zwane Mwaikambo wrote:
>>>
Hi,
I've got a box which boots up with UDMA33 but during the boot
sequence
Greg Lehey wrote:
> On Saturday, 1 December 2001 at 13:05:53 +0100, Søren Schmidt wrote:
>
>>It seems Zwane Mwaikambo wrote:
>>
>>>Hi,
>>> I've got a box which boots up with UDMA33 but during the boot
>>>sequence gets write problems and ends up disabling it and i presume
>>>falling back to
Had to go home to get the messages. Whilst i was there i examined the
verbose boot and pinpointed the DMA problem to the PIO cdrom i have (i
thought it was a UDMA one). Removing that from the same cable fixed the
DMA problem. Thanks for your time. But hopefully this might still help you
with my dr
Hi,
I've got a box which boots up with UDMA33 but during the boot
sequence gets write problems and ends up disabling it and i presume
falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have
had no problems running it at UDMA33.
Host: SiS 5591 (revision?)
Disk: Seagate 3.2G
On Sat, 1 Dec 2001, Søren Schmidt wrote:
> Ohhh, I need alot more info before I can tell whats going on..
> I need at least the dmesg from a verbosely booted system and
> also a pciconf -l to tell what chips you have.
Ok i can get the pciconf but how do i set the bootverbose flag?
Thanks.
Zwan
It seems Zwane Mwaikambo wrote:
> On Sat, 1 Dec 2001, Søren Schmidt wrote:
>
> > Ohhh, I need alot more info before I can tell whats going on..
> > I need at least the dmesg from a verbosely booted system and
> > also a pciconf -l to tell what chips you have.
>
> Ok i can get the pciconf but how
It seems Zwane Mwaikambo wrote:
> Hi,
> I've got a box which boots up with UDMA33 but during the boot
> sequence gets write problems and ends up disabling it and i presume
> falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have
> had no problems running it at UDMA33.
>
> H
10 matches
Mail list logo