[SOLVED] Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-17 Thread Omer Zak
On Wed, 2006-03-15 at 09:14 +0200, Omer Zak wrote: > Several days ago I complained about being unable to boot from newer > kernels after doing a routine upgrade of Debian Etch (Testing). > > Now, I found document about initrd replacements in Debian: > http://wiki.debian.org/InitrdReplacementOption

Initrd woes after upgrade from vanilla Debian Testing

2006-03-14 Thread Omer Zak
Several days ago I complained about being unable to boot from newer kernels after doing a routine upgrade of Debian Etch (Testing). Now, I found document about initrd replacements in Debian: http://wiki.debian.org/InitrdReplacementOptions -- Every good master plan involves building a time machin

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-06 Thread Omer Zak
Hello Haggai, Can you please let me (and if not too long - also the Linux-IL members) know how exactly you invoke yaird and what other steps you need to do to get 2.6.15 to boot from Debian Testing? [I do not think I'll need the "software suspend 2" patch, so if there is clean separation of the ste

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-06 Thread Shachar Shemesh
Let me try and summarize for the non-kernel hackers: Traditionally, the way to boot linux was by setting attributes inside the kernel image that would hardcode the location of the root partition. This would either be picked by the kernel build system and copied from the machine on which the kernel

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-06 Thread Haggai Eran
I'm using debian testing with a 2.6.15 kernel. I'm using (almost) standard yaird initrd file to boot, except I patched it to support software suspend 2. -- Haggai Eran On 3/6/06, Omer Zak <[EMAIL PROTECTED]> wrote: > Question to anyone who uses Debian Testing and is successful in running > kerne

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-06 Thread Omer Zak
On Mon, 2006-03-06 at 11:19 +0200, Shachar Shemesh wrote: > As for your problem, I'm not sure what to recommend to you. Try to > install "mkinitrd" and run it manually, see whether images it create > work better. make sure that yaird is installed. RTFM yaird and run it > manually. Other than that,

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-06 Thread Shachar Shemesh
Omer Zak wrote: >Thanks also to Gilboa Davara, Gilad Ben-Yossef and Muli Ben-Yehuda for >responding to this. > >Now, I need the techl's: > >1. What (if any) should I write in the grub.conf file in my laptop to >properly boot from /boot/vmlinuz-2.6.15-1-686? > >2. Is there any other configuration,

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-05 Thread Muli Ben-Yehuda
On Mon, Mar 06, 2006 at 08:47:32AM +0200, Gilad Ben-Yossef wrote: > I wonder if enough people are interested in a talk about early user > space. +1 from me. I'm always interested in kernel talks. Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-05 Thread Gilad Ben-Yossef
Shachar Shemesh wrote: Gilad Ben-Yossef wrote: This approach will allow in the future to throw out all the code in the kernel that has anything to do with finding the root file system, mounting NFS as root fs, kernel DHCP and IP setting (aka autoconfiguration) and replacing them will "early us

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-05 Thread Omer Zak
Thanks also to Gilboa Davara, Gilad Ben-Yossef and Muli Ben-Yehuda for responding to this. Now, I need the techl's: 1. What (if any) should I write in the grub.conf file in my laptop to properly boot from /boot/vmlinuz-2.6.15-1-686? 2. Is there any other configuration, which I need to carry out?

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-05 Thread Muli Ben-Yehuda
On Sun, Mar 05, 2006 at 05:01:24PM +0200, Shachar Shemesh wrote: > In short, I don't understand why a new technology was necessary. http://lwn.net/Articles/14776/ http://lwn.net/Articles/14448/ It provides an early userspace environment to do a bunch of things in that used to be done in the kern

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-05 Thread Shachar Shemesh
Gilad Ben-Yossef wrote: > This approach will allow in the future to throw out all the code in > the kernel that has anything to do with finding the root file system, > mounting NFS as root fs, kernel DHCP and IP setting (aka > autoconfiguration) and replacing them will "early user space" - user >

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-05 Thread Gilad Ben-Yossef
Shachar Shemesh wrote: IIRC, they are using a new mechanism to generate an initrd replacement (this is NOT an initrd in the usual sense of the word, but something understood by the kernel directly). Sadly, I don't know the precise details of the change. Perchance one of the kernel devs on this l

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-04 Thread Shachar Shemesh
Omer Zak wrote: >Does anyone know what happened and how to repair the initrd.img? >The current version of initrd-tools is 0.1.84. Should I try to >downgrade it to a previous version? > > Quite frankly, I'm no longer using Sid/Testing as a primary platform, so I'm not entirely up to speed on the

Re: Initrd woes after upgrade from vanilla Debian Testing

2006-03-04 Thread Gilboa Davara
On Fri, 2006-03-03 at 22:50 +0200, Omer Zak wrote: > Today, after few days, I upgraded the Debian Testing (Etch) installation > on ThinkPad R40e laptop to have the most recent package versions. > > The laptop has few kernels - among them I have 2.6.15-1, 2.6.12-1 and > 2.6.8-2. > The 2.6.15-1 neve

Initrd woes after upgrade from vanilla Debian Testing

2006-03-03 Thread Omer Zak
Today, after few days, I upgraded the Debian Testing (Etch) installation on ThinkPad R40e laptop to have the most recent package versions. The laptop has few kernels - among them I have 2.6.15-1, 2.6.12-1 and 2.6.8-2. The 2.6.15-1 never worked for me, when I try to boot it, it locks up sometime du