Knoppix 3.6 remaster - 2.6 kernel can't find filesystem?

[PMT]

Okay. I've been banging my head against the wall since Friday, trying to figure this out.

Whenever I roll my own 3.6 CD, the 2.4 kernel loads perfectly fine, but the 2.6 kernel drops me out to Can't find KNOPPIX filesystem, sorry. with no additional errors listed.

I haven't installed any modules or screwed with the kernel in any way.

Heck, I even tried redoing it four seperate times, to make sure I didn't touch the kernel...

Am I missing something obvious? I would really like 2.6 to load properly.

EDIT: Oh, and on a relevant note, the standard KNOPPIX 3.6 CD works perfectly, in either kernel.

EDIT 2: Oh, and by 2.4 kernel works perfectly, I mean it warns that /etc/modules.conf is newer than the 2.4 one, but I know I never edited it. Perhaps apt-get upgrade did? I did turn down the kernel upgrade of 2.4, however...so I'm at a loss.

[Steve F]

Well, one thing for sure, running apt-get upgrade can be risky. I read in the HowTo's that one of the first things you should do after copying the uncompressed file system to a directory is chroot and run apt-get update. I did that the first times I tried to remaster and always resulted in broken knoppix. I stopped doing that. My remastering involves taking away every package not necessary for a boot to shell. I haven't needed to upgrade anything. Then I can add the packages I want. I control the versions by setting apt sources to the distribution release I want. That way I can manage on a package by package basis the version dependencies.

Have you tried copying the uncompressed file system and then recompress it without doing any other changes? Does that boot?

[PMT]

Okay. See, I just tried a burn with only KDE 3.3, Gweled, zSNES, Abiword, Logjam, VisualBoyAdvance, KPlayer, and MPlayer. 2.4 boots into KDE 3.3 perfectly, but can't use the IPW modules since they were 2.6 compiled.

2.6, of course, still gives that FS error.

[PMT]

Okay. I swear this is a problem with KNOPPIX, somehow.

I installed Gweled, Abiword, Logjam, and removed openoffice and associated non-English locales.

That's it. And 2.6 still dies on boot with a "Cannot find KNOPPIX filesystem, sorry." and no error listed.

Please, somebody tell me what I'm doing wrong.

EDIT: Oh, and on my latest attempt, I'm receiving permissions errors in 2.4 kernel loading KDE, saying it has permission denied to write /tmp. I've never gotten that before.

[build6]

I have encountered a similar problem that I think has the same root cause (I'm thinking some phase during the filesystem search/mount stage) with v3.6 (2004-08-16-EN). I have a empty system with 3 partitions (hda1-4, hda2 being a 2GB or so swap partition). I previously booted knoppix with tohd=/dev/hda3|4, but now, when I try to reboot, *even from* the Knoppix CD, I end up with the same error message and get dropped to shell. There's nothing wrong with the CD because I can boot up another machine successfully with it. My original guess was that the script (?) that is responsible for mounting the base knoppix filesystem gets confused upon finding multiple cloop-compressed KNOPPIX filesystems on the hard disk, but of course I could be wrong...

[MarshallBlake]

I had the same problem. What fixed it for me was using the following command at the "boot:" prompt:

knoppix nodma

[rooksmahn]

I have the same problem too with 3.6. I'm not a linux admin so I'm out of my element with this OS.

I haven't tried this CD with another system yet, but my suspicion is with the CDROM. It an IBM BladeCenter which uses a USB CDROM. I have a feeling it is having problems mounting this volume.

I did try booting with "knoppix nodma" with the same result.

I will try the CD in another non-usb cdrom to make sure the cd is not the problem. I was hoping to find an easy answer but I guess I won't be that lucky this time!

[rooksmahn]

so I just tested the same cd on another system and it worked fine. So it's definitely something to do with the CDROM and how it accesses it. In this case it used /dev/scd0 to mount the cd (if I'm using the right terminology here). At this point it will be faster for me to have the UNIX Admin jumpstart this box with Redhat than to mess around more with this. If I find an answer though I will post it.

[rooksmahn]

BTW

I have not tried altering the original distribution at all. I just downloaded the 3.6 version, checked the MD5 checksum matched, and burned it to cd.

[rooksmahn]

A little more info. Apparently someone else is having the same issue, and someone else said they have no problems booting with a USB CDROM.

I'm going to try updating the BIOS on the blade and see if that makes a difference. Wouldn't put my money on it but it's worth a try.

Here's the link to the other posting if anyone is interested:

http://www.knoppix.net/forum/viewtopic.php?t=14649