LinuKS-KDE-versions2.1.1 -& rpm - build/release-date #'s
Hello all - I have SuSE70 - kernel-2.4.2 - kde 2.1.1 update/w/qt2/3 - I am at the suse - LinuKS-page to get development parts of kde that I didn't include in my previous update to the kde 2.1.1 series. There is a message that says - 'Please note when updating any packages: Already installed packages listed at KDE2 base packages have to be of the same version as listed there. If unsure update all base packages!' I get the same versions, but rpm -qpi shows the ' build-release numbers are later than my 'kde-may series'. My question is, will these mix ok with the kde 2.1.1 installed-base, or will I get conflicts, with the newer, kde-build/release#'s, development-apps-libs?. I'm just trying to avoid potential problem with lib conflicts, esp. qt2.3, and static- libs . Thanks for any help.
I am using dhclient-3.0 to configure my cable modem ip. I've configure dhclient to start at bootup. At bootup it runs, and I obtain my ip ... in fact everything works properly, except that I get 2 "modprobe: Can't locate module errors". If I run rcdhclient start manually, I get the following in my logs. As you can see, it works, but I get this modprobe errors which are niggling. How can I fix this? A good start would be to know what module it is looking for. I never had this problem with other versions of dhclient (Suse 6.4). I get this error with the default suse kernel k_deflt. ------------BEGIN---------- Jul 22 19:32:01 foomanchu kernel: eth0: 0 multicast blocks dropped. Jul 22 19:32:02 foomanchu modify_resolvconf: no matching backup found, left everything alone Jul 22 19:32:02 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:03 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:06 foomanchu dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 22 19:32:06 foomanchu dhclient: DHCPACK from 203.164.3.215 Jul 22 19:32:06 foomanchu dhclient: bound to 203.164.22.41 -- renewal in 229257 seconds. -----------END----------- Thanks.
This is a bug in dhclient. If is fixed in 3.0rc8. It is benign,
though annoying. THe program is searching for interfaces, finding two
in your case, and then trying to load the driver named the empty
string instead of the actual name of the interface. The system can't
find them and prints the message with the name (empty) of the not
found module/driver at the end of the message.
Below is a diff between rc7 and rc8 that fixes the problem in
common/discover.c:
@@ -406,6 +406,7 @@
log_fatal ("Can't allocate interface %s: %s",
name, isc_result_totext (status));
tmp -> flags = ir;
+ strncpy (tmp -> name, name, IFNAMSIZ);
interface_reference (&tmp -> next, interfaces, MDL);
interface_dereference (&interfaces, MDL);
interface_reference (&interfaces, tmp, MDL);
Note that lines numbers will be different in rc4.
HTH,
Jeffrey
Quoting A Nourai
I am using dhclient-3.0 to configure my cable modem ip. I've configure dhclient to start at bootup. At bootup it runs, and I obtain my ip ... in fact everything works properly, except that I get 2 "modprobe: Can't locate module errors".
If I run rcdhclient start manually, I get the following in my logs. As you can see, it works, but I get this modprobe errors which are niggling.
How can I fix this? A good start would be to know what module it is looking for. I never had this problem with other versions of dhclient (Suse 6.4).
I get this error with the default suse kernel k_deflt.
Jul 22 19:32:01 foomanchu kernel: eth0: 0 multicast blocks dropped. Jul 22 19:32:02 foomanchu modify_resolvconf: no matching backup found, left everything alone Jul 22 19:32:02 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:03 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:06 foomanchu dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 22 19:32:06 foomanchu dhclient: DHCPACK from 203.164.3.215 Jul 22 19:32:06 foomanchu dhclient: bound to 203.164.22.41 -- renewal in 229257 seconds.
Thanks.
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
Thanks!
Yeh I noticed it was trying to load the driver for the empty string by
renaming modprobe to
modprobe.back and then checking my logs (which is the only way I know how to
find out which module modprobe is trying to load). I'll apply the patch.
I'd assume SuSE will also provide an update since it is a real annoying bug.
-----Original Message-----
From: Jeffrey Taylor [mailto:jeff.taylor@ieee.org]
Sent: Sunday, 22 July 2001 8:20 PM
To: suse-linux-e@suse.com
Subject: Re: [SLE] dhclient-3.0rc4 : modprobe error
This is a bug in dhclient. If is fixed in 3.0rc8. It is benign,
though annoying. THe program is searching for interfaces, finding two
in your case, and then trying to load the driver named the empty
string instead of the actual name of the interface. The system can't
find them and prints the message with the name (empty) of the not
found module/driver at the end of the message.
Below is a diff between rc7 and rc8 that fixes the problem in
common/discover.c:
@@ -406,6 +406,7 @@
log_fatal ("Can't allocate interface %s:
%s",
name, isc_result_totext
(status));
tmp -> flags = ir;
+ strncpy (tmp -> name, name, IFNAMSIZ);
interface_reference (&tmp -> next, interfaces, MDL);
interface_dereference (&interfaces, MDL);
interface_reference (&interfaces, tmp, MDL);
Note that lines numbers will be different in rc4.
HTH,
Jeffrey
Quoting A Nourai
I am using dhclient-3.0 to configure my cable modem ip. I've configure dhclient to start at bootup. At bootup it runs, and I obtain my ip ... in fact everything works properly, except that I get 2 "modprobe: Can't locate module errors".
If I run rcdhclient start manually, I get the following in my logs. As you can see, it works, but I get this modprobe errors which are niggling.
How can I fix this? A good start would be to know what module it is looking for. I never had this problem with other versions of dhclient (Suse 6.4).
I get this error with the default suse kernel k_deflt.
Jul 22 19:32:01 foomanchu kernel: eth0: 0 multicast blocks dropped. Jul 22 19:32:02 foomanchu modify_resolvconf: no matching backup found, left everything alone Jul 22 19:32:02 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:03 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:06 foomanchu dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 22 19:32:06 foomanchu dhclient: DHCPACK from 203.164.3.215 Jul 22 19:32:06 foomanchu dhclient: bound to 203.164.22.41 -- renewal in 229257 seconds.
Thanks.
-----Original Message-----
From: Jeffrey Taylor [mailto:jeff.taylor@ieee.org]
Sent: Sunday, 22 July 2001 8:20 PM
To: suse-linux-e@suse.com
Subject: Re: [SLE] dhclient-3.0rc4 : modprobe error
This is a bug in dhclient. If is fixed in 3.0rc8. It is benign,
though annoying. THe program is searching for interfaces, finding two
in your case, and then trying to load the driver named the empty
string instead of the actual name of the interface. The system can't
find them and prints the message with the name (empty) of the not
found module/driver at the end of the message.
Below is a diff between rc7 and rc8 that fixes the problem in
common/discover.c:
@@ -406,6 +406,7 @@
log_fatal ("Can't allocate interface %s:
%s",
name, isc_result_totext
(status));
tmp -> flags = ir;
+ strncpy (tmp -> name, name, IFNAMSIZ);
interface_reference (&tmp -> next, interfaces, MDL);
interface_dereference (&interfaces, MDL);
interface_reference (&interfaces, tmp, MDL);
Note that lines numbers will be different in rc4.
HTH,
Jeffrey
Quoting A Nourai
I am using dhclient-3.0 to configure my cable modem ip. I've configure dhclient to start at bootup. At bootup it runs, and I obtain my ip ... in fact everything works properly, except that I get 2 "modprobe: Can't locate module errors".
If I run rcdhclient start manually, I get the following in my logs. As you can see, it works, but I get this modprobe errors which are niggling.
How can I fix this? A good start would be to know what module it is looking for. I never had this problem with other versions of dhclient (Suse 6.4).
I get this error with the default suse kernel k_deflt.
Jul 22 19:32:01 foomanchu kernel: eth0: 0 multicast blocks dropped. Jul 22 19:32:02 foomanchu modify_resolvconf: no matching backup found, left everything alone Jul 22 19:32:02 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:03 foomanchu modprobe: modprobe: Can't locate module Jul 22 19:32:06 foomanchu dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 22 19:32:06 foomanchu dhclient: DHCPACK from 203.164.3.215 Jul 22 19:32:06 foomanchu dhclient: bound to 203.164.22.41 -- renewal in 229257 seconds.
Thanks.
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (3)
-
A Nourai -
Jeffrey Taylor -
John W Mislan