Prev: No dejes que te cambien en la farmacia
Next: Android phone is not recognized by Android SDK, despite udev conf
From: Ravi Roy on 13 Aug 2010 05:10
Hi

I am installing new debian machine debian 5.0 - 64-bit. Everything goes
well; as a part of installation using presseding, I am installing new kernel
2.6.33.3 into this machine, but I can not make to boot the maching using
this kernel. It only boots from old kernel.

Can somebody help here on this ?

Regards
Ravi
From: Jordan Metzmeier on 13 Aug 2010 10:40
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/13/2010 09:47 AM, Stephen Powell wrote:
>
> I seem to recall seeing something on the lists about an incompatibility between
> the 2.6.32 kernel used by Squeeze and the version of udev which runs on Lenny.
> I assume that the same incompatibility exists with the 2.6.33 kernel. If you
> need a 2.6.33 kernel, I suggest you install Squeeze rather than Lenny.
>

This is backwards. The udev in squeeze requires a newer kernel with
CONFIG_SYSFS_DEPRECATED=n . The squeeze kernel works fine in lenny, and
is even available in Lenny backports. You just can not go the other way
around (Lenny kernel on a squeeze machine).

The .32 kernel is also available in the kmuto Lenny installer.

- --
Jordan Metzmeier

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJMZViQAAoJEKj/C3qNthmTvBEQAI4+zCfTvTisMeBsClGH1aGa
o8MN0A52z5tdlaOIVCmhV8k+sG/o8eeU1pqkaDEyQTHL94CPwnI2tt4tUhqJoj55
v1ShljSmpgymCyBMtllTxXi/5S1mm05ElbGGY1+GTkJu7hT7WswD5L7Emkb8v9jy
zdylRutjmSDMXRxET4AklhKZlnQ8G0V70unf5YeqDgYNC4DyQxoX/5C3ek4bB2Le
UB7V08Pvu0CvZ8xwPW5GjEmnYDXMUzKB2MqRIS2CrIJRmoOt2wJKV6eKwaEkd/gr
Jc8xc0d8CHi3LNa0jJV/fr4186u6d1FnKGknYNfUEI54VxhuyEW10BjkFjs7WRoO
lnbCXFa1pLNtPYpACYQRb4zSgGrmvROKcYQGng6ZPCsDDLKQGA7vPMIdiuovs/VR
usznct0pT3ttSU0IztyBOGbVQhXbSfR6kVNKajjxkd5gCzd0c8kqnCc4KMGZshZE
34BEUYwnFfHK5v2ONnmXE135/ZFflsLHPKzSGav5aEjdnF/DwuBPhrycprN2/xmi
ZRxWb4dTKjB1pDW7uLBJnkDwlOFuLJMRoAjQXGu/bamHIJMbxEohuQrwliaagpOh
rZopJhiVsTtoJltqeT/VVFhSOG8XgNHK8hVFFdno9vsdZZG0vq4H8JmaZOe8V++c
1H2K2R3FANqH6WKHpqzp
=Ju9I
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C655890.6000600(a)gmail.com
From: Ravi Roy on 13 Aug 2010 12:30
On 8/13/10, Stephen Powell <zlinuxman(a)wowway.com> wrote:
>
> On Fri, 13 Aug 2010 10:37:04 -0400 (EDT), Jordan Metzmeier wrote:
> > On 08/13/2010 09:47 AM, Stephen Powell wrote:
> As for the OP, please provide more information, such as:



My apologies for being newbie; would try to answer questions; some might
not be in right
terminology of linux..

(1) Where did you get your 2.6.33 kernel? Backports? Experimental?
> Custom built? etc. How did you install it?


it is custom built kernel, compiled by a colleague some time ago, it is
basically a debian package which is installed
Installation is being triggered as late command in preseed.cfg

(2) What bootloader do you use? grub? (version 1) grub-pc (version 2),
> lilo? extlinux? etc.


I use grub version 0.97

(3) What is the contents of /etc/kernel-img.conf?


Will try installation again and let you know.

(4) What is the contents of your boot loader configuration file?
> (/etc/lilo.conf for lilo, /boot/grub/menu.lst for grub version 1,
> etc.)


menu.lst contains two entries for kernel 2.6.26.2, which boots perfectly.

(5) What scripts exist in /etc/kernel/postinst.d, /etc/kernel/postrm.d,
> and /etc/initramfs/post-update.d?


Have to try to install it again and will let you know.

(6) Are symbolic links used for the kernel, such as vmlinuz,
> and vmlinuz.old? And what about the initial RAM file systems?
> Are symbolic links used for them too? (initrd.img, initrd.img.old)
> If so, where are these symbolic links? (/, /boot, etc.)


When I boot with old kernel under /boot, i can not see initrd.img for
2.6.33.3;
means it is missing nor links exists.

(7) What exactly are the symptoms of failure when you attempt to
boot the 2.6.33 kernel?

At installation time it does not give any error and system reboots and
boots with old kernel.

I think first issue is initrd.img is missing for 2.6.33.3 and that is the
reason menu list also not being updated.

Thanks!

Ravi

--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster(a)lists.debian.org
Archive:
http://lists.debian.org/1324991559.70067.1281711490732.JavaMail.root(a)md01.wow.synacor.com
 | 
Pages: 1
Prev: No dejes que te cambien en la farmacia
Next: Android phone is not recognized by Android SDK, despite udev conf