Trial to install after the manual : grml-tips sarge

Hello
After a lot of fooling around with this one year old hardware amilopro I do not come to an end with getting a homogenous computer landscape, as all other systems at locoware.de have sarge, (with gnome, firefox, evolution except for the firewall) and a very low maintenance load. I would like to keep it that way.
But this notebook does not like the old kernels of sarge. Installation is somewhat possible. I tried original sarge installation, It did not work because of kernel now with a DVD of sarge stable , sata_via cannot be loaded and this is needed for HDD. It did something other bad with an old cdrom from the times, when sarge was testing. some more info : floppy, via_sata (error) and generic ide support stalls the installation on this sarge stable DVD
I tried then knoppix(4.01), which charged 240000 files on my HDD and is just a huge collection of lots of sources, started nicely as the DVD came with the notebook and recommendation by knoppix is anyhow to not install on a HDD.
Then I tried grml with the known compatibility problems of xservers. So I tried `grml-tips sarge`.
What is a general problem with CDROM Live systems : reply: 1. locatedb older than 8 days, very helpful, but I knew that before, I want to know if this-> or that-> file is there. going along the manual of grml-tips sarge installation was very helpful, also sda1 was found and a filesystem made with mkfs.ext3.
there is an output of mkfs.ext3 : Dateisystem wird geprüft alle .., je nachdem ..., veränderbar mit tune2fs -c oder -t must be veränderbar mit tune2fs -c oder -i =================================^ lots of downloads going on, install is fine.
but after the chroot TROUBLE vi : unkown terminal type screen.linux so lets use some other editors: pico, nano, nvi what there is in the same directory, all the same reply: unkown terminal type screen.linux As I did the chroot in a second console, I could continue to do the editing work in the first console with longer directory strings. in the chroot : no tab completion, but for a few commands okay, and no paths are found. apt-get, mount works and that is needed. horrible flashing of the whole screen when pressing cursor direction keys and backspace in position one after the prompt.
perl continued to complain LANGUAGE unset, lots of messages also i have given lang=de at the grml boot and the keyboard understands german. LC_TYPE, LC_MESSAGES and LC_ALL are all de_DE , fine. mkinitrd.conf was not there, apt-get initrd-tools fixed it.
I continued through the script, and probably made a mistake : installed kernel-image-2.6.8-2 from sarge edited lilo but did not edit the kernel line as vmlinu? in chroot: did /sbin/lilo added linux* looked okay.
Surprise at the reboot kernel 2.6.17-grml shows up. a sarge like font, a grml like kernel.
Actually this is what I wanted to have, but not in this completely uncontrolled manner.
the kernel still sits somewhere on the HDD, not over written and I ask myself Did lilo content itself when finding this kernel ??????? (this happened actually twice.)
BACK TO THE ROOTS !
1. I need a working system as reference : grml2hd -untouched ! 2. I need a sarge stable business environment with adaptions to actual hardware : sarge + 2.6.17-grml + Xserver XFree86 VESA or VESAFB 3. maybe I install a testing environment for grml 0.9.
erased all partitions : made 1 swap (sda1), one for grml 0.8 (sda2), one for sarge(sda3) just in time info that grml 0.9 is coming, erased sda3, and made sda3 and sda4 (all primary partitions) sda3 for grml 0.9 sda4 for sarge
mkfs.ext3 does not read sda4 as primary partition!!! ls does not show it either , so I make a "Erweitere" partition and eliminate sda4, sda3.
this is the typescript of the session: Script wurde gestartet: Mi 29 Nov 2006 18:47:12 CET
root@amilopro #fdisk /dev/sda
Die Anzahl der Zylinder für diese Platte ist auf 4864 gesetzt. Daran ist nichts verkehrt, aber das ist größer als 1024 und kann in bestimmten Konfigurationen Probleme hervorrufen mit: 1) Software, die zum Bootzeitpunkt läuft (z. B. ältere LILO-Versionen) 2) Boot- und Partitionierungssoftware anderer Betriebssysteme (z. B. DOS FDISK, OS/2 FDISK) Befehl (m für Hilfe): p Platte /dev/sda: 40.0 GByte, 40007761920 Byte 255 Köpfe, 63 Sektoren/Spuren, 4864 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Gerät boot. Anfang Ende Blöcke Id System /dev/sda1 1 62 497983+ 82 Linux Swap / Solaris /dev/sda2 63 671 4891792+ 83 Linux /dev/sda3 672 4864 33680272+ 5 Erweiterte /dev/sda5 672 1280 4891761 83 Linux /dev/sda6 1281 4864 28788448+ 83 Linux
Befehl (m für Hilfe): d Partitionsnummer (1-6): 6 Befehl (m für Hilfe): d Partitionsnummer (1-5): 5 Befehl (m für Hilfe): n Befehl Aktion l Logische Partition (5 oder größer) p Primäre Partition (1-4) l Erster Zylinder (672-4864, Vorgabe: 672): Benutze den Standardwert 672 Letzter Zylinder oder +Größe, +GrößeK oder +GrößeM (672-4864, Vorgabe: 4864): +5000M Befehl (m für Hilfe): n Befehl Aktion l Logische Partition (5 oder größer) p Primäre Partition (1-4) l Erster Zylinder (1281-4864, Vorgabe: 1281): Benutze den Standardwert 1281 Letzter Zylinder oder +Größe, +GrößeK oder +GrößeM (1281-4864, Vorgabe: 4864): Benutze den Standardwert 4864 Befehl (m für Hilfe): w Die Partitionstabelle wurde verändert! Rufe ioctl() um Partitionstabelle neu einzulesen.
WARNUNG: Neueinlesen der Partitionstabelle führte zu Fehler 16: Das Gerät oder die Ressource ist belegt. Der Kernel benutzt noch die alte Tabelle. Die neue Tabelle wird beim nächsten Neustart verwendet. Synchronisiere Platten. root@amilopro # init 0 Script beendet: Mi 29 Nov 2006 18:48:24 CET ls /dev/sd* does not show /dev/sda4, /dev/sda5, /dev/sda6 !
I cannot mkfs.ext3 /dev/sda5/ dev/sda6 ! no devices. /dev/sda4 cannot be found not as p-partition, nor /dev/sda5 and /dev/sda6 as l-partition. This is Wednesday 19:08
Lots of backfeed
regards

