It looks like what has happened is the package names have changed from jaunty to karmic. I don't see a -pae package in jaunty but it exists in karmic. And in karmic linux-server is a metapackage for the -pae kernel.
Use the free -m command to check and see if ubuntu is seeing more then 4 GB of ram while booted in the -server kernel. If it is then you are all set On Sat, Mar 20, 2010 at 11:13 PM, David Groos <[email protected]> wrote: > Sorry to keep bothering! I got this: > dgr...@gcos2:~$ sudo aptitude install linux-generic-pae > [sudo] password for dgroos: > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > Couldn't find any package whose name or description matched > "linux-generic-pae" > Couldn't find any package whose name or description matched > "linux-generic-pae" > No packages will be installed, upgraded, or removed. > 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 0B of archives. After unpacking 0B will be used. > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > Any ideas? > David > > > > On Sat, Mar 20, 2010 at 10:02 PM, ekul taylor <[email protected]>wrote: > >> That's strange it didn't select the pae kernel. In that case install the >> linux-generic-pae package. >> >> sudo aptitude install linux-generic-pae >> >> >> On Sat, Mar 20, 2010 at 10:50 PM, David Groos <[email protected]> wrote: >> >>> Thanks Ekul. I didn't really understand what you meant by the dpkg so >>> didn't go with that but did understand the sudo aptitude part :) So I did >>> this, it installed, I rebooted and checked: >>> >>> dgr...@gcos2:~$ uname -r >>> 2.6.28-18-server >>> >>> Which doesn't have the -pae in the name. Any ideas? >>> David >>> >>> >>> >>> On Sat, Mar 20, 2010 at 4:29 PM, ekul taylor <[email protected]>wrote: >>> >>>> It's actually really easy to install a kernel if you use the >>>> repositories. dpkg adds your kernel to the list of available kernels so if >>>> for any reason you have trouble you can simply use grub to boot into your >>>> old kernel. Among all package installations a new kernel is among the >>>> safest since reverting is as easy as hitting escape during grub and >>>> choosing >>>> the old kernel. >>>> >>>> I'm not sure what package mixture you have so I can't really deal with >>>> that but installing the PAE kernel is as simple as: >>>> sudo aptitude install linux-server >>>> This will install the kernel and any necessary headers. If you want to >>>> run the karmic kernel but nothing else from karmic you'll have to do some >>>> apt pinning. >>>> >>>> As for the reason you don't have the pae kernel I believe it is only >>>> selected by default when installing via the server cd. Any other method >>>> you >>>> have to add it via apt after install. >>>> >>>> On Sat, Mar 20, 2010 at 12:34 PM, David Groos <[email protected]>wrote: >>>> >>>>> I find I'm not using the server kernel which surprises me--isn't that >>>>> the one that the 'alternate CD' used? Shouldn't that be the standard >>>>> install for a thin client server using Edubuntu? >>>>> >>>>> So, how do I go about installing this kernel? I used the link that >>>>> Alkis provided and I could download the kernel. I couldn't access it via >>>>> Synaptic, probably because I've set sources to Jaunty but I wasn't sure >>>>> how >>>>> to set some to Karmic. Any link/suggestion would be appreciated! I don't >>>>> want to willy-nilly upgrade a kernel, sounds like risky business. >>>>> >>>>> Thanks! >>>>> David >>>>> >>>>> On Mar 19, 2010, at 4:35 PM, ekul taylor wrote: >>>>> >>>>> Run >>>>> uname -r >>>>> which will tell you the specific build of the kernel you are running. >>>>> If the PAE kernel is in use it will have -pae in the name. if you don't >>>>> see that you'll need to install the linux-server package. >>>>> >>>>> You can also run free -m as a check to ensure all your ram is being >>>>> addressed. However much you think there is should match the total column >>>>> in >>>>> MB. If it doesn't something isn't quite working. >>>>> >>>>> On Fri, Mar 19, 2010 at 5:07 PM, David Groos <[email protected]>wrote: >>>>> >>>>>> Thanks Ekul for the further info, I get it now. I think I'll use >>>>>> solution #1 below--sounds like it is doable and will help out with what I >>>>>> need for these last couple of months of school then over summer power-up >>>>>> with a new Lucid install. I'm pretty sure I'm currently using the server >>>>>> install. How can I tell? >>>>>> >>>>>> David >>>>>> >>>>>> >>>>>> On Fri, Mar 19, 2010 at 8:35 AM, ekul taylor >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> The 32/64 bit question is very complicated. Hopefully I can help. >>>>>>> >>>>>>> Any AMD Opteron or Intel Xeon server made in the past few years has >>>>>>> support for running 32 bit and 64 bit code (even at the same time). So >>>>>>> you >>>>>>> could clone your existing server and it would work fine but you might >>>>>>> not be >>>>>>> able to take advantage of all of your RAM. >>>>>>> >>>>>>> If you have more then 4 GB of RAM you have 3 options to use it all: >>>>>>> >>>>>>> 1. Clone your 32 bit server install but install the linux-server >>>>>>> package if it isn't already used. This kernel is PAE enabled which is >>>>>>> something Intel developed to let 32 bit processors address more then 4 >>>>>>> GB of >>>>>>> RAM. It does have slight performance issues and no one process can >>>>>>> address >>>>>>> more then 4 GB of RAM but for a terminal server this isn't important. >>>>>>> >>>>>>> 2. Clone your 32 bit server but install and run a 64 bit kernel. >>>>>>> This can be tricky dependency-wise so I wouldn't recommend it so I >>>>>>> won't >>>>>>> outline the many steps here. >>>>>>> >>>>>>> 3. Install a 64 bit version of edubuntu and reuse >>>>>>> your configuration files from your old server. It's pretty easy to do >>>>>>> since >>>>>>> except for /etc/modules.d and /etc/modprobe.conf none of the config >>>>>>> files >>>>>>> are about the kernel. You do have to build your chroot a little >>>>>>> differently >>>>>>> if you use this option as thin clients will almost certainly need a 32 >>>>>>> bit >>>>>>> boot environment. To do this you use the command: >>>>>>> ltsp-build-client --arch i386 >>>>>>> instead of just ltsp-build-client. This is what I option I would use >>>>>>> when installing lucid but if you're just going to be using karmic for a >>>>>>> few >>>>>>> months option 1 will involve the least setup. >>>>>>> >>>>>>> >>>>>>> On Fri, Mar 19, 2010 at 9:11 AM, David Groos <[email protected]>wrote: >>>>>>> >>>>>>>> Confusion compounds... >>>>>>>> >>>>>>>> the one thing I might have understood... >>>>>>>> >>>>>>>>> >>>>>>>>> If you install this kernel in Jaunty/Karmic, then you can access >>>>>>>>> more >>>>>>>>> than 4 Gb of RAM while having 32 bit systems/OS: >>>>>>>>> http://packages.ubuntu.com/karmic/linux-server >>>>>>>>> >>>>>>>>> So you can do that either in the old or the new server. >>>>>>>>> >>>>>>>> >>>>>>>> You're saying that: >>>>>>>> --I could install the above kernel onto my current 32 bit hardware. >>>>>>>> --then I could either: >>>>>>>> --------install up to 64 Gb RAM on old server >>>>>>>> or... >>>>>>>> --------then I could clone this new setup to the new server. >>>>>>>> ? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> David >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> edubuntu-users mailing list >>>>>>>> >>>>>>>> [email protected] >>>>>>>> Modify settings or unsubscribe at: >>>>>>>> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> >
-- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
