Thanks for the output. I'm almost certain I know what the problem is,
but
I'd like to confirm my hunch. Please send me a copy of this system's
/proc/bus/pci/devices file.
Hello,
Here it is (I replaced tab by spaces).
Loïc
On Tue, 3 Jul 2007, [EMAIL PROTECTED] wrote:
Thanks for the output. I'm almost certain I know what the problem is,
but
I'd like to confirm my hunch. Please send me a copy of this system's
/proc/bus/pci/devices file.
Here it is (I replaced tab by spaces).
Thanks. This confirms my
Thanks. This confirms my hunch. I've just committed a change to fix
this. It'll show up tomorrow (CVSWeb, cvsup, etc.) and in 4.6.99.27.
Okay, I'll try it as soon as possible.
Thanks !
Loïc Mahé - ATOS ORIGIN INTEGRATION
AMO DTI/ATM/VIG/LdBO-expertise calculateur
Bureau M77 / [EMAIL
On Mon, 2 Jul 2007, [EMAIL PROTECTED] wrote:
Without the output from `scanpci -v -v` that I asked you for, there is
nothing I can rework it to.
This is strange, my second message, submitted on 22/06, was sent by the
list only on 30/06, along with you first answer. This is the reason I
didn't
Okay, more investigation on this error.
I noticed the same message (INVALID IO ALLOCATION) in the logfile
for another chipset (ATI Technologies Inc RS480 [Radeon Xpress 200G
Series])
on a Nec VL350 computer. I noticed a beep when starting XFree86, which
this
time doesn't fail. This beep
On Fri, 22 Jun 2007, [EMAIL PROTECTED] wrote:
Okay, more investigation on this error.
I noticed the same message (INVALID IO ALLOCATION) in the logfile
for another chipset (ATI Technologies Inc RS480 [Radeon Xpress 200G
Series])
on a Nec VL350 computer. I noticed a beep when starting
