On Wednesday 18 April 2001 14:39, Jens Axboe wrote:
Please send me strace info when reading/writing to the drive (or at
least attempting to), this looks very queer indeed.
Attached patch for 2.4.4-pre4 which fixes all known DVD-RAM ATAPI bugs.
Both pio and dma mode work fine here, using
Hi Jens,
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
---
Uniform CD-ROM driver Revision: 3.12
Unable to handle kernel NULL pointer dereference at virtual address
printing eip: ...
Oops:
...
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
This should fix it.
It boots now. But I still cannot read a DVD-RAM disk (same behavior
as before):
# strace dd of=/dev/null if=/dev/hdc bs=2k count=3
open("/dev/hdc",
On Thursday 19 April 2001 14:15, Jens Axboe wrote:
This is really strange, are you sure your drive is ok? Does mounting
dvd-rom and cd-rom's work fine?
OK. I'll check again with 2.4.4-pre4+patches:
(1) Mounting the SuSE DVD-ROM (-t iso9660) from /dev/hdc on /dvd and
reading from /dvd
On Thursday 19 April 2001 15:03, Jens Axboe wrote:
On Thu, Apr 19 2001, Stefan Jaschke wrote:
OK. I'll check again with 2.4.4-pre4+patches:
(1) Mounting the SuSE DVD-ROM (-t iso9660) from /dev/hdc on /dvd and
reading from /dvd works. Same for CD-ROMs. I don't have a formatted
DVD
On Friday 20 April 2001 00:49, J . A . Magallon wrote:
Hi,
Just built 2.4.3-ac10 and got an oops when booting. It tries to detect
the CD and gives the oops.
EIP; c01bfc7c cdrom_get_entry+1c/50 =
This appears to be a known problem. Jens Axboe sent a patch in a different
thread
On Wednesday 18 April 2001 20:40, Francois Romieu wrote:
Hello,
Oliver Teuber [EMAIL PROTECTED] écrit :
[...]
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev
06) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
00:07.0 ISA bridge: VIA
Hi,
it seems the epic100 driver broke between 2.4.2 and 2.4.3.
I reloaded the epic100 module with the parameter "debug=6".
Unfortunately, I cannot make much out of the log:
Apr 20 12:47:01 antares kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
[EMAIL PROTECTED]
Apr 20 12:47:01
2.4.2 2.4.3
VT82C595 ok fscked. (no mention of bios experience)
Oliver Teuber:
2.2.19 2.4.3-ac7
VT82C598 ok fscked
Romieu:
2.2.xx 2.4.[123]
82443BX ok ok
Stef
On Friday 20 April 2001 13:33, Jeff Garzik wrote:
Here's a suggestion to try: go through epic100.c and write 0x12
unconditionally to MIICfg register. Right now it is conditional: if
(dev-if_port...) out(0x12,ioaddr+MIICfg);
I changed all three such lines. Same behavior as before.
offtopic
On Friday 20 April 2001 12:25, Francois Romieu wrote:
What happen's if you compile 2.4.2 epic100 driver in a 2.4.3 tree (I) ?
I would really appreciate if you could give a look at (I).
I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles and works
without
problems.
This
On Friday 20 April 2001 16:33, Francois Romieu wrote:
Stefan Jaschke [EMAIL PROTECTED] ecrit :
I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles
and works without problems.
This gives me a workable solution :-)
Thanks for the info.
Now, why do you get so much
On Friday 20 April 2001 18:45, Francois Romieu wrote:
I assume nothing is overclocked or whatever
Nothing is overclocked.
Could you try this patch (more output during the loop):
Tried it. The (lengthy) log is attached.
The interrupt is triggered when the other side initiates a request.
eth0
Hi Jens,
I took some time to try to understand why "mke2fs -b 2048 /dev/hdc"
wants 500MB memory. Here is a first explanation:
# mke2fs -m 0 -n /dev/hdc
mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
On Saturday 21 April 2001 20:52, Tamas Nagy wrote:
extend the current file-system with an optional plug-in system, which
allows for file-system level encryption instead of file-level. This could
be used transparently for applications or even for file-system drivers.
This doesn't mean an
Judging from the thread started Jan 1, 2001, by Andre Hedrick,
I thought IDE DVD-RAM just works out of the box and got a
Toshiba SD-W2002.
Problem: /dev/hdc cannot be read or written to when the drive contains
DVD-RAM media. The behavior is the same for the stock 2.4.3 kernel
and the
On Tuesday 17 April 2001 18:45, Oliver Teuber wrote:
my smc epic100 card does not work with the device driver from
linux-2.4.3-ac7.
linux-2.2.19 works fine for me.
Same behavior here. Just want to add that the 2.4.0 kernel (SuSE 7.1) also
works fine.
Stefan
-
To unsubscribe from this list:
On Wednesday 18 April 2001 14:39, Jens Axboe wrote:
> Please send me strace info when reading/writing to the drive (or at
> least attempting to), this looks very queer indeed.
>
> Attached patch for 2.4.4-pre4 which fixes all known DVD-RAM ATAPI bugs.
> Both pio and dma mode work fine here,
Hi Jens,
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
---
Uniform CD-ROM driver Revision: 3.12
Unable to handle kernel NULL pointer dereference at virtual address
printing eip: ...
Oops:
...
> > I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
> > boot (just right after the IDE init) with
>
> This should fix it.
It boots now. But I still cannot read a DVD-RAM disk (same behavior
as before):
# strace dd of=/dev/null if=/dev/hdc bs=2k count=3
open("/dev/hdc",
On Thursday 19 April 2001 14:15, Jens Axboe wrote:
> This is really strange, are you sure your drive is ok? Does mounting
> dvd-rom and cd-rom's work fine?
OK. I'll check again with 2.4.4-pre4+patches:
(1) Mounting the SuSE DVD-ROM (-t iso9660) from /dev/hdc on /dvd and
reading from /dvd
On Thursday 19 April 2001 15:03, Jens Axboe wrote:
> On Thu, Apr 19 2001, Stefan Jaschke wrote:
> > OK. I'll check again with 2.4.4-pre4+patches:
> > (1) Mounting the SuSE DVD-ROM (-t iso9660) from /dev/hdc on /dvd and
> > reading from /dvd works. Same for CD-ROMs. I d
On Friday 20 April 2001 00:49, J . A . Magallon wrote:
> Hi,
>
> Just built 2.4.3-ac10 and got an oops when booting. It tries to detect
> the CD and gives the oops.
> >>EIP; c01bfc7c<=
This appears to be a known problem. Jens Axboe sent a patch in a different
thread ("SD-W2002 DVD-RAM")
On Wednesday 18 April 2001 20:40, Francois Romieu wrote:
> Hello,
>
> Oliver Teuber <[EMAIL PROTECTED]> écrit :
> [...]
>
> > 00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev
> > 06) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
> > 00:07.0 ISA
Hi,
it seems the epic100 driver broke between 2.4.2 and 2.4.3.
I reloaded the epic100 module with the parameter "debug=6".
Unfortunately, I cannot make much out of the log:
Apr 20 12:47:01 antares kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
<[EMAIL PROTECTED]>
Apr 20 12:47:01
niel Nofftz:
> 2.4.2 2.4.3
> VT82C595 ok fscked. (no mention of bios experience)
>
> Oliver Teuber:
> 2.2.19 2.4.3-ac7
> VT82C598 ok fscked
>
> Romieu:
> 2.2.xx 2.4.[1
On Friday 20 April 2001 13:33, Jeff Garzik wrote:
> Here's a suggestion to try: go through epic100.c and write 0x12
> unconditionally to MIICfg register. Right now it is conditional: if
> (dev->if_port...) out(0x12,ioaddr+MIICfg);
I changed all three such lines. Same behavior as before.
You
On Friday 20 April 2001 12:25, Francois Romieu wrote:
> What happen's if you compile 2.4.2 epic100 driver in a 2.4.3 tree (I) ?
> I would really appreciate if you could give a look at (I).
I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles and works
without
problems.
This
On Friday 20 April 2001 16:33, Francois Romieu wrote:
> Stefan Jaschke <[EMAIL PROTECTED]> ecrit :
> > I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles
> > and works without problems.
> > This gives me a workable solution :-)
>
> Thanks for t
On Friday 20 April 2001 18:45, Francois Romieu wrote:
> I assume nothing is overclocked or whatever
Nothing is overclocked.
> Could you try this patch (more output during the loop):
Tried it. The (lengthy) log is attached.
The interrupt is triggered when the other side initiates a request.
Hi Jens,
I took some time to try to understand why "mke2fs -b 2048 /dev/hdc"
wants 500MB memory. Here is a first explanation:
# mke2fs -m 0 -n /dev/hdc
mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
On Saturday 21 April 2001 20:52, Tamas Nagy wrote:
> extend the current file-system with an optional plug-in system, which
> allows for file-system level encryption instead of file-level. This could
> be used transparently for applications or even for file-system drivers.
> This doesn't mean an
Judging from the thread started Jan 1, 2001, by Andre Hedrick,
I thought IDE DVD-RAM just works out of the box and got a
Toshiba SD-W2002.
Problem: /dev/hdc cannot be read or written to when the drive contains
DVD-RAM media. The behavior is the same for the stock 2.4.3 kernel
and the
On Tuesday 17 April 2001 18:45, Oliver Teuber wrote:
> my smc epic100 card does not work with the device driver from
> linux-2.4.3-ac7.
> linux-2.2.19 works fine for me.
Same behavior here. Just want to add that the 2.4.0 kernel (SuSE 7.1) also
works fine.
Stefan
-
To unsubscribe from this
34 matches
Mail list logo
