OpenSUSE Install :: New Kernel As Part Of Auto Update?
Jan 20, 2010
the normal auto updater ran and installed a new kernel for security vulnerability and it was a .pae version. So after restart I now have 4 options on the boot screen, which includes the normal "SUSE" and a 'SUSE pae" version. defaulted to the new pae version and booted up. I got the video definition not found and had to enter a value manually. The system comes up but not into x system. It gives me a login prompt and startx yields a "terminal not found." Ran SaX2 and startx now works. Unfortunately my KDE desktop is messed up now. There are none of the normal "taskbar" at boot up started processes there. So what should I have done? how do I get my system back to normal and roll out the new kernel and all these changes?
how certain packages such as glib, yast2, etc. are part of "Online update" i.e. new versions show up there, whereas certain packages are not (e.g. NVIDIA drivers). Is it a setting on the repository, the package, or does the new version need to be labelled specifically?
Subject: grub no auto update new hard drive.doc Date: 07/26/2010 03:48:45 PM grub no auto update new hard drive.When installed 11.2 on Western Digital VelociRaptor 150 GB hard drive and now installed 300 GB VelociRaptor drive. Your grub does not update correctly to identity the op systems after the new drive is imaged; youre kidding right? I request that you provide the instruction for correcting this; you must have and auto update for grub.
I updated my fc12 x86_64 server today, and one of the updated included kernel 18.104.22.168-174.2.3.fc12.x86_64 from the previous one of kernel-22.214.171.124-174.fc12.x86_64.When I boot with that kernel, it stops when my logical volumes that are built on a raid 5 array (linux software raid built using mdadm) are not there.I can start them afterward with mdadm --auto-detect which seemingly loads the appropriate modules and starts the array, but I have never had to do this before.
Reading the mdadm man page, it mentions that this is generally done by the initrd. So, I am guessing the initrd that came with the new kernel is missing something.
The most recent update that produced the kernel version above is bit of a disaster for me. The open source radeon driver does not work with VirtualBox (it crashes at startup), and the ATI fglrx driver either builds without acceleration (or the X server loads it that way?) or fails to build.
Is there a way to undo some (or all, if necessary) of the update?
I installed the new 126.96.36.199-0.1 security update earlier today. Now, the login screen no longer responds to my keyboard. In particular, I cannot type my password to log in. If I reboot into failsafe mode, the keyboard works and I can log in.
As the title says. System is openSUSE 11.1 running KDE3.5 with KDE4.3 also installed to use desktop effects in KDE3.5. After update X uses 90% CPU to scroll down a page in FF, OOo or even in text editor, either with KWin and KWin4. With KWin4 desktop effects can't be enabled in system config.
From Xorg.conf: Code: Section "Device" BoardName "ATI Radeon HD 3200 Graphics" Driver "fglrx" Identifier "Device" Option "XAANoOffscreenPixmaps" "true" Option "Capabilities" "0x00000000" Option "OpenGLOverlay" "off" Option "FSAAScale" "0" Option "FSAAEnable" "off" Option "VideoOverlay" "on" Screen 0 VendorName "ATI" Rolling back to kernel 188.8.131.52 fixed the problem.
After the lastest update 11.2 also suffers from the problem already reported here for 11.3. I am lucky to have two linux partitions and was actualy able to boot into the second partition. From this second system I could repair this or at least a quick-n-dirty fallback to be able to boot.
1. Copied the 184.108.40.206-0.2 version for initrd and vmlinuz from /boot to /first_partition/boot 2. Copied the /first_partition/boot/grub/menu.lst.old to /first_partition/boot/grub/menu.lst to reset to the old menu.
After boot the system could start but modules were not loaded.
3. copied /lib/modules/220.127.116.11-0.2-desktop from the second partition to the first. 4. The same for /usr/src/linux-18.104.22.168-0.2*
Now my system will boot and start modules such as network and sound. Still, was this correct? I don't know for sure if there are some issues that I haven't discovered yet. And obviously, what will happen with future updates (either kernel or other)?
After upgrading kernel, system (AMD 780G)refuses to start in graphic mode. Computer services running fine, but there's nothing or some trash on screen when X started. And no way how to get out except restarting or shutting down from remote computer.
Reinstalling, unistalling ATI driver doesn't help. Also manipulations with xorg.conf (install, safe etc previous file versions)doesn't help.
Sax2 detects videocard correctly, but result is same regardless which resolution@Hz is specified.
In logfiles I just can find this
Jan 19 04:12:55 www kdm_config: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc Jan 19 04:12:55 www kdm: X server died during startup Jan 19 04:12:55 www kdm: X server for display :0 cannot be started, session disabled
Since the update to 11.3 i'm getting kernel panics randomly. Because the X server freezes and I can only force an "unexpected reboot", there is not much information I have. I installed kdump and activated it with the Yast module. I'm collecting dump files, now. But I'm not sure what to do with does files.
I updated the Kernel to 22.214.171.124-0.1-desktop. First problem was in order to do that I had to uninstall ndiswrapper. Now I have multiple entries in the bootloader, the default, the desktop, and the openSUSE 11.3 -2.6.34-12. Since I am new to linux what am I suppose to do with all those entries?
On a fresh install 11.3 gnome I am getting an update freeze on the kernel-desktop-126.96.36.199-0.5.1. This is on the initial software update after first log in on fresh system. It downloads the package and freezes during the update and causes all my other updates to reload. I went to init 3 and ran zypper update and saw that it made it to 91% and then stopped. After that I usually get a corrupted install.
I was doing a kernel update and can no longer boot into 11.3. I am dual booting with XP. I get Grub screen but no longer see Suse as a boot option, only Windows. I have tried to reinstall, but for some reason I can't get it to boot with DVD. So, is there a way that I can repair my computer without doing a reinstall?
Here's what to do right after applying the latest kernel security patch (188.8.131.52-0.4) to get the ATI driver back to work. Do not reboot yet make sure the update installed the headers and sources for kernel 184.108.40.206-0.4: rpm -qa | grep 220.127.116.11-0.4 should print the files in red on a 64bit system:
I recently installed 11.3 from DVD Am using Ubuntu Lucid Grub2 bootloader as I have several OS's Updated Grub so that the new kernel version 4 would boot but it boots to a command line... What has happened to my desktop?
This is just a nit, but I have noticed that whenever the kernel is updated, the background picture that I have set up for the login screen seems to be reset to "default_blue". No other setting seems to be disturbed.
After each update, I have to go into Configure Desktop->Login manager and set my background picture again. Why is this happening? Is there a way to fix this?
Recently I did a kernel update (compiling it manually with help of SuSE Automatic Kernel Compiler). Everything works fine and I am happy with my own settings, however there is one thing that I would to enable. On the stock kernel there is a openSUSE bootsplash on startup and a nice looking openSUSE background image in console mode. On my newly compiled kernel there is no such a eyecandies. My question is: How to enable them on my own compiled 2.6.38 kernel?
P.S In the attachment you can see what i mean with that background image in console mode, so you get my point. This is the image found on the internet, my system is openSUSE 11.4 (64 bit)
telling me if this behavior of my openSuSE 11.2 installation is normal? I use a 64-Bit openSuSE 11.2 with kernel 2.6.31.x with root partition ext4. After adding and updating from repository kernel:/HEAD/etc to 2.6.34-rc4 I can not boot anymore due to a lack of module ext4. I thought today ext4 is stable and fix built-in in the actual kernel releases, isn't it? The error message at boot time: FATAL: Module ext4 not found. Which is right because in /lib/modules/<kernelversion>/kernel/ there is NO 'fs' subfolder. Isn't the kernel:/HEAD/ repository the official update path to get a newer major kernel? (besides openSuSE's Updates for security reasons) Do you know how I can fix it without self-compiling?
I have manually added an entry for Ubuntu in my grub menu, using Yast. But every time the kernel is updated, this entry disappears. On the other hand, the one for Windows, that was added during OpenSuse's installation, is still there. So how can I keep this entry for Ubuntu ?
Edit : when I save the menu configuration in Yast, I get the following message : Code: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kbuildsycoca4 running...
I am an old days RH release user(from 6.x) and just switching back from Debian/Ubuntu to CentOS on some servers, but I can not understand the kernel update strategy currently enabled in CentOS.There are two boxes, with almost identical installation, but recently there was an auto update of kernel on one box. This auto update also seems to issue an auto reboot on the machine, which is unacceptable on server machines.
A recent kernel update seems to have misplaced the Kernel Headers. VMWare needs these headers and cannot find them. Attempting to run VMWARE gets the message: Kernel headers for version 18.104.22.168-0.2-desktop were not found.
Attempting install of 11.3 on previous 11.2 dual windows boot box. I want to format the Linux parts including /Home and retain the Win / NTFS part. (dual boot) Peculiar behavior of install DVD. Here is fdisk -l that clearly indicates a 500 GB HD and the Win partition, extended partition and the 3 basic Linux partitions and they seem okay in total.
Linux-mocx:/ # fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x252d252c
I aborted the installation. What could possibly cause the 11.2 parts and bootloader to get this wacked up ? Outside of some sound issues the 11.2 install works okay for the most part. No crashing or lockups. Really want to get up to 11.3. though. I obviously have some work to do with 35 GB of missing space on the HD and Grub living someplace on the wrong side of the river. Suggestions and a pointer or two would be most welcome guys. ( I really don't want the pain of installing that �other� OP system or I'd reformat and reinstall nice and clean.) Do I need to repartition, change mount points and reinstall Grub maybe.