Hello, does anybody know a good way to replace the SuSE 10 installtion kernal? It seems like the inst itself uses a far older version then the one that is being installed and the old one isnt able to recognize SIS761 chipset. Greets, -- Benjamin Belau Support | IVV5 | Math | uni-muenster.de Tel.: (0251) 83-33754 http://wwwmath.uni-muenster.de/IVV
Benjamin Belau wrote:
Hello,
does anybody know a good way to replace the SuSE 10 installtion kernal?
1) install kotd via YOU or 2) download latest vanilla or bleeding edge stuff from kernel.org and roll your own. I've usually done 2), but also occasionally 1). /Per Jessen, Zürich (2.37 °C) -- http://www.spamchek.com/ - managed anti-spam and anti-virus solution. Let us analyse your spam- and virus-threat - up to 2 months for free.
On Thu, 2006-01-19 at 09:30 +0100, Per Jessen wrote:
Benjamin Belau wrote:
Hello,
does anybody know a good way to replace the SuSE 10 installtion kernal?
1) install kotd via YOU or 2) download latest vanilla or bleeding edge stuff from kernel.org and roll your own.
I've usually done 2), but also occasionally 1).
That takes place -after- the install, the OP wants to replace the install kernel on the install media so it is used when the install takes place. At least that is how I read the message. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
1) install kotd via YOU or 2) download latest vanilla or bleeding edge stuff from kernel.org and roll your own.
I've usually done 2), but also occasionally 1).
That takes place -after- the install, the OP wants to replace the install kernel on the install media so it is used when the install takes place. At least that is how I read the message.
I did think of that, but decided it couldn't be - what would be the point? New hardware support? Still, replacing the installation kernel is only a matter of creating an ISO-image of CD1, mounting it, replacing the kernel, then burning a new CD. /Per Jessen, Zürich (3.75 °C) -- http://www.spamchek.com/ - managed anti-spam and anti-virus solution. Let us analyse your spam- and virus-threat - up to 2 months for free.
On Thu, 2006-01-19 at 14:37 +0100, Per Jessen wrote:
Ken Schneider wrote:
1) install kotd via YOU or 2) download latest vanilla or bleeding edge stuff from kernel.org and roll your own.
I've usually done 2), but also occasionally 1).
That takes place -after- the install, the OP wants to replace the install kernel on the install media so it is used when the install takes place. At least that is how I read the message.
I did think of that, but decided it couldn't be - what would be the point? New hardware support?
That would be my guess, maybe a raid/sata controller so there is support at install time. Maybe the OP could elaborate on this request and get further help. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-01-19 at 14:37 +0100, Per Jessen wrote:
I did think of that, but decided it couldn't be - what would be the point? New hardware support?
That his "SIS761 chipset" does not work during install.
Still, replacing the installation kernel is only a matter of creating an ISO-image of CD1, mounting it, replacing the kernel, then burning a new CD.
How do you extract the boot image from a CD? The boot image has to be given to mkisofs to create a new bootable CD/DVD from the recreated dvd tree. There is no kernel image in /dvd/boot, it must instead reside inside /dvd/boot/rescue or equivalent file. This file is a gziped file, which when expanded is detected as "Linux rev 1.0 ext2 filesystem data". When mounted (mount -o loop rescue ./mnt/) the filesystem appears: cer@nimrodel:~/tmp/rescueboot/mnt> du -sh * 3.7M bin 1.0K boot <--- 260K dev 1.5M etc 1.0K home 11M lib 3.0K media 1.0K mnt 151K opt 1.0K proc 11K root 8.3M sbin 1.0K sys 1.0K tmp 23M usr 39K var But notice that the "boot" directory is empty! So the kernel image has got to be somewhere else. Where? How? Perhaps they are in "/dvd/boot/root": cer@nimrodel:/dvd/boot> file root root.fonts root: Linux Compressed ROM File System data, little endian size 64507904 version #2 sorted_dirs CRC 0x36fda5d3, edition 0, 39127 blocks, 6971 files root.fonts: gzip compressed data, was "root.fonts 32161", from Unix, max compression This "root" file contains: 4.1M bin 512 boot <-- 3.4M etc 13M lib 307K opt 17K root 5.9M sbin 118M usr 32K var Again, no kernel images. I think they are in /dvd/boot/loader/linux: linux: Linux/x86 Kernel, Setup Version 0x203, bzImage, RO-rootFS, root_dev 0x6802, Normal VGA But, how is/are it loaded during boot? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDz7ZItTMYHG2NR9URAo0KAJoCcrhbQ27zLLXMJDzn45xrsHDkJwCfUcDY w/QZM0TH1OEe3HQd+UY4kMk= =bGum -----END PGP SIGNATURE-----
Carlos E. R. wrote:
I did think of that, but decided it couldn't be - what would be the point? New hardware support?
That his "SIS761 chipset" does not work during install.
That could perhaps be overcome by just loading an external module during install? Or is a new kernel required?
How do you extract the boot image from a CD?
I don't know - but I'm sure you can recreate it from material on the CD.
But, how is/are it loaded during boot?
Like you said, you pass some option to mkisofs identifying which boot-sector to use (or something like that). Sorry for being a little vague - I haven't researched how to create/burn a bootable CD. I still suspect Benjamins problem could be solved by loading an external SYS761 module (from floppy e.g.) at install time. /Per Jessen, Zürich (2.25 °C) -- http://www.spamchek.com/ - managed anti-spam and anti-virus solution. Let us analyse your spam- and virus-threat - up to 2 months for free.
participants (4)
-
Benjamin Belau -
Carlos E. R. -
Ken Schneider -
Per Jessen