Hi, Just tried to install mainline kernel 2.6.12 on SUSE 9.3. Works fine, but had to assemble initrd manually. Seems that SUSEs mkinird copies modules to initrd from wrong kernel release ( 2.6.11.12 on my case ); anyone here that might have read that script through and figured out what goes ballistic with it? -- // Janne
Janne Karhunen wrote:
Hi,
Just tried to install mainline kernel 2.6.12 on SUSE 9.3. Works fine, but had to assemble initrd manually. Seems that SUSEs mkinird copies modules to initrd from wrong kernel release ( 2.6.11.12 on my case ); anyone here that might have read that script through and figured out what goes ballistic with it?
I've had no problems up to 2.6.12-rc6-git8 and I'm now compiling 2.6.12, so I shall see if anything has changed when I bring it up late this evening. This is contents of my script called INITRD and I normally do e.g. "INITRD 2.6.12". cd /boot; mkinitrd -k $1 -i initrd$1 -d /dev/hda1 -s 1024x768 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Sid Boyce wrote:
Janne Karhunen wrote:
Hi,
Just tried to install mainline kernel 2.6.12 on SUSE 9.3. Works fine, but had to assemble initrd manually. Seems that SUSEs mkinird copies modules to initrd from wrong kernel release ( 2.6.11.12 on my case ); anyone here that might have read that script through and figured out what goes ballistic with it?
I've had no problems up to 2.6.12-rc6-git8 and I'm now compiling 2.6.12, so I shall see if anything has changed when I bring it up late this evening. This is contents of my script called INITRD and I normally do e.g. "INITRD 2.6.12". cd /boot; mkinitrd -k $1 -i initrd$1 -d /dev/hda1 -s 1024x768 Regards Sid. No problems with 2.6.12. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On Sunday 19 June 2005 01:36, Sid Boyce wrote:
No problems with 2.6.12. Regards
Turns out the problem wasn't with mkinitrd ( however, it had placed wrong module versions on the image along with the right ones ), but the halt was possibly caused by udev. Reiserfs and ide modules load properly (partitions etc are detected), but /dev/hdaX device files never show up. Don't know udev well enough yet to resolve this ; to best of my understanding nothing from userspace is running at this point. -- // Janne
On Sunday 19 June 2005 09:56, Janne Karhunen wrote:
properly (partitions etc are detected), but /dev/hdaX device files never show up. Don't know udev well enough yet to resolve this ; to best of my understanding nothing from userspace is running at this point.
Seems that there's someone else with the same problem; http://lists.suse.com/archive/suse-linux/2005-May/2143.html -- // Janne
Janne Karhunen wrote:
On Sunday 19 June 2005 01:36, Sid Boyce wrote:
No problems with 2.6.12. Regards
Turns out the problem wasn't with mkinitrd ( however, it had placed wrong module versions on the image along with the right ones ), but the halt was possibly caused by udev. Reiserfs and ide modules load properly (partitions etc are detected), but /dev/hdaX device files never show up. Don't know udev well enough yet to resolve this ; to best of my understanding nothing from userspace is running at this point.
There are some postings on the kernel mailing list for this week. It seems some backlevel versions of udev are the problem. SuSE has 0.50, the latest is 058, for all I know SuSE 0.50 may equate to 058 in the rest of the world, but I have had no problems with 2.6.12 on either x86 or x86_64. One other interesting point, I have all the modules that initrd is supposed to load compiled in and in 9.2 the usb modules used to load, but on 9.3 I found that mkinitrd was needed and last week I saw on the kernel mailing list a post saying that with the new kernels mkinitrd was a must. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On Sunday 19 June 2005 14:42, Sid Boyce wrote:
There are some postings on the kernel mailing list for this week. It seems some backlevel versions of udev are the problem.
OK - i started a discussion on linux-hotplug-devel while ago; http://sourceforge.net/mailarchive/forum.php?thread_id=7543673&forum_id=3157 Let's see if this gets resolved there. -- // Janne
Janne Karhunen wrote:
On Sunday 19 June 2005 14:42, Sid Boyce wrote:
There are some postings on the kernel mailing list for this week. It seems some backlevel versions of udev are the problem.
OK - i started a discussion on linux-hotplug-devel while ago; http://sourceforge.net/mailarchive/forum.php?thread_id=7543673&forum_id=3157
Let's see if this gets resolved there.
OK, I'll watch that thread. /sbin/mkinitrd is just a bash script, so it should be easily modified, I've done it with 9.0 and 2.6.x-pre kernels to get it work right. may be someone could send me a copy of the latest script .gz and I'll take a look. My guess is it's changed round about --- [ -L "/boot/$kernel_image" ] && continue kernel_version=$(/sbin/get_kernel_version \ /boot/$kernel_image 2> /dev/null) initrd_image=$(echo $kernel_image | sed -e "s|${regex}|initrd|") if [ "$kernel_image" != "$initrd_image" -a \ -n "$kernel_version" -a \ -d "/lib/modules/$kernel_version" ]; then kernel_images="$kernel_images /boot/$kernel_image" initrd_images="$initrd_images /boot/$initrd_image" fi done Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On Saturday 18 June 2005 04:36 am, Janne Karhunen wrote:
Hi,
Just tried to install mainline kernel 2.6.12 on SUSE 9.3. Works fine, but had to assemble initrd manually. Seems that SUSEs mkinird copies modules to initrd from wrong kernel release ( 2.6.11.12 on my case ); anyone here that might have read that script through and figured out what goes ballistic with it?
-- // Janne
I've had no problems using mkinitrd when it is fed the proper arguments. man mkinitrd
participants (3)
-
Bruce Marshall -
Janne Karhunen -
Sid Boyce