On Sun, 2009-08-16 at 00:45 +0100, Ben Hutchings wrote: > On Sun, 2009-08-16 at 00:30 +0200, advocatux wrote: > > 2009/8/15 Ben Hutchings <[email protected]>: > > > On Sat, 2009-08-15 at 21:55 +0200, advocatux wrote: > > >> 2009/8/15 Ben Hutchings <[email protected]>: > > >> [...] > > >> > > >> I'm afraid I'm addressing the 'classic' problem -> insmod: error > > >> inserting 'r128.ko': -1 Invalid module format. > > > > > > Damn, I thought I'd matched the configuration properly. Does the kernel > > > log have any more specific error messages? > > > > > > > Hi again Ben, > > > > In kern.log there're a lot of 'Xorg:3526 freeing invalid memtype ...' then: > > > > agpgart-intel 0000:00:00.0: AGP 2.0 bridge > > agpgart-intel 0000:00:00.0: putting AGP V2 device into 1x mode > > pci 0000:01:00.0: putting AGP V2 device into 1x mode > > platform r128_cce.0: firmware: requesting r128/r128_cce.bin > > > > then another bunch of 'Xorg:3526 freeing invalid memtype ...' and, > > finally, this line 6 times -> r128: no symbol version for > > module_layout > > I have put a new version of the module up in the same location. Please > try again with this version. > > > P.S. As you'd send me this email without CC to [email protected], > > I'm replying just to you. > > > > Is it OK? > > That was unintentional. Please carry on cc'ing the bug report.
...which should be addressed as above, not as in my previous message. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
