SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2009-12-08 13:51:38

mass04
New Member
Registered: 2009-12-08
Posts: 5

dist-upgrade dual boot conflict solved

Hello, I have a Sylvania gnetbook with the updated gOS dual booting with #! 8.04.02.  I didnt install bootloader with #!, I was hoping #! would allow cpu frequency scaling on my machine VIA proc clocked down at half speed with this fix:
http://www.a110wiki.de/wiki/CPU#CPU_fre … .3D_2.6.24

Howver, I cannot get the modules to compile using 'make', I then tried to apt-get dist-upgrade (which I was weary to do) hoping to upgrade the kernel and allow this to work.  But since I didnt install the bootloader the kernel images did not get made during the upgrade.  I have not restarted the machine yet because Im assuming it will not boot.  Any help for this

Thanks

Last edited by mass04 (2009-12-10 13:23:54)

Offline

Help fund CrunchBang, donate to the project!

#2 2009-12-08 15:25:22

anonymous
The Mystery Member
From: Arch Linux Forums
Registered: 2008-11-29
Posts: 9,418

Re: dist-upgrade dual boot conflict solved

Make sure you have build-essentials installed before compiling.

Offline

#3 2009-12-08 20:26:53

alon_h
#! Junkie
Registered: 2008-12-13
Posts: 269

Re: dist-upgrade dual boot conflict solved

You can try installing grub to #!'s own partition, (say /dev/sda2), reconfigure the kernel ('dpkg-reconfigure linux-....'), then either remove grub or chainloading it (I would reccomend that, as it will keep you booting the latest kernel if/when you upgrade, say for a security fix).

a.

Offline

#4 2009-12-09 13:36:02

mass04
New Member
Registered: 2009-12-08
Posts: 5

Re: dist-upgrade dual boot conflict solved

alon_h wrote:

You can try installing grub to #!'s own partition, (say /dev/sda2), reconfigure the kernel ('dpkg-reconfigure linux-....'), then either remove grub or chainloading it (I would reccomend that, as it will keep you booting the latest kernel if/when you upgrade, say for a security fix).

a.

Oh yes this may work, I have not chainloaded before but I have done some reading.  Does this sound correct to get this working:

1) #! is installed in /dev/sda6 therefore I will

grub-install /dev/sda6 or I think this would work also
grub-install hd0,5

Then reboot into gOS where bootloader is installed in MBR, edit /boot/grub/menu.lst to include
2)
title Linux @ sda6
root (hd0,5)
chainlader +1


Is this all it takes?

Thanks

Offline

#5 2009-12-10 11:15:38

alon_h
#! Junkie
Registered: 2008-12-13
Posts: 269

Re: dist-upgrade dual boot conflict solved

sounds right.
note that if you use grub2 the numbering might have changed to start the partitions from 1 (so /dev/sda6 is (hd0,6) or (hd1,6). if you use it check what the local /boot/grub/grub.cfg says.
also in gOS menu.lst put the entry at the end, after the "automagic someting", that way it is kept when update-grub is activated (like, when you install a new kernel).

a.

Offline

#6 2009-12-10 13:21:33

mass04
New Member
Registered: 2009-12-08
Posts: 5

Re: dist-upgrade dual boot conflict solved

UPDATE:
I did get this to work work the above install and menu.lst edit.  I am now chainloading #! (which its grub menu lists all available #! kernels) and gOS.  Like I mentioned the main goal of this was to allow cpufreq scaling with e_powersave.  I was unable to install the kernel headers using sudo apt-get install kernel-headers.  It took quite awhile to find the right package but I found it on Ubuntu package site under "software":

linux-headers-lbm-2.6.24-24-generic

After this install I was able to 'make' the powersave module then install it as needed.  I now boot up with the full 1200MHz!


Thanks for the help

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo