I have an old Knoppix installation on a HDD with encrypted user data for which I have forgotten the password, i.e. I can no longer access my data in knoppix-data.aes. Unfortunately, I also cannot remember enough of the password such that a brute-force attack would be feasible. The HDD has two partitions SYSTEM and DATA. The latter is empty, but I noticed three very large files KNOPPIX, KNOPPIX1, and KNOPPIX2 with no filename extension inside SYSTEM. To my understanding, these files are not encrypted. - Is there any chance that either one of these three files may contain at least some of the data encrypted in knoppix-data.aes (such as digital photo albums)? - Can I simply browse/extract their content e.g. from within Ubuntu or Linux Mint, or are certain packages required which are exclusive to Knoppix?

Instead of downloading the ISO, is there a way to download all the source packages and compile it locally? I came across the following URL https://knopper.net/knoppix-sources/ and would like to know whether it is possible to somehow download everything and compile everything in sequence locally.

I have an old PC here and I want to check the HDD. I want to read it once completely into /dev/null. While doing this I want to see the speed. Because the PC is old I couldn't boot a recent Debian version. But I got Knoppix running. There is a lot of stuff on the CD but unfortunately dd does not support the status=progress option (because it's old) and pv is not installed. Any ideas? Knoppix version is 3.2.

There is some weird feature of either Compiz or KDE which allows to paint on the screen with the shortcut Win+Alt+left mouse clicks. How do I undo, erase or remove these markings?

Wife's laptop no longer boots after a failed windows (home x64) 10 update--bluescreen. I'm able to boot it with a Knoppix live USB thumbdrive. However when I mount the ntfs filesystem holding C:, I only see Default, Public, and desktop.ini in what would have been c:\Users. I've also tried a few searches using find in that filesystem for keywords of files/directories she would have had with out any luck. Is anyone able to point me in the right direction of where it might be hiding? Thank you in advance

I have this error when I try to do most things.. bash: /usr/bin/program: Input/output error This is a fresh install of the latest Knoppix, running off of a USB. The hash is correct, so I don't know what it really could be. Some dmesg output:

[ 1422.551305] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.551567] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.551832] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.552106] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.552367] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.552635] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.552907] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.553185] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.553476] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.553729] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.554017] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.554350] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1422.554678] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1481.701353] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1481.701356] print_req_error: 34 callbacks suppressed
[ 1481.701358] print_req_error: I/O error, dev cloop0, sector 6375040 flags 0
[ 1481.701615] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1481.701617] print_req_error: I/O error, dev cloop0, sector 6375040 flags 0
[ 1481.702060] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1481.702062] print_req_error: I/O error, dev cloop0, sector 6375216 flags 0
[ 1481.702319] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1481.702321] print_req_error: I/O error, dev cloop0, sector 6375216 flags 0
[ 1633.631162] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0
[ 1633.631170] print_req_error: I/O error, dev cloop0, sector 6375040 flags 0
[ 1633.631815] cloop: decompression error -3 uncompressing block 12451 70223 bytes @ 1154490597, flags 0

Full dmesg output: http://0x0.st/i5py.json

I am trying to check certain specifications of a hard drive on a computer with no operating system installed. I am using a Knoppix bootable disk (v8.6.1) to run a bash script with the line smartctl -i /dev/nvme0 However, I keep getting the same message: > Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Bad address I can run this command just fine on another computer (same model) with a different Linux distribution already installed, but for some reason the command fails when running on the Knoppix disk. Note: I can run commands like smartctl -d nvme --scan which outputs > /dev/nvme0 -d nvme # /dev/nvme0, NVMe device but I cannot run smartctl commands such as smartctl -i /dev/nvme0 smartctl -x /dev/nvme0 smartctl -a /dev/nvme0 smartctl -H /dev/nvme0 or any other command that should actually return information about the hard drive. They all produce the same "bad address" message stated above.

