No you don't have to reinstall. If you go from say an Intel to AMD CPU then I would use the k_athlon kernel pkg vs k_deflt but that's about it.

* Tom Kostiainen (tom.kostiainen@pp.inet.fi) [030104 13:24]: -> ->Hi, -> ->Do I need to reinstall SuSE Linux after I've changed ->my CPU and motherboard? What's the easyest way ->to do this?

Ben's right. It's about that simple. Try that with XP. ;) It should work out just fine, but you didn't tell us if *all* you changed was the CPU and motherboard. Is it a new motherboard with a bunch of onboard sound/video/LAN and stuff? That might be another issue entirely. Generally I disable that stuff anyway and stick to PCI cards. ;) -Jonathan

Tom Kostiainen wrote:

Well I will probably update to a new AMD cpu (now using a AMD Thunderbird), so would that mean I don't have to do anything to my kernel?

I'm quite a newbie with Linux so if something doesn't work and the SuSE install can't do what I need it to do it will probably be easyer for me to just reinstall the hole thing =) ...or is updating the kernel so difficult as I've understood?

The video card might be a problem. I'm planing on keeping my old one but what if I update? What can I do if X won't start because of the video driver?

My networkcard is a PCI, and so is my soundcard, so motherboard integrated cards aren't a problem.

- tk

----- Original Message ----- From: Jonathan Nichols To: SuSE Linux List Sent: Saturday, January 04, 2003 5:31 PM Subject: Re: [SLE] Reinstalling?

...

...

No you don't have to reinstall. If you go from say an Intel to AMD CPU then I would use the k_athlon kernel pkg vs k_deflt but that's about it.

* Tom Kostiainen (tom.kostiainen@pp.inet.fi) [030104 13:24]: -> ->Hi, -> ->Do I need to reinstall SuSE Linux after I've changed ->my CPU and motherboard? What's the easyest way ->to do this?

Ben's right. It's about that simple. Try that with XP. ;)

It should work out just fine, but you didn't tell us if *all* you changed was the CPU and motherboard. Is it a new motherboard with a bunch of onboard sound/video/LAN and stuff? That might be another issue entirely.

Generally I disable that stuff anyway and stick to PCI cards. ;)

-Jonathan

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Reinstalling won't help you in the long run. It's not what Linux is all about - that M$' turf. In Linux you can fix things on the fly. Also you need to be comfortable in the console/text mode and learn to do things there - it seems intimidating but after you get used to it you'll wonder why you waited.... Why? Becuase unlike M$ with a "master" registry file, that if corrupt, can take the "whole" system down with it, Linux is about layers. Your Xserver is the 2nd most top layer - the gui is the top layer and last to load. You need to learn and understand that in order to config the xserver/gui usually it entails installing drivers and configuring the XF86Config file. If the module for the vidcard is loaded and working then it's just about the xf86config (usually - other things may need to be looked at). Agian, there is no master reg file in Linux - each component has its own file for configuration and this is in plain text - just open a text editor and change it to meet your needs. If you have any question the list is here to specifically answer them. If your post isn't answered (usually with in 1 hour to a day) then repost and change the tittle of the message. This is a very knowledgable list and the users are very good about walking people through things. You need to know about getting message from you system to add to your post (another nice feature of Linux - it essentially talks to you in the sense of giving you messages about whats right or wrong with something). This is he most useful and friendly Linux list I've found and I've tried many. Cheers, Curtis.

(CC'd to you and list, sorry for the duplicate)

Well I will probably update to a new AMD cpu (now using a AMD Thunderbird), so would that mean I don't have to do anything to my kernel?

Chances are you have the k_deflt kernel. Easy to tell by doing "rpm -q k_deflt" and if it responds, you have it. :)

I'm quite a newbie with Linux so if something doesn't work and the SuSE install can't do what I need it to do it will probably be easyer for me to just reinstall the hole thing =) ...or is updating the kernel so difficult as I've understood?

Sometimes reinstalling everything from scratch is a good learning tool. In the case of SuSE, installing a new/different kernel from SuSE isn't that hard at all. Building your own is a different story, but I usually just stick to the SuSE kernels. All you really need to do is rpm -Uvh k_athlon.bla.bla.rpm and reboot the machine (after downloading the new kernel, of course)

The video card might be a problem. I'm planing on keeping my old one but what if I update? What can I do if X won't start because of the video driver?

Not entirely sure. I never install any of the desktop environments..

My networkcard is a PCI, and so is my soundcard, so motherboard integrated cards aren't a problem.

- tk

----- Original Message ----- From: Jonathan Nichols To: SuSE Linux List Sent: Saturday, January 04, 2003 5:31 PM Subject: Re: [SLE] Reinstalling?

...

...

No you don't have to reinstall. If you go from say an Intel to AMD CPU then I would use the k_athlon kernel pkg vs k_deflt but that's about it.

* Tom Kostiainen (tom.kostiainen@pp.inet.fi) [030104 13:24]: -> ->Hi, -> ->Do I need to reinstall SuSE Linux after I've changed ->my CPU and motherboard? What's the easyest way ->to do this?

Ben's right. It's about that simple. Try that with XP. ;)

