Re: md5400 Network Problem

2003-01-17 Thread Kowalski Boris
Hello again,
> > Hi,
> > -lsmod shows
> > Module Size Used by Not tainted
> [various filesystems.  you really use all of those?  The nice thing
> about modules is you don't have to load them until they're needed.]
no i dont need them ... i compiled a new kernel and have this all disabled

> Well, it isn't saying here that it hates you - the module *is* loaded.
> You should in fact be able to unload it and reload (with rmmod) to
> see the effect repeated.
now there is are the 8139* drivers compiled in kernel not module

-8 But please note that loading the module won't invoke ifconfig at the
> same time; there will be more to do.
ifconfig shows me that the device eth0 is up and configured right

> It is worth mentoning that there was more than one available module
> that can handle 8139 cards;  perhaps you need the other one.
>

on bootup there are this messages
8139too Fast Ethernet driver 0.9.24
PCI: Enabling device 00:08.0 ( -> 0003)
PCI: Found IRQ 9 for device 00:08.0
PCI: Sharing IRQ 9 with 00:06.0
IRQ routing conflict for 00:0c.0, have irq 10, want irq 9
PCI: Sharing IRQ 9 with 00:0d.0
eth0: RealTek RTL8139 Fast Ethernet at 0xd4824000, 00:40:ca:bc:97:e9, IRQ 9
eth0:  Identified 8139 chip type 'RTL-8139C'

> Anyways, the next part is, give us the messages that happen when you
> only unload and reload the 8139too module, and what ifconfig eth0 says
> after that.
i compile the kernel new with network as module so i can test this and send
new
entries when tested

thx boris



Re: md5400 Network Problem

2003-01-17 Thread Kowalski Boris
Hello again,
> > Hi,
> > -lsmod shows
> > Module Size Used by Not tainted
> [various filesystems.  you really use all of those?  The nice thing
> about modules is you don't have to load them until they're needed.]
no i dont need them ... i compiled a new kernel and have this all disabled

> Well, it isn't saying here that it hates you - the module *is* loaded.
> You should in fact be able to unload it and reload (with rmmod) to
> see the effect repeated.
now there is are the 8139* drivers compiled in kernel not module

-8 But please note that loading the module won't invoke ifconfig at the
> same time; there will be more to do.
ifconfig shows me that the device eth0 is up and configured right

> It is worth mentoning that there was more than one available module
> that can handle 8139 cards;  perhaps you need the other one.
>

on bootup there are this messages
8139too Fast Ethernet driver 0.9.24
PCI: Enabling device 00:08.0 ( -> 0003)
PCI: Found IRQ 9 for device 00:08.0
PCI: Sharing IRQ 9 with 00:06.0
IRQ routing conflict for 00:0c.0, have irq 10, want irq 9
PCI: Sharing IRQ 9 with 00:0d.0
eth0: RealTek RTL8139 Fast Ethernet at 0xd4824000, 00:40:ca:bc:97:e9, IRQ 9
eth0:  Identified 8139 chip type 'RTL-8139C'

> Anyways, the next part is, give us the messages that happen when you
> only unload and reload the 8139too module, and what ifconfig eth0 says
> after that.
i compile the kernel new with network as module so i can test this and send
new
entries when tested

thx boris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: md5400 Network Problem

2003-01-17 Thread Heather Stern
On Thu, Jan 16, 2003 at 08:33:19AM +0100, Kowalski Boris wrote:

...a private reply.  Doris, the Debian Laptop list exists so that all
its members can benefit from good answers;  also so that multiple people
can help someone with a very tricky problem.  I'm cc'ing the list, which
I'm on, and I'd appreciate if the thread continues to be public.  TIA.

> Hi,
> > Good.  You should be able to spot its entry by using lspci.

I've reduced the list below to the things which relate to ethernet...

> > If its driver needs options then you can messa round with insmod until
> > you have given it options that seem to load it safely, then get those
> > established in an extra textfile in /etc/modutils.  (I like to use
> > local-servicetype, you know, ether or sound or whatever.)
> >
> > Let us know what lspci says about your card?
> -lspci
> 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
> 10)
> 
> -lsmod shows
> Module Size Used by Not tainted
[various filesystems.  you really use all of those?  The nice thing
about modules is you don't have to load them until they're needed.]
> af_packet 13416 0 (autoclean)
> nls_cp437 4380 0 (autoclean)
> agpgart 31136 0 (unused)
[audio things]
> 8139too 14664 0
> mii 1008 0 [8139too]

Well, it isn't saying here that it hates you - the module *is* loaded.
You should in fact be able to unload it and reload (with rmmod) to
see the effect repeated.

But please note that loading the module won't invoke ifconfig at the
same time; there will be more to do.

It is worth mentoning that there was more than one available module
that can handle 8139 cards;  perhaps you need the other one.

> serial 51908 0 (autoclean)
> mousedev 3864 0
[various USB things]
> ds 6472 1
> yenta_socket 8704 1
> pcmcia_core 37568 0 [ds yenta_socket]

your pcmcia looks good but it appears that your ethernet is builtin
so don't worry about this part.

> rtc 6940 0 (autoclean)
> cloop 23396 1
 
compressed loopback?  You running knoppix maybe?  :)

> thx Boris

Anyways, the next part is, give us the messages that happen when you
only unload and reload the 8139too module, and what ifconfig eth0 says 
after that.

