You are not logged in.

#1 2011-04-07 08:23:24

apronouva
Member
Registered: 2011-04-07
Posts: 4

[SOLVED] Does pacman Upgrade Custom Kernel ?

Hi,

I'm a newbie so CMIIW. I just installed Archlinux Core i686 on my Lenovo G450 Dual Core T4300. At first the default kernel was 2.6.33 (can't remember exactly). Under the thought of my BCM4312 PHY can't work under kernel 2.6.34 and below, I go to Archwiki and did a kernel upgrade from source, to 2.6.38

*please note that at this moment, I haven't do any Install on the system yet.

Both kernel is working fine, as well as Grub selection (3 option : Default Kernel, Default Kernel Fallback, Custom Kernel).

After that, under the new custom kernel, I did "pacman Syu" and successfully upgrade the system. There was some obstacle like "firmware" exists and so but solved otherwise.

After the upgrade finished, I reboot the system. I see that default kernel has changed(upgraded) to 2.6.37-ARCH. Both 2.6.37 and my custom 2.6.38 still works fine.

What I wanted to asks :
1. Why pacman upgrading my default kernel instead of what I recently used ?
2. What is the wise steps towards these change, since I haven't install any other additional package yet (NVIDIA drivers, X systems, application etc), I mean, should I use the upgraded default kernel (its 2.6.37 now so it should be fine with my Broadcom 4312 PHY) ?
3. What  are the disadvantages if I use my custom 2.6.38 kernel ? I mean on the basis of effect by pacman, of course

Thank you in advance,
apronouva

ps: I don't know if I posted this on the right section, but since its not kernel problem but Pacman question, so I put it in here, tried the search, can't find any

Last edited by apronouva (2011-04-07 08:46:06)


simply creative - LXDE - 2.6.37-ARCH i686 Dual Core CPU T4300

Offline

#2 2011-04-07 08:40:35

Awebb
Member
Registered: 2010-05-06
Posts: 6,688

Re: [SOLVED] Does pacman Upgrade Custom Kernel ?

1. Pacman upgrades packages with the same name. It updates kernel26, not your "kernel26-customwhatever". It does not know what to do with your custom kernel.
2. If the only thing you need from a newer kernel is driver compatibility, there is no real reason to use a custom kernel, if the stock kernel supports your device.
3. It won't be updated. There is also the possibility that installing kernel modules will fail, if you don't have the proper headers installed and so on.

Offline

#3 2011-04-07 08:45:42

apronouva
Member
Registered: 2011-04-07
Posts: 4

Re: [SOLVED] Does pacman Upgrade Custom Kernel ?

Awebb wrote:

1. Pacman upgrades packages with the same name. It updates kernel26, not your "kernel26-customwhatever". It does not know what to do with your custom kernel.
2. If the only thing you need from a newer kernel is driver compatibility, there is no real reason to use a custom kernel, if the stock kernel supports your device.
3. It won't be updated. There is also the possibility that installing kernel modules will fail, if you don't have the proper headers installed and so on.

Okay thank you very much Awebb, then I'll stick with the upgraded default kernel. Now I've gotta search a way to remove my custom built kernel.

Thank you in advance


simply creative - LXDE - 2.6.37-ARCH i686 Dual Core CPU T4300

Offline

#4 2011-04-07 08:47:56

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,237
Website

Re: [SOLVED] Does pacman Upgrade Custom Kernel ?

Awebb wrote:

.... It does not know what to do with your custom kernel.

Just to clarify this point... Pacman knows about your -custom kernel and handles it just fine... The difference is that it's a package you built yourself, so there will never be a newer version (of kernel26-custom-whatever) in the repos for pacman to consider upgrading it. If you built a custom package called "kernel26", then pacman would try to upgrade it to the 'kernel26' that the devs compile and put in the [core] repo.

Offline

#5 2011-04-07 08:57:07

apronouva
Member
Registered: 2011-04-07
Posts: 4

Re: [SOLVED] Does pacman Upgrade Custom Kernel ?

fukawi2 wrote:
Awebb wrote:

.... It does not know what to do with your custom kernel.

Just to clarify this point... Pacman knows about your -custom kernel and handles it just fine... The difference is that it's a package you built yourself, so there will never be a newer version (of kernel26-custom-whatever) in the repos for pacman to consider upgrading it. If you built a custom package called "kernel26", then pacman would try to upgrade it to the 'kernel26' that the devs compile and put in the [core] repo.


I see, so thats why its not affecting the new custom build kernel at all, so I guess sticking with the default is the best for now. Thanks fukawi2, another knowledge gained smile

regards,
apronouva


simply creative - LXDE - 2.6.37-ARCH i686 Dual Core CPU T4300

Offline

Board footer

Powered by FluxBB