Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-16-2005, 02:49 PM
|
#1
|
Member
Registered: Dec 2001
Location: California, USA
Distribution: Ubuntu, Debian
Posts: 128
Rep:
|
Mandrake 10.1 - kernel weirdness
Greetings:
I just upgraded my office machine to Mandrake 10.1 from 9.2.
After the upgrade, the stock 2.6.8 kernel would not load the ext3 module, so most of my partitions did not get mounted.
I tried recompiling the kernel with the ext3 module compiled in...this worked, but the new kernel continued to look for its modules in /lib/modules/2.6.8.1-12mdk instead of /lib/modules/2.6.8.1-12mdkcustom, which is where the modules are actually installed after the kernel is compiled - so therefore, no modules get loaded.
I had the same results with the updated stock kernel (2.6.8.1-24mdk); custom-compile: same results.
What's up??????
Thanks in advance for any help. In the meantime, I'm able to boot with the old 2.4.22-10mdk kernel from 9.2, but I'd like to use the 2.6 kernel.
Bob
|
|
|
03-16-2005, 03:35 PM
|
#2
|
Senior Member
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090
Rep:
|
Eh, the "stock" kernel supports ext3 just fine.
However there was a dramatic change to ext3 which may prohibit it from seeing older ext3 partitions.
When I upgraded a system to 10.1 I noticed that it was unable to mount a particular ext3 partition I had on a drive.
I ended up having to reformat/partition that drive to get ext3 to work.
You may be running into something similiar.
|
|
|
03-16-2005, 03:45 PM
|
#3
|
Member
Registered: Dec 2001
Location: California, USA
Distribution: Ubuntu, Debian
Posts: 128
Original Poster
Rep:
|
Actually, this isn't the case. If I do boot into the stock kernel, log in as root (since my / and /usr partitions are ext2, I can do this), then
modprobe ext3
mount -a
all the partitions are mounted and read/writable; however, none of my system services are running and have to be started manually.
Also, as I said, if I hard-compile the module into the kernel, it mounts everything - but then looks in the wrong /lib/modules subdir for the other modules.
The message I get with the stock kernel is something like this:
mount: fs type ext3 not supported by kernel
Thanks...Bob
|
|
|
03-16-2005, 09:26 PM
|
#4
|
Member
Registered: Dec 2001
Location: California, USA
Distribution: Ubuntu, Debian
Posts: 128
Original Poster
Rep:
|
I rebuilt the initrd for the stock kernel using the "--with=ext3"
parameter. It now boots up and mounts the partitions. There are still
some problems which aren't related to this (I'm getting errors when the
network scripts get executed):
Mar 16 17:47:14 officebox ifup: arping: socket: Address family not
supported by protocol Mar 16 17:47:14 officebox ifup: Error, some other
host already uses address 127.0.0.1.
Mar 16 17:47:14 officebox network: Bringing up loopback interface:
failed
Mar 16 17:47:14 officebox ifup: arping: socket: Address family not
supported by protocol
Mar 16 17:47:14 officebox ifup: Error, some other host already uses
address 10.218.96.90.
Mar 16 17:47:14 officebox network: Bringing up interface eth0: failed
Mar 16 17:47:15 officebox ifup: arping: socket: Address family not
supported by protocol Mar 16 17:47:15 officebox ifup: Error, some other
host already uses address 192.168.56.2. Mar 16 17:47:15 officebox
network: Bringing up interface eth1: failed
Mar 16 17:47:15 officebox firewall.iptables: Starting Firewall services
Mar 16 17:47:15 officebox firewall.iptables: firewall: Configuring
Firewall Rules using iptables Mar 16 17:47:15 officebox
firewall.iptables: iptables v1.2.9:
Mar 16 17:47:15 officebox firewall.iptables: can't initialize iptables
table `filter': iptables who? (do you need to insmod?)
Most of the modules do get loaded; not all. NFS doesn't work, either,
since the network interfaces aren't up.
I'm getting there, but this is a PITA...shouldn't have to rebuild this
stuff myself to get things working.
|
|
|
03-16-2005, 09:33 PM
|
#5
|
Senior Member
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090
Rep:
|
Quote:
Originally posted by Malibyte
Actually, this isn't the case. If I do boot into the stock kernel, log in as root (since my / and /usr partitions are ext2, I can do this), then
modprobe ext3
mount -a
all the partitions are mounted and read/writable; however, none of my system services are running and have to be started manually.
Also, as I said, if I hard-compile the module into the kernel, it mounts everything - but then looks in the wrong /lib/modules subdir for the other modules.
The message I get with the stock kernel is something like this:
mount: fs type ext3 not supported by kernel
Thanks...Bob
|
Since this WORKS for you, all you have to do is add
ext3
to the /etc/modprobe.preload file then issue a mkinitrd...
A VERY easy way to do the latter is to go into the MCC and choose a different booth theme, then choose whichever one you actually want and hit OK.
Remember to only do this AFTER you add the above line to modprobe.preload and modprobe.conf
That will fix what you are seeing.
Rebuilding the kernel is almost NEVER required in Mandrake, and even then only for the more esoteric drivers not provided with a stock kernel.
By rebuilding the kernel as you have you are probably inadvertently "breaking things" as well.
Last edited by opjose; 03-16-2005 at 09:46 PM.
|
|
|
03-16-2005, 09:50 PM
|
#6
|
Member
Registered: Dec 2001
Location: California, USA
Distribution: Ubuntu, Debian
Posts: 128
Original Poster
Rep:
|
Thanks...that's a feature of Mandrake that I've never messed with (boot themes). I'll look it over.
|
|
|
All times are GMT -5. The time now is 08:09 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|