On Monday 12 April 2010 13:34:51 Oddball wrote:
Oddball schreef: ...
AMD64x2-sfn1:/home/oddball # uname -r 2.6.27.29-0.1-default AMD64x2-sfn1:/home/oddball # grep -i ext4 /boot/config-`uname -r` CONFIG_EXT4DEV_FS=m CONFIG_EXT4DEV_FS_XATTR=y CONFIG_EXT4DEV_FS_POSIX_ACL=y CONFIG_EXT4DEV_FS_SECURITY=y AMD64x2-sfn1:/home/oddball # modprobe --list ext4dev /lib/modules/2.6.27.29-0.1-default/kernel/fs/ext4/ext4dev.ko AMD64x2-sfn1:/home/oddball # modprobe -v ext4dev insmod /lib/modules/2.6.27.29-0.1-default/kernel/lib/crc16.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/jbd2/jbd2.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/ext4/ext4dev.ko AMD64x2-sfn1:/home/oddball #
There is no complain from modprobe and that means the driver is loaded. I would recommend to check is driver really loaded after modprobe or it is crashing later when you try to use it. Right after the modprobe -v ext4dev run lsmod | grep -i ext4 to see is driver loaded. Then if you see the driver try to mount hard disk: mount /dev/sda11 /mnt and then run again: lsmod | grep -i ext4 to see is driver still in place. If it is, then try to see content. If you can't then run again: lsmod | grep -i ext4 As mentioned I used it and it worked fine. The main difference, so far I recall, is that I don't have so many partitions. If you see kernel update from regular update repo then do it, but make sure that zypper will keep old kernel. Set option: multiversion = kernel-default in /etc/zypp/zypp.conf which will preserve your old kernel, and make possible to boot the old one, if new fails. -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org