2009/9/30 Cliff McDiarmid <[email protected]>:
> Hi
>
> When upgrading a version of LFS 6.0 with a much newer kernel(2.6.27.10)in
> order to get a new wireless driver I'm getting a kernel panic and stop.
> Would there be a problem with upgrading an LFS with glibc-2.3.4 and older
> packages, to a newer kernel. I ask this because I have a much newer version
> of LFS and this particular kernel runs without problems.
>
> Any advice appreciated
>
> MAC
>
> --
6.0 ? Hmm, all-but 5 years old, with gcc-3.4.1.
In theory, gcc-3.4.1 should be good enough because
it meets the minimum requiremets in
Documentation/Changes, but on the other hand all
sorts of changes can break things and not get noticed
because nobody tested that particular version of gcc.
The 2.6.27 series ('stable') is supposed to be fine, but
2.6.27.10 is rather old - current is 2.6.27.35. I don't know
when the driver you want was committed to the stable
tree, but sometimes the back-porting goes wrong, and
a newer release might fix it. As always, newer kernels
should have more fixes for known problems.
I upgrade my desktop boxes frequently, have done
for years, and usually the only problems are from duff
code in -rc versions. But funnily enough, on one of my
non-desktop boxes (with a much newer system than
yours) I haven't managed to boot 2.6.27, and identifying
the problem is a low priority for me.
2.6.27 was accompanied by a lot of changes in the
disk area (libata now preferred to the old IDE), if I
remember correctly. So, do you have any idea where
it dies ? Sometimes you can see messages, particularly
if (like mine) it doesn't mount the rootfs.
If you know that, google in case anything useful comes
up.
Failing that, review your config. In fact, you should
probably do that anyway, there are some things in
recent kernels that most people will turn on because
their systems are recent enough, and it's possible you
acquired one of those settings. If in doubt, read the help.
After that, I suppose you need to work out when the
breakage happened, e.g. 2.6.27 (inital release), 2.6.26,
etc. ... Oh. 6.0 had the 2.6.8 kernel (I won't ask if
you've upgraded it since then) and udev 030. That
version of udev is not adequate, according to Changes
(unless that file in 2.6.27 is different from what is in
2.6.30).
Upgrading udev on a version of LFS before LFS-6.2
may be painful, as in "you keep both pieces". It might
work, or it might not. It's also possible that your version
of udev is not a problem, but there are no guarantees.
ĸen
--
After tragedy, and farce, "OMG poneys!"
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