* Erich Minderlein erminderlein@locoware.de [20061129 19:15]:
[...]
What is a general problem with CDROM Live systems : reply: 1. locatedb older than 8 days, very helpful, but I knew that before, I want to know if this-> or that-> file is there.
Hm? That's just timestamp based and we won't release a new stable release every 8 days just to supress the warning. ;)
Seriously: it's just a warning message, nothing to care about on the live-cd - everything ok. On your hd-installation run 'updatedb' to update the locate database, but don't care about it on the live-cd.
going along the manual of grml-tips sarge installation was very helpful, also sda1 was found and a filesystem made with mkfs.ext3.
there is an output of mkfs.ext3 : Dateisystem wird geprüft alle .., je nachdem ..., veränderbar mit tune2fs -c oder -t must be veränderbar mit tune2fs -c oder -i =================================^ lots of downloads going on, install is fine.
mkfs.ext3 is nothing which is controlled by grml. You mean the output of mkfs.ext3 regarding tune2fs contains errors?!
but after the chroot TROUBLE vi : unkown terminal type screen.linux so lets use some other editors: pico, nano, nvi what there is in the same directory, all the same reply: unkown terminal type screen.linux As I did the chroot in a second console, I could continue to do the editing work in the first console with longer directory strings. in the chroot : no tab completion, but for a few commands okay, and no paths are found.
Just set $TERM to something like 'linux' when chrooting...
[...]
perl continued to complain LANGUAGE unset,
[...]
Just install 'locales'.
I continued through the script, and probably made a mistake : installed kernel-image-2.6.8-2 from sarge edited lilo but did not edit the kernel line as vmlinu? in chroot: did /sbin/lilo added linux* looked okay.
Surprise at the reboot kernel 2.6.17-grml shows up. a sarge like font, a grml like kernel.
Actually this is what I wanted to have, but not in this completely uncontrolled manner.
the kernel still sits somewhere on the HDD, not over written and I ask myself Did lilo content itself when finding this kernel ??????? (this happened actually twice.)
Seems you did not adjust the lilo.conf corresponding to your needs.
[...]
erased all partitions :
[...]
mkfs.ext3 does not read sda4 as primary partition!!! ls does not show it either , so I make a "Erweitere" partition and eliminate sda4, sda3.
this is the typescript of the session: Script wurde gestartet: Mi 29 Nov 2006 18:47:12 CET
root@amilopro #fdisk /dev/sda
[...]
WARNUNG: Neueinlesen der Partitionstabelle führte zu Fehler 16: Das Gerät oder die Ressource ist belegt. Der Kernel benutzt noch die alte Tabelle. Die neue Tabelle wird beim nächsten Neustart verwendet. Synchronisiere Platten. root@amilopro # init 0 Script beendet: Mi 29 Nov 2006 18:48:24 CET ls /dev/sd* does not show /dev/sda4, /dev/sda5, /dev/sda6 !
I cannot mkfs.ext3 /dev/sda5/ dev/sda6 ! no devices. /dev/sda4 cannot be found not as p-partition, nor /dev/sda5 and /dev/sda6 as l-partition.
For sure, because something is still accessing your disk so the partition table can not be reread using the BLKRRPART ioctl(). Very probably its an enabled swap partition. Take a look at output of 'swapon -s' and disable swap partitions via 'swapoff -a'.
Now guess why we disable automatic enabling of swap partitions starting with grml 0.9. ;)
regards, -mika-
Teilnehmer (2)
-
Erich Minderlein
-
Michael Prokop