🚀 go-pugleaf

Paul Furrer <elliott@web.de> wrote:
> Kernel 2.0.34 (nicht logisch). Weiss jemand, wieso noch
> immer 2.0.34 angezeigt wird ?

What does uname -a say ?

If it's still 2.0.36 -> edit /etc/lilo.conf, launch again /sbin/lilo
else it's just a RH bug.

BTW: is RH 5.1 supposed to be 2.2-upgradeable ?  Not 5.2 ??

Marc SCHAEFER wrote:
> 
> Paul Furrer <elliott@web.de> wrote:
> > Kernel 2.0.34 (nicht logisch). Weiss jemand, wieso noch
> > immer 2.0.34 angezeigt wird ?
> 
> What does uname -a say ?
> 
> If it's still 2.0.36 -> edit /etc/lilo.conf, launch again /sbin/lilo
> else it's just a RH bug.
> 
> BTW: is RH 5.1 supposed to be 2.2-upgradeable ?  Not 5.2 ??

It's not a bug, it's a feature. In RedHat the kernel is in
/boot/vmlinuz*, but when you install a kernel from the sources, it is
put in /vmlinuz.

Stefan

Hi folks

Thanks for your tips. I'll do the upgrade again and
shall check about your suggestions.

Bye
Paul


Stefan Heimers <stefan.heimers@kosta.ch> schrieb in im Newsbeitrag:
3720902E.17E5C115@kosta.ch...
> Marc SCHAEFER wrote:
> >
> > Paul Furrer <elliott@web.de> wrote:
> > > Kernel 2.0.34 (nicht logisch). Weiss jemand, wieso noch
> > > immer 2.0.34 angezeigt wird ?
> >
> > What does uname -a say ?
> >
> > If it's still 2.0.36 -> edit /etc/lilo.conf, launch again /sbin/lilo
> > else it's just a RH bug.
> >
> > BTW: is RH 5.1 supposed to be 2.2-upgradeable ?  Not 5.2 ??
>
> It's not a bug, it's a feature. In RedHat the kernel is in
> /boot/vmlinuz*, but when you install a kernel from the sources, it is
> put in /vmlinuz.
>
> Stefan

Peter Ehrbar <ehrbar@eek.ee.ethz.ch> schrieb in im Newsbeitrag:
37203005.0@pfaff.ethz.ch...
> Paul Furrer <elliott@web.de> wrote:
>
> > Ich habe soeben mein System von 2.0.34 (Redhat 5.1 & KDE 1.0) auf den
> > neuen Kernel updated. Alles hat geklappt ausser, dass ich beim Aendern
> > der Kernelkonfiguration vergass, LILO neu zu installieren. Somit kann
> > ich nochmals von vorne beginnen.
>
> Haeh?! Weshalb LILO neu installieren? Du meinst wohl 'lilo' ausfuehren.
> Ansonsten ist die Lektuere des Kernel-HOWTOs sehr zu empfehlen.
>
In meiner Installationsanleitung heisst es "Reinstalling the LILO is usually
a matter of running /sbin/lilo" und "Reinstalling" heisst doch �bersetzt
"Re-Installation" oder nicht ?
Nat�rlich kannst Du auch sagen "running /sbin/lilo" heisst "ausf�hren". Nun
ja, ich glaube wir meinen das Gleiche.

> > Nun aber meine Frage: Nach dem Update zeigte das System vor dem
> > einloggen noch immer Redhat 5.1 (logisch) und Kernel 2.0.34 (nicht
> > logisch). Weiss jemand, wieso noch immer 2.0.34 angezeigt wird ?
>
> Hmm, was heisst "das System zeigt an"? Falls Du den Login-Prompt damit
> meinst, kann der natuerlich Beliebiges anzeigen. AFAIK ist das der
> Inhalt der Datei /etc/issue. Was kommt denn bei 'uname -r' raus?
>
'uname -r' kontrolliere ich, sobald ich das Update nochmals durchgef�hrt
habe. Danke f�r den Tip.

Paul

Marc SCHAEFER wrote:

> To my knowledge, nothing automatic moves your kernel to /vmlinuz. In
> my case it would be ineffective, since I always name my kernel
> by versions (vmlinuz-2.0.37pre7).

I use make zlilo. This moves the new kernel to /vmlinuz and calls lilo
automatically. But it doesn't check if lilo.conf is appropriate.

Stefan

Stefan Heimers <stefan.heimers@kosta.ch> wrote:
> It's not a bug, it's a feature. In RedHat the kernel is in
> /boot/vmlinuz*, but when you install a kernel from the sources, it is
> put in /vmlinuz.

Well, no.  The kernel is compiled and available in arch/i386/boot/zImage,
then it's up to the user to move it to the appropriate /etc/lilo.conf
referenced place.

You can put it wherever you want. Modern distributions (such as SuSE
and maybe Red Hat) create a /boot *partition* so that the 1024-cylinder
BIOS-bug is bypassed.

To my knowledge, nothing automatic moves your kernel to /vmlinuz. In
my case it would be ineffective, since I always name my kernel
by versions (vmlinuz-2.0.37pre7).

Hi again

It worked now (however "just" with an update from 2.0.34 to 2.0.36) !

Thanks for all your suggestions.

The whole mess just arrived because I wanted to add sound to my
LINUX.

But I still DO NOT have any sound at all. I used "make xconfig" several
times and also "make config". I have an ESS Solo 1 1938 which says to
be SB compatible. I also tried using ALSA-drivers.

Nothing works. My LINUX is just making "beep".

Did anybody of you configure this sound system himself and does
have any tips and tricks ?

Thanks a lot.
Paul


Stefan Heimers wrote:

> Marc SCHAEFER wrote:
>
> > To my knowledge, nothing automatic moves your kernel to /vmlinuz. In
> > my case it would be ineffective, since I always name my kernel
> > by versions (vmlinuz-2.0.37pre7).
>
> I use make zlilo. This moves the new kernel to /vmlinuz and calls lilo
> automatically. But it doesn't check if lilo.conf is appropriate.
>
> Stefan

Paul Furrer <elliott@web.de> wrote:
> Did anybody of you configure this sound system himself and does
> have any tips and tricks ?

Give us the dmesg output pertaining to the sound system.

Marc SCHAEFER wrote:

> Paul Furrer <elliott@web.de> wrote:
> > Did anybody of you configure this sound system himself and does
> > have any tips and tricks ?
>
> Give us the dmesg output pertaining to the sound system.

Hi

Thanks a lot for all your help and
suggestions.

I am finally able to hear sound !
I did it as follows:

The point is to compile the linux-
kernel with an "m" for modules in
the sound-section (for me it was not
as clearly written in the mini-HOWTO)
and install it.
Thereafter compile the ALSA-drivers
and install them, compile the ALSA-libs
and install them and compile the ALSA-
utils and install them according to the
Alsa-sound-mini-HOWTO. Thereafter, one
should not use "modprobe snd-es1938"
but "modprobe snd-esssolo1" to play
an audio-cd and in addition to the
above "modprobe snd-pcm1-oss" to play
wav- and mid-files. With the "alsamixer"
one has to set the loudness of the speakers
after the modprobe-commands ("master" and
"AuxA" for audio-cds and "master" and "pcm"
for mid- and wav-files). With the above,
the file "conf.modules" is not necesssary
at all in order to hear sound.

Kind regards
Paul