[arch-general] 2010.05 iso images problem?
Hi guys, I have downloaded a 2010.05 x86_64 core iso image from http://mir.archlinux.fr/iso/ and verified its sha1sum. After installation, I end up with a 2.6.37 kernel (out in 2011.01) with no modules (2.6.27 and 2.6.33 modules are available). http://mirrors.kernel.org/archlinux/iso/ has the same sha1sum for this iso. Is there not a problem with these images? Right now I am updating this Archlinux installation from a Debian chroot, so it is not a blocking problem, but out of curiosity, I would like to know. Thanks, Didier.
On Sat, 26 Feb 2011 09:04:58 +0100 didier gaumet <didier.gaumet@gmail.com> wrote:
Hi guys,
I have downloaded a 2010.05 x86_64 core iso image from http://mir.archlinux.fr/iso/ and verified its sha1sum. After installation, I end up with a 2.6.37 kernel (out in 2011.01) with no modules (2.6.27 and 2.6.33 modules are available).
http://mirrors.kernel.org/archlinux/iso/ has the same sha1sum for this iso.
Is there not a problem with these images? Right now I am updating this Archlinux installation from a Debian chroot, so it is not a blocking problem, but out of curiosity, I would like to know.
Thanks, Didier.
The new testisos found at http://releng.archlinux.org/isos/ is prefered, but the old release iso should work just fine too. Are there actually no modules in /lib/modules/2.6.37-ARCH/ or is the kernel just complaining about no depmod file? If the former, reinstalling the kernel26 package should solve it, but the intresting questin is why the modules didn't get installed in the first place. If the later, just run a depmod -a
Le Tue, 1 Mar 2011 11:28:42 +0100, Øyvind Heggstad <mrelendig@har-ikkje.net> a écrit :
The new testisos found at http://releng.archlinux.org/isos/ is prefered, but the old release iso should work just fine too.
I was not aware of the existence of these images, thank you.
Are there actually no modules in /lib/modules/2.6.37-ARCH/ or is the kernel just complaining about no depmod file? If the former, reinstalling the kernel26 package should solve it, but the intresting questin is why the modules didn't get installed in the first place. If the later, just run a depmod -a
I've ugraded the kernel modules via a Debian chroot to solve the problem. There was no /lib/modules/2.6.37-ARCH/ directory and to me that was to be expected from a 2010.05 image (2.6.33 kernel). What puzzles me is to find a 2.6.37 kernel installed by this image: if I am not wrong, 2.6.37 was out in 2011.01, eight months after the 2010.05 iso was out...
On Tue, 1 Mar 2011 20:16:22 +0100 didier gaumet <didier.gaumet@gmail.com> wrote:
What puzzles me is to find a 2.6.37 kernel installed by this image: if I am not wrong, 2.6.37 was out in 2011.01, eight months after the 2010.05 iso was out...
did you do a netinstall? that fetches the latest packages from the mirror... Dieter
Le Tue, 1 Mar 2011 21:03:56 +0100, Dieter Plaetinck <dieter@plaetinck.be> a écrit :
did you do a netinstall? that fetches the latest packages from the mirror...
No, that was a "core" iso image, the source selected was "CD" (albeit being actually a usb key), no ethernet network physically available and wifi was not configured.
On Wed, 2 Mar 2011 07:51:08 +0100 didier gaumet <didier.gaumet@gmail.com> wrote:
Le Tue, 1 Mar 2011 21:03:56 +0100, Dieter Plaetinck <dieter@plaetinck.be> a écrit :
did you do a netinstall? that fetches the latest packages from the mirror...
No, that was a "core" iso image, the source selected was "CD" (albeit being actually a usb key), no ethernet network physically available and wifi was not configured.
Did you happen to reuse an old /boot or / partion? (or maybe had the wrong /boot partion in your booloader?)
Le Wed, 2 Mar 2011 17:53:41 +0100, Øyvind Heggstad <mrelendig@har-ikkje.net> a écrit :
Did you happen to reuse an old /boot or / partion? (or maybe had the wrong /boot partion in your booloader?)
Being at times a very absent-minded person, I was seriously beginning to doubt what I had actually done. So this morning, I downloaded the very same iso image from the very same mirror, verified its sha1sum, burnt it on a disc and installed it onto an usb key. The result was: - a brand new functional Archlinux with its 2.6.33 kernel and modules - an ashamed me. Much ado about nothing. The one reason of this problem I can think of is that being absent-minded, I forgot about somehow failing to upgrade properly to 2.6.37 after having *successfully* installed 2.6.33 from the iso. Please guys accept my apologies for having wasted your time, and my thanks for your answers :-)
On Thu, 3 Mar 2011 10:36:51 +0100 didier gaumet <didier.gaumet@gmail.com> wrote:
The one reason of this problem I can think of is that being absent-minded, I forgot about somehow failing to upgrade properly to 2.6.37 after having *successfully* installed 2.6.33 from the iso.
Please guys accept my apologies for having wasted your time, and my thanks for your answers :-)
Actually I knew it had to be some kind of PEBKAC: I'm familiar enough with the laws of physics to know you couldn't possibly have installed a kernel straight from the iso, if it only existed 8 months after we created the iso. So you didn't waste too much of my time. Dieter
Le Thu, 3 Mar 2011 10:45:19 +0100, Dieter Plaetinck <dieter@plaetinck.be> a écrit :
Actually I knew it had to be some kind of PEBKAC: [...]
I am familiar with the french expression for it but you just taught me the english acronym ;-)
participants (3)
-
didier gaumet
-
Dieter Plaetinck
-
Øyvind Heggstad