**Summary:** How do I make the following cheat-code permanent on knoppix 8.6.1 on usb stick, because filesystem type is iso9660 (read-only) and won't let me edit /mnt-system/boot/isolinux/isolinux.cfg. **Cheat code entered at boot prompt:** knoppix xmodule=vesa **Full Details:** I've just put knoppix 8.6.1 on a usb stick (persistence was there by default). But X Window won't display unless I enter the cheat-code "knoppix xmodule=vesa" at the initial boot prompt. Incidentally, when using Knoppix 7.7.1 on a usb stick, on the EXACT SAME laptop (Acer Aspire 5755G), I don't need the cheat-code. I'd like to **not have to type the cheat-code in every time** I boot the 8.6.1, and believe that I can achieve that by adding "xmodule=vesa" as a kernel parameter on an "APPEND" line in /boot/isolinux/isolinux.cfg. I can get to that file using the path /mnt-system/boot/isolinux/isolinux.cfg. **But it won't let me write** to that file because /mnt-system is mounted read only. When I try to remount /mnt-system as read-write, it says "write-protected." /UNIONFS **is** mounted as read-write, but the path /UNIONFS/boot/isolinux/ does not exist. I understand that because partition 1 (the main Knoppix system) is filesystem type iso9660*, that it is by definition read-only. (*On which I believe /boot/isolinux/isolinux.cfg sits). **Main Question:** So could you tell me please, what method I need to use to make my cheat-code permanent? **Reason for Using 8.6.1:** I'm trying out 8.6.1 because it has a newer kernel than 7.7.1, and I've read that a newer kernel might fix my problem of downloads halting when the lid is closed. I've already tried many lid disabling methods, but none of them prevent the downloading from halting.

I have an old Knoppix CD V4.0.2 Kernel 2.6 dated 2005-09-23. It is too old to boot on any machine I have (I think because it does not have SATA support). It says Can't find knoppix filesystem, sorry. I would like to find a way to access the files in the CD without booting it. I assume this is some sort of mount of a file on the CD. I can access the files on the CD from linux (Ubuntu) with no problem. There is a large (600MB) file called KNOPPIX, and I have tried things like: mount -t auto -o loop KNOPPIX /media/tmp but it does not work. Is there a way to see the files that would be present on the filesystem after KNOPPIX boots and mounts its drives?

This question is about the optional encryption of user data with the live Linux distribution KNOPPIX v6.2 (2009-11-18), which as I understand is based on Debian. I do not use this old version anymore, but I am trying to retrieve years-old data from the persisted data file **knoppix-data.aes** created by KNOPPIX v6.2 in the startup prompts. The file is one byte less than 4 GiB. I was hoping someone who knows about Linux encryption standards going back to the late 2000s might be able to provide some information about this file (as I shall explain below). I'm not very familiar with Linux encryption standards, and am a bit overwhelmed by the myriad of terms I see (like "LUKS", "dm-crypt", etc.) -- I'm not certain which, if any, applies to my situation with late 2000s Knoppix. Obviously the ".aes" in the file name indicates AES encryption. At first I suspected I was typing the password incorrectly, but now I wonder if there might be another issue that would render my attempts to correctly type the password futile. I will explain: When I view the file with a hex editor, it's surprising to see that the beginning of the file is a cleartext list of file names and hashes, e.g.: f4374a5897aafd09a2439f6c3f4a961d5cc7c1a1 *autorun.bat eaf953dce8de1442e4e32769260e22435a70f3bc *autorun.inf (etc.) (also included are hashes for many files that obviously relate to Knoppix, such as **KNOPPIX/knoppix-logo-small.png**, to give one example) The beginning bytes seems to match exactly with the plaintext file **/mnt-system/KNOPPIX/sha1sums** (on the USB drive where Knoppix is installed, so it's apparently part of the Knoppix installation). After that there are expanses of null bytes (00), and then random gibberish. I was expecting the entire thing would be random gibberish; in the context of AES encryption, the cleartext at the beginning of the ".aes" file would seem to be incongruous. As a test, I powered off, renamed the original AES file, and then rebooted and created another **knoppix-data.aes** that is 256 MiB, with password "123456789". This one does not contain the cleartext at the beginning, and I am able to write to it (and successfully decrypt it on subsequent boots). But I don't know about this opaque file format (or where the documentation for it is), other than it (presumably) involves an AES algorithm (but I have no details about mode of operation, key derivation, header, etc.). In particular, is it normal to have this cleartext stuff (sha hashes and file names) at the beginning of the file, as some kind of header, perhaps? Or would it indicate that the file has somehow become corrupted (such as by being concatenated with the **sha1sums** file in some bizarre circumstances)? If the answer is that it's normal for the cleartext sha1 sums to be there, does that mean I need to provide an offset to **losetup** to move past the cleartext? I'm currently using echo "mypassword" | losetup -p 0 -e aes -k 256 /dev/loop2 knoppix-data.aes mount /dev/loop2 /media/mydir/ to avoid having to reboot every time I want to attempt decryption. This works for the 256 MiB test version of **knoppix-data.aes**, with password "123456789" and with no cleartext at the beginning, but not for the original 4 GiB file that has the cleartext hashes (it complains about the file system not being specified, which presumably means that it cannot be automatically determined, which presumably means that the decryption produced gibberish rather than the desired data, possibly because the cleartext is not supposed to be there, or because **losetup** needs an offset to move past it).