* Heather Stern * star@ many places...
* Starshine Technical Services -*- 800 938 4078



Re: md5400 Network Problem

2003-01-17 Thread Heather Stern
On Thu, Jan 16, 2003 at 08:33:19AM +0100, Kowalski Boris wrote:

...a private reply.  Doris, the Debian Laptop list exists so that all
its members can benefit from good answers;  also so that multiple people
can help someone with a very tricky problem.  I'm cc'ing the list, which
I'm on, and I'd appreciate if the thread continues to be public.  TIA.

> Hi,
> > Good.  You should be able to spot its entry by using lspci.

I've reduced the list below to the things which relate to ethernet...

> > If its driver needs options then you can messa round with insmod until
> > you have given it options that seem to load it safely, then get those
> > established in an extra textfile in /etc/modutils.  (I like to use
> > local-servicetype, you know, ether or sound or whatever.)
> >
> > Let us know what lspci says about your card?
> -lspci
> 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
> 10)
> 
> -lsmod shows
> Module Size Used by Not tainted
[various filesystems.  you really use all of those?  The nice thing
about modules is you don't have to load them until they're needed.]
> af_packet 13416 0 (autoclean)
> nls_cp437 4380 0 (autoclean)
> agpgart 31136 0 (unused)
[audio things]
> 8139too 14664 0
> mii 1008 0 [8139too]

Well, it isn't saying here that it hates you - the module *is* loaded.
You should in fact be able to unload it and reload (with rmmod) to
see the effect repeated.

But please note that loading the module won't invoke ifconfig at the
same time; there will be more to do.

It is worth mentoning that there was more than one available module
that can handle 8139 cards;  perhaps you need the other one.

> serial 51908 0 (autoclean)
> mousedev 3864 0
[various USB things]
> ds 6472 1
> yenta_socket 8704 1
> pcmcia_core 37568 0 [ds yenta_socket]

your pcmcia looks good but it appears that your ethernet is builtin
so don't worry about this part.

> rtc 6940 0 (autoclean)
> cloop 23396 1
 
compressed loopback?  You running knoppix maybe?  :)

> thx Boris

Anyways, the next part is, give us the messages that happen when you
only unload and reload the 8139too module, and what ifconfig eth0 says 
after that.

* Heather Stern * star@ many places...
* Starshine Technical Services -*- 800 938 4078


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: md5400 Network Problem

2003-01-15 Thread Kowalski Boris
Hi,
> If it's pcmcia based, the fille to tell it to not try some interrupts
> is /etc/pcmcia/config.opts
I dont know how the Netcard is "connected" it is an internal not in the
pcmcia Slot.

> If it's not, then you may need to set options for the kernel module -
> esp on an older system where it may be effectively an ISA card.
And when the card is an pci or sth else is there a config for that case?
Its an P4 2,53GHz so i dont think it was an isa card
--
thx
Kowalski Boris




Re: md5400 Network Problem

2003-01-15 Thread Kowalski Boris
Hi,
> If it's pcmcia based, the fille to tell it to not try some interrupts
> is /etc/pcmcia/config.opts
I dont know how the Netcard is "connected" it is an internal not in the
pcmcia Slot.

> If it's not, then you may need to set options for the kernel module -
> esp on an older system where it may be effectively an ISA card.
And when the card is an pci or sth else is there a config for that case?
Its an P4 2,53GHz so i dont think it was an isa card
--
thx
Kowalski Boris



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: md5400 Network Problem

2003-01-13 Thread Heather Stern
On Mon, Jan 13, 2003 at 10:05:01PM +0100, Kowalski Boris wrote:
> Hello,
> i have a problem on my Notebook. It has an internal Networkcard that works
> under knoppix, when i disable apic and apm. When i now try to use the Card
> on my debian woody installation the NIC doesnt work.
> I disable apic apm and/or acpi but it doesnt work. On bootup there are
> messages that there are 3 devices that would have irq9 where the netcard is.
> could that be the problem and when how could i fix that?
> The Device is up and configured correkt (ip and so on) but pings dont
> work... all network operations dont work.
> thx for answer

If it's pcmcia based, the fille to tell it to not try some interrupts
is /etc/pcmcia/config.opts

If it's not, then you may need to set options for the kernel module - 
esp on an older system where it may be effectively an ISA card.


* Heather Stern * star@ many places...
* Starshine Technical Services -*- 800 938 4078



Re: md5400 Network Problem

2003-01-13 Thread Heather Stern
On Mon, Jan 13, 2003 at 10:05:01PM +0100, Kowalski Boris wrote:
> Hello,
> i have a problem on my Notebook. It has an internal Networkcard that works
> under knoppix, when i disable apic and apm. When i now try to use the Card
> on my debian woody installation the NIC doesnt work.
> I disable apic apm and/or acpi but it doesnt work. On bootup there are
> messages that there are 3 devices that would have irq9 where the netcard is.
> could that be the problem and when how could i fix that?
> The Device is up and configured correkt (ip and so on) but pings dont
> work... all network operations dont work.
> thx for answer

If it's pcmcia based, the fille to tell it to not try some interrupts
is /etc/pcmcia/config.opts

If it's not, then you may need to set options for the kernel module - 
esp on an older system where it may be effectively an ISA card.


* Heather Stern * star@ many places...
* Starshine Technical Services -*- 800 938 4078


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]