VectorLinux

The nuts and bolts => Kernel => Topic started by: flip city on August 16, 2009, 11:28:53 am

Title: DANGER-Will Robinson!!
Post by: flip city on August 16, 2009, 11:28:53 am
ALERT LINUX KERNEL COMPROMISE http://www.theregister.co.uk/2009/08/14/critical_linux_bug/ (http://www.theregister.co.uk/2009/08/14/critical_linux_bug/) :-[
Title: Re: DANGER-Will Robinson!!
Post by: kc1di on August 16, 2009, 01:03:38 pm
it's already been pactched should be in the repository soon.
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 16, 2009, 06:05:54 pm
A patched kernel for 6.0 is here:
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/kernels/kernel-2.6.27.29-i686-1vl60.tlz
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/kernels/kernel-modules-2.6.27.29-i686-1vl60.tlz
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/kernels/kernel-src-2.6.27.29-i686-1vl60.tlz

and 5.9 here:
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-5.9/kernels/kernel-2.6.27.29-i686-1vl59.tlz
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-5.9/kernels/kernel-modules-2.6.27.29-i686-1vl59.tlz
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-5.9/kernels/kernel-src-2.6.27.29-i686-1vl59.tlz

Thanks to rbistolfi for building the 5.9 kernel

Uelsk8s
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 16, 2009, 06:14:39 pm
Do we install these like regular packages? Should we modify LILO to allow a choice between the old kernel and the patched kernel? I need a little guidance about how to install these.
--GrannyGeek
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 16, 2009, 06:35:59 pm
download the kernels and install like any other package.
You will need the kernel and kernel-module packages, the kernel-src package is optional and only needed to build kernel and drivers
After you install run vliloconf or manually add the new kernel to your bootloader.
After rebooting with the new kernel and verifying that it works on your system, you may remove the older kernel if you want.
Title: Re: DANGER-Will Robinson!!
Post by: Daniel on August 16, 2009, 06:47:25 pm
Since this is apparently a major security patch, will it be included in the downloadable vl60 iso files from the download page on vectorlinux.com so it won't have to be added after installation?
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 16, 2009, 07:34:21 pm
Thanks for the directions. I'll try it  now.
--GrannyGeek
Title: Re: DANGER-Will Robinson!!
Post by: flip city on August 16, 2009, 08:07:37 pm
download the kernels and install like any other package.
You will need the kernel and kernel-module packages, the kernel-src package is optional and only needed to build kernel and drivers
After you install run vliloconf or manually add the new kernel to your bootloader.
After rebooting with the new kernel and verifying that it works on your system, you may remove the older kernel if you want.

OK...just to be on the safe side...download the kernel packages, right click on package, click install package, enter root pw. After installation then change the /boot/grub/menu.lst to reflect the new kernel. This ONLY applies to those that are using GRUB as the bootloader !
What script do you use to remove the old kernel ?
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 16, 2009, 08:14:59 pm
removepkg kernel-2.6.27.12-i686-1vl60

make sure you use the complete old kernel package name like above
Title: Re: DANGER-Will Robinson!!
Post by: flip city on August 16, 2009, 09:51:46 pm
GOOD REPORT...all systems are go...after successful brain salad surgery. Thanks to all... I would never had dared before to attempt a kernel update...KUDOS to team vector ! ::)
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 17, 2009, 07:58:31 pm
I've installed it on two computers and everything is working fine.
--GrannyGeek
Title: Re: DANGER-Will Robinson!!
Post by: Trex on August 17, 2009, 08:27:09 pm
Sweated over it, expecting a disaster, it all went smooth as silk..easy peesy...

Thanks for the quick how to...
Title: Re: DANGER-Will Robinson!!
Post by: zhymm on August 18, 2009, 08:54:27 pm
Well, lost wireless love with the patched kernel with my laptop.  I have a Dell Latitude 600 with the infamous Broadcom 43xx chip.  :'(

Now to patch the desktop (crosses fingers).

Old Man Zhymm
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 18, 2009, 09:05:54 pm
Well, lost wireless love with the patched kernel with my laptop.  I have a Dell Latitude 600 with the infamous Broadcom 43xx chip.  :'(

Now to patch the desktop (crosses fingers).

