Re: PCMCIA configuration in sarge
Am 2006-03-14 23:09:07, schrieb Doofus: orinoco_cs orinoco hermes and then after boot is finished, ds.o is loaded but not my driver modules. I'm guessing this is because the init scripts are trying to load the contents of /etc/modules before ds.o is loaded, which won't work? Please correct me if I'm wrong. You need to add those modules to your pcmcia-config. There is a section where you can telle the script what to load. Greetings Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration in sarge
Doofus wrote: Andrei Popescu wrote: On Tue, 14 Mar 2006 23:09:07 + Doofus [EMAIL PROTECTED] wrote: After my laptop is booted, I can get driver modules: orinoco_cs orinoco hermes loaded just by typing `modprobe orinoco_cs` Now I'm trying, unsuccessfully, to get them loaded automatically at boot time. If I put any or all of the modules in /etc/modules, I get an error message in the boot process very close to: ds: no socket driver! and then after boot is finished, ds.o is loaded but not my driver modules. I'm guessing this is because the init scripts are trying to load the contents of /etc/modules before ds.o is loaded, which won't work? Please correct me if I'm wrong. Can someone explain what's happening here, and what the solution is get everything loaded in the right order? I haven't found an answer in /usr/share/doc/pcmcia_cs. kernel 2.4.27 dell inspiron 8200 Many thanks for any assistance. Just a wild thought ... did you try adding ds to /etc/modules? (before the others of course). That is if ds.o is also a module (AFAIK modules now have the extension .ko) Andrei I should have thought of trying that in view of my description above. It still doesn't work though. The exact error message is: ds: No socket drivers loaded! but as I said the ds module does get loaded a bit later - probably by the pcmcia scripts. I'm using the kernel pcmcia support and the yenta socket driver, and Dave Hinds pcmcia_cs package. There's obviously something not in place that's preventing the ds.o module from being loaded early in the boot - don't know what it is though. I guess I could just compile some of this stuff into the kernel but I don't really want to do that. The problem, I believe, is not with ds, but with something that ds depends on (one of the socket networking drivers). Most (all?) of the networking stuff on Debian systems seems to be started in the /etc/rcS.d directory by the S40networking script. You might want to consider adding your own rc script, linked to a file name in /etc/rcS.d that would make it run after the S40networking script, that does the modprobe of orinoco_cs. If I understand the rc setup, this should provide the sockets needed by ds, which would then load, followed by your orinoco related drivers. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration in sarge
Not sure of any of this, but; Have you loaded yenta_socket ? On a vanilla kernel Sarge 3.1r1 (kernel 2.6.8-2-i386), it's lisyed in 'lsmod'. Also note my (Debian's) default runlevel is 2, so perhaps review ; $ cat /etc/rc2.d/S20pcmcia I have this is lsmod; ds 17796 0 yenta_socket 19200 0 pcmcia_core63028 2 ds,yenta_socket See; http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123713 follow the older bug if necessary (123457 ?) AFAIK, as mentioned, 2.6 kernel (at some point in version) uses .ko , not .o Do a $ locate yenta /lib/modules/2.6.8-2-386/kernel/drivers/pcmcia/yenta_socket.ko perhaps also do; $ locate pcmcia to find related documentation (locally) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PCMCIA configuration in sarge
After my laptop is booted, I can get driver modules: orinoco_cs orinoco hermes loaded just by typing `modprobe orinoco_cs` Now I'm trying, unsuccessfully, to get them loaded automatically at boot time. If I put any or all of the modules in /etc/modules, I get an error message in the boot process very close to: ds: no socket driver! and then after boot is finished, ds.o is loaded but not my driver modules. I'm guessing this is because the init scripts are trying to load the contents of /etc/modules before ds.o is loaded, which won't work? Please correct me if I'm wrong. Can someone explain what's happening here, and what the solution is get everything loaded in the right order? I haven't found an answer in /usr/share/doc/pcmcia_cs. kernel 2.4.27 dell inspiron 8200 Many thanks for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration in sarge
On Tue, 14 Mar 2006 23:09:07 + Doofus [EMAIL PROTECTED] wrote: After my laptop is booted, I can get driver modules: orinoco_cs orinoco hermes loaded just by typing `modprobe orinoco_cs` Now I'm trying, unsuccessfully, to get them loaded automatically at boot time. If I put any or all of the modules in /etc/modules, I get an error message in the boot process very close to: ds: no socket driver! and then after boot is finished, ds.o is loaded but not my driver modules. I'm guessing this is because the init scripts are trying to load the contents of /etc/modules before ds.o is loaded, which won't work? Please correct me if I'm wrong. Can someone explain what's happening here, and what the solution is get everything loaded in the right order? I haven't found an answer in /usr/share/doc/pcmcia_cs. kernel 2.4.27 dell inspiron 8200 Many thanks for any assistance. Just a wild thought ... did you try adding ds to /etc/modules? (before the others of course). That is if ds.o is also a module (AFAIK modules now have the extension .ko) Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration in sarge
Andrei Popescu wrote: On Tue, 14 Mar 2006 23:09:07 + Doofus [EMAIL PROTECTED] wrote: After my laptop is booted, I can get driver modules: orinoco_cs orinoco hermes loaded just by typing `modprobe orinoco_cs` Now I'm trying, unsuccessfully, to get them loaded automatically at boot time. If I put any or all of the modules in /etc/modules, I get an error message in the boot process very close to: ds: no socket driver! and then after boot is finished, ds.o is loaded but not my driver modules. I'm guessing this is because the init scripts are trying to load the contents of /etc/modules before ds.o is loaded, which won't work? Please correct me if I'm wrong. Can someone explain what's happening here, and what the solution is get everything loaded in the right order? I haven't found an answer in /usr/share/doc/pcmcia_cs. kernel 2.4.27 dell inspiron 8200 Many thanks for any assistance. Just a wild thought ... did you try adding ds to /etc/modules? (before the others of course). That is if ds.o is also a module (AFAIK modules now have the extension .ko) Andrei I should have thought of trying that in view of my description above. It still doesn't work though. The exact error message is: ds: No socket drivers loaded! but as I said the ds module does get loaded a bit later - probably by the pcmcia scripts. I'm using the kernel pcmcia support and the yenta socket driver, and Dave Hinds pcmcia_cs package. There's obviously something not in place that's preventing the ds.o module from being loaded early in the boot - don't know what it is though. I guess I could just compile some of this stuff into the kernel but I don't really want to do that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration
On 15 Jan 2006, Tom Allison wrote: Anthony Campbell wrote: [snip] This may not be relevant, but I've had problems with my Cisco Aironet 340 which sound similar. I eventually tracked them to hotplug. If you have upgraded this recently you could try going back to the version in Stable. Anthony Similarly, I reset my apt_preferences from unstable to testing. purged everything related to pcmcia and wireless. reinstalled pcmcia-cs and wireless tools. Now it works. kernel 2.6.15. I'm thinking there might be a big fat hairy bug when whatever is in unstable gets into testing Unfortunately my installation, until today, was rather spread out between testing and unstable. That's been remedied as I can no longer afford this to be an unstable branch. I need it to work. I would downgrade to stable if I could, but I have a few other packages that I need in testing, so this is as far as I dare go. I'm following unstable myself (and it doesn't seem to be noticeably more hazardous than following testing, which I used to do) and mostly things don't break too badly. However the hotplug gotcha was very difficult to spot and to disentangle from wireless-tools etc. I submitted a bug report on hotplug, naturally, but nothing has come back beyond the formal acknowledgement. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration
I'm following unstable myself (and it doesn't seem to be noticeably more hazardous than following testing, which I used to do) and mostly things don't break too badly. However the hotplug gotcha was very difficult to spot and to disentangle from wireless-tools etc. I submitted a bug report on hotplug, naturally, but nothing has come back beyond the formal acknowledgement. It takes time for the bug reports to get processed. Some packages have to wait for a confirmation from other users to keep from chasing every It won't run bug report. Many times I was convinced I had found a real bug only to realize that I needed to RTFM better. I still submit a bug, but a minor one as a suggested improvement. This one I think was real only because it was working for 1 year and then broke in an upgrade. Unfortunately I've scrambled my installation enough to be uncertain what exactly the cause might be. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PCMCIA configuration
Grr... I've having problems with my Orinoco gold pcmcia card that used to work. I'll assume some kind of upgrade problem maybe but whatever it is, I'm no longer able to sort it out myself. From the syslog, it appears that the encryption is no longer valid. This is confusing because I haven't changed anything (that I know of) for well over a year. I've checked the access point and it's working and such... help? Between /etc/pcmcia/network.opts /etc/pcmcia/wireless.opts /etc/network/ifconfig I'm not getting anything to work. the card doesn't appear to load at all or only partially. ifconfig shows wifi0 Link encap:UNSPEC HWaddr 00-02-2D-61-9C-4E-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:652 (652.0 b) Interrupt:3 Base address:0x100 wlan0 Link encap:Ethernet HWaddr 00:02:2D:61:9C:4E inet6 addr: fe80::202:2dff:fe61:9c4e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:652 (652.0 b) Interrupt:3 Base address:0x100 iwconfig shows lono wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. wifi0 IEEE 802.11b ESSID:SECRET Nickname:notebook Mode:Managed Frequency:2.422 GHz Access Point: None Bit Rate:2 Mb/s Sensitivity=1/3 Retry limit:4 RTS thr:off Power Management:off wlan0 IEEE 802.11b ESSID:SECRET Nickname:notebook Mode:Managed Frequency:2.422 GHz Access Point: None Bit Rate:2 Mb/s Sensitivity=1/3 Retry limit:4 RTS thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ## At some point I had this working nicely under eth1 in the /etc/network/interfaces file with a configuration in that file of: auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet dhcp wireless_essid SECRET wireless_mode managed wireless_key1 s:ANOTHER_SECRET wireless_defaultkey 1 and syslog statements of: Jan 15 10:08:02 localhost kernel: prism2_config() failed Jan 15 10:08:03 localhost cardmgr[3905]: executing: './network start wlan0 21' Jan 15 10:08:03 localhost cardmgr[3905]: + Wavelan IEEE Orinoco Jan 15 10:08:03 localhost cardmgr[3905]: + iwconfig wlan0 mode Managed Jan 15 10:08:03 localhost kernel: prism2: wlan0: operating mode changed 3 - 2 Jan 15 10:08:03 localhost cardmgr[3905]: + iwconfig wlan0 key s:ANOTHER_SECRET Jan 15 10:08:03 localhost kernel: Could not read current WEP flags. Jan 15 10:08:03 localhost kernel: wifi0: encryption setup failed Jan 15 10:08:03 localhost kernel: wlan0: set_encryption failed Jan 15 10:08:03 localhost cardmgr[3905]: + Error for wireless request Set Encode (8B2A) : Jan 15 10:08:03 localhost cardmgr[3905]: + SET failed on device wlan0 ; Invalid argument. Jan 15 10:08:03 localhost cardmgr[3905]: + iwconfig wlan0 essid SECRET Jan 15 10:08:03 localhost cardmgr[3905]: + Allison network Jan 15 10:08:03 localhost cardmgr[3905]: + /sbin/ifconfig wlan0 up Jan 15 10:08:03 localhost cardmgr[3905]: + /sbin/dhclient wlan0 /dev/null 21 Jan 15 10:08:03 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c Jan 15 10:08:03 localhost kernel:retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS) Jan 15 10:08:03 localhost kernel:A1=00:00:00:00:00:00 A2=00:02:2d:61:9c:4e A3=33:33:00:00:00:16 A4=00:00:00:00:00:00
Re: PCMCIA configuration
On Sunday, 15 January 2006 at 10:22:59 -0500, Tom Allison wrote: Grr... I've having problems with my Orinoco gold pcmcia card that used to work. I'll assume some kind of upgrade problem maybe but whatever it is, I'm no longer able to sort it out myself. From the syslog, it appears that the encryption is no longer valid. This is confusing because I haven't changed anything (that I know of) for well over a year. I've checked the access point and it's working and such... help? Between /etc/pcmcia/network.opts /etc/pcmcia/wireless.opts /etc/network/ifconfig I'm not getting anything to work. the card doesn't appear to load at all or only partially. I have a very similar problem with an Orinoco PCMCIA card. There were a number of suggestions here a couple of weeks ago, and on debian-laptop just afterwards, but no solution yet. One thing I haven't yet tried is getting the latest driver. Does your card connect if you temporarily turn off encryption at the access point? Mine does (by manual 'ifup eth0'). If it does we may have the same complaint... -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration
On 1/15/2006, Richard Lyons [EMAIL PROTECTED] wrote: On Sunday, 15 January 2006 at 10:22:59 -0500, Tom Allison wrote: Grr... I've having problems with my Orinoco gold pcmcia card that used to work. I'll assume some kind of upgrade problem maybe but whatever it is, I'm no longer able to sort it out myself. From the syslog, it appears that the encryption is no longer valid. This is confusing because I haven't changed anything (that I know of) for well over a year. I've checked the access point and it's working and such... help? Between /etc/pcmcia/network.opts /etc/pcmcia/wireless.opts /etc/network/ifconfig I'm not getting anything to work. the card doesn't appear to load at all or only partially. I have a very similar problem with an Orinoco PCMCIA card. There were a number of suggestions here a couple of weeks ago, and on debian-laptop just afterwards, but no solution yet. One thing I haven't yet tried is getting the latest driver. Does your card connect if you temporarily turn off encryption at the access point? Mine does (by manual 'ifup eth0'). If it does we may have the same complaint... --Jan 15 11:30:03 localhost kernel: hostap_cs: setting Vcc=33 (constant) Jan 15 11:30:03 localhost kernel: hostap_cs: CS_EVENT_CARD_INSERTION Jan 15 11:30:03 localhost kernel: hostap_cs: setting Vcc=50 (from config) Jan 15 11:30:03 localhost kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01) Jan 15 11:30:03 localhost kernel: IO window settings: cfg-io.nwin=1 dflt.io.nwin=1 Jan 15 11:30:03 localhost kernel: io-flags = 0x0046, io.base=0x, len=64 Jan 15 11:30:03 localhost kernel: hostap_cs: Registered netdevice wifi0 Jan 15 11:30:03 localhost kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f Jan 15 11:30:03 localhost kernel: prism2_hw_init: initialized in 40 ms Jan 15 11:30:03 localhost kernel: wifi0: NIC: id=0x01 v4.2.1 Jan 15 11:30:03 localhost kernel: wifi0: PRI: id=0x15 v4.4.1 Jan 15 11:30:03 localhost kernel: wifi0: STA: id=0x1f v7.28.1 Jan 15 11:30:03 localhost cardmgr[7737]: socket 1: Lucent Technologies WaveLAN/IEEE Adapter Jan 15 11:30:03 localhost kernel: wifi0: CMD=0x0121 = res=0x7f, resp0=0x0004 Jan 15 11:30:03 localhost kernel: wifi0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc33, len=2) Jan 15 11:30:03 localhost kernel: wifi0: Beacon interval setting to 100 failed Jan 15 11:30:03 localhost kernel: wifi0: CMD=0x0121 = res=0x7f, resp0=0x0004 Jan 15 11:30:03 localhost kernel: wifi0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc10, len=2) I tried that with no luck. I'm beginning to think that I'm in that nasty realm of either the card is NFG or the drivers are buggy. This is one of the best cards I've owned.
Re: PCMCIA configuration
On 15 Jan 2006, Richard Lyons wrote: On Sunday, 15 January 2006 at 10:22:59 -0500, Tom Allison wrote: Grr... I've having problems with my Orinoco gold pcmcia card that used to work. I'll assume some kind of upgrade problem maybe but whatever it is, I'm no longer able to sort it out myself. From the syslog, it appears that the encryption is no longer valid. This is confusing because I haven't changed anything (that I know of) for well over a year. I've checked the access point and it's working and such... help? Between /etc/pcmcia/network.opts /etc/pcmcia/wireless.opts /etc/network/ifconfig I'm not getting anything to work. the card doesn't appear to load at all or only partially. I have a very similar problem with an Orinoco PCMCIA card. There were a number of suggestions here a couple of weeks ago, and on debian-laptop just afterwards, but no solution yet. One thing I haven't yet tried is getting the latest driver. Does your card connect if you temporarily turn off encryption at the access point? Mine does (by manual 'ifup eth0'). If it does we may have the same complaint... -- richard This may not be relevant, but I've had problems with my Cisco Aironet 340 which sound similar. I eventually tracked them to hotplug. If you have upgraded this recently you could try going back to the version in Stable. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration
On Sun, Jan 15, 2006 at 05:08:41PM +, Anthony Campbell wrote: This may not be relevant, but I've had problems with my Cisco Aironet 340 which sound similar. I eventually tracked them to hotplug. If you have upgraded this recently you could try going back to the version in Stable. Ah, yes, I saw something similar recently with an orinoco_cs card. A configuration on my other notebook somehow lent a hint. It seemed that hotplug incorrectly loaded the yenta_socket module when it started up, so the regular pcmcia startup didn't get a chance to do it correctly. I blacklisted yenta_socket from hotplug to allow it to later be initialized properly by pcmcia scripts. [EMAIL PROTECTED]:~$ cat /etc/hotplug/blacklist.d/pcmcia pcmcia_core yenta_socket And reboot. -- John M Flinchbaugh [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: PCMCIA configuration
On 15 Jan 2006, John M Flinchbaugh wrote: On Sun, Jan 15, 2006 at 05:08:41PM +, Anthony Campbell wrote: This may not be relevant, but I've had problems with my Cisco Aironet 340 which sound similar. I eventually tracked them to hotplug. If you have upgraded this recently you could try going back to the version in Stable. Ah, yes, I saw something similar recently with an orinoco_cs card. A configuration on my other notebook somehow lent a hint. It seemed that hotplug incorrectly loaded the yenta_socket module when it started up, so the regular pcmcia startup didn't get a chance to do it correctly. I blacklisted yenta_socket from hotplug to allow it to later be initialized properly by pcmcia scripts. [EMAIL PROTECTED]:~$ cat /etc/hotplug/blacklist.d/pcmcia pcmcia_core yenta_socket And reboot. -- John M Flinchbaugh [EMAIL PROTECTED] Never looked into the configureation of hotplug before. I don't have anything at all in /etc/hotplug/blacklist.d. At present I've simply put hotplug on hold to keep it at the version in Stable and provided I do this everything works. -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA configuration
Anthony Campbell wrote: On 15 Jan 2006, Richard Lyons wrote: On Sunday, 15 January 2006 at 10:22:59 -0500, Tom Allison wrote: Grr... I've having problems with my Orinoco gold pcmcia card that used to work. I'll assume some kind of upgrade problem maybe but whatever it is, I'm no longer able to sort it out myself. From the syslog, it appears that the encryption is no longer valid. This is confusing because I haven't changed anything (that I know of) for well over a year. I've checked the access point and it's working and such... help? Between /etc/pcmcia/network.opts /etc/pcmcia/wireless.opts /etc/network/ifconfig I'm not getting anything to work. the card doesn't appear to load at all or only partially. I have a very similar problem with an Orinoco PCMCIA card. There were a number of suggestions here a couple of weeks ago, and on debian-laptop just afterwards, but no solution yet. One thing I haven't yet tried is getting the latest driver. Does your card connect if you temporarily turn off encryption at the access point? Mine does (by manual 'ifup eth0'). If it does we may have the same complaint... -- richard This may not be relevant, but I've had problems with my Cisco Aironet 340 which sound similar. I eventually tracked them to hotplug. If you have upgraded this recently you could try going back to the version in Stable. Anthony Similarly, I reset my apt_preferences from unstable to testing. purged everything related to pcmcia and wireless. reinstalled pcmcia-cs and wireless tools. Now it works. kernel 2.6.15. I'm thinking there might be a big fat hairy bug when whatever is in unstable gets into testing Unfortunately my installation, until today, was rather spread out between testing and unstable. That's been remedied as I can no longer afford this to be an unstable branch. I need it to work. I would downgrade to stable if I could, but I have a few other packages that I need in testing, so this is as far as I dare go. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PCMCIA configuration troubles
I used pcnetconfig to configure my PCMCIA network Specify the IP address... NN.MM.OO.17 Enter the netmask 255.255.255.0 Enter the network address:NN.MM.OO.0 (default) Enter the broadcast address: NN.MM.OO.255 (default) Enter the gateway address:NN.MM.OO.254 Enter the local domain name: xxx.yy.xx ... 1st 2nd and 3rd nameservers... no nfs mount poins With this configuration I have no route to the gateway... I try different things and found that it works if I added the following in /etc/network/interfaces iface eth0 inet static address NN.MM.OO.17 network NN.MM.OO.0 netmask 255.255.255.0 and make ifup eth0 It is working but I really don't understant why I shoud add this last. Now I can connect to the network, but I would like to have a cleaner installation. Chris. -- Christian Lemer Service de Conformation des Macromolecules Biologiques et de Bioinformatique Universite Libre de Bruxelles Brussels Free University [EMAIL PROTECTED] +32.2.648.52.00http://www.ucmb.ulb.ac.be/~chris
Re: PCMCIA configuration troubles
Christian Lemer wrote: I used pcnetconfig to configure my PCMCIA network Specify the IP address... NN.MM.OO.17 Enter the netmask 255.255.255.0 Enter the network address:NN.MM.OO.0 (default) Enter the broadcast address: NN.MM.OO.255 (default) Enter the gateway address:NN.MM.OO.254 Enter the local domain name: xxx.yy.xx ... 1st 2nd and 3rd nameservers... no nfs mount poins With this configuration I have no route to the gateway... I've done the same thing and obtained the same result ! I've reinstalled Debian 2.2 (yes, I know, but it work so well ;-) and configured the network at that time, and it works. So just like Christian, I'd like to know the clean way to achieve the configuration... Olivier.
