Ti wrote regarding 'Re: [SLE] scsi problem' on Mon, Oct 11 at 16:28:

Marc Collin writes:

...

with suse 8.0, 8.1, 8.2 and 9 i don't have this problem... the problem happen with kernel 2.6...

=A0i have a scsi hd on the 68-Pin Wide SCSI Internal port and a cdrom and b= urner =A0scsi on my 50-Pin SCSI-2 Internal port

=A0i get often =A0sym0: SCSI parity error detected: SCR1=3D132 DBC=3D2440a04 SBCL=3D0 =A0linux kernel: eth0: no IPv6 routers present =A0linux kernel: sym0: SCSI parity error detected: SCR1=3D132 DBC=3D2440a04= SBCL=3D0 ...

SCSI parity errors are often indicative of improper SCSI termination, cable too long, or problems with a particular device. It is almost always a hardware problem.

SCSI FAQ entry #1: q: I'm having a problem - any problem - with my SCSI devices. Why? a: Check termination, and maybe check cables. --Danny, noting that nearly every problem traces back to termination :)

Le 12 Octobre 2004 11:59, Mikus Grinbergs a écrit :

On Tue, 12 Oct 2004 09:39:58 -0500 Danny Sauer wrote:

...

...

SCSI parity errors are often indicative of improper SCSI termination, cable too long, or problems with a particular device. It is almost always a hardware problem.

SCSI FAQ entry #1:

q: I'm having a problem - any problem - with my SCSI devices. Why? a: Check termination, and maybe check cables.

--Danny, noting that nearly every problem traces back to termination :)

Pay attention to the messages shown on the console when you first boot your system. Typically, SCSI BIOSes will list their devices. If one or more SCSI devices do not show up, that is often a sign of improper SCSI termination or incorrect SCSI adapter settings.

mikus

all my scsi devices show up in the scsi bioes -- La boîte à prog http://www.laboiteaprog.com

Le 13 Octobre 2004 06:26, Catimimi a écrit :

Hello,

I come in this discussion, in order to tell you that I got a similar problem with module sym53c8xx.ko when they switch from version 'i" (kernel 2.4 and early 2.6) to version "j". The error messages were not parity errors, but domain validation errors and the boot sequence was aborting.

I used 2 different solutions before finding the reason :

- 1° - I inserted the "i" sources and headers for scsi in the 2.6 kernel and it worked. - 2° - I patched the "j" release in order to stop domain validation end it worked.

But I happened to change one of my old drives : a maxtor 72Gb hdd and release "j" works. Making some googling, I found that some people had problems with old drives.

I suggest you to disconnect ( one by one) your drives and to check if the boot process succeeds.

To be complete, I installed this old drive in my summer house with release "j", but with an adaptec scsi 29160 adaptor, and it works !

i don't have problem to boot, it's when i use linux... i got some reset... after the reset, i can continu to use my hd, cdrom... scsi i tried a 2940 adapter and i don't have the problem they seem to be the driver can you send me the patched module?

Michel.

--

Michel et Catherine Garnier

4 résidence les chênes Le parc de Rocquencourt

78150 Rocquencourt

Tel/Fax : + 33 (0)1 39 43 80 13 Email : Michel.R.Garnier@wanadoo.fr Catherine.F.Garnier@wanadoo.fr

ICQ : 155138655

-- La boîte à prog http://www.laboiteaprog.com