I'm trying to set up a PXE boot server for multiple different OSes. So far I have it working with Linux Mint, Arch Linux, and a GParted image. I'm trying to do Damn Small Linux completely within RAM, so the host doesn't have to stay connected to the network to work. I followed this tutorial: http://damnsmalllinux.org/f/topic-3-26-15960-0.html However, I get the following screen when I try to boot it: vesafb: scrolling: redraw vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0 Console: switching to colour frame buffer device 100x37 fb0: VESA VGA frame buffer device pty: 256 Unix98 ptys configured FDC 0 is a S82078B RAMDISK driver initialized: 16 RAM disks of 100000K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX3: IDE controller at PCI slot 00:01.1 PIIX3: chipset revision 0 PIIX3: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xc300-0xc307, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xc308-0xc30f, BIOS settings: hdc:pio, hdd:pio ide: late registration of driver. SCSI subsystem driver Revision: 1.00 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 Initializing Cryptographic API NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 bind 32768) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 49583k freed VFS: Mounted root (ext2 filesystem). kmod: failed to exec /sbin/modprobe -s -k block-major-3, errno = 2 VFS: Cannot open root device "" or 03:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 03:02 I'm not sure what I need to do here. My minirt24.gz is available for inspection at https://k7dxs.xyz/files/minirt24.gz , and here is the relevant portion of my pxelinux.cfg/default: LABEL Damn Small Linux LINUX dsl/linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=789 initrd=dsl/minirt24.gz nomce noapic loud BOOT_IMAGE=knoppix frominitrd nopcmcia noagp noswap base

A computer illiterate family member asked me to recover photos from an SD card she used in her camera. She went to fetch them from her computer when it informed her that the device needed to be formatted. She swears that she didnt proceed with the format and asked if I knew how to fix it. I use a Knoppix boot cd that I like because it comes prebundled with ddrescue and other tools. Plugging the card into my built in reader, it recognized the device under /dev/sdc however it didnt automatically mount. I ran the command ddrescue -d /dev/sdc /media/sdb1/test.img /media/sdb1/testimage.log The output suggested it ran perfectly fine. It successfully read all 16GB and reported 0 errors. When I opened the img file in a hex editor however it was 16GB of zeros. I wasnt sure if ddrescue was just silently failing at every read attempt and just writing a zero, so I also tried plain vanilla dd and got the same result. Everything about the card appears to be fine, it is apparently just empty. Normally I am used to when memory controllers on these cards start to go bad that they misreport the memory size or there are bad sectors but here it all just seems like a happy factory fresh SD card. Of course she is tech illiterate so i cant rule out that she accidentally zero filled the thing but I would think if anything she would have accidentally quick formatted it and blew away the partition table leaving the bytes at address intact. Is there anything I might be missing or doing wrong here or is the card just completely hosed?