Old Man Zhymm
try installing this package for your wireless ftp://vectorlinux.osuosl.org/pub/vectorlinux/veclinux-6.0/packages/drivers/broadcom-wl-5.10.27.6_2.6.27.29-i586-1vl60.tlz
Title: Re: DANGER-Will Robinson!!
Post by: zhymm on August 18, 2009, 09:08:42 pm
Reacted too soon :-[  .  On second boot my wireless on the lappy is working.  Dunno why it didn't the first time.

Old Man Zhymm
Title: Re: DANGER-Will Robinson!!
Post by: Pita on August 19, 2009, 09:29:20 pm
Installed kernel, module and src did my lilo and mvidia will not start any longer.

Reinstalled mvidia with gslapt still it says mvidia is not configured in the kernel or such a thing.

How to go about?
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 20, 2009, 05:07:01 am
run vxconf so the nvidia kernel module can be built for this kernel version
Title: Re: DANGER-Will Robinson!!
Post by: newt on August 20, 2009, 09:37:01 am
I also lost wireless after the upgrade, however was able to modprobe the driver and was back in a few seconds.  Is it good general practice to 'depmod -aq' after a kernel upgrade?  Would 'depmod -aq' have re-listed/linked/found/modprobed any modules that were present prior to the upgrade without me having to know what was there before?  Sorry for all the questions; I'm just trying to have a better handle on this for the future.

cheers,
newt
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 20, 2009, 09:56:43 am
it looks like we really should have a kernel upgrade howto somewhere

1)download the kernels and install like any other package.
You will need the kernel and kernel-module packages, the kernel-src package is optional and only needed to build kernel and drivers

2)update your bootloader to add the new kernel, this can be done easily with vliloconf

