PCMCIA NIC problem
Hi there, I have a Xircom Realport NIC in my notebook which run Debian Woody stable and now unstable. I have to use a dhcp server (dhcp-client 2.0pl5-15) when I am connected in the office and no network connection while I am at home. The problem now is, that while I am at the office and dhcp is working everything is fine and I can shutdown/reboot the machine and it always comes up again with a fresh dhcp connect. Now when I am using the computer at home for a while (without network link) and come back into the office, the network link does not come up again. ifconfig shows the eth0 interface but the ip address is missing. Everything else seems to be ok. Of course there is no routing information because dhcp gives up after a while with the following messages: ... dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 ... dhclient: No DHCPOFFERS received. ... dhclient: No working leases in persistent database. ... dhclient: Sleeping. On the dhcp server I can see that it actually does get a connection assigned but somehow the communication on my clients side looses something. I also tried the dhcp3-client but it didn't make any changes. After I run the notebook without network link something seems to get messed up. To get it back to live, I have to start/stop /etc/init.d/networking, /etc/init.d/pcmcia and /etc/pcmcia/network a couple of times. So far I was not able to find a procedure which always works to get the link working again. Any ideas would be welcome to debug this weird behaviour. :-) TIA, Harry
Different network environments
Hi there, I am looking for a way to manage different network configurations for environments I am working in with my notebook (Woody unstable). Sometimes I have to use DHCP, sometimes its a static IP and so on. I tried to find something using 'apt-cache search' but for all keywords I get so many hits that its somewhat complex. Any suggestions? TIA, Harry
No fsck in battery mode
Hello, is there a way to avoid the regular fsck run (every n mounts or after m days) when the laptop is in battery mode? I think its quite a waste of battery power for the fsck run and rescheduling for the next reboot (with powersupply available) would be very nice. :-) Any idea how to get around the fsck run? TIA for any ideas, Harry
Re: No fsck in battery mode
Hi again, --On Monday, September 01, 2003 10:19:23 AM +0200 Albert Dengg <[EMAIL PROTECTED]> wrote: ... Any idea how to get around the fsck run? ... with `tune2fs -c 0 -i 0 /dev/hdaX` you can disable all automatic checks (except for filesystem errors & not clean unmounted, I think) ...regardless of the powersupply status I hope I could help I know how to turn them off completely but that's not what I really want to do. I do not want to get rid of the checks completely because its quite a good idea to check the FS from time to time. I just would like to have it limited to the times when there is a powersupply available. :-) Harry
PCMCIA NIC problem
Hi there, I have a Xircom Realport NIC in my notebook which run Debian Woody stable and now unstable. I have to use a dhcp server (dhcp-client 2.0pl5-15) when I am connected in the office and no network connection while I am at home. The problem now is, that while I am at the office and dhcp is working everything is fine and I can shutdown/reboot the machine and it always comes up again with a fresh dhcp connect. Now when I am using the computer at home for a while (without network link) and come back into the office, the network link does not come up again. ifconfig shows the eth0 interface but the ip address is missing. Everything else seems to be ok. Of course there is no routing information because dhcp gives up after a while with the following messages: ... dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 ... dhclient: No DHCPOFFERS received. ... dhclient: No working leases in persistent database. ... dhclient: Sleeping. On the dhcp server I can see that it actually does get a connection assigned but somehow the communication on my clients side looses something. I also tried the dhcp3-client but it didn't make any changes. After I run the notebook without network link something seems to get messed up. To get it back to live, I have to start/stop /etc/init.d/networking, /etc/init.d/pcmcia and /etc/pcmcia/network a couple of times. So far I was not able to find a procedure which always works to get the link working again. Any ideas would be welcome to debug this weird behaviour. :-) TIA, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Different network environments
Hi there, I am looking for a way to manage different network configurations for environments I am working in with my notebook (Woody unstable). Sometimes I have to use DHCP, sometimes its a static IP and so on. I tried to find something using 'apt-cache search' but for all keywords I get so many hits that its somewhat complex. Any suggestions? TIA, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No fsck in battery mode
Hello, is there a way to avoid the regular fsck run (every n mounts or after m days) when the laptop is in battery mode? I think its quite a waste of battery power for the fsck run and rescheduling for the next reboot (with powersupply available) would be very nice. :-) Any idea how to get around the fsck run? TIA for any ideas, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No fsck in battery mode
Hi again, --On Monday, September 01, 2003 10:19:23 AM +0200 Albert Dengg <[EMAIL PROTECTED]> wrote: ... Any idea how to get around the fsck run? ... with `tune2fs -c 0 -i 0 /dev/hdaX` you can disable all automatic checks (except for filesystem errors & not clean unmounted, I think) ...regardless of the powersupply status I hope I could help I know how to turn them off completely but that's not what I really want to do. I do not want to get rid of the checks completely because its quite a good idea to check the FS from time to time. I just would like to have it limited to the times when there is a powersupply available. :-) Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network on bootup
Hi there, thanks for the responses so far. Somehow I still had no success with an automatically upcoming eth0. I tried to edit /etc/pcmcia/network.opts but that did not change anything. When I removed 'auto eth0', the network did not come up at all, not even after I restarted the network with /etc/init.d/network. Where exactly does this problem come from? Do other people also face this kind of uncomfortable situation? TIA, Harry --On Friday, February 13, 2004 02:18:03 PM -0500 Bill Marcum <[EMAIL PROTECTED]> wrote: On Fri, Feb 13, 2004 at 01:26:19PM +0100, Bjoern Schmidt wrote: [EMAIL PROTECTED] wrote: > My /etc/network/interfaces looks like this: > -- > auto lo > iface lo inet loopback > > auto eth0 > iface eth0 inet static > address 192.168.1.250 > netmask 255.255.255.0 > broadcast 192.168.1.255 > gateway 192.168.1.1 > -- > > Any ideas out there how to get it boot up properly? sure. edit /etc/pcmcia/network.opts to configure pcmcia-cards. And remove the "auto eth0" line from /etc/network/interfaces. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network on bootup
Hi there, thanks for the responses so far. Somehow I still had no success with an automatically upcoming eth0. I tried to edit /etc/pcmcia/network.opts but that did not change anything. When I removed 'auto eth0', the network did not come up at all, not even after I restarted the network with /etc/init.d/network. Where exactly does this problem come from? Do other people also face this kind of uncomfortable situation? TIA, Harry --On Friday, February 13, 2004 02:18:03 PM -0500 Bill Marcum <[EMAIL PROTECTED]> wrote: On Fri, Feb 13, 2004 at 01:26:19PM +0100, Bjoern Schmidt wrote: [EMAIL PROTECTED] wrote: > My /etc/network/interfaces looks like this: > -- > auto lo > iface lo inet loopback > > auto eth0 > iface eth0 inet static > address 192.168.1.250 > netmask 255.255.255.0 > broadcast 192.168.1.255 > gateway 192.168.1.1 > -- > > Any ideas out there how to get it boot up properly? sure. edit /etc/pcmcia/network.opts to configure pcmcia-cards. And remove the "auto eth0" line from /etc/network/interfaces.