It should work out just fine, but you didn't tell us if *all* you changed was the CPU and motherboard. Is it a new motherboard with a bunch of onboard sound/video/LAN and stuff? That might be another issue entirely.

Generally I disable that stuff anyway and stick to PCI cards. ;)

-Jonathan

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Yes, if you are using LILO, No if you are using GRUB On Mon, 2003-01-06 at 12:51, Franklin Maurer wrote:

On Monday 06 January 2003 12:28 pm, Jonathan Nichols wrote:

...

All you really need to do is rpm -Uvh k_athlon.bla.bla.rpm and reboot the machine (after downloading the new kernel, of course)

Don't you need to run mkinitrd, after upgrading / installing the kernel? I thought that without it you'd get a kernel panic upon rebooting. I'm just checking my newbie knowledge, but i thought i had learned this key point through others mistakes.

Maybe it's because i upgreded the kernel through apt-get.

-- Franklin Maurer Using SuSE 8.1. -- Harry Wert Wert Enterprises

On Mon, 2003-01-06 at 17:04, John wrote:

On Monday 06 January 2003 13:12 pm, Harry Wert wrote:

...

Yes, if you are using LILO, No if you are using GRUB

On Mon, 2003-01-06 at 12:51, Franklin Maurer wrote:

...

On Monday 06 January 2003 12:28 pm, Jonathan Nichols wrote:

...

All you really need to do is rpm -Uvh k_athlon.bla.bla.rpm and reboot the machine (after downloading the new kernel, of course)

Don't you need to run mkinitrd, after upgrading / installing the kernel? I thought that without it you'd get a kernel panic upon rebooting. I'm just checking my newbie knowledge, but i thought i had learned this key point through others mistakes.

Maybe it's because i upgreded the kernel through apt-get.

Okay, so to keep it all nice and simple, I download the k_athlon rpm, click on it in konqueror and kpackage pops up and I install it. Once it's installed, bring up a konsole, do mkinitrd *and* lilo, then reboot. Is this right? Correct - just remember you need to be ROOT or SU when you execute mkinitrd and then lilo

One more question about this...will I still have all my same old files and all that stuff? Settings, etc., in kde? Can I then on the first bootup after the install of the new kernel, log in as root and open Control Center->System->Kernel configurator and do any tweaking there? And if I 'can', do I need to do mkinitrd and lilo again before rebooting?

Yes, all your old files, settings, etc., in kde will be intact. When you reboot after you have executed mkinitrd and lilo you are FINISHED with the kernel unless you are an expert. Stay out of the kernel configurator or much grief may head your way! Seriously, there is no need to use the kernel configurator unless you have the need to add specialized kernel boot information. Unlikely, or you would probably have experienced a kernel panic or failure to boot at all. This of course assumes you had an operating system PRIOR to your kernel upgrade. And Yes, if you make any kernel modifications or additions it is necessary to do another mkinitrd and lilo operation. Regards, Harry

Thanks for all this info and help,

John -- Harry Wert Wert Enterprises

* On Monday 06 January 2003 05:04 pm, John wrote:

Okay, so to keep it all nice and simple, I download the k_athlon rpm, click on it in konqueror and kpackage pops up and I install it. Once it's installed, bring up a konsole, do mkinitrd *and* lilo, then reboot. Is this right? One more question about this...will I still have all my same old files and all that stuff? Settings, etc., in kde? Can I then on the first bootup after the install of the new kernel, log in as root and open Control Center->System->Kernel configurator and do any tweaking there? And if I 'can', do I need to do mkinitrd and lilo again before rebooting?

Thanks for all this info and help,

John

--====================== John, Let me interject something at this point. When you install the k_athlon kernel, you are not overwriting the k_deflt kernel you already had installed. You may not have known that or the others helping failed to point that out. What happens then is that you end up with two kernels instead of one and it's quite possible you will still be using the k_deflt the next time you boot. It only overwrites, if it is the same name/type kernel. You must remove the old kernel first then install the new to keep down any possible conflicts. Use "rpm -e k_deflt" to remove the original. Patrick --- KMail v1.4.3 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206

On 01/07/2003 01:51 AM, Franklin Maurer wrote:

Don't you need to run mkinitrd, after upgrading / installing the kernel? I thought that without it you'd get a kernel panic upon rebooting. I'm just checking my newbie knowledge, but i thought i had learned this key point through others mistakes.

Maybe it's because i upgreded the kernel through apt-get.

It depends, which is why I would rather use a console to update my kernel with the rpm command than a GUI frontend that hides any feedback. Some of the last few Mantel kernels already run mkinitrd, and if you used GRUB, that would be enough. So, it depends on what the kernel rpm does. Another thing, the Mantel kernel only updates the one kernel image (/boot/vmlinuz) and not the one for failsafe (/boot/vmlinuz.suse), so when I see that when the rpm runs mkinitrd and fails to create the failsafe initrd, I know I need to copy vmlinuz to vmlinuz.suse. So, even though it is quite easy to upgrade, it is still not a no brainer, but since I usually get the latest kernel from Mantel (for testing and 'having fun' :-) ), I don't expect a no brainer, I expect to need to think. I actually prefer that, one of Linux's freedoms. YMMV -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.