3)install any extra driver packages needed by your system, these can be found by searching for the old kernel version in /var/log/packages
Quote
root:$ ls /var/log/packages/*2.6.27.12*
/var/log/packages/broadcom-wl-5.10.27.6_2.6.27.12-i586-1vl60

4)run depmod to update the kernel module dependancies
Code: [Select]
root:$ depmod -aq 2.6.27.29depmod needs to be ran with the new kernels version as an argument or ran under the kernel you want the modules updated for.

5)reboot into the new kernel and verify that it is working correctly
run "depmod -aq" and reboot if not ran in lest step
This would include making sure your video driver was working and that you compiled a driver for the running kernel if needed.
 
6)remove old kernel and driver packages with removepkg
be careful not to remove the kernel-headers package even if it looks like an old version

Title: Re: DANGER-Will Robinson!!
Post by: Hiero2 on August 20, 2009, 01:35:54 pm
Two or three important comments to make.


Hiero2
Title: Re: DANGER-Will Robinson!!
Post by: Pita on August 20, 2009, 07:00:51 pm
run vxconf so the nvidia kernel module can be built for this kernel version

Nothing doing. That is what I get.

Unable to find the kernel source tree for the currently running kernel
.......
If you know the  correct kernel source files are installed, you may specify the kernel source   
path with the '--kernel-source-path' command line option.     

I tried verious options for "--kernel-source-path" none will bite.
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 20, 2009, 07:28:31 pm
did you install the kernel-src package?
http://vectorlinux.osuosl.org/veclinux-6.0/kernels/kernel-src-2.6.27.29-i686-1vl60.tlz
Title: Re: DANGER-Will Robinson!!
Post by: Pita on August 20, 2009, 08:23:38 pm
did you install the kernel-src package?
http://vectorlinux.osuosl.org/veclinux-6.0/kernels/kernel-src-2.6.27.29-i686-1vl60.tlz

Yes I did, however, apparently wrong. Reinstalled and all is working now. Nvidia running. :D
Title: Re: DANGER-Will Robinson!!
Post by: Pita on August 21, 2009, 06:37:37 pm
I just found that after installing the new kernel my sound is gone.

Running alsaconf detects my sound card and shows no errors running its course.
Yet ther is no sound.

:$ /usr/sbin/alsactl restore
/usr/sbin/alsactl: load_state:1616: No soundcards found...

:$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such file or directory

:$ /sbin/lsmod | grep snd
snd_pcm                75268  0
snd_timer              20872  1 snd_pcm
snd                    54052  2 snd_pcm,snd_timer
soundcore               7008  1 snd
snd_page_alloc          8712  1 snd_pcm

Should there not be more of them?

On booting it says starting alsa [OK]

And here:

:$ sudo /etc/rc.d/rc.alsa stop
Shutting down sound driver: amixer: Mixer attach default error: No such file or directory
amixer: Mixer attach default error: No such file or directory
/usr/sbin/alsactl: save_state:1513: No soundcards found...

:$ sudo /etc/rc.d/rc.alsa start
Starting sound driver: snd-intel8x0 WARNING: Error inserting ac97_bus (/lib/modules/2.6.27.29/kernel/sound/misc/ac97_bus.ko): Invalid module format
WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.27.29/kernel/sound/pci/ac97/snd-ac97-codec.ko): Invalid module format
FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.27.29/kernel/sound/pci/snd-intel8x0.ko): Invalid module format
done
ERROR: Could not load ALSA drivers


Help appreciated!
Title: Re: DANGER-Will Robinson!!
Post by: Pita on August 22, 2009, 12:19:53 am
I just found that after installing the new kernel my sound is gone.

Running alsaconf detects my sound card and shows no errors running its course.
Yet ther is no sound.

:$ /usr/sbin/alsactl restore
/usr/sbin/alsactl: load_state:1616: No soundcards found...

:$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such file or directory

:$ /sbin/lsmod | grep snd
snd_pcm                75268  0
snd_timer              20872  1 snd_pcm
snd                    54052  2 snd_pcm,snd_timer
soundcore               7008  1 snd
snd_page_alloc          8712  1 snd_pcm

Should there not be more of them?

On booting it says starting alsa [OK]

And here:

:$ sudo /etc/rc.d/rc.alsa stop
Shutting down sound driver: amixer: Mixer attach default error: No such file or directory
amixer: Mixer attach default error: No such file or directory
/usr/sbin/alsactl: save_state:1513: No soundcards found...

:$ sudo /etc/rc.d/rc.alsa start
Starting sound driver: snd-intel8x0 WARNING: Error inserting ac97_bus (/lib/modules/2.6.27.29/kernel/sound/misc/ac97_bus.ko): Invalid module format
WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.27.29/kernel/sound/pci/ac97/snd-ac97-codec.ko): Invalid module format
FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.27.29/kernel/sound/pci/snd-intel8x0.ko): Invalid module format
done
ERROR: Could not load ALSA drivers


Help appreciated!


SOLVED! :D :D

Reinstalled kernel and modules. ??? ???
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 22, 2009, 04:59:24 pm
I had some trouble today after I removed the old kernel files with removepkg and tried to update LILO to reflect the new kernel and no longer list the old, gone kernel. When I ran vliloconf, I got a message:
cannot find kernel (vmlinuz)
and vliloconf terminated. The same thing happened when I ran VASM to modify LILO.

I solved the problem by updating the symlinks for @System.map, @config, and @vmlinuz in /boot and then I reran vliloconf. LILO was updated and my reboot was successful. Had I been a total newbie, I would have freaked out, though.

I use the XP boot loader to chainload LILO and I had to go through a procedure twice. I had to remake my bootsect.lnx file that goes in C:\ by doing
dd if=/dev/hda6 of=/tmp/bootsect.lnx bs=1 count=512

Then I copied that file to /mnt/win-c. Then I did vliloconf and just to be safe, I ran
lilo -v
to make sure LILO was changed. I then rebooted and LILO offered the new kernel.

I'll be removing the old kernel files from another computer tomorrow and will see what happens with LILO there.
--GrannyGeek
Title: Re: DANGER-Will Robinson!!
Post by: Pita on August 22, 2009, 06:48:59 pm
I just found that after installing the new kernel my sound is gone.

Running alsaconf detects my sound card and shows no errors running its course.
Yet ther is no sound.

:$ /usr/sbin/alsactl restore
/usr/sbin/alsactl: load_state:1616: No soundcards found...

:$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such file or directory

:$ /sbin/lsmod | grep snd
snd_pcm                75268  0
snd_timer              20872  1 snd_pcm
snd                    54052  2 snd_pcm,snd_timer
soundcore               7008  1 snd
snd_page_alloc          8712  1 snd_pcm

Should there not be more of them?

On booting it says starting alsa [OK]

And here:

:$ sudo /etc/rc.d/rc.alsa stop
Shutting down sound driver: amixer: Mixer attach default error: No such file or directory
amixer: Mixer attach default error: No such file or directory
/usr/sbin/alsactl: save_state:1513: No soundcards found...

:$ sudo /etc/rc.d/rc.alsa start
Starting sound driver: snd-intel8x0 WARNING: Error inserting ac97_bus (/lib/modules/2.6.27.29/kernel/sound/misc/ac97_bus.ko): Invalid module format
WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.27.29/kernel/sound/pci/ac97/snd-ac97-codec.ko): Invalid module format
FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.27.29/kernel/sound/pci/snd-intel8x0.ko): Invalid module format
done
ERROR: Could not load ALSA drivers


Help appreciated!


SOLVED! :D :D

Reinstalled kernel and modules. ??? ???

Rejoiced too early.
When I rebooted this morning the sound was gone again.
Reinstalling kernel and modules does not work this time.
This is now really ****. :(:(

All above error messages still apply.
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 23, 2009, 07:23:31 am
I had some trouble today after I removed the old kernel files with removepkg and tried to update LILO to reflect the new kernel and no longer list the old, gone kernel. When I ran vliloconf, I got a message:
cannot find kernel (vmlinuz)
and vliloconf terminated. The same thing happened when I ran VASM to modify LILO.

I solved the problem by updating the symlinks for @System.map, @config, and @vmlinuz in /boot and then I reran vliloconf. LILO was updated and my reboot was successful. Had I been a total newbie, I would have freaked out, though.

I use the XP boot loader to chainload LILO and I had to go through a procedure twice. I had to remake my bootsect.lnx file that goes in C:\ by doing
dd if=/dev/hda6 of=/tmp/bootsect.lnx bs=1 count=512

Then I copied that file to /mnt/win-c. Then I did vliloconf and just to be safe, I ran
lilo -v
to make sure LILO was changed. I then rebooted and LILO offered the new kernel.

I'll be removing the old kernel files from another computer tomorrow and will see what happens with LILO there.
--GrannyGeek
Reinstall the NEW kernel package after removal of the old kernel package will update symlinks
looks like another step for the howto  :)
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 23, 2009, 04:23:13 pm
I have a royal mess right now on my laptop with the upgraded kernel. I can't boot into 2.6.27.29 and I've removed 2.6.27.12.

I had removed the old kernel before I read the message about running depmod. I have LILO on the /dev/hda6 boot sector. I use the XP boot loader to chain to LILO. However, my bootsect.lnx file is messed up and when I choose VectorLinux from the operating system choice screen, I get a screen of 99 99 99 going halfway down the screen, which goes no further into the boot process. This computer has no floppy drive and I don't want to put LILO into the MBR until I have a way to recover the MBR. I can't put in an XP recovery console with access to the FIXMBR command because of Service Pack 3, which is newer than the setup files on my Windows partition and the only XP installation disk I have won't work with an OEM version of Windows. (This computer came with a Recovery Disk, not a real installation disk.)

I can boot with the VL 6 Light CD, but it uses kernel 2.6.27.12 and my computer has 2.6.27.29, so no modules load. I need to boot into 2.6.27.29 in order to do the needed repairs but I can't seem to do it.

I burned a CD of VL 6 Light Live in hopes I could boot into /dev/hda6, my VectorLinux installation. VL6 Light Live includes the correct kernel version, but it offers no option to boot into an existing VL installation.

Is there anything I can do to fix this fiasco?

I upgraded another computer to 2.6.27.29 but haven't yet removed 2.6.27.29. I don't have any problems getting into 2.6.27.29 with the XP boot loader and LILO on /dev/hdb9's boot sector on that computer, but now I'm afraid to remove 2.6.27.12!

I'm writing this in VL6 Light Live and keeping my fingers crossed that someone can help me through this disaster.
--GrannyGeek
Title: Re: DANGER-Will Robinson!!
Post by: uelsk8s on August 23, 2009, 07:32:20 pm
granny,
Why do you need the modules loaded to rescue the system and make it boot the new kernel?
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 23, 2009, 08:36:47 pm
granny,
Why do you need the modules loaded to rescue the system and make it boot the new kernel?

At the moment, I can't do much of anything. For example, I can't mount an NTFS drive. I can't fix the corrupted bootsect.lnx file because when I boot with the VL 6 Light CD, it uses the 2.6.27.12 kernel but the installation is using the 2.6.27.29 kernel. When I do the dd command to create the bootsect.lnx file, it sets up a wrong boot sector image and I get a screen of 99s when the XP boot loa.der tries to chain to /dev/hda6. I can't go online because there are no network modules. I have no sound. When I try to load modules with modprobe, I can't get the 2.6.27.29 modules loaded because the 2.6.27.12 kernel was loaded by the VL Light CD.

I'm sure this is fixable but I don't know how to do it. I haven't had a chance to see if I can get the LiveCD to boot me into my VL on /dev/hda6.

I forgot something that may be important. I was able to get the XP boot loader to display LILO, but when I pick "linux" or anything else (tui or gui) I get this message:
Loading linux EBDA is big; kernel setup stack overlaps LILO second stage.

I haven't googled on that yet. Will do it after I post this.
--GrannyGeek
Title: Re: DANGER-Will Robinson!!
Post by: GrannyGeek on August 23, 2009, 10:06:34 pm
I'm back in business! I followed newt's suggestion in the VL Light Live 6.0 RC1 Feedback section and booted with the Light Live RC1 CD, tabbed for a more customizable boot option, and changed the command so that it reflected my installation on /dev/hda6. It worked! It got me into my installation with the 2.6.27.29 kernel and I was able to do
dd if=/dev/hda6 of=/tmp/bootsect.lnx bs=1 count=512
to get a proper bootsect.lnx file for the XP boot loader to use. I then checked the contents of lilo.conf, which were fine, and ran lilo -v. I copied bootsect.lnx to my FAT32 Windows Drive D and booted into XP. I then moved bootsect.lnx to C:\. I decided to copy it from inside Windows to avoid any funny business with the NTFS partition.

Holding my breath, I rebooted into VectorLinux through the XP boot loader. I got the LILO screen and had a successful boot into VL 6 Light on my /dev/hda6. Modules are all back. Now we'll see what happens tomorrow after a night of the computer being turned off.

Tomorrow I'll have to decide if I want to chance another Big Adventure when I remove the old kernel from my older desktop.
--GrannyGeek