Re: problem running kernel compiled on different machine
"H.S." <hs.samix@gmail.com> writes:
>I am testing a patch for the Debian kernel (regarding the firewire bug I
>reported earlier in this list). I have been sent the patch and I
>followed the Debian way of compiling the kernel after patching the source.
>( ---- Here's is the installation error -->>>>>> )
> Hmm. There is a symbolic link /lib/modules/2.6.32.100528-firewire/build
> However, I can not read it: No such file or directory
> Therefore, I am deleting /lib/modules/2.6.32.100528-firewire/build
>( ---- Here's is the installation error -->>>>>> )
> Hmm. The package shipped with a symbolic link
>/lib/modules/2.6.32.100528-firewire/source
> However, I can not read the target: No such file or directory
> Therefore, I am deleting /lib/modules/2.6.32.100528-firewire/source
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.
>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?
>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
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?
Reply to: