Alright, I have now updated to 2.6.24-7-generic and the allocation
message is gone. The only thing that is showing up before usplash is one
line:
PCI: Failed to allocate mem resource #6:20000@d0000000 for 0000:01:00.0
Could that line be lowered safely? As far as I can tell, nothing is
broken. The PCI device in question should be the graphics card which is
working perfectly.
Output of lspci attached.
On Fri, 2008-02-08 at 17:13 +0000, Stephan Klein wrote:
> It is showing up on startup, right before usplash kicks in.
> It also shows up in dmesg, but that is to be expected, I know. The point
> would be to have it only log to messages and not show up before usplash.
>
> On Fri, 2008-02-08 at 13:56 +0000, Stefan Bader wrote:
> > Please clarify, is this message still showing up on the console or just
> > in the message log/dmesg? It shouldn't show up on the console but it
> > will show up in the other places. This is intentional.
> >
>
Alright, I have now updated to 2.6.24-7-generic and the allocation
message is gone. The only thing that is showing up before usplash is one
line:
PCI: Failed to allocate mem resource #6:20000@d0000000 for 0000:01:00.0
Could that line be lowered safely? As far as I can tell, nothing is
broken. The PCI device in question should be the graphics card which is
working perfectly.
Output of lspci attached.
On Fri, 2008-02-08 at 17:13 +0000, Stephan Klein wrote:
> It is showing up on startup, right before usplash kicks in.
> It also shows up in dmesg, but that is to be expected, I know. The point
> would be to have it only log to messages and not show up before usplash.
>
> On Fri, 2008-02-08 at 13:56 +0000, Stefan Bader wrote:
> > Please clarify, is this message still showing up on the console or just
> > in the message log/dmesg? It shouldn't show up on the console but it
> > will show up in the other places. This is intentional.
> >
>