[opensuse] kernel problems
I am currently using kernel 2.6.34-12-desktop. I tried upgrading to 2.6.34.4 and found that X would not work. Downgrading resolved that issue. So I was pleased to see a new kernel out 2.6.34.7 However on trying this update my system wouldn't boot. It gives the following error message. mount: unknown filesystem type 'ext4' Has the new kernel not been built with support for ext4? Has anyone else updated to the new kernel and found this problem with ext4? Is there a simple solution or do I need to recompile the kernel? Thanks in advance. Eddie -- Delight thyself also in the Lord and He shall give thee the desires of thine heart. Psalm. 37:4 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I am currently using kernel 2.6.34-12-desktop. I tried upgrading to 2.6.34.4 and found that X would not work. Downgrading resolved that issue. So I was pleased to see a new kernel out 2.6.34.7 However on trying this update my system wouldn't boot. It gives the following error message.
mount: unknown filesystem type 'ext4'
Has the new kernel not been built with support for ext4? Has anyone else updated to the new kernel and found this problem with ext4? Is there a simple solution or do I need to recompile the kernel?
Thanks in advance. Eddie
I don't remember if ext4 is in the kernel or not (I'm still using ext3). Whatever, a simple solution is to add it to the initrd via Yast sysconfig editor, the initrd will be rebuilt upon exit. Can also be done from the command line by editing /etc/sysconfig/kernel and then running mkinitrd. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Sep 17, 2010 at 4:22 PM, dwgallien <dwgallien@gmail.com> wrote:
I am currently using kernel 2.6.34-12-desktop. I tried upgrading to 2.6.34.4 and found that X would not work. Downgrading resolved that issue. So I was pleased to see a new kernel out 2.6.34.7 However on trying this update my system wouldn't boot. It gives the following error message.
mount: unknown filesystem type 'ext4'
Has the new kernel not been built with support for ext4? Has anyone else updated to the new kernel and found this problem with ext4? Is there a simple solution or do I need to recompile the kernel?
Thanks in advance. Eddie
I don't remember if ext4 is in the kernel or not (I'm still using ext3). Whatever, a simple solution is to add it to the initrd via Yast sysconfig editor, the initrd will be rebuilt upon exit. Can also be done from the command line by editing /etc/sysconfig/kernel and then running mkinitrd.
If it's not already in the just released kernel by default, it's a bug pure and simple. I'll update my system now and try it out. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Sep 17, 2010 at 4:26 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Fri, Sep 17, 2010 at 4:22 PM, dwgallien <dwgallien@gmail.com> wrote:
I am currently using kernel 2.6.34-12-desktop. I tried upgrading to 2.6.34.4 and found that X would not work. Downgrading resolved that issue. So I was pleased to see a new kernel out 2.6.34.7 However on trying this update my system wouldn't boot. It gives the following error message.
mount: unknown filesystem type 'ext4'
Has the new kernel not been built with support for ext4? Has anyone else updated to the new kernel and found this problem with ext4? Is there a simple solution or do I need to recompile the kernel?
Thanks in advance. Eddie
I don't remember if ext4 is in the kernel or not (I'm still using ext3). Whatever, a simple solution is to add it to the initrd via Yast sysconfig editor, the initrd will be rebuilt upon exit. Can also be done from the command line by editing /etc/sysconfig/kernel and then running mkinitrd.
If it's not already in the just released kernel by default, it's a bug pure and simple.
I'll update my system now and try it out.
Greg
I did not test initrd which is used during boot, but I did test the new kernel itself and I see no problems with ext4. So there should not be any reason to recompile. == My test after booting a machine with no ext4 partitions # create a loopback file to mount gaf@tiger3-64bit:~/temp> dd if=/dev/zero of=tmp_fs bs=1M count=5000 5000+0 records in 5000+0 records out ... # put a ext4 fs on it gaf@tiger3-64bit:~/temp> sudo /sbin/mkfs.ext4 tmp_fs mke2fs 1.41.11 (14-Mar-2010) tmp_fs is not a block special device. Proceed anyway? (y,n) y ... # mount it loopback gaf@tiger3-64bit:~/temp> sudo mount -t ext4 -o loop tmp_fs /mnt # verify it mounted gaf@tiger3-64bit:~/temp> mount ... /dev/loop0 on /mnt type ext4 (rw) # make sure the ext4 module is now loaded. (It was not prior to these steps) gaf@tiger3-64bit:~/temp> lsmod | grep ext4 ext4 401916 1 jbd2 100410 1 ext4 crc16 1715 1 ext4 # verify I'm running the just released kernel gaf@tiger3-64bit:~/temp> uname -a Linux tiger3-64bit 2.6.34.7-0.2-desktop #1 SMP PREEMPT 2010-09-14 14:21:06 +0200 x86_64 x86_64 x86_64 GNU/Linux # all looks good Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 Sep 2010 23:00:03 Greg Freemyer wrote:
On Fri, Sep 17, 2010 at 4:26 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Fri, Sep 17, 2010 at 4:22 PM, dwgallien <dwgallien@gmail.com> wrote:
I am currently using kernel 2.6.34-12-desktop. I tried upgrading to 2.6.34.4 and found that X would not work. Downgrading resolved that issue. So I was pleased to see a new kernel out 2.6.34.7 However on trying this update my system wouldn't boot. It gives the following error message.
mount: unknown filesystem type 'ext4'
Has the new kernel not been built with support for ext4? Has anyone else updated to the new kernel and found this problem with ext4? Is there a simple solution or do I need to recompile the kernel?
Thanks in advance. Eddie
I don't remember if ext4 is in the kernel or not (I'm still using ext3). Whatever, a simple solution is to add it to the initrd via Yast sysconfig editor, the initrd will be rebuilt upon exit. Can also be done from the command line by editing /etc/sysconfig/kernel and then running mkinitrd.
If it's not already in the just released kernel by default, it's a bug pure and simple.
I'll update my system now and try it out.
Greg
I did not test initrd which is used during boot, but I did test the new kernel itself and I see no problems with ext4.
So there should not be any reason to recompile.
== My test after booting a machine with no ext4 partitions
# create a loopback file to mount gaf@tiger3-64bit:~/temp> dd if=/dev/zero of=tmp_fs bs=1M count=5000 5000+0 records in 5000+0 records out ...
# put a ext4 fs on it gaf@tiger3-64bit:~/temp> sudo /sbin/mkfs.ext4 tmp_fs mke2fs 1.41.11 (14-Mar-2010) tmp_fs is not a block special device. Proceed anyway? (y,n) y ... # mount it loopback
gaf@tiger3-64bit:~/temp> sudo mount -t ext4 -o loop tmp_fs /mnt
# verify it mounted gaf@tiger3-64bit:~/temp> mount ... /dev/loop0 on /mnt type ext4 (rw)
# make sure the ext4 module is now loaded. (It was not prior to these steps) gaf@tiger3-64bit:~/temp> lsmod | grep ext4 ext4 401916 1 jbd2 100410 1 ext4 crc16 1715 1 ext4
# verify I'm running the just released kernel gaf@tiger3-64bit:~/temp> uname -a Linux tiger3-64bit 2.6.34.7-0.2-desktop #1 SMP PREEMPT 2010-09-14 14:21:06 +0200 x86_64 x86_64 x86_64 GNU/Linux
# all looks good
Greg
Thanks All Something must have gone wrong with the update. I went back to yast and discovered that it was showing the old kernel as the one that was installed, and but all the supporting packages were showing the new version. So I tried updating the kernel again. This time it worked, and so far everything seems to be okay. Eddie -- Delight thyself also in the Lord and He shall give thee the desires of thine heart. Psalm. 37:4 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
dwgallien -
eddie -
Greg Freemyer