Dear All,
How to enable mod_jk2 in Suse-9.0 ?
I have some error when try to integrating Tomcat and Apache with Suse-9.0
This is my configuration file
# rpm -qa | grep apache
apache2-example-pages-2.0.47-63
apache2-doc-2.0.47-63
apache2-prefork-2.0.47-63
apache2-mod_php4-4.3.3-13
apache2-2.0.48-123
apache-ant-1.5.3-37
apache2-jakarta-tomcat-connectors-4.1.27-32
# cat /etc/sysconfig/apache2 | grep jk
APACHE_MODULES="access actions alias auth auth_dbm autoindex cgi dir env
expires include jk2 log_config mime negotiation php4 setenvif ssl suexec
userdir"
# cat /etc/apache2/httpd.conf | grep jk
Include /etc/apache2/conf.d/tomcat_jk.conf
# cat /etc/httpd/conf.d/tomcat_jk.conf
# simple configuration for apache (for AJP connector, modul mod_jk.so)
<IfModule mod_jk.c>
JkWorkersFile /opt/jakarta/tomcat/conf/workers.properties
JkLogFile /opt/jakarta/tomcat/logs/mod_jk.log
# Log level to be used by mod_jk
JkLogLevel error
# The following line makes apache aware of the location of
# the /examples context
Alias /examples "/opt/jakarta/tomcat/webapps/examples"
Hello all, Comparing the pre-Mantel and post-Mantel dmesg output from my SuSE 9.0 notebook, I can see that post-Mantel upgrade I am missing the following text in the dmesg output: "Intel(R) PRO/100 Network Driver - version 2.3.27 Copyright (c) 2003 Intel Corporation e100: selftest OK. e100: eth0: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled" I don't know much about kernels. Why does upgrading my kernel to Mantel's 2.6 series break the nic support? Any ideas on how to get it back? Thanks!
* dreadnought
I don't know much about kernels. Why does upgrading my kernel to Mantel's 2.6 series break the nic support? Any ideas on how to get it back?
Not to be rude, but if you don;t know much about kernels, you should steer clear of the mantel kernels, and esp. on notebooks simply stick to the stock SuSE kernel (2.4.21 I think was shipped with 9.0) . Currently listening to: pj92-03-04d1t07 Gerhard, (faliquid@xs4all.nl) == The Acoustic Motorbiker == -- __O You have had all that money can give you, but that wasn't enough =`\<, You became a thrill-seeker. Kill for the thrill. (=)/(=) The thrill-seeker comes from all walks of life. He comes from the home, a home where the parents are to busy to treat their children with respect."
On Wednesday 21 April 2004 14:56, Gerhard den Hollander wrote:
* dreadnought
(Tue, Apr 20, 2004 at 07:40:17PM -0700) I don't know much about kernels. Why does upgrading my kernel to Mantel's 2.6 series break the nic support? Any ideas on how to get it back?
Not to be rude, but if you don;t know much about kernels, you should steer clear of the mantel kernels, and esp. on notebooks simply stick to the stock SuSE kernel (2.4.21 I think was shipped with 9.0) .
Yes, 2.6 breaks the nic support but you can get it back easily by typing: modprobe nic-diver-name eg my nic driver is: eepro100 so I type: modprobe eepro100 I made it permanent on boot by adding the line: alias eth0 eepro100 to the file /etc/modprobe.conf HTH Steve.
Hi Steve, Thanks for the reply .. I gave "modprobe eepro100" a shot and it looks like everything in the dmesg output regarding the eepro100 is successful - however, a different driver is being used than the "Intel" driver from my default SuSE 9.0 installation. When I did an "ifconfig eth0 up" and "ifconfig" though, I see a 32 character hardware address with lots of 0's. This is the same way the nic would come up before I did "modprobe eepro100" and was/is my clue that the nic is not working properly. The hardware address should be 16 characters I think, or at least it is when the nic works on my default SuSE 9.0.
From the Gateway 200 ARC specifications, this is my nic chipset:
IntelR ICH3-M integrated LAN Controller and i82562ET Platform LAN Connect (PLC) device Not sure if that is eepro100 compatible or not .. Anyone else have one of these chipsets? -----Original Message----- From: steve-ss [mailto:mail@steve-ss.com] Sent: Wednesday, April 21, 2004 9:01 AM To: SuSE Help mail list Subject: Re: [SLE] Mantel 2.6 upgrade and dead notebook nic .. On Wednesday 21 April 2004 14:56, Gerhard den Hollander wrote:
* dreadnought
(Tue, Apr 20, 2004 at 07:40:17PM -0700) I don't know much about kernels. Why does upgrading my kernel to Mantel's 2.6 series break the nic support? Any ideas on how to get it back?
Not to be rude, but if you don;t know much about kernels, you should steer clear of the mantel kernels, and esp. on notebooks simply stick to the stock SuSE kernel (2.4.21 I think was shipped with 9.0) .
Yes, 2.6 breaks the nic support but you can get it back easily by typing: modprobe nic-diver-name eg my nic driver is: eepro100 so I type: modprobe eepro100 I made it permanent on boot by adding the line: alias eth0 eepro100 to the file /etc/modprobe.conf HTH Steve. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi Use whatever driver you had before with the 2.4 kernel. It just so happens that *mine* is eepro100. yast>network devices>change>edit>hardware details may help to find out what driver is needed. Steve. On Wednesday 21 April 2004 16:21, dreadnought wrote:
Hi Steve,
Thanks for the reply .. I gave "modprobe eepro100" a shot and it looks like everything in the dmesg output regarding the eepro100 is successful - however, a different driver is being used than the "Intel" driver from my default SuSE 9.0 installation. When I did an "ifconfig eth0 up" and "ifconfig" though, I see a 32 character hardware address with lots of 0's. This is the same way the nic would come up before I did "modprobe eepro100" and was/is my clue that the nic is not working properly. The hardware address should be 16 characters I think, or at least it is when the nic works on my default SuSE 9.0.
From the Gateway 200 ARC specifications, this is my nic chipset:
IntelR ICH3-M integrated LAN Controller and i82562ET Platform LAN Connect (PLC) device
Not sure if that is eepro100 compatible or not .. Anyone else have one of these chipsets?
-----Original Message----- From: steve-ss [mailto:mail@steve-ss.com] Sent: Wednesday, April 21, 2004 9:01 AM To: SuSE Help mail list Subject: Re: [SLE] Mantel 2.6 upgrade and dead notebook nic ..
On Wednesday 21 April 2004 14:56, Gerhard den Hollander
wrote:
* dreadnought
(Tue, Apr 20, 2004 at 07:40:17PM -0700) I don't know much about kernels. Why does upgrading my kernel to Mantel's 2.6 series break the nic support? Any ideas on how to get it back?
Not to be rude, but if you don;t know much about kernels, you should steer clear of the mantel kernels, and esp. on notebooks simply stick to the stock SuSE kernel (2.4.21 I think was shipped with 9.0) .
Yes, 2.6 breaks the nic support but you can get it back easily by typing: modprobe nic-diver-name
eg my nic driver is: eepro100 so I type: modprobe eepro100
I made it permanent on boot by adding the line:
alias eth0 eepro100
to the file /etc/modprobe.conf
HTH Steve.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (4)
-
dreadnought
-
Gerhard den Hollander
-
Muhammad Reza
-
steve-ss