pcmcia interfaces for boot floppies

2000-01-30 Thread Randolph Chung
In looking through dbootstrap, it seems that the pcmcia+dhcp code is not yet
completed. i'm not sure who was working on that last. If you, faithful reader, 
are that person, please speak up! :-)

Now, if you are installing on dhcp+ethernet, dbootstrap writes to
/etc/network/interfaces, and I believe this works fine. However, what is the
scenario with pcmcia+/etc/network/interfaces? Does pcmcia work with that
file? What are the exact configuration information that dboostrap will need
to write for pcmcia+dhcp to work?

thanks,
randolph
-- 
Debian Developer <[EMAIL PROTECTED]>
http://www.TauSq.org/


pcmcia modem

2000-01-30 Thread Tim Sailer

Hi all.
  I have that Xircom combo card, and I can bully the ethernet part
into working, but I'm still having fits with the modem. Although it
seems to configure as ttyS1, stty gives an i/o error, and even
poking it with minicom seems to have no effect. Any pointers?

Tim

-- 
 (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps
   Now and then an innocent man is sent to the legislature.
** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**


Re: Bug#56600: pcmcia interfaces for boot floppies

2000-01-30 Thread Stefan Gybas
Randolph Chung wrote:

> In looking through dbootstrap, it seems that the pcmcia+dhcp code is not yet
> completed. i'm not sure who was working on that last. If you, faithful reader,
> are that person, please speak up! :-)

Hopefully a friend of mine will lend me his laptop next week so I can finish
this - right now I don't have PCMCIA.

> Now, if you are installing on dhcp+ethernet, dbootstrap writes to
> /etc/network/interfaces, and I believe this works fine.

Not really. The problem is that netbase tries to call dhclient (from the
dhcp-client package) for DHCP interfaces in /etc/network/interfaces. However,
dhclient requires a kernel that was compiled with CONFIG_PACKET and
CONFIG_FILTER. Both kernels (standard and compact) have af_packet.o as module
but only the compact kernel has CONFIG_FILTER=y - so you can't use dhclient
with the standard kernel.

The best solution would be if ifup from netbase used pump instead of
dhclient. pump is also on the boot floppies and it requires only
CONFIG_PACKET (but on the other hand only works with kernel 2.2). I have
filed an important bug against netbase (#56020) which includes a patch
for this.

> However, what is the scenario with pcmcia+/etc/network/interfaces?

PCMCIA interfaces take their network configuration from the file
/etc/pcmcia/network.opts, you can also set DHCP there.

> Does pcmcia work with that file?

No, the maintainer of pcmcia-cs decided not to use this file because it
contains some comments about the alpha state of ifup/ifdown (see the recent
discussion on debian-boot with the subject "Static network configuration").

-- 
Stefan Gybas



Re: Remapping Keyboard Keys

2000-01-30 Thread Seth Golub

I wrote:

> Your default keymap is in /etc/kbd/ 

Oops.  I'm out of date.  If you're more modern than I am, it's in
/etc/console-tools/.


Re: Sound on IBM Thinkpad 390E

2000-01-30 Thread Florian Lohoff
On Wed, Jan 26, 2000 at 04:06:40PM -0600, Bryan K. Walton wrote:
> insmod soundcore
> insmod esssolo1
> mixctrl 7 0
> mixctrl 0 100
> mixctrl 4 100
> 

I am using Alsa and have no problems at all - Works like a charm ...

conf.modules excerpt ...

---
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 0.4.0 ---
alias char-major-116 snd
alias snd-card-0 snd-card-es1938
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm1-oss
alias sound-service-0-12 snd-pcm1-oss
options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=
29 snd_device_uid=0
options snd-card-es1938 snd_index=1 snd_id=CARD_1
# --- END: Generated by ALSACONF, do not edit. ---
---

Suspend/Resume doesnt work (Doesnt work for IRDA either) and i have a
"Feature Request" open :)

Flo
-- 
Florian Lohoff  [EMAIL PROTECTED]   +49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."


Re: EtherExpress Pro fails on 100baseTx

2000-01-30 Thread Bart-Jan Vrielink
On Sat, 29 Jan 2000, John Lapeyre wrote:

> I have an Intel EtherExpress PRO/100
> 16 bit combo card.  I am testing it
> on various 10baseT hubs and with a 
> crossover cable directly to 100 Mbit cards.

I happen to have a ethernet only EtherExpress PRO/100, but I'm not sure
it's the same type of card, there are different types of cards under the
same name. Mine uses the xircom driver.
 
> It works fine if both cards are set to 10baseT-HD
> (for instance with D Becker's mii-diag program,
> or through autonegotiation).  I can pretty much 
> saturate the link.  However at 10baseT-FD, I
> get only about 100 KB/s (instead of 800 or 900).
> Also at 100baseTx I either get 100KB/s (talking to
> a card using the rtl8139 driver) or nothing
> at all (talking to a DLink card that uses 
> via-rhine driver ).  mii-diag shows that the cards are reading
> each other's beat frequencies and they negotiate fine.
> But if they negotiate for, or I force, 100baseTx (HD or FD) 
> it doesn't work. Again, if I force 10baseT-HD I get about
> 800 KB/s.  
>   I have only tried one crossover cable so far.
> I have not really tested the modem, but it dials OK.

I have only tested against a 3C905btx, and only HD on a switched lan, with
ttcp.
I found out that the card wasn't any faster on 100base than it was on
10baset, only when transmitting it was 50% faster, but at a cost of 100%
CPU load...
I never managed to get autonegotiation to work with this card (but gave op
quite soon), so I generally only use 10base HD.

> I am running a current Debian potato on a new Sager 3550 notebook. I
> am running kernel 2.2.14.  I have compiled all the pcmcia stuff myself.  I
> tried various recent pcmcia-cs and module versions, and a few recent
> versions of the via-rhine driver. (I have tried the latest stable and
> unstable versions, if available, from the authors' websites).
> 
> Anyone have a clue what is going on ? 

Well, rememeber that a 16 bit PCMCIA bus can be compared with ISA
speeds... and that's just enough to handle 10base networks. (I have a
3c515 network card too - 100basetx ISA NIC...)

You do know that using Full Duplex with a HUB isn't going to work ??

-- 
Tot ziens,

Bart-Jan