Re: [SLE] Problem with PCMCIA with laptop (Suse 8.0)
Thanks for your reply! Here's the output if I try external: # /etc/init.d/pcmcia start Starting external PCMCIA /lib/modules/2.4.18-64GB-SMP/pcmcia-external/i82365.o: invalid parameter parm_probe_io /lib/modules/2.4.18-64GB-SMP/pcmcia-external/i82365.o: insmod /lib/modules/2.4.18-64GB-SMP/pcmcia-external/i82365.o failed /lib/modules/2.4.18-64GB-SMP/pcmcia-external/i82365.o: insmod i82365 failed failed I looked in that folder and found no yenta_socket so it seems that I cannot use that approach. Any other suggestions? Ico On Monday 20 May 2002 09:07, you wrote:
What about PCMCIA_SYSTEM="external" ?
--tosi
On Mon, 2002-05-20 at 18:44, Ivica Bukvic wrote:
Hi all!
I've just finished installing Suse 8.0 on my laptop (inspiron 8200) and am having some problems with the pcmcia service. It freezes my cpu every time I boot. I've looked already through the search database and found out what was the cause but here's the confusing part:
If I do: modprobe pcmcia_core modprobe yenta_socket modprobe ds
Everything starts just fine and the pcmcia slots work fine.
However, if I do, /etc/init.d/pcmcia start -> it freezes
Here's my /etc/sysconfig/pcmcia file (which I altered accordingly but it makes no difference):
# # There are two PCMCIA Systems available: The external from D.Hinds, # which has proven to work flawlessly, and a newer one included in # the kernel source tree, which may be neccessary with some (new) # hardware. You can choose here which one you like to use. Set the # variable to "external" or "kernel". # If there is only one of these systems installed this varable will # be ignored. # PCMCIA_SYSTEM="kernel"
# This variable lets you manually controls which socket driver will # be used for the choosen pcmcia system. Valid Values are "i82365" # or "tcic" for dhinds pcmcia or "yenta_socket", "i82365" or "tcic" # for kernel pcmcia. # If it is left empty, the start script will determine it or use a # reasonable default, so you don't have to set it in most cases. # PCMCIA_PCIC="yenta_socket"
# # PCMCIA_PCIC_OPTS - socket driver timing parameters here. These # parameters are described in "man i82365" (or "man tcic"). # e.g.: PCMCIA_PCIC_OPTS="par1=val1 par2=val21,val22 par3=val3" # For more information, look for "PCIC_OPTS" in the PCMCIA-HOWTO. # You can find it under /usr/doc/packages/pcmcia. # These options will be ignored if you use kernel PCMCIA. (Exactly when # yenta_socket has been choosen) # # If PCMCIA locks your System, try the following option with a list # of free interrupts (and which won't be used later) and/or disable # the use of pci interrupts. # e.g. PCMCIA_PCIC_OPTS="irq_list=3,4,5,7,9,10,11 pci_int=0" # PCMCIA_PCIC_OPTS="probe_io=0"
# # PCMCIA_CORE_OPTS - Put pcmcia_core options here. These options # are described in "man pcmcia_core" # For more information, look for "CORE_OPTS" in the PCMCIA-HOWTO. # You can find it under /usr/doc/packages/pcmcia. # These options are used both for external and kernel PCMCIA. # PCMCIA_CORE_OPTS=""
Any help would be greatly appreciated! Thanks!
Ico
-- 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 archives at http://lists.suse.com
Hi, Have a problem with SuSEfirewall2 on SuSE8.0 - situation is as follow: when turning on SuSEfirewall2 basicly for masquerade reason I can not access both IP addresses (external and internal network) on my firewall machine from INTERNAL NETWORK only - external is OK ?! Have any hint what to change to have an access from internal network to my firewall machine - I need that access because this machine is runing SambaPDC so it is necessery. Thanks in advance this is my /etc/sysconfig/SuSEfirewall2 config file: FW_DEV_EXT="eth0" FW_DEV_INT="eth0:1" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.30.0/24" exactly what is written into an example file in /usr/share/doc/packgages/SuSEfirewall2
Hi The difference in my setup is: FW_DEV_INT=eth0 FW_MASQ_DEV=eth1 FW_PROTECT_FROM_INTERNAL=no IP_FORWARD=yes Try it, and let us know if it works. Jaska. On Monday 20 May 2002 20:36, Ryszard Hodiak wrote:
Hi,
Have a problem with SuSEfirewall2 on SuSE8.0 - situation is as follow: when turning on SuSEfirewall2 basicly for masquerade reason I can not access both IP addresses (external and internal network) on my firewall machine from INTERNAL NETWORK only - external is OK ?!
Have any hint what to change to have an access from internal network to my firewall machine - I need that access because this machine is runing SambaPDC so it is necessery.
Thanks in advance
this is my /etc/sysconfig/SuSEfirewall2 config file:
FW_DEV_EXT="eth0" FW_DEV_INT="eth0:1" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.30.0/24"
exactly what is written into an example file in /usr/share/doc/packgages/SuSEfirewall2
Hi, I'm sorry to say that but it is not working still?! Mayby the problem is that I don't have two network adapter but only one and I made an alias ? (for me it wouldn't be a reason as long as I have two up interfaces ) cheers, Richard On Mon, 20 May 2002, jaakko tamminen wrote:
Hi
The difference in my setup is: FW_DEV_INT=eth0 FW_MASQ_DEV=eth1 FW_PROTECT_FROM_INTERNAL=no IP_FORWARD=yes
Try it, and let us know if it works.
Jaska.
On Monday 20 May 2002 20:36, Ryszard Hodiak wrote:
Hi,
Have a problem with SuSEfirewall2 on SuSE8.0 - situation is as follow: when turning on SuSEfirewall2 basicly for masquerade reason I can not access both IP addresses (external and internal network) on my firewall machine from INTERNAL NETWORK only - external is OK ?!
Have any hint what to change to have an access from internal network to my firewall machine - I need that access because this machine is runing SambaPDC so it is necessery.
Thanks in advance
this is my /etc/sysconfig/SuSEfirewall2 config file:
FW_DEV_EXT="eth0" FW_DEV_INT="eth0:1" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.30.0/24"
exactly what is written into an example file in /usr/share/doc/packgages/SuSEfirewall2
-- 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 archives at http://lists.suse.com
* Ryszard Hodiak;
Hi,
I'm sorry to say that but it is not working still?! Mayby the problem is that I don't have two network adapter but only one and I made an alias ? (for me it wouldn't be a reason as long as I have two up interfaces )
What does FW_SERVICE_SAMBA has (by default it is "no" -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
made an alias ? (for me it wouldn't be a reason as long as I have two up interfaces )
What does FW_SERVICE_SAMBA has (by default it is "no"
FW_SERVICE_SAMBA is set to "yes" for obvious reason (I have a Samba PCD server) and also I set FW_SERVICE_DHCPD="yes" because this machine is also DHCP server for internal network cheers, Richard
--
Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
* Ryszard Hodiak;
FW_SERVICE_SAMBA is set to "yes" for obvious reason (I have a Samba PCD server)
and also I set FW_SERVICE_DHCPD="yes" because this machine is also DHCP server for internal network
Could you send the output of the firewall config grep -v # /etc/sysconfig/SuSEfirewall2 -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
Here you are - this is my /etc/sysconfig/SuSEfirewall2 config file: FW_DEV_EXT="eth0" FW_DEV_INT="eth0:1" FW_ROUTE="yes" FW_MASQUERADE="yes" IP_FORWARD="yes" #FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_DEV="eth0:1" FW_MASQ_NETS="0/0" (also tryied with 10.10.30.0/24) FW_SERVICE_DHCPD="yes" FW_SERVICE_SAMBA="yes" FW_PROTECT_FROM_INTERNAL="no" FW_LOG_ACCEPT_ALL="no" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_DROP_ALL="no" FW_LOG_DROP_CRIT="yes" FW_AUTOPROTECT_SERVICES="no" FW_ALLOW_FW_TRACEROUTE="yes"
Could you send the output of the firewall config
grep -v # /etc/sysconfig/SuSEfirewall2
--
Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
* Ryszard Hodiak;
Here you are - this is my /etc/sysconfig/SuSEfirewall2 config file:
Can you try with the changes I made FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.30/24" (if your network topology is different put the proper ones) FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" Then start /sbin/SuSefirewall test (warning this is not protection) and try to do the things that you were unable to do before (in theory you should be able to do all the things) get a copy of the firewall log ( interested parts is DROP ) Now start /sbin/SuSEgirewall (now you are on protection) try the things again if you fail accomplishing whatyou want to do compare the firewall log with the previous log (the one you had copied when running in the test mode) Report back if you fail succeed etc. but DO NOT give up :-) -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
Hi Just a thought as we had a similar problem. Do you have broadband internet, e.g. connection from a DSL modem? Where does your internet plug into? The hub/switch? Try: FW_DEV_EXT= ppp0 Steve. On Tuesday 21 May 2002 09:13, Ryszard Hodiak wrote:
Hi,
I'm sorry to say that but it is not working still?! Mayby the problem is that I don't have two network adapter but only one and I made an alias ? (for me it wouldn't be a reason as long as I have two up interfaces )
cheers, Richard
On Mon, 20 May 2002, jaakko tamminen wrote:
Hi
The difference in my setup is: FW_DEV_INT=eth0 FW_MASQ_DEV=eth1 FW_PROTECT_FROM_INTERNAL=no IP_FORWARD=yes
Try it, and let us know if it works.
Jaska.
On Monday 20 May 2002 20:36, Ryszard Hodiak wrote:
Hi,
Have a problem with SuSEfirewall2 on SuSE8.0 - situation is as follow: when turning on SuSEfirewall2 basicly for masquerade reason I can not access both IP addresses (external and internal network) on my firewall machine from INTERNAL NETWORK only - external is OK ?!
Have any hint what to change to have an access from internal network to my firewall machine - I need that access because this machine is runing SambaPDC so it is necessery.
Thanks in advance
this is my /etc/sysconfig/SuSEfirewall2 config file:
FW_DEV_EXT="eth0" FW_DEV_INT="eth0:1" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="10.10.30.0/24"
exactly what is written into an example file in /usr/share/doc/packgages/SuSEfirewall2
-- 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 archives at http://lists.suse.com
participants (5)
-
Ivica Bukvic -
jaakko tamminen -
Ryszard Hodiak -
steve -
Togan Muftuoglu