Re: your mail
On Sun, Sep 09, 2007 at 12:52:59PM -0400, Cavan Mejias wrote: >Setting up bcm43xx-fwcutter (005-2) ... >--12:11:39-- [1]http://boredklink.googlepages.com/wl_apsta.o ... >12:11:54 ERROR 404: Not Found. ... >Is it a temporary problem? Googling doesn't mention it and I can't see that's not google's biz, rather a matter for bugs.debian.org. Seems that links for such wl_apsta.o are a bit volatile. Try with the XP driver that came with the card. -- paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Tue, Jun 06, 2006 at 11:57:08AM -0400, [EMAIL PROTECTED] wrote: > my friend has a Compaq Presario 1255, and we just reloaded it with Windows > 98 2nd Edition. Now he has no sound, and he has tried everything to get it > to work. We figure that there is a driver that is missing. Is there anyway > that you can tell us what driver we need, and where the heck can we get it > from? I searched, and they tell me that the sound card is a Aureal A3D > Interactive 360 Degree Positional Sound. Thanks for the help. If you want somebody that can help you to read your post: 1. put something relevent in the subject line 2. post to a relevent mailing list questions about Windows98 do not belong here... DigbyT -- Digby R. S. Tarvin digbyt(at)digbyt.com http://www.digbyt.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Wireless driver clobbers X (was: Re: your mail)
thanks your e-mail, since after i installed wireless driver, it seemed to me it became unstable ... i start as single user mode ...by the way i'm using testing version, and take out kdm, gdm ... then when i did startx or X, noting show up, XFree86.0.log is following ... thanks, ryoji > Incoming from Ryoji Takahashi: >> after i've got wireless driver for my latitude D600,it became unstable >> ... >> and now >> X is dead ... i've downloaded intel driver ... it works for my laptop >> though. Why >> it affects X environment ? does some has any idea? > > Why do you think it's caused by the wireless driver? Do you have > errors in /var/log/XFree86.0.log that you're not showing us? Also, > please give us enough information about your situation to try to track > it down: stable, testing, unstable? What happens when you try to fire > up X? Is this while using kdm, gdm, or xdm? Have you tried disabling > those and just trying startx? > > > -- > Any technology distinguishable from magic is insufficiently advanced. > (*) http://www.spots.ab.ca/~keeling > - - > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- Ryoji Takahashi LSU Capital, Center for Computation and Technology (CCT) 3rd Floor Frey Computing Services Center Baton Rouge, LA 70803 Office: 225/578-6868 Fax:225/578-5362 E-mail: [EMAIL PROTECTED] XFree86.0.log Description: Binary data
Wireless driver clobbers X (was: Re: your mail)
Incoming from Ryoji Takahashi: > after i've got wireless driver for my latitude D600,it became unstable ... > and now > X is dead ... i've downloaded intel driver ... it works for my laptop > though. Why > it affects X environment ? does some has any idea? Why do you think it's caused by the wireless driver? Do you have errors in /var/log/XFree86.0.log that you're not showing us? Also, please give us enough information about your situation to try to track it down: stable, testing, unstable? What happens when you try to fire up X? Is this while using kdm, gdm, or xdm? Have you tried disabling those and just trying startx? -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - -
Wireless driver clobbers X (was: Re: your mail)
Incoming from Ryoji Takahashi: > after i've got wireless driver for my latitude D600,it became unstable ... > and now > X is dead ... i've downloaded intel driver ... it works for my laptop > though. Why > it affects X environment ? does some has any idea? Why do you think it's caused by the wireless driver? Do you have errors in /var/log/XFree86.0.log that you're not showing us? Also, please give us enough information about your situation to try to track it down: stable, testing, unstable? What happens when you try to fire up X? Is this while using kdm, gdm, or xdm? Have you tried disabling those and just trying startx? -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pcmcia: "bridge register mapping failed :check cb_mem_base setting" (was Re: your mail)
Incoming from Jollivet Christophe: > > I am trying to install the Debian Woody r1 on my Laptop (HP Pavilion N5402l) > The matter is during PCMCIA CardBus bridge configuration. > Before i used RedHat 9 and i worked well. > lspci on the RedHat was giving: > > 02:04.0 CardBus bridge : 02 Micro, Inc 0Z6933 Cardbus Controler (rev 01) > 02:04.1 CardBus bridge : 02 Micro, Inc 0Z6933 Cardbus Controler (rev 01) > > I tried both possibilities during the install and open a second console > where dmesg was giving for module i8365 : > > Linux PCMCIA card Services 3.1.33 > Kernel build 2.4.18:bf2.4 unknow > option [pci] [cardbus] [apm] > Intel ISA/PCI/CardBus PCIC probe > PCI : Found IRQ9 for device 02/04.0 > PCI Sharing IRQ9 with 00:02.0 > PCI Sharing IRQ9 with 00:1d.0 > bridge register mapping failed :check cb_mem_base setting What's in your /etc/pcmcia/config.opts? Are you using kernel pcmcia or pcmcia-cs modules? -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - -
pcmcia: "bridge register mapping failed :check cb_mem_base setting" (was Re: your mail)
Incoming from Jollivet Christophe: > > I am trying to install the Debian Woody r1 on my Laptop (HP Pavilion N5402l) > The matter is during PCMCIA CardBus bridge configuration. > Before i used RedHat 9 and i worked well. > lspci on the RedHat was giving: > > 02:04.0 CardBus bridge : 02 Micro, Inc 0Z6933 Cardbus Controler (rev 01) > 02:04.1 CardBus bridge : 02 Micro, Inc 0Z6933 Cardbus Controler (rev 01) > > I tried both possibilities during the install and open a second console > where dmesg was giving for module i8365 : > > Linux PCMCIA card Services 3.1.33 > Kernel build 2.4.18:bf2.4 unknow > option [pci] [cardbus] [apm] > Intel ISA/PCI/CardBus PCIC probe > PCI : Found IRQ9 for device 02/04.0 > PCI Sharing IRQ9 with 00:02.0 > PCI Sharing IRQ9 with 00:1d.0 > bridge register mapping failed :check cb_mem_base setting What's in your /etc/pcmcia/config.opts? Are you using kernel pcmcia or pcmcia-cs modules? -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Thu, 1 Jan 2004, Rafal wrote: > I need drivers to inspiron1100 controler ethernet controler vidio controler > audio Sure. I need some cash, a new car, a big house on a small island and my private learjet. What the hell did you smoke to post such an §&%/§$&%/= email? http://rtfm.bsdzine.org/ Marcel.
Re: your mail
On Thu, 1 Jan 2004, Rafal wrote: > I need drivers to inspiron1100 controler ethernet controler vidio controler audio Sure. I need some cash, a new car, a big house on a small island and my private learjet. What the hell did you smoke to post such an §&%/§$&%/= email? http://rtfm.bsdzine.org/ Marcel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Fri, Dec 26, 2003 at 04:54:58PM -, alan clark wrote: > Hi, > > Just like to know where I can locate a copy of a manual for a Toshiba T4500 > laptop? Dude, At least give it a try, 3 minutes walltime from www.toshiba.com will bring you here: http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=106706&moid=1073769823&BV_SessionID=1486651951.1072464018&BV_EngineID=adckfhelmfhcgfkceghdgngdgli.0&ct=DL (Generally, manufacturers have a "support" section that contains a "download" section which hold all the manuals for their products). /Y
Re: your mail
On Fri, Dec 26, 2003 at 04:54:58PM -, alan clark wrote: > Hi, > > Just like to know where I can locate a copy of a manual for a Toshiba T4500 laptop? Dude, At least give it a try, 3 minutes walltime from www.toshiba.com will bring you here: http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=106706&moid=1073769823&BV_SessionID=1486651951.1072464018&BV_EngineID=adckfhelmfhcgfkceghdgngdgli.0&ct=DL (Generally, manufacturers have a "support" section that contains a "download" section which hold all the manuals for their products). /Y -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Am 2003-11-19 20:22:37, schrieb Carlos Augusto Martins de Carvalho: > >driver da placa pcmcia zonet ZEN1200 10/100 NotBook para windows 98se >Aguardo retorno >grato >Tulio Marques You are using the false Operating System It is time to change your live Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Am 2003-11-19 20:22:37, schrieb Carlos Augusto Martins de Carvalho: > >driver da placa pcmcia zonet ZEN1200 10/100 NotBook para windows 98se >Aguardo retorno >grato >Tulio Marques You are using the false Operating System It is time to change your live Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org.
Re: your mail
Quoting jamal khan ([EMAIL PROTECTED]): > i want driver for crystal sound fusion (tm) cs-4281 >thankyou I believe that this card is supported by alsa's cirrus logic module. You should be able to apt-get install alsa, and build it from source. Assuming, (of course), that it was a linux driver you were after :) -- Matt Foster [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mattfoster.clara.co.uk icq: 106411042 signature.asc Description: Digital signature
Re: your mail
Quoting jamal khan ([EMAIL PROTECTED]): > i want driver for crystal sound fusion (tm) cs-4281 >thankyou I believe that this card is supported by alsa's cirrus logic module. You should be able to apt-get install alsa, and build it from source. Assuming, (of course), that it was a linux driver you were after :) -- Matt Foster [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mattfoster.clara.co.uk icq: 106411042 signature.asc Description: Digital signature
Re: your mail
On 19 Mar 2003 21:04:33 -0600 Shyamal Prasad <[EMAIL PROTECTED]> wrote: > Most likely you have an 'auto' line in /etc/network/interfaces for > your pcmcia card. Take that out and it should work fine. Basically, if > you don't have the auto line the network script in /etc/init.d/ will > ignore the interface, and the pcmcia startup scripts there will > correctly bring the card up later. Does this work if one PCMCIA card is wired (and has a static address) but another is wireless (and gets a dynamic address)? I sometimes use one, and sometimes the other but not both at the same time. Kevin
Re: your mail
On 19 Mar 2003 21:04:33 -0600 Shyamal Prasad <[EMAIL PROTECTED]> wrote: > Most likely you have an 'auto' line in /etc/network/interfaces for > your pcmcia card. Take that out and it should work fine. Basically, if > you don't have the auto line the network script in /etc/init.d/ will > ignore the interface, and the pcmcia startup scripts there will > correctly bring the card up later. Does this work if one PCMCIA card is wired (and has a static address) but another is wireless (and gets a dynamic address)? I sometimes use one, and sometimes the other but not both at the same time. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Sorry about this one. Written last night but the problem was solved by the time my mail system actually let go of it... -- Derek - Original Message - From: "Derek Broughton" <[EMAIL PROTECTED]> To: "debian-laptop" Sent: Friday, March 21, 2003 9:55 AM Subject: Re: your mail > Mike Beattie wrote: > > On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: > > > >>I've reinstalled pcmcia-cs just to make sure that I _do_ have a default > >>network.opts (attached). > > > > It's not. you need to purge it, then install it. > > Doh...Still, the difference isn't the problem since we see ifup not > working... > > > > ... > > > >>Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 > >>Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 already configured > > > > > > Get rid of hotplug, it's getting there 'first'. > > If it is, then its a problem - since I need hotplug for the USB. I'll > pull it tomorrow and see, but I really don't think this is the problem - > if they really are both running ifup, then either one working is good > enough. This is presumably why the sid version of pcmcia-cs specifically > skips doing ifup/ifdown if it finds the hotplug program. I suppose that > both trying to run at once might make _neither_ work. > > Anyway, thanks for the help and I'll see what happens tomorrow when I > have a network card. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > >
Re: your mail
Sorry about this one. Written last night but the problem was solved by the time my mail system actually let go of it... -- Derek - Original Message - From: "Derek Broughton" <[EMAIL PROTECTED]> To: "debian-laptop" <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 9:55 AM Subject: Re: your mail > Mike Beattie wrote: > > On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: > > > >>I've reinstalled pcmcia-cs just to make sure that I _do_ have a default > >>network.opts (attached). > > > > It's not. you need to purge it, then install it. > > Doh...Still, the difference isn't the problem since we see ifup not > working... > > > > ... > > > >>Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 > >>Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 already configured > > > > > > Get rid of hotplug, it's getting there 'first'. > > If it is, then its a problem - since I need hotplug for the USB. I'll > pull it tomorrow and see, but I really don't think this is the problem - > if they really are both running ifup, then either one working is good > enough. This is presumably why the sid version of pcmcia-cs specifically > skips doing ifup/ifdown if it finds the hotplug program. I suppose that > both trying to run at once might make _neither_ work. > > Anyway, thanks for the help and I'll see what happens tomorrow when I > have a network card. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Mike Beattie wrote: On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: I've reinstalled pcmcia-cs just to make sure that I _do_ have a default network.opts (attached). It's not. you need to purge it, then install it. Doh... Unfortunately doing a _real_ reinstall buggers up /etc/default/pcmcia (reset PCIC="i82365", which is wrong). Still, the difference between my network.opts and the proper one isn't the problem since we see ifup not working... Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 already configured Get rid of hotplug, it's getting there 'first'. Yeah, that's it. It's a problem - since I need hotplug for the USB, but I need it much less than I need pcmcia. This is presumably why the sid version of pcmcia-cs specifically skips doing ifup/ifdown if it finds the hotplug program. I'm not sure why the ifup from hotplug wasn't doing the job successfully, but it's working now. I'll wait until the next versions of pcmcia-cs & hotplug get out of sid before trying them together again. Thanks all for the help... derek
Re: your mail
Mike Beattie wrote: On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: I've reinstalled pcmcia-cs just to make sure that I _do_ have a default network.opts (attached). It's not. you need to purge it, then install it. Doh...Still, the difference isn't the problem since we see ifup not working... ... Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 already configured Get rid of hotplug, it's getting there 'first'. If it is, then its a problem - since I need hotplug for the USB. I'll pull it tomorrow and see, but I really don't think this is the problem - if they really are both running ifup, then either one working is good enough. This is presumably why the sid version of pcmcia-cs specifically skips doing ifup/ifdown if it finds the hotplug program. I suppose that both trying to run at once might make _neither_ work. Anyway, thanks for the help and I'll see what happens tomorrow when I have a network card.
Re: your mail
Mike Beattie wrote: On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: I've reinstalled pcmcia-cs just to make sure that I _do_ have a default network.opts (attached). It's not. you need to purge it, then install it. Doh... Unfortunately doing a _real_ reinstall buggers up /etc/default/pcmcia (reset PCIC="i82365", which is wrong). Still, the difference between my network.opts and the proper one isn't the problem since we see ifup not working... Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 already configured Get rid of hotplug, it's getting there 'first'. Yeah, that's it. It's a problem - since I need hotplug for the USB, but I need it much less than I need pcmcia. This is presumably why the sid version of pcmcia-cs specifically skips doing ifup/ifdown if it finds the hotplug program. I'm not sure why the ifup from hotplug wasn't doing the job successfully, but it's working now. I'll wait until the next versions of pcmcia-cs & hotplug get out of sid before trying them together again. Thanks all for the help... derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Mike Beattie wrote: On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: I've reinstalled pcmcia-cs just to make sure that I _do_ have a default network.opts (attached). It's not. you need to purge it, then install it. Doh...Still, the difference isn't the problem since we see ifup not working... ... Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 already configured Get rid of hotplug, it's getting there 'first'. If it is, then its a problem - since I need hotplug for the USB. I'll pull it tomorrow and see, but I really don't think this is the problem - if they really are both running ifup, then either one working is good enough. This is presumably why the sid version of pcmcia-cs specifically skips doing ifup/ifdown if it finds the hotplug program. I suppose that both trying to run at once might make _neither_ work. Anyway, thanks for the help and I'll see what happens tomorrow when I have a network card. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Fri, 21 Mar 2003 14:36:23 +1200 Mike Beattie <[EMAIL PROTECTED]> wrote: > man 5 interfaces > > (for the ifscheme script, see http://bugs.debian.org/15) > > And it Just Works(tm), So, you can see that there is no difference > between using interfaces(5) for a builtin card, or a pcmcia card. The > point is, that network.opts does the magic of calling ifup or ifdown > for you, if you leave the configuration alone. Thanks, Mike. I'll check that out. I've been playing musical network.opts. Kevin
Re: your mail
On Thu, Mar 20, 2003 at 08:56:44PM -0500, [EMAIL PROTECTED] wrote: > Where can I read about The Debian Way of letting /e/n/interfaces handle > pcmcia? man 5 interfaces e.g: My wireless card is eth1: (builtin ethernet is eth0) /etc/network/interfaces has: ... mapping eth1 script /etc/network/ifscheme # Home iface eth1-home inet dhcp wireless_nick toolbox wireless_mode managed wireless_essid blah wireless_key 's:12345' # Others... ... etc. (for the ifscheme script, see http://bugs.debian.org/15) And it Just Works(tm), So, you can see that there is no difference between using interfaces(5) for a builtin card, or a pcmcia card. The point is, that network.opts does the magic of calling ifup or ifdown for you, if you leave the configuration alone. Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 "This isnt Mission Difficult Mr Hunt, this is Mission Impossible. Difficult should be a walk in the park for you." -- MI:2
Re: your mail
On Fri, 21 Mar 2003 11:48:25 +1200 Mike Beattie <[EMAIL PROTECTED]> wrote: > It seems backwards, I know. but if you leave that file alone, and use > interfaces(5), it'll work. Where can I read about The Debian Way of letting /e/n/interfaces handle pcmcia? Kevin
Re: your mail
On Fri, 21 Mar 2003 14:36:23 +1200 Mike Beattie <[EMAIL PROTECTED]> wrote: > man 5 interfaces > > (for the ifscheme script, see http://bugs.debian.org/15) > > And it Just Works(tm), So, you can see that there is no difference > between using interfaces(5) for a builtin card, or a pcmcia card. The > point is, that network.opts does the magic of calling ifup or ifdown > for you, if you leave the configuration alone. Thanks, Mike. I'll check that out. I've been playing musical network.opts. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Thu, Mar 20, 2003 at 08:56:44PM -0500, [EMAIL PROTECTED] wrote: > Where can I read about The Debian Way of letting /e/n/interfaces handle > pcmcia? man 5 interfaces e.g: My wireless card is eth1: (builtin ethernet is eth0) /etc/network/interfaces has: ... mapping eth1 script /etc/network/ifscheme # Home iface eth1-home inet dhcp wireless_nick toolbox wireless_mode managed wireless_essid blah wireless_key 's:12345' # Others... ... etc. (for the ifscheme script, see http://bugs.debian.org/15) And it Just Works(tm), So, you can see that there is no difference between using interfaces(5) for a builtin card, or a pcmcia card. The point is, that network.opts does the magic of calling ifup or ifdown for you, if you leave the configuration alone. Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 "This isnt Mission Difficult Mr Hunt, this is Mission Impossible. Difficult should be a walk in the park for you." -- MI:2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: > Well, no I didn't, but a private email led me to understand the error of > my ways. It still seems odd that I need to leave network.opts saying > DHCP="n" if I want to get ifup to use dhcp. But I do understand that > that's correct. Of course, it still didn't work... > > I've reinstalled pcmcia-cs just to make sure that I _do_ have a default > network.opts (attached). It's not. you need to purge it, then install it. The stanza in network.opts doesnt apply, because it's not using dhcp/bootp/whatever, and has no IP assigned. that's what the list of it_true's at the bottom is for. In my default config, they're uncommented. It seems backwards, I know. but if you leave that file alone, and use interfaces(5), it'll work. > But whatever's happening, I'm seeing 'ifdown' execute (correctly - it > runs the firewall's stop script) but 'ifup' doesn't: > > cardmgr[308]: + /sbin/ifup: interface eth0 already configured > > At least I can see that it's _trying_ to run ifup. ... > Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 > Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface > eth0 already configured Get rid of hotplug, it's getting there 'first'. Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 Contentsofsignaturemaysettleduringshipping.
Re: your mail
On Fri, 21 Mar 2003 11:48:25 +1200 Mike Beattie <[EMAIL PROTECTED]> wrote: > It seems backwards, I know. but if you leave that file alone, and use > interfaces(5), it'll work. Where can I read about The Debian Way of letting /e/n/interfaces handle pcmcia? Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Thu, Mar 20, 2003 at 09:21:11AM -0400, Derek Broughton wrote: > Well, no I didn't, but a private email led me to understand the error of > my ways. It still seems odd that I need to leave network.opts saying > DHCP="n" if I want to get ifup to use dhcp. But I do understand that > that's correct. Of course, it still didn't work... > > I've reinstalled pcmcia-cs just to make sure that I _do_ have a default > network.opts (attached). It's not. you need to purge it, then install it. The stanza in network.opts doesnt apply, because it's not using dhcp/bootp/whatever, and has no IP assigned. that's what the list of it_true's at the bottom is for. In my default config, they're uncommented. It seems backwards, I know. but if you leave that file alone, and use interfaces(5), it'll work. > But whatever's happening, I'm seeing 'ifdown' execute (correctly - it > runs the firewall's stop script) but 'ifup' doesn't: > > cardmgr[308]: + /sbin/ifup: interface eth0 already configured > > At least I can see that it's _trying_ to run ifup. ... > Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifup eth0 > Mar 20 09:07:10 casio.othello.dyn.ca cardmgr[308]: + /sbin/ifup: interface eth0 > already configured Get rid of hotplug, it's getting there 'first'. Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 Contentsofsignaturemaysettleduringshipping. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
From: "Mike Beattie" <[EMAIL PROTECTED]>
It seems I'd picked up a version of pcmcia-cs from sid in one of my
experiments, but even having downgraded this to 3.1.33-6 it does
_not_ seem to invoke ifup/ifdown (all that seems different is the
use of hotplug in sid). I _did_ reset DHCP="y" when I recreated the
network.opts file.
Of cource, you do realise that when using /e/n/interfaces with
pcmcia, you dont want to change the default network.opts at all,
right?
Well, no I didn't, but a private email led me to understand the error of
my ways. It still seems odd that I need to leave network.opts saying
DHCP="n" if I want to get ifup to use dhcp. But I do understand that
that's correct. Of course, it still didn't work...
I checked /etc/network/interfaces and I don't have "auto" specified for
eth0.
I've reinstalled pcmcia-cs just to make sure that I _do_ have a default
network.opts (attached). Now the only thing that comes to mind is
hotplug, which was installed for USB but is now getting invoked for
PCMCIA cards, too.
But whatever's happening, I'm seeing 'ifdown' execute (correctly - it
runs the firewall's stop script) but 'ifup' doesn't:
cardmgr[308]: + /sbin/ifup: interface eth0 already configured
At least I can see that it's _trying_ to run ifup.
My configs are attached, along with the relevant part of syslog (minus
too verbose output from dhclient showing that it did get an IP).
### etherconf DEBCONF AREA. DO NOT EDIT THIS AREA OR INSERT TEXT BEFORE IT.
auto lo
iface lo inet loopback
iface eth0 inet dhcp
hostname casio
### END OF DEBCONF AREA. PLACE YOUR EDITS BELOW; THEY WILL BE PRESERVED.
up /etc/init.d/firestarter start
post-down /etc/init.d/firestarter stop
# Network adapter configuration
#
# The address format is "scheme,socket,instance,hwaddr".
#
# Note: the "network address" here is NOT the same as the IP address.
# See the Networking HOWTO. In short, the network address is the IP
# address masked by the netmask.
#
case "$ADDRESS" in
*,*,*,*)
INFO="Sample private network setup"
# Transceiver selection, for some cards -- see 'man ifport'
IF_PORT=""
# Use BOOTP (via /sbin/bootpc, or /sbin/pump)? [y/n]
BOOTP="n"
# Use DHCP (via /sbin/dhcpcd, /sbin/dhclient, or /sbin/pump)? [y/n]
DHCP="n"
# If you need to explicitly specify a hostname for DHCP requests
DHCP_HOSTNAME=""
# Use PPP over Ethernet (via the pppoe package)? [y/n]
PPPOE="n"
# Use WHEREAMI (via the whereami package)? [y/n]
WHEREAMI="n"
# Host's IP address, netmask, network address, broadcast address
IPADDR=""
NETMASK="255.255.255.0"
NETWORK="10.0.1.0"
BROADCAST="10.0.1.255"
# Gateway address for static routing
GATEWAY="10.0.1.1"
# Things to add to /etc/resolv.conf for this interface
DOMAIN=""
SEARCH=""
# The nameserver IP addresses specified here complement the
# nameservers already defined in /etc/resolv.conf. These nameservers
# will be added to /etc/resolv.conf automatically when the PCMCIA
# network connection is established and removed from this file when
# the connection is broken.
DNS_1=""
DNS_2=""
DNS_3=""
# NFS mounts, should be listed in /etc/fstab
MOUNTS=""
# If you need to override the interface's MTU...
MTU=""
# For IPX interfaces, the frame type and network number
IPX_FRAME=""
IPX_NETNUM=""
# Run ipmasq? [y/n] (see the Debian ipmasq package)
IPMASQ="n"
# Extra stuff to do after setting up the interface
start_fn () { return; }
# Extra stuff to do before shutting down the interface
stop_fn () { return; }
# Card eject policy options
NO_CHECK=n
NO_FUSER=n
;;
esac
# This tries to use Debian's network setup in /etc/network/interfaces
# if no settings are given higher up in this file. You can delete it
# if that isn't desired.
#is_true $PUMP || is_true $BOOTP || is_true $DHCP || is_true $DHCLIENT || \
#if [ ! "$IPADDR" -a -f /etc/network/interfaces ] ; then
INFO="Debian network setup"
start_fn () {
log /sbin/ifup $1
}
stop_fn () {
log /sbin/ifdown $1
}
#fi
Mar 20 09:06:42 casio.othello.dyn.ca cardmgr[308]: executing: './network stop
eth0'
Mar 20 09:06:44 casio.othello.dyn.ca cardmgr[308]: + Stopping firestarter
firewall: firestarter.
Mar 20 09:06:44 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe -r
pcnet_cs'
Mar 20 09:06:44 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe -r 8390'
Mar 20 09:06:44 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifdown eth0
Mar 20 09:07:00 casio.othello.dyn.ca cardmgr[308]: socket 0: NetGear FA411 Fast
Ethernet
Mar 20 09:07:00 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe 8390'
Mar 20 09:07:01 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe
pcnet_cs'
Mar 20 09:07:01 casio.othello.dyn.ca cardmgr[308]: executing: './network start
eth0'
Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/
Re: your mail
From: "Mike Beattie" <[EMAIL PROTECTED]>
It seems I'd picked up a version of pcmcia-cs from sid in one of my
experiments, but even having downgraded this to 3.1.33-6 it does
_not_ seem to invoke ifup/ifdown (all that seems different is the
use of hotplug in sid). I _did_ reset DHCP="y" when I recreated the
network.opts file.
Of cource, you do realise that when using /e/n/interfaces with
pcmcia, you dont want to change the default network.opts at all,
right?
Well, no I didn't, but a private email led me to understand the error of
my ways. It still seems odd that I need to leave network.opts saying
DHCP="n" if I want to get ifup to use dhcp. But I do understand that
that's correct. Of course, it still didn't work...
I checked /etc/network/interfaces and I don't have "auto" specified for
eth0.
I've reinstalled pcmcia-cs just to make sure that I _do_ have a default
network.opts (attached). Now the only thing that comes to mind is
hotplug, which was installed for USB but is now getting invoked for
PCMCIA cards, too.
But whatever's happening, I'm seeing 'ifdown' execute (correctly - it
runs the firewall's stop script) but 'ifup' doesn't:
cardmgr[308]: + /sbin/ifup: interface eth0 already configured
At least I can see that it's _trying_ to run ifup.
My configs are attached, along with the relevant part of syslog (minus
too verbose output from dhclient showing that it did get an IP).
### etherconf DEBCONF AREA. DO NOT EDIT THIS AREA OR INSERT TEXT BEFORE IT.
auto lo
iface lo inet loopback
iface eth0 inet dhcp
hostname casio
### END OF DEBCONF AREA. PLACE YOUR EDITS BELOW; THEY WILL BE PRESERVED.
up /etc/init.d/firestarter start
post-down /etc/init.d/firestarter stop
# Network adapter configuration
#
# The address format is "scheme,socket,instance,hwaddr".
#
# Note: the "network address" here is NOT the same as the IP address.
# See the Networking HOWTO. In short, the network address is the IP
# address masked by the netmask.
#
case "$ADDRESS" in
*,*,*,*)
INFO="Sample private network setup"
# Transceiver selection, for some cards -- see 'man ifport'
IF_PORT=""
# Use BOOTP (via /sbin/bootpc, or /sbin/pump)? [y/n]
BOOTP="n"
# Use DHCP (via /sbin/dhcpcd, /sbin/dhclient, or /sbin/pump)? [y/n]
DHCP="n"
# If you need to explicitly specify a hostname for DHCP requests
DHCP_HOSTNAME=""
# Use PPP over Ethernet (via the pppoe package)? [y/n]
PPPOE="n"
# Use WHEREAMI (via the whereami package)? [y/n]
WHEREAMI="n"
# Host's IP address, netmask, network address, broadcast address
IPADDR=""
NETMASK="255.255.255.0"
NETWORK="10.0.1.0"
BROADCAST="10.0.1.255"
# Gateway address for static routing
GATEWAY="10.0.1.1"
# Things to add to /etc/resolv.conf for this interface
DOMAIN=""
SEARCH=""
# The nameserver IP addresses specified here complement the
# nameservers already defined in /etc/resolv.conf. These nameservers
# will be added to /etc/resolv.conf automatically when the PCMCIA
# network connection is established and removed from this file when
# the connection is broken.
DNS_1=""
DNS_2=""
DNS_3=""
# NFS mounts, should be listed in /etc/fstab
MOUNTS=""
# If you need to override the interface's MTU...
MTU=""
# For IPX interfaces, the frame type and network number
IPX_FRAME=""
IPX_NETNUM=""
# Run ipmasq? [y/n] (see the Debian ipmasq package)
IPMASQ="n"
# Extra stuff to do after setting up the interface
start_fn () { return; }
# Extra stuff to do before shutting down the interface
stop_fn () { return; }
# Card eject policy options
NO_CHECK=n
NO_FUSER=n
;;
esac
# This tries to use Debian's network setup in /etc/network/interfaces
# if no settings are given higher up in this file. You can delete it
# if that isn't desired.
#is_true $PUMP || is_true $BOOTP || is_true $DHCP || is_true $DHCLIENT || \
#if [ ! "$IPADDR" -a -f /etc/network/interfaces ] ; then
INFO="Debian network setup"
start_fn () {
log /sbin/ifup $1
}
stop_fn () {
log /sbin/ifdown $1
}
#fi
Mar 20 09:06:42 casio.othello.dyn.ca cardmgr[308]: executing: './network stop eth0'
Mar 20 09:06:44 casio.othello.dyn.ca cardmgr[308]: + Stopping firestarter firewall:
firestarter.
Mar 20 09:06:44 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe -r pcnet_cs'
Mar 20 09:06:44 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe -r 8390'
Mar 20 09:06:44 casio.othello.dyn.ca /etc/hotplug/net.agent: invoke ifdown eth0
Mar 20 09:07:00 casio.othello.dyn.ca cardmgr[308]: socket 0: NetGear FA411 Fast
Ethernet
Mar 20 09:07:00 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe 8390'
Mar 20 09:07:01 casio.othello.dyn.ca cardmgr[308]: executing: 'modprobe pcnet_cs'
Mar 20 09:07:01 casio.othello.dyn.ca cardmgr[308]: executing: './network start eth0'
Mar 20 09:07:01 casio.othello.dyn.ca /etc/hotplug/net.agent: invo
Re: your mail
"Derek" == Derek Broughton <[EMAIL PROTECTED]> writes: Derek> As near as I can tell, when you put stuff in Derek> /etc/network/interfaces, it gets executed at init time, Derek> before pcmcia gets started. If your card is already Derek> inserted, then when pcmcia _does_ start, ifup doesn't get Derek> executed. Perhaps I'm misconfigured, but this is what's Derek> happening to me. Most likely you have an 'auto' line in /etc/network/interfaces for your pcmcia card. Take that out and it should work fine. Basically, if you don't have the auto line the network script in /etc/init.d/ will ignore the interface, and the pcmcia startup scripts there will correctly bring the card up later. IMHO, this is the "correct" way to do it. It also works fine (I've done it like this for a while and, to be honest, since moving to Debian I've actually forgotten how to muck with network.opts and all those other pcmcia-cs files). Cheers! Shyamal
Re: your mail
"Derek" == Derek Broughton <[EMAIL PROTECTED]> writes: Derek> As near as I can tell, when you put stuff in Derek> /etc/network/interfaces, it gets executed at init time, Derek> before pcmcia gets started. If your card is already Derek> inserted, then when pcmcia _does_ start, ifup doesn't get Derek> executed. Perhaps I'm misconfigured, but this is what's Derek> happening to me. Most likely you have an 'auto' line in /etc/network/interfaces for your pcmcia card. Take that out and it should work fine. Basically, if you don't have the auto line the network script in /etc/init.d/ will ignore the interface, and the pcmcia startup scripts there will correctly bring the card up later. IMHO, this is the "correct" way to do it. It also works fine (I've done it like this for a while and, to be honest, since moving to Debian I've actually forgotten how to muck with network.opts and all those other pcmcia-cs files). Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
> > 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit > > circular, when > > /etc/pcmcia/network.opts does "/sbin/ifup"? There's a thread from Jan 7 2003 Re: PCMCIA NIC & internal NIC Allow me to quote Shyamal: "PCMCIA cards are brought up by the PCMCIA subsystems, the other network cards are brought up by the network scripts (which run earlier). So, if you are setting up the PCMCIA card via /etc/network/interfaces do not use the 'auto' keyword for eth1. That should take care of it unless you did something else to the standard installation." -- micha.
Re: your mail
On Wed, Mar 19, 2003 at 01:47:55PM -0400, Derek Broughton wrote: > OK, that obviously wasn't necessary - I probably did it myself long ago. I've > used etherconf to reconfigure my network without any damage - but without > fixing > things. No, because ifupdown is not what controls the pcmcia sockets. you want to let cardmgr do the work, including calling ifup for configuration of the interface. > I changed that and things have changed, but they're still not right. > > If I do "ifdown eth0", the firewall is torn down. If I do "ifup eth0" the > firewall is rebuilt. This is good. But if I remove/replace the pcmcia card, > ifup/ifdown don't appear to be run. The script as I have it (taken from a > reinstall, so not my fault :-) ) contains: ... > It seems I'd picked up a version of pcmcia-cs from sid in one of my > experiments, > but even having downgraded this to 3.1.33-6 it does _not_ seem to invoke > ifup/ifdown (all that seems different is the use of hotplug in sid). I _did_ > reset DHCP="y" when I recreated the network.opts file. Of cource, you do realise that when using /e/n/interfaces with pcmcia, you dont want to change the default network.opts at all, right? Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 "Sometimes I think that the surest sign that intellegent life exists elsewhere in the universe is that none of it has tried to contact us."
Re: your mail
> > 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit > > circular, when > > /etc/pcmcia/network.opts does "/sbin/ifup"? There's a thread from Jan 7 2003 Re: PCMCIA NIC & internal NIC Allow me to quote Shyamal: "PCMCIA cards are brought up by the PCMCIA subsystems, the other network cards are brought up by the network scripts (which run earlier). So, if you are setting up the PCMCIA card via /etc/network/interfaces do not use the 'auto' keyword for eth1. That should take care of it unless you did something else to the standard installation." -- micha. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Wed, Mar 19, 2003 at 01:47:55PM -0400, Derek Broughton wrote: > OK, that obviously wasn't necessary - I probably did it myself long ago. I've > used etherconf to reconfigure my network without any damage - but without fixing > things. No, because ifupdown is not what controls the pcmcia sockets. you want to let cardmgr do the work, including calling ifup for configuration of the interface. > I changed that and things have changed, but they're still not right. > > If I do "ifdown eth0", the firewall is torn down. If I do "ifup eth0" the > firewall is rebuilt. This is good. But if I remove/replace the pcmcia card, > ifup/ifdown don't appear to be run. The script as I have it (taken from a > reinstall, so not my fault :-) ) contains: ... > It seems I'd picked up a version of pcmcia-cs from sid in one of my experiments, > but even having downgraded this to 3.1.33-6 it does _not_ seem to invoke > ifup/ifdown (all that seems different is the use of hotplug in sid). I _did_ > reset DHCP="y" when I recreated the network.opts file. Of cource, you do realise that when using /e/n/interfaces with pcmcia, you dont want to change the default network.opts at all, right? Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 "Sometimes I think that the surest sign that intellegent life exists elsewhere in the universe is that none of it has tried to contact us." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
From: "Derek Broughton" <[EMAIL PROTECTED]>
> As near as I can tell, when you put stuff in /etc/network/interfaces, it gets
> executed at init time, before pcmcia gets started. If your card is already
> inserted, then when pcmcia _does_ start, ifup doesn't get executed. Perhaps
I'm
> misconfigured, but this is what's happening to me. I try to start firewall
> rules in /etc/network/interfaces and they don't start at power-up, but they
_do_
> start if I remove and reinsert the card. Now, looking at the file I see two
> potential problems:
>
> 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit circular,
when
> /etc/pcmcia/network.opts does "/sbin/ifup"?
OK, that obviously wasn't necessary - I probably did it myself long ago. I've
used etherconf to reconfigure my network without any damage - but without fixing
things.
> 2) the firewall script runs in a "pre-up" as well. It seemed like a good idea
> at the time, because I was thinking I wanted the firewall up before the link
was
> really active - but now that I think of it, I'm not sure dhclient will have
run
> before the firewall script starts - so I'll have to rtfm and check that. If
I'm
> right on this, it would explain why resetting the card will work, because dhcp
> always gets the same IP here, anyway.
I changed that and things have changed, but they're still not right.
If I do "ifdown eth0", the firewall is torn down. If I do "ifup eth0" the
firewall is rebuilt. This is good. But if I remove/replace the pcmcia card,
ifup/ifdown don't appear to be run. The script as I have it (taken from a
reinstall, so not my fault :-) ) contains:
is_true $DHCLIENT || \
is_true $PUMP || is_true $BOOTP || is_true $DHCP || \
if [ -z "$IPADDR" -a -f /etc/network/interfaces ] ; then
INFO="Debian network setup"
start_fn () {
log /sbin/ifup $1
}
stop_fn () {
log /sbin/ifdown $1
}
fi
It seems I'd picked up a version of pcmcia-cs from sid in one of my experiments,
but even having downgraded this to 3.1.33-6 it does _not_ seem to invoke
ifup/ifdown (all that seems different is the use of hotplug in sid). I _did_
reset DHCP="y" when I recreated the network.opts file.
Re: your mail
From: "Derek Broughton" <[EMAIL PROTECTED]>
> As near as I can tell, when you put stuff in /etc/network/interfaces, it gets
> executed at init time, before pcmcia gets started. If your card is already
> inserted, then when pcmcia _does_ start, ifup doesn't get executed. Perhaps
I'm
> misconfigured, but this is what's happening to me. I try to start firewall
> rules in /etc/network/interfaces and they don't start at power-up, but they
_do_
> start if I remove and reinsert the card. Now, looking at the file I see two
> potential problems:
>
> 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit circular,
when
> /etc/pcmcia/network.opts does "/sbin/ifup"?
OK, that obviously wasn't necessary - I probably did it myself long ago. I've
used etherconf to reconfigure my network without any damage - but without fixing
things.
> 2) the firewall script runs in a "pre-up" as well. It seemed like a good idea
> at the time, because I was thinking I wanted the firewall up before the link
was
> really active - but now that I think of it, I'm not sure dhclient will have
run
> before the firewall script starts - so I'll have to rtfm and check that. If
I'm
> right on this, it would explain why resetting the card will work, because dhcp
> always gets the same IP here, anyway.
I changed that and things are still not right.
If I do "ifdown eth0", the firewall is torn down. If I do "ifup eth0" the
firewall is rebuilt. This is good. But if I remove/replace the pcmcia card,
ifup/ifdown don't appear to be run. The script as I have it (taken from a
reinstall, so not my fault :-) ) contains:
is_true $DHCLIENT || \
is_true $PUMP || is_true $BOOTP || is_true $DHCP || \
if [ -z "$IPADDR" -a -f /etc/network/interfaces ] ; then
INFO="Debian network setup"
start_fn () {
log /sbin/ifup $1
}
stop_fn () {
log /sbin/ifdown $1
}
fi
It seems I'd picked up a version of pcmcia-cs from sid in one of my experiments,
but even having downgraded this to 3.1.33-6 it does _not_ seem to invoke
ifup/ifdown (all that seems different is the use of hotplug in sid). I _did_
reset DHCP="y" when I recreated the network.opts file.
Re: your mail
From: "Derek Broughton" <[EMAIL PROTECTED]>
> As near as I can tell, when you put stuff in /etc/network/interfaces, it gets
> executed at init time, before pcmcia gets started. If your card is already
> inserted, then when pcmcia _does_ start, ifup doesn't get executed. Perhaps
I'm
> misconfigured, but this is what's happening to me. I try to start firewall
> rules in /etc/network/interfaces and they don't start at power-up, but they
_do_
> start if I remove and reinsert the card. Now, looking at the file I see two
> potential problems:
>
> 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit circular,
when
> /etc/pcmcia/network.opts does "/sbin/ifup"?
OK, that obviously wasn't necessary - I probably did it myself long ago. I've
used etherconf to reconfigure my network without any damage - but without fixing
things.
> 2) the firewall script runs in a "pre-up" as well. It seemed like a good idea
> at the time, because I was thinking I wanted the firewall up before the link
was
> really active - but now that I think of it, I'm not sure dhclient will have
run
> before the firewall script starts - so I'll have to rtfm and check that. If
I'm
> right on this, it would explain why resetting the card will work, because dhcp
> always gets the same IP here, anyway.
I changed that and things have changed, but they're still not right.
If I do "ifdown eth0", the firewall is torn down. If I do "ifup eth0" the
firewall is rebuilt. This is good. But if I remove/replace the pcmcia card,
ifup/ifdown don't appear to be run. The script as I have it (taken from a
reinstall, so not my fault :-) ) contains:
is_true $DHCLIENT || \
is_true $PUMP || is_true $BOOTP || is_true $DHCP || \
if [ -z "$IPADDR" -a -f /etc/network/interfaces ] ; then
INFO="Debian network setup"
start_fn () {
log /sbin/ifup $1
}
stop_fn () {
log /sbin/ifdown $1
}
fi
It seems I'd picked up a version of pcmcia-cs from sid in one of my experiments,
but even having downgraded this to 3.1.33-6 it does _not_ seem to invoke
ifup/ifdown (all that seems different is the use of hotplug in sid). I _did_
reset DHCP="y" when I recreated the network.opts file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
From: "Derek Broughton" <[EMAIL PROTECTED]>
> As near as I can tell, when you put stuff in /etc/network/interfaces, it gets
> executed at init time, before pcmcia gets started. If your card is already
> inserted, then when pcmcia _does_ start, ifup doesn't get executed. Perhaps
I'm
> misconfigured, but this is what's happening to me. I try to start firewall
> rules in /etc/network/interfaces and they don't start at power-up, but they
_do_
> start if I remove and reinsert the card. Now, looking at the file I see two
> potential problems:
>
> 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit circular,
when
> /etc/pcmcia/network.opts does "/sbin/ifup"?
OK, that obviously wasn't necessary - I probably did it myself long ago. I've
used etherconf to reconfigure my network without any damage - but without fixing
things.
> 2) the firewall script runs in a "pre-up" as well. It seemed like a good idea
> at the time, because I was thinking I wanted the firewall up before the link
was
> really active - but now that I think of it, I'm not sure dhclient will have
run
> before the firewall script starts - so I'll have to rtfm and check that. If
I'm
> right on this, it would explain why resetting the card will work, because dhcp
> always gets the same IP here, anyway.
I changed that and things are still not right.
If I do "ifdown eth0", the firewall is torn down. If I do "ifup eth0" the
firewall is rebuilt. This is good. But if I remove/replace the pcmcia card,
ifup/ifdown don't appear to be run. The script as I have it (taken from a
reinstall, so not my fault :-) ) contains:
is_true $DHCLIENT || \
is_true $PUMP || is_true $BOOTP || is_true $DHCP || \
if [ -z "$IPADDR" -a -f /etc/network/interfaces ] ; then
INFO="Debian network setup"
start_fn () {
log /sbin/ifup $1
}
stop_fn () {
log /sbin/ifdown $1
}
fi
It seems I'd picked up a version of pcmcia-cs from sid in one of my experiments,
but even having downgraded this to 3.1.33-6 it does _not_ seem to invoke
ifup/ifdown (all that seems different is the use of hotplug in sid). I _did_
reset DHCP="y" when I recreated the network.opts file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
From: "Ivar Alm" <[EMAIL PROTECTED]> > At 04:26 2003-03-19, mi wrote: > >Derek Broughton: > > > He appears to be using pcmcia nics, in which case changing anything in > > > .../interfaces won't do him a bit of good. > > > >In the past that would have been true. > >Now it's changed and the pcmcia tools join with > >etc/network/interfaces. > >Code's in movement, anytime. > > I have never understood (nor looked seriously at) /etc/pcmcia/network.opts. > I have only used /etc/interfaces, when setting up my pcmcia nic(s). > Perhaps it works but is the "wrong" way to do it? > > I might go back and rt(fine)m, but on the other hand - it works now. No, if you can get it to work, having it in /etc/network/interfaces is the right way. I, otoh, can't get a simple firewall script to run when my pcmcia nic is plugged in.
Re: your mail
From: "Mike Beattie" <[EMAIL PROTECTED]> > On Tue, Mar 18, 2003 at 10:37:00AM -0400, Derek Broughton wrote: > > > RTFM://interfaces(5) - around line 70 or so. > > > > He appears to be using pcmcia nics, in which case changing anything in > > ../interfaces won't do him a bit of good. > > What a load of shit. I use /e/n/interfaces for all of my PCMCIA cards, have > never had to modify /etc/pcmcia/*.opts . > > Go read some docs yourself, before commenting. (specifically, the last 16 or > so lines of /etc/pcmcia/network.opts) Geez. I'm taking a heck of a lot of abuse for a fairly reasonable line of response. I'd be taking less if your mail client hadn't, apparently auto-inserted the subject "your mail". Then I got a nasty response off-list for using that subject. Too bad, Angela, but I don't like changing subjects mid-thread. However, this is important enough to me that I'm willing to still be friendly about it. As near as I can tell, when you put stuff in /etc/network/interfaces, it gets executed at init time, before pcmcia gets started. If your card is already inserted, then when pcmcia _does_ start, ifup doesn't get executed. Perhaps I'm misconfigured, but this is what's happening to me. I try to start firewall rules in /etc/network/interfaces and they don't start at power-up, but they _do_ start if I remove and reinsert the card. Now, looking at the file I see two potential problems: 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit circular, when /etc/pcmcia/network.opts does "/sbin/ifup"? 2) the firewall script runs in a "pre-up" as well. It seemed like a good idea at the time, because I was thinking I wanted the firewall up before the link was really active - but now that I think of it, I'm not sure dhclient will have run before the firewall script starts - so I'll have to rtfm and check that. If I'm right on this, it would explain why resetting the card will work, because dhcp always gets the same IP here, anyway. derek
Re: your mail
From: "Ivar Alm" <[EMAIL PROTECTED]> > At 04:26 2003-03-19, mi wrote: > >Derek Broughton: > > > He appears to be using pcmcia nics, in which case changing anything in > > > .../interfaces won't do him a bit of good. > > > >In the past that would have been true. > >Now it's changed and the pcmcia tools join with > >etc/network/interfaces. > >Code's in movement, anytime. > > I have never understood (nor looked seriously at) /etc/pcmcia/network.opts. > I have only used /etc/interfaces, when setting up my pcmcia nic(s). > Perhaps it works but is the "wrong" way to do it? > > I might go back and rt(fine)m, but on the other hand - it works now. No, if you can get it to work, having it in /etc/network/interfaces is the right way. I, otoh, can't get a simple firewall script to run when my pcmcia nic is plugged in. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
From: "Mike Beattie" <[EMAIL PROTECTED]> > On Tue, Mar 18, 2003 at 10:37:00AM -0400, Derek Broughton wrote: > > > RTFM://interfaces(5) - around line 70 or so. > > > > He appears to be using pcmcia nics, in which case changing anything in > > ../interfaces won't do him a bit of good. > > What a load of shit. I use /e/n/interfaces for all of my PCMCIA cards, have > never had to modify /etc/pcmcia/*.opts . > > Go read some docs yourself, before commenting. (specifically, the last 16 or > so lines of /etc/pcmcia/network.opts) Geez. I'm taking a heck of a lot of abuse for a fairly reasonable line of response. I'd be taking less if your mail client hadn't, apparently auto-inserted the subject "your mail". Then I got a nasty response off-list for using that subject. Too bad, Angela, but I don't like changing subjects mid-thread. However, this is important enough to me that I'm willing to still be friendly about it. As near as I can tell, when you put stuff in /etc/network/interfaces, it gets executed at init time, before pcmcia gets started. If your card is already inserted, then when pcmcia _does_ start, ifup doesn't get executed. Perhaps I'm misconfigured, but this is what's happening to me. I try to start firewall rules in /etc/network/interfaces and they don't start at power-up, but they _do_ start if I remove and reinsert the card. Now, looking at the file I see two potential problems: 1) it does "pre-up /etc/pcmcia/network start" - isn't this a bit circular, when /etc/pcmcia/network.opts does "/sbin/ifup"? 2) the firewall script runs in a "pre-up" as well. It seemed like a good idea at the time, because I was thinking I wanted the firewall up before the link was really active - but now that I think of it, I'm not sure dhclient will have run before the firewall script starts - so I'll have to rtfm and check that. If I'm right on this, it would explain why resetting the card will work, because dhcp always gets the same IP here, anyway. derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
At 04:26 2003-03-19, mi wrote: Derek Broughton: > He appears to be using pcmcia nics, in which case changing anything in > .../interfaces won't do him a bit of good. In the past that would have been true. Now it's changed and the pcmcia tools join with etc/network/interfaces. Code's in movement, anytime. I have never understood (nor looked seriously at) /etc/pcmcia/network.opts. I have only used /etc/interfaces, when setting up my pcmcia nic(s). Perhaps it works but is the "wrong" way to do it? I might go back and rt(fine)m, but on the other hand - it works now. //I -- * Ivar Alm ! Where does Microsoft want to drag you today? ! Umeå, Sweden ! Do you really want to go there? ! [EMAIL PROTECTED] http://www.octofingers.com
Re: your mail
At 04:26 2003-03-19, mi wrote: Derek Broughton: > He appears to be using pcmcia nics, in which case changing anything in > .../interfaces won't do him a bit of good. In the past that would have been true. Now it's changed and the pcmcia tools join with etc/network/interfaces. Code's in movement, anytime. I have never understood (nor looked seriously at) /etc/pcmcia/network.opts. I have only used /etc/interfaces, when setting up my pcmcia nic(s). Perhaps it works but is the "wrong" way to do it? I might go back and rt(fine)m, but on the other hand - it works now. //I -- * Ivar Alm ! Where does Microsoft want to drag you today? ! Umeå, Sweden ! Do you really want to go there? ! [EMAIL PROTECTED] http://www.octofingers.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Derek Broughton: > He appears to be using pcmcia nics, in which case changing anything in > .../interfaces won't do him a bit of good. In the past that would have been true. Now it's changed and the pcmcia tools join with etc/network/interfaces. Code's in movement, anytime. -- micha.
Re: your mail
I don't see any need to flip out about it, but for reference:
---
[EMAIL PROTECTED]:~$ tail -n 16 /etc/pcmcia/network.opts
DHCP="n"
IPADDR="10.0.1.212"
NETMASK="255.255.255.0"
NETWORK="10.0.1.0"
BROADCAST="10.0.1.255"
GATEWAY="10.0.1.1"
DOMAIN="cyn.org"
DNS_1="127.0.0.1"
IPMASQ="n"
start_fn () { return; }
stop_fn () { return; }
# Card eject policy options
NO_CHECK="n"
NO_FUSER="n"
;;
esac
---
referencing comments from config files isn't generally effective because
you have no idea when they got the original file and modified it to fit
their needs - it's better to quote things or suggest things to search
for, from docs or man pages - config files that *will* exist won't always
have the same comments - but same systems should have the same docfiles
and man pages. I personally haven't edited my network.opts file except to
create multiple schemes, I've not removed any comments. [it just has the
comments at the top, talking about the "network address" != IP and to see
the Networking HOWTO.
-Martin N.
On Wed, 19 Mar 2003, Mike Beattie wrote:
> On Tue, Mar 18, 2003 at 10:37:00AM -0400, Derek Broughton wrote:
> > > RTFM://interfaces(5) - around line 70 or so.
> >
> > He appears to be using pcmcia nics, in which case changing anything in
> > ../interfaces won't do him a bit of good.
>
> What a load of shit. I use /e/n/interfaces for all of my PCMCIA cards, have
> never had to modify /etc/pcmcia/*.opts .
>
> Go read some docs yourself, before commenting. (specifically, the last 16 or
> so lines of /etc/pcmcia/network.opts)
>
> Mike.
> --
> Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184
Re: your mail
Derek Broughton: > He appears to be using pcmcia nics, in which case changing anything in > .../interfaces won't do him a bit of good. In the past that would have been true. Now it's changed and the pcmcia tools join with etc/network/interfaces. Code's in movement, anytime. -- micha. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
I don't see any need to flip out about it, but for reference:
---
[EMAIL PROTECTED]:~$ tail -n 16 /etc/pcmcia/network.opts
DHCP="n"
IPADDR="10.0.1.212"
NETMASK="255.255.255.0"
NETWORK="10.0.1.0"
BROADCAST="10.0.1.255"
GATEWAY="10.0.1.1"
DOMAIN="cyn.org"
DNS_1="127.0.0.1"
IPMASQ="n"
start_fn () { return; }
stop_fn () { return; }
# Card eject policy options
NO_CHECK="n"
NO_FUSER="n"
;;
esac
---
referencing comments from config files isn't generally effective because
you have no idea when they got the original file and modified it to fit
their needs - it's better to quote things or suggest things to search
for, from docs or man pages - config files that *will* exist won't always
have the same comments - but same systems should have the same docfiles
and man pages. I personally haven't edited my network.opts file except to
create multiple schemes, I've not removed any comments. [it just has the
comments at the top, talking about the "network address" != IP and to see
the Networking HOWTO.
-Martin N.
On Wed, 19 Mar 2003, Mike Beattie wrote:
> On Tue, Mar 18, 2003 at 10:37:00AM -0400, Derek Broughton wrote:
> > > RTFM://interfaces(5) - around line 70 or so.
> >
> > He appears to be using pcmcia nics, in which case changing anything in
> > ../interfaces won't do him a bit of good.
>
> What a load of shit. I use /e/n/interfaces for all of my PCMCIA cards, have
> never had to modify /etc/pcmcia/*.opts .
>
> Go read some docs yourself, before commenting. (specifically, the last 16 or
> so lines of /etc/pcmcia/network.opts)
>
> Mike.
> --
> Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Tue, Mar 18, 2003 at 10:37:00AM -0400, Derek Broughton wrote: > > RTFM://interfaces(5) - around line 70 or so. > > He appears to be using pcmcia nics, in which case changing anything in > ../interfaces won't do him a bit of good. What a load of shit. I use /e/n/interfaces for all of my PCMCIA cards, have never had to modify /etc/pcmcia/*.opts . Go read some docs yourself, before commenting. (specifically, the last 16 or so lines of /etc/pcmcia/network.opts) Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 Spock, the women on your planet are logical. No other planet in the galaxy can make that claim. -- Capt. James T. Kirk
Re: your mail
On Tue, Mar 18, 2003 at 10:37:00AM -0400, Derek Broughton wrote: > > RTFM://interfaces(5) - around line 70 or so. > > He appears to be using pcmcia nics, in which case changing anything in > ../interfaces won't do him a bit of good. What a load of shit. I use /e/n/interfaces for all of my PCMCIA cards, have never had to modify /etc/pcmcia/*.opts . Go read some docs yourself, before commenting. (specifically, the last 16 or so lines of /etc/pcmcia/network.opts) Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 Spock, the women on your planet are logical. No other planet in the galaxy can make that claim. -- Capt. James T. Kirk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
From: "Mike Beattie" <[EMAIL PROTECTED]> > On Mon, Mar 17, 2003 at 09:04:52PM +0100, [EMAIL PROTECTED] wrote: > > The problem is, I want to run ipmasq on this laptop. Right now I let the > > settings for the NICs be taken from /etc/network/interfaces. The cards are > > configured correctly. But ipmasq is started two early, so I have to manually > > restart ipmasq after each boot to make it work. I saw an option in > > /etc/pcmcia/network.opts that lets me choose whether to run ipmasq. I think this could solve > > the problem. But for this option to be effective I must put my configuration > > for both cards in /etc/pcmcia/network.opts. > > So use the 'up' directive in /e/n/interfaces > > RTFM://interfaces(5) - around line 70 or so. He appears to be using pcmcia nics, in which case changing anything in .../interfaces won't do him a bit of good.
Re: your mail
From: "Mike Beattie" <[EMAIL PROTECTED]> > On Mon, Mar 17, 2003 at 09:04:52PM +0100, [EMAIL PROTECTED] wrote: > > The problem is, I want to run ipmasq on this laptop. Right now I let the > > settings for the NICs be taken from /etc/network/interfaces. The cards are > > configured correctly. But ipmasq is started two early, so I have to manually > > restart ipmasq after each boot to make it work. I saw an option in > > /etc/pcmcia/network.opts that lets me choose whether to run ipmasq. I think this could solve > > the problem. But for this option to be effective I must put my configuration > > for both cards in /etc/pcmcia/network.opts. > > So use the 'up' directive in /e/n/interfaces > > RTFM://interfaces(5) - around line 70 or so. He appears to be using pcmcia nics, in which case changing anything in .../interfaces won't do him a bit of good. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Mon, Mar 17, 2003 at 09:04:52PM +0100, [EMAIL PROTECTED] wrote: > The problem is, I want to run ipmasq on this laptop. Right now I let the > settings for the NICs be taken from /etc/network/interfaces. The cards are > configured correctly. But ipmasq is started two early, so I have to manually > restart ipmasq after each boot to make it work. I saw an option in > /etc/pcmcia/network.opts that lets me choose whether to run ipmasq. I think > this could solve > the problem. But for this option to be effective I must put my configuration > for both cards in /etc/pcmcia/network.opts. So use the 'up' directive in /e/n/interfaces RTFM://interfaces(5) - around line 70 or so. Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 "This isnt Mission Difficult Mr Hunt, this is Mission Impossible. Difficult should be a walk in the park for you." -- MI:2
Re: your mail
On Mon, Mar 17, 2003 at 09:04:52PM +0100, [EMAIL PROTECTED] wrote: > The problem is, I want to run ipmasq on this laptop. Right now I let the > settings for the NICs be taken from /etc/network/interfaces. The cards are > configured correctly. But ipmasq is started two early, so I have to manually > restart ipmasq after each boot to make it work. I saw an option in > /etc/pcmcia/network.opts that lets me choose whether to run ipmasq. I think this > could solve > the problem. But for this option to be effective I must put my configuration > for both cards in /etc/pcmcia/network.opts. So use the 'up' directive in /e/n/interfaces RTFM://interfaces(5) - around line 70 or so. Mike. -- Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184 "This isnt Mission Difficult Mr Hunt, this is Mission Impossible. Difficult should be a walk in the park for you." -- MI:2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
El jue, 07-03-2002 a las 08:51, Francesco P. Lovergine escribió: > Did anyone install a Compaq Presario 2700? > I'm going to buy one of that monsters and I'd like to install sid on it. > Any problem with video/sound/etc? Any first hand suggestion? Two weeks ago I bought a Compaq Presario 1711LA. I know that is not the same model, but normally they share the sames chipsets. I don't have the notebook here, but the folowing is I remember: lspci (kernel-2.4.18), show unknown model in almost all. Video: ATI Radeon Mobile L6 Y. This card is not supported by any xfree's debian package. Some mails says that XFree 4.2 has support for this chip, but the xfree86 doesn't say anything specifically. May be CVS. However, it's work as VESA, 1024x768, 24 bits depth, without acceleration. Sound: Intel AC'97. Perhaps its need an ALSA patch to work. I don't if exists. Network card: Intel. Doesn't work with kernel-2.2.x at least you must compile e100 module (there is a e100-source package). I installed by network, but I used a pcmcia network card. After install 2.4.18 (also 2.4.17), the network card started to works fine with eepro100 module. APM doesn't work. You need to compile ACPI support on the kernel. I don't know how it works, because I haven't have time to do it. Touchpad, works fine (/dev/psaux). -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html
Re: your mail
El jue, 07-03-2002 a las 08:51, Francesco P. Lovergine escribió: > Did anyone install a Compaq Presario 2700? > I'm going to buy one of that monsters and I'd like to install sid on it. > Any problem with video/sound/etc? Any first hand suggestion? Two weeks ago I bought a Compaq Presario 1711LA. I know that is not the same model, but normally they share the sames chipsets. I don't have the notebook here, but the folowing is I remember: lspci (kernel-2.4.18), show unknown model in almost all. Video: ATI Radeon Mobile L6 Y. This card is not supported by any xfree's debian package. Some mails says that XFree 4.2 has support for this chip, but the xfree86 doesn't say anything specifically. May be CVS. However, it's work as VESA, 1024x768, 24 bits depth, without acceleration. Sound: Intel AC'97. Perhaps its need an ALSA patch to work. I don't if exists. Network card: Intel. Doesn't work with kernel-2.2.x at least you must compile e100 module (there is a e100-source package). I installed by network, but I used a pcmcia network card. After install 2.4.18 (also 2.4.17), the network card started to works fine with eepro100 module. APM doesn't work. You need to compile ACPI support on the kernel. I don't know how it works, because I haven't have time to do it. Touchpad, works fine (/dev/psaux). -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
Hi folks. Did anyone install a Compaq Presario 2700? I'm going to buy one of that monsters and I'd like to install sid on it. Any problem with video/sound/etc? Any first hand suggestion? Thanks PS: Please CC me. -- Francesco P. Lovergine
Re: your mail
Hi folks. Did anyone install a Compaq Presario 2700? I'm going to buy one of that monsters and I'd like to install sid on it. Any problem with video/sound/etc? Any first hand suggestion? Thanks PS: Please CC me. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On 23 May 2001, CC. Spindler wrote: > >Sorry, we working on the task-kichen package. > >Maybe u should try fridge-0.1.deb and fridge-contents-0.1-be(er)ta.deb >first. > >CC. --- a bit silly today. ;) > what I'm looking for is the cold-beer packageI have the source but its not compiling too well, there seems to be some missing libraries or something, something like libkeg and libglass. Any ideas where to download them...? Alex
Re: your mail
On 23 May 2001, CC. Spindler wrote: > >Sorry, we working on the task-kichen package. > >Maybe u should try fridge-0.1.deb and fridge-contents-0.1-be(er)ta.deb >first. > >CC. --- a bit silly today. ;) > what I'm looking for is the cold-beer packageI have the source but its not compiling too well, there seems to be some missing libraries or something, something like libkeg and libglass. Any ideas where to download them...? Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
The keyboard of Alexander Clouter <[EMAIL PROTECTED]> wrote: >> [something about tacky kitchens] > > I'm not sure if I can see a .deb package for it.. Sorry, we working on the task-kichen package. Maybe u should try fridge-0.1.deb and fridge-contents-0.1-be(er)ta.deb first. CC. --- a bit silly today. ;) -- Geometric shapes are the easiest. Fractals are simple. But after the Fractals the real mess starts. -- Benoit B. Mandelbrot
Re: your mail
The keyboard of Alexander Clouter <[EMAIL PROTECTED]> wrote: >> [something about tacky kitchens] > > I'm not sure if I can see a .deb package for it.. Sorry, we working on the task-kichen package. Maybe u should try fridge-0.1.deb and fridge-contents-0.1-be(er)ta.deb first. CC. --- a bit silly today. ;) -- Geometric shapes are the easiest. Fractals are simple. But after the Fractals the real mess starts. -- Benoit B. Mandelbrot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Tue, 22 May 2001, John wrote: > > Hey there, I found a great retail site with all kinds of products. Home > decor, office decor, travel, outdoors, kitchen, etc... Take a look around > at http://www.merchandisewholesale.com just click on the images of the > product to enlarge it for a better view. > however can the kitchen be plugged into my infra-red port? Are there any drivers for it? I'm not sure if I can see a .deb package for it.. Alex
Re: your mail
On Tue, 22 May 2001, John wrote: > > Hey there, I found a great retail site with all kinds of products. Home > decor, office decor, travel, outdoors, kitchen, etc... Take a look around > at http://www.merchandisewholesale.com just click on the images of the > product to enlarge it for a better view. > however can the kitchen be plugged into my infra-red port? Are there any drivers for it? I'm not sure if I can see a .deb package for it.. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
everyone, this is a LINUX list. I think this question is toofar out-of-topic here! On Tue, 17 Oct 2000, Duccio Medini wrote: > On Tue, 17 Oct 2000, sparlinek wrote: > > > Hi, I have a laptop with an ES1869 AudioDrive > > card, which I have tried to compile into windows 2000. It seems not to be > > working properly. Any suggestions, where to download the right driver. > > Thanks. Sparlinek > > Do you know of ANY sound card 'properly' working on a lap with > w2000 on? Do you know of any w2000-lap 'properly' working at all? > > Duccio > > > ++ > > doct. Duccio Medini |mobile: +39 347 3343114 > PhD Student |phone: +39 075 5852760 > Physics Dept. | > Biophysics Sector |fax:+39 075 44666 > Perugia University (ITALY) |Via A. Pascoli > INFM, Perugia Unit |06123 Perugia (I) > > e-mail: [EMAIL PROTECTED] > > ++ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > --- Andor Demarteau [EMAIL PROTECTED] ---
Re: your mail
everyone, this is a LINUX list. I think this question is toofar out-of-topic here! On Tue, 17 Oct 2000, Duccio Medini wrote: > On Tue, 17 Oct 2000, sparlinek wrote: > > > Hi, I have a laptop with an ES1869 AudioDrive > > card, which I have tried to compile into windows 2000. It seems not to be > > working properly. Any suggestions, where to download the right driver. > > Thanks. Sparlinek > > Do you know of ANY sound card 'properly' working on a lap with > w2000 on? Do you know of any w2000-lap 'properly' working at all? > > Duccio > > > ++ > > doct. Duccio Medini |mobile: +39 347 3343114 > PhD Student |phone: +39 075 5852760 > Physics Dept. | > Biophysics Sector |fax:+39 075 44666 > Perugia University (ITALY) |Via A. Pascoli > INFM, Perugia Unit |06123 Perugia (I) > > e-mail: [EMAIL PROTECTED] > > ++ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > --- Andor Demarteau [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Tue, 17 Oct 2000, sparlinek wrote: > Hi, I have a laptop with an ES1869 AudioDrive > card, which I have tried to compile into windows 2000. It seems not to be > working properly. Any suggestions, where to download the right driver. > Thanks. Sparlinek Do you know of ANY sound card 'properly' working on a lap with w2000 on? Do you know of any w2000-lap 'properly' working at all? Duccio ++ doct. Duccio Medini |mobile: +39 347 3343114 PhD Student |phone: +39 075 5852760 Physics Dept. | Biophysics Sector |fax:+39 075 44666 Perugia University (ITALY) |Via A. Pascoli INFM, Perugia Unit |06123 Perugia (I) e-mail: [EMAIL PROTECTED] ++
Re: your mail
On Tue, 17 Oct 2000, sparlinek wrote: > Hi, I have a laptop with an ES1869 AudioDrive > card, which I have tried to compile into windows 2000. It seems not to be > working properly. Any suggestions, where to download the right driver. > Thanks. Sparlinek Do you know of ANY sound card 'properly' working on a lap with w2000 on? Do you know of any w2000-lap 'properly' working at all? Duccio ++ doct. Duccio Medini |mobile: +39 347 3343114 PhD Student |phone: +39 075 5852760 Physics Dept. | Biophysics Sector |fax:+39 075 44666 Perugia University (ITALY) |Via A. Pascoli INFM, Perugia Unit |06123 Perugia (I) e-mail: [EMAIL PROTECTED] ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: your mail
On Thu, May 25, 2000 at 10:29:30AM -0500, Jeffrey Knight wrote: > Morning all: > What's the best place to get started in actually conributing to debian? I > subscribed to debian-users but couldn't take the bulk of email. Where does > the project need help? did you try reading www.debian.org/devel ? Might be a good start. Anyway: I guess documentation needs much work. Marcin -- ++ The reason we come up with new versions |Marcin Owsiany | is not to fix bugs. It's the stupidest |[EMAIL PROTECTED]| reason to buy a new version ++ I ever heard.- Bill Gates
