MandrakeUpdateRobot, UGH!

Community Support question - to convert into a paid question, click here

Lines in bold below have not yet been seen by the customer - those in blue are from the customer

Username : Date : Action : Comments [ close all ]
jdii1215 : 22/12/01 06:51 AM : Incident created -   Well, this is a question in RE why the MandrakeUpdateRobot fetched and installed kernel set 2.4.8-34 and then after rebooting I get an immediate "EBDA too big" in all modes when trying to load through LiLo. I told it to fetch and load all it could find, selecting EVERYTHING it offered me. What the heck is an EBDA? A Linux Newbie. John.
Linegod_7611 : 22/12/01 07:33 PM : Reply received -   Kernels should never be updated by MandrakeUpdate (newer version do not allow it), but should be done 'by hand'. To recover, boot with your Linux boot disk, and when it comes up, switch to a console and as root, run '/sbin/lilo' to reconfigure LILO.
jdii1215 : 23/12/01 03:17 AM : Incident closed -   Ok, but this was MandrakeUpdateRobot package from the 8.1 i586 distribution, run from within the software manager-- the kernel packs were Security Flagged on Update-Source. And the packages offered were not stated as Source, they were mdk (mandrake) RPM packs. I got it back up, thanks. However, I reloaded it to recover, from scratch, so I cannot dig the logs out to figure out the details of the crash cascade. I HOPE to heck that ML 8.2 will not allow this, but this was NOT an attempt at a raw kernel compile via the Software Manager. You are correct, I would NOT do THAT without EXPECTING MAJOR problems. John.

---