I've booted *Knoppix* with *Compiz* window manager on my MacBook and I've accidentally added a fire effect on the screen by holding ⌘-Shift and clicking on the screen. Now I see a fire burning effect on my screen. Changing desktop doesn't help. How to destroy/remove that fire effect? What would be the keyboard shortcut to do that?

I've got a problem when I unplug and then plug in LAN cable, the eth0 connection stops working, also LAN LED is off. If I restart the system, LAN connection is normal. This happens only to onboard LAN port. LAN ports on NIC adapters don't have this issue.

I'm trying to boot KNOPPIX to RAM from the grub prompt. Booting using grub> set root=(cd1) grub> linux /boot/isolinux/linux lang=en grub> initrd /boot/isolinux/minirt.gz grub> boot works just fine, but adding the toram parameter causes it to get stuck after pressing Enter on boot. I've seen this question where the poster uses loopback loop /boot/iso/knoppix.iso and bootfrom=.../boot/iso/knoppix.iso. I've tried adding both using /KNOPPIX/bootonly.iso, which is the only .iso file I was able to find on the CD, neither of which helped. I know I should be able to boot the OS to ram from grub as I've done this with other distros. Is there something I'm missing?

Summary: I want to use the live knoppix DVD (KNOPPIX_V7.0.2DVD-2012-05-30-EN.iso) to do a virus check on my laptop and then to do some repartitioning. After booting the live DVD, at the moment I'm just leaving the laptop sat doing nothing, while I work on another computer. But after half an hour to an hour, the laptop gets disturbingly hot to the touch near the fan underneath (see Full Details below for exact location). It feels about 50 or 60 degrees C to the touch. My question: Is there a power-management program (or whatever) that isn't running on the DVD, but should be? What can I do to stop the laptop overheating? On this same laptop, I also have the live DVD installed on the hard drive. And when I use it from the hard drive, there is no overheating. The area near the fan is then about 25 to 30 degrees C to the touch. Full Details: The problem is repeatable - every time I use the laptop booted from the live DVD, the overheating occurs. The fan is about 2 1/2 inches in from the left edge of the laptop, roughly under number-key "3" on the keyboard (above the qwerty keys). The hot area extends from the fan to the left edge of the laptop, and down towards the front of the laptop by about 4 inches. The laptop is an Acer Aspire 5755G.

I am trying to use the setup at [this link](http://ftp.free.fr/mirrors/ftp.knoppix.org/contrib/knoppix-webserver-setup/) to set up a LAMP server on my Knoppix USB drive. I have seen in multiple places that Knoppix comes with Apache, MySQL, and PHP; however I am unable to find anything of the sort. The setup from the link *requires* this to be present, as is evident by viewing the source code of SETUP. Should I install the needed packages manually, or is there some way to launch the builtin versions that I do not know of? Note: dpkg -l apa* returns no packages and dpkg -l http* just returns some httptunneling package.

I have created a bootable USB drive with Knoppix. It works fine, but I was specifically looking for chntpw and a tool to wipe a HDD. This question is about where to find a package (chntpw) that Synaptic Package Manager says is already installed. How do I find an application that's already installed? I have looked through the menus, but I don't see it anywhere. Thanks, Jono

I've been looking on the web and through the few Knoppix books I have. I cannot see where to locate the hard drives for a CentOS server I've booted with Knoppix. I am booting the CentOS server with Knoppix, so I can run fsck on the disk. The server hangs during boot.

I'm using VMware on windows to run Knoppix but the default resolution is too small and changing the resolution each time I load it with su xrandr is annoying. Is there a way to change the default resolution permanently?