Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261509AbTIWXJV (ORCPT ); Tue, 23 Sep 2003 19:09:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261670AbTIWXJV (ORCPT ); Tue, 23 Sep 2003 19:09:21 -0400 Received: from [208.158.5.221] ([208.158.5.221]:12175 "EHLO dalive.com") by vger.kernel.org with ESMTP id S261509AbTIWXJU (ORCPT ); Tue, 23 Sep 2003 19:09:20 -0400 Message-ID: <3F70D21A.4010109@flashmail.com> Date: Tue, 23 Sep 2003 19:07:06 -0400 From: DALive Editor Reply-To: dalive@flashmail.com Organization: Live Corp =?ISO-8859-1?Q?=A9?= User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Possible Kernel 2.4.22 Bug - Please advise Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 806 Lines: 31 Objective: To successfully complete my first kernel compilation, thereby upgrading my Kernel to the 2.4.22. Problem: After having sorted through literally dozens of problems, most related to my ignorance on the topic, I finally got a booting kernel image. Yet, with my new kernel, the boot sequence always fails to determine ip information, yet this always work with my old, and only working, kernel (except when there are problems with the ISP). Host Setup: -Red Hat 9.0 Distro -Grub as boot loader -2 NIC's (different) Please advise Thank you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/