HI,
It is almost impossible to boot 2.5.6 with IDE disk with
chipset :
00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if 80
[Master])
Subsystem: Intel Corporation 82801AA IDE
Flags: bus master, medium devsel, latency 0
I/O ports at 2460 [size=16]
I get an oops with every configuration I tried.
Of course I have no way to save log this oops,
and I had no time to write it down. Anyway it is the usual
"attemped to kill init" message.
Apart of this there is the old OSS driver with still
a virt_to_bus() in dma.c file,
and drm/i810.c has the same problem too, also if a trivial
(and of course wrong, also if it works temporally) fix
is quite fast.
I am willing to test any patch
Luigi
I forgot to specify that the oops occourse when initializing the IDE
controller.
On Fri, 8 Mar 2002, Luigi Genoni wrote:
> HI,
>
> It is almost impossible to boot 2.5.6 with IDE disk with
> chipset :
>
> 00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if 80
> [Master])
> Subsystem: Intel Corporation 82801AA IDE
> Flags: bus master, medium devsel, latency 0
> I/O ports at 2460 [size=16]
>
>
> I get an oops with every configuration I tried.
> Of course I have no way to save log this oops,
> and I had no time to write it down. Anyway it is the usual
> "attemped to kill init" message.
>
> Apart of this there is the old OSS driver with still
> a virt_to_bus() in dma.c file,
> and drm/i810.c has the same problem too, also if a trivial
> (and of course wrong, also if it works temporally) fix
> is quite fast.
>
>
> I am willing to test any patch
>
> Luigi
>
>
> -
> 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/
>
Luigi Genoni wrote:
> HI,
>
> It is almost impossible to boot 2.5.6 with IDE disk with
> chipset :
>
> 00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if 80
> [Master])
> Subsystem: Intel Corporation 82801AA IDE
> Flags: bus master, medium devsel, latency 0
> I/O ports at 2460 [size=16]
>
>
> I get an oops with every configuration I tried.
> Of course I have no way to save log this oops,
> and I had no time to write it down. Anyway it is the usual
> "attemped to kill init" message.
>
> Apart of this there is the old OSS driver with still
> a virt_to_bus() in dma.c file,
> and drm/i810.c has the same problem too, also if a trivial
> (and of course wrong, also if it works temporally) fix
> is quite fast.
Could you please tell me which was the last version (possible up to
pre status) which worked? And could you possible tell where the
system actually hangs during the boot process (what is the
last init message which appears on the screen?).
During IDE setup? During mounting? During fsck or whatever.
I'm asking this becouse I couldn't get patch-2.5.6-pre3 working
on my athlon system and there are as well apparent instabilities
on my i440MX based notebook, which are not related to the IDE changes.
(pre2 with patch number 16 and 17 applied works for me of course on
both of them quite well...)
Thank you in advance.
Due to a lack of time i tried just 2.5.5, which worked very well.
I get the oops while initializing the IDE controller, just after
hdc: LTN485, ATAPI CD/DVD-ROM drive
and before the expected:
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
On Fri, 8 Mar 2002, Martin Dalecki wrote:
> Luigi Genoni wrote:
> > HI,
> >
> > It is almost impossible to boot 2.5.6 with IDE disk with
> > chipset :
> >
> > 00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if 80
> > [Master])
> > Subsystem: Intel Corporation 82801AA IDE
> > Flags: bus master, medium devsel, latency 0
> > I/O ports at 2460 [size=16]
> >
> >
> > I get an oops with every configuration I tried.
> > Of course I have no way to save log this oops,
> > and I had no time to write it down. Anyway it is the usual
> > "attemped to kill init" message.
> >
> > Apart of this there is the old OSS driver with still
> > a virt_to_bus() in dma.c file,
> > and drm/i810.c has the same problem too, also if a trivial
> > (and of course wrong, also if it works temporally) fix
> > is quite fast.
>
> Could you please tell me which was the last version (possible up to
> pre status) which worked? And could you possible tell where the
> system actually hangs during the boot process (what is the
> last init message which appears on the screen?).
>
> During IDE setup? During mounting? During fsck or whatever.
> I'm asking this becouse I couldn't get patch-2.5.6-pre3 working
> on my athlon system and there are as well apparent instabilities
> on my i440MX based notebook, which are not related to the IDE changes.
> (pre2 with patch number 16 and 17 applied works for me of course on
> both of them quite well...)
>
> Thank you in advance.
>
Luigi Genoni wrote:
> Due to a lack of time i tried just 2.5.5, which worked very well.
> I get the oops while initializing the IDE controller, just after
>
> hdc: LTN485, ATAPI CD/DVD-ROM drive
>
> and before the expected:
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>
OK thank you very much this helps. I will actually have to fake the
detection on my system to think it's the same as yours...
One thing for sure: it's not dircetly inside the
PCI host initialization, so I wonder why this problem
doesn't occur to more people.
...
On Fri, 8 Mar 2002, Martin Dalecki wrote:
> Luigi Genoni wrote:
> > Due to a lack of time i tried just 2.5.5, which worked very well.
> > I get the oops while initializing the IDE controller, just after
> >
> > hdc: LTN485, ATAPI CD/DVD-ROM drive
> >
> > and before the expected:
> > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >
>
> OK thank you very much this helps. I will actually have to fake the
> detection on my system to think it's the same as yours...
> One thing for sure: it's not dircetly inside the
> PCI host initialization, so I wonder why this problem
> doesn't occur to more people.
You will soon learn about the way ATAPI removable media violate the rules
of how the maintain their status and signal lines. However you already
knew this information as I am wasting electrons
Andre Hedrick
The Second Linux X-IDE guy
Andre Hedrick wrote:
> On Fri, 8 Mar 2002, Martin Dalecki wrote:
>
> > Luigi Genoni wrote:
> > > Due to a lack of time i tried just 2.5.5, which worked very well.
> > > I get the oops while initializing the IDE controller, just after
> > >
> > > hdc: LTN485, ATAPI CD/DVD-ROM drive
> > >
> > > and before the expected:
> > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > >
> >
> > OK thank you very much this helps. I will actually have to fake the
> > detection on my system to think it's the same as yours...
> > One thing for sure: it's not dircetly inside the
> > PCI host initialization, so I wonder why this problem
> > doesn't occur to more people.
>
> You will soon learn about the way ATAPI removable media violate the rules
> of how the maintain their status and signal lines. However you already
> knew this information as I am wasting electrons
Can you get more specific ?
Do you mean
a) Some ATAPI devices violate the "ATA/ATAPI-4" NCITS 317-1998 standard (or
a newer version),
And your driver contained workarounds for these buggy devices? (And
Martins driver doesn't contain these.)
b) Your driver conforms to the standard, and Martin's driver does not?
On Fri, 8 Mar 2002, Gunther Mayer wrote:
> Andre Hedrick wrote:
>
> > On Fri, 8 Mar 2002, Martin Dalecki wrote:
> >
> > > Luigi Genoni wrote:
> > > > Due to a lack of time i tried just 2.5.5, which worked very well.
> > > > I get the oops while initializing the IDE controller, just after
> > > >
> > > > hdc: LTN485, ATAPI CD/DVD-ROM drive
> > > >
> > > > and before the expected:
> > > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > > >
> > >
> > > OK thank you very much this helps. I will actually have to fake the
> > > detection on my system to think it's the same as yours...
> > > One thing for sure: it's not dircetly inside the
> > > PCI host initialization, so I wonder why this problem
> > > doesn't occur to more people.
> >
> > You will soon learn about the way ATAPI removable media violate the rules
> > of how the maintain their status and signal lines. However you already
> > knew this information as I am wasting electrons
>
> Can you get more specific ?
>
> Do you mean
> a) Some ATAPI devices violate the "ATA/ATAPI-4" NCITS 317-1998 standard (or
> a newer version),
Few conform to "ATA/ATAPI-4" NCITS 317-1998 standard" or newer
> And your driver contained workarounds for these buggy devices? (And
> Martins driver doesn't contain these.)
> b) Your driver conforms to the standard, and Martin's driver does not?
It may look like a simple protocol, and it is once you understand it and
all the nasties done to it by the ATAPI folks.
I do not know because I am working on making the ATA/ATAPI transport work
correctly in 2.4 and will release something in 2.6.
Regards,
Andre Hedrick
The Second Linux X-IDE guy
Andre Hedrick wrote:
> On Fri, 8 Mar 2002, Martin Dalecki wrote:
>
>
>>Luigi Genoni wrote:
>>
>>>Due to a lack of time i tried just 2.5.5, which worked very well.
>>>I get the oops while initializing the IDE controller, just after
>>>
>>>hdc: LTN485, ATAPI CD/DVD-ROM drive
>>>
>>>and before the expected:
>>>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>>
>>>
>>OK thank you very much this helps. I will actually have to fake the
>>detection on my system to think it's the same as yours...
>>One thing for sure: it's not dircetly inside the
>>PCI host initialization, so I wonder why this problem
>>doesn't occur to more people.
>>
>
> You will soon learn about the way ATAPI removable media violate the rules
> of how the maintain their status and signal lines. However you already
> knew this information as I am wasting electrons
I think an oops is rather good sign here, since it is
more of a sign of a trival typo mistake or therelike.
If the system where actually going into boot mode and starting
to be flaky then, then I would see more serious trouble...