Re: problem running kernel compiled on different machine

["H.S." <hs.samix@gmail.com>]

Cameron Hutchison wrote:
> "H.S." <hs.samix@gmail.com> writes:

> You can ignore these two errors. You are installing the kernel on a
> different machine to the one you built on, so those links do not work.
> That is why it deletes the links.

Okay.


>> Anybody know why I am getting this error? Also AFAIK, a 32 bit kernel
>> can be compiled on a 64 bit machine as long as it is running a 32 bit
>> OS. Correct?
> 
> Correct.
> 
>> Use menuconfig to load the current config from /boot and save and exit
>> $> cp /boot/config-`uname -r` ./.config
> 
> This looks like you are copying the config from the build machine, not
> your target. Can you confirm you actually copied the config from the
> target machine?

Initially, I was using the config from the host (build) machine. I have
since repeated the kernel compilation by using target machine's config
as well. No change in the results.


>> Then apply the patch
>> $> patch --verbose -p1 < patches-hs/firewire_trv25_bug.patch
> 
> I assume there's a typo there? Should be ../patches-hs/... and you
> should be in the linux directory if you are using patch -p1

Yes, perhaps it is a typo, but the patch actually was applied successfully.


> Otherwise it looks you've done it right.
> 
> In your later post, you show errors trying to mount /dev/hda4. The
> /dev/hd* driver is the legacy PATA driver (CONFIG_IDE). The newer driver
> based on libata (CONFIG_ATA - both SATA and PATA) uses /dev/sd* .
> 
> It looks like your fstab is set up to mount partitions based on the
> legacy driver, but you are probably using the new driver. I'd say you
> are not using the same config from the target when building the new
> kernel. Is your old target kernel also 2.6.32?

I have used the config from the target machine as well. Same results.

Host (build) machine:
Debian Unstable, AMD64 CPU, running 2.6.32-5-686-bigmem
Target machine:
Debain Testing, Intel 32 bit, currently running 2.6.32-trunk-686

Here are the grub.cfg stanzas for the current running kernel and for my
compiled kernel respectively:
#the default debian kernel
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686" --class debian
--class gnu-linux --class gnu --class os {
        insmod ext2
        set root='(hd0,5)'
        search --no-floppy --fs-uuid --set
9db23921-b7bc-4f1f-8b31-306f2126af0e
        echo    Loading Linux 2.6.32-trunk-686 ...
        linux   /vmlinuz-2.6.32-trunk-686
root=UUID=0300e89b-ae92-43f5-b1f0-0d53c2b589ca ro vga=792 quiet
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.32-trunk-686
}
#kernel compiled by me the Debian way
menuentry "Debian GNU/Linux, with Linux 2.6.32-100528-firewire" --class
debian --class gnu-linux --class gnu --class os {
        insmod ext2
        set root='(hd0,5)'
        search --no-floppy --fs-uuid --set
9db23921-b7bc-4f1f-8b31-306f2126af0e
        echo    Loading Linux 2.6.32-100528-firewire ...
        linux   /vmlinuz-2.6.32-100528-firewire
root=UUID=0300e89b-ae92-43f5-b1f0-0d53c2b589ca ro vga=792 quiet
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.32-100528-firewire
}


Thanks.


-- 

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.