Modul laden nach pcmcia start

Hi, ich hab ein Notebook auf debian testing mit Kernel 2.4.24-1-586tsc installiert. Nun wird der tulip Treiber für eine PCMCIA LAN Karte nicht mehr automatisch geladen. Bei 2.4.24 wird für PCMCIA yenta_socket verwendet im Gegensatz zu i8265 bei 2.4.18. An welcher Stelle muss ich nun angeben,

Re: Modul laden nach pcmcia start

Bonjour, this list is for english speakers :-) Merci Jerome Christoph Löffler wrote: Hi, ich hab ein Notebook auf debian testing mit Kernel 2.4.24-1-586tsc installiert. Nun wird der tulip Treiber für eine PCMCIA LAN Karte nicht mehr automatisch geladen. Bei 2.4.24 wird für PCMCIA yenta_socket

load module after pcmcia start

Hi, sorry for my post in german, monday morning I also read debian-user-german, then I decided to post this on debian-testing...ok: I have a notebook with debian testing and Kernel 2.4.24-1-586tsc The PCMCIA LAN card needs the tulip driver which is not loaded automatically. In 2.4.24 yenta

E-mail nao pode ser entregue - Mail not delivered

E-mail Filtrado REMETENTE / SENDER: <[EMAIL PROTECTED]> DESTINATARIO / RECIPIENT: <[EMAIL PROTECTED]> ASSUNTO / SUBJECT: ARQUIVOS ANEXADOS / ATTACHMENTS: cjchz.pif REGRA / RULE: Arq. PIF Seu limite e de: kbytes E-mail destruido por exceder limite de ta

Goodbye from our Mailinglist

Goodbye from our Mailinglist, sorry to see you go. You have been unsubscribed from the following mailinglists: * PKList D If there is an error in this information, you can re-subscribe: please go to http://www.pksites.net/lists/?p=subscribe and follow the steps. Thank you -- T

Problem with apache in testing

This morning I noticed that my apache server wasn't working, and wasn't able to start. `apache` was exiting immediately with a 0 return value, and `apache -X` was doing a segfault. Under gdb, I noticed that the segfault happened in strcmp() in libc6. Unfortunately, my gdb experiment is not good

Re: Problem with apache in testing

On Mon, 2004-02-02 at 23:18 -0500, Louis-David Perron wrote: > This morning I noticed that my apache server wasn't working, and wasn't able to > start. `apache` was exiting immediately with a 0 return value, and `apache -X` was > doing a segfault. Under gdb, I noticed that the segfault happened i