[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

2.4 -> 2.6

Hi Kyle,

	Here's what I hear you saying:

1. Copy the lines below into a file and put that on the J6000. I did this
and it's in a file /tmp/mkinitrd.txt.

2. cd /usr/sbin (probably not necessary, but I don't know what a/mkinitrd
and b/mkinitrd mean)

3. patch -p1 </tmp/mkinitrd.txt

4. apt-get remove kernal-image-2.6.8-2-32-smp (I had already installed it
before I got this email)

5. apt-get install kernal-image-2.6.8-2-32-smp (this should create the new

6. double check palo.conf and run palo.

7. reboot

Sorry to be such a newbie, but I've wasted so much time on this that I would
really appreciate it if you would double check me.



-----Original Message-----
From: Kyle McMartin [mailto:kyle@debian.org]
Sent: Friday, February 25, 2005 5:16 PM
To: Harry Cochran
Cc: debian-hppa@lists.debian.org
Subject: Re: Anyone know where 2.4.26-pa5-32-smp is?

On Fri, Feb 25, 2005 at 04:06:45PM -0500, Harry Cochran wrote:
> 	I originally had the "Searching for devices" problem on 2.4.27-32-smp.
> However, like you, I loaded 2.4.27-32 on my C3000 with no problem. At this
> point, I'm moments away from getting to 2.6.8-2-32-smp I hope. I'm just
> waiting to hear back from Thibaut before I do something dumb again and
> another 2 hours.


Could you please apply the following patch to /usr/sbin/mkinitrd? You
can copy it to your home directory, and apply it with something like
# patch -p1 </home/hcochran/mkinitrd.diff

--- a/mkinitrd  2005-02-25 17:01:18.786866158 -0500
+++ b/mkinitrd  2005-02-25 17:01:36.109329936 -0500
@@ -589,6 +589,7 @@
                                s/^isp2x00$/qlogicfc/; t
                                s/^ncr53c7xx$/53c7,8xx/; t
                                s/^ncr53c8xx$/sym53c8xx/; t
+                               s/^sym53c8xx_2$/sym53c8xx/; t
                                s/^A2091$/a2091/; t
                                s/^A3000$/a3000/; t
                                s/^Amiga7xx$/amiga7xx/; t

The patch is also available at,

The root of the problem is that mkinitrd, which builds the initrd
that loads all the drivers required to mount your root filesystem, finds
modules by looking at the name the scsi driver places in /proc/scsi/. Since
sym53cxx_2 was renamed to sym53cxx (and the original deleted), mkinitrd
is unable to find module corresponding to the entry. This sets up a mapping
from the old name (in 2.4) to the new module name (in 2.6).

Hope this helps,
	Kyle M.

Reply to: