[ag-automation] Antwort: Re: Antwort: Re: Booting fails with 2.6.21.6-rt21

[M.Voss at wzl.rwth-aachen.de]

I used to do it on older versions (SuSE 9.2, 9.3 and 10.0) and older 
versions of a stable "rt-patch". There the installation was not that 
comfortable like now with the makefile. I needed to copy everthing 
manually to the boot-directory and setup initrd and the bootmanager. But 
that worked out without problems on the same hardware.

Here are the steps in detail, that I did for the older versions (in german 
only) :

1. SuSE Linux standardmäßig installieren.
2. Download des Standard Linux Kernels 
   (z. B. Version 2.6.14
    ==> linux-2.6.14.tar.bz2)
3. Download des RT-Preemption Patches mit 
   passender Versionsnummer
   (z. B. Version 2.6.14-rt22
    ==> patch-2.6.14-rt22)
4. Kernel entpacken (mit "bunzip2 <filename>" 
   und danach "tar xvf <filename>")
5. Patch in das Kernelverzeichnis kopieren und anwenden: 
   folgendes im Kernelverzeichnis ausführen:
   "patch -p1 < patch-2.6.14-rt22"
6. Kernel-Standardkonfiguration in das Kernelverzeichnis 
   kopieren:
   im Kernelverzeichnis: "zcat /proc/config.gz > .config"
7. Kernel konfigurieren: 
   im Kernelverzeichnis "make xconfig" aufrufen
   Bei "Processor type and features" folgendes einstellen:
   [X] High Resolution Timer Support
       (1000) High Resolution Timer resolution
              (nanoseconds)
   Preemption Mode
       [X] Complete Preemption (Real-Time)

   Dann die Konfiguration speichern.
8. Kernel-Image kompilieren durch "make bzImage".
9. Kernel-Module kompilieren durch "make modules".
10. als "root" einloggen und im Kernelverzeichnis 
    "make modules_install" ausführen.
11. Den neuen Kernel aus dem Unterverzeichnis nach 
    "file:/boot" kopieren:
    "cp ./arch/i386/boot/bzImage /boot/RTpatchedKernel"
12. Die Datei "initrd" aus dem Verzeichnis "file:/boot" 
    folgendermaßen klonen:
    Im Verzeichnis "file:/boot" folgendes ausführen:
    "cp ./initrd ./initrd_rtpatched"
13. im Verzeichnis "file:/boot" folgendes ausführen: 
    "mkinitrd -k "RTpatchedKernel" -i "initrd_rtpatched"
14. Bootloader konfigurieren (mit Yast): 
    Neuen Eintrag für den RTpatchedKernel erstellen.
FERTIG ! 


Best regards,

Markus

--------------------------------------------------------------------- 
Dipl.-Inform. Markus Voss

Werkzeugmaschinenlabor - RWTH Aachen 
Lehrstuhl fuer Werkzeugmaschinen 
Steinbachstr. 53 B
D-52074 Aachen 

Tel:  ++49 241 80 28235
Fax: ++49 241 80 22293 

M.Voss at wzl.rwth-aachen.de
http://www.wzl.rwth-aachen.de 
-------------------------------------------------------------------- 



Carsten Emde <Carsten.Emde at osadl.org> 
22.11.2007 14:40

An
M.Voss at wzl.rwth-aachen.de
Kopie
Thomas Gleixner <tglx at linutronix.de>, "ag-automation at www.osadl.org" 
<ag-automation at www.osadl.org>
Thema
Re: [ag-automation] Antwort: Re:  Booting fails with 2.6.21.6-rt21 






M.Voss at wzl.rwth-aachen.de wrote:
>>> I have a running openSuSE 10.3 with original Kernel 2.6.22.12.
>>> I compiled a new kernel (2.6.21.6) patched with the RT-Preempt patch 
>>> according to the Installation How-To an the OSADL-website. Everything 
>>> worked fine. Even a correct entry within the GRUB bootmanager has been 

>>> generated. 
>>> But when I now try to boot the new kernel it seems to have problems 
with 
>>> the hard disk. I get the following message:
>>> "Waiting for device 
>>> /dev/disk/by-id/scsi_SATA_Maxtor_33073H3_L3HC4GBC-part2 to appear 
>>> ...................................
>>>  could not find scsi_SATA_Maxtor_33073H3_L3HC4GBC-part2"
>>> After that message I get a question I can answer Y/N... whatever I 
type, 
>>> the booting stops and I end up in a shell.
>> Hmm. Looks like the symbolic link is missing or incorrect.
>> Can you please provide the output of: ls -l /dev/disk/by-id/ 
>> for a working and a non working kernel ?
> ls -l /dev/disk/by-id
> here for the working kernel:
> [..]
> on the not-booting rt-patched-kernel I there ist no "disk" and no "sda" 
> entry in the "/dev" directory. So, there seems to be the problem... is 
> there a way to fix it?
Any SuSEologist out there? Is there a special SuSE way to replace a 
distro kernel with a native one? If so, I would like to add the 
appropriate description to the HOWTO on the OSADL Web site.

                 --cbe