This shows you the differences between two versions of the page.
— |
grml_0.7 [2011/10/13 23:55] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Issues regarding grml 0.7 ====== | ||
+ | |||
+ | You found a bug in [[http://grml.org/|grml 0.7]] not yet mentioned on this page? [[http://grml.org/bugs/|Please report it via grml.org/bugs/!]] (Please don't forget to add your name and mailadress so we contact you if we have further questions.) The grml-team will add bug-reports (plus their possible fixes) to this page then. Please do not add bug reports on your own to this page if you do not provide contact information, thanks. | ||
+ | |||
+ | ===== losetup ===== | ||
+ | * Due to problems with losetup on unionfs it is not possible to create a loop device with files on the live-cd _EXCEPT_ if the file is in /home/grml, /tmp or /ramdisk. You'll notice an error like 'ioctl: LOOP_SET_FD: Invalid argument' [mika] | ||
+ | * Notice: this is not a grml specific problem. See INSTALL file in unionfs sources: "If you want to use losetup, then you need to define -DSUPPORT_BROKEN_LOSETUP. You will be able to use it read-only, but when you try to use it read-write, you will get an Oops. This should eventually be fixed when we have our own address-space operations (so that we can support sendfile)." [mika] | ||
+ | |||
+ | ===== isolinux fails with 'Could not find kernel image: grml' ===== | ||
+ | |||
+ | * Another warning you might get is 'Unknown keyword in config file'. Your BIOS seems to be broken. The problem has been [[http://syslinux.zytor.com/archives/2006-April/006784.html|reported to isolinux/syslinux upstream]]. Try to boot with 'linux26'. If this still does not work try to boot via [[http://btmgr.webframe.org/|btmgr]]. [Notice taken from [[problems|problems-webpage]]] [mika] | ||
+ | |||
+ | ===== some PCMCIA WLAN cards don't work out of the box ===== | ||
+ | |||
+ | * Deprecated pcmcia-cs was removed with grml 0.6. Now pcmciautils is state-of-the-art. Some kernel drivers (like for example PCMCIA WLAN cards) are not autoloaded by default now. They should work anyway by loading the module manually. Run for example 'hwinfo --netcard' to figure out which network module has to be loaded. (Some more information regarding the device is available via 'udevinfo -a -p /sys/class/net/eth0/'). [mika] | ||
+ | |||
+ | ===== running grml-lang with unknown parameter fails ===== | ||
+ | |||
+ | * running grml-lang using a not supported parameter outputs: "line 62: return: can only `return' from a function or sourced script"; notice: this does not affect the usability of grml-lang itself, it's just a cosmetic error (fixed in new grml-scripts package) [mika] | ||
+ | |||
+ | ===== /usr/include/linux does not link to /usr/src/linux/include/linux/ ===== | ||
+ | |||
+ | If you get errors like (for example when running 'make menuconfig' on kernel-source): | ||
+ | |||
+ | <code> | ||
+ | In file included from /usr/include/bits/posix1_lim.h:153, | ||
+ | from /usr/include/limits.h:144, | ||
+ | from /usr/lib/gcc/i486-linux-gnu/4.0.3/include/limits.h:122, | ||
+ | from /usr/lib/gcc/i486-linux-gnu/4.0.3/include/syslimits.h:7, | ||
+ | from /usr/lib/gcc/i486-linux-gnu/4.0.3/include/limits.h:11, | ||
+ | from scripts/basic/fixdep.c:113: | ||
+ | /usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory | ||
+ | [...] | ||
+ | </code> | ||
+ | |||
+ | fix it via running: | ||
+ | |||
+ | <code> | ||
+ | cd /usr/include/ | ||
+ | mv linux/ivtv.h /usr/src/linux/include/linux/ | ||
+ | rm -rf linux | ||
+ | ln -s /usr/src/linux/include/linux linux | ||
+ | </code> | ||
+ | |||
+ | Problem reported by Roberto Murer, thanks! [mika] | ||
+ | |||
+ | ===== symlink /dev/cdrom does not exist ===== | ||
+ | |||
+ | The symlink /dev/cdrom does not exist. This is not a serious problem in live-CD mode. If you are running a harddisk-installation activate the udev-rules running either: | ||
+ | |||
+ | <code> | ||
+ | # cd /etc/udev/rules.d/ | ||
+ | # ln -s ../cd-aliases-generator.rules z75_cd-aliases-generator.rules | ||
+ | </code> | ||
+ | |||
+ | or update the udev package running 'apt-get update ; apt-get install udev'. Problem reported by Gebi, fix by mika, updated udev-package by tklauser. | ||
+ | |||