H.S. wrote: > H.S. wrote: >> 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. >> >> The kernel was compiled (and the deb created) on an AMD64 bit machine >> which is running a 32 bit kernel (2.6.32-5-686-bigmem). The deb created >> can be installed without any problems on this host machine. However, if >> I try to install that deb on a target machine (Intell 32 bit processor), >> the installation gives errors and I cannot boot into that kernel: > <SNIP> > > Some more info. I tried the --initrd this time while compiling the > kernel with the above mentioned patch. So different. <SNIP> > > My next step is compile the ext3 support in the kernel and not as a > module.
Well, nothing has worked. I have tried the config file from the host machine, with and without compiling the file system options within the kernel (or as a module). I have used config from the target machine, with and without compiling the file system as compiled in (or as modules). I am getting the same error. Basically, the boot fails at file system check. Just a recap: I am trying to compile a kernel (on a machine running Unstable) from linux-source-2.6.32 for a different machine (running Testing). The compilation goes well, but I cannot boot in to the target machine using the compiled kernel. So, what am I missing here? Or this is a bug? -- 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/htvgv9$79...@dough.gmane.org
