On Mon, Feb 26, 2001 at 11:58:05PM -0600, Jerry Kreps wrote:
Why are these unselected drivers appearing?
IIRC you did compile your own kernel after the 7.1 install. My guess is when youdid the install yast also installed the kernel rpm. Unless you remove that rpm and rerun the make modules_install command followed by depmod -a you will continue to see these unresolved dependencies. HTH -- Togan Muftuoglu
I did install with yast1 and yes, it did install a kernel source, but it was for the 2.4 kernel, not the 2.2.18 kernel. I used yast to remove the 2.4 kernel and install the 2.2.18 kernel. Yast is an rpm tool and uses rpm files Nothing I want to do about that. Are you saying that I should download a tar source and install it? I'm not keen on that idea. The modules were already for the 2.2.18 kernel, so I thought it rather strange that a fresh install of the distro would install the 2.4 kernel source and the 2.2.18 kernel and modules. I've found SuSE 7.1 to be a very mixed bag. I've NEVER had so many problems of such a variety and so pervasive as the case with my copy of 7.1. It took all of 3 or 4 hours in 7.0 to do what I've been trying to do for the last three days in 7.1. Simply install the Zip100 drive on my second parallel card. I have to pay bills and run a reconcilliation, but I can't get my MoneyDance files off my zip drive. To be honest, if I had enountered these problems with SuSE 5.3 I wouldn't have used it. JLK On Tuesday 27 February 2001 00:12, Togan Muftuoglu wrote:
On Mon, Feb 26, 2001 at 11:58:05PM -0600, Jerry Kreps wrote:
Why are these unselected drivers appearing?
IIRC you did compile your own kernel after the 7.1 install. My guess is when youdid the install yast also installed the kernel rpm. Unless you remove that rpm and rerun the make modules_install command followed by depmod -a you will continue to see these unresolved dependencies.
HTH
Jerry Kreps wrote:
I did install with yast1 and yes, it did install a kernel source, but it was for the 2.4 kernel, not the 2.2.18 kernel. I used yast to remove the 2.4 kernel and install the 2.2.18 kernel. Yast is an rpm tool and uses rpm files Nothing I want to do about that. Are you saying that I should download a tar source and install it? I'm not keen on that idea.
No this is not what I meant. First have a look to what kernel rpms are installed either thru yast or via rpm -q . What I do normall is since the sue compiled kernel is unnecessarly big for my needs, I do issue a make cloneconfig command to get the suse config options. Then I remove the precooked kernel and the related kernel modules with yast and then compile my own kernel (for that I use the suse kernel source rpm lx_suse something) This way unresolved symbols do not come to the screen. On the other hand other than making the kernel image smaller, I think all the necessary modules are built by Suse so there should not be any problems using the suse supplied kernel (actually this is a must for suse support request) Yast for me is not an rpm tool but and administraiton tool using rpm as one menthod and actually does not use the full rpm commands (someone correct me I am wrong) yast uses rpm with --nodeps and --force options IIRC -- Togan Muftuoglu
On Tuesday 27 February 2001 01:14, Togan Muftuoglu wrote:
Jerry Kreps wrote:
I did install with yast1 and yes, it did install a kernel source, but it was for the 2.4 kernel, not the 2.2.18 kernel. I used yast to remove the 2.4 kernel and install the 2.2.18 kernel. Yast is an rpm tool and uses rpm files Nothing I want to do about that. Are you saying that I should download a tar source and install it? I'm not keen on that idea.
No this is not what I meant. First have a look to what kernel rpms are installed either thru yast or via rpm -q . What I do normall is since the sue compiled kernel is unnecessarly big for my needs, I do issue a make cloneconfig command to get the suse config options. Then I remove the precooked kernel and the related kernel modules with yast and then compile my own kernel (for that I use the suse kernel source rpm lx_suse something)
That was the first thing I did, after I saw that SuSE was using the 2.2.18 kernel and modules but had installed the 2.4 source tree. My box now has the 2.2.18 source tree, installed by yast. But, I didn't make cloneconfig the first time. I went through every option in menuconfig and set what I wanted and unset what I didn't need. JLK
This way unresolved symbols do not come to the screen. On the other hand other than making the kernel image smaller, I think all the necessary modules are built by Suse so there should not be any problems using the suse supplied kernel (actually this is a must for suse support request)
Yast for me is not an rpm tool but and administraiton tool using rpm as one menthod and actually does not use the full rpm commands (someone correct me I am wrong) yast uses rpm with --nodeps and --force options IIRC
participants (2)
-
Jerry Kreps -
Togan Muftuoglu