Andreas Jaeger wrote:

...

...

Did yast somehow give me the wrong kernel? It was the only kernel available for download and this was the first kernel upgrade I've done on this system. This system was freshly installed yesterday. Nothing outside of the suse distro is installed on it.

I just finished fixing the same issue on a 32-bit machine. The kernel is fine except the update does not execute mkinitrd which the reiserfs module doesn't like. Just boot off the CD into the rescue system. Create a directory in /tmp

Strange, I just tested on my private system (after testing yesterday at work several system) and did not encounter any problems. We had a first kernel out that was broken indeed but removed that and issued a new update :-(

Booting off the DVD into rescue mode and issuing mkinitrd fixed it for me as well. I have the following modules in initrd if it matters: scsi_mod, sd_mod, megaraid_mm, megaraid_mbox, and reiserfs. The really good news is that this kernel allows me to use USB, 8 GB ram, and the nvidia driver. Everythings looking good. Mark

From http://lists.suse.com/archive/suse-security/2004-Dec/0118.html: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following only affects SUSE Linux 9.2. We received additional reports of breakage if you have additionaly the UserMode Linux Kernel package "kernel-um" installed. In this case the system initrd will be created from "kernel-um" and not from "kernel-default" or "kernel-smp" As workaround: - If you do not need the kernel-um package, deinstall it using: rpm -e kernel-um and recreate the system initird by running: mkinitrd before rebooting. - if you need the kernel-um package, restore the symlink using: ln -sf /boot/initrd-2.6.8-24.10-default /boot/initrd (replace -default by the kerneltyp you use, detectable by: rpm -qa|grep kernel- which will be either "default", "smp" or "bigsmp".) after installing the updated packages and before booting the new kernel. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

On Saturday 25 December 2004 17:12, Detlef Grittner wrote:

Andreas Jaeger wrote:

...

From http://lists.suse.com/archive/suse-security/2004-Dec/0118.html: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following only affects SUSE Linux 9.2.

We received additional reports of breakage if you have additionaly the UserMode Linux Kernel package "kernel-um" installed.

.....

Just went into the same trap and had to revive my system by calling mkinitrd from the rescue system. But the question is: Why is the UserMode Linux package installed on my system? It is part of the kernel update ... if you look closely when doing a YOU, you will see that it is documented in the description of included packages.

If one does an online update without checking it comes along automatically. Fortunately forewarned is forearmed in my case and I managed to avoid it after seeing everyone else's problems. Waiting till it's fixed or the 2.6.10 version.

I never installed it separately and didn't even know that it is on my machine since today .

Detlef

Hello all and seasons greetings: I just got a koday cx7530. The camera is recognized automatically using the usb cable (use digikam with "usb ptp class camera" setting). Photos look great but it seems to save video as an mov file. Do any mov viewers come with suse 9.1[amd 64] ? I tried kaffeine, noatun, totem, and xine with no luck. - David Joyner

Thanks for the suggestion, but it seems mov files are not supported by xanim. Here is what I get: XAnim Rev 2.80.2 BETA by Mark Podlipec Copyright (C) 1991-2000. All Rights Reserved Video Codec: Unknown mp4v(6d703476) not yet supported.(E18) Can't Open /dev/dsp device Notice: Video and Audio are present, but not yet supported. Marcus Meissner wrote:

On Sat, Dec 25, 2004 at 12:12:31PM -0500, David Joyner wrote:

...

Hello all and seasons greetings:

I just got a koday cx7530. The camera is recognized automatically using the usb cable (use digikam with "usb ptp class camera" setting). Photos look great but it seems to save video as an mov file. Do any mov viewers come with suse 9.1[amd 64] ? I tried kaffeine, noatun, totem, and xine with no luck.

- David Joyner

try xanim ... even though it is old it might be able to handle JPEGs encapsulated in a MOV container.

Ciao,Marcus

Scott Leighton wrote:

On Saturday 25 December 2004 12:54 pm, David Joyner wrote:

...

Thanks for the suggestion, but it seems mov files are not supported by xanim. Here is what I get:

XAnim Rev 2.80.2 BETA by Mark Podlipec Copyright (C) 1991-2000. All Rights Reserved Video Codec: Unknown mp4v(6d703476) not yet supported.(E18) Can't Open /dev/dsp device Notice: Video and Audio are present, but not yet supported.

MPlayer plays some types of .mov files, you might give it a try.

That worked. Thanks!

Scott

Janis Klava writes:

...

On Saturday 25 December 2004 17:12, Detlef Grittner wrote:

...

Andreas Jaeger wrote:

...

From http://lists.suse.com/archive/suse-security/2004-Dec/0118.html: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following only affects SUSE Linux 9.2.

We received additional reports of breakage if you have additionaly the UserMode Linux Kernel package "kernel-um" installed.

.....

Just went into the same trap and had to revive my system by calling mkinitrd from the rescue system. But the question is: Why is the UserMode Linux package installed on my system?

I guess you selected at one time "kernel-development" as option to install.

...

It is part of the kernel update ... if you look closely when doing a YOU, you will see that it is documented in the description of included packages.

That's not right - the patch mentions kernel-default,kernel-smp, kernel-um, ltmodem etc - and only those that are installed will get updated. So, if you do not have kernel-um installed, it will not get updated. Otherwise everybody on the list should have kernel-um installed;-) I've been doing YOUs to a completely stock system and as you say, it is there in the included files but at no time have I ever done anything special. I

On Saturday 25 December 2004 18:38, Andreas Jaeger wrote: probably have um but I believe that was one of the features of 9.2. This bug would seem to just that, a bug in the latest update. Janis

Andreas

Fredag 24 december 2004 07:42 skrev Mark Horton:

Andreas Jaeger wrote:

...

...

...

Did yast somehow give me the wrong kernel? It was the only kernel available for download and this was the first kernel upgrade I've done on this system. This system was freshly installed yesterday. Nothing outside of the suse distro is installed on it.

I just finished fixing the same issue on a 32-bit machine. The kernel is fine except the update does not execute mkinitrd which the reiserfs module doesn't like. Just boot off the CD into the rescue system. Create a directory in /tmp

Strange, I just tested on my private system (after testing yesterday at work several system) and did not encounter any problems. We had a first kernel out that was broken indeed but removed that and issued a new update :-(

Booting off the DVD into rescue mode and issuing mkinitrd fixed it for me as well. I have the following modules in initrd if it matters: scsi_mod, sd_mod, megaraid_mm, megaraid_mbox, and reiserfs.

The really good news is that this kernel allows me to use USB, 8 GB ram, and the nvidia driver. Everythings looking good.

nvidia driver with respect to what ??

Mark

...

noticed that the new kernels reset the runlevel and powersave configurations to defaults which is really annoying.

That should not happen. I'm confused. If you have some more details and can tell me what exactly is broken, I would appreciate it,

Since I update with every YOU update, which is quite often, I did not keep track of what exactly happend when but here is what I noticed. After initial install I had to configure the powersave feature in Yast2 to get my monitor to standby and then turn of. This was quite straight forward except I think that I had to do the setup once in Yast2 to get this going even though powersaved was running (I also created my own scheme). I know this is too vague but the bottom line is the default install would not turn of my monitor. Then after one of the recent YOU updates (not the latest problematic kernel one) the monitor powersaving stopped working. I had to go into Yast2 just go through my scheme without changing anything and hit Finish which would then result in everything working fine (I didn't change any of the options and used my old scheme). Hope this helps. Brana