oard, and disabled everything but USB.
No, they have a separate USB chip, but it has the same PCI ID as the
builtin silicon in the southbridge.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
everything but USB.
No, they have a separate USB chip, but it has the same PCI ID as the
builtin silicon in the southbridge.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
exactly 18",
not longer, not shorter.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
not longer, not shorter.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
aram -k /dev/hda
> keepsettings = 0 (off)
>
> Is this normal?
This only relates to a ide bus reset in case of a failure, not system reset.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
his normal?
This only relates to a ide bus reset in case of a failure, not system reset.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
ecommended to set it with hdparm?
It does:
via82cxxx.c, line 536: hwif->drives[i].io_32bit = 1;
Actually this seems to be required for correct operation in PIO modes.
Anyway, it doesn't have an effect if DMA/UDMA modes are used -
BusMastering is always 32bit.
--
Vojtech Pavlik
SuSE Labs
-
T
:
via82cxxx.c, line 536: hwif-drives[i].io_32bit = 1;
Actually this seems to be required for correct operation in PIO modes.
Anyway, it doesn't have an effect if DMA/UDMA modes are used -
BusMastering is always 32bit.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line
-d1 -X69 /dev/hda => I get 36MB/s
>
> Then I tried kernel 2.4.1. I issued exactly the same hdparm command.
> i got in syslog the message: "ide0: Speed warnings UDMA 3/4/5 is not
> functional"!
>
> What is the problem?
The 80-wire cable was not detected. Try this driver
Then I tried kernel 2.4.1. I issued exactly the same hdparm command.
i got in syslog the message: "ide0: Speed warnings UDMA 3/4/5 is not
functional"!
What is the problem?
The 80-wire cable was not detected. Try this driver ...
--
Vojtech Pavlik
SuSE Labs
#ifndef _IDE_TIMING
On Wed, Feb 21, 2001 at 11:05:33AM -0300, Rogerio Brito wrote:
> On Feb 21 2001, Vojtech Pavlik wrote:
> > On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
> > > Ok, can I still use -u1 -k1 -c1 on the drives or is it even
> > > necessary anymore.
> >
On Wed, Feb 21, 2001 at 11:05:33AM -0300, Rogerio Brito wrote:
On Feb 21 2001, Vojtech Pavlik wrote:
On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
Ok, can I still use -u1 -k1 -c1 on the drives or is it even
necessary anymore.
If you enable automatic DMA in the kernel
On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
> On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote:
> > On Tue, Feb 20, 2001 at 03:59:27PM -0800, Shane Wegner wrote:
> >
> > > > You wanted my VIA driver for 2.2. Here is a patch that brings
DMA instead.
Hmm, I'll have to look into this anyway - many users seem to do that and
it isn't as harmless as it looks (it worked by pure luck with the
previous version).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
ives (hdparm -i ...)?
I can send you the VIA latest drivers if you are interested in trying
whether they'll help.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
ing it. Because of that, it's superfluous. And the code relies on
the compiler to optimize it out.
If written like:
#ifndef CONFIG_IDEDMA_IVB
#define IDE_UDMA_MASK 0x4000
#else
#define IDE_UDMA_MASK 0x6000
#endif /* CONFIG_IDEDMA_IVB */
byte eighty_ninty_three (ide_drive_t *drive)
{
Hi Andre!
You wanted my VIA driver for 2.2. Here is a patch that brings the very
latest 4.2 driver to the 2.2 kernel. The patch is against the
2.2.19-pre13 kernel plus yours 1221 ide patch.
Enjoy!
--
Vojtech Pavlik
SuSE Labs
via-4.2x-for-2.2.19-pre13-ide1221.diff.bz2
Hi Andre!
You wanted my VIA driver for 2.2. Here is a patch that brings the very
latest 4.2 driver to the 2.2 kernel. The patch is against the
2.2.19-pre13 kernel plus yours 1221 ide patch.
Enjoy!
--
Vojtech Pavlik
SuSE Labs
via-4.2x-for-2.2.19-pre13-ide1221.diff.bz2
-hw_config IDE_UDMA_MASK);
}
it'd be probably somewhat clearer.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please r
if you are interested in trying
whether they'll help.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
- many users seem to do that and
it isn't as harmless as it looks (it worked by pure luck with the
previous version).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote:
On Tue, Feb 20, 2001 at 03:59:27PM -0800, Shane Wegner wrote:
You wanted my VIA driver for 2.2. Here is a patch that brings the very
latest 4.2 driver
ack to a hardcoded 33.
>
> What should I do next?
Are you willing to do some experiments? I suppose the 686b is somewhat
different than the other chips (I tested it on 686a and 586b).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
vers. Other non IDE devices, such as matroxfb,
> > may be interested in PCI speed too.
>
> that file will most likely go away in 2.5
Good, it should.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
.
that file will most likely go away in 2.5
Good, it should.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
the 686b is somewhat
different than the other chips (I tested it on 686a and 586b).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
dea?
Since version 2.30 of the VIA driver (2.4.2-pre2), the driver leaves
prefetch as is set by BIOS. It seems that ATAPI devices need this set to
off at least on some of the VIA chips.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
needed. However, it still might be
worth to pass the PCI speed to other drivers ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
speed measuring code needs help from the chipset
itself, so it isn't possible to implement in generic code. Maybe a
callback could be added to the chipset-specific drivers, though ...
I do have some plans with ide-pci.c, so ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
numbers to 4 and 2.
Could anyone with these chipsets check these drivers if they detect the
PCI clock correctly on their systems?
Thanks.
Just untar the attached file into drivers/ide and recompile.
--
Vojtech Pavlik
SuSE Labs
amd-2.0+via-4.0.tar.bz2
numbers to 4 and 2.
Could anyone with these chipsets check these drivers if they detect the
PCI clock correctly on their systems?
Thanks.
Just untar the attached file into drivers/ide and recompile.
--
Vojtech Pavlik
SuSE Labs
amd-2.0+via-4.0.tar.bz2
the chipset-specific drivers, though ...
I do have some plans with ide-pci.c, so ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
to other drivers ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
), the driver leaves
prefetch as is set by BIOS. It seems that ATAPI devices need this set to
off at least on some of the VIA chips.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please re
ong timeout = jiffies + ((HZ + 19)/20) + 1;
> > > while (0 < (signed long)(timeout - jiffies));
> >
> > On that bit we agree.
>
> What do you want fixed?
> Send a patch and lets try it
How about this?
--
Vojtech Pavlik
SuSE Labs
--- pdc202xx.c.old Fri Jul 2
long)(timeout - jiffies));
On that bit we agree.
What do you want fixed?
Send a patch and lets try it
How about this?
--
Vojtech Pavlik
SuSE Labs
--- pdc202xx.c.old Fri Jul 28 21:08:30 2000
+++ pdc202xx.c Fri Feb 9 09:08:55 2001
@@ -747,14 +747,11 @@
{
unsigned long
= so that the Active/Recover
timings are correct. If KT7A doesn't work with UDMA at high PCI clocks
*even when* idebus= is correct would mean that the UDMA timing is in
1/(PCICLK*3) units instead of units of 10ns.
Anyone help us?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: s
686b |33 |1 2 1 | 10 | 6T=33.3 4T=66.6 2T=100.0
... that is, if the 686b indeed has a 100MHz clock source. If not, then
in the case of 25 MHz, T would be 13.3ns. If you can verify this, it'd
be nice.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from
... that is, if the 686b indeed has a 100MHz clock source. If not, then
in the case of 25 MHz, T would be 13.3ns. If you can verify this, it'd
be nice.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
that the UDMA timing is in
1/(PCICLK*3) units instead of units of 10ns.
Anyone help us?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
uctions are too fast. The VIA driver on 2.2 doesn't
> correctly program the PCI card, so you don't see weird behavior running 2.2
> with a faster PCI clock.
>
> (Note: 1.14 * 33 = 37.6 PCI Clk)
It's 38:
114 / 3 == 38 == 1.14 * 33.33
But definitely it isn't 34 or the default 33.
ia) data for both
so that I can compare them?
If I find any differences, I'll know what the bug is.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
roblems i've been talking about
Btw, if you run your FSB at 114 MHz, you need to pass 'idebus=38' to the
IDE driver so that it knows your PCI bus runs at 38 MHz (3x38 = 114).
Otherwise you'll get incorrect timing etc.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line &quo
iveness than 2.4.x . Could this be because of via problems on
> the 2.4.x kernel or is it 2.4.x arch ?
No, probably not.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Jan 30, 2001 at 11:55:25PM -0800, David Raufeisen wrote:
> On Wednesday, 31 January 2001, at 08:36:42 (+0100),
> Vojtech Pavlik wrote:
>
> > Hi!
> >
> > 1) You don't seem to have any drives on the VIA controller. If this is
> > true, I don't think thi
On Tue, Jan 30, 2001 at 11:55:25PM -0800, David Raufeisen wrote:
On Wednesday, 31 January 2001, at 08:36:42 (+0100),
Vojtech Pavlik wrote:
Hi!
1) You don't seem to have any drives on the VIA controller. If this is
true, I don't think this can be a VIA IDE driver problem.
Hi
this be because of via problems on
the 2.4.x kernel or is it 2.4.x arch ?
No, probably not.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
to pass 'idebus=38' to the
IDE driver so that it knows your PCI bus runs at 38 MHz (3x38 = 114).
Otherwise you'll get incorrect timing etc.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECT
what the bug is.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
with a faster PCI clock.
(Note: 1.14 * 33 = 37.6 PCI Clk)
It's 38:
114 / 3 == 38 == 1.14 * 33.33
But definitely it isn't 34 or the default 33.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECT
related anyhow.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Jan 30, 2001 at 10:48:26AM +0100, Vojtech Pavlik wrote:
> The current VIA driver in 2.4.0 is version 2.1e. I wouldn't push a new
> version, but VIA has released the vt82c686b chip and it's causing a lot
> of trouble.
>
> The 2.1e version can't recognize it from the vt82
be getting much less
mails about non-working 686b's.
It's against 2.4.1-pre12, but should patch cleanly against pre11 or
anything later.
Thanks.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Mon, Jan 29, 2001 at 12:49:16PM -0800, Tim Moore wrote:
> Is via82cxxx.c v3.17 a 2.4.x only patch or did I miss something else?
Yes, it's currently 2.4.x only.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Mon, Jan 29, 2001 at 12:49:16PM -0800, Tim Moore wrote:
Is via82cxxx.c v3.17 a 2.4.x only patch or did I miss something else?
Yes, it's currently 2.4.x only.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Tue, Jan 30, 2001 at 10:48:26AM +0100, Vojtech Pavlik wrote:
The current VIA driver in 2.4.0 is version 2.1e. I wouldn't push a new
version, but VIA has released the vt82c686b chip and it's causing a lot
of trouble.
The 2.1e version can't recognize it from the vt82c686a, the only
be getting much less
mails about non-working 686b's.
It's against 2.4.1-pre12, but should patch cleanly against pre11 or
anything later.
Thanks.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
related anyhow.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
ng here that I can not do a damn thing with until I
> stop these blasted kernel deaths! (Yeah I'm pissed, but at the situation
> not at the kernel or anyone involved with the VIA stuff. Please don't take
> it that way.)
Sure, I'll need a more precise description, though.
--
Vojtech P
ming should be always the same, independent on the PCI
clock. However, it is programmed in terms of PCI cycles, so yes, the
only thing my driver does is exactly this compensation for the PCI speed
so that the IDE timing stays constant.
Yes, my driver is doing exactly what you say.
--
Vojtech
y thing my driver does is exactly this compensation for the PCI speed
so that the IDE timing stays constant.
Yes, my driver is doing exactly what you say.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
pissed, but at the situation
not at the kernel or anyone involved with the VIA stuff. Please don't take
it that way.)
Sure, I'll need a more precise description, though.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
83 MHz FSB, you'll get 41.5 MHz
or 27.6 MHz PCI. And there are chips speced for 75 and 83 MHz FSB's -
Cyrix 6x86MX etc.
No way to get 33 here, if you *don't* want to over/under-clock the CPU.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-
hwif->autodma = 1;
> +#endif /* CONFIG_IDEDMA_AUTO */
> }
> #endif /* CONFIG_BLK_DEV_IDEDMA */
> }
>
Linus, if you haven't applied my disable-dma-in-all-cases patch I've
sent you earlier, please do apply this one - it's correct and should be
there. It conflicts with t
}
#endif /* CONFIG_BLK_DEV_IDEDMA */
}
Linus, if you haven't applied my disable-dma-in-all-cases patch I've
sent you earlier, please do apply this one - it's correct and should be
there. It conflicts with the older one, obviously.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this
or 27.6 MHz PCI. And there are chips speced for 75 and 83 MHz FSB's -
Cyrix 6x86MX etc.
No way to get 33 here, if you *don't* want to over/under-clock the CPU.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Sun, Jan 21, 2001 at 01:42:41PM +0100, Mike Galbraith wrote:
> On Sun, 21 Jan 2001, Vojtech Pavlik wrote:
>
> > On Sat, Jan 20, 2001 at 02:57:07PM -0800, Andre Hedrick wrote:
> >
> > > chipset ---\
> > > |
> > >
> fs). I did disable UDMA everywhere and still saw it happen, this problem is
> not present in older 2.4.0-test kernels so it's something in the late
> pre-release stage and into the release stage.
Do you have the via driver compiled in? If yes, try without, if no, try
with it ...
--
Vojte
64, LBA=yes, LBAsects=16514064
> tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1
> mword2
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
> UDMA modes: mode0 mode1 *mode2
>
> ----------
>
> /dev/hda:
> Timing buffered disk reads: 64 MB in 6.
my setup as possible wish to
> help me with this? (I'm not discounting the mismatched setups, I just want
> a baseline to go from. If someone with my setup is NOT ahving trouble then
> I may need to look at something different).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
tly when they have a
UDMA100 HPT370 onboard)?
... btw, if we ever implement UDMA slowdown code based on CRC errors, we
should differentiate between CRC errors on read and CRC errors on write,
because each are caused by a different problem ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from
wdown code based on CRC errors, we
should differentiate between CRC errors on read and CRC errors on write,
because each are caused by a different problem ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
to look at something different).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
via driver compiled in? If yes, try without, if no, try
with it ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
/sec
I don't suppose the fact that my hdparm is oldish (3.6 I think) have
any bearing on this?
No, 3.6 is OK I think.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please re
On Sun, Jan 21, 2001 at 01:42:41PM +0100, Mike Galbraith wrote:
On Sun, 21 Jan 2001, Vojtech Pavlik wrote:
On Sat, Jan 20, 2001 at 02:57:07PM -0800, Andre Hedrick wrote:
chipset ---\
|
\-IDC-header
chipset
attachment to
> Vojtech Pavlik's mail which were placed in drivers/ide directory -
> ERRORS.
> Alan
Wonderful! A case where I can compare a working setup with a nonworking
one! :) Could you please send me the usual stuff (dmesg, lspci -vvxxx,
cat /proc/ide/via, hdparm -i /dev/hd*,
send me the usual stuff (dmesg, lspci -vvxxx,
cat /proc/ide/via, hdparm -i /dev/hd*, hdparm -t /dev/hd*) for both the
2.2 case and the 2.4.0+VIA-latest case? That'll allow me to find the
differences and possibly fix the new driver.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send
foolproof with respect to the 'idebus'
setting, which is quite a misnomer, btw.
Care to try them out?
Andre, you're the only one I know of having the 766 chip, so please test
this driver, I'd like to know if it really works ... thanks.
--
Vojtech Pavlik
SuSE Labs
via-amd-ide.tar.bz2
nd 2.4.1-pre7). I find it odd
> that if it isn't a kernel-related problem, that it's only manifesting itself
> under 2.4.
>
> I'm running a slot A athlon on an abit KA7-100.
My bet is ACPI/powermanagement messing with it ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
it KA7-100.
My bet is ACPI/powermanagement messing with it ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
foolproof with respect to the 'idebus'
setting, which is quite a misnomer, btw.
Care to try them out?
Andre, you're the only one I know of having the 766 chip, so please test
this driver, I'd like to know if it really works ... thanks.
--
Vojtech Pavlik
SuSE Labs
via-amd-ide.tar.bz2
On Wed, Jan 17, 2001 at 11:53:36AM -0700, Terrence Martin wrote:
> Vojtech Pavlik wrote:
>
> > Hi!
> >
> > Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
> > driver, could you try with the 2.4.0 kernel if it fixes the behavior?
> &
then you can read it back and checksum the contents.
>
> It does destroy the content on the drive, this is no worse than a random
> "File System Corruption " because it absolutely destroys or corrupts the
> original content for testing purposes.
>
>
> On Wed, 17 J
at 0xea02 [0xea02].
> > Bus 0, device 10, function 0:
> > Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> > Medium devsel. IRQ 11. Master Capable. Latency=64. Min
> > Gnt=10.Max Lat=10.
> > I/O at 0xe000 [0xe001].
> > Non
001 at 02:38:00PM -, Chandler, Alan wrote:
> On Wed Jan 10 2001 - 06:45:24 EST Vojtech Pavlik <[EMAIL PROTECTED]> wrote
>
> >For all of you who had problems getting the VIA IDE driver to work
> >correctly on the 686b, here is a driver that should work with those
>
at 02:38:00PM -, Chandler, Alan wrote:
On Wed Jan 10 2001 - 06:45:24 EST Vojtech Pavlik [EMAIL PROTECTED] wrote
For all of you who had problems getting the VIA IDE driver to work
correctly on the 686b, here is a driver that should work with those
chips, even in UDMA 100 mode. I've
32 bit memory at 0xe600 [0xe608].
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Andre Hedrick
Linux ATA Development
--
Vojtech Pavlik
read it back and checksum the contents.
It does destroy the content on the drive, this is no worse than a random
"File System Corruption " because it absolutely destroys or corrupts the
original content for testing purposes.
On Wed, 17 Jan 2001, Vojtech Pavlik wrote:
Hi!
On Wed, Jan 17, 2001 at 11:53:36AM -0700, Terrence Martin wrote:
Vojtech Pavlik wrote:
Hi!
Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
driver, could you try with the 2.4.0 kernel if it fixes the behavior?
Hmm ok I will give it a try...this will have
ot;.
>
> Note that "hdparm -X34 -d1" enables old DMA, not UDMA. (The board was
> advertised as UDMA capable but it isn't AFAIK).
It should be able to do UDMA33.
Is the board still available for some testing?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: se
then that actually means 'working and
probably would work perfect with a shorter cable'.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Sun, Jan 14, 2001 at 09:45:09AM +0100, Tobias Ringstrom wrote:
> On Sun, 14 Jan 2001, Vojtech Pavlik wrote:
> > On Sat, Jan 13, 2001 at 11:36:13PM +0100, Tobias Ringstrom wrote:
> >
> > > I have now tried the SAMSUNG VG34323A disk with two other controllers at
> >
bly submit another
one that will allow to override the no-dma rule by a kernel command line
option, as Alan Cox suggested.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
K. When writing, the
controller provides the clock and for some reason the Samsung can't keep
up with the setting the driver selects for it. The question is why and
why the driver selects the incorrect (or just too tight?) value.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
masqueraded 598,
> > which identifies itself as 597, and a 686a southbridge. This got the
> > 2.2 ide driver completely confused, for example.
>
> Maybe the VIA IDE chipset support option should depend on PCI quirks now ?
No, in 2.4 the VIA IDE driver doesn't use this (northbrid
the incorrect (or just too tight?) value.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
.
Maybe the VIA IDE chipset support option should depend on PCI quirks now ?
No, in 2.4 the VIA IDE driver doesn't use this (northbridge) information
anymore.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
, as Alan Cox suggested.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Sun, Jan 14, 2001 at 09:45:09AM +0100, Tobias Ringstrom wrote:
On Sun, 14 Jan 2001, Vojtech Pavlik wrote:
On Sat, Jan 13, 2001 at 11:36:13PM +0100, Tobias Ringstrom wrote:
I have now tried the SAMSUNG VG34323A disk with two other controllers at
home (Promise ATA100 an VIA vt82c686a
801 - 900 of 1085 matches
Mail list logo
