PIRQ problem (Please try using pci=biosirq)

Hi,

I am using 256kb BIOS flashrom, etherboot, and kernel image
   on compact flash IDE .

I get this error in LinuxBIOS. 
   ***Extract***
   Copying IRQ routing tables to 0xf0000...done.
   Verifing priq routing tables copy at 0xf0000...failed
   Wrote linuxbios table at: 00000500 - 0000064c  checksum b79a
   ***Extract***
   When I try do read from 0xf0000 after copying, it does shows 
   0xff instead some value.
   I had forced the sizeram to return 1MB less then the actual
   Ramsize to make it work with etherboot.

When the kernel boots up, the ethernet interface does 
   not come up.
   **Extract for the Linux kernel messaage**
   eth0: RealTek RTL8139 Fast Ethernet at 0xc4800000, 00:30:02:09:02:93, IRQ 0
PCI: No IRQ known for interrupt pin A of device 01:05.0. Please try using pci=biosirq.
eth1: RealTek RTL8139 Fast Ethernet at 0xc4802000, 00:30:02:09:02:92, IRQ 0
   **Extract for the Linux kernel messaage**

I have tried the checkpir,etc on the irq tables. It is OK 
   at the command prompt. But I still get this error.

Any suggestion on this.

Regards
Deepak

Regards
Deepak

[ron minnich]

On Sat, 17 May 2003 [e-mail] wrote:
> Hi,
>
> I am using 256kb BIOS flashrom, etherboot, and kernel image
>    on compact flash IDE .

I need to know if CONFIG_COMPRESS is set to 0, I am guessing not. Can you 
please check?

ron

[Deepak Kotian]

I do not have acces to my system now, so cannot tell for sure but what
it the signifigance  of this paramater CONFIG_COMPRESS = 0 or 1
I have seen this in couple of other responses as well which talks about this
one.

Can on please elaborate on this please and how this paramerter would lead
to this error.

Regards
Deepak

----- Original Message -----
From: "ron minnich" 
To: 
Cc: 
Sent: Saturday, May 17, 2003 8:51 PM
Subject: Re: PIRQ problem (Please try using pci=biosirq)
> On Sat, 17 May 2003 [e-mail] wrote:
> > Hi,
> >
> > I am using 256kb BIOS flashrom, etherboot, and kernel image
> >    on compact flash IDE .
>
> I need to know if CONFIG_COMPRESS is set to 0, I am guessing not. Can you
> please check?
>
> ron

"Deepak Kotian"  writes:
> I do not have acces to my system now, so cannot tell for sure but what
> it the signifigance  of this paramater CONFIG_COMPRESS = 0 or 1
> I have seen this in couple of other responses as well which talks about this
> one.
>
> Can on please elaborate on this please and how this paramerter would lead
> to this error.

LinuxBIOS is naturally split into 2 components.  
The part that runs after ram is believed to be working.
And the part that is used to initialize ram.

During ram initialization the code must run out of
the ROM chip.  After that however the code can live
in RAM.  And we take advantage of that fact by compressing
that code in the ROM chip.

Currently the PIRQ tables are just copied from the LinuxBIOS
image in the ROM chip into RAM.  Around 0xf0000 - 0xfffff.
If ``shadow'' ram has not been enabled there the copy fails.

However if LinuxBIOS is not compressed in the ROM chip, the
uncompressed table can still be found in the last 64K before 1M.
And so the pirq table can still be found that way.

The real fix is to enable shadow RAM.  Disabling compression
is an effective short term work around.

Eric

[Deepak Kotian]

Thanks, this is a good one.
One more question. How does one enable Shadow Ram.

Regards
Deepak

----- Original Message -----
From: "Eric W. Biederman" 
To: "Deepak Kotian" 
Cc: "ron minnich" ; 
Sent: Sunday, May 18, 2003 12:01 AM
Subject: Re: PIRQ problem (Please try using pci=biosirq)
> "Deepak Kotian"  writes:
> > I do not have acces to my system now, so cannot tell for sure but what
> > it the signifigance  of this paramater CONFIG_COMPRESS = 0 or 1
> > I have seen this in couple of other responses as well which talks about

this
> > one.
> >
> > Can on please elaborate on this please and how this paramerter would

lead
> > to this error.
>
> LinuxBIOS is naturally split into 2 components.
> The part that runs after ram is believed to be working.
> And the part that is used to initialize ram.
>
> During ram initialization the code must run out of
> the ROM chip.  After that however the code can live
> in RAM.  And we take advantage of that fact by compressing
> that code in the ROM chip.
>
> Currently the PIRQ tables are just copied from the LinuxBIOS
> image in the ROM chip into RAM.  Around 0xf0000 - 0xfffff.
> If ``shadow'' ram has not been enabled there the copy fails.
>
> However if LinuxBIOS is not compressed in the ROM chip, the
> uncompressed table can still be found in the last 64K before 1M.
> And so the pirq table can still be found that way.
>
> The real fix is to enable shadow RAM.  Disabling compression
> is an effective short term work around.
>
> Eric
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

Deepak Kotian  writes:
> Thanks, this is a good one.
> One more question. How does one enable Shadow Ram.

It is chipset and cpu specific.  I would look it up in the documentation.

Eric