Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having

Moe Trin wrote:
I'm guessing here, but this sounds like the problem that Donald Becker
reported about the RTL8139[BC] some time ago. What driver are you using?
Do you see anything relating to the card in /var/log/messages - see where
the kernel is looking for the card at boot time.

Hi;
I know you know I'm not the OP, and for the sake of clarification, my
issue seems to be the almost exact *opposite* of the OP's; In my win98
+ Debian Sarge 3.1r1 (2.6.8-2 kernel) dual-boot setup, it's when I boot
up into *win98* after being in Debian for a while (anywhere from 1 day
to however long) that Microcrud's 'ZeroConf' crap occurs in win98 for
me. My (quickest) workaround has been to just reboot....ala the MS way
:-/

Some information that may be relevant;
* WakeOnLan connection from NIC to Mobo is 'connected', though I don't
use it.
* My NIC (Netgear) info;

~$ sudo lspci -vv
[...]
0000:00:0e.0 Ethernet controller: National Semiconductor Corporation
DP83815 (MacPhyter) Ethernet Controller
Subsystem: Netgear: Unknown device f312
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 90 (2750ns min, 13000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 1400 [size=256]
Region 1: Memory at f4000000 (32-bit, non-prefetchable)
[size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=320mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

* ACPI is active (via 'acpi=force' in GRUB Kernel command line) on this
circa 1999 Intel 440BX (PentiumII) mobo;

~$ dmesg | grep -i ACPI
BIOS-e820: 000000000bffdc00 - 000000000bfffc00 (ACPI data)
BIOS-e820: 000000000bfffc00 - 000000000c000000 (ACPI NVS)
ACPI: RSDP (v000 PTLTD ) @
0x000f6a80
ACPI: RSDT (v001 PTLTD RSDT 0x00000001 PTL 0x01000000) @
0x0bffde96
ACPI: FADT (v001 GATEWA TABOR II 0x19991104 PTL 0x000f4240) @
0x0bfffb8c
ACPI: DSDT (v001 GATEWA TABOR II 0x00000001 MSFT 0x01000004) @
0x00000000
ACPI: PM-Timer IO Port: 0x8008
Kernel command line: root=/dev/hdc1 ro acpi=force
ACPI: Subsystem revision 20040326
ACPI: IRQ9 SCI: Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: Power Resource [PFAN] (on)
PCI: Using ACPI for IRQ routing
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: PCI interrupt 0000:00:07.2[D] -> GSI 9 (level, low) -> IRQ 9
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 9 (level, low) -> IRQ 9
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: (supports S0 S1 S5)
ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:07.2[D] -> GSI 9 (level, low) -> IRQ 9
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5

* These last 4 'fail' entries above only occur using the 2.6 kernel,
and while I don't have a 2.4 setup installed right now, I recall these
errors specifically *not* being there without using 'hald' and whatever
udev elements(vs devfs) the 2.6.8-2 kernel uses.

* Speaking of the 2.4 kernel; when Debian was on this system using the
2.4 kernel, this issue never occured (IIRC). I've reinstalled Debian
quite a few times, for various reasons, over the last year or
so...sometimes using 2.4, sometimes 2.6, sometimes using the
[+]FileServer install along with [+]Desktop, but most times not. Either
way, this is the 1st install of Debian using a separate (physical) HD
drive (on a very LOUD small 9.1 GB Western Digital)...and in this case
- both FileServer + Desktop were chosen during install time.

~$ dmesg | grep -i hd*
[...]
hda: HDS728080PLAT20, ATA DISK drive # win98 on 80GB Hitachi
hdb: LITE-ON LTR-32123S, ATAPI CD/DVD-ROM drive
hdc: WDC AC29100D, ATA DISK drive # Debian Sarge on 9.1GB WD
hdd: _NEC DVD_RW ND-3550A, ATAPI CD/DVD-ROM drive

Also note;
I've uninstalled the AppleTalk Services(?) a couple months back --
During Boot, the system would take a l-o-n-g time and get hung up
(30-60seconds) trying to locate/find/initialize the AppleTalk stuff
that gets installed when choosing 'FileServer' - drats, I don't have
the exact dmesg/messages from that time (maybe a few months ago). I
think I tracked down the issue and used Synaptic to uninstall, though I
don't believe I "purged".

....Aha!!
It was called 'Netatalk', 'atalkd', and 'afpd'...
w00t! -- I just figured out how to use gzip to view docs that have root
as owner :-) (KDE, Konquerer complains - permission denied, for good
reason, I know)

$ cd /var/log
$ ls -al | less
-rw-r----- 1 root adm 67234 2006-06-10 06:17 syslog
-rw-r----- 1 root adm 24864 2006-06-08 06:25 syslog.0
-rw-r----- 1 root adm 14621 2006-05-26 06:25 syslog.1.gz
-rw-r----- 1 root adm 616 2006-05-07 06:25 syslog.2.gz
-rw-r----- 1 root adm 13858 2006-05-06 06:25 syslog.3.gz
-rw-r----- 1 root adm 14734 2006-05-03 06:25 syslog.4.gz
-rw-r----- 1 root adm 10989 2006-05-01 06:25 syslog.5.gz
(note the Dates)

$ sudo gzip -dc syslog.5.gz | less
[...]
May 1 05:44:12 localhost kernel: eth0: DSPCFG accepted after 0 usec.
May 1 05:44:12 localhost kernel: eth0: link up.
May 1 05:44:12 localhost kernel: eth0: Setting full-duplex based on
negotiated link capability.
May 1 05:44:12 localhost kernel: NET: Registered protocol family 17
May 1 05:44:15 localhost lpd[3078]: restarted
May 1 05:44:15 localhost kernel: NET: Registered protocol family 5
May 1 05:44:15 localhost atalkd[3097]: restart (2.0.2)
May 1 05:44:16 localhost atalkd[3097]: zip_getnetinfo for eth0
May 1 05:44:36 localhost last message repeated 2 times
May 1 05:44:46 localhost atalkd[3097]: config for no router
May 1 05:44:47 localhost atalkd[3097]: ready 0/0/0
May 1 05:44:59 localhost papd[3105]: restart (2.0.2)
May 1 05:44:59 localhost papd[3105]: CUPS support enabled (1.1)
May 1 05:45:00 localhost afpd[3107]: Registering CNID module [last]
May 1 05:45:00 localhost afpd[3107]: Registering CNID module [cdb]
May 1 05:45:00 localhost afpd[3107]: Registering CNID module [dbd]
May 1 05:45:00 localhost afpd[3107]: Loading ConfigFile
May 1 05:45:00 localhost afpd[3107]: Finished parsing Config File
May 1 05:45:01 localhost kernel: NET: Registered protocol family 10
May 1 05:45:01 localhost kernel: Disabled Privacy Extensions on device
c02cc960(lo)
May 1 05:45:01 localhost kernel: IPv6 over IPv4 tunneling driver
May 1 05:45:02 localhost rpc.statd[3149]: Version 1.0.6 Starting
May 1 05:45:02 localhost rpc.statd[3149]: statd running as root. chown
/var/lib/nfs/sm to choose di
fferent user
May 1 05:45:02 localhost /usr/sbin/cron[3154]: (CRON) INFO (pidfile fd
= 3)
May 1 05:45:02 localhost /usr/sbin/cron[3155]: (CRON) STARTUP (fork
ok)
May 1 05:45:02 localhost /usr/sbin/cron[3155]: (CRON) INFO (Running
@reboot jobs)


Lessee...

=========================================
[..snipped...most of this older post from Donald Becker, archived by
Moe...]
This can be solved by using the 'pci-scan' module and updated driver
from
http://www.scyld.com/network/updates.html
[...snipped...]
==========================================

So...
because my problem is the opposite, I wouldn't think this would be
useful to me(?) since it's winblows that has this 169.254.x.x addy
*after* being booted into Debian.

you likley will see a 169.xxx.xxx.xxx address
given to your NIC - this is some sort of twisted Multicast IP addy
(which is what mine defaults to when this occurs).

See RFC3330 - it's actually a random address in the 169.254.x.x range,
called ZeroConf. Microsoft adopted this concept (originally from Apple)
[...]

Thanks for the refresher - I couldn't recall the specifics offhand -
http://en.wikipedia.org/wiki/Zeroconf has some info...and your
abundance of networking experience helps too.

The problem is that windoze has screwed up the configuration of the card,
and only a power-on reset (or the front panel reset button if you still
have one of those) will grab the card's attention.

I wonder how much the Client for MS Networking (win98) munges the
settings.

WAG; it may have something to do with the fact that I have smbd and
nmbd daemons running while in Linux (and perhaps others associated with
File Server setup) , which then wreak havoc on the router's DHCP server
capabilities.

Nope - nothing to do with it.

Okee Dokee - I'll easily accept that from someone as experienced as
you, no prob :-)

[Aside]
perhaps using the 'followup-to' header would be more appropro, I'm not
sure. :(

Normally it is, and as you quoted the entire thread without trimming
(normally a no-no),

Understood ...In this case - is about the only time that I can think
of offhand, that I'd quote the entire (albeit small) thread...and only
if I catch it early on, as I have in this case.

every one there should be able to pick it up. I did
set the followup-to, so the O/P should look in that group for further
responses.

Noted - and (hopefully) retained :-)
[/Aside]

Thanks for any/all input about these problems, and I hope I haven't
hijacked this thread...if I have - just disregard this post - this
minor issue is not a huge deal for me, considering all the other issues
I'm having with my installation (too intricate - especially for this
thread).

Thanks again Moe Trin
Regards

.