chuck, did the kernel portion of the upgrade complete correctly. i have seen the module kind of error you mention before after a rpm kernel upgrade. what i found was that the modules did not get put into the new kernel named directory thus causing all modules to fail to load on startup.
you can find out by looking in /etc/conf/modules/<kernel version number> and see if there are any modules there. if this is the problem, my solution was to rerun the kernel rpm. as rpm is not working for you, this is obviously not an option currently. try reverting back to the previous kernel first so the old modules will be loaded. -- quitnin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of chuck Sent: Monday, November 12, 2001 11:14 AM To: [EMAIL PROTECTED] Subject: Re: [expert] 8.0 to 8.1 Upgrade On Mon, 2001-11-12 at 09:14, Salvatore Enrico Indiogine wrote: > Just a shot in the dark, but try: rpm --rebuilddb > > It is actually a good command to run after you do a lot of rpm installs > and/or uninstalls. > > Ciao, > Enrico > That was the first thing I tried. Sorry that I forgot to mention it. After seeing the 'filesystem' thing, I tried to run diskdrake and it wouldn't run either. It read: modprobe: Can't locate module floppy Segmentation fault. In /var/log/messages, I noticed 'kernel BUG at super.c:274!' and 'invalid operand: 0000 It's a pet peeve of mine to just reinstall without finding the cause. I wonder if a kernel upgrade will do it? > On Sunday 11 November 2001 18:29, you wrote: > > I did the 'upgrade' from 8.0 to 8.1. Now, any RPM command causes a > > segmentation fault, usually after it says 'D: getting list of mounted > > filesystems'. Wine also used to work, but it also gives me the > > segmentation fault error. > > > > I did a Google search and found nothing. > > > > Thanks in advance, > > > > Chuck >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
