There are two other proplems with this board:grub error 28: Selected item cannot fit into memory.Well dear, I got EXACTLY the same problems while trying to install SUSE 8.1 on this motherboard. I'd tried REDHAT7.3 also but there also I can't initialise XFree86 =>system hangs.
1. XFree86 doesn't work with the supplied drivers. You must download a special one from http://www.nvidia.com/. The good news is, this driver is probably optimised a lot better than your average XFree86-packaged one, so you should get really good performance.
2. APM (power mangement) functions will hang with the default kernel. X server test will actually trigger this problem, as it includes a panel that does some power management stuff to decide if it ought to display "battery status" applet. To get around this, try specifying "apm=off" when asked for extra kernel options during install. Also, the problem has been resolved in the latest official kernel update.
Hmmm. Possibly. At any rate, the memory layout is somewhat special on this board...The thing I remarked is that when I use the HIMEM.SYS from a dos bootfloppy there's an error message telling me that there is no upper memory available. I think that this is yet again a very old problem that is surfacing again: Memory regions.
What I did initially, wasSolution is in my opinion to pass the GRUB to LILO . Since the mandrake8.0 install passed a whole lot better (boots with LILO) . The procedure to do this I still have to test (and since i'm a linux-newbie I rekken this will take some time ;-) ) If you should have a procedure to overcome this problem I would be VERY greathfull if you would pass the info.
1. Boot from floppy created in rescue mode. (You could also get the installer to do it, of course.)
2. Run command 'lilo'
That was it; Red Hat installer will install config for LILO *and* GRUB config, so switching between them is just a matter of running the appropriate command to install the boot sector (i.e. lilo or grub-install.)
Since then, I've been able to switch back to GRUB. Apparently, its developers have rewritten parts of it in a manner that resolves this problem, and Red Hat are working on an updated package, which I was given an early version of.
>From my side if I find a solution I'll send it to you too. Greetings, K. Belgium mailto:mailme@;freeworld.be **** DISCLAIMER **** "This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation."
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
