[opensuse-factory] Netiso MS3: Not all needed modules present in repo.
Hi, I updated to MS3, using zypper dup, rebooting complained about two missing kernelmodules: result no desktop starting up, no tty. Fixing the issue using the Netiso leaded to ncurses and trying to load the installmodules 3 times. Not possible to install or repair. 'an error occured'.... All went well untill the install should start: ti connecting to the server, downloading the modules. Than few modules missing, and stop. Rescue did work, but i did not know the commands to get it doing what i needed. Luckily i have a still working 11.1 install. Any ideas as how to get the missing modules installed, and getting the system booted? (amd modules and pata are missing, caught in a glimps) Unfortunately i am not able to get to the bootlog from this install, i will try to get the right names of the missing modules. -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 21/03/10 13:27, Oddball wrote:
Hi,
I updated to MS3, using zypper dup, rebooting complained about two missing kernelmodules: result no desktop starting up, no tty. Fixing the issue using the Netiso leaded to ncurses and trying to load the installmodules 3 times. Not possible to install or repair. 'an error occured'.... All went well untill the install should start: ti connecting to the server, downloading the modules. Than few modules missing, and stop. Rescue did work, but i did not know the commands to get it doing what i needed.
Luckily i have a still working 11.1 install.
Any ideas as how to get the missing modules installed, and getting the system booted?
(amd modules and pata are missing, caught in a glimps) Unfortunately i am not able to get to the bootlog from this install, i will try to get the right names of the missing modules Actually, in my experience with recent openSUSE kernels is that the kernel says things like FATAL: module piix not found all the time and it is rarely actually fatal. The problem is most likely something else. How far did the MS3 system get on starting up?
Regards, Tejas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Tejas Guruswamy schreef:
On 21/03/10 13:27, Oddball wrote:
Hi,
(and other things)
Actually, in my experience with recent openSUSE kernels is that the kernel says things like FATAL: module piix not found all the time and it is rarely actually fatal. The problem is most likely something else. How far did the MS3 system get on starting up?
Regards, Tejas
Well, it has been a long time i've seen a bug this magnitude.. :) Mostly grub hickups caused a version not to boot... This, i've only seen with wrong x-config, but that is only after login in. No text, or error recognision appeared, just a black screen... It got until the loginscreen should appear, or closely to there... The messages about udevd i've got since MS1 are gone though, which is good.. -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Tejas Guruswamy schreef:
The problem is most likely something else.
Regards, Tejas
I think not, as i am using an amd, the other module has to do with harddrives..
-- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 21/03/10 17:18, Oddball wrote:
Tejas Guruswamy schreef:
On 21/03/10 13:27, Oddball wrote:
Hi,
(and other things)
Actually, in my experience with recent openSUSE kernels is that the kernel says things like FATAL: module piix not found all the time and it is rarely actually fatal. The problem is most likely something else. How far did the MS3 system get on starting up?
Well, it has been a long time i've seen a bug this magnitude.. :) Mostly grub hickups caused a version not to boot... This, i've only seen with wrong x-config, but that is only after login in. No text, or error recognision appeared, just a black screen... It got until the loginscreen should appear, or closely to there... The messages about udevd i've got since MS1 are gone though, which is good..
Sounds more like an X problem - can you boot to runlevel 3? (just add a "3" to the end of the boot options in grub when starting up) Regards, Tejas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Hi,
<snip> i will try to get the right names of the missing modules.
amd74xx, and ide_pci_generic are the missing modules in the install. I have not been able to boot into init 3 imediately.. What is the keycombination to get into init 3 from say, the loginscreen? (i suspect there should be a loginscreen, but the screen is black...ctrl+alt+del reboots the system at this point, without confirmationnessesity...) -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/22/2010 10:33 AM, Oddball wrote:
Oddball schreef:
Hi,
<snip> i will try to get the right names of the missing modules.
amd74xx, and ide_pci_generic are the missing modules in the install. I have not been able to boot into init 3 imediately.. What is the keycombination to get into init 3 from say, the loginscreen? (i suspect there should be a loginscreen, but the screen is black...ctrl+alt+del reboots the system at this point, without confirmationnessesity...)
Those modules are missing because they depend on CONFIG_IDE, which was dropped 25 Feb. The pata_amd driver should be used instead. It's enabled on all openSUSE configs. Is that driver not getting loaded? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkungTYACgkQLPWxlyuTD7IMmACdEKjKUj0ZEYuntRM36x8ddIwF zlgAn1qo4tieptDaq7TEVX9VBIMpn1YX =7SOY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Jeff Mahoney schreef:
On 03/22/2010 10:33 AM, Oddball wrote:
Oddball schreef:
Hi,
<snip> i will try to get the right names of the missing modules.
amd74xx, and ide_pci_generic are the missing modules in the install. I have not been able to boot into init 3 imediately.. What is the keycombination to get into init 3 from say, the loginscreen? (i suspect there should be a loginscreen, but the screen is black...ctrl+alt+del reboots the system at this point, without confirmationnessesity...)
Those modules are missing because they depend on CONFIG_IDE, which was dropped 25 Feb. The pata_amd driver should be used instead. It's enabled on all openSUSE configs. Is that driver not getting loaded?
-Jeff
Is there a way to check that? As said, the screen is black.... -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 03/22/2010 09:52 AM, Oddball wrote:
Jeff Mahoney schreef:
On 03/22/2010 10:33 AM, Oddball wrote:
Oddball schreef:
<snip> i will try to get the right names of the missing modules.
Those modules are missing because they depend on CONFIG_IDE, which was dropped 25 Feb. The pata_amd driver should be used instead. It's enabled on all openSUSE configs. Is that driver not getting loaded?
Is there a way to check that? As said, the screen is black....
Can you switch to an alternate console using Ctrl+Alt+FX? There should be a shell for X equals 2, 5, 6 or 9. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Larry Finger schreef:
On 03/22/2010 09:52 AM, Oddball wrote:
Jeff Mahoney schreef:
On 03/22/2010 10:33 AM, Oddball wrote:
Oddball schreef:
<snip> i will try to get the right names of the missing modules.
Those modules are missing because they depend on CONFIG_IDE, which was dropped 25 Feb. The pata_amd driver should be used instead. It's enabled on all openSUSE configs. Is that driver not getting loaded?
Is there a way to check that? As said, the screen is black....
Can you switch to an alternate console using Ctrl+Alt+FX? There should be a shell for X equals 2, 5, 6 or 9.
Larry
I wil try.. I was able to get to init 3, by typing init 3 in the grubbootloader commandline.. :) There seems to be a problem with x. 'startx' from here gives the same black screen, and sax2 was not able to setup an x server, but recommended to try sax2 -p and select a single device.. This however was impossible, as there was only a return with my ATI Radeon 7500 PCIE, and no possiblity to get it started... There was a series of hexdump, but i do not know how to get to these filkes from 11.1.: The dir is visible, but empty..... -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
There was a series of hexdump, but i do not know how to get to these filkes from 11.1.: The dir is visible, but empty.....
The reason is that ext4 cann't be read from 11.1:
oddball@AMD64x2-sfn1:~> dmesg | tail SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=74 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=54 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=74 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=54 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=74 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=54 SFW2-INext-DROP-DEFLT-INV IN=eth0 OUT= MAC=00:1b:b9:c9:34:4c:00:1e:e5:70:49:b6:08:00 SRC=67.227.180.144 DST=192.168.1.102 LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=8323 PROTO=TCP SPT=80 DPT=53293 WINDOW=0 RES=0x00 RST URGP=0 EXT3-fs: sda11: couldn't mount because of unsupported optional features (240). SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=74 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=54 konsole[4947]: segfault at e0 ip 00007fc60d0eeb1b sp 00007fffc5a2cc40 error 4 in libkdeui.so.5.3.0[7fc60cdb7000+3d7000] EXT3-fs: sda11: couldn't mount because of unsupported optional features (240). EXT3-fs: sda11: couldn't mount because of unsupported optional features (240). EXT3-fs: sda11: couldn't mount because of unsupported optional features (240). oddball@AMD64x2-sfn1:~>
-- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
It seems indeed an xserver problem. Is MS4 ready on thursday? (i read that many people had black, blanc or multicoloured screens....imho this 'better than sax2 sw' is not completely finished.....but no option to repair, or setup an alternate xserver is worse... How to get to the logfiles?) -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 22 March 2010 10:37:28 Oddball wrote:
The reason is that ext4 cann't be read from 11.1:
modprobe ext4dev then you can mount ext4 file system. Above should work. I don't have any 11.1 installations left, so I can't check the driver name, but it should be in: /lib/modules/<kernel version>/kernel/fs/ext4/ -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Monday 22 March 2010 10:37:28 Oddball wrote:
The reason is that ext4 cann't be read from 11.1:
modprobe ext4dev then you can mount ext4 file system.
Above should work. I don't have any 11.1 installations left, so I can't check the driver name, but it should be in: /lib/modules/<kernel version>/kernel/fs/ext4/
Thnx Rajko, will try.. -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Rajko M. schreef:
On Monday 22 March 2010 10:37:28 Oddball wrote:
The reason is that ext4 cann't be read from 11.1:
modprobe ext4dev then you can mount ext4 file system.
Above should work. I don't have any 11.1 installations left, so I can't check the driver name, but it should be in: /lib/modules/<kernel version>/kernel/fs/ext4/
Thnx Rajko, will try..
there is 'ext4dev.ko' in the given location...'modprobe ext4dev.ko /lib/modules/2.6.27.29-01-default/kernel/fs/ext4/' gives: modules not found modprobe ext4dev /lib/modules/2.6.27.29-01-default/kernel/fs/ext4/.. changes nothing, so still cannot open ext4 from 11.1.. :( -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 11 April 2010 08:17:45 Oddball wrote: ...
The reason is that ext4 cann't be read from 11.1: modprobe ext4dev then you can mount ext4 file system. ... there is 'ext4dev.ko' in the given location...'modprobe ext4dev.ko /lib/modules/2.6.27.29-01-default/kernel/fs/ext4/' gives: modules not found modprobe ext4dev /lib/modules/2.6.27.29-01-default/kernel/fs/ext4/.. changes nothing, so still cannot open ext4 from 11.1.. :(
If you use kernel 2.6.27.29-01-default which is precondition to load ext4dev then: modprobe ext4dev will load the driver, but I'm not sure that it is included in HAL, so GUI tools that use HAL to mount drives can fail. Try plain console: mount /dev/sdXN /mnt where X is drive letter and N drive number of partition formatted with ext4. Then see is there any content in /mnt directory. So far I recall I used it that way and it worked fine. -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Sunday 11 April 2010 08:17:45 Oddball wrote: ...
The reason is that ext4 cann't be read from 11.1:
modprobe ext4dev then you can mount ext4 file system.
...
there is 'ext4dev.ko' in the given location...'modprobe ext4dev.ko /lib/modules/2.6.27.29-01-default/kernel/fs/ext4/' gives: modules not found modprobe ext4dev /lib/modules/2.6.27.29-01-default/kernel/fs/ext4/.. changes nothing, so still cannot open ext4 from 11.1.. :(
If you use kernel 2.6.27.29-01-default which is precondition to load ext4dev then: modprobe ext4dev will load the driver, but I'm not sure that it is included in HAL, so GUI tools that use HAL to mount drives can fail. Try plain console: mount /dev/sdXN /mnt where X is drive letter and N drive number of partition formatted with ext4. Then see is there any content in /mnt directory. So far I recall I used it that way and it worked fine.
installed is 2.6.27.29-0.1.1 (aug. 2009) but mount in a console gives the same output as in a gui: incorrect file system type, invalid option, missing code page, being lacking aid programme, bad super block-system on /dev/sda11, or another wrong .. available is: 2.6.27.45-0.1.1 (feb. 2010) Would it be wise to install that one? -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 11 April 2010 12:54:38 Oddball wrote:
installed is 2.6.27.29-0.1.1 (aug. 2009) but mount in a console gives the same output as in a gui: incorrect file system type, invalid option, missing code page, being lacking aid programme, bad super block-system on /dev/sda11, or another wrong ..
You have to check is driver actually loaded with: lsmod | grep ext it should output driver name and all other kernel modules that use it. What is output of (as root): file -s /dev/sda11 it should give you file system type. You can try also (as root): mount -t ext4 /dev/sda11 /mnt
available is: 2.6.27.45-0.1.1 (feb. 2010) Would it be wise to install that one?
If that is regular update then use it independent on ext4dev driver issues. -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Sunday 11 April 2010 12:54:38 Oddball wrote:
installed is 2.6.27.29-0.1.1 (aug. 2009) but mount in a console gives the same output as in a gui: incorrect file system type, invalid option, missing code page, being lacking aid programme, bad super block-system on /dev/sda11, or another wrong ..
You have to check is driver actually loaded with: lsmod | grep ext it should output driver name and all other kernel modules that use it.
What is output of (as root): file -s /dev/sda11 it should give you file system type.
You can try also (as root): mount -t ext4 /dev/sda11 /mnt
oddball@AMD64x2-sfn1:~> lsmod | grep ext ext2 68712 1 ext3 140824 5 mbcache 9484 2 ext2,ext3 jbd 61752 1 ext3 oddball@AMD64x2-sfn1:~> su Wachtwoord: AMD64x2-sfn1:/home/oddball # file -s /dev/sda11 /dev/sda11: Linux rev 1.0 ext4 filesystem data (extents) (large files) (huge files) AMD64x2-sfn1:/home/oddball # mount -t ext4 /dev/sda11 /mnt mount: onbekende bestandssysteemsoort 'ext4' (mount: unknown filesystem 'ext4') AMD64x2-sfn1:/home/oddball #
available is: 2.6.27.45-0.1.1 (feb. 2010) Would it be wise to install that one?
If that is regular update then use it independent on ext4dev driver issues.
-- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 11 April 2010 14:16:31 Oddball wrote:
oddball@AMD64x2-sfn1:~> lsmod | grep ext ext2 68712 1 ext3 140824 5 mbcache 9484 2 ext2,ext3 jbd 61752 1 ext3
The module is not loaded. Post output of: uname -r then grep -i ext4 /boot/config-`uname -r` then modprobe --list etx4dev then modprobe -v etx4dev -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Sunday 11 April 2010 14:16:31 Oddball wrote:
oddball@AMD64x2-sfn1:~> lsmod | grep ext ext2 68712 1 ext3 140824 5 mbcache 9484 2 ext2,ext3 jbd 61752 1 ext3
The module is not loaded.
Post output of: uname -r then grep -i ext4 /boot/config-`uname -r` then modprobe --list etx4dev then modprobe -v etx4dev
AMD64x2-sfn1:/home/oddball # uname -r 2.6.27.29-0.1-default AMD64x2-sfn1:/home/oddball # grep -i ext4 /boot/config-'uname-r' grep: /boot/config-uname-r: Bestand of map bestaat niet (file or dir does not exist) 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 # -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Il lunedì 12 aprile 2010, Oddball scrisse:
AMD64x2-sfn1:/home/oddball # uname -r 2.6.27.29-0.1-default AMD64x2-sfn1:/home/oddball # grep -i ext4 /boot/config-'uname-r' Backtick: (`) and not ('). Missing space between uname and -r. So: # grep -i ext4 /boot/config-`uname -r` Bye.
-- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Daniele schreef:
Il lunedì 12 aprile 2010, Oddball scrisse:
AMD64x2-sfn1:/home/oddball # uname -r 2.6.27.29-0.1-default AMD64x2-sfn1:/home/oddball # grep -i ext4 /boot/config-'uname-r'
Backtick: (`) and not ('). Missing space between uname and -r. So: # grep -i ext4 /boot/config-`uname -r` Bye.
thnx... :-) -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Rajko M. schreef:
On Sunday 11 April 2010 14:16:31 Oddball wrote:
oddball@AMD64x2-sfn1:~> lsmod | grep ext ext2 68712 1 ext3 140824 5 mbcache 9484 2 ext2,ext3 jbd 61752 1 ext3
The module is not loaded.
Post output of: uname -r then grep -i ext4 /boot/config-`uname -r` then modprobe --list etx4dev then modprobe -v etx4dev
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 #
-- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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
Rajko M. schreef:
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.
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 # lsmod | grep -i ext4 ext4dev 223264 0 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # mount /dev/sda11 /mnt AMAMD64x2-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 # lsmod | grep -i ext4 ext4dev 223264 0 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # mount /dev/sda11 /mnt AMD64x2-sfn1:/home/oddball # lsmod | grep -i ext4 ext4dev 223264 1 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # D64x2-sfn1:/home/oddball # lsmod | grep -i ext4 ext4dev 223264 1 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # I have visual on the ext4 partition now.. It is slow, and i do not know the pathdepth yet, but it mounts! Thank you very much for your help.. It will be much easier now to get to the logs i need.. Btw, Stefan Dirsch was able to tackle the 'X' problem...it is not perfect yet, but i have visual there also... -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Larry Finger schreef:
Can you switch to an alternate console using Ctrl+Alt+FX? There should be a shell for X equals 2, 5, 6 or 9.
Larry
Nope... The only way to get a terminalscreen is add init 3 to the commandline at the bootloaderscreen... -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Daniele -
Jeff Mahoney -
Larry Finger -
Oddball -
Rajko M. -
Tejas Guruswamy