From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Andre LeBlanc <ap.leblanc@shaw.ca>
Cc: bert hubert <ahu@ds9a.nl>, linux-kernel@vger.kernel.org
Subject: Re: No Network after Compiling, 2.4.19-pre8 under Debian Woody (Long Message)
Date: Wed, 15 May 2002 09:27:20 +0200 [thread overview]
Message-ID: <20020515092720.A13317@bouton.inet6-interne.fr> (raw)
In-Reply-To: <003c01c1fb9d$345e0a20$2000a8c0@metalbox> <20020514202912.GA18544@outpost.ds9a.nl> <000c01c1fba2$1779da60$2000a8c0@metalbox>
On Tue, May 14, 2002 at 04:50:13PM -0700, Andre LeBlanc wrote:
> [...]
> hda: 60046560 sectors (30744 MB) w/2048KiB Cache, CHS=3971/240/63, UDMA(100)
>
> hdb: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, DMA
>
> Uniform CD-ROM driver Revision: 3.12
>
> hdc: ATAPI 48X DVD-ROM drive, 128kB Cache, UDMA(33)
>
> [...]
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> hdb: DMA disabled
>
> ide0: reset: success
>
Your CDROM drive doesn't play well with your hard drive with 2.4 kernels.
2.4 enables UDMA (which 2.2 doesn't) for your hard drive transfers and CRC
errors show up.
When your network will be sorted out, I'd be interested by the result of the
following commands after the above errors and channel reset:
hdparm /dev/hda
hdparm -i /dev/hda
hdparm /dev/hdb
hdparm -i /dev/hdb
Then put your CDROM drive on the secondary channel with your DVD and see if the
error messages go away or focus on the DVDROM drive instead.
LB.
next prev parent reply other threads:[~2002-05-15 7:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 23:15 No Network after Compiling, 2.4.19-pre8 under Debian Woody Andre LeBlanc
2002-05-14 20:29 ` bert hubert
2002-05-14 23:50 ` No Network after Compiling, 2.4.19-pre8 under Debian Woody (Long Message) Andre LeBlanc
2002-05-14 21:21 ` bert hubert
2002-05-15 7:27 ` Lionel Bouton [this message]
2002-05-15 15:57 ` Xavier Bestel
2002-05-15 16:25 ` bert hubert
2002-05-15 16:26 ` bert hubert
2002-05-15 19:31 ` No Network after Compiling,2.4.19-pre8 " Andre LeBlanc
2002-05-17 10:21 ` No Network after Compiling, 2.4.19-pre8 " Liakakis Kostas
2002-05-15 7:34 ` No Network after Compiling, 2.4.19-pre8 under Debian Woody Lionel Bouton
[not found] ` <000f01c1fc45$ff2d0cd0$2000a8c0@metalbox>
2002-05-15 16:38 ` No Network after Compiling,2.4.19-pre8 under Debian Woody (Long Message) Xavier Bestel
2002-05-16 11:20 ` No Network after Compiling,2.4.19-pre8 under Debian Woody(Long Message) Denis Vlasenko
2002-05-16 9:05 ` Xavier Bestel
2002-05-16 14:21 ` Denis Vlasenko
2002-05-16 9:59 ` Xavier Bestel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020515092720.A13317@bouton.inet6-interne.fr \
--to=lionel.bouton@inet6.fr \
--cc=ahu@ds9a.nl \
--cc=ap.leblanc@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®