OK. Turns out it wasn't (or may not have been) a problem with the vmmon module at all. I eventually gave up trying to make the patch for the module work and upgraded from Core5 to 6; figuring that the modules would be easier to find. No luck. What turned out to be the problem was a slight difference between the kernel and kernel-devel
<br><br>[root@natsumi ~]# rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" | grep kernel | sort <br>kernel-2.6.18-1.2798.fc6.x86_64<br>kernel-devel-2.6.18-1.2798.fc6.i686<br>kernel-headers-2.6.18-1.2798.fc6.x86_64
<br><br>After removing the i686 kernel-devel and installing the x86-64, the config program worked. Windows is happily installing from a copy of Windows XP Home that I bought about a year ago by mistake and all is well with the world. Well, all will be well if I can run the software I did all of this for..
<br><br>Thanks everybody, for your help,<br>Jack<br><br><div><span class="gmail_quote">On 5/5/07, <b class="gmail_sendername">Lincoln Peters</b> <<a href="mailto:sampln@sbcglobal.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sampln@sbcglobal.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Saturday 05 May 2007 12:01, Jack Smith wrote:<br>
> Aaarghh. So doesn't it work in Core 5? Should I upgrade? Build the<br>> player from the tar file instead of using the rpm? Something simple and<br>> obvious (I hope) that I'm missing?<br><br>My guess is that the vmmon module was written for a different version of the
<br>kernel. Usually the difference between minor releases (e.g. 2.6.x) are<br>small, and won't break third-party modules, but sometimes they do.<br><br>Probably the easiest solution is to find out what version of the Linux kernel
<br>the vmmon module was originally written for and use that, even if it's<br>slightly older than what you're running now.<br><br><br>Another possibility is that the Fedora kernel contains third-party patches<br>
that breaks something in vmmon. If that's the case, you might have to build
<br>a custom kernel, and that has a much steeper learning curve than typing in<br>"rpm -U kernel". Hopefully it won't come to that.<br><br><br>--<br>Lincoln Peters <<a href="mailto:sampln@sbcglobal.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sampln@sbcglobal.net</a>><br><br>A classic is something that everyone wants to have read<br>and nobody wants to read.<br> -- Mark Twain, "The Disappearance of Literature"<br><br>_______________________________________________
<br>talk mailing list<br><a href="mailto:talk@nblug.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">talk@nblug.org</a><br><a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://nblug.org/cgi-bin/mailman/listinfo/talk</a><br></blockquote></div><br><br clear="all">
<br>-- <br>English doesn't borrow from other languages -- English follows other languages down dark alleys and takes what it wants.