Failure of Knoppix 7.2.0 with amd64 lenny

[chiendarret]

The problem I am at, is that I changed motherboard, CPU, and 2 x GPU, and the new system does not recognize the file system (grub2 on master record, raid1, md0). All other stuff is md1, LVM, vg1 seven partitions: home, user etc.

With Knoppix 7.2.0, this morning I could fully analyze this amd64 raid1, with a recent kernel. It worked nicely, although by the vendor I had no internet connection.

7.2.0 did not work, as I said, with a lenny server (kernel 2.6), while it worked with i386, recent kernel.

Knoppix 5.3.1 failed to work with the new CPU-GPU machine, while it worked with the old server.

So, it seems that one should use the Knoppix version according to the Debian kernel age of his hardware.

All that just to answer quickly your kind message. Now I am busy in getting the new machine to work (molecular dynamics). After that, should you want detailed tests from me, please ask and I'll try to do (I am a biochemist, not and expert in computers, however)

Thanks

francesco pietra

[Capricorny]

The problem I am at, is that I changed motherboard, CPU, and 2 x GPU, and the new system does not recognize the file system (grub2 on master record, raid1, md0). All other stuff is md1, LVM, vg1 seven partitions: home, user etc.

That kind of system surgery may be done fairly efficiently with Linux, and I have found old grub (legacy grub) to be simpler for such tasks. There may be any number of configuration issues involved in such a case. My experience is that one should count on them cropping up.

With Knoppix 7.2.0, this morning I could fully analyze this amd64 raid1, with a recent kernel. It worked nicely, although by the vendor I had no internet connection.

7.2.0 did not work, as I said, with a lenny server (kernel 2.6), while it worked with i386, recent kernel.

Why did you expect it to work? And the name "kernel 2.6" subsumes a few years of kernel development, through something like 39 major revisions. Again, I know nothing about Knoppix 7.2.0, but 7.0.2 easily becomes somewhat dysfunctional when you use it with older kernels. You may get it up and running, but typically some functionality will be broken because of wrong kernel modules/behavior. If you need older versions, the safest is to compile and install them, and often there will be limits to what you can do, so you may need patched versions of older kernels.

Knoppix 5.3.1 failed to work with the new CPU-GPU machine, while it worked with the old server.

So, it seems that one should use the Knoppix version according to the Debian kernel age of his hardware.

And my question is, where you got it from that you can do kernel/system mixing and matching and still have a fully functioning system? The rule is, that you have to match kernel and system carefully, which is why you should never attempt kernel swapping with Knoppix before you have got the system running in a reasonably stable way with the native kernel of the release, which is 3.3.7 for Knoppix 7.0.2. With legacy grub, you may just create a new subdirectory of the /boot directory grub works from, throw the kernel and minirt.gz (initrd) stuff in there and make an entry referring to this in /boot/grub/menu.lst. You can have several kernels/minirts there, with a menu entry for each combination.
A few days ago, I tried to install a 3.X kernel package with a 64-bits squeeze-based Knoppix remastering (running custom compiled 2.6.39.2), and I couldn't even get the package to install correctly. You may of course have luck and just graft on a different pre-compiled kernel with no apparent problems, but don't expect the world to be so kind to you next time Good luck with your dynamics application!