From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753687AbXLBXft (ORCPT ); Sun, 2 Dec 2007 18:35:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751793AbXLBXfj (ORCPT ); Sun, 2 Dec 2007 18:35:39 -0500 Received: from mx0.sover.net ([209.198.87.162]:61262 "EHLO mx0.sover.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751501AbXLBXfi (ORCPT ); Sun, 2 Dec 2007 18:35:38 -0500 X-Greylist: delayed 598 seconds by postgrey-1.27 at vger.kernel.org; Sun, 02 Dec 2007 18:35:37 EST Message-Id: <200712022336.SAA12095@granite.sover.net> To: linux-kernel@vger.kernel.org Subject: PROBLEM: loadlin incompatible with 2.6.23 kernels Date: 2007 12 02 Cc: lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com reply-to: kmh@nerdshack.com from: kmh@nerdshack.com (Kenneth Howlett) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The loadlin boot loader fails to boot 2.6.23 kernels. I used msdos 6.22 in real mode, without himem.sys or any other memory manager, without any tsrs; loadlin 1.6c; and kernel 2.6.23.1-42.fc8, which is the install kernel for the fedora core 8 distribution. The normal loadlin messages are displayed, the display is cleared and the cursor moves to the upper left corner, and then nothing else happens. No kernel boot messages are displayed. The computer does not respond to most keyboard actions, but the computer does reboot when I press control-alternate-delete. My computer is a dell dimension 4100 with pentium III 733mhz and intel chipset, and ATI radeon all-in-wonder display controller. The output of loadlin -d is: LOADLIN v1.6c (C) 1994..2002 Hans Lermen Your current LINUX kernel boot configuration is: image file: fed8.ker kernel version 2.6.23.1-42.fc8 (kojibuilder@xenbuilder1.fedora.redhat.com) #1 SMP Tue Oct 30 13:05:10 EDT 2007 kernel size: 0x001E0300 (high loaded) setup size: 0x2C00, heap: 0x1200 VGA mode: 0xFFFF command line (size 0x0013): BOOT_IMAGE=fed8.ker Your current DOS/CPU configuration is: load buffer size: 0x00F60000 EXT , setup buffer size: 0x3E00 lowmem buffer: 0x00080000 (part of load buffer) total memory: 0x040FFC00 CPU is in REAL mode SetupIntercept: YES, legal intercept, setup header version 0206 stat1: cpu in real 386 mode, no need to backswitch input params (size 0x0011): fed8.ker -d o.txt LOADLIN started from DOS-prompt Option -t set, Linux not loaded I tried using loadlin -f, and the result was the same. I tried using loadlin -noheap, and the computer rebooted itself instead of crashing. I tried using freedos 1.0 instead of msdos 6.22, and instead of crashing, the computer displayed a message saying invalid opcode, and the dos prompt returned. I tried using the 586, 686, and debug kernels from packages on the fedora core 8 dvd, and the result was the same. I tried using the pae kernel from the package on the fedora core 8 dvd, and the computer crashed like before, but this time the computer did not respond to control-alternate-delete. Loadlin works ok with older kernels. The kernel works ok with other boot loaders. I tested the integrity of my fedora core 8 dvd and it was ok. I searched the web, and the only reference I found was http://kerneltrap.org/node/14842. The first comment is from me. The person who wrote the original post seems to be compiling his own kernels; therefore this is probably a kernel problem, not a problem with the fedora core 8 distribution. The person who wrote the original post says that kernel 2.6.22.12 did not have this problem, therefore the problem probably appeared in the 2.6.23 kernels, and earlier kernels are probably ok. I do not know if the problem is with the kernel or with loadlin. Probably some people will say it is the kernel's fault, and other people will say it is loadlin's fault. I am not knowledgable about the kernel boot process, but I am guessing that the first thing the kernel does is uncompress itself, and the second thing the kernel does is set the vga or framebuffer mode. I am guessing that the clearing of the display is not done by loadlin, but is done as part of setting the vga or framebuffer mode. Therefore I guessed that the kernel successfully uncompressed itself, then got stuck setting the vga or framebuffer mode. So I tried changing the vga options. With vga=normal, the result is the same. With vga=771 (vesa framebuffer, 800x600, 256 colors), the computer crashes like before, but the cursor is not visible in the upper left corner. With vga=ask, the computer displays a message saying press enter for list, press space to continue. If I press space, the computer crashes. If I press enter, the computer displays a list of video modes. If I select 0, the computer crashes without changing the display. If I select 1, the text becomes smaller and occupies a smaller part of the display, and the computer crashes. If I select 2, the display clears and the computer crashes. With all of these crashes, the computer can still be rebooted by pressing control alternate delete. I conclude that the problem occurs after or at the end of setting the vga or framebuffer mode. The problem probably occurs before or at the beginning of probing for hardware, because no kernel boot messages are displayed after the vga=ask messages. I do not know why this occurs with loadlin and not with other boot loaders. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754390AbXLCB5w (ORCPT ); Sun, 2 Dec 2007 20:57:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751931AbXLCB5n (ORCPT ); Sun, 2 Dec 2007 20:57:43 -0500 Received: from mail.tmr.com ([64.65.253.246]:39205 "EHLO gaimboi.tmr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752140AbXLCB5m (ORCPT ); Sun, 2 Dec 2007 20:57:42 -0500 Message-ID: <4753664A.6060000@tmr.com> Date: Sun, 02 Dec 2007 21:13:30 -0500 From: Bill Davidsen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061105 SeaMonkey/1.0.6 MIME-Version: 1.0 To: kmh@nerdshack.com CC: linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels References: <200712022336.SAA12095@granite.sover.net> In-Reply-To: <200712022336.SAA12095@granite.sover.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kenneth Howlett wrote: > The loadlin boot loader fails to boot 2.6.23 kernels. > > I used msdos 6.22 in real mode, without himem.sys or any other memory > manager, without any tsrs; loadlin 1.6c; and kernel 2.6.23.1-42.fc8, which > is the install kernel for the fedora core 8 distribution. The normal loadlin > messages are displayed, the display is cleared and the cursor moves to the > upper left corner, and then nothing else happens. No kernel boot messages > are displayed. The computer does not respond to most keyboard actions, but > the computer does reboot when I press control-alternate-delete. > > My computer is a dell dimension 4100 with pentium III 733mhz and intel > chipset, and ATI radeon all-in-wonder display controller. > > The output of loadlin -d is: > LOADLIN v1.6c (C) 1994..2002 Hans Lermen > > Your current LINUX kernel boot configuration is: > image file: fed8.ker > kernel version 2.6.23.1-42.fc8 (kojibuilder@xenbuilder1.fedora.redhat.com) #1 SMP Tue Oct 30 13:05:10 EDT 2007 > kernel size: 0x001E0300 (high loaded) setup size: 0x2C00, heap: 0x1200 > VGA mode: 0xFFFF > command line (size 0x0013): > BOOT_IMAGE=fed8.ker > > Your current DOS/CPU configuration is: > load buffer size: 0x00F60000 EXT , setup buffer size: 0x3E00 > lowmem buffer: 0x00080000 (part of load buffer) > total memory: 0x040FFC00 > CPU is in REAL mode > SetupIntercept: YES, legal intercept, setup header version 0206 > stat1: cpu in real 386 mode, no need to backswitch > input params (size 0x0011): > fed8.ker -d o.txt > LOADLIN started from DOS-prompt > > Option -t set, Linux not loaded > > > I tried using loadlin -f, and the result was the same. I tried using loadlin > -noheap, and the computer rebooted itself instead of crashing. I tried using > freedos 1.0 instead of msdos 6.22, and instead of crashing, the computer > displayed a message saying invalid opcode, and the dos prompt returned. I > tried using the 586, 686, and debug kernels from packages on the fedora core > 8 dvd, and the result was the same. I tried using the pae kernel from the > package on the fedora core 8 dvd, and the computer crashed like before, but > this time the computer did not respond to control-alternate-delete. > > Loadlin works ok with older kernels. The kernel works ok with other boot > loaders. I tested the integrity of my fedora core 8 dvd and it was ok. > > I searched the web, and the only reference I found was > http://kerneltrap.org/node/14842. > The first comment is from me. The person who wrote the original post > seems to be compiling his own kernels; therefore this is probably a kernel > problem, not a problem with the fedora core 8 distribution. The person who > wrote the original post says that kernel 2.6.22.12 did not have this > problem, therefore the problem probably appeared in the 2.6.23 kernels, and > earlier kernels are probably ok. > > I do not know if the problem is with the kernel or with loadlin. Probably > some people will say it is the kernel's fault, and other people will say it > is loadlin's fault. > > I am not knowledgable about the kernel boot process, but I am guessing that > the first thing the kernel does is uncompress itself, and the second thing > the kernel does is set the vga or framebuffer mode. I am guessing that the > clearing of the display is not done by loadlin, but is done as part of > setting the vga or framebuffer mode. Therefore I guessed that the kernel > successfully uncompressed itself, then got stuck setting the vga or > framebuffer mode. So I tried changing the vga options. > > With vga=normal, the result is the same. With vga=771 (vesa framebuffer, > 800x600, 256 colors), the computer crashes like before, but the cursor is > not visible in the upper left corner. With vga=ask, the computer displays a > message saying press enter for list, press space to continue. If I press > space, the computer crashes. If I press enter, the computer displays a list > of video modes. If I select 0, the computer crashes without changing the > display. If I select 1, the text becomes smaller and occupies a smaller part > of the display, and the computer crashes. If I select 2, the display > clears and the computer crashes. With all of these crashes, the computer can > still be rebooted by pressing control alternate delete. > > I conclude that the problem occurs after or at the end of setting the vga or > framebuffer mode. The problem probably occurs before or at the beginning of > probing for hardware, because no kernel boot messages are displayed after > the vga=ask messages. > > I do not know why this occurs with loadlin and not with other boot loaders. > Lots of stuff has changed in recent versions, if you can try booting with the option "acpi=off" that might or might not be informative. Haven't used loadlin in years, and be aware that the Fedora kernel is not entirely compatible with the kernel.org releases, although that's rarely a problem. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753641AbXLDMAv (ORCPT ); Tue, 4 Dec 2007 07:00:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752753AbXLDMAo (ORCPT ); Tue, 4 Dec 2007 07:00:44 -0500 Received: from web26905.mail.ukl.yahoo.com ([217.146.176.94]:30288 "HELO web26905.mail.ukl.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752739AbXLDMAn (ORCPT ); Tue, 4 Dec 2007 07:00:43 -0500 X-Greylist: delayed 399 seconds by postgrey-1.27 at vger.kernel.org; Tue, 04 Dec 2007 07:00:42 EST DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=d0Ff+foI+6glgxCMix5qSKIpjogEWpp+zNqhXyMP3Y+w31zu9wCIipRjQR2LSy/pHAh9fIwIzzfXtv6HoZrqURoyR1yLTvZhKEP3cHhXiT4wh2KZELoGt7bkGdm7PD46uFmjVf711tyEVJtaVlfd1pD+d9IkJkv+/c6BZcX4OPA=; X-YMail-OSG: 5dsqtr0VM1k3D7BGTsyRossZAI_JOWEbNUTDgPbAbt1N_ChwRLuMKz.4bdxvV7l_f16GIGLEEpdJuh8ytphWZLNCFau3ttwQgTrvB5.UxkeVPWCB Date: Tue, 4 Dec 2007 12:54:01 +0100 (CET) From: Etienne Lorrain Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels To: linux-kernel@vger.kernel.org Cc: kmh@nerdshack.com, davidsen@tmr.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Message-ID: <462551.26009.qm@web26905.mail.ukl.yahoo.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kenneth Howlett wrote: > The loadlin boot loader fails to boot 2.6.23 kernels. Maybe not a solution with loadlin, but is it working with the "tiny.exe" version of Gujin? Download: http://www.mirrorservice.org/sites/download.sourceforge.net/pub/sourceforge/g/gu/gujin/install-2.3.tar.gz/install/tiny.exe?extract=true and execute under DOS: tiny c:\vmlinuz c:\initrd.img root=/dev/hda4 ro or maybe (to use an alternate way to collect BIOS data and the 32 bits entry point): tiny /p c:\vmlinuz c:\initrd.img root=/dev/hda4 ro To have debug data on a DOS file named "DBG" you may download: http://www.mirrorservice.org/sites/download.sourceforge.net/pub/sourceforge/g/gu/gujin/standard-2.3.tar.gz/lotiny.exe?extract=true and execute (with or without /p): lotiny c:\vmlinuz c:\initrd.img root=/dev/hda4 ro If you want that debug on screen (screen will be messy, but the last few lines may tell you the problem, and that is the only solution if the DBG file is not properly closed by DOS), download: http://www.mirrorservice.org/sites/download.sourceforge.net/pub/sourceforge/g/gu/gujin/standard-2.3.tar.gz/lodtiny.exe?extract=true and execute (with or without /p): lodtiny c:\vmlinuz c:\initrd.img root=/dev/hda4 ro It may not help if you are stuck with loadlin, but may tell if it is a kernel problem or a loadlin problem. More info for Gujin at http://gujin.org - current version v2.3 Etienne. _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755061AbZAUXKB (ORCPT ); Wed, 21 Jan 2009 18:10:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753598AbZAUXJu (ORCPT ); Wed, 21 Jan 2009 18:09:50 -0500 Received: from terminus.zytor.com ([198.137.202.10]:45713 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753355AbZAUXJu (ORCPT ); Wed, 21 Jan 2009 18:09:50 -0500 Message-ID: <4977AB27.8080608@zytor.com> Date: Wed, 21 Jan 2009 15:09:27 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: kmh@nerdshack.com CC: linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels References: <200712022336.SAA12095@granite.sover.net> In-Reply-To: <200712022336.SAA12095@granite.sover.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kenneth Howlett wrote: > I do not know if the problem is with the kernel or with loadlin. Probably > some people will say it is the kernel's fault, and other people will say it > is loadlin's fault. > > I do not know why this occurs with loadlin and not with other boot loaders. LOADLIN uses memory it isn't allowed to use by the boot protocol. Newer kernels use more memory than previous ones, and starts using memory LOADLIN expects to use. Unfortunately LOADLIN hasn't been updated for a very long time, and there doesn't seem to be much interest in maintaining it. -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754777AbZAUXoF (ORCPT ); Wed, 21 Jan 2009 18:44:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754154AbZAUXnw (ORCPT ); Wed, 21 Jan 2009 18:43:52 -0500 Received: from solo.fdn.fr ([80.67.169.19]:56744 "EHLO solo.fdn.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754112AbZAUXnv (ORCPT ); Wed, 21 Jan 2009 18:43:51 -0500 Date: Thu, 22 Jan 2009 00:43:47 +0100 From: Samuel Thibault To: "H. Peter Anvin" Cc: kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels Message-ID: <20090121234347.GI5237@const.famille.thibault.fr> Mail-Followup-To: Samuel Thibault , "H. Peter Anvin" , kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com References: <200712022336.SAA12095@granite.sover.net> <4977AB27.8080608@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4977AB27.8080608@zytor.com> User-Agent: Mutt/1.5.12-2006-07-14 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, H. Peter Anvin, le Wed 21 Jan 2009 15:09:27 -0800, a écrit : > Kenneth Howlett wrote: > >I do not know if the problem is with the kernel or with loadlin. Probably > >some people will say it is the kernel's fault, and other people will say it > >is loadlin's fault. > > > >I do not know why this occurs with loadlin and not with other boot loaders. > > LOADLIN uses memory it isn't allowed to use by the boot protocol. Newer > kernels use more memory than previous ones, and starts using memory > LOADLIN expects to use. > > Unfortunately LOADLIN hasn't been updated for a very long time, and > there doesn't seem to be much interest in maintaining it. I've fixed loadlin in debian and actually plan to maintain it upstream. I had to patch it quite a bit to make it compilable by yasm, but it can now boot recent big kernels & initrds. Samuel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755771AbZAVAQo (ORCPT ); Wed, 21 Jan 2009 19:16:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754646AbZAVAQf (ORCPT ); Wed, 21 Jan 2009 19:16:35 -0500 Received: from terminus.zytor.com ([198.137.202.10]:51447 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754569AbZAVAQf (ORCPT ); Wed, 21 Jan 2009 19:16:35 -0500 Message-ID: <4977BAC2.3060009@zytor.com> Date: Wed, 21 Jan 2009 16:16:02 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Samuel Thibault , "H. Peter Anvin" , kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels References: <200712022336.SAA12095@granite.sover.net> <4977AB27.8080608@zytor.com> <20090121234347.GI5237@const.famille.thibault.fr> In-Reply-To: <20090121234347.GI5237@const.famille.thibault.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Samuel Thibault wrote: >> >> Unfortunately LOADLIN hasn't been updated for a very long time, and >> there doesn't seem to be much interest in maintaining it. > > I've fixed loadlin in debian and actually plan to maintain it upstream. > I had to patch it quite a bit to make it compilable by yasm, but it can > now boot recent big kernels & initrds. > Excellent news! Is there a new upstream location (or do you need one)? -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755884AbZAVAZI (ORCPT ); Wed, 21 Jan 2009 19:25:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754741AbZAVAY4 (ORCPT ); Wed, 21 Jan 2009 19:24:56 -0500 Received: from solo.fdn.fr ([80.67.169.19]:33293 "EHLO solo.fdn.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754732AbZAVAYz (ORCPT ); Wed, 21 Jan 2009 19:24:55 -0500 Date: Thu, 22 Jan 2009 01:24:47 +0100 From: Samuel Thibault To: "H. Peter Anvin" Cc: kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels Message-ID: <20090122002447.GJ5237@const.famille.thibault.fr> Mail-Followup-To: Samuel Thibault , "H. Peter Anvin" , kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com References: <200712022336.SAA12095@granite.sover.net> <4977AB27.8080608@zytor.com> <20090121234347.GI5237@const.famille.thibault.fr> <4977BAC2.3060009@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4977BAC2.3060009@zytor.com> User-Agent: Mutt/1.5.12-2006-07-14 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org H. Peter Anvin, le Wed 21 Jan 2009 16:16:02 -0800, a écrit : > Samuel Thibault wrote: > >> > >>Unfortunately LOADLIN hasn't been updated for a very long time, and > >>there doesn't seem to be much interest in maintaining it. > > > >I've fixed loadlin in debian and actually plan to maintain it upstream. > >I had to patch it quite a bit to make it compilable by yasm, but it can > >now boot recent big kernels & initrds. > > > > Excellent news! Is there a new upstream location (or do you need one)? Not yet, there will be when I take some time to settle one on thefreecat.org. In the meanwhile you can just get it from debian. Samuel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753111AbZBHCIm (ORCPT ); Sat, 7 Feb 2009 21:08:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752417AbZBHCId (ORCPT ); Sat, 7 Feb 2009 21:08:33 -0500 Received: from solo.fdn.fr ([80.67.169.19]:55541 "EHLO solo.fdn.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752301AbZBHCId (ORCPT ); Sat, 7 Feb 2009 21:08:33 -0500 Date: Sun, 8 Feb 2009 03:08:28 +0100 From: Samuel Thibault To: "H. Peter Anvin" Cc: kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels Message-ID: <20090208020828.GB11308@const.famille.thibault.fr> Mail-Followup-To: Samuel Thibault , "H. Peter Anvin" , kmh@nerdshack.com, linux-kernel@vger.kernel.org, lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com, cebbert@redhat.com References: <200712022336.SAA12095@granite.sover.net> <4977AB27.8080608@zytor.com> <20090121234347.GI5237@const.famille.thibault.fr> <4977BAC2.3060009@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4977BAC2.3060009@zytor.com> User-Agent: Mutt/1.5.12-2006-07-14 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org H. Peter Anvin, le Wed 21 Jan 2009 16:16:02 -0800, a écrit : > Samuel Thibault wrote: > >> > >>Unfortunately LOADLIN hasn't been updated for a very long time, and > >>there doesn't seem to be much interest in maintaining it. > > > >I've fixed loadlin in debian and actually plan to maintain it upstream. > >I had to patch it quite a bit to make it compilable by yasm, but it can > >now boot recent big kernels & initrds. > > > > Excellent news! Is there a new upstream location (or do you need one)? Here it is: http://youpibouh.thefreecat.org/loadlin/ Samuel