Re: kernel/mkinitrd udpate broken? [Was: Missing in action...] (fwd)
by Satish Balay
<using forward to start a new thread>
On Wed, 1 Sep 2004, Satish Balay wrote:
> BTW: I notice the following error in today's update:
>
> --
> hal-cups-utils 100 % done 18/120
> Stopping cups: [ OK ]
> Starting cups: [ OK ]
> mkinitrd 100 % done 19/120
> /var/tmp/rpm-tmp.23804: line 1: 5655 Segmentation fault /sbin/modprobe loop 2>/dev/null >/dev/null
> kernel 100 % done 20/120
> --
Ok - something causes the newly installed kernel (538) not to boot. I
get:
---
Red Hat nash version 4.1.9 starting
insmod: error inserting '/lib/ext3.ko': -1 Unknown symbol in module
ERROR /bin/insmod exited abnormally!
mount: error 19 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
---
And I get similar error wth kerne-535 installed which was installed
nash-2.1.8..
I'm able to boot to kernel-533 (which was working fine before the
updates/reboot) - but now I get a bunch of ext3 errors.
And 'lsmod' shows only module loaded are 'ext3' and 'jbd' (no
networking - so I can't cut/paste)
Something is seriously broken..
Satish
19 years, 7 months
yum - checkbootloader
by shrek-m@gmx.de
hi,
fc3t1 yesterdays/todays update
# rpm -q yum
yum-2.1.0-1
can i ignore this error?
# yum -y --exclude=libsoup\* update
<snip>
[...]
Completing update for dev - 269/271
Completing update for libxml2-devel - 270/271
Completing update for gnome-desktop - 271/271
Kernel Updated/Installed, checking for bootloader
Traceback (most recent call last):
File "/usr/bin/yum", line 30, in ?
File "/usr/share/yum/yummain.py", line 375, in main
File "/usr/share/yum/pkgaction.py", line 588, in kernelupdate
ImportError: No module named checkbootloader
</snip>
--
shrek-m
19 years, 7 months
Oddity when removing kernel versions
by Paul F. Johnson
Hi,
Not sure if this is a broken script problem, but when I remove a kernel,
I'm still finding directories in /lib/modules for the kernel versions
I've removed.
Is this normal and if it is, why are they still there?
TTFN
Paul
--
"Our enemies are innovative and resourceful - and so are we,"
"They never stop thinking about new ways to harm our country and our
people - and neither do we." - George W. Bush, Aug 2004
19 years, 7 months
module-init-tools-3.0-2.i386.rpm
by Paul F. Johnson
--
Get your free @ukpost.com account now
http://www.ukpost.com/
Hi,
For some reason best known to my computer, /var/cache/yum/development/packages is completely empty, so I'm left with a machine which can't be connected to the net for fixes.
I've seen a few suggestions for getting things to work by using module-init-tools-3.0-2. Unfortunately, I don't have this RPM.
Can someone please make it available (upload it somewhere)?
I've googled around to see if I can find the package anywhere, but nothing is around.
Thanks
TTFN
Paul
(using Lynx from his laptop, connected to his son's machine as neat seems to be broken in the current set of releases as well)
19 years, 7 months
RE: kernel/mkinitrd udpate broken? [Was: Missing in action...]
by Fred New
On Wed 9/1/2004 at 7:07 PM, John Ellson wrote:
> In addition to backing down to kernel-533, I also backed out to
> initscripts-7.73-1 and module-init-tools-3.0-2
> (not sure that both are broken, but one of them cleared up the module issues.)
>
> I did not back out mkinitrd.
>
> I had to back out to xorg-x11-6.7.0-7.2 because of the i810 graphics issue.
>
> And I backed out to metacity-2.8.4-1 because my desktop was still funky.
> (not 100% sure about this last being a real problem.)
>
> Basically, there are multiple breakages in the latest updates.
>
> Don't lose your old rpms.
With the last set of updates, I saw a lot of segfaults from modprobe, so I
backed out module-init-tools:
rpm -Uvh --oldpackage module-init-tools-3.0-2.i386.rpm
Everything else seems to be running okay so far:
kernel-2.6.8-1.538
xorg-x11-6.7.99.903-2
selinux-policy-targeted-1.17.8-1
Fred
19 years, 7 months
Missing in action...
by Paul F. Johnson
Hi,
libgal-2.2.so.0, libsoup-2.2.so.6, libgal-a11y-2.2.so.0 are missing, so
ev and ev-data-server can't be updated. Is this a rebuild problem or
have they just not hit rawhide yet?
TTFN
Paul
--
"If I face my God tomorrow, I can tell Him I am innocent.
I've never harmed anyone. I have cheated no one.
I have deceived no one. I have hurt no one.
Except myself. And that He will forgive me." - Hans Holzel
19 years, 7 months
Intel i810 graphics
by Mark Guzzo
Hello all,
I've just updated my FC3-T1 and now in X the screen/apps do not get
refreshed unless I mouse over the area. I tried different resolutions,
but the problem is still there.
For now I changed the driver in xorg.confg from "i810" to "vesa" and
everything works great even if it's at 800x600 :-(
[guzmar@LORDLINUX ~]$ rpm -q xorg-x11
xorg-x11-6.7.99.903-1
Should I bugzilla this ?
Mark
19 years, 7 months
New kudzu test updates for FC1 and FC2
by Bill Nottingham
This update reworks the network device detection in kudzu, fixing various
reported bugs, among them #108178, #111639, #112837, #120584, #120988,
#122983, and #124765.
If no new regressions are posted, this will be pushed live by Tuesday,
September 3.
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/
fecb12d2dec11f4a563ce105b75baf47 SRPMS/kudzu-1.1.36.3-1.src.rpm
95d8210cfcdc6f18dabd886ac7ca06ae x86_64/kudzu-1.1.36.3-1.x86_64.rpm
9dedc825c538c0fc24eac2410accfb36 x86_64/kudzu-devel-1.1.36.3-1.x86_64.rpm
e3c61d98a323e41f40fc2ebf8c00bcdc x86_64/debug/kudzu-debuginfo-1.1.36.3-1.x86_64.rpm
d21120943cf168135655ab0b090f33b3 i386/kudzu-1.1.36.3-1.i386.rpm
97ae20f26adbadd39980ee4a854be449 i386/kudzu-devel-1.1.36.3-1.i386.rpm
7b56d41513a2ab540600187616c323c9 i386/debug/kudzu-debuginfo-1.1.36.3-1.i386.rpm
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/2/
d4bddcf0642ca5ce5395db42aca40205 SRPMS/kudzu-1.1.68.2-1.src.rpm
78b3311d8899cbb82abd1966f513232a x86_64/kudzu-1.1.68.2-1.x86_64.rpm
be9e499dda11c7c64bf88b8a7a9933c6 x86_64/kudzu-devel-1.1.68.2-1.x86_64.rpm
6712cf0ea2acf1ac6069e1d2ffc86dd4 x86_64/debug/kudzu-debuginfo-1.1.68.2-1.x86_64.rpm
8b756f69a035b946e23af14520855b3e i386/kudzu-1.1.68.2-1.i386.rpm
97429801907a848da96cc57824d87924 i386/kudzu-devel-1.1.68.2-1.i386.rpm
1b353518033e838c16d16c3af7ec1773 i386/debug/kudzu-debuginfo-1.1.68.2-1.i386.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command. You may
need to edit your up2date channels configuration. Within
/etc/sysconfig/rhn/sources enable the following line:
yum updates-testing http://fedora.redhat.com/updates/testing/fedora-core-2
---------------------------------------------------------------------
19 years, 7 months